Printable View
Hi Guys
I have run into some difficulty today after flasing updated tune to E38.
I takes quite some time to connect to the vehicle. Once connected I can start log but it only lasts for 400 odd frames then freezes.
I attempted to flash previous tune back and it wont communicate with the PCM at all.
Any suggestions welcome.
Cheers Rob
PS I am loading V7.5 again as I type so hopefully this fixes the bug.
Try....
- Checking the ODB-II cable and ensure it is making a good connection at both ends.
- Ensure the ignition is turned "on".
- Try rebooting the PC, then connecting the V2 and then stating EFILive.
- try a PCM reset by pulling the PCM/ECM/BCM fuse ( 10A from memory ) and turning on th ignition till the warning tone is heard. then turn off and replace the fuse.
- try disconnecting the car battery for 10 to 15 min if all else fails.
Simon
Swingy I triedall of your suggestions to no avail.
Here is the routine from start to fail
13:49:49.420: EFILive V7.5 Version V7.5.5 (Build 83)
13:50:10.090: Ready.
13:54:22.763: Scanning for EFILive FlashScan V2 USB
13:54:22.779: Autodetect interface ...
13:54:24.666: Interface not detected
13:54:25.353: Scanning for EFILive FlashScan V2 HAPI
13:54:25.368: Autodetect interface ...
13:54:25.446: Interface firmware version: 2.6.6
13:54:25.446: Connection to [FSV2] interface is OK
13:54:25.478: CAN-VPW Bridge Activated
13:54:25.493: Current protocol set to: "ISO 15765 CAN"
13:54:25.493: Autodetect PCM...
13:54:27.568: PCM not detected.
13:54:27.568: Autodetect ECM...
13:54:27.599: Connection to ECM is OK
13:54:27.599: Autodetect TCM...
13:54:27.630: Connection to TCM is OK
13:54:27.662: Current protocol: "ISO 15765 CAN"
13:54:27.693: Interface firmware model: FSV2
13:54:27.724: Interface firmware version: 2.6.6
13:54:27.755: Interface firmware date: Dec 14, 2008
13:54:27.771: FlashScan serial number: 003685700619
13:54:27.786: FlashScan license number: 003685700619
13:54:27.864: Request GM VIN...
13:54:27.989: VIN: 6G1EX55H09L169486
13:54:27.989: Request serial number...
13:54:28.114: Serial number: 86K17355W1CM
13:54:28.114: Request hardware number...
13:54:28.114: Hardware: 0
13:54:28.223: Request GM operating system...
13:54:28.239: GM operating system: 12624402
13:54:28.254: Request GM NVM...
13:54:28.286: GM NVM: 12624488
13:54:28.286: Request GM Engine calibration...
13:54:28.301: Request GM Engine diagnostics...
13:54:28.332: Request GM Transmission calibration...
13:54:28.364: Request GM Transmission diagnostics...
13:54:28.379: Request GM Fuel system...
13:54:28.410: Request GM System...
13:54:28.426: Request GM Speedometer...
13:54:28.457: Request GM BCC...
13:54:28.504: GM BCC: YRTM
13:54:28.504: Request GM VAT/IGN Cycles...
13:54:28.535: GM VAT/IGN cycles: 0
13:54:28.535: Request GM oil life...
13:54:28.566: Oil life: 82
13:54:28.566: Query support for stream.01 scan mode...
13:54:28.863: Query support for stream.02 scan mode...
13:54:28.972: Calculating number of dynamic packet ID's...
13:54:32.170: Loading generic configuration file: sae_generic.txt
13:54:32.170: User defined calculated PIDs file: calc_pids.txt
13:54:32.170: Enhanced configuration file: gm_enhanced.prn
13:54:39.518: Request GM VIN...
13:54:39.845: VIN: 6G1EX55H09L169486
13:54:40.001: Request GM operating system...
13:54:40.079: GM operating system: 12624402
13:54:40.344: Validating PIDs...
13:54:43.636: Validating Modules...
13:54:43.854: Initialising PIDs...
13:54:58.940: Initialising Modules...
13:55:00.032: Ready.
13:56:29.498: Programming PID E38.AFRATIO_DMA, into dynamic packet 0[0..1] offset: 0...
13:56:29.919: Programming PID E38.APCYL_DMA, into dynamic packet 0[2..3] offset: 2...
13:56:30.324: Programming PID E38.ESTCATDEG_DMA, into dynamic packet 0[4..5] offset: 4...
13:56:30.855: Programming PID E38.INVLVTMP_DMA, into dynamic packet 1[0..1] offset: 0...
13:56:31.245: Programming PID GM.INJPWB1, into dynamic packet 1[2..3] offset: 2...
13:56:31.307: Programming PID GM.TRQTRANS, into dynamic packet 1[4..5] offset: 4...
13:56:31.370: Programming PID SAE.O2S11, into dynamic packet 2[0..1] offset: 0...
13:56:31.432: Programming PID SAE.RPM, into dynamic packet 2[2..3] offset: 2...
13:56:31.479: Programming PID GM.KR, into dynamic packet 2[4..4] offset: 4...
13:56:31.557: Programming PID GM.TFT, into dynamic packet 2[5..5] offset: 5...
13:56:31.619: Programming PID SAE.ECT, into dynamic packet 3[0..0] offset: 0...
13:56:31.682: Programming PID SAE.IAT, into dynamic packet 3[1..1] offset: 1...
13:56:31.744: Programming PID SAE.MAP, into dynamic packet 3[2..2] offset: 2...
13:56:31.822: Programming PID SAE.SPARKADV, into dynamic packet 3[3..3] offset: 3...
13:56:31.884: Programming PID SAE.TP, into dynamic packet 3[4..4] offset: 4...
13:56:31.947: Programming PID SAE.VSS, into dynamic packet 3[5..5] offset: 5...
13:56:32.072: Using scan mode: Stream-Fast
13:57:09.746: Autodetect interface ...
13:57:09.855: Interface firmware version: 241.17.106
13:57:10.728: Interface firmware version: 241.17.106
13:57:10.806: Interface not detected
13:57:10.869: Autodetect interface ...
13:57:10.978: Interface firmware version: 241.17.106
13:57:11.867: Interface firmware version: 241.17.106
13:57:11.930: Interface not detected
13:57:11.976: Autodetect interface ...
13:57:12.086: Interface firmware version: 241.17.106
13:57:12.959: Interface firmware version: 241.17.106
13:57:12.990: Interface not detected
13:57:13.068: Autodetect interface ...
13:57:13.162: Interface firmware version: 241.17.106
13:57:14.067: Interface firmware version: 2.6.6
13:57:14.114: Connection to [FSV2] interface is OK
13:57:14.145: Autodetect ECM...
13:57:15.268: ECM not detected.
13:57:15.315: Autodetect interface ...
13:57:15.440: CAN-VPW Bridge Activated
13:57:15.502: Current protocol set to: "ISO 15765 CAN"
13:57:15.596: Interface firmware version: 2.6.6
13:57:15.627: Connection to [FSV2] interface is OK
13:57:15.658: Autodetect ECM...
13:57:16.750: ECM not detected.
13:57:16.797: Autodetect interface ...
13:57:16.859: CAN-VPW Bridge Activated
13:57:16.922: Current protocol set to: "ISO 15765 CAN"
13:57:17.000: Interface firmware version: 2.6.6
13:57:17.031: Connection to [FSV2] interface is OK
13:57:17.078: Autodetect ECM...
13:57:18.170: ECM not detected.
13:57:18.216: Autodetect interface ...
13:57:18.279: CAN-VPW Bridge Activated
13:57:18.341: Current protocol set to: "ISO 15765 CAN"
13:57:18.450: Interface firmware version: 2.6.6
13:57:18.482: Connection to [FSV2] interface is OK
13:57:18.497: Autodetect ECM...
13:57:19.589: ECM not detected.
13:57:19.636: Autodetect interface ...
13:57:19.698: CAN-VPW Bridge Activated
13:57:19.745: Current protocol set to: "ISO 15765 CAN"
13:57:19.839: Interface firmware version: 2.6.6
13:57:19.854: Connection to [FSV2] interface is OK
13:57:19.886: Autodetect ECM...
13:57:20.978: ECM not detected.
13:57:21.024: Autodetect interface ...
13:57:21.102: CAN-VPW Bridge Activated
13:57:21.165: Current protocol set to: "ISO 15765 CAN"
13:57:21.258: Interface firmware version: 2.6.6
13:57:21.274: Connection to [FSV2] interface is OK
13:57:21.305: Autodetect ECM...
13:57:22.413: ECM not detected.
13:57:22.460: Autodetect interface ...
13:57:22.522: CAN-VPW Bridge Activated
13:57:22.584: Current protocol set to: "ISO 15765 CAN"
13:57:22.662: Interface firmware version: 2.6.6
13:57:22.694: Connection to [FSV2] interface is OK
13:57:22.725: Autodetect ECM...
13:57:23.801: ECM not detected.
13:57:23.848: Autodetect interface ...
13:57:23.910: CAN-VPW Bridge Activated
13:57:23.973: Current protocol set to: "ISO 15765 CAN"
13:57:24.051: Interface firmware version: 2.6.6
13:57:24.082: Connection to [FSV2] interface is OK
13:57:24.113: Autodetect ECM...
13:57:25.190: ECM not detected.
13:57:25.236: Autodetect interface ...
13:57:25.299: CAN-VPW Bridge Activated
13:57:25.346: Current protocol set to: "ISO 15765 CAN"
13:57:25.439: Interface firmware version: 2.6.6
13:57:25.486: Connection to [FSV2] interface is OK
13:57:25.517: Autodetect ECM...
13:57:26.609: ECM not detected.
13:57:26.656: Autodetect interface ...
13:57:26.718: CAN-VPW Bridge Activated
13:57:26.765: Current protocol set to: "ISO 15765 CAN"
13:57:26.859: Interface firmware version: 2.6.6
13:57:26.874: Connection to [FSV2] interface is OK
13:57:26.937: Autodetect ECM...
13:57:28.044: ECM not detected.
13:57:28.091: Autodetect interface ...
13:57:28.154: CAN-VPW Bridge Activated
13:57:28.216: Current protocol set to: "ISO 15765 CAN"
13:57:28.310: Interface firmware version: 2.6.6
13:57:28.356: Connection to [FSV2] interface is OK
13:57:28.388: Autodetect ECM...
13:57:29.511: ECM not detected.
13:57:29.573: Autodetect interface ...
13:57:29.651: CAN-VPW Bridge Activated
13:57:29.729: Current protocol set to: "ISO 15765 CAN"
13:57:29.807: Interface firmware version: 2.6.6
13:57:29.838: Connection to [FSV2] interface is OK
13:57:29.870: Autodetect ECM...
13:57:30.962: ECM not detected.
13:57:31.024: Autodetect interface ...
13:57:31.102: CAN-VPW Bridge Activated
13:57:31.164: Current protocol set to: "ISO 15765 CAN"
13:57:31.258: Interface firmware version: 2.6.6
13:57:31.305: Connection to [FSV2] interface is OK
13:57:31.336: Autodetect ECM...
13:57:32.412: ECM not detected.
13:57:32.459: Autodetect interface ...
13:57:32.522: CAN-VPW Bridge Activated
13:57:32.584: Current protocol set to: "ISO 15765 CAN"
13:57:32.662: Interface firmware version: 2.6.6
13:57:32.693: Connection to [FSV2] interface is OK
13:57:32.724: Autodetect ECM...
13:57:33.801: ECM not detected.
13:57:33.848: Autodetect interface ...
13:57:33.910: CAN-VPW Bridge Activated
13:57:33.957: Current protocol set to: "ISO 15765 CAN"
13:57:34.050: Interface firmware version: 2.6.6
13:57:34.082: Connection to [FSV2] interface is OK
13:57:34.097: Autodetect ECM...
13:57:35.205: ECM not detected.
13:57:35.252: Autodetect interface ...
13:57:35.314: CAN-VPW Bridge Activated
13:57:35.361: Current protocol set to: "ISO 15765 CAN"
13:57:35.439: Interface firmware version: 2.6.6
13:57:35.470: Connection to [FSV2] interface is OK
13:57:35.486: Autodetect ECM...
13:57:36.578: ECM not detected.
13:57:36.656: Autodetect interface ...
13:57:36.718: CAN-VPW Bridge Activated
13:57:36.765: Current protocol set to: "ISO 15765 CAN"
13:57:36.858: Interface firmware version: 2.6.6
13:57:36.890: Connection to [FSV2] interface is OK
13:57:36.921: Autodetect ECM...
13:57:38.028: ECM not detected.
13:57:38.060: Autodetect interface ...
13:57:38.122: CAN-VPW Bridge Activated
13:57:38.169: Current protocol set to: "ISO 15765 CAN"
13:57:38.262: Interface firmware version: 2.6.6
13:57:38.278: Connection to [FSV2] interface is OK
13:57:38.325: Autodetect ECM...
13:57:39.666: ECM not detected.
13:57:39.729: Autodetect interface ...
13:57:39.791: CAN-VPW Bridge Activated
13:57:39.885: Current protocol set to: "ISO 15765 CAN"
13:57:40.010: Interface firmware version: 2.6.6
13:57:40.041: Connection to [FSV2] interface is OK
13:57:40.103: Autodetect ECM...
13:57:41.195: ECM not detected.
13:57:41.258: Autodetect interface ...
13:57:41.351: CAN-VPW Bridge Activated
13:57:41.460: Current protocol set to: "ISO 15765 CAN"
13:57:41.570: Interface firmware version: 2.6.6
13:57:41.585: Connection to [FSV2] interface is OK
13:57:41.648: Autodetect ECM...
13:57:42.755: ECM not detected.
13:57:42.786: Autodetect interface ...
13:57:42.849: CAN-VPW Bridge Activated
13:57:42.896: Current protocol set to: "ISO 15765 CAN"
13:57:42.989: Interface firmware version: 2.6.6
13:57:43.005: Connection to [FSV2] interface is OK
13:57:43.036: Autodetect ECM...
13:57:44.128: ECM not detected.
13:57:44.175: Autodetect interface ...
13:57:44.237: CAN-VPW Bridge Activated
13:57:44.300: Current protocol set to: "ISO 15765 CAN"
13:57:44.393: Interface firmware version: 2.6.6
13:57:44.409: Connection to [FSV2] interface is OK
13:57:44.440: Autodetect ECM...
13:57:45.548: ECM not detected.
13:57:45.594: Autodetect interface ...
13:57:45.657: CAN-VPW Bridge Activated
13:57:45.719: Current protocol set to: "ISO 15765 CAN"
13:57:45.828: Interface firmware version: 2.6.6
13:57:45.844: Connection to [FSV2] interface is OK
13:57:45.875: Autodetect ECM...
13:57:46.983: ECM not detected.
13:57:47.030: Autodetect interface ...
13:57:47.092: CAN-VPW Bridge Activated
13:57:47.154: Current protocol set to: "ISO 15765 CAN"
13:57:47.232: Interface firmware version: 2.6.6
13:57:47.264: Connection to [FSV2] interface is OK
13:57:47.295: Autodetect ECM...
13:57:48.449: ECM not detected.
In scan tool, Go to...
[edit]-[properties]-[Logging]
On the right hand side at the top, ensure "Scan Mode" is set to "Dynamic" this is what you should use for the E38.
See if that helps.
Simon
Well that got it cracking but I wonder why I've never had this problem til now.
I have changed laptops recently. Funny thing is I turned the wireless adaptor off and the whole program stopped jumping around, stalling etc etc.........spose its possible:doh2:
Anyway half way through my log I got the message attached
Had a good look over the cables cant see any nicks or squashes, cleaned both ends of the cables with contact cleaner
Thanks Simon for your input mate, I think you half sorted it, I'll try it fresh tomorrow.
Cheers Rob
You may need to check the plugs for dirt or grime as well. Dynamic mode has always been the way to go. I found out the hard way 18 months ago when it was all fairly new stuff......
BTW, don't log TP% with the E38, log ETCTP%. That way you'll actually get 0-100% instead of peaking at around 85%
Simon
boyley, are you still having trouble...?
When you get the message in post #6 can you also post the text log.
Things are better, flashed a tune this morning and logged it for about 30 mins before it hung up again. Could not reconnect.
Is this what your after Joecar
Error report generated by EFILive at 14:52:27 on Apr 09, 2009
Error code: ERR_ILINKLOST/34
Cannot communicate with interface via EFILive FlashScan V2.
EFILive Version: 7.5.5 (Build 83)
Platform: Windows NT
Version: 6.0 (build 6001)
Processor type: Pentium 2194MHz
Directories
Temporary Cache: C:\Users\KMR\Documents\EFILive\V7.5\Temporary cache
Logged Data: C:\Users\KMR\Documents\EFILive\V7.5\Logged data
Customers: C:\Users\KMR\Documents\EFILive\V7.5\Customers
Configuration: C:\Program Files\EFILive\V7.5\Configuration
Exported Data: C:\Users\KMR\Documents\EFILive\V7.5\Exported data
Images: C:\Users\KMR\Documents\EFILive\V7.5\Images
Sounds: C:\Users\KMR\Documents\EFILive\V7.5\Sounds
Maps: C:\Users\KMR\Documents\EFILive\V7.5\Maps
Pids: C:\Users\KMR\Documents\EFILive\V7.5\PIDs
Virtual Dash: C:\Users\KMR\Documents\EFILive\V7.5\VDash
Print Reports: C:\Users\KMR\Documents\EFILive\V7.5\Print reports
Bug Reports: C:\Users\KMR\Documents\EFILive\V7.5\Bug reports
Connected: No
Com port: 0
Com setup: EFILive FlashScan V2.5: USB
Requested baud rate: 115200
Cable id: 7
Cable code: FlashScan V2
Cable desc: EFILive FlashScan V2
Cable version: 2.6.6
Cable Firmware date: 20081214
Cable model: FSV2
Cable Serial number: 003685700619
Protocols: 0
Protocol list:
Auto connect: No
Scan OBDII info: No
Error retries: 1
Retry delay: 10
Message throttle: 0
Most recently used VIN: 6G1EX55H09Lxxxxxx (Note: 1)
PCM information
Hardware Number: N/A
Calibration ID: Unknown
Serial Number: Unknown
Operating System: 12624402
Engine Operation: 92223442
Engine Diagnostics: 92223454
Not used: 92223478
Not used: 92223454
Fuel System: 92223462
System: 92226294
Speedometer: 92223478
Operating System BCC: YRTM
Stream-Slow scan mode: Supported
After changing the scan mode to dynamic, the only times I've had logging issues is when there has been a physical disruption in the cables, be it USB or ODBII. I found that the RJ45 plug was very suspect, even from new and now I use a length of Velcro to ensure the RJ45 does not come loose.
try this.
- Connect up with the ignition on, but the engine doesn't need to be running.
- Start a log and give it a few seconds to capture some data.
- Start wobbling the leads and plugs to see if anything occurs. Gently pull on the RJ45 plug to see if it disconnects without actually coming free from the V2. Do the same with the USB cable.
- Normally,if you loose USB connectivity, Scan tool will attempt to reconnect and you loose the data during the disconnect.
- If you loose connection on the ODBII cable, the V2 should reset and power up on USB. This will cause the scan tool to drop the connection and not attempt to reconnect automatically.
I'm still guessing there is a bad / intermittent connection in the ODBII cable.
Simon.