Disconnecting problem?

Fusion Ed · Post by **Fusion Ed** » Fri Nov 02, 2007 4:30 am

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.

Matt · Post by **Matt** » Fri Nov 02, 2007 10:36 am

if you can do a log when it disconnect or when you have problems, zip it up and shoot it through i can have a look for you

Fusion Ed · Post by **Fusion Ed** » Fri Nov 02, 2007 1:50 pm

Just a normal record log or a debug log? I think i already have several of both, where does nistune put its debug logs? I have never thought to have a look?

Matt · Post by **Matt** » Fri Nov 02, 2007 5:36 pm

First enable: File - Configuration - Debug logging

Next restart NIStune

Logs get put in C:\Program Files\NIStune\logs

Fusion Ed · Post by **Fusion Ed** » Wed Nov 14, 2007 11:30 am

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

Matt · Post by **Matt** » Wed Nov 14, 2007 12:19 pm

What version of NIStune did you notice this started occuring? When was the last working version you didn't notice the problem

That way I can compare code between versions to see what has changed

I'll have a look at the log file tonight

Fusion Ed · Post by **Fusion Ed** » Wed Nov 14, 2007 12:34 pm

It appeared to be fine before I tested any of the test versions. I don't recall this ever happening before then.

Matt · Post by **Matt** » Wed Nov 14, 2007 12:37 pm

No probs so that would be 0.9110 version then

Fusion Ed · Post by **Fusion Ed** » Wed Nov 14, 2007 12:46 pm

Thing is matt this was a new batch of Nistune boards, as well. Did you change anything on these between the first lot and the second lot I had?

Matt · Post by **Matt** » Wed Nov 14, 2007 7:32 pm

Nothing has changed between versions except board locking was introduced

What is the firmware version PID shown when you connect?

Matt · Post by **Matt** » Wed Nov 14, 2007 10:56 pm

That link doesn't work when I click on it

Can you check that the filename in the link is correct?

Fusion Ed · Post by **Fusion Ed** » Thu Nov 15, 2007 4:08 am

I didn't check that file. I'll correct it now..

Edit: Done.....

Fusion Ed · Post by **Fusion Ed** » Thu Nov 15, 2007 1:00 pm

Update: new version of nistune seems to have no problems at all. Used it for about 4 hours today and never had a problem with it once. Strange but true... and on the same car too

Matt · Post by **Matt** » Thu Nov 15, 2007 2:49 pm

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

Matt · Post by **Matt** » Fri Nov 16, 2007 1:03 am

Hi Ed

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?