Logged data is missing and playback is messed up?

IsaacHayes · Post by **IsaacHayes** » Sat Dec 29, 2007 7:19 pm

Ok I got my definition file, and it shows up ALL the data for everything under the sun. I'm using my own modified ads for the 1994-95 3100 which adds a few more things and completes the CCodes descriptions. This is the one on the tunerpro site that ryan.hess made that says $1FA (although $1FA computer is actually the A body MAF 3100's only).

1) BUT when I go to log it, and view it, it's missing BLM's, O2, etc etc. All the important stuff I wanted to log.... What gives? They are all 0's.

2) When I click play back, it doesn't work. It does something but none of the values change, except the trouble codes, they all randomly go from OFF/ON.

Here is an example log:
http://isaachayes.60degreev6.com/aldlcable/hwy.csv

And here is the def I use (same problem with the $1FA one though)
http://isaachayes.60degreev6.com/aldlca ... 994-95.ads

Missing info (all 0's)
BLM
INT
Oxygen mV
TCC Slippage
IAC Steps
Voltage at Fuel Pump
Spark Advance shows up but as a weird #...

All above values work fine in real time though..

Help!!

IsaacHayes · Post by **IsaacHayes** » Sun Dec 30, 2007 11:31 pm

Well I import the def into ScannerPro, set RS232 echo, and made a connection macro (disable coms, pause, listen for silence, connect), and set the MAT formula to "X" as it was set to the # for the MAT table and not working that way.

It works great, plays back logs fine, but the trouble codes are switching on/off. Not sure if that's legit or not as it's showing all kinds of bad things! But in TunerPro RT none show as being tripped...

So I'm thinking perhaps it's a bug in TunerPro... I might make a copy of the def, and strip out all but RPM, BLM (important stuff) and see if it will play back and log a .CSV with the info instead of all 0's....

IsaacHayes · Post by **IsaacHayes** » Thu Jan 03, 2008 2:55 pm

This seems to be a bug with TunerPro recording the data stream.

ScannerPro has no problem recording it.

Moonwell said the TunerPro .adl file was full of holes compared to the ScannerPro .xdl file of mine.

Files are in the directory link above if anyone wants to look at them.

Post by **Mangus** » Sat Jan 05, 2008 11:22 am

TunerPro only logs the master/monitor message - it doesn't log the other commands in the datastream definition. It should log whatever you see in the UI.

Outside of that, I can't think of any reason for what you're seeing. Are you sure you're recording to a fresh log file?

I did a lot of work to the scanning and logging engines in ScannerPro. I'm happy to hear that it's working.

IsaacHayes · Post by **IsaacHayes** » Mon Jan 14, 2008 1:31 pm

Yes I tried fresh logs. I tried re-installing, recording to a different directory and drive, powering the laptop from battery alone, wearing different colored socks, etc, etc...

It shows the data flawlessly in real time. But when it records it's missing chunks of data.... And of course won't play back at all, and CSV export is missing data....

ScannerPro works flawlessly, but has no .CSV export of course.

I fully believe it's a bug with TP... Any links to older versions? I know someone else made a def file a long time ago with the same car as mine and he was able to log... I could try an older version and see if it works...

Post by **Mangus** » Mon Jan 14, 2008 1:32 pm

No, there are no older versions available. The logging code in TunerPro hasn't changed in years.

IsaacHayes · Post by **IsaacHayes** » Tue Jan 15, 2008 12:03 pm

SP however shows codes section going nuts, but I'm thinking I need to make a 2nd def with the master command as Mode1 Message2 (check codes) instead of Mode1 Message0 (data) and try that...

Since SP you can't manually send commands. I have a macro setup to connect right now that sends a disable coms command first before connecting.

ECM OVERVIEW
------------
The ECM is the master of ALDL. When an ALDL tester is used
to gather ALDL data, it should gain master ship of ALDL by issuing
a mode 8 to the ECM. Once the tester has gained mastership, it's the
testers responsibility to schedule and command normal mode messages
(see normal mode message schedule) from the ECM to maintain normal
system functionality while gathering ALDL data from any module on
the data link.

Post by **Mangus** » Tue Jan 15, 2008 4:51 pm

IsaacHayes wrote: Since SP you can't manually send commands. I have a macro setup to connect right now that sends a disable coms command first before connecting.

Yup, that's exactly what you need to do. It's all automatic that way, when you hit the connect button.

IsaacHayes · Post by **IsaacHayes** » Sat Jan 26, 2008 5:47 pm

Got it working and reading codes as a 2nd def file. You can't read codes and read sensor data at the same time at least on this ECM since it's a different mode.

Scanner Pro can't manually send commands though so to clear trouble codes I use TunerPro to send that command manually.

Will SP export .CSV in the future? I'd use TP but it doesn't record the datastream right on my ECM when logging.

Post by **Mangus** » Sat Jan 26, 2008 10:43 pm

Yes, SP is a long way from releasable. export will be there, etc.