[titan2782]

What can I use to read and/or visualize datalogs?

 

[titan2782]

I see that the EZFlash application is not obfuscated. I can see the IL using ILSpy and dotPeek which means I can get the structure of the data logs. Being a .NET developer, I can build my own reader. anyone interested in this?

Edit: Doing a code review right now. I'd like to have a word or two with whoever wrote this thing.

 

[titan2782]

no reason to charge for it.

 

[titan2782]

Quick update: I can read the data log (VIN, PCM Type, DTCs, data frames) but I am still working out how to decipher the meaning of the data points on each frame. Looking into how the logger requests data/receives data and what type of data (if it's configurable). As soon as I can determine the meaning of each data point on a frame I'll slap a graph on it and put up the first version.

 

[titan2782]

I started a new job last week so I haven't had much time to put into this. There is a ton of code to support a bunch of different ECM types for multiple cars. It's like a needle in a haystack, but I'm still working on it. If anyone else knows .NET (or Java) and want to help out, let me know. I'm concerned that I might not be on the right path though, I spoke to VT and they said they log 200+ data points out of the available 400 that the computer can monitor. The frames I'm reading in have ~9 bytes of data each. No idea if Trifecta is only logging certain things they need or if I'm reading the frame wrong. I'm pretty sure I'm reading the frame correctly though since I'm literally reversing the write process.

If anyone has an helpful info, please post it.

 

[titan2782]

Update: I asked Vince for either a data log reader we can all use or some details on the frame data so I can make a first release to you guys. The code is intense. I may have to hook up my car and debug it live.

 

[titan2782]

Woohoo! Made some great progress today. I've identified how the frames are broken down and which data points are being logged. I still ahve some work but I'm going to try to get IAT's mapped today.

BTW: Vince said no dice on a public log reader and he has nothing to share with me as far as the data format. BUT, he DOES have some loggers to sell from a 3rd party vendor (at discount of course).

So it seems that providing data loggers to us would hurt business since he sells logging products.

 

[titan2782]

Success! I've broken to code and I can now read the data and I can chart it as well. Below are some screens. I used a very short data log where I only went to 23 MPH and low RPM's to verify the data I'm seeing.

View attachment 8130 View attachment 8131 View attachment 8132 View attachment 8133 View attachment 8134 View attachment 8135


However, there are some data points that are all jacked up although I'm not quite sure why. I think it might have to do with the length of the data point. Right now I'm handling data points with a length of 1 and 2 bytes. For example, IAT readings are whack even though it's only 1 byte in length. So still some tweaking to do.

View attachment 8136

I'm going to clean it up and try to work out why some data points are being strange and then I'll release to you guys.

 

[titan2782]

It would be helpful if someone could run through this thing and help verify the data using another tool like the Torque app or something else.

 

[titan2782]

It's been released. See http://www.cruzetalk.com/forum/10-e...data-log-reader-first-release.html#post132136