New to Tuning

[Tordne]

The device will probably show as a "USB Serial Converter" under the Universal Serial Bus controller section. If you get the device properties there should be an Advanced tab. On the Advanced tab there should be an checkbox option "Load VCP". Enable this option and then select OK to close the properties dialog.

Then disconnect and reconnect the device and you should see the new hardware wizard hopefully automatically load a driver for a new device (the Virtual COM Port). If this does happen then you should have a "Ports (COM&LPT)" section in Device Manager with the new COM device that you can further configure.

The above is all based on an assumption that the Moates device is going to present the same as a generic USB Serial Converter device. I've never actually seen one physically so can be definitive sorry.

Cheers,

[Gordon]

I have done everything that you have suggested. I downloaded the ALDL driver and installed it. I'm getting closer, but I still can't get any data to show up. This is what I get now.

15:50.015: Check vehicle interface...
15:50.021: Waiting for Aldl bus silence of at least 10ms...
15:50.027: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
15:50.045: Max232 interface detected OK

15:50.046: Scanning for heartbeat and chatter frames...
15:50.046: Waiting for Aldl bus silence of at least 10ms...
15:51.612: Heartbeat frame:
15:51.612: 15:50.109: $F0,$56,$F4,$C6
15:51.612: Heartbeat frame is followed by 64ms of silence
15:51.612: Advisable value for T6 is 32ms

15:51.612: Chatter frame(s):
15:51.612: 15:50.173: $90,$5A,$20,$00,$72,$5C,$FF,$29
15:51.612: 15:50.205: $0A,$58,$FF,$03,$27,$75
15:51.612: 15:50.268: $90,$5A,$20,$00,$72,$5C,$FF,$29

15:59.522: Start macro: Eng&Trans Data: Mode1_M0M1
15:59.517: Synchronising ALDL communications...
15:59.517: Waiting for heartbeat: $12,$55,$99
15:59.517: Waiting for Aldl bus silence of at least 10ms...
16:01.090: Heartbeat not found in previous 32 chatter frames - giving up looking for heartbeat
16:01.097: Synchronising ALDL communications...
16:01.097: Waiting for heartbeat: $12,$55,$99
16:01.097: Waiting for Aldl bus silence of at least 10ms...
16:02.690: Heartbeat not found in previous 32 chatter frames - giving up looking for heartbeat
16:02.798: Synchronising ALDL communications...
16:02.798: Waiting for heartbeat: $12,$55,$99
16:02.798: Waiting for Aldl bus silence of at least 10ms...
16:04.401: Heartbeat not found in previous 32 chatter frames - giving up looking for heartbeat
16:04.411: Stop macro: Eng&Trans Data: Mode1_M0M1

[Blacky]

Have you loaded the correct vehicle definition file for your vehicle?
I think the best one for a 94 Camaro is A274.xml

EFILive has detected that the heartbeat frame is
15:51.612: 15:50.109: $F0,$56,$F4,$C6

And that the best value for T6 is 32ms
15:51.612: Advisable value for T6 is 32ms

However, the currently loaded vehicle definition file is configured to look for a heartbeat frame of $12,$55,$99.

If you have loaded the correct vehicle definition, then you'll need to edit it to suit your vehicle. Change the heartbeat frame to $F0,$56,$F4,$C6 and change T6 to 32ms.

Or you could just try it with no heartbeat defined, like the way the A274.xml definition is defined.

Regards
Paul

[Blacky]

Don't forget to turn off the View->Show Serial I/O setting once you get it working. If you leave it on it can slow down the comms and cause data to be dropped.

Regards
Paul

[Gordon]

I changed the heartbeat frame as I also changed T6 to 32ms. This is the response,

56:32.102: Initialising...
56:32.709: Opening COM4 8228,8,N,1
56:32.920: Ready.
57:02.843: Check vehicle interface...
57:02.850: Waiting for Aldl bus silence of at least 32ms...
57:02.961: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
57:02.976: Max232 echo was incorrect:" $90,$5A,$02,$00,$77,$1C,$FF,$82
57:02.981: No response from Max232
57:02.981: Retrying Max232 detection...

57:02.981: Waiting for Aldl bus silence of at least 32ms...
57:03.024: Requesting Max232 interface to acknowlege: $FF,$5A,$02,$00,$77,$1C,$FF,$13...
57:03.025: Max232 echo was incorrect:" $0A,$58,$FF,$00,$00,$9F
57:03.035: No response from Max232
57:03.035: Retrying Max232 detection...

