Page 1 of 5 123 ... LastLast
Results 1 to 10 of 50

Thread: Trouble communicating

  1. #1
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default Trouble communicating

    Hi all, was wondering if someone could help me out. I'm a DIY'er and recently purchased EFI Live V4 Pro. I own a 1990 ZR-1. I have bought the correct ALDL cable and installed all the software and drivers properly. I can't seem to get the 2 talking to each other. I have tried several different vehicle files, my COM and port #'s are the same, Max echo 232 is off and EFI support suggested changing the T6 value to 10ms, which I did with no success. I followed the ALDL troubleshooting guide which says to use the hyper terminal program (which isn't on Windows7 had to copy it from XP) and connect the cable, laptop, and car together, and if you see code displayed in the program, you know the cable is working properly. I did that and saw the code streaming. So I know the cable is fine. Depending on what vechicle file is loaded, I get different errors when in the Macro tab. It's either "expecting frame header byte", "reply frame checksum failure", or "data frame truncated (followed by a long line code)". I believe EFI Live V4 pro should be able display the dashboard, data log, etc.., but I believe some values need to be changed or I need a different vehicle file in order to do so. I have no programming background, and limited computer saavy, lol. And besides my limited knowledge, I don't want to play around changing things, then end up frying my ECU (they're not made anymore, very hard to find, and very, very expensive). Any help is great appreciated, as I'm at my wit's end trying to get this to work.
    Thanks, Joe

  2. #2
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,501

    Default

    The error messages you are seeing usually indicate a faulty cable or connection, but it may still be a config problem, so...

    Turn on the option: View->Show I/O, then select ALDL->Auto Detect Chatter.
    Allow the chatter to display for about 10 seconds, then click Stop.
    Copy/paste the chatter into this thread and I'll see if I can help you get it working.

    Regards
    Paul
    Before asking for help, please read this.

  3. #3
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default

    Hi Paul, thanks for responding. Ok the first vehicle file is Corvette_Camaro_90_91, I turned on Serial I/O and clicked Auto detect and got
    25:00.497: Initialising...
    25:01.117: Opening COM2 8228,8,N,1
    25:01.434: Ready.
    25:56.183: Opening COM2 8228,8,N,1
    26:47.135: Check vehicle interface...
    26:47.142: Interface not checked because "Max232 echo" is not set. (see Com port settings)

    26:47.145: Scanning for heartbeat and chatter frames...
    26:47.145: Waiting for Aldl bus silence of at least 16ms...
    26:49.065: Heartbeat frame:
    26:49.065: 26:48.841: $40,$55,$6B
    26:49.065: Heartbeat frame is followed by 32ms of silence
    26:49.065: Advisable value for T6 is 16ms

    26:49.065: Chatter frame(s):
    26:49.065: 26:48.873: $41,$61,$00,$20,$00,$3E,$3D,$01,$00,$00,$00,$7A,$0 0,$33,$15
    26:49.065: 26:49.017: $10,$59,$0A,$3E,$00,$00,$4F

    Then I clicked start and got
    27:48.033: Start macro: : ECM
    27:48.046: Synchronising ALDL communications...
    27:48.046: Waiting for heartbeat: $F0,$56,$F1,$C9
    27:48.046: Waiting for Aldl bus silence of at least 16ms...
    27:48.091: Start reading frame
    27:48.190: Aldl frame header byte: $10
    27:48.190: Aldl frame length byte: $59
    27:48.207: Recv: $10,$59,$0A,$3E,$00,$00,$4F
    27:48.207: Finished reading frame
    27:48.207: Frame: 0 = $10,$59,$0A,$3E,$00,$00,$4F
    27:48.207: Start reading frame
    27:48.222: Aldl frame header byte: $40
    27:48.222: Aldl frame length byte: $55
    27:48.223: Recv: $40,$55,$6B
    27:48.223: Finished reading frame
    27:48.223: Frame: 1 = $40,$55,$6B
    27:48.223: Start reading frame
    27:48.223: Aldl frame header byte: $41
    27:48.238: Aldl frame length byte: $61
    27:48.239: Recv: $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    27:48.239: Finished reading frame
    27:48.239: Frame: 2 = $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    27:48.239: Start reading frame
    27:48.366: Aldl frame header byte: $F0
    27:48.383: Aldl frame length byte: $56
    27:48.383: Recv: $F0,$56,$F1,$C9
    27:48.383: Finished reading frame
    27:48.383: Frame: 3 = $F0,$56,$F1,$C9
    27:48.383: Found heartbeat: $F0,$56,$F1,$C9 - ALDL synchronised
    27:48.383: Send suspend command: $F1,$56,$08,$B1
    27:48.383: Start writing frame
    27:48.383: Send: $F1,$56,$08,$B1
    27:48.383: Finished writing frame
    27:48.383: Start reading frame
    27:48.398: Aldl frame header byte: $F1
    27:48.398: Aldl frame length byte: $56
    27:48.398: Recv: $F1,$56,$08,$B1
    27:48.398: Finished reading frame
    27:48.399: Start writing frame
    27:48.399: Send: $F4,$57,$01,$00,$B4
    27:48.399: Finished writing frame
    27:48.399: Start reading frame
    27:48.414: Aldl frame header byte: $F4
    27:48.414: Aldl frame length byte: $57
    27:48.414: Recv: $F4,$57,$01,$00,$B4
    27:48.415: Finished reading frame
    27:48.536: Start writing frame
    27:48.536: Send: $F4,$57,$01,$00,$B4
    27:48.536: Finished writing frame
    27:48.536: Start reading frame
    27:48.542: Aldl frame header byte: $F4
    27:48.542: Aldl frame length byte: $57
    27:48.558: Recv: $F4,$57,$01,$00,$B4
    27:48.558: Finished reading frame
    27:48.584: Start writing frame
    27:48.584: Send: $F4,$57,$01,$00,$B4
    27:48.584: Finished writing frame
    27:48.584: Start reading frame
    27:48.590: Aldl frame header byte: $3F
    27:48.590: Aldl frame length byte: $F3
    27:48.793: Com timeout: Data frame truncated: $3F,$F3,$13,$75,$F3,$1E,$21,$66,$66,$F4,$57,$01,$0 0,$B4,$C0,$C0,$83,$00,$96,$FF,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$04,$08,$00,$00,$71,$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,$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,$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
    27:48.823: Aborting request due to previous error
    27:48.833: Start writing frame
    27:48.833: Send: $F4,$57,$01,$00,$B4
    27:48.833: Finished writing frame
    27:48.833: Start reading frame
    27:48.847: Aldl frame header byte: $F4
    27:48.847: Aldl frame length byte: $57
    27:48.847: Recv: $F4,$57,$01,$00,$B4
    27:48.847: Finished reading frame
    27:48.876: Start writing frame
    27:48.876: Send: $F4,$57,$01,$00,$B4
    27:48.876: Finished writing frame
    27:48.876: Start reading frame
    27:48.877: Aldl frame header byte: $10
    27:48.877: Aldl frame length byte: $40
    27:48.877: Recv: $10,$55,$00
    27:48.877: Error: Reply frame checksum failure
    27:48.905: Finished reading frame
    27:48.905: Aborting request due to previous error
    27:48.912: Start writing frame
    27:48.912: Send: $F4,$57,$01,$00,$B4
    27:48.912: Finished writing frame
    27:48.912: Start reading frame
    27:48.913: Aldl frame header byte: $ 0
    27:48.913: Aldl frame length byte: $ 0
    27:48.913: Recv: $00,$55,$00
    27:48.913: Error: Reply frame checksum failure
    27:48.942: Finished reading frame
    27:48.942: Aborting request due to previous error

    I stopped it after a few seconds
    I'll post the next file in post#4
    Last edited by vilant; January 28th, 2013 at 10:46 AM.

  4. #4
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default

    Here's what I got when I had zr1_1991 selected as the vehicle file.
    28:09.806: Opening COM2 8228,8,N,1
    28:27.658: Check vehicle interface...
    28:27.666: Interface not checked because "Max232 echo" is not set. (see Com port settings)

    28:27.666: Scanning for heartbeat and chatter frames...
    28:27.666: Waiting for Aldl bus silence of at least 16ms...
    28:27.683: Start reading frame
    28:27.760: Aldl frame header byte: $F0
    28:27.760: Aldl frame length byte: $56
    28:27.760: Recv: $F0,$56,$F1,$C9
    28:27.760: Finished reading frame
    28:27.760: Start reading frame
    28:27.792: Aldl frame header byte: $10
    28:27.792: Aldl frame length byte: $59
    28:27.792: Recv: $10,$59,$0A,$3E,$00,$00,$4F
    28:27.792: Finished reading frame
    28:27.792: Start reading frame
    28:27.824: Aldl frame header byte: $40
    28:27.824: Aldl frame length byte: $55
    28:27.824: Recv: $40,$55,$6B
    28:27.824: Finished reading frame
    28:27.824: Start reading frame
    28:27.824: Aldl frame header byte: $41
    28:27.824: Aldl frame length byte: $61
    28:27.840: Recv: $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    28:27.840: Finished reading frame
    28:27.840: Start reading frame
    28:27.948: Com timeout: Expecting frame header byte
    28:28.041: Heartbeat frame:
    28:28.041: 28:27.824: $40,$55,$6B
    28:28.041: Heartbeat frame is followed by 16ms of silence
    28:28.041: Advisable value for T6 is 8ms

    28:28.041: Chatter frame(s):
    28:28.041: 28:27.840: $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14

    I clicked start and got

    28:42.510: Start macro: Engine data: DATA
    28:42.506: Synchronising ALDL communications...
    28:42.506: Waiting for heartbeat: $08,$55,$A3
    28:42.506: Waiting for Aldl bus silence of at least 16ms...
    28:42.542: Start reading frame
    28:42.542: Aldl frame header byte: $40
    28:42.542: Aldl frame length byte: $55
    28:42.542: Recv: $40,$55,$6B
    28:42.542: Finished reading frame
    28:42.542: Frame: 0 = $40,$55,$6B
    28:42.542: Start reading frame
    28:42.558: Aldl frame header byte: $41
    28:42.558: Aldl frame length byte: $61
    28:42.574: Recv: $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    28:42.574: Finished reading frame
    28:42.574: Frame: 1 = $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    28:42.574: Start reading frame
    28:42.683: Com timeout: Expecting frame header byte
    28:42.743: No heartbeat found - ALDL not synchronised yet
    28:42.748: Synchronising ALDL communications...
    28:42.748: Waiting for heartbeat: $08,$55,$A3
    28:42.748: Waiting for Aldl bus silence of at least 16ms...
    28:42.792: Start reading frame
    28:42.894: Aldl frame header byte: $F0
    28:42.894: Aldl frame length byte: $56
    28:42.894: Recv: $F0,$56,$F1,$C9
    28:42.894: Finished reading frame
    28:42.894: Frame: 0 = $F0,$56,$F1,$C9
    28:42.894: Start reading frame
    28:42.926: Aldl frame header byte: $10
    28:42.926: Aldl frame length byte: $59
    28:42.926: Recv: $10,$59,$0A,$3E,$00,$00,$4F
    28:42.926: Finished reading frame
    28:42.927: Frame: 1 = $10,$59,$0A,$3E,$00,$00,$4F
    28:42.927: Start reading frame
    28:42.958: Aldl frame header byte: $40
    28:42.958: Aldl frame length byte: $55
    28:42.958: Recv: $40,$55,$6B
    28:42.958: Finished reading frame
    28:42.958: Frame: 2 = $40,$55,$6B
    28:42.958: Start reading frame
    28:42.959: Aldl frame header byte: $41
    28:42.959: Aldl frame length byte: $61
    28:42.975: Recv: $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    28:42.975: Finished reading frame
    28:42.975: Frame: 3 = $41,$61,$00,$20,$00,$3E,$3E,$01,$00,$00,$00,$7A,$0 0,$33,$14
    28:42.975: Start reading frame
    28:43.073: Com timeout: Expecting frame header byte
    28:43.177: No heartbeat found - ALDL not synchronised yet
    28:43.184: Synchronising ALDL communications...
    28:43.184: Waiting for heartbeat: $08,$55,$A3
    28:43.184: Waiting for Aldl bus silence of at least 16ms...
    28:43.213: Start reading frame
    28:43.322: Com timeout: Expecting frame header byte
    28:43.340: No heartbeat found - ALDL not synchronised yet
    28:43.349: Stop macro: Engine data: DATA

    Hopefully you can make sense of this, because I sure can't, lol.

  5. #5
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,501

    Default

    Quote Originally Posted by vilant View Post
    Hi Paul, thanks for responding. Ok the first vehicle file is Corvette_Camaro_90_91, I turned on Serial I/O and clicked Auto detect and got
    25:00.497: Initialising...
    25:01.117: Opening COM2 8228,8,N,1
    25:01.434: Ready.
    25:56.183: Opening COM2 8228,8,N,1
    26:47.135: Check vehicle interface...
    26:47.142: Interface not checked because "Max232 echo" is not set. (see Com port settings)
    Can you try this one again with the Max232 Echo set. Set the checkbox in the Edit->Properties->Comms tab page.
    I think your cable is echoing back commands.

    27:48.383: Start writing frame
    27:48.383: Send: $F1,$56,$08,$B1
    27:48.383: Finished writing frame
    27:48.383: Start reading frame
    27:48.398: Aldl frame header byte: $F1
    27:48.398: Aldl frame length byte: $56
    27:48.398: Recv: $F1,$56,$08,$B1
    27:48.398: Finished reading frame
    27:48.399: Start writing frame
    27:48.399: Send: $F4,$57,$01,$00,$B4
    27:48.399: Finished writing frame
    27:48.399: Start reading frame
    27:48.414: Aldl frame header byte: $F4
    27:48.414: Aldl frame length byte: $57
    27:48.414: Recv: $F4,$57,$01,$00,$B4
    27:48.415: Finished reading frame

    It looks like the cable is reflecting back (echoing) what you're transmitting. I.e. You're getting back exactly what you transmitted but the software is not discarding the echo from the cable.
    To tell the software to discard the echo and wait for the actual reply from the vehicle you need to the Max232 echo check box ticked.

    Regards
    Paul
    Before asking for help, please read this.

  6. #6
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default

    Hi Paul, I tried again w/ Max echo 232 on (the reason it was off was because in the directions I was given from the seller, it says to make sure it is off/unticked). Here's what I got when vehicle file Corvette_Camaro_90_91 was selected and I clicked auto detect
    56:04.870: Check vehicle interface...
    56:04.878: Waiting for Aldl bus silence of at least 16ms...
    56:04.975: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
    56:04.990: Max232 interface detected OK

    56:05.349: Scanning for heartbeat and chatter frames...
    56:05.349: Waiting for Aldl bus silence of at least 16ms...
    56:07.391: Heartbeat frame:
    56:07.391: 56:06.158: $40,$55,$6B
    56:07.391: Heartbeat frame is followed by 32ms of silence
    56:07.391: Advisable value for T6 is 16ms

    56:07.391: Chatter frame(s):
    56:07.391: 56:06.190: $41,$61,$00,$20,$00,$40,$41,$01,$00,$00,$00,$7A,$0 0,$38,$0A
    56:07.391: 56:06.334: $10,$59,$0A,$40,$00,$00,$4D

    and I got this when I clicked start
    56:11.740: Start macro: : ECM
    56:11.747: Synchronising ALDL communications...
    56:11.747: Waiting for heartbeat: $F0,$56,$F1,$C9
    56:11.747: Waiting for Aldl bus silence of at least 16ms...
    56:12.373: Com timeout: Expecting frame header byte
    56:12.385: Send: $F4,$57,$01,$00,$B4
    56:12.483: Recv: $F4,$95,$01,$20,$F9,$00,$00,$00,$00,$00,$12,$20,$2 0,$57,$00,$28,$00,$00,$10,$00,$00,$00,$00,$FF,$41, $F3,$13,$73,$F2,$1E,$25,$66,$66,$80,$80,$00,$00,$0 0,$80,$80,$83,$00,$96,$FF,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 3,$BE,$00,$00,$E9
    56:12.498: Synchronising ALDL communications...
    56:12.498: Waiting for heartbeat: $F0,$56,$F1,$C9
    56:12.499: Waiting for Aldl bus silence of at least 16ms...
    56:12.732: Com timeout: Expecting frame header byte
    56:12.746: Synchronising ALDL communications...
    56:12.746: Waiting for heartbeat: $F0,$56,$F1,$C9
    56:12.746: Waiting for Aldl bus silence of at least 16ms...
    56:12.966: Com timeout: Expecting frame header byte
    56:12.981: Synchronising ALDL communications...
    56:12.981: Waiting for heartbeat: $F0,$56,$F1,$C9
    56:12.981: Waiting for Aldl bus silence of at least 16ms...
    56:13.200: Com timeout: Expecting frame header byte
    56:13.313: Stop macro: : ECM

    I got almost the same thing w/ zr1_1991 vehicle file selected. I can post it you want, but it was the same result. What do you think is going on? Does it matter that even though my car is GM, the engine was designed by Lotus?

  7. #7
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,501

    Default

    Quote Originally Posted by vilant
    56:12.385: Send: $F4,$57,$01,$00,$B4
    56:12.483: Recv: $F4,$95,$01,$20,$F9,$00,$00,$00,$00,$00,$12,$20,$2 0,$57,$00,$28,$00,$00,$10,$00,$00,$00,$00,$FF,$41, $F3,$13,$73,$F2,$1E,$25,$66,$66,$80,$80,$00,$00,$0 0,$80,$80,$83,$00,$96,$FF,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 3,$BE,$00,$00,$E9
    This tells me the comms are now ok with the Max232 echo set on.

    $F4 is the module ID that the request was sent to.
    $57 is the number of bytes in the message less $55, $57-$55=$02 = 02 decimal.
    $01,$00 are the two data bytes
    $B4 is the checksum

    $F4 is the module that replied
    $95 is the number of bytes in the message less $55, $95-$55=$40 = 64 decimal.
    $01,$29,$F9.......$BE,$00,$00 are the 64 data bytes
    $E9 is the checksum

    So at least we now know that data is being set/received correctly.

    You need to set up the heartbeat frame correctly.
    Quote Originally Posted by vilant
    26:47.145: Scanning for heartbeat and chatter frames...
    26:47.145: Waiting for Aldl bus silence of at least 16ms...
    26:49.065: Heartbeat frame:
    26:49.065: 26:48.841: $40,$55,$6B
    26:49.065: Heartbeat frame is followed by 32ms of silence
    26:49.065: Advisable value for T6 is 16ms
    So you should set the heartbeat to $40,$55,$6B like this:
    Click image for larger version. 

