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! :p

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 (http://mpsav.com/MPSUTECLogger/MPS_UTECLogger_Download.htm)

Everyone enjoy!

-jason

PayPal donation sent! I hope others follow suit. :)

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.

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

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. :)

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

PayPal donation sent! I hope others follow suit. :)

Mine is out as well. Thanks again, Jason!

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? :)

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

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 :)

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

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.

:(

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.

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

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

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

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?

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).

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

Bump :banana:

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

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 :)

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

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

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

logs sent jmussetter, let me know if you need anything else =)

Feature idea... ability to choose > and < high and low values and coordinate them with colors, so you could set it if AFR is greater than 16:1 then the text is colored to whatever you choose, lets say red. and then if it dropped below 12:1 it would go, lets say we choose... Blue.

And allow you to map colors and ranges to all the gauges.

One more idea, a big "Open Loop/Closed Loop" fueling indicator.

logs sent jmussetter, let me know if you need anything else =) I havn't seen any logs (or message from you) come in through email or PM... :confused: Can you please try sending them again, the best place to send stuff like this is... UTECLogger@mpsav.com (mailto:UTECLogger@mpsav.com)

One more idea, a big "Open Loop/Closed Loop" fueling indicator. This should be an easy one...but...How is open/closed loop determined from the UTEC log? Would it be based off whether the Load column was 0 (closed loop) or >0 (open loop)? I don't know if this would indicate whether the stock ECU is in open/closed loop though or just if the UTEC is in control. I know the UTEC dashboard shows this info, but I can't access that along with logging.

-jason

i sent them all to logmapper@yahoo.com. I resent them all to uteclogger@mpsav.com. Let me know if you need anything else.

i sent them all to logmapper@yahoo.com. Um, yeah, that's not my email address...

-jason

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
DATA1

RPM,AFR ,Lambda,Ana 1,Ana 2,D1 St,D1 Freq,D1 Duty,D2 St,D2 Freq,D2 Duty,Knock
,Gas , , , , , Hz, %, , Hz, %, time
0, 14.83, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.6, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.87, 1.01, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.87, 1.01, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.8, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -13.8, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.78, 1.00, -14.8, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.74, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.9, -14.9, L, 0, 50, L, 0, 50, 0
0, 14.83, 1.00, -14.8, -14.9, L, 0, 50, L, 0, 50, 0

The UTEC log line is displayed and shows 0 where the w/b reading would be if connected to the TUNER, the com port settings you list are correct.

Is anyone having any luck by doing the manual install that I was mentioning earlier? I want to know if manually extracting the files and copying/registering them is working for people?

-jason

I was able to do this with my desktop(xp) but I don't know how to register the files on my laptop that is running ME . Can any one help me in how to register the needed files with MS ME?

I was running the setup on 98 and had a slight delay because it says some files were too old and to hit ok to restart and get newer files. After i restarted, i tried setup again and it works this time.

P.S. Sorry about the confusion Jason. I just sent a reply to the email you sent me and the email of logmapper@yahoo.com was the address.

How long can we expect to wait for the next version with techedge support? I borrowed my friends techedge and would love to use this logger with it.

How long can we expect to wait for the next version with techedge support? To be honest, probably 2-4 weeks at this point unfortunately. I have a couple of big (paying) programming projects I need to take care of in the next few weeks that will be taking up most of my time. When I'm finished with these, I will hopefully have the time to complete the next set of features. At this point, I am also trying to get feedback on the last set of new features. If I have to fix any bugs, I would like the fixes to be on the next release also.

-jason

At this point, I am also trying to get feedback on the last set of new features. If I have to fix any bugs, I would like the fixes to be on the next release also.

-jason

FYI...Ver 2.0 is crashing my lap top about 50% of the time. It seems to happen when I go to close the program.

I was able to do this with my desktop(xp) but I don't know how to register the files on my laptop that is running ME . Can any one help me in how to register the needed files with MS ME?

You can force a "Open With..." right click menu option by holding either CTRL or SHIFT when you right click a file. Forgot which... Should work on 98, ME, 2000, and XP. "Open With..." then select "Choose Program...". In that window, you can browse for any program and check the box at the bottom for "Always use selected program to open this file type." That should register the file extension to that program.

Or in Explorer (my computer), go to Tools, Folder Options, File Types and work with that tool. It's a lot more cumbersome, though.

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

