TunaPro Logging problem, need some ideas
TunaPro Logging problem, need some ideas
What up all,
I got around to installing my tuna pro last week and have had a consistant problem with logging. The utec is connected to the rear port of the tuna pro using the cable that came with the utec, I use secure crt v.3.0 for the terminal session with the same session setup i have been using wiht the utec for months now. Prior to installing the tuna logging was working fine. Here is the situation:
When I serial into the tuna I am able to toggle back and forth between the utec menu and the tuna menue just fine. When in the Tuna menu and I try to run log (1 or shift 1) from the tuna interface the first two columns of the first log line fill in then the interface hangs and I am not able to back out of the menues. At that point I have to shut off the car and restart it (power cycle the tuna) before I can get back in, disconnecting the session and trying to reconnect does no good.
If I run logs from the utec interface (1 or shift 1) the logs fill in rather slow and the wide band reading does not match the display on the tuna. for example, if the afr is reading 14.6-14.8 on the tuna, the logs will show 14.00. reving the engine a bit will have the tuna display drop to the 13's while the logged vlaue never really moves at all.
Anyone seen this before??? not sure If I got a bad firmware flash or a bad cable or what.
Dip switches ar all in the up possition, all the serial connections are screwed down and seated well, and the tuna display seems very acurate.. just got this logging problem to sort out
I got around to installing my tuna pro last week and have had a consistant problem with logging. The utec is connected to the rear port of the tuna pro using the cable that came with the utec, I use secure crt v.3.0 for the terminal session with the same session setup i have been using wiht the utec for months now. Prior to installing the tuna logging was working fine. Here is the situation:
When I serial into the tuna I am able to toggle back and forth between the utec menu and the tuna menue just fine. When in the Tuna menu and I try to run log (1 or shift 1) from the tuna interface the first two columns of the first log line fill in then the interface hangs and I am not able to back out of the menues. At that point I have to shut off the car and restart it (power cycle the tuna) before I can get back in, disconnecting the session and trying to reconnect does no good.
If I run logs from the utec interface (1 or shift 1) the logs fill in rather slow and the wide band reading does not match the display on the tuna. for example, if the afr is reading 14.6-14.8 on the tuna, the logs will show 14.00. reving the engine a bit will have the tuna display drop to the 13's while the logged vlaue never really moves at all.
Anyone seen this before??? not sure If I got a bad firmware flash or a bad cable or what.
Dip switches ar all in the up possition, all the serial connections are screwed down and seated well, and the tuna display seems very acurate.. just got this logging problem to sort out
Last edited by Mad_SB; Sep 4, 2004 at 01:32 PM.
There shouldn't be anything different..
Out of curiosity, do you get a new menu option to switch between the UTEC and TUNA?
Mine definitely works right away, and didn't have any issues. Does the Tuner "count down" as its warming up the the O2 sensor? When your connected with the serial interface, do you also see it counting down?
Do you interrupt it as its warming up before its finished?
Just a few things to check..
Out of curiosity, do you get a new menu option to switch between the UTEC and TUNA?
Mine definitely works right away, and didn't have any issues. Does the Tuner "count down" as its warming up the the O2 sensor? When your connected with the serial interface, do you also see it counting down?
Do you interrupt it as its warming up before its finished?
Just a few things to check..
Out of curiosity, do you get a new menu option to switch between the UTEC and TUNA?
Does the Tuner "count down" as its warming up the the O2 sensor?
When your connected with the serial interface, do you also see it counting down?
Do you interrupt it as its warming up before its finished?
Funny thing is, if I look at the dash board view the reading are right in line with the displayed value on the tuna. Thanx for the input Jack. I actually already flashed the unit twice with the latest firmware from txs with the verify option turned on so I don't think it would be a bad flash but maybee the latest firmware is not so compatible with the evo utec. The file I used is TunerVersion15.zip
Another suggestion is your settings on your terminal application..
When you get a chance, make sure your flow control is set to Hardware in the connection settings. If its set to NONE, or XON/XOFF you could actually be losing data as its coming in..
Also, I noticed some older laptops have 16450 or lower serial interface controllers which have very small buffers and lose data as its being recieved. (I've seen it occasionally on USB-Serial interfaces that aren't interrupt driven) I know, technobabble..
Ok.. The gist of it is I have noticed that the UTEC and the TUNER handle flow control a little differently.. so here's a list of things to try before you give up..
1) Check the tuner and the UTEC to make sure their both in RUN mode, not program mode
2) Replace the serial cable between the UTEC and the Tuner (a wire for flow control may be bad)
3) Replace the cable going to the computer
4) If you have a USB-Serial adapter, try a different one, or try on someone elses Laptop or a PC
If all else fails, call TurboXS and arrange to have (which ever unit they determine) it shipped back to them to be serviced/exchanged, if you call them and talk to them, you'll find out very quickly that their responsive and accomodating.
I'm inclined to believe that your terminal program is what is your problem and either its formatting or handshake/Flow control settings may be the problem. Since you reflashed it twice correctly with verify without a problem, if there were a problem with the cable or interface you'd definitely experience a problem transferring the flash to the Tuner.
When you get a chance, make sure your flow control is set to Hardware in the connection settings. If its set to NONE, or XON/XOFF you could actually be losing data as its coming in..
Also, I noticed some older laptops have 16450 or lower serial interface controllers which have very small buffers and lose data as its being recieved. (I've seen it occasionally on USB-Serial interfaces that aren't interrupt driven) I know, technobabble..
Ok.. The gist of it is I have noticed that the UTEC and the TUNER handle flow control a little differently.. so here's a list of things to try before you give up..
1) Check the tuner and the UTEC to make sure their both in RUN mode, not program mode
2) Replace the serial cable between the UTEC and the Tuner (a wire for flow control may be bad)
3) Replace the cable going to the computer
4) If you have a USB-Serial adapter, try a different one, or try on someone elses Laptop or a PC
If all else fails, call TurboXS and arrange to have (which ever unit they determine) it shipped back to them to be serviced/exchanged, if you call them and talk to them, you'll find out very quickly that their responsive and accomodating.
I'm inclined to believe that your terminal program is what is your problem and either its formatting or handshake/Flow control settings may be the problem. Since you reflashed it twice correctly with verify without a problem, if there were a problem with the cable or interface you'd definitely experience a problem transferring the flash to the Tuner.
Thread
Thread Starter
Forum
Replies
Last Post
Vivid Racing
Evo Vendor 'Group Buy / Specials' Classifieds
13
May 27, 2007 02:45 PM
Evoisdream
General Engine Management / Tuning Forum
60
Jun 15, 2005 11:07 AM
