MPS_UTEClogger 2.3

Reply Subscribe

Thread Tools

Search this Thread

Aug 5, 2005 | 03:50 PM

#16

Widebandphillip

Evolved Member

iTrader: (1)

Joined: Oct 2004

Posts: 714

Likes: 0

From: Houston, TX

I think the uteclogger is awesome. It works well with wrxs and stis. I'll try it on the evo soon and report back.

Aug 7, 2005 | 10:44 AM

#17

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Let me know if all of you are having the same logging problems or if anyone has had success yet.

I'm baffled why the Evo logging won't work when it is almost identical to the STi parsing. The only difference between the 2 log types is that the STi uses MAF volts while the Evo uses MAF Hertz. The colums are the same though.

Also, if there IS a problem, I need to see some recorded logs of what it is doing, that may help me pinpoint where the problem is... I havn't received any problem logs to examine yet.

-jason

Aug 7, 2005 | 06:39 PM

#18

dryad001

Evolved Member

iTrader: (27)

Joined: Nov 2003

Posts: 2,123

Likes: 1

From: Oak Creek, WI

My logs look fine, the only thing I had a problem with is the "dashboard". Also, is there any way to use the mapper with old logs? I know it says "current" or "real-time" but this would be an awsome tool to have also. I'm not sure if you have ever looked at the UCC but it kinda does what I'm asking but in a very detuned sort of way. I know that your logmapper is just an average but if i can implement that some way to create a timing map better than the one I have now i will fly to CA and give you a huge hug. Sounds like a pretty good deal hey?

Aug 7, 2005 | 07:41 PM

#19

EVO8LTW

EvoM Guru

iTrader: (41)

Joined: Jul 2004

Posts: 4,606

Likes: 98

From: Northern Virginia

Can't wait to try this since I have a UTEC and LM-1 but no Tuner.

Aug 8, 2005 | 09:15 AM

#20

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Quote:

My logs look fine, the only thing I had a problem with is the "dashboard".

So the timing was being shown as negative in the "dashboard" screen? But was correct on the LogMap screen? I'll see if I can hunt this down.

Quote:

Also, is there any way to use the mapper with old logs? I know it says "current" or "real-time" but this would be an awsome tool to have also.

Unfortunately no. However there IS an application out that does this. Check out the LogMapper at this link:
http://www.logmapper.com/

If you save out a log using MPS_UTECLogger, make sure you use "Make compliant Log" option for recording the log. You can use MPS_UTECLogger to see the 'realtime' Logmap. Once you loose the logmap in MPS_UTECLogger (by shutting down or clearing), you can try running the saved Log file through the stand-alone LogMapper 2.0 program. The stand-alone LogMapper 2.0 program will read logs off the hard-drive and plot them. I though that the LogMapper2.0 creator was trying to add evo compatibility too, but it may work anyway.

-jason

Aug 8, 2005 | 10:26 AM

#21

BJai02

Evolving Member

iTrader: (5)

Joined: Feb 2004

Posts: 354

Likes: 0

From: Bay Area

Quote:

Originally Posted by jmussetter

Unfortunately no. However there IS an application out that does this. Check out the LogMapper at this link:
http://www.logmapper.com/

Or simply use a screen capture program for it

Aug 8, 2005 | 10:59 AM

#22

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Quote:

Or simply use a screen capture program for it

That would be even easier, yes.

1) Size window to display all information needed...
2) Press <Alt>+<printscreen>
3) Open Photoshop/Word/Excel/WordPad
4) Pres <Ctrl>+V to paste screencapture into document
5) Save

However the stand-alone LogMapper2.0 by Jason Gambler is a very nice program, and has some extra features to it that make it more helpful than just a screen capture graphic.

-jason

Aug 8, 2005 | 01:31 PM

#23

sgplancer

Thread Starter

Evolving Member

iTrader: (25)

Joined: Jan 2004

Posts: 358

Likes: 1

From: Houston, TX

Quote:

Originally Posted by jmussetter

Unfortunately no. However there IS an application out that does this. Check out the LogMapper at this link:
http://www.logmapper.com/

Jason, Jonathan here from Innovene, this is an excellent tool, but could you please send me, e-mail or post here, a log of yours that works with this type of log mapper?

I am trying to run this with an evo log, but I am unable to map the log. I would be curious to see what an sti/wrx log looks like in relation to an evo log. Thanks.

Aug 9, 2005 | 12:02 PM

#24

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Quote:

