rusefi.com

I have an android head unit running Torque Pro app for gauges. The AFR gauge in Torque doesn't match what I'm seeing in Tunerstudio, it seems to be inverted. If TS says 10 Torque says 20. Is there something I can do to correct this in TS? I'm using a 14point7 wideband which seems to be working properly. 0v =10, 5v = 20 AFR.

how is torque getting the afr?

how is rusEFI getting the afr?

I have a generic ELM327 device connected to android/torque via USB. The ELM is plugged into OBD2 port. This was all set up and working with the factory GM ECM CAN bus, though I never used the AFR gauge with the factory ECM.
RusEFI gets AFR from a 14Point7 WBO sensor connected to pin 26 of MRE, standard calibration, 0v=10AFR 5v=19.99AFR. MRE is connected to the factory harness using a jumper/adapter harness, including CAN lines connected to OBD2 port. Torque just automatically and unexpectedly started displaying data from RusEFI on a new screen layout that I didn't create, including an AFR gauge. Beyond that, I don't know how any of it works, I wasn't really expecting it to work without some setup.
I have also tried the Lambda gauge in Torque, it also displays backwards. Lambda 1 = Lambda 1, but Lambda 1.1 in Tunerstudio reads .9 in Torque.

That's a lot of integration! Also you use a rarely touched OBD2 monitoring part of rusEFI. One day we need a developer to look into this

https://github.com/rusefi/rusefi/issues/5160

Looks like we just have it backwards, we're sending phi instead of lambda.

https://github.com/rusefi/rusefi/pull/5164 for the fix