Constant Disconnects and Detection of Interface

[KrisS]

Having not used it in years, I recently installed 7.5 for use with my AT V2 interface. It detects the interface and connects, but as soon as it begins collecting data, it disconnects and redetects the interface as below. I also note that it sets the speed to 19,200 regardless of the port setting.

Any input is appreciated.

Thanks, Kris

11:36:26.140: Autodetect interface ...
11:36:26.281: Interface firmware version: 2.0.2
11:36:26.281: Connection to [AT1] interface is OK
11:36:26.312: Autodetect PCM...
11:36:26.359: Connection to PCM is OK
11:36:26.359: Autodetect TCM...
11:36:27.375: TCM not detected.
11:36:27.390: Current protocol: "SAE J1850 VPW"
11:36:27.406: Interface firmware model: AT1
11:36:27.421: Interface firmware version: 2.0.2
11:36:27.437: Interface firmware date: Sep 24, 2002
11:36:27.453: AutoTap serial number: xxxxxx
11:36:27.531: Request GM VIN...
11:36:27.640: VIN: xxxxxx
11:36:27.656: Request serial number...
11:36:27.765: Serial number: xxxxxx
11:36:27.765: Request hardware number...
11:36:27.828: Hardware: 9386530
11:36:27.828: Request GM operating system...
11:36:27.875: GM operating system: 12593358
11:36:27.875: Request GM NVM...
11:36:27.921: GM NVM: 12204901
11:36:27.921: Request GM Engine calibration...
11:36:27.968: Request GM Engine diagnostics...
11:36:28.015: Request GM Transmission calibration...
11:36:28.062: Request GM Transmission diagnostics...
11:36:28.125: Request GM Fuel system...
11:36:28.156: Request GM System...
11:36:28.203: Request GM Speedometer...
11:36:28.250: Request GM BCC...
11:36:28.296: GM BCC: DHYN
11:36:28.296: Request GM VAT/IGN Cycles...
11:36:28.343: GM VAT/IGN cycles: 0
11:36:28.343: Request GM oil life...
11:36:28.562: Oil life: 100
11:36:28.562: Query support for stream.01 scan mode...
11:36:28.750: Query support for stream.02 scan mode...
11:36:28.953: Calculating number of dynamic packet ID's...
11:36:30.046: Loading generic configuration file: sae_generic.txt
11:36:30.046: User defined calculated PIDs file: calc_pids.txt
11:36:30.046: Enhanced configuration file: gm_enhanced.prn
11:36:30.718: Request GM VIN...
11:36:31.015: VIN: xxxxxxx
11:36:31.015: Request GM operating system...
11:36:31.062: GM operating system: 12593358
11:36:31.078: Validating PIDs...
11:36:31.359: Validating Modules...
11:36:31.375: Initialising PIDs...
11:36:31.921: Initialising Modules...
11:36:31.953: Ready.