I am trying to run this with an evo log, but I am unable to map the log. I would be curious to see what an sti/wrx log looks like in relation to an evo log. Thanks.

I too tried running an Evo log through it and it didn't work on version 2.0 (release). However, on version 2.0 (beta4) there are options to manually pick which log type to use (WRX, WRX+Tuner, Sti, Sti+Tuner). If I selected Sti or Sti+Tuner manually, then it processed the Evo log perfect without any problems. I think the "log type autodetect" in 2.0(release) can't identify the Evo logs. See if you can download the (beta4) version, or contact Jason Gambler (author or LogMapper2.0) to see if he can add the log type select back into the program.

To answer the second part of your question:

The Evo logs are IDENTICAL to the STi logs with the exception that the MAF column on the Sti reads volts (ie: 1.0-5.0v) while the Evo reads Hertz. The column format is the same though.

The WRX logs on the other hand are different in there is an extra column between the "Knock" column and the "Ign #1" column that reads the stock O2 sensor AFR (12.0-21.0). For some reason, TurboXS removed this column when they made the STi and Evo UTEC's. This inconsistency with column format on TXS part has been a headache for us programmers trying to get software to work with all types of log files.

Work Around:

The MPS_UTECLogger program has an option that is ON by default, called "Make compliant UTEC Log". If this option is selected, then no matter what type of UTEC you are using (WRX, Sti, or Evo), the log format is "forced" to be compliant with a plain jane original WRX log. (ie: adds the AFR column that the WRX has instead of adding the AFR data to the end like the Tuner does). This might seem weird for anyone without a WRX UTEC, however, because this was the ORIGINAL UTEC format, there are more 3rd party programs out there that support this format. That option is on there for this specific purpose, so that the resulting logs are compatible with as many other 3rd party programs as possible.

So, if you record a log in MPS_UTECLogger with the "compliant UTEC log" option ON, you will end up with a log that is IDENTICAL to a WRX log. You then should be able to run it through Jason Gambler's LogMapper2.0 program and it *should* recognize it.

-jason

Aug 9, 2005 | 12:10 PM

#25

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Here is a sample of a "compliant UTEC log" output from using MPS_UTECLogger...

Notice the EXTRA AFR column between "Knock" and "Ign#1"... On a WRX log, this read the stock O2 sensor. When MPS_UTECLogger logs to a compliant log, this column no longer shows the stock O2 sensor reading, but instead the wideband O2 readings (so they are accurate). The output will look like this reguardless of what type of UTEC is being used if the log is being forced to be "compliant".

