Page 1 of 1

Comm Error

Posted: Mon Feb 06, 2017 1:32 pm
by 2002tiiguy
Having an issue with tunerstudio disconnecting and reconnecting a lot. Ive Redone the comm settings for my serial port according to the manual and its still happening. Any help would be greatly appreciated.

Here is the com log 2:53:38 is the first disconnect
bug.txt

Re: Comm Error

Posted: Thu Feb 09, 2017 2:54 pm
by LT401Vette
It looks like plain old timeouts.

What type of cable and USB to db9 cable are you using?
Is the issue primarily when the engine is running?

Re: Comm Error

Posted: Fri Feb 10, 2017 4:51 am
by 2002tiiguy
No usb, i am running this from a serial port on the back of a panasonic toughbook that is running windows xp, it does not matter whether its running or not. The one time it was so bad that it was just going online offline continuously.

Thanks in advance,
Hunter

Re: Comm Error

Posted: Fri Feb 10, 2017 3:16 pm
by LT401Vette
Send a full TunerStudioAppDebug.txt with Comm Debug turned on. That may give something more.

Re: Comm Error

Posted: Sat Feb 11, 2017 8:42 am
by 2002tiiguy
how can i post the entire log? it was too big a file so i copied and pasted the relevant part from it into that text file i posted.

Re: Comm Error

Posted: Mon Feb 13, 2017 7:11 am
by LT401Vette
You can email it to support <at> efianalytics.com with a link to this thread.

Re: Comm Error

Posted: Mon Feb 13, 2017 7:49 am
by 2002tiiguy
Kk will do when i get home

Re: Comm Error

Posted: Mon Feb 13, 2017 2:26 pm
by 2002tiiguy
ok, sent, and thanks again

Re: Comm Error

Posted: Tue Feb 14, 2017 12:50 pm
by LT401Vette
I got the log, but Comm Debug wasn't turned on.. :(

Try this..
- Delete TunerStudioAppDebug.txt
- Start TunerStudio
- On the main menu select: Communications --> Comm Debug
- Open your project

Then let it disconnect a few times, close TS and send the log.

Re: Comm Error

Posted: Tue Feb 14, 2017 12:53 pm
by 2002tiiguy
Oh, kk will do

Re: Comm Error

Posted: Wed Feb 15, 2017 4:38 am
by 2002tiiguy
https://drive.google.com/open?id=0B_FN5 ... DY1eGpMUmM
ok, def comm debug on, sorry about leaving the gps on, kinda forgot about it, if its an issue, i can turn it off

Re: Comm Error

Posted: Wed Feb 15, 2017 4:43 am
by 2002tiiguy
timeouts occured at 6:18:19, 6:21:34, 6:24:56, 6:25:25, 6:28:22, 6:30:35, and 6:31:50.
i figured it might be helpful if you had the times, its a lot of text to read through

Re: Comm Error

Posted: Wed Feb 15, 2017 6:38 am
by LT401Vette
It looks like it is just loosing data. There are many more timeouts there, but they recovered on the retry. It gets data back, but under-runs.

It looks like there is an issue with your Serial port.

You could try reducing the buffer size in Device Manager's advanced settings.
The best bet is to buy an FTDI based USB to RS232 cable.

Re: Comm Error

Posted: Wed Feb 15, 2017 1:38 pm
by 2002tiiguy
im gonna run it again with the gps off, im having issues with it anyway. would be really ironic if i had to go back to a usb serial adapter to fix errors

Re: Comm Error

Posted: Wed Feb 15, 2017 3:44 pm
by LT401Vette
2002tiiguy wrote:im gonna run it again with the gps off, im having issues with it anyway. would be really ironic if i had to go back to a usb serial adapter to fix errors
That is an interesting one. Way back USB to serial cables were often buggy, so we would all be desperately trying to hang on to anything with a real serial port. Not so much the case any more, if you have a decent USB to serial cable they work quite well. Thankfully seeing that it is hard to find a laptop with a db9 port on it any more.

Re: Comm Error

Posted: Wed Feb 15, 2017 3:47 pm
by 2002tiiguy
Lol unfortunately I just bought this laptop specifically because it had a serial port

Re: Comm Error

Posted: Thu Mar 02, 2017 5:43 am
by 2002tiiguy
Windows issue, Reinstalled xp and it works flawlessly. who knows why