Name:	aldl1.PNG 
Views:	348 
Size:	45.8 KB 
ID:	14448
    If you continue to get interference by other modules on the network, you may need to change the $F1's (in the Suspend and Resume commands) to $F4's, if you do click the [...] buttons to the left and change it that way, then click [Refresh] to update the checksum byte correctly. That has the effect of sending the suspend/resume commands to module $F4 (the engine controller) instead of module $F1 (most likely the body controller)

    And I would try setting set the timing to this:
    Click image for larger version. 

Name:	aldl2.PNG 
Views:	348 
Size:	47.7 KB 
ID:	14449
    Setting T6 to 200 (or even 1000, 2000 etc) will prevent the
    56:11.747: Waiting for Aldl bus silence of at least 16ms...
    56:12.373: Com timeout: Expecting frame header byte
    Basically you want the T6 value to be larger than the longest time between chatter frames.

    Regards
    Paul
    Before asking for help, please read this.

  8. #8
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default

    Hi Paul, Ok I changed the heartbeat to $40,$55,$6B and T3 and T6 to 200ms on Corvette_Camaro_90_91 hit auto detect and got

    05:49.191: Initialising...
    05:49.813: Opening COM2 8228,8,N,1
    05:50.135: Ready.
    06:16.725: Updating vehicle information...
    06:16.839: Opening COM2 8228,8,N,1
    06:37.419: Check vehicle interface...
    06:37.427: Waiting for Aldl bus silence of at least 200ms...
    06:45.460: Can't find silence greater than 200ms
    06:45.462: Hint: try halving T6 from 200ms to 100ms
    06:45.462: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
    06:45.476: Max232 interface detected OK

    06:45.479: Scanning for heartbeat and chatter frames...
    06:45.479: Waiting for Aldl bus silence of at least 200ms...
    06:53.543: Can't find silence greater than 200ms
    06:53.544: Hint: try halving T6 from 200ms to 100ms
    06:53.544: Error: Reply frame checksum failure
    06:53.544: No chatter found

    So I changed T6 to 100ms hit auto detect and got

    07:06.346: Updating vehicle information...
    07:06.461: Opening COM2 8228,8,N,1
    07:45.346: Updating vehicle information...
    07:45.445: Opening COM2 8228,8,N,1
    07:49.147: Check vehicle interface...
    07:49.153: Waiting for Aldl bus silence of at least 100ms...
    07:49.391: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
    07:49.397: Max232 interface detected OK

    07:49.399: Scanning for heartbeat and chatter frames...
    07:49.399: Waiting for Aldl bus silence of at least 100ms...
    07:51.510: Heartbeat frame:
    07:51.510: 07:50.070: $40,$55,$6B
    07:51.510: Heartbeat frame is followed by 32ms of silence
    07:51.510: Advisable value for T6 is 16ms

    07:51.510: Chatter frame(s):
    07:51.510: 07:50.102: $41,$61,$00,$20,$00,$44,$46,$01,$00,$00,$00,$7A,$0 0,$3F,$FA
    07:51.510: 07:50.246: $10,$59,$0A,$44,$00,$00,$49

    Clicked start and got this repeating, so I stopped it

    07:55.095: Start macro: : ECM
    07:55.095: Synchronising ALDL communications...
    07:55.095: Waiting for heartbeat: $40,$55,$6B
    07:55.095: Waiting for Aldl bus silence of at least 100ms...
    07:55.535: Com timeout: Data frame truncated: $80,$7C,$AB,$84,$B1,$05,$01,$02,$02,$A4,$01,$FF,$C A,$10,$59,$0A,$44,$00,$00,$49,$40,$55,$6B,$41,$61, $00,$20,$00,$44,$47,$01,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00
    07:55.551: Error: No echo received from MAX232
    07:55.560: Send: $F4,$57,$01,$00,$B4
    07:55.653: Recv: $F4,$95,$01,$20,$F9,$00,$00,$00,$00,$00,$12,$20,$2 0,$57,$00,$28,$00,$00,$10,$00,$00,$00,$00,$FF,$44, $EF,$13,$71,$F1,$1E,$2B,$66,$66,$80,$80,$00,$00,$0 0,$80,$80,$83,$00,$96,$FF,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 3,$5C,$00,$00,$49
    07:55.670: Synchronising ALDL communications...
    07:55.670: Waiting for heartbeat: $40,$55,$6B
    07:55.670: Waiting for Aldl bus silence of at least 100ms...
    07:55.933: Error: Reply frame checksum failure
    07:55.948: Error: No echo received from MAX232
    07:55.952: Send: $F4,$57,$01,$00,$B4
    07:56.045: Recv: $F4,$95,$01,$20,$F9,$00,$00,$00,$00,$00,$12,$20,$2 0,$57,$00,$28,$00,$00,$10,$00,$00,$00,$00,$FF,$44, $EF,$13,$71,$F1,$1E,$2B,$66,$66,$80,$80,$00,$00,$0 0,$80,$80,$83,$00,$96,$FF,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 3,$5C,$00,$00,$49
    07:56.055: Synchronising ALDL communications...
    07:56.055: Waiting for heartbeat: $40,$55,$6B
    07:56.055: Waiting for Aldl bus silence of at least 100ms...
    07:56.549: Com timeout: Data frame truncated: $01,$F1,$56,$08,$B1,$00,$3F,$F9,$10,$59,$0A,$44,$0 0,$00,$49,$40,$55,$6B,$41,$61,$00,$20,$00,$44,$47, $01,$00,$00,$00,$7A,$00,$3F,$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,$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,$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
    07:56.565: Error: No echo received from MAX232

    I got the same with zr1_1991 as the vehicle file. You don't think it's my laptop somehow, do you? BTW, I really appreciate you taking time to help me out.

  9. #9
    Junior Member
    Join Date
    Jan 2013
    Posts
    31

    Default

    Hey Paul, sorry to bother you. I tried working with "support" and Andrew directed me back to you, lol. Had to change T6 to 100ms (per the software reecommendation, because 200ms wasn't working). When I went through the "help" section of V4, it says my car is supported (1990 Car J 5.7 LT5 SFI $F4,$57,$01,$00). But I'm still having no luck.
    Here's a screen shot, better than posting lines of code. I don't understand why it can't see the Max echo when I start, but can when I auto-detect.
    Attachment 14528
    Does something else need to be configured differently?

  10. #10
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,501

    Default

    For some reason, I can't see that screen shot. Can you try re-posting it. Although if it is a screen shot of the text it is much better if you copy/paste the actual text. That way I can search it much more easily using text editing tools.
    Regards
    Paul
    Before asking for help, please read this.

Page 1 of 5 123 ... LastLast

Similar Threads

  1. Corisca and communicating with ALDL
    By tunethis in forum EFILive V4
    Replies: 4
    Last Post: December 20th, 2012, 11:31 AM
  2. Trouble Communicating with E38 ECM
    By philip.long in forum E37, E38 & E67 PFI ECM's
    Replies: 5
    Last Post: January 25th, 2009, 09:33 AM
  3. FS not communicating in dead poll
    By Big Block in forum Black Box Logging
    Replies: 4
    Last Post: January 7th, 2008, 12:24 PM
  4. Having trouble communicating with 07tbss
    By Stoichiometric in forum E37, E38 & E67 PFI ECM's
    Replies: 3
    Last Post: October 12th, 2007, 07:57 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •