ECM Hope?

First - thanks to all the smart folks here trying to solve our fleet wide ECM problem.

Second - I was looking at the ECM poll and might there be a clue to the cause of this by comparing the police bike to non-police bike ECM’s…..since none of the 2002-2007 police bike owners have reported a 25/26 issue? Just an observation.
 
There are some wiring differences with P version. Strobe lights and horn harness. Also flasher relay is 3-wire with ground. However, knock-sensor circuit to ECM wiring is exactly same.

I suppose difference in code 25/26 reports may be due to significantly smaller number of P models. Along with more regular maintenance during their 1st 80-90k-miles. And less likelihood they have had electrical farkles while in service. Once into private hands however…
 
Last edited:
First - thanks to all the smart folks here trying to solve our fleet wide ECM problem.

Second - I was looking at the ECM poll and might there be a clue to the cause of this by comparing the police bike to non-police bike ECM’s…..since none of the 2002-2007 police bike owners have reported a 25/26 issue? Just an observation.
Larry said:
"It’s not just pre 07 years, as I’ve seen several on new late model unit escort bikes.
But to be fair, these bikes always have a lot of jury rigged wiring stuff added on.
Let’s keep our fingers crossed. "

I don't know if these were P models or just regular bikes.


 
ECM never advances timing. Only starts with what’s programmed in maps. Then retards from there if knock is detected. This dithering always results in ignition-advance values lower than pre-programmed map values.
Correct. It is more technically precise to state that the programmed maps accomplish this if this is what you mean, but those maps reside in the ECM do they not? I chose to use the more general term of ECM when I wrote that.

The conditions of operation of the engine are constantly changing. In a compuer controlled engine the ignition timing is never stagnant, it constantly fluctuates to respond to those changes. This is one of the big benefits of computer controlled engine management vs the old system where the ignition timing was fixed based primarily on RPM regardless of the other conditions.

The maps that decide where the timing needs to be at any given instant reside in the ECM. I didn't get in to the sequence of events or pathways of how the final result is arrived at within the ECM because it doesn't matter, but in simplistic terms if those maps determine that less timing advance is needed that will be commanded. If they determine that more timing advance is needed, that will also be commanded. This is what I meant when I wrote that the ECM advances the timing. Maybe a better choice of words would have been that the ECM changes the timing as opposed to advances it because it can only change it from one fixed value value to another fixed value along its map based on the inputs that it receives from multiple sources. It constantly dithers, as you say, from one fixed value to another at an extremely high response rate based on inputs from multiple sources of data. One of those sources is the input that the ECM receives from the knock sensor, which it uses as part of the calculation to determine where the timing needs to be. A relevant signal from the knock sensor will cause the timing to be further reduced to an amount less than where the maps would normally have placed it under the conditions that are present at that moment. No such signal and the maps are free to do their thing unaltered by the conditions that are monitored by the knock sensor.
 
Knock sensors are only needed when there is a fault, such as caused by the engine or the fuel or the operator. The rest of the time they don't do anything at all. They are just fault sensors. Engine knock is abnormal. Maps do not cause knock.
 
Yeah, it's extremely difficult to trigger knock/detonation. Maybe once in decade type of thing if you tried really, really hard or did something really, really wrong! :eek: It's not part of normal engine-operation in any way, unless it's a diesel.

Sometime in '80s, Honda moved away from using ECUs with Intel chips to proprietary NEC/Hitachi CPUs which makes things a little more difficult. Renesas acquired NEC/Hitachi's ECU chip division and is now providing SuperH-based ECUs to most of Japanese & Swedish auto/moto makers. Here's some datasheets to get started.

Renesas - SH7052/53/54 datasheet
Renesas - SH7058 datasheet
NPX/Motorola - MC33186 bridge

Hitachi developed EFI system adopted by Toyota & Honda back in early '80s. It had strangely similar algorithms to Bosch's LH & D-Jetronic EFI systems...
 
Last edited:
Well I pulled the green blue ground wire from out of the ecm harness and that does not stop the code 26 from coming back.
 
Just a couple of questions if anyone can say. Since posting this I've [re]read everything available here and through some of the other relevant threads, revisited it a few times to edit my questions.

Has anyone determined specifically how feedback from the knock sensor is utilized by either the first or second version ECM.

Is feedback processing delayed until a specific rpm threshold is passed, then used [along with other sensor inputs] to sequentially trim the advance, set the [25 or 26] fault code then revert to a secondary timing mode if a reduction in advance fails to reduce the knock signal.

