New to Tuning

[Gordon]

I am new to tuning. Engine Power Systems did the initial tuning of the PCM. I am going to install 32 lb/hr injectors. I have the tuning software to do so, but I need to have data logging ability to set the fuel trim. I have everything plugged up and running properly, but I can not get any data to come thru onto the laptop so I can see what my fuel trim is. I probably have something set wrong and it's just something stupid and simple. But if anyone has any information that might assist it would be greatly appreciated. Thank's.

[joecar]

Hi Gordon, welcome to the forum...:cheers:

Do you have FlashScan V1 or V2...?

Which year/model/vehicle...?

In the scantool, did you:
- click the green connect button (upper left)...?
- do Info->Validate PIDs...?
- goto PIDs tab and select pids...?
- click the red record button (bottom center)...?

Post a screenshots of the PIDs tab.

[Gordon]

I am using EFILive V4 Pro. I am using it on a 94 Camaro Z28.

[joecar]

Ah, V4, I'll move the thread to the V4 section.

I pm'd Tech Support on your problem.

[Tordne]

Do you get any errors reported that might be helpful for diagnosis?

We have previously seen vehicles with aftermarket chips (that don't behave like a factory PCM) where EFILive V4 does not work with them.

[Gordon]

No, I do not get any error messages. I am using the stock chip that was in the PCM. I do not believe there is any error. I believe it is something that I do not have set correctly in the program to read the PCM. I get the green light on the left side of the DTC window, but it is always red on the right side of the window. I have the correct comm port selected and I also have the correct baud selected. But I still can not get any data to come up. Hopefully this information helps.

[Blacky]

Try logging data with the "Max232 Echo" property setting checked and try again with it unchecked. Depending on the hardware/cable that you are using it will either require or not require that setting.

You could also try turning on the menu option View->Show Serial IO. That will provide a more detailed display of what the software is trying to do when communicating with the PCM. That info may offer some clues as to what is happening.

Regards
Paul

[Gordon]

This is what I get when I try it with and without 232baud.

42:27.411: Opening COM3 8228,8,N,1
42:37.503: Check vehicle interface...
42:37.508: Waiting for Aldl bus silence of at least 10ms...
42:37.518: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
42:37.518: Start writing frame
42:37.518: Send: $FF,$55,$AC
42:37.518: Finished writing frame
42:37.518: Start reading frame
42:37.526: Aldl frame header byte: $FF
42:37.526: Aldl frame length byte: $ 0
42:37.526: Recv: $FF,$55,$AC
42:37.526: Finished reading frame
42:37.526: Max232 interface detected OK

42:37.528: Scanning for heartbeat and chatter frames...
42:37.528: Waiting for Aldl bus silence of at least 10ms...
42:37.533: Start reading frame
42:37.643: Com timeout: Expecting frame header byte
42:37.704: No chatter found

And the chatter button on the right is red. It is always red.

[Blacky]

Hi Gordon,

The 94 Camaro should be sending out chatter frames. The chatter indicator will turn from red to green when those frames are detected.

Is it possible that your laptop has a built in modem and that the built in modem is using the COM port that you have set up in EFILive?
A modem can appear to the EFILive software as if it is a max232 ALDL interface. Check in the Windows hardware manager (right click My Computer" and select Properties). to see what COM ports you have available. Maybe you need to choose a different one.

If you are using a USB-Serial converter then it most likely won't work. You'll need a real ALDL-USB cable (www.moates.net (http://www.moates.net) sells them) or you need to use a real RS232 serial port.

Regards
Paul

[Gordon]

I am using a aldl cable with a converter that I purchased from Moates. It plugs in up under the dash, on to a small converter box, then to a usb that plugs into the laptop. I am also using a newer laptop with Windows7. I did run into problems using Windows7 with C.A.T.S. Tuner software. I eventually got it to work properly by installing 3 missing activex controls. Don't know if that little bit of information might help or not. I just did some checking and the laptop modem is operating on com3. The EFILIVE Software is running on the same com. I have tried using other coms but it get less when I don't use com3. How can I fix/change?

[ScarabEpic22]

Set them modem to another COM port and point EFILive V4 to that port now. You're getting less info now because EFILive cant find the actual interface now instead of having the modem feed it bad data.

On my W7 laptop, I double clicked my modem in Device Manager to see how to change COM ports (havent done this for a while now, last time was probably 4+ years ago). So double click the ALDL cable, go to the advanced tab, and click Advanced Port Settings. Should be able to change the COM port there, then mirror whatever port you chose in EFILive V4. It might be slightly different to setup your ports, in fact its probably a little different.

[Gordon]

I went into the properties tab and changed the modem from 3 to 5. (port4 is in use) that's what it's telling me anyway. So your suggestion is to now leave EFILive V4 on COM3?

[Gordon]

58:12.253: Check vehicle interface...
58:12.259: Waiting for Aldl bus silence of at least 10ms...
58:12.265: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
58:12.277: Error: Reply frame checksum failure
58:12.281: No response from Max232
58:12.281: Retrying Max232 detection...

58:12.281: Waiting for Aldl bus silence of at least 10ms...
58:12.296: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
58:12.305: Error: Reply frame checksum failure
58:12.313: No response from Max232
58:12.313: Retrying Max232 detection...

58:12.313: Waiting for Aldl bus silence of at least 10ms...
58:12.327: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
58:12.337: Error: Reply frame checksum failure
58:12.345: No response from Max232
58:12.345: Retrying Max232 detection...

58:12.345: Interface cannot be detected

58:12.354: Scanning for heartbeat and chatter frames...
58:12.354: Waiting for Aldl bus silence of at least 10ms...
58:12.467: Com timeout: Expecting frame header byte
58:12.472: No chatter found

This is what I'm getting now after changing the laptop to com5. I have changed everything back to it's original setting's and now I'm getting error messages that I have not gotten before.

[Blacky]

You need to go into the Windows device manager and find the virtual COM port (under Ports COM & LPT) that the Moates cable is using. There should be an option to select which COM port you want it to use. Select an unused COM port, i.e. not COM2 that the modem is using.
There should also be an option to force it to use the exact COM port you selected all the time. You should select that option as well, other wise you'll need to keep looking up what COM port the Moates cable uses each time you boot your PC (as it may change).

Regards
Paul

[Blacky]

58:12.253: Check vehicle interface...
58:12.259: Waiting for Aldl bus silence of at least 10ms...
58:12.265: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
58:12.277: Error: Reply frame checksum failure
58:12.281: No response from Max232
58:12.281: Retrying Max232 detection...

Un-check the Max232 echo option. I'm pretty sure the Moates cable does not echo the commands.

P.S. Sorry about my previous reply being a tad late, I did not see any of the other replies until now.

Regards
Paul

[Gordon]

I am trying to locate ports (COM & LPT) in the device manager. I have located it on my desktop but I will have to do more searching with the laptop. Thanks for the help. Will let you know how it goes once I figure it out.

[ScarabEpic22]

I went into the properties tab and changed the modem from 3 to 5. (port4 is in use) that's what it's telling me anyway. So your suggestion is to now leave EFILive V4 on COM3?

Sorry you should set it to say COM 5 in Device Manager and also in EFILive V4. If they dont match, you'll get funky errors.

[Blacky]

I am trying to locate ports (COM & LPT) in the device manager. I have located it on my desktop but I will have to do more searching with the laptop. Thanks for the help. Will let you know how it goes once I figure it out.


Right click on the "Computer" Icon, either on the desktop or in the Start menu, then select Properties. (Or press Windows+Pause/Break shortcut key)
Then see attached images for further instructions.

Regards
Paul

[Gordon]

When I go into my device manager, I do not have a drop down selection for the Ports (COM&LPT). Not sure why I don't have it available. I've been going thru and trying to locate it elsewhere. But still to no avail.

[Blacky]

When I go into my device manager, I do not have a drop down selection for the Ports (COM&LPT). Not sure why I don't have it available. I've been going thru and trying to locate it elsewhere. But still to no avail.

Have you installed the USB drivers for the Moates ALDL cable?

Look under "Universal Serial Bus controllers" (the last item in the list) and look for something like "Virtual COM port" or "FTDI USB device". When you plug/unplug your Moates cable, the entry should appear/disappear.

So, with the cable plugged in to your PC you should see the entry for it under "Universal Serial Bus controllers". Right click it and select properties. There should be an option (a checkbox) to activate the Virtual COM port for that USB device. Activate the Virtual COM Port and it should then appear in the "Ports (COM & LPT)" section.

Regards
Paul

[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

[Gordon]

cant load vehicle from file:C:\Program files (x86)EFILive \V4\ vehicle data streams \A274.xml. mismatch in datapacket

[Blacky]

Some anti virus packages mess with the *.xml files incorrectly thinking they contain a virus.
Open the xml file using notepad and look for the test DEFANGED_ (it will be near the start of the file), remove the text and save the file and try again.

Or try downloading the attached file. Unfortunately the same thing may happen to this attached file if any virus checkers between here and your machine think it is dangerous. I've called the file A274.txt so you'll need to rename it to A274.xml after you have downloaded it.

Regards
Paul

[Gordon]

I searched thru the A274 file, I could not locate "test DEFANGED_" anywhere in that file. I downloaded and renamed the file you also sent and I still get the message of being "mismatch datapacket" . I even tried to use both of the LT1 files and neither would display the dtc data, dashboard data, etc... I am however getting closer to getting what I need as we slowly work thru. I appreciate your time and effort.

:cheers:

[Blacky]

I searched thru the A274 file, I could not locate "test DEFANGED_" anywhere in that file. I downloaded and renamed the file you also sent and I still get the message of being "mismatch datapacket" . I even tried to use both of the LT1 files and neither would display the dtc data, dashboard data, etc... I am however getting closer to getting what I need as we slowly work thru. I appreciate your time and effort.

:cheers:

I meant to say look for the text DEFANGED_ (not "test DEFANGED_").

I'd be tempted to uninstall V4, re-download it from the web site and re-install it. Just in case the xml libraries that EFILive V4 uses to load the *.xml files were not installed correctly.

Regards
Paul

[Gordon]

I am going to uninstall EFILive and then i'm going to try re-installing it from scratch

[Gordon]

I have uninstalled and re-installed. I still get the same message about being mismatch datapacket.

[Gordon]

I have uninstalled and reinstalled both EFILive and the Moates ALDL driver. I was unable to locate "DEFANGED" in the A274 file. I disabled the firewall and still to no avail. I am stuck. If you or anyone else has any other idea's I am all ears/eyes.

[Blacky]

I have uninstalled and reinstalled both EFILive and the Moates ALDL driver. I was unable to locate "DEFANGED" in the A274 file. I disabled the firewall and still to no avail. I am stuck. If you or anyone else has any other idea's I am all ears/eyes.

Please email me the a274.xml file (rename it to a274.txt and zip it first).
Email: paul@efilive.com

Regards
Paul

[Gordon]

I have sent the file to you via e-mail.

[Blacky]

I've got the file, thanks. I can see the problem and I am working out a way to fix it.
Regards
Paul

[Blacky]

My mistake,
After pulling my hair out trying to figure out why the A274.xml file format was incorrect I finally realized that I should have said use the file gm274.xml instead of A274.xml.
The A274.xml file was an experimental xml format that should not have been included in the V4 installation.
So try using gm274.xml with your Camaro.

Regards
Paul

[Gordon]

My apologies in my delay for a response. I figured out the issue I had with the registering the software after I uninstalled and then reinstalled the software. But I am still having the same issue when using gm274.xml. I get no data displaying on the virtual dashboard or dtc's. The laptop reads that it is connected to the car, but I still get no data readout.

[Blacky]

Have you selected (clicked on) the "Engine data and DTCs (DATADTC)" macro item prior to starting the data?

Regards
Paul

[Gordon]

I have selected Engine and Trans Data. Should I only use the Engine Data?

[Blacky]

Load the gm274.xml file, then click on the "Engine data and DTCs (DATADTC)" macro item, then click on the green "start aldl data" button. See image.
8239

Regards
Paul

[Gordon]

I will give that a try, but if I am remembering correctly, I did that and I still get no data readout. But will try again and let you know.

[Blacky]

If you still have no luck, check the menu: "View->Serial I/O" so that it shows a tick mark next to the "Serial I/O" entry. Then click on the green "Start ALDL" button. Let it run for about 5 seconds, then stop it and copy/paste ALL the text (right click and select "Copy All") into a reply. I'll see if I can see what is going wrong.

Regards
Paul

[Blacky]

Hi Gordon,

First off, it looks like the interface you are using is echoing the commands sent by EFILive to the vehicle. For example, look at this data:

45:57.045: Start macro: Engine data and DTCs: DATADTC
45:57.060: Send: $F4,$57,$01,$00,$B4
45:57.269: Com timeout: Data frame truncated: $21,$FD,$F4,$57,$01,$00,$B4,$F4,$92,$01,$00,$00,.. .

The PC sent the bytes: $F4,$57,$01,$00,$B4
Then the PC read the following data from the vehicle:
$21,$FD,$F4,$57,$01,$00,$B4,$F4,$92,$01,$00,$00,.. .

The $21,$FD is just left over data from a previous message that the vehicle sent.
But the important data is the next set of bytes: F4,$57,$01,$00,$B4,$F4,$92,$01,$00,$00,...

The F4,$57,$01,$00,$B4 is an echo of the command that was sent.

Next, the actual data that we are interested in was sent:
$F4,$92,$01,$00,$00,...

So the problem appears to be two-fold:
1. The echo check box should be set.
2. We need to prevent the vehicle sending data other than what we want to log.

Problem 1 is easily solved, the EFILive software MUST be told discard that echo data so you should have the Max232 Echo check box ticked.

Problem 2 should be solved by setting up the [Chatter] and [Timing] tab pages as per the attached images.
By telling EFILive what the heartbeat frame is, EFILive will scan for a frame that matches the heartbeat frame.
When it finds that frame, it will wait for T6 milliseconds, then send the Suspend command. That command stops the PCM from sending any data other than what EFILive requests.

By stopping all the other data, some modules in the vehicle may "complain" that they can't communicate with the PCM anymore. The complaint often
takes the form of an instrument malfunction light illuminating of alarm chime sounding. That is normal while data logging with chatter suspended.
Once you stop scanning EFILive will send the Resume command which allows the extra data to resume.

You may find that the heartbeat frame sent by the vehicle could change which would prevent EFILive from detecting the frame. If that is the case, remove the trailing bytes in the heartbeat frame that do not match the actual heartbeat data sent by the vehicle. For example the heartbeat should be set to $F0,$56,$F4,$C6 (as per the attached image). If the vehicle sometimes sends the heartbeat as $F0,$56,$F4,$C6 and other times send the heartbeat frame as $F0,$56,$F1,$C9, then you should reduce the defined heartbeat frame in the [Chatter] tab page to just $F0,$56 since those bytes remain constant and will match regardless of which heartbeat frame is sent.

Regards
Paul


Here is the information that you requested for me to copy and send to you. I'm sorry I am sending it via email, the forum said I had too many characters. So I just thought I would send it this way so you can see what I see. And I do have the T6 value set at 32. If I set the Max232 echo, it does not work properly and will not display any data, so I leave it not set.


45:51.049: Check vehicle interface...
45:51.055: Interface not checked because "Max232 echo" is not set. (see Com port settings)

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

45:52.658: Chatter frame(s):
45:52.658: 45:51.219: $90,$5A,$21,$00,$60,$5C,$FF,$3A
45:52.658: 45:51.266: $0A,$58,$FF,$03,$48,$54
45:52.658: 45:51.315: $90,$5A,$21,$00,$60,$5C,$FF,$3A

45:57.045: Start macro: Engine data and DTCs: DATADTC
45:57.060: Send: $F4,$57,$01,$00,$B4
45:57.269: Com timeout: Data frame truncated: $21,$FD,$F4,$57,$01,$00,$B4,$F4,$92,$01,$00,$00,.. .
45:57.277: Send: $F4,$57,$01,$00,$B4
45:57.293: Recv: $F4,$57,$01,$00,$B4
45:57.298: Send: $F4,$57,$01,$00,$B4
45:57.309: Error: Reply frame checksum failure
45:57.350: Send: $F4,$57,$01,$00,$B4
45:57.360: Error: Reply frame checksum failure
45:57.450: Send: $F4,$57,$01,$00,$B4
45:57.460: Recv: $0A,$58,$01,$03,$5A,$40
45:57.550: Send: $F4,$57,$01,$00,$B4
45:57.768: Com timeout: Data frame truncated: $B9,$F4,$57,$01,$00,$B4,$F4,$92,$01,$00,$00,...
45:57.772: Send: $F4,$57,$01,$00,$B4
45:57.790: Recv: $F4,$57,$01,$00,$B4

[Gordon]

43:43.216: Opening COM4 8228,8,N,1
43:46.761: Check vehicle interface...
43:46.768: Interface not checked because "Max232 echo" is not set. (see Com port settings)

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

43:48.400: Chatter frame(s):
43:48.400: 43:46.960: $90,$5A,$1B,$00,$63,$5C,$FF,$3D
43:48.400: 43:47.008: $0A,$58,$FF,$02,$86,$17
43:48.400: 43:47.056: $90,$5A,$1C,$00,$63,$5C,$FF,$3C

This is the reading I get when I have Max232 Echo not checked. When I have the Max232 Echo checked I get the following message.

42:40.225: Updating vehicle information...
42:40.333: Opening COM4 8228,8,N,1
42:48.206: Check vehicle interface...
42:48.214: Waiting for Aldl bus silence of at least 32ms...
42:48.288: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
42:48.300: Max232 echo was incorrect:" $90,$5A,$1B,$00,$63,$5C,$FF,$3D
42:48.311: No response from Max232
42:48.311: Retrying Max232 detection...

42:48.311: Waiting for Aldl bus silence of at least 32ms...
42:48.382: Requesting Max232 interface to acknowlege: $FF,$5A,$1B,$00,$63,$5C,$FF,$CE...
42:48.396: Error: Reply frame checksum failure
42:48.417: No response from Max232


42:48.417: Retrying Max232 detection...

42:48.417: Waiting for Aldl bus silence of at least 32ms...
42:48.647: Requesting Max232 interface to acknowlege: $FF,$5A,$90,$5A,$19,$00,$63,$41...
42:48.658: Max232 echo was incorrect:" $0A,$58,$FF,$02,$88,$15
42:48.680: No response from Max232
42:48.680: Retrying Max232 detection...

42:48.680: Interface cannot be detected

[Blacky]

Try logging data with the echo checkbox checked off, but with the heartbeat, suspend and resume frames defined.

Regards
Paul

[Gordon]

I did not have much time to work with it. But I believe you are getting my very close if not right where I need to be. Shortly after I sent you the last message I tried it again but changed the echo box settings. I started getting ton's of data and the dashboard started showing me data as well. I do not have the time right now to continue working on it. But I do believe that the issue is resolved. I will let you know more in the next couple of day's. Your help and time are greatly appreciated. Thank's for everything.

Regards
Gordon

[OZ38]

What happened with this, did it get resolved ?

Cheers

Deek