Moates ALDU1, 8192 baud, and v4 issues.

[95naSTA]

Hopefully you guys can help me out.

Here's what I have:
A 95 Bonneville with a L36 (95+ n/a 3.8 ) running on a $5B ID (94-95 L67 supercharged 3.8 ). I've been tuning with TunerCATs and an Ostrich 1.0.

It runs good and I have been able to use my Actron cp9110 without issue.

I just bought the ALDU1 and CABL2 Combo from Moates.net to use with EFILive v4.

Right now I only have the trial version of v4..

When I plug in the ALDU1 to my laptop, it can see the interface.

When I plug in the ALDU1 to my OBD2 style plug, it connects but then it cannot see the interface.

I selected the correct vehicle that goes with my ID, and I set both the driver and the program to COM port 2. COM port 2 is also not in use by anything else.

EFILive v4 just dosen't seem to want to work with the ALDU1..

I do know of one other person that is using EFILive v4 with the same style pcm but they built their own interface with a max 232 chip..


Does anyone have suggestions?

[Blacky]

Have you contacted Moates? It sounds like there may be a config/setup problem with the interface cable.

Regards
Paul

[Craig Moates]

Try setting it up to COM5 in the driver and software, and also set your latency timer in the driver settings down to 1 mS.

Other than that, it should work fine. The switch position should not matter, but put it in the 'open' or 'middle' position.

There are some software settings within EFI Live V4 that you'll want to play with, I'll leave it to Paul to elaborate on that.

[95naSTA]

Thanks for the replies.

After I changed both the driver and v4 to used COM port 5, and changed the latency timer to 1 ms, it now sees the interface and detects chatter at the same time. But, I still cannot 'Start aldl'.

Below is what I am getting, maybe it will help?

05:20.875: Check vehicle interface...
05:20.886: Waiting for Aldl bus silence of at least 50ms...
05:21.002: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
05:21.014: Max232 interface detected OK

05:21.016: Scanning for heartbeat and chatter frames...
05:21.016: Waiting for Aldl bus silence of at least 50ms...
05:22.236: Heartbeat frame:
05:22.236: 05:22.170: $A0,$55,$0B
05:22.236: Heartbeat frame is followed by 6ms of silence
05:22.236: Advisable value for T6 is 3ms

05:22.236: Chatter frame(s):
05:22.236: 05:22.176: $A1,$56,$00,$09
05:22.236: 05:22.225: $90,$59,$1C,$02,$0C,$5D,$90
05:22.236: 05:22.235: $91,$59,$02,$08,$FF,$34,$D9

05:48.785: Start macro: Clear diagnostic trouble codes: CLRDTC
05:48.801: Error: Max232 echo: $20,$5C,$A4,$01,$00,$1C,$20,$00,$5F,$44 did not match command: $F4,$56,$08,$AE
05:48.831: Stop macro: Clear diagnostic trouble codes: CLRDTC

06:01.049: Start macro: Clear diagnostic trouble codes: CLRDTC
06:01.091: Resuming normal ALDL communications...
06:01.117: Stop macro: Clear diagnostic trouble codes: CLRDTC

The last two sections are from trying to Start aldl.

[95naSTA]

Any other tips on reading data with EFILive v4??

[Blacky]

05:48.801: Error: Max232 echo: $20,$5C,$A4,$01,$00,$1C,$20,$00,$5F,$44 did not match command: $F4,$56,$08,$AE

Turn off the Max232 Echo checkbox in the Properties window and try again.
I'm pretty sure the Moates interface does not echo commands back to the PC like the Max232 interface does.

(Sorry, I meant to reply earlier...)

Regards
Paul

[Craig Moates]

It should echo the same way the MAX232 does.

[Blacky]

It should echo the same way the MAX232 does.

Ok, then leave the Max232 echo checkbox checked.

You should try turning on the menu option: View->Show Serial IO, then attempt to start the ALDL data stream. You should get a more detailed output, please post that text here so we can see what is going wrong.

Regards
Paul

[95naSTA]

I tried it with the echo off and it didn't work either..

I came back to post that, saw the last reply, and ran back out to get the more detailed log of what's happening.

Here is the log with the echo back on and Show Serial I/O selected:

46:48.010: Initialising...
46:48.849: Opening COM5 8228,8,N,1
46:49.351: Ready.
47:03.787: Start macro: Clear diagnostic trouble codes: CLRDTC
47:03.795: Heartbeat not specified - no synchronisation performed
47:03.795: Send suspend command: $F4,$56,$08,$AE
47:03.795: Start writing frame
47:03.795: Send: $F4,$56,$08,$AE
47:03.796: Finished writing frame
47:03.796: Wait 10 ms after writing, before reading...
47:03.806: Start reading frame
47:03.806: Aldl frame header byte: $34
47:03.806: Aldl frame length byte: $D9
47:04.006: Com timeout: Data frame truncated: $34,$D9,$20,$5C,$A8,$09,$00,$2A,$20,$00,$6A,$1F,$A 8,$56,$47,$BB,$A9,$5A,$55,$00,$00,$00,$FF,$A9,$90, $59,$24,$02,$0E,$5C,$87,$91,$59,$02,$08,$FF,$34,$D 9,$20,$5C,$A8,$09,$00,$2B,$20,$00,$6A,$1E,$90,$59, $24,$02,$0E,$5C,$87,$91,$59,$02,$08,$FF,$34,$D9,$2 0,$5C,$A8,$09,$00,$2C,$20,$00,$6A,$1D,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00
47:04.062: Error: No echo received from MAX232
47:04.064: Start writing frame
47:04.064: Send: $F4,$57,$0A,$00,$AB
47:04.065: Finished writing frame
47:04.065: Wait 10 ms after writing, before reading...
47:04.075: Start reading frame
47:04.075: Aldl frame header byte: $90
47:04.075: Aldl frame length byte: $59
47:04.075: Recv: $90,$59,$24,$02,$0E,$5C,$87
47:04.075: Finished reading frame
47:04.075: Error: Max232 echo: $90,$59,$24,$02,$0E,$5C,$87 did not match command: $F4,$57,$0A,$00,$AB
47:04.100: Wait 10 ms after writing, before reading...
47:04.110: Start reading frame
47:04.110: Aldl frame header byte: $91
47:04.110: Aldl frame length byte: $59
47:04.110: Recv: $91,$59,$02,$08,$FF,$34,$D9
47:04.110: Finished reading frame
47:04.130: Stop macro: Clear diagnostic trouble codes: CLRDTC


Thanks for the replies.

[Blacky]

Which *.xml vehicle definition file are you using?
Regards
Paul