I have no clue. Someone with a factory shop manual with an ECU pin printout should show a CAN hi/lo wire(s). If it's multi sensor assist, from ECU out to dashboard, CAN is wrapped around the main harness so as to split signals out to the dash. Say TPS and a stepper motor use the same sensors, how can the dash know who is who to set the code light on. Make sense? It's all about frequency interferences.
The ignore boils down to this. To ride a limped bike, codes run under the a/N Method. Said as Alpha/numeric or follows nature how FI is handcuffed to the 1 ATMO, or 14.7 = Digital.
You were running Analog with no codes. Sensor drops out of the loop, it resets how to follow the rpm as throttle input. You have the light to mid throttle load, then the WOT heavy load. So to know if you are in a protected limp mode, where the ignition curve is going to stumble up the ignition curve, injectors might spit sporadic, it's going to buck and misfire kind of no throttle up is the code is set. No code is linear smooth up to redline.
Buck up to redline or way before that, then it's a hard set code. Smooth as glass, ignore it says phantom codes. Don't know how sophisticated an ECU is these days, but going thru different generations of the same bike, one ECU would turn the code off within seconds. Latest bike uses an 02 sensor.
I disconnected it to see if it rode different. I reconnected and it did not shut off till so many key turns later. I ignored it because it was a simple disconnect. I can only take a wild guess and it learned all over again, thinking, the disconnect flushed the RAM it had saved, but the disconnect dumped to ground doing that I guess, thus the relearn?
I've disconnected the TPS and that sets the Method. Did the old bucking bronco and learned it will limp you home, but getting to redline is not about to happen. So the guess is let it learn and eventually shuts off? Or, pin swap at the harness between years? Same black box. Where a weather-pac pin is in the connector, meaning 'not used.'
Again, book calls the pin out so as to match pin to wire.
The ignore boils down to this. To ride a limped bike, codes run under the a/N Method. Said as Alpha/numeric or follows nature how FI is handcuffed to the 1 ATMO, or 14.7 = Digital.
You were running Analog with no codes. Sensor drops out of the loop, it resets how to follow the rpm as throttle input. You have the light to mid throttle load, then the WOT heavy load. So to know if you are in a protected limp mode, where the ignition curve is going to stumble up the ignition curve, injectors might spit sporadic, it's going to buck and misfire kind of no throttle up is the code is set. No code is linear smooth up to redline.
Buck up to redline or way before that, then it's a hard set code. Smooth as glass, ignore it says phantom codes. Don't know how sophisticated an ECU is these days, but going thru different generations of the same bike, one ECU would turn the code off within seconds. Latest bike uses an 02 sensor.
I disconnected it to see if it rode different. I reconnected and it did not shut off till so many key turns later. I ignored it because it was a simple disconnect. I can only take a wild guess and it learned all over again, thinking, the disconnect flushed the RAM it had saved, but the disconnect dumped to ground doing that I guess, thus the relearn?
I've disconnected the TPS and that sets the Method. Did the old bucking bronco and learned it will limp you home, but getting to redline is not about to happen. So the guess is let it learn and eventually shuts off? Or, pin swap at the harness between years? Same black box. Where a weather-pac pin is in the connector, meaning 'not used.'
Again, book calls the pin out so as to match pin to wire.