57:03.035: Waiting for Aldl bus silence of at least 32ms...
57:03.117: Requesting Max232 interface to acknowlege: $FF,$58,$FF,$00,$00,$AA...
57:03.120: Max232 echo was incorrect:" $F0,$56,$F4,$C6
57:03.129: No response from Max232
57:03.129: Retrying Max232 detection...

57:03.129: Interface cannot be detected

57:03.140: Scanning for heartbeat and chatter frames...
57:03.140: Waiting for Aldl bus silence of at least 32ms...
57:04.928: Heartbeat frame:
57:04.928: 57:03.520: $F0,$56,$F4,$C6
57:04.928: Heartbeat frame is followed by 64ms of silence
57:04.928: Advisable value for T6 is 32ms

57:04.928: Chatter frame(s):
57:04.928: 57:03.584: $90,$5A,$02,$00,$76,$1C,$FF,$83
57:04.928: 57:03.632: $0A,$58,$FF,$00,$00,$9F
57:04.928: 57:03.680: $90,$5A,$02,$00,$76,$1C,$FF,$83

If I try to use the definition file of A274.xml, I get an error message saying it's a missmatch.

[Blacky]

I changed the heartbeat frame as I also changed T6 to 32ms. This is the response,

57:02.961: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
57:02.976: Max232 echo was incorrect:" $90,$5A,$02,$00,$77,$1C,$FF,$82
57:02.981: No response from Max232
57:02.981: Retrying Max232 detection...

That info is telling you that the Moates cable is not echoing the requests from the EFILive software. You should un-check the "Max232 echo" check box in the properties window.

Regards
Paul

[Gordon]

I unchecked the MAX232 box.

58:38.640: Start macro: Eng&Trans DTCs: Mode1_M2
58:38.655: Synchronising ALDL communications...
58:38.655: Waiting for heartbeat: $F0,$56,$F4,$C6
58:38.655: Waiting for Aldl bus silence of at least 31ms...
58:38.796: Error: Reply frame checksum failure
58:51.562: Error: Reply frame checksum failure
59:04.967: Error: Reply frame checksum failure
59:47.487: Error: Reply frame checksum failure
59:47.503: Error: Reply frame checksum failure
59:47.519: Error: Reply frame checksum failure
59:47.520: Resuming normal ALDL communications...
59:47.535: Error: Reply frame checksum failure
59:47.538: Stop macro: Eng&Trans DTCs: Mode1_M2

[ScarabEpic22]

Change T6 to 32ms, its set at 31ms now so now it might not be waiting long enough.

[Gordon]

I need to find the fuel trim and make sure I keep it at it's correct level once I install the new injectors. I have to be able to see the data so I don't over or under compensate the setting's so I don't wash the ring's. Once I finally get the setting's correct that is when I can start the motor, watch and record the data, correct? I get no data readings being displayed in the dashboard, dtc's, charts,aldl, or status flag. I have no data coming thru, but the program is chatting with the pcm, everything is green and appears to be working smoothly now. Now this just came up.

30:33.109: Start macro: Eng&Trans Data: Mode1_M0M1
30:33.122: Synchronising ALDL communications...
30:33.122: Waiting for heartbeat: $F0,$56,$F4,$C6
30:33.122: Waiting for Aldl bus silence of at least 32ms...
30:33.443: Error: Reply frame checksum failure
30:33.459: Error: Reply frame checksum failure
30:33.572: Com timeout: Data frame truncated: $00,$79,$FC,$8C,$98,$00,$00,$10,$6E,$7E,$7F,$7C,$0 0,$FA,$01,$13,$05,$69,$00,$60,$46,$15,$02,$0E,$F3, $01,$00,$00,$00,$03,$B6,$06,$00,$00,$00,$00,$00,$0 0,$00
30:33.576: Resuming normal ALDL communications...
30:33.591: Stop macro: Eng&Trans Data: Mode1_M0M1

[Blacky]

When EFILive sends a request for data to the PCM, it expects an exact number of bytes to be returned. The number of bytes returned is different for different controllers. That is one of the reasons you must use the correct vehicle definition.

I still think A274.xml is the correct one for your vehicle.

You said earlier when you try to use that definition the software says its incompatible. Can you post the exact error message?

Regards
Paul