MPS_UTECLogger v2.0 software is here! - calling all UTEC users!

[jmussetter]

It's here, Finally! What started out as a small simple upgrade to the previous version, has now grown into a larger undertaking as the entire program has transformed into something different, and something better... The best UTEC companion software around!

With v2.0, Now you can...

- Bridge your UTEC logs with Wideband AFR's from an LM-1, an LC-1, or an AEM wideband meter!

- Digital UTEC dashboard with eight (8) digital guages (plus knock warning) that can run full screen on your PC monitor!

- Integrated REAL-TIME LogMapper that maps averaged/total values for seven (7) UTEC readings, all on the fly, while you drive!

- Supports WRX and STi version UTEC

- Also Works stand-along with the UTEC if you don't have a Wideband O2 meter

Here is a link to the updated download page with screen shots and full description...
MPS_UTECLogger Download Page

Everyone enjoy!

-jason

* Registered users of the site do not see these ads.

[x99percent]

PayPal donation sent! I hope others follow suit.

[serendipity]

What if I have a TXS Tuna already? Will it pull the AFRs directly from my UTEC's logs? I'm interested in the logmapper and dashboard functionality.

[jmussetter]

What if I have a TXS Tuna already? Will it pull the AFRs directly from my UTEC's logs? I'm interested in the logmapper and dashboard functionality.

If you have the TXS Tuna already, then you have the cabability to log w/ AFR already through that. However, since the Tuna appends AFR to the end of the log, *in theory*, the program should record regular logfiles from the Tuner just fine...

The dashboard and the logmapper *should* still work also, however the AFR for both will read 0 as the program ignores the UTEC AFR since it assumes its from the stock O2 sensor. The rest of the Digital gauges and Logmapper should record just fine though, meaning you'll have access to RPM, Boost, TPS, MAP, MAF, Timing, IDC% and Knock.

Let us all know if the rest of the gauges and logmapper work with the Tuner connected, since I know the Tuner changes the normal UTEC log, I'm very interested to know if it works.

-jason

[serendipity]

Originally Posted by jmussetter

If you have the TXS Tuna already, then you have the cabability to log w/ AFR already through that. However, since the Tuna appends AFR to the end of the log, *in theory*, the program should record regular logfiles from the Tuner just fine...

The dashboard and the logmapper *should* still work also, however the AFR for both will read 0 as the program ignores the UTEC AFR since it assumes its from the stock O2 sensor. The rest of the Digital gauges and Logmapper should record just fine though, meaning you'll have access to RPM, Boost, TPS, MAP, MAF, Timing, IDC% and Knock.

Let us all know if the rest of the gauges and logmapper work with the Tuner connected, since I know the Tuner changes the normal UTEC log, I'm very interested to know if it works.

-jason

I'll give it a shot to see what happens. On the STi UTEC, there is no "UTEC AFR" column. If you add a Tuna, another column (W/B AFR) is appended to the end. So if your software ignores the front O2 AFR column and looks to the last column for an AFR (which it appends from an LM-1), it might work normally...

Thanks for sharing your work with us.

[AaronWRX]

Originally Posted by jmussetter

If you have the TXS Tuna already, then you have the cabability to log w/ AFR already through that. However, since the Tuna appends AFR to the end of the log, *in theory*, the program should record regular logfiles from the Tuner just fine...

The dashboard and the logmapper *should* still work also, however the AFR for both will read 0 as the program ignores the UTEC AFR since it assumes its from the stock O2 sensor. The rest of the Digital gauges and Logmapper should record just fine though, meaning you'll have access to RPM, Boost, TPS, MAP, MAF, Timing, IDC% and Knock.

Let us all know if the rest of the gauges and logmapper work with the Tuner connected, since I know the Tuner changes the normal UTEC log, I'm very interested to know if it works.

-jason

Same question as above. Here is a snip of STI Utec + Tuner logs:

	 DATA1

	,	 ,    ,   ,Load,Knock,	  ,	  , Mod,  Mod,	  , Mod,  WB 
 RPM,  MAP, MAF,TPS,Site,Count, Ign#1, Inj#1, Ign,  Fuel,Boost, MAF,  AFR
	,  psia, V , % ,    ,	 ,  deg , duty , deg,   %  ,(CL) ,  V ,
  746,-11.6,1.2,  2, 00,   00,  +17.0,   1.3,ECU. , +0.0,ECU.  ,1.2, 14.78
  750,-11.6,1.2,  2, 00,   00,  +17.0,   1.5,ECU. , +0.0,ECU.  ,1.2, 14.78
  740,-11.6,1.2,  2, 00,   00,  +17.5,   1.2,ECU. , +0.0,ECU.  ,1.2, 14.74
 1355,-11.6,1.4,  2, 00,   00,  +18.9,   5.0,ECU. , +0.0,ECU.  ,1.4, 20.28
 1143,-11.6,1.3,  2, 00,   00,  +17.8,   5.0,ECU. , +0.0,ECU.  ,1.3, 22.62
  929,-11.6,1.3,  2, 00,   00,  +23.9,   0.0,ECU. , +0.0,ECU.  ,1.4, >25:1
  858,-11.4,1.4,  2, 00,   00,  +23.4,   1.9,ECU. , +0.0,ECU.  ,1.3, >25:1
 1011,-11.2,1.3,  2, 00,   00,  +13.8,   2.0,ECU. , +0.0,ECU.  ,1.3, >25:1
 1050,-11.0,1.3,  2, 00,   00,  +11.2,   1.7,ECU. , +0.0,ECU.  ,1.2, >25:1
 1018,-11.2,1.2,  2, 00,   00,  +11.8,   2.1,ECU. , +0.0,ECU.  ,1.2, >25:1
 1008,-11.2,1.7, 11, 00,   00,  +18.0,   4.5,ECU. , +0.0,ECU.  ,1.7, >25:1
 1353,-10.8,1.8, 12, 00,   00,  +25.4,   4.1,ECU. , +0.0,ECU.  ,1.8, >25:1
 1838,-10.2,1.9, 13, 00,   00,  +19.6,   4.3,ECU. , +0.0,ECU.  ,1.9, >25:1
 2568, -9.4,2.2, 16, 00,   00,  +29.8,   9.9,ECU. , +0.0,ECU.  ,2.2, 16.11
 2434, -8.5,2.2, 16, 00,   00,  +45.7,   9.0,ECU. , +0.0,ECU.  ,2.2, 14.42
 1955,-12.0,1.6, 11, 00,   00,  +27.8,  82.7,ECU. , +0.0,ECU.  ,1.7, 19.16
 2287,-11.4,2.2, 17, 00,   00,  +25.7,   8.1,ECU. , +0.0,ECU.  ,2.3, 20.53
 2161,-10.0,2.3, 19, 00,   00,  +41.0,   9.5,ECU. , +0.0,ECU.  ,2.3, 22.62
 2177, -7.5,2.7, 61, 10,   00,  +26.7,  16.4,+24.0, +4.8,375.00,2.8, 17.53
 2287, -4.7,2.7,104, 10,   00,  +19.5,  17.3,+23.8, +4.9,375.00,2.9, 13.47
 2290, -1.8,2.8,105, 10,   00,  +17.5,  19.2,+23.4, +4.9,375.00,3.0, 12.86
 2355, +0.4,2.9,105, 10,   00,  +14.8,  21.7,+17.8, +4.9,375.00,3.0, 12.99
 2456, +1.9,2.9,106, 20,   00,  +12.9,  23.5,+16.9, +4.9,375.00,3.2, 12.74
 2525, +3.1,3.1,105, 20,   00,  +11.2,  26.2,+16.0, +3.2,375.00,3.2, 12.49
 2583, +4.5,3.1,105, 40,   00,  +10.3,  30.0,+16.0, +4.9,375.00,3.3, 12.59
 2651, +5.9,3.3,106, 40,   00,   +9.6,  33.2,+16.0, +3.6,375.00,3.5, 12.45
 2738, +8.0,3.5,105, 60,   00,   +9.6,  39.8,+15.0, +3.4,375.00,3.6, 12.25
 2876, +9.8,3.5,105, 70,   00,   +9.2,  44.5,+14.0, +4.0,375.00,3.7, 12.25
 2981,+11.9,3.6,105, 80,   00,   +9.2,  51.3,+13.0, +4.5,375.00,4.0, 12.05
 3046,+13.7,3.5,104, 80,   00,   +8.9,  57.3,+13.0, +4.5,375.00,4.0, 11.80
 3168,+14.9,3.6,106, 80,   00,   +9.2,  46.5,+13.0, +4.5,375.00,4.0, 11.48
 3343,+15.7,3.7,105, 80,   00,   +9.1,  59.0,+13.4, +3.9,375.00,4.1, 11.14
 3390,+15.9,3.9,105, 90,   00,   +9.2,  52.0,+13.4, +3.8,375.00,4.0, 10.93
 3523,+16.4,4.0,105, 90,   00,   +9.1,  62.8,+13.5, +3.4,375.00,4.0, 10.78