I've been trying to install the program for the last 2 weeks Jason, and it hasn't worked for me. I await some info on the next version. Hopefully it will work, since it's the reason I bought the monstrosity that is the LM1.

Also, when I try to manually extract, it tells me there isn't enough storage available to perform the operation. Safe to say, I'm baffled.

Other than that, thanks! It's nice to see that it works for some.
Maybe I should get a new laptop.

:banana:

I just downloaded the latest version (2.1.0) this morning. It's not working right with an STi UTEC + LM-1. :(

The program always overwrites the Ign#1 column with either the LM-1 AFR values or "W/B" (which one is dependent on the "overwrite" checkbox in your program).

The program always overwrites the Ign#1 column with either the LM-1 AFR values or "W/B" (which one is dependent on the "overwrite" checkbox in your program). Here is the deal with the STi output. The STi UTEC doesn't normally have the AFR column where the regular WRX AFR column is. In order to maintain log compatibility with as many 3rd party log 'processing' programs that are out there, the UTEC_Logger "converts" the native STi format to a format that is compatible with the "original" UTEC format. While it may look a little different than the log you're normally used to seeing, this is the log format that the UTEC uses for the WRX.

Here is the question though, disreguarding and header labels that may be in the log, if you look at the column data itself, did the WB value "overwrite" the Ign#1 column, or did it get "inserted" before it as an additional column BETWEEN the "knock" column and "Ign#1" column. If it's INSERTING the value in a new column, then this is the correct operation that the program is supposed to do. If it IS overwriting the value, let me know...can you post a sample log with the "overwrite UTEC AFR" option ON for me to look at?

