View Full Version : Lost PIDs
LBZRCKS
August 25th, 2011, 08:40 AM
After updating to the most recent versions posted build 170 and v8.2.1 build 160, I seem to have lost the pids I used to log. There's another thread on duramaxdiesels.com where a few others have had the same problem. http://www.duramaxdiesels.com/forum/showthread.php?t=33433 Also when I try to use my V2 for BBL and use my previous saved PID Lists the values are all 0 and it won't save the file.
joecar
August 25th, 2011, 08:48 AM
Hi L,
Those are not the most recent versions...
see posts #1 and #9 here: Release-Candidate-2-Aug-19-2011 (http://forum.efilive.com/showthread.php?17096-Release-Candidate-2-Aug-19-2011)
LBZRCKS
August 25th, 2011, 08:52 AM
I'm downloading those now. Thanks
Hi L,
Those are not the most recent versions...
see posts #1 and #9 here: Release-Candidate-2-Aug-19-2011 (http://forum.efilive.com/showthread.php?17096-Release-Candidate-2-Aug-19-2011)
LBZRCKS
September 21st, 2011, 09:24 AM
I put installed this update along with updating the firmware and bootlock and the BBL now works again. But now there is another issue where some pids are not displaying correctly on the "dashboard" tab when trying to look at the log. I searched a little but haven't found any other threads where this seems to be an issue, but I have talked to some other people that have the same issue now too. Here's a log that doesn't show the Injection Pulse Width correctly. It does display correctly on the "data" tab though.
11998
joecar
September 21st, 2011, 10:56 AM
You mean on the chart it shows zero all the time, but on the Data tab it shows the correct value.
I pm'd Tech Support.
LBZRCKS
September 21st, 2011, 11:06 AM
You mean on the chart it shows zero all the time, but on the Data tab it shows the correct value.
I pm'd Tech Support.
Yes the data tab show's correct. I just tried it again and it was doing the same thing. It maxed out at 53, which is the same as my boost which was 52.7, so I right clicked it and tried to change it to the pid it should be showing, even though it was labeled to be showing the pulsewidth and it works now. Maybe it was some weird glitch where it was labeled one thing but actually showing the value of another?
Tordne
September 21st, 2011, 11:39 AM
Seems to be something incorrect in the graph. If you right click on the PID and select 'Other PIDs' at the bottom and then the GM.MAIN1T_DMA the values are then displayed correctly.
joecar
September 21st, 2011, 12:30 PM
Tordne is correct, see attached pic:
11999
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.