[scrat]

Originally Posted by x99percent

PayPal donation sent! I hope others follow suit.

Mine is out as well. Thanks again, Jason!

[serendipity]

I tried to install it on my carpc, but had no joy The first time, it said I had some system files that were out of date, so I cliked "OK" to update them, then restarted. Ran setup again, and got the same message

It's a Windows 2000 PC running the latest service pack. Don't think I've updated the VB runtimes (is that what your program uses? It didn't say what system files were out of date). Any hints?

[jmussetter]

I tried to install it on my carpc, but had no joy The first time, it said I had some system files that were out of date, so I cliked "OK" to update them, then restarted. Ran setup again, and got the same message

When I installed on my XP Pro desktop, I got the same message during setup, I told it to use the newest versions of files, and when the install finishes the program works fine. I don't have a Win2000 PC to test on though, and I know that Win2000 in notorious for giving headache to many compatibility problems with both hardware and sofware.

Just to note, I have it running on 2 XP Pro machines ("homebrewed" desktop and a toshiba laptop), and Mark did beta testing on a Win 98 laptop I believe.

Is the setup program crashing after this message? (mine continued after selecting which files to keep) Does the program get installed on the computer at all? Did you try running the program (from "Start:Program Files:MPS_Software:MPS_UTECLogger.exe")after the install? If it crashes, does it just freeze, or give a run-time error? What point in the program or startup does it crash if it is crashing?

Sorry for so many questions, but I want to help, and all this can help to point to where the problem lies...

It's a Windows 2000 PC running the latest service pack. Don't think I've updated the VB runtimes (is that what your program uses? It didn't say what system files were out of date). Any hints?

Yes, the program was written in VB6.0. All needed files should be included in the setup .cab file.

-jason

[serendipity]

Originally Posted by jmussetter

When I installed on my XP Pro desktop, I got the same message during setup, I told it to use the newest versions of files, and when the install finishes the program works fine. I don't have a Win2000 PC to test on though, and I know that Win2000 in notorious for giving headache to many compatibility problems with both hardware and sofware.

Just to note, I have it running on 2 XP Pro machines ("homebrewed" desktop and a toshiba laptop), and Mark did beta testing on a Win 98 laptop I believe.

Is the setup program crashing after this message? (mine continued after selecting which files to keep) Does the program get installed on the computer at all? Did you try running the program (from "Start:Program Files:MPS_Software:MPS_UTECLogger.exe")after the install? If it crashes, does it just freeze, or give a run-time error? What point in the program or startup does it crash if it is crashing?

Sorry for so many questions, but I want to help, and all this can help to point to where the problem lies...

Yes, the program was written in VB6.0. All needed files should be included in the setup .cab file.

-jason

Sorry - should have given more details. The second time around, it just did exactly the same thing as the first. Same message, clicked ok, wanted to restart, but apparently the files didn't get updated. No crashes, but nothing was installed. I'll just manually update the VB runtimes and give it another shot

[jmussetter]

The second time around, it just did exactly the same thing as the first. Same message, clicked ok, wanted to restart, but apparently the files didn't get updated. No crashes, but nothing was installed.

Did you have any luck getting it to work. I've done some research and my suspicions about win2k were right. Appearantly, according to some VB forums, this is a common issue installing applications created with "MS Package & Deployment Wizard" on Win2000 computers specifically. However, I am still searching the MSDN for workarounds/fixes. I would like everyone, reguarless of operating system to be able to use this program, so I will continue to do some research.

In the meantime, you *may* be able to manually extract the .CAB file, and then copy all the files to the location of your liking. You can try running the app and see if it works then...

If it still give you errors, you will need to look at the *.ocx and *.dll files and copy any of the files you DON'T already have to your C:\windows\system32\ directory. You will then manually register the new files. This is a BIG pain though, so I'm hoping to find a solution...

-jason

[steve]

