Disconnecting problem?
Moderator: Matt
Disconnecting problem?
This is a recent one, although I cannot be sure exactly what version this appeared to happen with, however I am getting repeated drop-outs randomly on the nistune consult connection.
As yet I am not entirely sure of the cause, but its happened a couple of times now on cars I never had a problem with initially. Even connecting to the zetronics wideband seems a bit of an issue. Now first i thought earth loop, but then I tried moving things around and no improvement. So then I suspected my usb-serial converter, but it seems fine.
What made me suspect the software slightly was the fact I could connect to the WB with the zetronics software, fine, no problems but with nistune it wouldn't connect at all..
I need to look into it further, but I think this has only been with the test releases, and like I have said I still need to find out a bit more from when it happens.
As yet I am not entirely sure of the cause, but its happened a couple of times now on cars I never had a problem with initially. Even connecting to the zetronics wideband seems a bit of an issue. Now first i thought earth loop, but then I tried moving things around and no improvement. So then I suspected my usb-serial converter, but it seems fine.
What made me suspect the software slightly was the fact I could connect to the WB with the zetronics software, fine, no problems but with nistune it wouldn't connect at all..
I need to look into it further, but I think this has only been with the test releases, and like I have said I still need to find out a bit more from when it happens.
Right I have a log file:
here
Strange thing is it worked PERFECTLY for over an hour and a half. I then saved the map to the nistune board and immediately started having disconnection problems.
I'd like to know your thoughts Matt, its virtually impossible to use when it does this.
Ed
here
Strange thing is it worked PERFECTLY for over an hour and a half. I then saved the map to the nistune board and immediately started having disconnection problems.
I'd like to know your thoughts Matt, its virtually impossible to use when it does this.
Ed
Last edited by Fusion Ed on Thu Nov 15, 2007 4:10 am, edited 1 time in total.
Not much changed with the consult code between test versions and 0.91121 version
I'll have a look at the log anyway to see any problems you were getting.
I've still got an open issue when consult connection fails (say due to loading wrong address file) that it becomes difficult to get it working again without restarting when using the correct address file. Fortunately issues list is getting smaller again so will be able to get to that one soon
I'll have a look at the log anyway to see any problems you were getting.
I've still got an open issue when consult connection fails (say due to loading wrong address file) that it becomes difficult to get it working again without restarting when using the correct address file. Fortunately issues list is getting smaller again so will be able to get to that one soon
Hi Ed
ECU communications problem
Apart from the first character 0x35 is inverse of 0xCA, the following characters in protocol must match
There were quite a few 'non fatal' communications errors flagged in the log. However since the data is register read data we are tolerant of it
When there is a TX line problem to the ECU it will barf. This happened a few times which caused disconnects
This is a problem with the consult serial data getting corrupted. Were you using the blazt or PLMS consult cable here?
ECU communications problem
Apart from the first character 0x35 is inverse of 0xCA, the following characters in protocol must match
TX:CA 02 0F 44 01
RX:35 02 0B 44 01 FF 01 00 (0F/=0B)
TX:CA 02 0B 44 01
RX:35 02 0B 40 01 FF 01 00 (44/=40)
TX:CA 02 D0 42 01
RX:FE FE 2F FE FE (ECU did not receive valid command) - NIStune disconnect
TX:CA 02 CF 41 01
RX:35 02 4F 41 01 FF 01 92 (CF/=4F)
TX:CA 02 75 44 01
RX:FE FE FE FE FE (ECU did not receive valid command) - NIStune disconec
There were quite a few 'non fatal' communications errors flagged in the log. However since the data is register read data we are tolerant of it
When there is a TX line problem to the ECU it will barf. This happened a few times which caused disconnects
This is a problem with the consult serial data getting corrupted. Were you using the blazt or PLMS consult cable here?