Can't Get TunerPro to Link-up - please need help

[jmgtp]

I have a bunch of codes and I need to see what my swapped motor is doing.

I'm using TunerPro RT, a moates cable and a serial to usb adapter. I've used all this stuff successfully in the past. But now my new laptop is windows 7 and it wont connect.

I'm using DF.ecu (DF_v1.4.3.adx, by Sil) that I've used in the past, so I don't think its that.

When I configure the plug-in component the cable tests OK.
But when I try to auto-detect the hardware it fails that test.

I think I've got the com port stuff right.
If I click the edit ADX button what should I see for values?

Default baud = 8192
Parity = None
RS232 echo is checked.
Stop Bits = 1
Byte Size = 8
Connection = Mode 1 ALDL Dump Request Send
Monitor = None
Disconnect = None

My cable is plugged into the cigarette lighter and it is powered.

I just can't connect and I really need it to so I can see what my ECM is doing.
I'm doing battle with my LX9 swap and have codes 15, 22, 34, 43. An alternator that won't charge. But the damn thing runs, the idle is rough but considering all the codes and the fact that its running on the dohc code I give it credit.

[jmgtp]

Ok, I can now get get TunerPro to connect to the ALDL. I imported df.ecu but I see not data from the cars ecm. I do not have an xdf loaded. I dont have one. Is it needed?
Going nuts trying to figure this out

[jmgtp]

Maybe it isn't connecting, I cannot get it to recognize my cable.
You can see in the pic that the USB/serial adapter is com 3. I have tunerpro set to com 3. I have the cable plugged in, and powered by the cig lighter. When I test it I get the error that you see. I have no idea what to do!

[robertisaar]

that test isn't always 100% correct anyways.

Connection = Mode 1 ALDL Dump Request Send
Monitor = None
Disconnect = None

^^ that concerns me, you should have a monitor command, usually the mode 1 macro, otherwise, it will connect, then instantly disconnect since there is nothing to do. the connection option is for vehicles that require "conditioning" of the ALDL circuit to remove chatter from other modules.

[Superdave]

where it says "use plug in" have you tried the other option?

TP5 was pretty buggy when i was trying to get it running on my test bench...

[jmgtp]

I got it to work My targus usb/serial adapter woudlnt work at all. I ended up using an old bulky belkin adapter and a windows xp driver (running windows 7) and finally it works. How do I make TunerProRT (v5.x) refresh faster? It seems laggy, like if I stab the throttle there is a 1 second lag before the TPS % change is reflected.

[robertisaar]

1 second is definitely wrong, you should get updates between 8 and 10 times per second...

the only reasons you'll get lag like that is if the computer can't handle it, the connection at the ALDL port is flaky, the serial-USB adapter is flaky, or the monitor command is bad.

[jmgtp]

Can you elaborate some on the monitor command and what I should be seeing there?

I've used the same laptop in the past with excellent results as well as the same cable and usb/serial adapter. So, I don't think the hardware is the issue.
The laptop was upgraded from Windows Vista to Windows7 and that caused the driver issues that led to my cable not working. I want to say that the lag is software and not hardware. Once a second may have been an exaggeration but I'd say that it is updating no more than 2x/second. Its not 'smooth' if that makes sense. I fear any datalogs that I do with this slow of a refresh won't be too helpful.

[robertisaar]

in the bottom status bar, there's actually a rate indicator next to the blue bar that says "connected", it should give the update rate in Hz, find out what that is. or record a log and post it somewhere, average sample rate can be determined from that as well.

[jmgtp]

I remember seeing that floating around at 4.9x with the motor off but igntiion on and down to 1.9x with the motor running.
I'll check tonight to be sure. So I assume the refresh rate isn't adjustable in TunerPro then and it just runs as fast as it can in the given conditions.

[robertisaar]

hmm.... the fact that it changes with motor on/off is an issue... 5Hz is still low.

refresh rate is determined(in Tunerpro anyways) by the monitor command, and how it's setup. normally in the monitor macro you'll have just the send and recieve commands. if those are the only objects, then refresh rate will be at it's maximum possible for the datastream, and with $DF it should be between 8-10 updates per second due to the size of the datastream and working at 8192 baud.

if there's anything other than just the send/receive commands, then the sample rate will drop due to some kind of action taking place between TP sending the command to the ECM to dump the datastream and it reading the response, then doing it again until you tell it to disconnect.