aempro not logging O2#1 when pc logging

[ComputerJLT]

so i have a innovate lm1 wired in to a mk4 supra box; the ems software shows AFR no problem and the box logs o2#1 when configured to do so but when i do the pc logging o2#1 shows 0 in the logs

i tried restarting the software, nothing; restarted the laptop; nothing

have not tried another laptop yet and have not reinstalled the software

this is the first time this has happened; this same laptop w/ the same aempro software (latest version btw) has logged o21 from a 1050 box but now its not..

anyone have any ideas?

/edit: 1.19 firmware and cal btw; o2 feedback disabled only wired the lm1 into the aem to log but now i can't log

[specialed]

so i have a innovate lm1 wired in to a mk4 supra box; the ems software shows AFR no problem and the box logs o2#1 when configured to do so but when i do the pc logging o2#1 shows 0 in the logs

i tried restarting the software, nothing; restarted the laptop; nothing

have not tried another laptop yet and have not reinstalled the software

this is the first time this has happened; this same laptop w/ the same aempro software (latest version btw) has logged o21 from a 1050 box but now its not..

anyone have any ideas?

/edit: 1.19 firmware and cal btw; o2 feedback disabled only wired the lm1 into the aem to log but now i can't log

Are you sure you only have one parameter window open with the O2 #1 parameter when starting your PC Log?

[mx5]

In your calibration - what are the AFR Scalar and Offset options set to?
If I have to guess you have both set at 0 (which is wrong) and your problem should be right there

[specialed]

If your AFR Scaler and Offset values are modified at all, I'd suggest reloading a clean AEM startup calibration. Whether or not you converted a calibration or someone changed these values manually, there's a problem with that calibration file itself. Those options are only found through your Full-List and no one should really ever be browsing around back there.

[mx5]

If your AFR Scaler and Offset values are modified at all, I'd suggest reloading a clean AEM startup calibration. Whether or not you converted a calibration or someone changed these values manually, there's a problem with that calibration file itself. Those options are only found through your Full-List and no one should really ever be browsing around back there.

I guess you don't know your product
IIRC some startup calibrations already come wrongly zeroed by you and while that kinda works similar to scalar and offset values of 0.5, the problem is that logging doesn't work.

And the scalar and offset can be modified - if one wants to modify the lambda range being used (i.e. narrower range for better lambda precision). One just needs to know what those two things do before playing with them.

Why not just explain him what's wrong with the calibration he most likely got from you, instead of talking general blah blah about the two options.

[nutzsrt4]

did you change any of the aem log template parameters