Can't stay connected with TS

[WisAndy]

trakkies, Thanks for the reply. I was away from the car for a while (darn job gets in the way). I did not bring my megasquirt home with me, so the soldering/inspection will have to wait for tomorrow. I'll attempt a datalog too. It may be Sunday before I get to back to you. The job thing. WisAndy

[WASyL]

hi there,

had similar issue with mu connection to TS, i was using this kind of rs-232 cable

and found that smoe of the com port's on some devices won't work properly and using cable with filter (that round stuff on picture below, thon know proper name in english for it) solved problem


best regards

[WisAndy]

WASyL, Thanks for the reply. My mother's ancestors are from Poland. I traveled through Poland by bicycle in 1991.

Could you post a part number for that cable? I looked at Pacific Cable's website and I'm having difficulty finding the cable in the picture. Thanks. WisAndy

[trakkies]

The 'lumps' are simply ferrite beads, clamped round the cable. Radio Shack may have them to be used with any cable. However, they are more to suppress any radiation from the cable than to help with any entering it.

[WASyL]

Sorry WisAndy i found this picture on google just as an exapmle

OT good to hear that some MS users visit Poland

best regards

[WisAndy]

WASyL, Thanks for the reply. trakkies said that there may be something available from radioshack.

LT401Vette, trakkies, WASyL, I took a video of how TS is behaving for me. Spent most of today trying to upload to this forum. My connection is very slow so I will have to pursue a better connection. Uploading to youtube may be an alternative.

I did inspect/solder the connections between the DB9 connector, the U6 chip and the processor socket. Some connections were suspect. Will know more tomorrow. Also attempt a datalog.

WisAndy

[WisAndy]

LT401Vette, trakkies,WASyL,

Have a video on youtube showing what is happening. It is at http://youtu.be/LJUJvlQQYTM.

The results of inspecting/soldering the connections between the DB9 connector, U6 chip and processor did not remove the online/offline condition.

Attached is a datalog taken yesterday.

I've tried 3 different cables. I don't know what to do next.

WisAndy

[WASyL]

hey,

you'r using wrong ini file, is should be 2.90 B&G Embded not 2.905, download this one and use it:
http://www.megamanual.com/files/ini/ - go there and get file megasquirt-II.ini.2.900


best regards

[WisAndy]

WASyL,

Thanks for the reply. Found and downloaded the 2.90 ini. Will try it tomorrow.

WisAndy

[LT401Vette]

Yes, you are not having comm problems at all, in fact you are on a bench there. The series of warning message are key to the problem.

You should not ignore ini mismatch error message.

[WisAndy]

LT401Vette, Thanks for the reply. I take it you have watched the video. I am currently using v2.905 on the Megasquirt controller. I thought I was using the corresponding 2.905 ini. WASyL said that I should be using the 2.90 ini. I have tried that with the same results. Have I done something wrong in the process of loading the controller? Do I have something wrong with how I am using TunerStudio? WisAndy

[LT401Vette]

Actually looking more closely at the video, it seems you have 2.905 on both.. But what it is showing from the controller is missing the trailing white space, that is why TS isn't finding the correct ini on it's own.

What version of TS are you running?

Can you turn on Comm Debug and send the TunerStudioAppDebug.txt file?

[WisAndy]

LT401Vette, Thanks for the reply.

When I start TunerStudio it says across the top of the screen TunerStudio MS Lite! v2.0.6

I attempted to attach TunerStudioAppDebug.txt. Mine is over 3 MB. Message from the forum max. allowed is 1 MB. Is there a way around this?

WisAndy

[LT401Vette]

Several...
You could delete it first, then start TS and turn on comm debug. It will create a new smaller file.

Zip it

or just email it to me at support@efianalytics.com

[WisAndy]

LT401Vette, Thanks for the reply.

I will save the current TunerStudioAppDebug.txt file under another name if we need to refer back. Start TS and turn on the comm debug feature and send you that file. It will be later today. The car is at a different location from where I am now.

WisAndy

[WisAndy]

LT401Vette,

Have a file for you to look at. Activated comm debug. All of the behavior is the same as the video. I could not start the car because the battery was run down from leaving the trunk open for two days.

WisAndy

[LT401Vette]

Interesting... There does seem to be a comms issue.
It will be fine for a spell, then start getting reads with missing bytes.

Code: Select all

1/11/13 11:55:23 AM :Debug: break wait after 310 ms, 108 bytes read, expected:112
...
1/11/13 11:55:23 AM :Debug: break wait after 301 ms, 110 bytes read, expected:112
...
1/11/13 11:55:29 AM :Debug: break wait after 310 ms, 111 bytes read, expected:112
...
1/11/13 11:55:29 AM :Debug: break wait after 310 ms, 107 bytes read, expected:112
...
1/11/13 11:55:30 AM :Debug: break wait after 301 ms, 108 bytes read, expected:112
...

The number of dropped bytes seems to vary...

Am I right that in that video you did not have a running engine? So there should not be much for EM noise.

[WisAndy]

LT401Vette, Thanks for the reply.

In the video, the engine was not running until near the end. You may notice some shaking when I started the engine.

The log file I sent you had no engine operating at all.

The log file and video were two seperate events but almost identical behavior based on my observation.

WisAndy

[WisAndy]

LT401Vette,

What does the dropped bytes mean? Is there a problem on my laptop? I need some direction on where to go from here. Thanks.

WisAndy

[LT401Vette]

It means:
TunerStudio is requesting a read of the runtime data, for your firmware the response to that is 112 bytes.
It appears the controller is receiving the request and responds, I will assume with the 112 bytes.

In most cases the 112 bytes is getting back to TunerStudio, but it then seems to go through periods where it is only getting back 107-111 bytes, thus 1-5 bytes of the 112 never made it back to your laptop.

After 3 timeouts in a row, TunerStudio goes offline.

It still seems as though you have a problem with your serial cable or your laptops serial port.

If you have any other laptop/pc you could connect with that and rule out the MegaSquirt and cable as the problem.

Probably 95% of the time the problem is in the cable, but that doesn't mean always.