I'm releasing the basic logger for people to test out..

Basically it will quickly let you get logs.. No advanced features such as map tracing or wideband logging yet..

But I need to know the basic logger features work right.

http://www.aktivematrix.com/forum/viewtopic.php?t=55


If you have a problem or find a bug, please be VERY descriptive in your problem report to me..

 

Just a question Jack. I think you are still using the TXS wideband correct? Will you ever implement this into your logger. I know it's not the most common wideband out there like the ZT-2 or LC, LM-1. But it would be nice.

 

Yep.. It will be the first wideband I support.. second will likely be the PLX devices ones.. both of them get no love..

Someone let me know if the program works.. I have very limited testing on my own car.

 

No problem what so ever. have 3 logs and they all work perfect. i'm having issues importing them into dataloglab

 

What error are you getting in data log lab?? I imported mine fine..

 

it is saying that it does not have a time refrance

 

You probably need an updated mitsulogger.txt file..

Unfortunately there was errors made early on with the definition file.. I fixed mine but may not have redistributed the fixed version..

Basically each data entry needs to be unique.. Since this is the one that works on my DLL with the new logs, it should work for you.

 

Oh, and if you opened your files in Excel before loading it into data log lab.. Make sure you didnt save it.. It reformats the date which may cause problems..

 

Oops.. I was just able to reproduce it.. The data is correct, but I think there may be an invalid character embedded somewhere..

 

Okay, I tried it out just now in my '03 EVO8. The program runs fine and starts taking data quickly enough. Some functions seem to work perfectly (such as RPM and Coolant Temp), but others seem to have major calculation errors (maybe they just haven't been set up yet?), or glitch out intermittently. You asked for details, so here are some examples:

- Load calc jumps from 35% to 11870000% and back to 35.
- On the same sample line (sample 16), many other values seem to jump too. RPM holds steady while TPS goes 14.9-->50.32-->14.9. Gear calc just shows a blank.
- Gear calc is always wrong: shows numbers like 11870000.
- Some rows show "XXX" for Load and Gear.
- On my same laptop, the sample rate is slightly slower than EvoScan. Not major.. just a tad.

I've attached my log for your reference.

What's the difference between "ECU Load" and "Load"? They're close, but different.

BTW, showing that disabled "Map Tracing" checkbox is just plain cruel! ;^)

 

ECULoad is clipped just like the MAF frequency..

The calculations can be changed, the gear calc got left in there, its in the XML File if you want to see what I did to get that.. It was actually just a test, I was going to replace it with a calculation, I think its just dividing speed into RPM at this point.. Just something to see if the variables worked.

The sample rate is locked at 10 lines per second.. Anything faster and it drops data, probably still dropping data on slower laptops..

Load calc I have no idea why its jumping, probably the data itself is somehow wrong..

Some of the calculations may be wrong.. again if you look at the XML file and find anything that stands out, you can let me know..

I have noticed that sometimes the ECU doesn't respond with data.. And causes some stuff to jump around..

I am more concerned about the log files not loading in data log lab.. but I was able to reproduce that..

 

I'm still getting the sample rate dialed in.. I think the rate may still be too high and its dropping characters occasionally.. If you disable a few of the lineitems and the glitching goes away, then its definitely the sample rate is too high.

 

Ahh, I see it looks like its occasionally dropping column data.. I'll have to figure out how to work around that.. I think if it responds with invalid or no data, I'll use the previous value instead..

It looks like you have to compromize the amount of samples your taking to get all the lines to work right...

 

Yeah, formulas are easy enough to fix, but I'm more concerned with the data jumping around.

Actually, now that I look at it, I see what's happening. It's missing a value and shifting all the remaining values in that sample left by one column. For example, look at sample #16 (row 18 if viewed in Excel). O2 Sensor shows 14.9, which is actually Battery voltage. Battery voltage shows 50.32, which is actually Airflow. Etc., etc. Everything from approx. column "N" through "AB" is shifted (it's hard to tell exactly which the first column is that shifted, as the numbers are all around 0 or 1 in that area).

 

If you look at sample 1033, you can see that from there to the end of the file, coolant temp is never recorded and all columns to the right of column 'F' are shifted over.

The "XXX" values are odd too.