I'm at attempt #2 to install the program, and it doesn't look good.
The computer is a 2000 Sony Vaio, running XP Pro. It keeps telling me that the files on my computer are too old, and it will install them for me when I reboot. After reboot, nothing happens.

[AaronWRX]

it doesnt log right or display AFR's with the sti utec + tuner

seems like it would be an easy thing to fix. Just give the user a configuration option for sti utec + tuner or wrx utec + tuner since each combo logs differently.

[jmussetter]

it doesnt log right or display AFR's with the sti utec + tuner

It won't display AFR's. Unfortuneately, the program doesn't "parses" the AFR from a UTEC log line in it's current form. So for now, unless you use 2 com ports, AFR is not reported. I would need to change the UTEC parsing engine to include extracting and interpretating of the AFR ratio from the UTEC. This may be do-able in the next release. Since the program's main focus in the beginning was to be a "bridge", it doesn't have any means built into right now to get both the UTEC data and the WBO2 data from the same source.

You mention that it won't log correctly...what does the log look like, and how is it messed up? Just to note, the logger output for the Sti will have an extra column added to it for AFR where the normal UTEC log has it. In other words, it tries to convert an STi formatted log into a WRX formatted log so that it can parse and process both types of logs identically. The extra column that it adds doesn't do any harm, but may *look* different since it's not normally there. I'll look at the code for the Sti parsing and see if there is anything obviously wrong in there. Can you post a 'snipit' of a munched up log so I can see what's wrong? If it is messed up, I would like to fix it.

I *could* get an update out pretty fast, IF it was acceptable to have the program treat the tuner as a 3rd party WB. In other words, you'd have to connect the Tuner and the UTEC seperately to the laptop instead of linking them... This would be the fastest, easiest way of providing support to the Tuner users. It may *seem* like a pain to you Tuner users out there, but everyone else with a third party WB meter have to do it too... Would this solution be acceptable to the Tuner community? If so, I would need to know what the tuner outputs while stand-alone without the UTEC connected to it...can anyone with a Tuner help me with that info?

Comments/questions?

-jason

[jmussetter]

Tuner Users:
I implemented support for the TurboXS Tuner wide-band meter...however it may be different than some of you expected.

The next update (v2.1) will support the Tuner as a "stand-alone" WideBand. In other words, to get it to work with UTECLogger, you will need to connect it seperately from the UTEC on the WideBand meter Com Port.

The reason for this is 2 fold. First, the core engine of the program was designed as a bridge, meaning that AFR data ONLY is interpreted on the second Com port seperate from the UTEC. Because the Tuner alters the UTEC output prior to UTECLogger intercepting it, major modifications would be needed to support a UTEC+Tuner daisy chain configuration that the core program engine just doesn't support.

The second reason for implementing support in this way, is to keep compatibility with different widebands with different ECU's. As UTECLogger evolves, the support for other aftermarket ECU's may grow beyond just the UTEC (possibly AEM or Hydra, I dunno...). If this is the case, supporting the TurboXS tuner as a stand-alone meter will allow for the use of this option with other ECU's beyond just the UTEC.

I'm trying to make as many people as happy as possible and this seems to me to be the best solution (while some current Tuner owners may disagree) to be able to support the TurboXS tuner instead of alienating it's owners.

I want to hear about and current problems with v2.0 before I release the new update though, so that I can make the new version a little more stable. Please give feedback with bugs.

For those of you who are having installation problems, it seems to be a known problem to Microsoft using VB Package and Deployment wizard. I'm still looking for a sure bet fix which I have not found so far... other than trying to "manually install" the files by copying them from the .CAB file by hand.

-jason

[jmussetter]

Version 2.1 is available for download. TurboXS Tuner support has been added as another wideband O2 meter option. I hope some of you Tuner users can try it out and let me know if it works...

AaronWRX: If you connect your UTEC and Tuner to the new version (on seperate com ports!), the software *should* be able to interpret your STi UTEC and Tuner correctly. The Sti logs will look identical to regular WRX logs after the program processes and saves them. If you use other 3rd party log mappers with UTECLogger logs, have the log mapper interpret it as a WRX log instead of an STi log...

-jason

[gadget951]

Originally Posted by jmussetter

For those of you who are having installation problems, it seems to be a known problem to Microsoft using VB Package and Deployment wizard. I'm still looking for a sure bet fix which I have not found so far... other than trying to "manually install" the files by copying them from the .CAB file by hand.