11:36:42.546: Programming PID GM.AFR, into dynamic packet 0[0..1] offset: 0...
11:36:42.593: Programming PID GM.MAFFREQ, into dynamic packet 0[2..3] offset: 2...
11:36:42.640: Programming PID SAE.FUELSYS, into dynamic packet 0[4..5] offset: 4...
11:36:42.703: Programming PID SAE.MAF, into dynamic packet 1[0..1] offset: 0...
11:36:42.750: Programming PID SAE.RPM, into dynamic packet 1[2..3] offset: 2...
11:36:42.796: Programming PID GM.FTC, into dynamic packet 1[4..4] offset: 4...
11:36:42.843: Programming PID GM.HO2S11, into dynamic packet 1[5..5] offset: 5...
11:36:43.062: Programming PID GM.HO2S21, into dynamic packet 2[0..0] offset: 0...
11:36:43.109: Programming PID GM.KR, into dynamic packet 2[1..1] offset: 1...
11:36:43.140: Programming PID SAE.ECT, into dynamic packet 2[2..2] offset: 2...
11:36:43.203: Programming PID SAE.IAT, into dynamic packet 2[3..3] offset: 3...
11:36:43.234: Programming PID SAE.LONGFT1, into dynamic packet 2[4..4] offset: 4...
11:36:43.281: Programming PID SAE.LONGFT2, into dynamic packet 2[5..5] offset: 5...
11:36:43.312: Programming PID SAE.MAP, into dynamic packet 3[0..0] offset: 0...
11:36:43.359: Programming PID SAE.SHRTFT1, into dynamic packet 3[1..1] offset: 1...
11:36:43.406: Programming PID SAE.SHRTFT2, into dynamic packet 3[2..2] offset: 2...
11:36:43.453: Programming PID SAE.SPARKADV, into dynamic packet 3[3..3] offset: 3...
11:36:43.484: Programming PID SAE.TP, into dynamic packet 3[4..4] offset: 4...
11:36:43.515: Programming PID SAE.VSS, into dynamic packet 3[5..5] offset: 5...
11:36:43.562: Using scan mode: Stream-Fast
11:36:45.562: Autodetect interface ...
11:36:46.234: Interface not detected
11:36:46.250: Autodetect interface ...
11:36:47.125: Interface not detected
11:36:47.140: Autodetect interface ...
11:36:48.015: Interface not detected
11:36:48.031: Autodetect interface ...
11:36:48.703: Interface not detected
11:36:48.718: Autodetect interface ...
11:36:49.593: Interface not detected
11:36:49.656: Autodetect interface ...
11:36:50.453: Interface firmware version: 2.0.2
11:36:50.453: Connection to [AT1] interface is OK
11:36:50.468: Autodetect PCM...
11:36:50.531: Connection to PCM is OK
11:36:50.531: Programming PID GM.AFR, into dynamic packet 0[0..1] offset: 0...
11:36:50.578: Programming PID GM.MAFFREQ, into dynamic packet 0[2..3] offset: 2...
11:36:50.625: Programming PID SAE.FUELSYS, into dynamic packet 0[4..5] offset: 4...
11:36:50.671: Programming PID SAE.MAF, into dynamic packet 1[0..1] offset: 0...
11:36:50.718: Programming PID SAE.RPM, into dynamic packet 1[2..3] offset: 2...
11:36:50.765: Programming PID GM.FTC, into dynamic packet 1[4..4] offset: 4...
11:36:50.812: Programming PID GM.HO2S11, into dynamic packet 1[5..5] offset: 5...
11:36:50.859: Programming PID GM.HO2S21, into dynamic packet 2[0..0] offset: 0...
11:36:50.921: Programming PID GM.KR, into dynamic packet 2[1..1] offset: 1...
11:36:50.968: Programming PID SAE.ECT, into dynamic packet 2[2..2] offset: 2...
11:36:51.015: Programming PID SAE.IAT, into dynamic packet 2[3..3] offset: 3...
11:36:51.062: Programming PID SAE.LONGFT1, into dynamic packet 2[4..4] offset: 4...
11:36:51.109: Programming PID SAE.LONGFT2, into dynamic packet 2[5..5] offset: 5...
11:36:51.171: Programming PID SAE.MAP, into dynamic packet 3[0..0] offset: 0...
11:36:51.218: Programming PID SAE.SHRTFT1, into dynamic packet 3[1..1] offset: 1...
11:36:51.281: Programming PID SAE.SHRTFT2, into dynamic packet 3[2..2] offset: 2...
11:36:51.328: Programming PID SAE.SPARKADV, into dynamic packet 3[3..3] offset: 3...
11:36:51.375: Programming PID SAE.TP, into dynamic packet 3[4..4] offset: 4...
11:36:51.515: Programming PID SAE.VSS, into dynamic packet 3[5..5] offset: 5...
11:36:52.921: Autodetect interface ...
11:36:53.578: Interface not detected
11:36:53.593: Autodetect interface ...
11:36:54.375: Interface not detected
11:36:54.390: Autodetect interface ...
11:36:55.250: Interface not detected
11:36:55.265: Autodetect interface ...
11:36:55.921: Interface not detected
11:36:55.937: Autodetect interface ...
11:36:56.796: Interface not detected
11:36:56.828: Autodetect interface ...
11:36:57.593: Interface firmware version: 2.0.2
11:36:57.593: Connection to [AT1] interface is OK
11:36:57.609: Autodetect PCM...
11:36:57.640: Connection to PCM is OK
11:36:57.656: Programming PID GM.AFR, into dynamic packet 0[0..1] offset: 0...
11:36:57.703: Programming PID GM.MAFFREQ, into dynamic packet 0[2..3] offset: 2...
11:36:57.734: Programming PID SAE.FUELSYS, into dynamic packet 0[4..5] offset: 4...
11:36:57.781: Programming PID SAE.MAF, into dynamic packet 1[0..1] offset: 0...
11:36:57.843: Programming PID SAE.RPM, into dynamic packet 1[2..3] offset: 2...
11:36:57.890: Programming PID GM.FTC, into dynamic packet 1[4..4] offset: 4...
11:36:57.921: Programming PID GM.HO2S11, into dynamic packet 1[5..5] offset: 5...
11:36:57.953: Programming PID GM.HO2S21, into dynamic packet 2[0..0] offset: 0...
11:36:58.000: Programming PID GM.KR, into dynamic packet 2[1..1] offset: 1...
11:36:58.031: Programming PID SAE.ECT, into dynamic packet 2[2..2] offset: 2...
11:36:58.078: Programming PID SAE.IAT, into dynamic packet 2[3..3] offset: 3...
11:36:58.109: Programming PID SAE.LONGFT1, into dynamic packet 2[4..4] offset: 4...
11:36:58.156: Programming PID SAE.LONGFT2, into dynamic packet 2[5..5] offset: 5...
11:36:58.203: Programming PID SAE.MAP, into dynamic packet 3[0..0] offset: 0...
11:36:58.265: Programming PID SAE.SHRTFT1, into dynamic packet 3[1..1] offset: 1...
11:36:58.312: Programming PID SAE.SHRTFT2, into dynamic packet 3[2..2] offset: 2...
11:36:58.359: Programming PID SAE.SPARKADV, into dynamic packet 3[3..3] offset: 3...
11:36:58.406: Programming PID SAE.TP, into dynamic packet 3[4..4] offset: 4...
11:36:58.453: Programming PID SAE.VSS, into dynamic packet 3[5..5] offset: 5...
11:36:58.781: Autodetect interface ...
11:36:58.921: Interface firmware version: 2.0.2
11:36:58.921: Connection to [AT1] interface is OK
11:36:58.937: Autodetect PCM...
11:36:58.984: Connection to PCM is OK
11:37:02.515: Autodetect interface ...
11:37:03.171: Interface not detected
11:37:03.187: Autodetect interface ...
11:37:04.046: Interface not detected
11:37:04.062: Autodetect interface ...
11:37:09.390: Interface firmware version: 2.0.2
11:37:09.406: Connection to [AT1] interface is OK
11:37:09.406: Autodetect PCM...
11:37:09.453: Connection to PCM is OK
11:37:09.453: Programming PID GM.AFR, into dynamic packet 0[0..1] offset: 0

