That is correct. I also put it in the tuner rt folder before that. It did not work with it in there only, but it did when i installed it into the datastream folder. Maybe the combination. Let us know what you find out with yours.

this should be in the autoprom datalogging post please. sorry for the mistake

 

No problem. I got it anyway. I am sure others will want to know this as well.
I am keeping my fingers crossed that it works when I actually have a chance to try it...probably Thursday afternoon as I have classes all tonight and tomorrow night.
Thanx for the heads up!!!

 

you dont even need to be in the car to see if it fixes the problem. I sat at my desk and got mine fixed. It will show the same tables as if you were sitting in the car, just with no values. Its much easier to fix it in the house rather than in the car. just load up tuner pro rt and select the correct aldl file and verify that the sensor and bit data screens are blank or show no info. Next, close tuner pro and unzip the riched 20 dil file straight to the tuner pro aldl datastreams folder and to the tuner pro rt directory and that should fix the problem for you. Just load tuner pro back up and click on the sensor tab and the info should all be there, just with no values. It took me awhile to get mine to work right with my old laptop, but dont give up! good luck

 

fyi - its *very* strange that the dll needs to be in the datastreams folder.

the app looks for it in 3 places (in this order):

1) the windows/system(32) directory
2) the windows directory
3) the application root directory

No idea why it would only work if its in the datastreams directory.


anyway, glad you got it working.

 

clip...by no values, do you mean that the sensor data numerical column is blank? When I was using the TunerPro with riched20.dll loaded in the TunerPro directory, I was getting values in the column, but they were all screwed up...like 20.70 for Batt volts and a bunch of other weird stuff.
Sounds like another Win98 glitch to me.

 

your problem is completely unrelated and almost certainly a result of the incorrect aldl datastream template.

 

If you're in ALDL 160-baud mode and you see squirrely data on the datalog, take note of your data rate. If it's like 5 Hz or so, and not 0.6 Hz, then you're suffering. Go ahead and power down your car's ECM while TunerPro is running, and then bring it back. It should 'fall in line' at that point. Don't know why yet, but that's been my experience.

There's probably some AutoProm firmware upgrades that can get rid of this anomalous behavior. Don't know exactly what the deal is. Then again, I'm seeing this on a 165, don't know if it's the case in your app...

 

Now printing more good stuff...
Thanks, Craig...