-jason

Any update on the installation problem with a easier work around, patch or fix?

[Tap]

Originally Posted by jmussetter

Version 2.1 is available for download. TurboXS Tuner support has been added as another wideband O2 meter option. I hope some of you Tuner users can try it out and let me know if it works...

AaronWRX: If you connect your UTEC and Tuner to the new version (on seperate com ports!), the software *should* be able to interpret your STi UTEC and Tuner correctly. The Sti logs will look identical to regular WRX logs after the program processes and saves them. If you use other 3rd party log mappers with UTECLogger logs, have the log mapper interpret it as a WRX log instead of an STi log...

-jason

I cannot get it to work. I can telnet into Tuner and UTEC at the same time using seperate ports (the Tuner and UTEC not conneted) but the W/B does not showup on your logger and no error are displayed (like when you pick the wrong or same port).

[cornpops]

Can you make this work with the evos aswell? pretty please= ) Btw, i love your innovative thinking.

[gadget951]

Bump

[rewt]

any plan to support other WBO2 controllers like the zeitronix zt-2?

[GMTarkin]

How about a feature to monitor the narrowband? for those of us that don't have wideband. Like if you disabled the WB O2, then it would read from the narrowband.

Very nice program though, I've been waiting for something clean, with big letter to show me what's going on

[jmussetter]

Any update on the installation problem with a easier work around, patch or fix?

Unfortunately not as of yet. Like I said, it apprears to be a problem with Microsoft's Package and Deployment program that creates the install packages. The only workaround that I've found so far, would be for me to use a different 3rd party deployment option to create the install packages, such as the popular "InstallShield" (which isn't free!). There are a couple of "free" options for 3rd party deployment programs, but I havn't had a chance to look into them yet, and I'm not 100% sure that they will fix this issue in all instances.

Is anyone having any luck by doing the manual install that I was mentioning earlier? I know it's a pain in the *ss, but I'm sure some of you out there may have tried it. I want to know if manually extracting the files and copying/registering them is working for people?

-jason

[jmussetter]

Can you make this work with the evos aswell? pretty please= )

This shouldn't be too hard... how is the evo UTEC output different from say the STi or WRX output. I figured it would be identical to the STi output, but I may be wrong. Can you send me some sample Evo logs from the Logger #1 (without a Tuner or DTEC connected to the UTEC). This would be the log created with (Shift+1) from the main menu. If I have examples of what I'm working with, it makes it easier for me to add features.

any plan to support other WBO2 controllers like the zeitronix zt-2?

Yes, actually the TechEdge WB2.0 is next on the list as it is already partially completed. Others could be added in the future as well, however I havn't been able to find the zeitronix protocol manual on their website. If anyone has a copy of it so I can plan development could they email a copy. Otherwise, I may have to contact Zeitronix and have them send it to me (a pain).

How about a feature to monitor the narrowband?

I've thought about this, however, the Sti UTEC doesn't even output the narrowband info, and I don't think the Evo UTEC does either. So this would make the program rather inconsistent in operation between ECU types. After going through the beinfits, I concluded that TurboXS has removed the narrowband AFR from the Sti UTEC for a good reason. And after doing much of my own logging and tuning, I tend to agree, that the stock narrowband is not even consistent enough to be used as a 'rough' guideline.

-jason

[jmussetter]

I cannot get it to work. I can telnet into Tuner and UTEC at the same time using seperate ports (the Tuner and UTEC not conneted) but the W/B does not showup on your logger and no error are displayed (like when you pick the wrong or same port).

Is the UTEC portion of the log displaying in the "Current UTEC Log line" window? How about the other guages in the guages window? If the UTEC stuff is working, and just the Tuner isn't displaying, maybe the data from the Tuner is different than what the manual is saying?

Someone correct me if I'm wrong...I've never used a tuner in person...but I believe the following to be true about using the tuner in terminal:
1) Tuner com port settings are 19200,None,8,1
2) To get the tuner into Logger#1, a "<shift>+1" is used...(just like the UTEC)
3) The output from the Logger#1 consists of comma delimited log lines, with RPM as the first column, and the AFR as the second column, and the auxillary inputs after this.

Tuner users, help me out here. Maybe someone can email me or post a log of what the tuner outputs in STANDALONE when using logger#1. I can correct any parsing problems easily if I have examples of the output.

-jason