[Tordne]

The first things I would ask you to do is install the latest version of the V7.5 software (at time of this post 7.5.6 Build 112). The software can be downloaded form here: http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

If you still have issues please let us know and we can look at the issue on the current build of the software.

[KrisS]

Using the latest build, the result is nearly identical. It still shows 19,200 baud, and constantly reconnects. The only difference is that I can now stream data with key-on, engine-off. Before it would only stream with the engine running.

Input is appreciated.

[Tordne]

I wouldn't have expected the "streaming" to have changed. What you may notice is that wen you Monitor (not record) the gauges will move but the graphs will not.

I'll email Paul who can hopefully test with an AutoTap cable.

[Blacky]

I'll test it out tomorrow. I don't have an AutoTap cable in the office today.
Regards
Paul

[Blacky]

I just tested with an AutoTap AT1 V2 with firmware 2.0.2 and it scanned/logged data on an LS1 correctly.
I was using the latest EFILive software available here:
http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

A couple of things to try:
1. Try changing the Scan Mode to General on the [Logging] tab page of the Properties window in the Scan Tool. It will be very slow (1 frame per second) but it will confirm whether you can receive data from the PCM.
2. Try removing all the PIDs except TP (throttle position), then try to log data with key on and ignition off.

Lastly, after you have attempted to log data and it has tried to reconnect, stop the logging and save a user error report and send it to me at paul@efilive.com
To save an error report use the File->Generate Error Report menu option.