Code:

 2839, -7.3,2.2,  9, 00,   00,  14.6,+37.6,   7.6,ECU. , -1.6,ECU.  ,2.0
 2834, -7.5,2.2,  9, 00,   00,  14.4,+36.5,   8.1,ECU. , -1.6,ECU.  ,2.0
 2841, -7.9,2.2,  9, 00,   00,  14.3,+37.0,   7.2,ECU. , -1.6,ECU.  ,2.0
 2836, -8.1,2.2,  9, 00,   00,  14.4,+36.9,   7.3,ECU. , -1.6,ECU.  ,2.0
 2812, -8.1,2.2, 10, 00,   00,  14.6,+37.7,   7.4,ECU. , -1.6,ECU.  ,2.0
 2822, -8.1,2.2, 10, 00,   00,  14.6,+38.4,   9.2,ECU. , -1.6,ECU.  ,2.0
 2803, -7.7,2.2, 10, 00,   00,  14.4,+38.0,   7.1,ECU. , -1.6,ECU.  ,2.0
 2812, -7.5,2.2, 10, 00,   00,  14.6,+38.0,   7.5,ECU. , -1.6,ECU.  ,2.0
 2836, -7.5,2.3, 11, 00,   00,  14.8,+39.8,   8.9,ECU. , -1.6,ECU.  ,2.1
 2803, -7.3,2.3, 12, 00,   00,  14.4,+40.5,   8.4,ECU. , -1.6,ECU.  ,2.2
 2832, -6.9,2.4, 13, 00,   00,  15.0,+39.5,   9.9,ECU. , -1.6,ECU.  ,2.2
 2832, -6.5,2.5, 14, 00,   00,  14.4,+38.4,   9.6,ECU. , -1.6,ECU.  ,2.2
 2810, -5.7,2.5, 15, 00,   00,  14.4,+35.5,  10.8,ECU. , -1.6,ECU.  ,2.3
 2827, -5.1,2.6, 17, 00,   00,  14.5,+34.7,  11.0,ECU. , -1.6,ECU.  ,2.3
 2839, -4.3,2.6, 20, 10,   00,  14.4,+33.7,  12.1,+36.4, -4.3,ECU.  ,2.3
 2846, -3.4,2.7, 20, 10,   00,  14.6,+34.2,  12.7,+36.3, -4.4,ECU.  ,2.3
 2861, -2.8,2.7, 20, 10,   00,  14.6,+34.1,  12.5,+36.3, -4.3,ECU.  ,2.4
 2853, -2.2,2.7, 20, 10,   00,  14.6,+34.1,  12.7,+36.4, -4.4,ECU.  ,2.4
 2886, -1.6,2.7, 20, 10,   00,  15.0,+33.4,  13.5,+36.5, -4.4,ECU.  ,2.4
 2873, -1.6,2.7, 19, 00,   00,  13.8,+33.2,  13.2,ECU. , -1.6,ECU.  ,2.4
 2906, -1.6,2.7, 18, 00,   00,  13.7,+33.2,  14.2,ECU. , -1.6,ECU.  ,2.5
 2868, -1.4,2.7, 19, 00,   00,  13.9,+33.4,  12.2,ECU. , -1.6,ECU.  ,2.4
 2888, -1.6,2.7, 19, 00,   00,  14.5,+33.1,  12.1,ECU. , -1.6,ECU.  ,2.5
 2916, -1.6,2.7, 19, 00,   00,  14.5,+33.3,  12.2,ECU. , -1.6,ECU.  ,2.4
 2918, -1.6,2.7, 18, 00,   00,  14.6,+33.1,  14.1,ECU. , -1.6,ECU.  ,2.0
 3214, -3.4,1.3,  0, 00,   00,  13.1,+31.5,  23.3,ECU. , -1.6,ECU.  ,2.2
 3623, -4.0,2.1,  4, 00,   00,  12.0, +4.6,   4.2,ECU. , -1.5,ECU.  ,1.5
 3508, -6.1,2.2,  9, 00,   00,  13.9,+18.1,   7.2,ECU. , -1.5,ECU.  ,2.0
 3809, -7.7,2.6, 14, 00,   00,  16.5,+34.5,  11.8,ECU. , -1.5,ECU.  ,2.4
 3800, -7.1,2.8, 20, 10,   00,  14.8,+36.7,  17.3,+34.6, -4.9,ECU.  ,2.6
 3853, -6.3,3.1, 33, 10,   00,  14.7,+30.7,  21.2,+34.5, -5.0,ECU.  ,2.8
 3875, -3.4,3.3, 44, 10,   00,  14.1,+26.2,  26.4,+34.4, -5.3,ECU.  ,3.0
 3916, -0.4,3.5, 61, 20,   00,  13.7,+23.8,  30.7,+32.0, -6.4,ECU.  ,3.1
 3916, +3.3,3.7, 65, 40,   00,  13.5,+21.4,  42.6,+21.0, -2.7,ECU.  ,3.3
 4055, +7.0,3.9, 83, 60,   00,  11.5,+10.5,  58.4,+19.0, -1.0,ECU.  ,3.6
 4070,+10.6,4.0,102, 80,   00,  10.5, +8.8,  60.3,+18.0, -2.1,ECU.  ,3.6
 4208,+14.1,4.0,102, 90,   00,  10.9,+10.9,  56.6,+18.0, -3.1,ECU.  ,3.6
 4187,+16.6,4.1,102,100,   00,  10.8,+11.0,  60.3,+17.0, -2.3,ECU.  ,3.6
 4192,+17.6,4.0,102,100,   00,  10.9, +9.7,  58.9,+17.0, -2.6,ECU.  ,3.6
 4257,+18.0,4.1,102,100,   00,  11.0, +9.7,  62.4,+17.0, -3.0,ECU.  ,3.6
 4363,+17.6,4.1,102, 90,   00,  11.0,+10.8,  63.2,+18.5, -4.0,ECU.  ,3.6
 4340,+17.2,4.1,102, 90,   00,  10.9,+10.6,  63.0,+18.6, -4.2,ECU.  ,3.7
 4450,+16.8,4.1, 99, 90,   00,  10.9,+11.0,  62.1,+18.8, -4.3,ECU.  ,3.6
 4522,+16.1,4.1,102, 90,   00,  11.2,+11.7,  62.2,+19.2, -4.5,ECU.  ,3.6
 4655,+16.1,4.1,102, 80,   00,  11.1,+11.7,  64.1,+20.1, -4.9,ECU.  ,3.6
 4681,+16.6,4.2,102, 90,   00,  11.1,+11.2,  66.3,+19.6, -4.6,ECU.  ,3.6
 4688,+16.8,4.2,102,100,   00,  11.0,+11.2,  66.5,+19.0, -4.8,ECU.  ,3.7
 4701,+17.0,4.2,102, 90,   00,  11.0,+11.2,  67.2,+20.0, -5.1,ECU.  ,3.7
 4837,+17.6,4.2,102, 90,   00,  11.1,+11.9,  65.9,+20.3, -4.8,ECU.  ,3.7
 4901,+16.8,4.2,102, 90,   00,  11.0,+12.7,  68.6,+20.5, -4.9,ECU.  ,3.7
 4859,+16.6,4.2,101, 90,   00,  11.0,+13.1,  69.1,+20.9, -4.9,ECU.  ,3.7
 4909,+16.8,4.2,102, 90,   00,  10.9,+13.6,  68.5,+20.7, -5.2,ECU.  ,3.8

