MPS_UTEClogger 2.3
Sorry I havn't been around in awhile...
No I havn't heard of this one.
Adding more WB types to the expanding list is an ongoing quest. I must tell you, though, that the TechEdge and Zeitronic's brands are already on the list to do, and have been long in the waiting mostly because of the amount of time required to add and test new WB types. But others will follow...
BTW, look for new ver. 2.5 on the download page within the next day or two hopefully...I'm testing it now.
-jason
have you dealt with the PLX loggers yet?
Adding more WB types to the expanding list is an ongoing quest. I must tell you, though, that the TechEdge and Zeitronic's brands are already on the list to do, and have been long in the waiting mostly because of the amount of time required to add and test new WB types. But others will follow...
BTW, look for new ver. 2.5 on the download page within the next day or two hopefully...I'm testing it now.
-jason
Keep in mind that this is a donation-driven project for Jason, so if you want to give him some incentive to continue development, hit up his site and make a Paypal donation at the bottom of the page.
MPS_UTECLogger v.2.5 is now avail on the web.
New features include:
- Hotkeys for starting and stopping logs.
- Automatic logname generation to eliminate typing while driving...
- Audible knock warning!
- Time/Date stamps and comment stamp embedded to saved LogMaps.
- More Com Ports to select from.
- minor bug fixes...
-jason
New features include:
- Hotkeys for starting and stopping logs.
- Automatic logname generation to eliminate typing while driving...
- Audible knock warning!
- Time/Date stamps and comment stamp embedded to saved LogMaps.
- More Com Ports to select from.
- minor bug fixes...
-jason
I don't have any of the supported O2 reading devices. I have the Zeitronix unit, it uses a Bosch wideband sensor. Is there a possibility than one of the supported devices will work with the Zt-2? I wouldn't mind trying it out so long as their won't be any sort of damage caused.
BTW, I was messing with the 2.5 version of the software testing the auto naming and one button start/stop logging features and noticed the file extension is wrong. It looks like they are comma separated value (.csv) files but the auto name feature is attaching a .cvs extension. Other than that everything looks good. Keep up the good work.
BTW, I was messing with the 2.5 version of the software testing the auto naming and one button start/stop logging features and noticed the file extension is wrong. It looks like they are comma separated value (.csv) files but the auto name feature is attaching a .cvs extension. Other than that everything looks good. Keep up the good work.
Last edited by alfredob1; Oct 22, 2005 at 09:25 AM.
In terms of format, I think it would be nice to add a column logging what ignition timing the stock ECU wants to run. It would help looking for possible knocks that the stock ECU detected and the UTEC didn't. A good tuning tool for ignition tuning and knock sensor sensitivity adjustment.
Bump for anything new? I felt like I got screwed fore buying the PLX wideband, cause it is such a pain to have to try and compare the log on the PLX unit with tps and rpms and then look at the UTEC log in order to tune.
Originally Posted by Nez136
So i just was reading a post where a dude said he can read lower than 11.0 on the AEM, i can't with this software, is this true or are they full of ****?
Originally Posted by BJai02
It has nothing to do with this software. I know it displays lower than 11.0 with my LM-1 and this software.
Everything in their manual indicates that the AEM guage only reads down to 11.0:1 and no lower.
However, I don't own and AEM and couldn't confirm this when I added this to the program. If you can connect to the AEM from HyperTerm and log AFR's lower than 11:1, then let me know and I will fix the issue in the logging program.
-jason
However, I don't own and AEM and couldn't confirm this when I added this to the program. If you can connect to the AEM from HyperTerm and log AFR's lower than 11:1, then let me know and I will fix the issue in the logging program.
-jason



