What is the EXT.AD1 pid doing, Trackman?
That will tell you if the V2 is reading the input and it's just a calc.pid thing.
What is the EXT.AD1 pid doing, Trackman?
That will tell you if the V2 is reading the input and it's just a calc.pid thing.
I don't know the answer to that. I assumed if it was on it was doing it's job.
The scantool is freezing...? Are you able to post a screenshot...? Do you remember if the scantool was from a V7 build from this year...?
The scantool is not freezing.The afr pid is just stuck on a random number.
I believe the V7 build is from last fall. V7.5.7 build 282
I just don't understand what has changed from the summer of 2014 when the pid worked perfectly to now.
You need the latest software (EXT.ADx pids got broken and have been since fixed).
I updated to the March 2016 public pre release.
I have a V2.
I look forward to testing.
It seems to be working correctly now.
I am guessing the update was all that was needed .
Thanks again Joecar.
I was comparing my older cal pid vs the new version. I noticed the low and high of currently used pid are slightly different. Would this have any affect on my afr readings on my V2? The monitor does read from 9(0.5v)-20(4.5v) which is the low and high settings of the older pid version.
Last edited by Trackman; May 17th, 2016 at 06:09 AM.
Low, High, Fmt:
these are used to set the minimum tick mark, the maximum tick mark, and the number of digits after the decimal point when you add that pid to a chart or a gauge...
i.e. they effect how the guage/chart looks, they do not effect the value range of the pid.