Got a new Dell mini for tuning and lookin to download the tunerpro rt file. I had the older v4 version and never could get it to connect to the aldl with my older laptop....so a pain in the rear! So i got a new Dell and want to try this again so i can actualy get to tunning the thing! Has anyone had probelms with the new tunerpro rt V5 when connectiog to the ostrich and ALDL? Any input would be great with this as im not sure if the bugs have been worked out of the V5 yet....maybe i should just load the newest V4 and try that?

 

I use V5, MOST of the time. The only time I use V4 is when I'm tuning a '7747 ECM, I can get more consistant connection with V4 on the older ECMs for some reason.

 

I use and love V5, awesome piece of work. But, just as stated by Six_Shooter, I do believe that when I datalogged with v4 I had fewer errors. That was with a '165 and a '730. Cable used is aldlcables.com usb.

 

I've had no problems connecting to 8192 baud ECMs, like the '7730/'7749 and '7427 ECMs, using TP RT V5.

It's just the '7747 that I have had issues with, though I haven't tried it lately.

 

I have no probs connecting at all. But during a log I get a lot more error 'spikes' than before. Its not a big deal for me and I'm only about 80 percent sure its the software change So I havent said anything yet (I guess untill now). But it still works great

 

those spikes plauged me for a while... but then i threw in a ~20mS delay between recieving the last packet and requesting a new one... spikes disappeared completely.

 

Im a computer dummy so you totally lost me with that one. I went with the v4 for now....have not used it yet but we will see.

 

where do I add a 20ms delay in the adx file? the only thing I see is a 400ms timeout.

 

alright, what i do is go into the commands section, add new item, add as a "listen for silence", set silence length for 0, set timeout to 20mS(more if necessary), then i create another item, this time it's a macro command, throw in a few mode 8 commands(if necessary), the 20mS pause, the mode 1 message 0 macro(or whatever other message you want/need), the 20mS pause, then that ends the connect command.

i start another macro item, monitor macro, and add these items in this order:

mode 1 message 0
20mS pause

if any other messages need to be sent, they go below, in the pattern of message, pause, message, pause, message, pause, etc....

as long as it starts with a message and ends with a pause, i have had i think maybe 1 or 2 spikes in a log, but they were ALWAYS at the very beginning of a connection.