Hope that this explains a lot...

-jason

Aug 9, 2005 | 01:15 PM

#26

MalibuJack

EvoM Guru

iTrader: (5)

Joined: Feb 2003

Posts: 10,572

Likes: 14

From: Royse City, TX

It could be how your breaking up the columns.. the column widths are different slightly, there are elso embedded nulls in some of the columns at times... Are you parsing the data for the comma delimiter? or the specific spacing column number? I had to parse it to the delimiter and strip the spaces/nulls.. also I noticed the extra column in the middle for the OE O2 sensor reading...

Aug 9, 2005 | 04:18 PM

#27

jmussetter

Newbie

Joined: Aug 2005

Posts: 30

Likes: 0

From: BayArea, CA

Quote:

It could be how your breaking up the columns.. the column widths are different slightly

I (Jason Mussetter) created MPS_UTECLogger2.3, while Jason Gambler created LogMapper2.0. These are 2 programs from 2 people. I just want to clear any confusion so proper credit can be given where due.

Quote:

Are you parsing the data for the comma delimiter? or the specific spacing column number? I had to parse it to the delimiter and strip the spaces/nulls..

My program, MPS_UTECLogger, parses the data at the comma delimeters, and then strips the extra characters away from the data. This way column width to my program doesn't matter...

How LogMapper2.0 interprets the columns is beyond me.

-jason

Aug 11, 2005 | 07:47 AM

#28

dryad001

Evolved Member

iTrader: (27)

Joined: Nov 2003

Posts: 2,123

Likes: 1

From: Oak Creek, WI

Quote:

Originally Posted by jmussetter

So the timing was being shown as negative in the "dashboard" screen? But was correct on the LogMap screen? I'll see if I can hunt this down.

Unfortunately no. However there IS an application out that does this. Check out the LogMapper at this link:
http://www.logmapper.com/

If you save out a log using MPS_UTECLogger, make sure you use "Make compliant Log" option for recording the log. You can use MPS_UTECLogger to see the 'realtime' Logmap. Once you loose the logmap in MPS_UTECLogger (by shutting down or clearing), you can try running the saved Log file through the stand-alone LogMapper 2.0 program. The stand-alone LogMapper 2.0 program will read logs off the hard-drive and plot them. I though that the LogMapper2.0 creator was trying to add evo compatibility too, but it may work anyway.

-jason

I guess i should have been a little more clear on my typing here is whats going on. Dashboard- inj duty is always at 1.3%, timing reads in - , log mapper works great but the timing part will only read in -, logging screen reads everything perfect. If it wasnt raining here I would throw some screen shots up.

Aug 11, 2005 | 12:27 PM

#29

dryad001

Evolved Member

iTrader: (27)

Joined: Nov 2003

Posts: 2,123

Likes: 1

From: Oak Creek, WI

I just picked up the Innovate LC-1, on Jason's website it says his program accepts this WB. I can't wait for it to get here, I can finally get my tuning done with the WR and then head back to the dyno.

Aug 11, 2005 | 07:30 PM

#30

BJai02

Evolving Member

iTrader: (5)

Joined: Feb 2004

Posts: 354

Likes: 0

From: Bay Area

I've sent logs and screen shot to Jason for troubleshooting. He thinks he found the problem... the log mapper is looking at the ECU timing instead of the UTEC timing. He will fix this bug in his next release.

Once again, thanks to Jason for his hard work for the EVO community!!

Reply Share

First
Prev
2 / 8
Next
Last