No AFR read with Mircosquirt
Posted: Thu May 12, 2011 10:09 am
Hi Folks,
I have run into an issue that I can't resolve on my own ad I'd need some good ideas/hints.
On my last log I had no AFR signal and so I checked everything on the bike and the sensor / controller.
- WB sensor and controller work. Confirmed on the stim with my "old" V2.2 MSI. AFR read is 19 in free air and changes when near open flame.
- Bike wiring is also ok now. Sensor ground (pin 21) had an awkwardly high resistance measured to ground, so I made a new ground point here. It now has ground contact.
- The O2 wire is also functional. Resistance between (Pin 34) on the AmpSeal 35 pin connector and the WB controller is 0 ohms.
- When unplugging the AmpSeal and turning ignition on you can measure 5V (=AFR 19) between Pin21 and 34 as I'd expect.
So the Microsquirt "should" see the right voltage, but it shows 0V EGO-voltage.
I also suspected a misconfiguration issue as TunerStudio on Linux had an error when doing the AFR calibration.
Switching to WinXP and MegaTune made the AFR calibration work, but the wrong AFR read is still persistent.
What could I have missed ? (I'm fairly experienced in MS I, but not really in MS II)
I have run into an issue that I can't resolve on my own ad I'd need some good ideas/hints.
On my last log I had no AFR signal and so I checked everything on the bike and the sensor / controller.
- WB sensor and controller work. Confirmed on the stim with my "old" V2.2 MSI. AFR read is 19 in free air and changes when near open flame.
- Bike wiring is also ok now. Sensor ground (pin 21) had an awkwardly high resistance measured to ground, so I made a new ground point here. It now has ground contact.
- The O2 wire is also functional. Resistance between (Pin 34) on the AmpSeal 35 pin connector and the WB controller is 0 ohms.
- When unplugging the AmpSeal and turning ignition on you can measure 5V (=AFR 19) between Pin21 and 34 as I'd expect.
So the Microsquirt "should" see the right voltage, but it shows 0V EGO-voltage.
I also suspected a misconfiguration issue as TunerStudio on Linux had an error when doing the AFR calibration.
Switching to WinXP and MegaTune made the AFR calibration work, but the wrong AFR read is still persistent.
What could I have missed ? (I'm fairly experienced in MS I, but not really in MS II)