Or is the signal processed after a specific rpm threshold and then used only to set the fault code, revert to secondary mode based on intensity and / or duration of the feedback signal.

From what I recall seeing with some of the charts and information I'm guessing that it's later ECU programs that incorporate Knock Sensor feedback dynamically; substantially manipulating advance. Do all ST ECUs work about the same this way.

I certainly wouldn't attempt or recommend this, but has anyone with the fault attempted to relocate a knock sensor or hang the sensor away from the engine. If you haven't, don't... but if you did and it didn't blow anything up, did anything change.

Could real detonation caused by carbon fouling be the cause. If you bought the bike new, along with the service history, you'll know what grade of fuel you've used and what rpm / load you've operated the bike in. But if you bought used, it might be anyone's guess.

Is there any consensus on assessing how much carbon buildup might exist in the combustion chamber; if reading the spark plugs, a compression test and leak down test indicate carbon, would show that. Then, could running a cleaner after the fact, over some duration clean out some carbon deposits. I guess the question is has anyone resolved a 25/26 fault and attributed it to a reduction in carbon build up.

Would it be possible to monitor advance and injector pulse width / start time under load with a rising rpm and through a fault event, and could a comparison be made between one that faults and a known good one. If tests like this could be done, then we could also probably test to see if post 2008 ECUs have any manufacturing dated variances. It might be found that while all post 2008 ECUs are physically the same there are differences in knock sensing and / or secondary mode after a specific date of manufacture; could it be possible that a new replacement ECU might have the same part number and appearance but be a revised version that relies less on the knock sensors. This would make sense from a manufacturer's position, even if the real problem is burnt sensor wiring or something else, a dampened detection circuit or elimination of dynamic advance but no more faults might keep the buyer [who just spent $1800] happy.
 
Last edited:
Has anyone determined specifically how feedback from the knock sensor is utilized by either the first or second version ECM.

@DannoXYZ once posted some very interesting schematics and information on the most common industry schemes for filtering the knock sensor signal and alarming the CPU but I cannot find it anymore.

There were also interesting pictures of what the (noisy) signal looks like if I remember.
 
There was image-posting issues with most web-forums a month ago along with Google breaking image-embedding/sharing URLs. I’ll go back and repost those images.

Thanks to borrowed ECU, I’ve made some progress. Built a USB to K-line communications cable. Working up some software on Raspberry-PI to query ECU next.
 
Thanks to borrowed ECU, I’ve made some progress. Built a USB to K-line communications cable. Working up some software on Raspberry-PI to query ECU next.
Pardon a dumb question. Is the programming in the ECU that big and complicated that someone cannot take some other engine mapping (say from another Honda engine) and either transplant it and make some changes or use it as is? I have no idea if the program code runs 10's, thousands, or millions of lines, and/or how detailed said mapping is. I did read once that engine builders - race car guys - modified engine mapping to increase hp. Again, I know not what they do or how they do it.
 
....... Is the programming in the ECU complicated ......

Chances are the mapping is fine.

At fault may be more the signaling to the ECU that it needs to adjust AFR/Timing to stop detected knocking, or that the knock detection loop is actually working.

More the input to the CPU than the CPU itself.
 
Last edited:
Has anyone tried to use 2008 or later ECM since they are still available? I think it should work fine but would require the connectors to be re-pinned and upgraded to 33 pin style.

Chuck
 
The black and gray 33 pin female connectors are readily available with new pins for under $10 each so I.m planning to just re-pin the existing 2007 harness to the new connectors. If i can find the male half I will consider making some plug and play adapter harnesses. So far the only male half i found is a header that attaches to the PCB.
 
You still need to know whether the later ECM will operate the earlier engine.

They may have changed the connectors so people wouldn't try substitution.
 
You still need to know whether the later ECM will operate the earlier engine.

They may have changed the connectors so people wouldn't try substitution.
The sensors retain the same part numbers. I have successfully done this on pre 2000 valkyrie to GL1500 Goldwing ECM. Some of the mapping may be different for emission purposes but I have little doubt that the engine will run fine without throwing FI error codes. I have connectors on the way. Just need to find an good used ECM for a 2008 or later
 
The sensors retain the same part numbers. I have successfully done this on pre 2000 valkyrie to GL1500 Goldwing ECM. Some of the mapping may be different for emission purposes but I have little doubt that the engine will run fine without throwing FI error codes. I have connectors on the way. Just need to find an good used ECM for a 2008 or later
I sent mine to @DannoXYZ for testing.
 
Back
Top Bottom