communications issues

[Sam280Z]

Window 7 64bit
TS V 2.6.05
MS3 pre1.4alpha5
MS3X
CANEGT

CurrentTune (1).msq

CAN1_CurrentTune.msq

project.properties.txt

I don't know if this is a hardware, software, or user (most likely) problem, but this all started while I was playing with the CANEGT settings. The problem is intermittent, but occurs regularly. I thought it might be a bad USB cable because it stopped for a while with a new cable. (The only failure I've seen so far with the new cable is the loss of communications to the CANEGT)

It started with losing communication between TS and the CANEGT.
https://drive.google.com/file/d/0BwzTtn ... sp=sharing
I am also occasionally getting timeouts after three connection attempts.

I found that loading a similar project (everything the same except the fueling algorithm) would reestablish communication with the CANEGT. Then reloading the original project, it would be fixed - for a while.

A couple of times the TS gauges would slow way down.

I also got this error: https://drive.google.com/file/d/0BwzTtn ... sp=sharing

I can connect to the CANEGT directly with USB with no problem.

I have made sure that all of my COM settings are correct. Sometimes, when things are acting up and I try to connect to the MS3, I get this weirdness:
https://drive.google.com/file/d/0BwzTtn ... sp=sharing

I've also found this AppDebug file in my TS Projects folder: https://drive.google.com/file/d/0BwzTtn ... sp=sharing

Any ideas on the issue (i.e. what I'm doing wrong) or how to further diagnose?

Thanks,
Sam

[Matt Cramer]

First, try using the latest stable release code; does the issue persist there?

[Sam280Z]

OK. Before I attempted to load the release code, I wanted to make sure that it was still behaving badly. I turned everything on and connected to TS. Everything looked fine. I switched to CAN1 using the pulldown menu in TS. Everything was still working. Then I switched to realtime display under data for the CANEGT. TS informed me that I was offline. There were no other error messages. When I switched back to the MS3 project, both of my AFR readings (analog and serial from the LC1) indicated 10.00:1.
Screenshot:
https://drive.google.com/file/d/0BwzTtn ... sp=sharing

Link to debug file:
https://drive.google.com/file/d/0BwzTtn ... sp=sharing

I'm going to load the release firmware now and report back.

[Sam280Z]

Before installing the release firmware, I restarted the MS3 and did the exact same actions and it worked fine and stayed connected. grrrr.

release code being installed now...

[Sam280Z]

Thanks for the help.
release code is working. I haven't been able to initiate a failure yet.
If it means anything, it took over 3 minutes to install the release firmware. I don't recall it ever taking that long.
thoughts?

[Matt Cramer]

For some reason, firmware often takes longer to install via USB.

You ought to post about this glitch in the MS3 code development section. Could be some of the new CAN protocols broke something.

[LT401Vette]

In the Advanced settings for the Com port, there is a FTDI setting "Latency Timer", The default value for this is 16ms.
If you set it to 1, it significantly improves the performance for firmware loading and runtime data read rates.

If you use the D2XX driver in TS, then it doesn't matter, but for the firmware loader you are always working through virtual com

[Sam280Z]

I already had the latency set to 1.

I drove around using autotune. After around 15 minutes, I got the same errors. First the failed to communicate with CAN1; and then serial communication error during page burn. Then TS was going on and offline and acting generally sluggish.

Turned off MS3, restarted TS and then turning on MS3 gives me this: https://drive.google.com/file/d/0BwzTtn ... sp=sharing

Going to the communication settings and testing the port settings that were just working fails.
Detecting the device gives the weird characters in the detected firmwares.
Tried multiple time with 2 different USB cables. Cannot get it to connect.

Plugged in a bluetooth adapter and it connects to shadowdash just fine. Although I'm not sure if the CAN stuff is configured there.

unplugged bluetooth adapter and try to connect to TS - no dice. I get the exact same behavior.

Closed and reopened TS. Got this: https://drive.google.com/file/d/0BwzTtn ... sp=sharing
Still won't connect.

Meanwhile the car starts and runs fine.

Hardware failure? I don't think it's noise as it happens with everything off.

Thoughts?

[LT401Vette]

Any chance there is a wiring trouble on the CANH & CANL between the 2?

[Sam280Z]

I think I got it fixed.
It was a wiring problem of sorts.
I have the MS3 in the glove compartment. I had a USB and serial cable both plugged in and ran to a convenient location in the center console.
I know you can only use one or the other at a time, so I would either plug in the laptop to the USB or the bluetooth adapter to the serial cable. Both cables were always plugged into the MS3.
This worked fine until I added the CANEGT - and even then the problems were intermittent.
I unplugged the serial cable from the MS3 and have not had another communication error since.
Could this have been causing the problem?

Thanks,
Sam

[racingmini_mtl]

Could this have been causing the problem?

Yes. You basically had an antenna picking up noise and sending it to the serial port: that will mess up the serial connection.

Jean