Issue : when attempting to connect to a 160 baud ECM with TunerPro RT V5, I get the status message “DA: Connecting ...” but it never does. I read the similar TunerPro Discussion Forum “Just tried V5 can’t get $42 to connect” post but it really never gets to a solution. My issue differs somewhat in that V5 was communicating fine at 160 baud. I developed and tested several 8192 baud ADX’s and now none of my 160 baud applications work. I go back to a 8192 baud application and it works fine.
I have tried various other “scan” programs at 160 baud and they all work fine. When I go back to TunerPro RT V4, I also have no 160 baud problems at all. Unfortunately I have already gotten addicted to the new features available in V5 and I need a fix.
I have tried taking my currently working V4 ADS file and importing it to a new V5 ADX file, after all, that worked before . . . . no success. I tried updating from TunerPro RT Version 5.00 beta Build 5.00.6156.00 to the newest TunerPro RT Version 5.00 beta Build 5.00.6356.00 . . . . no success. I tried uninstalling TunerPro RT (which of course doesn’t really fully remove all the resources used) and reinstalling V5 . . . . no success.
Is there a ‘file/resource/module/etc.’ that could have gotten corrupted that is used in TunerPro RT for 160 baud communication that it doesn’t use for 8192 baud communication ??? Is there a PC port setting that would affect 160 baud communication only for TunerPro RT ????
HELP . . . I need my fix !!!
Thanks in advance ...... Carl
160 baud communication prob’s w/ V5
Moderators: Mangus, robertisaar, dex
OK, I just hooked up my 1227747 ECM, running $42 code, up to the test bench. Downloaded the $42.ads file straight off of the TunerPro site and imported it and loaded it into the latest version of v5.
I set up the COM port to match the port my cable is installed to (COM3 in my case). I then hit connect, and had an instant, accurate connection, with no dropouts.
Unfortunately that doesn't help you, but it does prove (at least to me) that the software is working as expected.
Unfortunately it sounds like you've tried the things I'd suggest. What kind of interface cable are you running?
I set up the COM port to match the port my cable is installed to (COM3 in my case). I then hit connect, and had an instant, accurate connection, with no dropouts.
Unfortunately that doesn't help you, but it does prove (at least to me) that the software is working as expected.
Unfortunately it sounds like you've tried the things I'd suggest. What kind of interface cable are you running?
***************************************
TunerPro Author
1989 Trans Am
TunerPro Author
1989 Trans Am
Unfortunately you may not be able to duplicate it on your testbench. I suspect it is a problem at my end, not one with V5.
V5 was working fine on my testbench but after working on some 1227727 applications(new harness for my bench), I went back to a 1227747 to run some tests and this issue showed up. I checked all the settings within TunerPro and looked at the computers comport settings and and I didn't find anything wrong(though I'm not the computer geek I thought I was years ago).
Is there any resourse/file that TunerPro only uses for 160 baud communication that could have gotten corrupted ???
Thanks for your reply ... Carl
V5 was working fine on my testbench but after working on some 1227727 applications(new harness for my bench), I went back to a 1227747 to run some tests and this issue showed up. I checked all the settings within TunerPro and looked at the computers comport settings and and I didn't find anything wrong(though I'm not the computer geek I thought I was years ago).
Is there any resourse/file that TunerPro only uses for 160 baud communication that could have gotten corrupted ???
Thanks for your reply ... Carl
I'm not sure what would cause v5 to not work where v4 does, though. That doesn't make much sense to me. In terms of the acquisition of the data packet, it pulls data from te port the same way as v4. It processes that data differently, but it pulls it in the same. So from that perspective, if it works in v4, it should work in v5.
If TunerPro runs, nothing with TunerPro itself is corrupt. It sounds like you know enough to check the definition you're using to see if something in it has changed. Worst case, do what I just did - re-download the ADS and import it.
I'd love to know what's causing this. I wonder if we can set up a remote session or something. Craig Moates has a way to do this, so maybe we can do it through his setup. Let me think on that and get back to you.
If TunerPro runs, nothing with TunerPro itself is corrupt. It sounds like you know enough to check the definition you're using to see if something in it has changed. Worst case, do what I just did - re-download the ADS and import it.
I'd love to know what's causing this. I wonder if we can set up a remote session or something. Craig Moates has a way to do this, so maybe we can do it through his setup. Let me think on that and get back to you.
***************************************
TunerPro Author
1989 Trans Am
TunerPro Author
1989 Trans Am
This morning I tried reinstalling the latest V5 into a new directory/folder. I imported the 1227747_42.ads to a new .adx file and still I just get the status message “DA: Connecting ...” but it never does. This is probably the fourth time I have tried this, but the first time in a new directory. I openned up V4.14 and it connects almost immediately. I didn't try a 8192 baud application yet but if the past is any indication it will connect in any version of TunerPro.
I am going to go back to my original question, is there a ‘file/resource/module/etc.’ that could have gotten corrupted that is used by TunerPro RT for 160 baud communication that it doesn’t use for 8192 baud communication ??? By this I don't necessarily mean in the TunerPro code itself. Any Windows resource that TunerPro calls on, say a .dll file for example. Or is there a PC port setting that would affect 160 baud communication only for TunerPro RT ???? This doesn't make a lot of sense to me but at this point I have to ask.
Thanks for the feedback . . . . Carl
I am going to go back to my original question, is there a ‘file/resource/module/etc.’ that could have gotten corrupted that is used by TunerPro RT for 160 baud communication that it doesn’t use for 8192 baud communication ??? By this I don't necessarily mean in the TunerPro code itself. Any Windows resource that TunerPro calls on, say a .dll file for example. Or is there a PC port setting that would affect 160 baud communication only for TunerPro RT ???? This doesn't make a lot of sense to me but at this point I have to ask.
Thanks for the feedback . . . . Carl
Thanks for the reply. Sorry for the delay in responding. I am buried in work, which is not such a bad thing these days.
Well, your answer is not the one I wanted to hear but it does suggest that this is most likely a problem at my end (which may also be an answer I don't want to hear).
An update: I may have a hard drive problem. I have cleaned/deleted unnecessary files from the drive, run chkdsk, and defragmented the hard drive. I then ran a hard drive diagnostic program and I'm showing some bad clusters. I again tried a fresh reinstall and ADS import - and no success, won't connect at 160 baud but will at 8192 baud and V4 works fine.
I replaced my hard drive just over 2 years ago because of bad clusters. Interestingly enough, TunerPro V4 wouldn't load from that drive (maybe you should market TunerPro as a hard drive health indicator program). My work is such that I'm really hard on laptops. They are always being loaded and transported, sometimes on rough roads in my 1 ton(stiff) service truck.
When I have time I will transfer my TunerPro files to my old laptop(iffy motherboard but still works - just not dependable) and if my communication problems magically disappear I will have to conclude I've lost some bit of necessary information that will allow V5 to connect. Unless you can see another solution, I will have to replace my hard drive and do a clean install (done once before and so not looking forward to it).
Thanks . . . . Carl
Well, your answer is not the one I wanted to hear but it does suggest that this is most likely a problem at my end (which may also be an answer I don't want to hear).
An update: I may have a hard drive problem. I have cleaned/deleted unnecessary files from the drive, run chkdsk, and defragmented the hard drive. I then ran a hard drive diagnostic program and I'm showing some bad clusters. I again tried a fresh reinstall and ADS import - and no success, won't connect at 160 baud but will at 8192 baud and V4 works fine.
I replaced my hard drive just over 2 years ago because of bad clusters. Interestingly enough, TunerPro V4 wouldn't load from that drive (maybe you should market TunerPro as a hard drive health indicator program). My work is such that I'm really hard on laptops. They are always being loaded and transported, sometimes on rough roads in my 1 ton(stiff) service truck.
When I have time I will transfer my TunerPro files to my old laptop(iffy motherboard but still works - just not dependable) and if my communication problems magically disappear I will have to conclude I've lost some bit of necessary information that will allow V5 to connect. Unless you can see another solution, I will have to replace my hard drive and do a clean install (done once before and so not looking forward to it).
Thanks . . . . Carl
Carl - again, hate to give you more bad news, but most likely this has nothing to do with your hard drive. If TunerPro loads at all, everything is fine. If any single component failed to load (including components within the operating system that TunerPro relies on), then the application would fail to load entirely.
Loading is an all-or-nothing thing.
What this could be is serial/USB hardware related. You still haven't told me what kind of interface cable you're running. Is it serial? USB? If serial, did you build it yourself or purchase it? 2-trans type or MAX232? If USB, is ia FTDI based? Etc, etc.
Loading is an all-or-nothing thing.
What this could be is serial/USB hardware related. You still haven't told me what kind of interface cable you're running. Is it serial? USB? If serial, did you build it yourself or purchase it? 2-trans type or MAX232? If USB, is ia FTDI based? Etc, etc.
***************************************
TunerPro Author
1989 Trans Am
TunerPro Author
1989 Trans Am
I am told that the bad clusters most likely mean there has been contact with the read head which leaves debris that will cause more bad clusters and on. If the drive is failing I need to replace it anyway, whether or not it will fix the issue. Maybe I can get lucky ????
It is a AKMcables.com cable connected directly to the serial port of a Dell 600M (I beleave Dell's last laptop that still came standard equipped w/ serial port).
It is a AKMcables.com cable connected directly to the serial port of a Dell 600M (I beleave Dell's last laptop that still came standard equipped w/ serial port).
The final chapter
I continued to mess around with various laptop settings until all versions of TunerPro RT would fail to successfully communicate (not my intent). At one time I got an error message about an incorrect version of winsta.dll and tried different versions only to get back to where I was before - TunerPro RT versions 3.09 and 4.14 work fine, version 5.00.6356 won't connect at 160 baud, but at 8192 baud it will connect and communicate fine.
After I was unsuccessful at resurrecting my other laptop(motherboard failure), I acquired an off-lease Dell Latitude D630 laptop in like new condition(Dell refurbished). Turns out these are one of the few non-military grade laptops that still have a serial port. For anyone who might be interested, these can be had for a really reasonable price on E-bay(~$300). I transferred the TunerPro RT v5 installation file and my ADX file over, installed it and, Voila ! , everything works fine. Just as it had been before this mysterious issue started.
Next step was to replace the hard drive on the Dell D600 laptop. New drive and fresh installation of OS and programs - again, TunerPro RT v5 is back to working correctly.
The good news . . . I now have two good TunerPro workhorse laptops. The bad news . . . though I know what I did to get the problem to "go away", I still don't know exactly what the actual cause was. I was really hoping to discover the cause to provide an easy fix should anyone ever run into a similar issue. Unfortunately this appears to have been "above my pay grade".
Keep the throttle down . . . Carl
I continued to mess around with various laptop settings until all versions of TunerPro RT would fail to successfully communicate (not my intent). At one time I got an error message about an incorrect version of winsta.dll and tried different versions only to get back to where I was before - TunerPro RT versions 3.09 and 4.14 work fine, version 5.00.6356 won't connect at 160 baud, but at 8192 baud it will connect and communicate fine.
After I was unsuccessful at resurrecting my other laptop(motherboard failure), I acquired an off-lease Dell Latitude D630 laptop in like new condition(Dell refurbished). Turns out these are one of the few non-military grade laptops that still have a serial port. For anyone who might be interested, these can be had for a really reasonable price on E-bay(~$300). I transferred the TunerPro RT v5 installation file and my ADX file over, installed it and, Voila ! , everything works fine. Just as it had been before this mysterious issue started.
Next step was to replace the hard drive on the Dell D600 laptop. New drive and fresh installation of OS and programs - again, TunerPro RT v5 is back to working correctly.
The good news . . . I now have two good TunerPro workhorse laptops. The bad news . . . though I know what I did to get the problem to "go away", I still don't know exactly what the actual cause was. I was really hoping to discover the cause to provide an easy fix should anyone ever run into a similar issue. Unfortunately this appears to have been "above my pay grade".
Keep the throttle down . . . Carl