Cable test function not working?

[dyeager535]

Using Tunerpro RT of course, '165 6E. APYP bin that I burned, starts/runs vehicle fine.

Built the two transistor cable, can't get tunerpro to connect.

Two laptops, both 366's, one win2k, other win98. Most up to date Tunerpro version. Two transistor cable I built. (actually built two, same issue) Disabled all the infrared stuff that I could. One doesn't have option in BIOS though.

Problem I have is that Tunerpro's cable test shows that the cable is connected and working even if there is no cable hooked up to the computer. This happens on either one. (plus my win2k desktop) I've tried reinstalling, no change.

It seems that only if Com2 is selected does the cable test show that the cable is connected and working.

I've changed the target sample rates and com ports, no difference.

Only other slightly odd thing is if I go with the '165/160 baud datastream definition, it will show that I'm connected to the ECM even without the cable, and will let me record. If I record (no data of course) then try to play, tunerpro crashes. I suspect this is due to no data, but just throwing that in there in case it indicates another issue.

I guess first things first, I need to know if the cable test "working" with no cable is because the com port is still being used by something else, or I've got something else going on. Since I built this cable and haven't had it work yet, I'd like to make sure the test works right.

[Mangus]

Cable test should be functioning. i'll check it later tonight.

Regarding the 160 baud "connected" dialog - this is rather misleading. What it should say is that TunerPro is looking for data, not necessarily that it has actually found data and is considered connected. I'll be fixing that too.