NOTE: The "overwrite UTEC AFR" option was added as an option for the original program to provide compatibility with 3rd party log processing programs. The original "tuner" format wouldn't work in some programs back when before many were made to be "STi" compatible. Since I am supporting different ECU's now and different W/B meters (which wasn't originally planned for), this option is more or less a "make WRX compatible" log. I use the program with this option ON all the time myself. I think this option is rather confusing now, but still has a valid purpose. For instance, in the next release, if you are using a Tuner as your WB meter, if you have this option ON, it will output like a WRX log, but if you turn the option off, it is going to append ALL Tuner info to the end of the log line, including the Tuners Aux inputs. Since no other programs can read a log with EXTRA data in it like the Aux inputs, there is no need to keep the log file WRX compatible, so it will record the log differently with extra data in it.

So to make a long explanation short, this "overwrite UTEC AFR" option will work differently depending on the ECU type and WB meter type that you have selected. In General, if you plan on processing the log with another program, TURN THIS OPTION ON before you log. The log will then be output in the 'original WRX UTEC' compliant format no matter what type of ECU you have selected.

-jason

Here is the question though, disreguarding and header labels that may be in the log, if you look at the column data itself, did the WB value "overwrite" the Ign#1 column, or did it get "inserted" before it as an additional column BETWEEN the "knock" column and "Ign#1" column. If it's INSERTING the value in a new column, then this is the correct operation that the program is supposed to do. If it IS overwriting the value, let me know...can you post a sample log with the "overwrite UTEC AFR" option ON for me to look at?It is *definitely* not inserting a new column. The Ign#1 column always gets overwritten.

The columns here from left to right are:
RPM, MAP, MAF V, TPS, Load Site, Knock Count, AFR, Inj duty, Mod Ign, Mod Fuel, Boost, and Mod MAF V.
2417, -6.1,2.1, 12, 00, 00, 14.6, 7.5,ECU. , +0.0,ECU. ,2.1
2418, -5.9,2.1, 12, 00, 00, 14.5, 6.0,ECU. , +0.0,ECU. ,2.1
2408, -5.9,2.1, 12, 00, 00, 14.6, 6.0,ECU. , +0.0,ECU. ,2.1
2434, -5.9,2.1, 12, 00, 00, 14.5, 7.8,ECU. , +0.0,ECU. ,2.1
2445, -5.9,2.1, 12, 00, 00, 14.3, 6.2,ECU. , +0.0,ECU. ,2.1
2436, -6.1,2.1, 12, 00, 00, 14.5, 7.4,ECU. , +0.0,ECU. ,2.1

It is *definitely* not inserting a new column. The Ign#1 column always gets overwritten. OK, this is definately a problem, I'll look into it. Thanks for posting the sample log...

edit: found the problem and fixed it for the next revision.

-jason

also with the sti live mapping, when i select injector duty peak average, i get ignition timing figures.

also with the sti live mapping, when i select injector duty peak average, i get ignition timing figures I *believe* this was a side effect of the above problem. The guage info is pulled from the log AFTER the AFR has been inserted, and the log has the 'extra' AFR column after the knock column at this point. The problem fixed above was causing the AFR to overwrite a different column, rather than inserting a new one. I believe this skews all the column data to right of the 'knock' column.

The next release should fix both of these problems, if this is still an issue when 2.2 comes out, definately let me know.

I need to get the fixes for the Sti stuff released ASAP for you guys, but I'm not close enough with the TechEdge WB stuff to let it go yet. I may release the next version WITHOUT the TechEdge support just so the Sti bugs can be fixed for those of you with these problems.

-jason

The UTEC log line is displayed and shows 0 where the w/b reading would be if connected to the TUNER, the com port settings you list are correct. The Tuner log that you posted, for the most part, is about what I was expecting. The program is looking for the AFR in the #2 column of the Tuner log which looks to be correct.

If it's only displaying a '0' for AFR with the Tuner connected to the WB com port, then I'm wondering if the Tuner is not being put into Logger#1 mode properly by the program.

Currently, when the com ports are open, the program will send a CR/LF (Enter key) to the unit to 'wake it up', and then sends a '!' character (shift+1) to it to start the logger. This is the EXACT same procedure that the program uses to connect to the UTEC as well. Is there a different way to do it on the Tuner?

If you try to use the program to connect to the UTEC and the Tuner like you were doing, when you close the com ports, open up hyperterminal and see where in the menu the Tuner was left... If the program is putting it into logging mode correctly, then when you disconnect and re-connect using hyperterminal, you should still be in the logger screen, if not then there is our problem.

I would like to get this part working correctly as well before the next release, so that I can have all the existing features debugged before I start adding more and more stuff.

Thanks,

-jason

I need to get the fixes for the Sti stuff released ASAP for you guys, but I'm not close enough with the TechEdge WB stuff to let it go yet. I may release the next version WITHOUT the TechEdge support just so the Sti bugs can be fixed for those of you with these problems.Pretty please? ...with Splenda on top? :D

Is there a version you can e-mail me? If so, please PM me.

After having my laptop mouse pad give me fits I borrow an old laptop from my brother, that I spent a few very frustrating days trying to get the UTECLogger to work on it. Once I finally get it to work I had to fight the USB to Serial adapter. I finally get every thing working and my O2 sensor craps out on me. At least I know it is a easy fix. Thanks for the program Jason I look forward to using it (I hope).

If you try to use the program to connect to the UTEC and the Tuner like you were doing, when you close the com ports, open up hyperterminal and see where in the menu the Tuner was left... If the program is putting it into logging mode correctly, then when you disconnect and re-connect using hyperterminal, you should still be in the logger screen, if not then there is our problem.
I-jason

I checked it out this morning, the UTEC is still logging when I re-connect using hyperterminal and the TUNER is not :( :( :( .

I checked it out this morning, the UTEC is still logging when I re-connect using hyperterminal and the TUNER is not Ok, so this is our problem, the Tuner is not logging becaue the program is not putting it into Logging mode correctly...

So what IS the correct way to get a Tuner into "Logger#1" mode if you are using hyperterminal? I am using Shift+'1' like the UTEC uses, but this apparently isn't working...

-jason

Ok, so this is our problem, the Tuner is not logging becaue the program is not putting it into Logging mode correctly...

So what IS the correct way to get a Tuner into "Logger#1" mode if you are using hyperterminal? I am using Shift+'1' like the UTEC uses, but this apparently isn't working...

-jason

I am sitting in my car right now and when I hyperterminal into the Tuner it only takes shift + '1' to go into the .csv data 1 logger.

What I have noticed is when I am in the MPS logger and I do not have the 'overwrite UTEC A/F values' checked it displays 'W/B' in the seventh column and another column is appended onto the end of the log '0.00'. The w/b is not displayed in the UTEC log when it is not connected to the Tuner. I think you said that you don't display the narrow band O2 sensor? When I click the 'overwrite UTEC A/F values' the 'W/B' becomes 0.0 and the appended column goes away. I have no idea if this has any effect on what is going on but I thought I would throw it out there.

I am sitting in my car right now and when I hyperterminal into the Tuner it only takes shift + '1' to go into the .csv data 1 logger.
This is what I thought. I did some bench testing (without Tuner), to make sure the keystrokes were being sent to the Tuner during a "Connect"... it it working just as the UTEC port does.

However, before sending the Shift-"1" to the Tuner, I am sending a Carriage Return first... do you think this is causing it to mess up?

I send the CR with the UTEC too, because when you first connect you need to "wake" it up, but perhaps the Tuner is not this way.

Could you test in hyperterm to see if sending a CR before sending Shift+"1" is causing it to go into a different menu, or somewhere unexpected? I definately want to fix this before I post the next release of fixes.

Thanks,

-jason

Could you test in hyperterm to see if sending a CR before sending Shift+"1" is causing it to go into a different menu, or somewhere unexpected?

When I go into hyperterm I can start logging by immediately sending shift+'1' or I can go to the main menu using CR and then shift +'1'. What you are sending (CR, shift + '1') should work.

I can hyperterm into the Tuner and start logging and close the hyperterminal, if I reopen the hyperterminal the Tuner is still logging. So this shows the tuner will continue to log even if the port is closed. If I try opening the MPS logger with tuner still logging (and the hyperterminal port closed) still nothing happens. BUT when I hyperterminal back into the tuner (after closing the connections in MPS logger) the Tuner is no longer logging. I tried this several times with the same result. When the MPS accesses the Tuner it causes the Tuner to stop logging. Whats that mean? Hell if I know.

Travis

New version available on Download site...

No new features, except some important "bug" fixes made. The Sti logging should now work properly.

TAP - I also made changes to the Tuner connection attempt, if you could check it out and see if it works or not I'd appreciate it...

-jason

It's telling me that the compressed folder is invalid or corrupted.

:(

Is this during downloading it, or installing it? I will do some testing myself on it. Is anyone else having these issues? I'm now running an updated version of VB as well as the Package and Deployment Wizard. This may be the cause.

-jason

I did some testing on both of my XP Pro PC's with no problems. I even downloaded the file from the website to reproduce the steps that would be taken to install the program.

I removed my previous version via Add/Remove Programs and installed the newer version without a hitch. No errors or warnings were given...

What OS are you running on your PC? I know that Win2000 has known issues installing programs made with package and deployment wizard. Another thing to try would be to download the file again and retry, maybe the file got corrupted during download.

-jason

BTW, I should mention before someone asks about it...

Yes, the new version 2.2 lists the "Tech Edge" as an available wideband unit...however this doesn't function yet... Don't bother trying it, it won't work in version 2.2. The code for the TechEdge is only partially developed and I felt I needed to get the Sti logging bug fixed and released as early as possible.

-jason

TAP - I also made changes to the Tuner connection attempt, if you could check it out and see if it works or not I'd appreciate it...

-jason

I am currently having serial/usb cable issues and will test out the logger later in the week (after I buy a new cable :rolleyes: )

Travis

jason, I redownloaded the program and it seems to have worked this time. No problems with the install either, thank you for that.

Now I need to hook up with the WRX again.
Unfortunately, I drove the truck in this morning.
:(

I'll keep you updated.

cheers, Steve.

New Version 2.3:

Now supports Evo8 UTEC logs, and has minor speed improvements...

Here is the link to the updated download page...
MPS_UTECLogger Download Page (http://mpsav.com/MPSUTECLogger/MPS_UTECLogger_Download.htm)

-jason

Just updated to 2.3, thanks for the great program and all the work you put in to it.


Scott

"Create "compliant" UTEC LogFile" :huh: Why the rewording?


Is there a way to have the log map page open to full screen by pushing say f11 like with IE or just a maximize box in the top right corner?

"Create "compliant" UTEC LogFile" Why the rewording?
Mostly because now that the Sti and Evo UTECs are supported, they don't have a AFR column at all, so the program isn't "overwritting" the UTEC AFR, it instead "inserts" a new AFR column where the regular WRX AFR is located, thus making it compliant.

-jason

wut does the cell hit count (sum) do 4 this prog?

wut does the cell hit count (sum) do 4 this prog? The "cell Hit Count (sum)" simply keeps track of how many time the program has recorded data for each cell on the map. each time a log-line is received and processed to the LogMap, the Hit Count for that cell is incremented. The Hit Count is used internally for calculating averages, however it can be handy to check how many "Hits" a cell has had to determine how accurate the data in that cell may be.

For instance, if AFR was showing 12.4 in a cell where you want it to be 12.2. You can look in the Hit Count of that cell, and if the hit count is low, 1or2, then you know that the AFR reading "might" be a fluke, however, if the hit count is something like 100, then you know you definately need to richen up the cell.

A lower hit count is more effected by skewed data than a high hit count is.

-jason

TAP - I also made changes to the Tuner connection attempt, if you could check it out and see if it works or not I'd appreciate it...

-jason

I tried it out and now it takes the very first value that it reads for the WBO2 and only shows that. for example, it 13.8 is the first value that the logger reads from the tuner that value does not change on the display or the logger output, no matter what the true reading is. If you disconnect and reconnect without shutting the program down just "0" is displayed and inserted into the log.

I would really like someone else to try this logger with their Tuner to ensure this problem is not caused by WinXP or my toshiba laptop.

Sent donation. Thanks for your hard work

I tried it out and now it takes the very first value that it reads for the WBO2 and only shows that. for example, it 13.8 is the first value that the logger reads from the tuner that value does not change on the display or the logger output, no matter what the true reading is.
OK, does this mean we are getting closer? So the question I need to ask is this, if you start fresh, and try to connect, then disconnect, then open up hyperterminal to see where in the Tuner menu it was left off? Did it actually make it to the <shift>+1 logging screen, or is on the main menu like before? That was very good troubleshooting you did last time to determine if the Logger was connecting or not.

Getting 1 value from it *could* mean that it's logging now and I just have a parsing error to deal with, or it could be a fluke, and we're still back at step 1 with the connection not working still.

Also, if you want to send me your email address, I can email you changes to the logging program to test after I make changes to the Tuner stuff. I would really like to get this sorted out, as I'm sure you would like to have it working correctly as well. Any troubleshooting you can do would be appreciated.

I would really like someone else to try this logger with their Tuner to ensure this problem is not caused by WinXP or my toshiba laptop.
I would be curious as well if others have the same problem. My guess is that the problem is NOT WinXP or your toshiba laptop as I'm devoloping the program on a Toshiba Laptop and WinXP Pro SP1. Your system is about the same as my development pc.

-jason

New Version 2.4 Available for Download...

New Feature: Ability to save out LogMap tables to .csv file for importing in Excel (or other spreadsheet program). Exports any combination or ALL of the 8 LogMaps to file.

Fixed: Evo8 parsing bug causing timing and IDC to display incorrectly.

Happy Tuning!

-jason

Thanks for the update and all the work you put in to this. I us your program every morning on the way to work, at lunch, and then on the drive home not to mention at the track (1/4 mile that is).


Scott

Question: I want to view the AFR information in that nice big window you have. When using this with a WRX UTEC with Tuner Pro do I have to seperate the serial cables and have both plugged into my laptop? By default the AFR info is already in the UTEC log file. Does the SW extract the AFR info itself or do have have to seperate the serial cables and setup the SW to look at one for the UTEC and the other for the tuner?

I want to view the AFR information in that nice big window you have. When using this with a WRX UTEC with Tuner Pro do I have to seperate the serial cables and have both plugged into my laptop?

Yes, the software was designed as a bridge, so AFR is not parsed from the UTEC port at all. (I know this would be handy, and will maybe be added in the future, but will require quite a bit of code rewriting to change). The software treats the Tuner like any other stand-alone wideband that needs to be connected seperately from the UTEC.

Let me know if this the Tuner is works for you once connected in this fashion. TAP reported to me that the Tuner isn't being put into Logging mode properly from the software, and has been having issues getting it to work. I myself use an LM-1, so I don't have a Tuner to test/debug with either, so I'm not sure if this issue is resolved yet or not.

If you do have problems (or success) getting the Tuner to log, I would like to hear from your experiences. The more info I can get about the problem, the more likely I can figure out what is causing it.

-jason

Jason,
I stumbled upon this last night. So I downloaded 2.4 and hooked it up to my utec. Everything went well.

Then today, I grabbed one of the LM-1's here at work and plugged it in via a serial->usb plug. UTEC logs comes up but the LM-1's numbers don't. Thought, OK maybe i'm having issues with the serial->usb connector, so I switched the UTEC and LM-1 around and changed the com ports in the software. Still no luck with the LM-1 numbers coming up.

One thought I have is do I have to download the LM-1 software to get this to work? Or can I just plug the serial cable into the computer and your software sucks it out?

I'm not real computer literate when it comes to this stuff, but any help is appreciated.

thanks,
Tim

Then today, I grabbed one of the LM-1's here at work and plugged it in via a serial->usb plug. UTEC logs comes up but the LM-1's numbers don't.
The most probable cause is the LM-1 that you used at work is probably running older firmware. Download the latest LM-1 firmware from Innovate Motorsports website and flash the LM-1 with it...

Firmware versions prior to 1.4 for the LM-1 do not output any data during operation. Earlier versions of the LM-1 need to be upgraded in order to receive data from them.

Good luck!

-jason

Thanks Jason!! Downloaded 1.41 and works like charm!! :)

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

Jason,
Does this works with the 4.2c & 5.0 Utec flash? My guess is yes as long as the output datalog remains the same.

Sweet! I hate the typing in a name thing while driving.

Kev

Does this works with the 4.2c & 5.0 Utec flash? My guess is yes as long as the output datalog remains the same. You are correct... I am running v5.0 of UTEC firmware and it works fine, I was running v.4.2a before and it worked. TurboXS has not changed the output of logger#1 between firmware updates, so everything works fine.

-jason

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! :p

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 (http://mpsav.com/MPSUTECLogger/MPS_UTECLogger_Download.htm)

Everyone enjoy!

-jason

all i have to say is awesome :banana: when i get some money (i'm a broke college student) i am going to donate to the cause, because this program is great. if you do a next version, you should put an analog gauge option it, then i might just rip out my guage cluster for a nice lil widescreen....

EDIT - I see above that somebody already posted basically the same thing. Im going to leave my post though just to raise the question again though, cant hurt can it?

jmussetter, i sent you an email today. I just wondered if there is a way you can help out us guys who have our tuner plugged into our utec. I am setup like that and with your program it completely ignores my afr and doesnt show it in the logmapper portion of the program nor in the digital gauges. Perhaps you can add an option in the wb02 dropdown that says "Tuner via UTEC" or something?

I know I dont need the bridging, but i'd love to use the LogMapper portion of your program, its awesome but I only really want the wb afr portion of it and as it is that is the one part of the logmapper that just shows all zero's.

Jeff

Also, did you write this in visual basic or visual C+? Im hoping basic because I dont know C and i'd like to tinker with writing a comm port interface (mainly utec) program.

Jeff

I hooked up the utec to com 1 and the lm-1 to a usb port with a converter to serial. When trying to run the logger it states "error open com port". I am not sure what to do to get this to work.

Thanks,

Greg

have you ever thought about coding support for the Zeitronix ZT-2 into your app?

Anyone know how to get the com ports to open? I can run utec but the the utec logger does not seem to recognize it.

Greg

MPS_UTECLogger v.2.6 is now avail on the web.

New features include:

- Color shaded LogMap cells! Shades each cell of logmap with gradiated color within color range and shades cells based on hit-count. Easily see how smooth you transitions are and how reliable the data in each cell is!

- More Hotkeys for turning windows on/off and connecting/disconnecting from devices.

- LogMapper now captures stock ECU Timing values as well. Use to compare to UTEC Timing maps or see the "health" of the current tune...

- More GUI enhancements including "remembering" window positions, LogMap data resizes with window size so all data is always visible, and rounded values in LogMapper make it easier to read.

- More Bug fixes...

Download at:
MPS_UTECLogger_Download (http://mpsav.com/MPSUTECLogger/MPS_UTECLogger_Download.htm)

Def. Worth the upgrade...

-jason

Anyone know how to get the com ports to open? I can run utec but the the utec logger does not seem to recognize it. The error your getting is most likely caused because either one of the com ports that you have told the program to use is already being used by another software, -or- one of the ports does not exist on the computer. First make sure you don't have hyperterminal or any other program open that may be using a serial port (ie: palm sync type programs).

Next you need to make sure that the com ports for both the UTEC and the WBO2 are selected properly on the Main interface of the logging software. If you are not sure which com ports are correct, then you will need to goto Windows device manager and look at "Ports" and see what com ports are assigned to serial ports.

-jason

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

I connected the utec to the tuna and then to my notebook, run the uteclogger and log map (realtime) to get the AFR readings filled up in the map, but i dont get anything. Aldo in the gauges theres no AFR reading.
Do i have to connect them separately?? cause in only connect to the utec in the main screen as i dont have a second device connected.
I'll try connecting the Utec directly to my notebook and the tuna also directly to the notebook and connect to both devices.
Anyway i'll apretiate an answere.
Thanks.

You know, I've been having a problem running v2.6. It might simply be something with my USB to Serial driver or something I'm not sure. My laptop would crash while trying to connect or disconnect and get the blue screen (aka BSOD) running Win XP. I was also getting connection problems too. For example, UTEC would still connect through Hyper T but when I would try to connect the MPS prog it would tell me that it couldn't connect to the port or something like that when I knew that the ports were open.

Anyway, I did a number of things last night to the laptop including uninstalling the USB to serial cable and reinstalling it, reinstalling the MPS prog, and relashing the bios on the laptop (I had an issue with the mouse pad and some other little things). It was actually running cleaner than it was previously. I just need to see if it improved anything now.

Anybody had this happen before. I believe the BSOD said something about corrupt mmpool driver (or was it mmspool). I think I may also switch the UTEC to use the USB adapter cable rather than the LM1 the way it is now.

Can any kind soul tell me is Innovate LC-1 oxygen sensor can be used to replace wrx OEM wideband O2 sensor..I am thinking of permanently mount it at the rear oxygen sensor location after downpipe to safe the trouble of taking it in and out..
I know the MPS UTECLogger can bridge to this wideband oxygen sensor. Need to confirm that before buying the sensor.

Guys, my laptop is still crashing from the MPS program. I would say that it crashes about every 1 out of 6 times. It happens when I have to "disconnect from the devices" in MPS so that I can connect to Hyperterminal to make changes to UTEC. It's a little frustrating but I can't complain too much since it's free ;) My laptop is an HP ZE4300 series with a fresh copy of Win XP ruuning on it. The blue crash screens usually say either mmpool or serpl (I don't remember this one exactly).

Yo,

I have the turbo xs generation 2 wideband...I connect the utec to com1 and connect the wideband to com 6 using the phone cable line and serial adapter...I get the utec readings however, can not get a afr reading from the wideband...i have the turbo xs wideband selected with the correct com 6 port.......can any one help.......does the software support the generation 2 wideband by turbo xs?

This is a wonderful tool and would love to resolve this and make a sizable donation. This is great for us do it yourself tuners.

is anyone running the turbo xs generation wideband w/ this interface?

Guys, my laptop is still crashing from the MPS program. I would say that it crashes about every 1 out of 6 times. It happens when I have to "disconnect from the devices" in MPS so that I can connect to Hyperterminal to make changes to UTEC.
It sounds like it may be a driver issue. I havn't seen this issue on any PC's that I've tested on. I know on occasion I would have a crash if the program was running and I physically unplugged the USB->Serial adapter, because it would cause the com port to vanish in windows, and thus from the program. Maybe you have a loose connection on the USB port? It's hard to say the actual cause, but coming short of trying different USB adapters, I would suggest removing and re-installing the latest drivers from the manufacture again.

Good Luck,

-jason

I have the turbo xs generation 2 wideband...I connect the utec to com1 and connect the wideband to com 6 using the phone cable line and serial adapter...I get the utec readings however, can not get a afr reading from the wideband...i have the turbo xs wideband selected with the correct com 6 port.......can any one help.......does the software support the generation 2 wideband by turbo xs?

There is a known bug that I havn't been able to fix yet, where the program can't get the Tuner to go into logging mode. I've made several attepts at fixing the issue, with no luck. It's hard to fix some issues like this when I don't have access to a physical Tuner, so I'm programming blind and can't test it in front of me.

Basically the program trys to connect to the Tuner the exact same way as it connects to the UTEC, (sending Shift+1) however, the UTEC responds by entering 'logging mode' and the Tuner does not...

Can you tell me, try to connect to the devices in MPS_UtecLogger, and then disconnect, then open up hyperterminal and connect to the tuner and see if it is still in logging mode or on the main menu... Let me know what you find out...

-jason

So after all this time is it available the Real Time Map log feature????
Last time i tried, i didn't get AFR readings.
Soon i'm getting new 800cc inyectors and a GT30r turbo kit and it would make tune up easier.
Thanks.

:( This seems to be a good program. I have a 06 STi running stage 2 UTEC. I see the dashboard connected to my AEM WB but the log function won't work. I key it up and stare at a blank log. I've tried to save to a named file first and run realtime and the log is still blank.
Any suggestions??

Great little app! Used it last night. I really like the logging and graphs. But...

Is there any possibility of releasing source or something so we could make the changes to AFR ourselves? I realize you want to maintain compatibility with 3rd party apps that may parse your output...but all I want is to use your app to do road tuning on my STi ;) Even a simple advanced checkbox or .ini file for "accept TurboXS WB values" would be fantastic!

Anyone try using v2.6.0 with the latest utec 5.8 release?
Thanks!1
xeve

How do I connect my AEM Uego to my laptop so I can link the 2 together?

Look in the UEGO manual for instructions. You need to get a female db9 adapter from radioshack and solder 2 wires - a chassis ground and the blue uego wire to pins 2 and 5. I forget which is which. Then connect to it at 9600 baud and it will spit our your AFRs.

Chris

So I got a new laptop, and the first place I had to go to was jmussetter's site. That's how good this software is.

Jason, you're a king among men.
Between openecu, and jmussetter's UTEC software, it's a great time to be a Subie nut.

Anyone tried this out with the UTEC delta?

Look in the UEGO manual for instructions. You need to get a female db9 adapter from radioshack and solder 2 wires - a chassis ground and the blue uego wire to pins 2 and 5. I forget which is which. Then connect to it at 9600 baud and it will spit our your AFRs.

Chris

For those using AEM UEGO WB02 sensors, this adapter makes the connections from the AEM AFR gauge easy (no soldering required). Connect the blue data wire to pin 2 position and ground to pin 5 position. Connect the adapter below to an RS232 male to USB wire to enable data transfer to the PC/program.

http://i119.photobucket.com/albums/o124/beaviscih/db9rs232connector.jpg

Hi,

I just got my AEM Wideband. Im able to see them both In the software but can't see the boost, injector duty and maf...
After about a minute, I loose the AFR, it freeze. Tried switching com1 and 4(usb) between the two device and same thing...

Am I the only one having this issue? Will try with an other laptop tomorrow.

Thx

MPS_UTECLogger v.3.0 is now avail on the web.

New features include:

- Support for WRX, STi, Evo8, and 350z/G35 Utec's

- Now supports PLX Devices WB, Tech Edge2.0 WB, and Zeitronix WB in addition to previously supported wide-band meters. (LM-1, LC-1, AEM, and Tuner)

- Now supports connecting the TurboXS Tuner in-line with UTEC.

- More Hotkeys and HotKey Help

- New interface "Look".

- FULL User Manual!

- More Bug fixes...

- Pay version (w/ 30 Day Free Trial)

Download at:
http://www.mpsav.com/MPSUTECLogger/MPS_UTECLogger_Download.htm

-jason

Ok nvm, only one serial port so it looks like Ill need a USB adapter.

I have baught and downloaded the latest version of the MPS logger 3.0. Everything works great except the AFR reads only a constant -1 from the UTEC log. I have resetup everything as instructed for the TurboXS tuner inline with the UTEC and still nothing. Is anyone else having this same problem?

any new features coming like auto connect and auto log?

Jason thanks a million for the link to the mps_utec logger :);):lol::D:banana:I realy appreaciate it. Mark

I have baught and downloaded the latest version of the MPS logger 3.0. Everything works great except the AFR reads only a constant -1 from the UTEC log. I have resetup everything as instructed for the TurboXS tuner inline with the UTEC and still nothing. Is anyone else having this same problem?

Yep, I have the same problem :sadbanana:, do you fixed? give me your tips man:cool:

Hi Jason. Just downloaded the latest version onto one of these new ASUS Eee mini laptops. The download and install went fine, connection was via COM4 and the dashboard works great.:cool:

I haven't tried connecting up my LC1 as I need a second Serial to USB converter. Should be fine though.....

My problem is when I de-select the gauges, and select the Map log, the map fires up but no data is displayed. Doesn't seem to matter which radio button I select (for data type), nothing comes up on the graph.:mad:

Communication seems good....I get a live UTEC feed with numbers changing, so I can't work out what I may be doing wrong. Do you have any advice to solve this one Jason?

Apart from this, the software looks useful & I'm keen to get it working properly.

cheers mate

Hi. Got it sorted. There was nothing wrong at all. I just needed have the logger open for longer to let it do it's thing. All looks good now.:banana:

If I'm reading a afr of 9 with the stock sensor is that basically like reading it as rich in the utec?:confused:

I reckon so. The logger just seems to drop from mid 12 to 9 in one hit. No 11's or 10's, but my LC1 shows the gradual decline.

I should note that the LC1 has never seen less than 10.8 yet the logger just sits on 9.