Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
Yes, with COS 2030003.
Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
Well this is getting frustrating. First of all ignore post 21, somehow the log reported properly. When I validate the FSP a 2kb file named 'external' is written. When I plug into PCM, automatic validation, a 5kb file is written named '1G1YY32G_Y5' is written. When i use the menu bar validate a 7kb file named '1G1YY32G_Y5_10' is written. You'd think they would all be the same size.
Is scan looking for the proper protocol in SAE J1850 VPW? I end up with anywhere from 348 to 370 validated pids usable while plugged into PCM.
There's a lot of talent on this forum, somebody has had to have destroyed their laptop and start all over.
Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
After you did that, does the V1 programming popup show non-zero pid channels...?
Yes but only till FSP is disconnected once from scan, like saving a Pid selection or just disconnecting. When FSP is reconnected only Pids with 0 channels are valid and these approx 70 Pids are unload-able to FSP.
Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
Misunderstood, once Pids are loaded in FSP they remain and are usable. I was mistakingly referring to scan validation.
Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
Well I believe it's a licensing issue. After validating Pids help/about still reports generic vin, PCM as N/A and PCM OS as N/A. Still no pids with a channel association selectable unless connected to PCM. The only difference I see is my upgrade is dated 15 Feb 2006 and my flashscan reports 18 Jan 2005. Anyone?
Y2K C5, M6, LS6 intake, Kooks LT headers, High flow cats, 216/224 113 LSA, 5.3 Stage II heads. STS twins. COS
I can confirm that there is a bug in the V7.5 software that will not load the validated PID list from a *.vpl file unless a vehicle is connected.
It will be fixed in the next update.
Meanwhile, you can fool the software into loading your validated PIDs by deleting the external.vpl file and renaming your vehicle's actual *.vpl file to "external.vpl". That will force the software to load your vehicle's validated PIDs when no vehicle connection exists. That is because when no connection exists it is only loading the external.vpl file (which usually contains the valid external PIDs, i.e. the analog voltage PIDs for FlashScan).
Regards
Paul
Before asking for help, please read this.