Regards
Paul

[Blacky]

Lastly, after you have attempted to log data and it has tried to reconnect, stop the logging and save a user error report and send it to me at paul@efilive.com
To save an error report use the File->Generate Error Report menu option.


Ignore that, I see you've already posted an error report, I'm looking it over now.

Regards
Paul

[Blacky]

Looking at the error report there is data being dropped. It is most likely caused by faulty connectors, cables or even a faulty AT1 unit.

The cable that goes from the AutoCal device to the vehicle's OBDII connector is compatible with EFILive's OBDII connector.
The cable that goes from the AutoCal device to the PC's serial port is just a standard RS232 serial cable.

It may be worth replacing one or both of those cables. I can't say for sure that will fix the problem, but if there is a broken wire that is failing intermittently that may explain the symptoms.


I'm basing it on this data from the log:
11:36:45.484 Recv: $01,$01,$C1,$0B,$6C,$F1,$10,$6A,$FE,$3A,$83,$19,$2 3,$02,$02,$A0
11:36:45.484 Recv: $01,$01,$C1,$0B,$6C,$F1,$10,$6A,$FD,$04,$10,$0E,$6 B,$13,$94,$D6
11:36:45.484 Recv: $01,$01,$C1,$0B,$6C,$F1,$10,$6A,$FC,$33,$00,$83,$4 0,$7E,$7A,$8F
11:36:45.484 Recv: $01,$01,$C1,$0B,$6C,$F1,$10,$6A,$FB,$2F,$82,$83,$9 E,$0C,$00,$7E
11:36:45.484 Recv: $F1,$10,$6A,$FC,$2E,$00,$83,$40,$7E,$7A,$8A,$01,$0 1,$C1,$0B,$6C,$F1,$10,$6A,$FB,$2F,$82,$83,$A5,$0C, $00,$85,$01,$01,$C1,$0B,$6C,$F1,$10,$6A,$FE,$3A,$8 3,$19,$00,$02,$02,$7D,$01,$01,$C1,$0B,$6C,$F1,$10, $6A


The green shows the correct streaming data being received by the AutoCal device, the red shows where the data begins to get corrupted. 5 bytes of data ($01,$01,$C1,$0B,$6C) were not either received by the AutoCal device or not transmitted by the AUtoCal device to the PC or were not received by the PC (I can't tell which of those connections failed).

Regards
Paul

[Blacky]

The only difference is that I can now stream data with key-on, engine-off. Before it would only stream with the engine running.
Input is appreciated.

It may be a voltage supply issue on the OBDII connector. If you have a multimeter, check that you have 12V always (with ign on and off) between pin 16 (lower right pin) and pins 4&5 center top two pins).

Also make sure that you battery voltage and alternator voltage supply is adequate.

Regards
Paul

[KrisS]

Balcky/Everyone,

I appreciate the support.

As the voltage was good, I swapped the cables from my EFI-Live and it is working - thanks!

I have yet to confirm which cable it is, but if it is the ALDL cable, does anyone know where an inexpensive replacment can be found?

Thanks, Kris

[Blacky]

This cable is compatible with the AutoTap interface:
http://www.efilive.com/index.php?page=shop.product_details&flypage=flypage_EFILive.tpl&product_id=45&category_id=7&option=com_virtuemart&Itemid=56
Its only $19, however the shipping from NZ would be about $40 overnight or around $5 by post.

Maybe AutoTap (www.autotap.com (http://www.autotap.com)) still sells replacement cables. I know that when they did, it was around $19 also. If you can get it through them then the shipping would only be a few dollars.

Or you can make one yourself by purchasing an OBDII cable end here:
http://www.multiplex-engineering.com/cables.htm (see cable #15) and then soldering your own 9 pin female serial plug onto the end.

The wiring pinouts are described on page 3 of this document:
http://download.efilive.com/Tutorials/PDF/Bench%20Harness%20Tutorial.pdf

Regards
Paul

[Ira]

That looks like a V1 OBD cable, I have plenty in stock for the same price as the web site and a lot less shipping because I'm in Los Angeles.

Ira