I am starting this thread to replace the other 2. Please only post in this thread from now on. I will post found bugs, future updates, corrections/updates in progress, and new software versions all in this thread. If you find a bug in the program, please send me a pm and we can get it fixed asap. Suggestions for future updates and design ideas regarding carputer layout is more than welcome.


Latest Version: 2.1.0 - 27JAN06 4:45pm EST
Download HERE (http://www.dezignduo.com/UTI/)

Map Editor: Version 2.0.2 - 28JAN06

Jeff

Note - This software is not officially endorsed by TurboXS. I am the sole designer and have no affiliation with TurboXS.

Hooray, quick question though... does this still require the same com connection as normal UTEC logging? ie. that old style laptop com port?

Yes, the only way to interface with a utec is through its com port. USB would have been nice but oh well ask TurboXS about that one.

Update: I just released Version 1.2. It is a noted improvement, please give feedback. I hope there are not bugs, i seriously think that they are starting to get minimal at this point.

Jeff

Hooray, quick question though... does this still require the same com connection as normal UTEC logging? ie. that old style laptop com port?

just use a serial to usb converter, thats what i do with my tablet pc, it has no serials on it. as for this program, navybluesubaru you've really done a good job :banana:

Ok the macromedia flash development is comming along VERY well. Here is a sneak preview of an actual flash gauge running perfectly inside the program.
http://www.dezignduo.com/UTI/preview.jpg

All I have done for now is a greddy boost gauge. It reads in Bar if you were curious.

Jeff

Still not logging. It links up. The graphs start generating numbers, low rpm and in the 0-10 columns and it acts golden, then with a little load it pops a huge white box that pauses for, say, 8 seconds? then a runtime error or something pops up. I couldn't see it in the sunlight while rolling.

I've seen: Run-time error '424' Object Required ( a few times)
and: Run-Time error '30009' Invalid Row value.

(both before running v1.2)

Hope that helps.

Oh, it doesn't seem to update the .ini file right away. I don't know enough to know if it should. If I open it before making any adjustment I can see the WRX5 and the stuff pertaining to autologging such as the 1000 - 8000 rpm numbers etc... I close it, make my settings, then re-open the .cfg and STi11 or whatever it is supposed to say isn't updated yet. I can close the program and re-open it and it'll go back to showing com4 instead of 1, but it's connected, so it's using the right port. Then I can go return a movie (which is what I just did during the test run) and hybernate the PC. I come back... everything is set tight. The .ini file says STI1.1 and all that. Odd. Or maybe not odd... I don't know. but I thought it might help.


Can we just set that file up manually?

1
WRX5
1000
8000
0
30
30
105
10
100
2
4
4
True
True
True
True
6
0
1
0
0
0
0
16
1
6

That screenshot is supah sweet!

Which DLL's does it require? Can't seem to get it fired up on my car PC. I've installed the VB6 DLL runtime library but no luck.

2phless - The '424' Object Required was caused by the autologs I believe. That has been fixed 1.2. Also, the runtime error has been fixed in 1.2.

I realize that when I moved the place inside the code where it decides to save, from when the program closes to when you update the settings, it wont update any of your dropdown settings. I am going to correct that in the new version comming out shortly. A workaround is to set them where you want them, then open the settings, then click update. It will work for now.

1.3 Later today, featuring digital gauges! I just finished the AFR gauge, it looks sweet!

Jeff

Gethin - It should tell you what DLL's you need when it starts. If it wont run then it will tell you what file is missing. I can research it but I dont know off the top of my head.

Jeff

Version 1.3 is out. It features flash gauges. They are very new and will probably get moved around a little bit before they are settled. I have plans to have a full gauge-pack that fills the screen of a carputer, so thats what im aiming towards.

Jeff

It's ok. I'm rebuilding my car PC from scratch again anyway, with service pack 2 this time.

I'm using a crappy quality touch screen so it's hard for me to see what DLL is missing.

I'll be running the program from and logging to a USB key, so I can take the key into the house and see the logs etc as the 7" screen is too finicky to work with text.

I'll try v1.3 :)

Gethin.

I tried 1.2 this morning and got the same "Run-time error '424' Object Required ".
Did this get fixed in 1.3?

Also, I noticed in settings the update doesn't update all the changes, just the one of the currently selected tab. For instance, I updated things on ever tab, then hit update. When I tried to connect it didn't because it was still set to com4 instead of com1 (what I set on the first tab).

Also, why is com 4 the default? I'd think most people would use com 1.

hey jeff, it would be really cool if you could use the defi amber faced gauges as your gauges. heres the link to them http://www.defi-shop.com/product/bf/bf_top.html.

just use a serial to usb converter, thats what i do with my tablet pc, it has no serials on it. as for this program, navybluesubaru you've really done a good job :banana:

Ok... I got issues... I have a serial to usb converter, it plugs in to the UTEC and then is a USB end on my laptop. I used this program and I was switching around different com ports until it said "connected".... but when it said it was connected it was not showing any values for any of the stats.... I did not have much time to mess around with it will try again tomorrow, but not sure if I was doing something wrong possibly?

I've gotten it to work more and more each time. This last time it worked but the "pop-up" was just a big white window that stayed for a few seconds. Turned all the pop-ups off and it seems to be fine. I haven't had a chance to peruse the logs it made though... had to eat dinner or pass out while reading logs. I chose dinner.

I made this video of an error earlier today. It was 1.2. I think it was just the pop-up hanging.

The sound might be crackly but it's not important. Just turn it down (http://media.putfile.com/Logger1)

If I hibernate and come back, I get a hidden window behind the carputer screen that says run time error - 8021 - application defined or object defined error

Ok... I got issues... I have a serial to usb converter, it plugs in to the UTEC and then is a USB end on my laptop. I used this program and I was switching around different com ports until it said "connected".... but when it said it was connected it was not showing any values for any of the stats.... I did not have much time to mess around with it will try again tomorrow, but not sure if I was doing something wrong possibly?

Same here I have an STI with a Serial to USB connection. I get data on the the gauge screen but nothing autologs...:-(

Type-C: this error should be gone. Although i'd like to know in more detail what the problem is caused by. I just changed something on every tab, then saved and closed. Then re-opened, and they are all updated. I have no problems here. With respect to the code, it doesnt matter what tab you are on, all that does is set the visibility property of the frames to show the proper settings for that tab you clicked. Com 4 is the default because that is what com port it is on my laptop w/ serial-usb converter ;)

2004stiwrb: I will look into those gauges.

drdome99: sometimes it takes up to 10 seconds to sync up. I am not sure why but im constantly looking to improve ways to speed this process up. How log did you wait and what version was it?

2phless: See if you can get it to happen in 1.3. Also, what is your termination delay set at?

I have read everybody's posts and im looking into all of the problems.

Jeff

I didn't have much time to play with it so it could have been I didn't give it enough time to sync, I will play more tomorrow though and get back to you.

2phless: See if you can get it to happen in 1.3. Also, what is your termination delay set at?



Jeff

I haven't seen an error in 1.3 since I turned off all the pop-ups. I'll turn one on, then the other and see if it'll hang. My delay is 8 seconds. Now that I think about it... maybe I turned off the fast logging as well.

For those with the CarPC environment, if the application does not support a reconnect on restore from hibernation, a great work-around is this utility called “Hibernation Trigger”. Basically you can specify any source file to run when the system enters hibernation mode, and then when restored from hibernation mode. For example, write a custom batch or other program to close this (and any other custom) monitoring applications if running. Use this as the script to call when the system is signaled for hibernation shutdown. Then specify any other start-up script (or this monitoring application) to launch when the system restores from hibernation and ensure the app is enabled for auto-reconnect. Completely automated start-up and shutdown while using hibernation…

http://www.rpi.edu/~desimn/suspendtrigger/index.html


PS: Please oh please make this app compatible with UTEC logger only (no Tuner) for us poor bastards who can’t afford the Tuner product… ;)

I fixed the DLL thingy. I had to manually register the dll after I installed it.

C:\WINDOWS\system32>regsvr32.exe MSSTDFMT.DLL

Ok everybody, im working on 1.4 right now. I have fixed several things and added error flexibility. Instead of crashing the program, errors will popup in a special messagebox that shows you what module had the problem and what the problem was. You will need to remember the module and the error and tell me what exactly it was and what you were doing(saving, autologging, etc) so that I can attempt to fix it. This should make it much easier for me to locate errors that you all are having.

Im hoping for sometime later today for the update, i'll keep everybody posted.

Jeff

I hope you all like blue!
http://www.dezignduo.com/UTI/newpreview.gif

Heads up in a few hours....its comming!

Jeff

For those wrx owners without a tuner, when you are running rich does it say "RICH", or "Rich" or "rich"?? Also does it ever say "Lean" or anything like that? I cannot remember, its been too long. The quicker I get the answer to this the quicker I can program compatability into my program for you.

Jeff

Update: Version 1.4 is now out. Please everybody download this and use. It is quite larger than the previous versions for obvious reasons. If you encounter an error, it will tell you what module had the problem. If you get one please pm me what the message box says and what you were doing when it popped up.

NON-Tuner owners: Please try out this version! I made some provisions for you so please give it a shot! Only use Logger-1 Mode though, if you try dashboard mode it wont work at all.

Thanks and everybody enjoy!

Jeff

ps - you need macromedia flash installed to use this version!

For those wrx owners without a tuner, when you are running rich does it say "RICH", or "Rich" or "rich"?? Also does it ever say "Lean" or anything like that?

Yes, under logger #1 it says "rich" and "lean", both lower-case. I believe this is true for all 5 logger positions...

Load Knock Mod Mod Mod
RPM MAP MAF TPS Site Count AFR Ign#1 Inj#1 Ign Fuel Boost MAF WB
psia V % deg duty deg % (CL) V AFR
2463 -12.8 1.4 0 0 0 24.5 11.8 3.5 ECU. -1.5 ECU. 1.2
2449 -12.8 1.4 0 0 0 24.2 11.9 23.8 ECU. -1.5 ECU. 1.4
2443 -12.4 1.9 3 0 0 24.2 22.8 38.7 ECU. -1.5 ECU. 1.9
2452 -10.8 2.5 13 0 0 14.1 39.5 8.7 ECU. -1.5 ECU. 2.2
2534 -8.3 2.6 28 0 0 rich 35.3 9.8 ECU. -1.5 ECU. 2.3
2575 -5.3 2.7 84 10 0 14 35.2 10 30.6 -8.3 310 2.3
2651 -2.4 2.7 98 10 0 14.4 34.9 10.8 30.4 -8.7 325 2.2
2710 -0.4 2.8 98 10 0 13.7 34.2 11.6 29 -9.2 325 2.3
2780 0.6 2.8 98 10 0 13 33.8 12.6 27.9 -9.4 325 2.3
2817 1.3 2.8 97 20 0 12 33.2 12.9 26.5 -10.2 325 2.4
2876 2.1 2.9 97 20 0 rich 33 13.4 25.3 -10.8 325 2.4
2962 2.9 3.1 98 20 0 12.1 32.8 14.4 23.3 -11.2 325 2.5
3035 3.7 3.1 98 30 0 rich 32.6 15.7 21.6 -12.3 325 2.5
3086 4.7 3.2 98 30 0 rich 32.5 16.4 20.3 -12.7 325 2.6
3205 5.7 3.3 98 40 0 rich 32.3 17.5 18.5 -13.5 325 2.6
3245 6.8 3.4 97 50 0 rich 32.2 21 16.9 -12.4 325 2.7
3370 8 3.5 97 50 0 rich 31.9 22.2 16.4 -13.2 325 2.7
3447 9.4 3.5 97 60 0 rich 31.6 23.4 15.5 -14.6 325 2.9
3534 11 3.7 97 70 0 rich 31.2 27.3 15 -15.2 325 2.9
3646 12.7 3.9 97 80 0 rich 30.4 30.2 15 -15.8 325 3
3741 14.9 4 96 90 0 rich 28.8 36.1 15.2 -14.7 325 2.9
3822 17 4.1 97 100 0 rich 28.5 37.1 15.7 -15 325 3
3926 18.4 4 96 100 0 rich 28.4 36.6 17 -14.6 325 3.2
4100 19.4 3.9 96 100 0 rich 27 38.5 17 -13.6 325 3.2
4257 20 4.1 96 100 0 rich 23.3 40.9 17 -13.3 325 3.1
4374 20 4.1 94 100 0 rich 21.8 43 17 -13.3 325 3.3
4462 20.6 4.2 95 100 0 rich 21.2 44.7 17.2 -14.6 325 3.2
4591 21 4.2 95 100 0 rich 20.8 47.3 17.8 -13.9 325 3.3
4748 21.2 4.2 95 100 0 rich 22.1 47 18.6 -15.6 325 3.3
4796 21.2 4.3 95 100 0 rich 21.8 48.2 19.3 -14.9 325 3.3
4952 21 4.3 95 100 0 rich 24.7 50.6 19.8 -15.6 325 3.3
5104 21 4.4 96 100 0 rich 27.1 49.8 20.3 -15.8 325 3.4
5257 21 4.4 95 100 0 rich 29.5 51.7 20.8 -15.9 325 3.4
5307 20.8 4.4 95 100 0 rich 29.5 53.3 21 -15.9 325 3.4
5491 21 4.4 96 100 0 rich 29.4 52.5 21 -15.8 325 3.4
5602 20.4 4.4 95 100 0 rich 29.4 57.3 21 -15.6 325 3.4
5717 20.2 4.5 95 100 0 rich 29.4 58.8 21 -15.1 325 3.5
5797 20.2 4.5 96 100 0 rich 30.5 56.8 21 -14.9 325 3.5
5963 20 4.4 95 100 0 rich 31.2 60 21 -14.7 325 3.5
6161 20 4.5 95 100 0 rich 31.5 60.2 21.3 -14.6 325 3.5
6172 19.8 4.5 95 100 0 rich 32.2 60.5 21.5 -14.7 325 3.5
6207 19.8 4.5 95 100 0 rich 35.5 61.2 21.9 -14.9 325 3.5
6349 19.2 4.5 96 100 0 rich 37 61.3 22 -14.9 325 3.5
6561 18.8 4.5 96 100 0 rich 38.3 63.3 22 -15.1 325 3.5
6626 19 4.5 96 100 0 rich 38.7 61.2 22 -15.2 325 3.6
6626 19 4.5 95 100 0 rich 38.9 60.5 22 -15.2 325 3.5
6747 19.4 4.6 96 100 0 rich 39.3 61.5 22 -15.2 325 3.5
6548 18.8 4.5 7 100 0 rich 10.8 14.2 ECU. -15.2 LCM. 2.8
6230 12.1 1.8 0 30 0 15.4 11.1 5.8 ECU. -15.2 LCM. 1.4
5807 4.5 2 0 10 0 lean 11 6.4 ECU. -16.4 LCM. 1.6
5420 -3 2.1 0 10 0 lean 11.2 6.1 ECU. -17 LCM. 1.5
4997 -10.2 2 0 10 0 24.5 10.8 6 ECU. -17 ECU. 1.6
4675 -11 2.1 0 0 0 24.5 11.1 34.2 ECU. -1 ECU. 1.9

Jeff, for the log lines I err on the side of caution and just remove all whitespace and convert everything to lowercase so if TXS decides to change its mind on things it will never change from my perspective. You use VB right? So this should be pretty easy. I don't have reference for VB out but its something like Trim and ToLower.

Update: Version 1.4 is now out.

Holy crap 3 minor revisions out in less than 24 hours! I wish I had that kinda time :lol:

I am using mps logger as it is an interface between my lc-1 and the utec but would like to try your program out if it works the same way. I have a usb to serial connection for both the utec and the lc-1 and they log in the same file through the mps logger. Does your utec interface handle the wideband in the same way cause I think your gui is pretty sweet and logs in a nice fashion

I dont have access to an LC-1 so I dont know how to code for it. If somebody in the jacksonville area had one then I could code for it. If it is possible to sync up with it in hyperterminal, then someone who has one can capture text, then connect to it and save the stuff it does for at least a couple seconds.

Jeff

Ok, i updated the program to look for "rich" and "lean". If you are running without a tuner, you need to re-download it from my site. Otherwise dont bother.

Jeff

I haven't loaded 1.4 yet but I'll post the 1.3 error now that i've had some time to reproduce it sitting still (set TPS to 1, boost to -9 etc... to make it easy) and it's still fresh in my mind.

2 things. 1. The logs recorded are all empty. 2, The white screen that pops up is the pull log. (or perhaps the report) I hunt for the close button and it goes away. No errors, but no saved data either. The info section is reading everything though. Pull Report brigns up a properly layed out window, but again, no data in it.

I'll have 1.4 installed right after I get home or the next time I find an open wireless internet connection.

Hmmm interesting. I'll take a look at that. Does it make the log files at all? Are they empty or do they simply not exist at all? Does the autolog popup window show nothing but it still pops up?

Jeff

They all exist. 1 kb each. And each has a unique.txt name... Just empty.

The window is a white, empty window that's just a little smaller than the "info" screen when it's open. It pretty well covers the screen.

They all exist. 1 kb each. And each has a unique.txt name... Just empty.

The window is a white, empty window that's just a little smaller than the "info" screen when it's open. It pretty well covers the screen.

1up on this issue. I have a serial to usb converter. STI UTEC with Tuner installed.

anyone want to share their myAFRTable.csv? I'll take a stab at creating a STI/vf39 one.

OK. 1.4 in now. New colors! Still no logs or reports. It creates the file but leaves it empty. Errors that came up after meeting the autolog conditions:

Error in ALT_Timer Object required.

Error in Autolog Monitor. which popped up several times in a row.

Ok thanks 2phless, that will help me a lot in determining where the error is. It seems to only happen with STI's so far I guess.

So what do you all think of the new look in 1.4?

Jeff

2phless, i bet you have your fast-logging set to "During Pulls" dont you? I just found an error. It is calling to disable the fastlogger timer control, but I didnt reference which window it was in so it was looking locally in the autologger window, and of course it didnt find it so it has that "Object required" error. Ok that one is now getting taken care of.

The same code typo was in the AutoLogMonitor code, so I took care it that as well. This should be good to go now! New release later today...

Jeff

Mine was set to "Always" and still came up with the same error.

Just found out that I never coded in the condition that checks to see if you even want to autolog or not, it would just autolog 24/7 anyways. +1 for me!

Jeff

Hey Type-C, I discovered what you are talking about. I see now what is causing the error with the settings being saved and im taking care of it right now.

Jeff

Here is a good add-on. How about something audible/visible that happends when preset conditions are met. like too much boost or a combo of timing/Injector pulse. Should be a couple of if/then statements.

Update: New version 1.5 is out! Major bugs fixed. Please check the website updates and read them before using.

http://www.dezignduo.com/UTI/

Jeff

Here is a good add-on. How about something audible/visible that happends when preset conditions are met. like too much boost or a combo of timing/Injector pulse. Should be a couple of if/then statements.

I have actually thought of this but I have not had time to implement it yet. You will definitely see it in a future version.

Jeff

Mine was set to "Always" and still came up with the same error.

When did it come up with the error? what were you doing, etc.

Jeff

Maybe I misspoke. The error was that no data was being logged. I will test out 1.5 a little later.

anyone want to share their myAFRTable.csv? I'll take a stab at creating a STI/vf39 one.

Here is my first attempt at a AFRTable

STi, 93 octane, TBE, vf39 running 17-19psi ...


copy this text into notepad and save it as myAFRTable.csv in your UTI direcroty. Comments/Critiques welcome.


500,14.7,14.5,14.5,0,0,0,0,0,0,0,0
750,14.7,14.5,14.5,0,0,0,0,0,0,0,0
1000,14.7,14.5,14.5,0,0,0,0,0,0,0,0
1250,14.7,14.5,14.5,13.8,0,0,0,0,0,0,0
1500,14.7,14.5,14.5,13.8,0,0,0,0,0,0,0
1750,14.7,14.5,14.3,13.8,13,0,0,0,0,0,0
2000,14.7,14.5,14.3,13.8,13,0,0,0,0,0,0
2250,14.7,14.5,14,13.5,13,13,0,0,0,0,0
2500,14.7,14.5,14,13.5,13,13,13.4,12.7,12.5,12.5,1 1
2750,14.7,14.5,13.8,13.5,13,13,13.4,12.7,12.5,12.5 ,11
3000,14.7,14.5,13.6,13.5,13,13,13,12.7,12.5,12.5,1 1
3250,14.7,14.3,13.5,13.3,13,12.9,12.9,12.7,12.5,12 .5,11
3500,14.7,14,13.3,13.1,12.8,12.8,12.5,12.5,12.2,12 .2,11
3750,14.7,13.7,13.1,13,12.8,12.8,12,12,12,12,11
4000,14.4,13.5,12.9,13,12.8,12.6,12,11.8,11.8,11.8 ,11.2
4250,14,13.5,12.9,12.8,12.8,12.6,12,11.8,11.8,11.8 ,11.2
4500,13.5,13.5,12.9,12.8,12.8,12.6,11.8,11.8,11.8, 11.8,11.2
4750,13.5,13.5,12.9,12.8,12.8,12.6,11.8,11.8,11.6, 11.6,11.2
5000,13,13,12.9,12.8,12.8,12.6,11.6,11.5,11.5,11.5 ,11.2
5250,12.8,12.8,12.6,12.6,12.5,12.6,11.6,11.5,11.5, 11.5,11.2
5500,12.8,12.8,12.6,12.6,12.5,12.5,11.6,11.5,11.5, 11.5,11.2
5750,12.8,12.8,12.6,12.6,12.5,12.5,11.6,11.5,11.5, 11.5,11.2
6000,12.8,12.8,12.6,12.6,12.5,12.5,11.4,11.5,11.5, 11.5,11.2
6250,12.5,12.4,12.4,12.4,12.4,12.4,11.4,11.5,11.5, 11.5,11.2
6500,12.5,12.4,12.4,12.4,12.4,12.4,11.4,11.2,11.3, 11.2,11.2
6750,12.5,12.5,12.5,12.3,12.3,12.3,11.4,11.2,11.3, 11.2,11.2
7000,12.5,12.5,12.5,12.3,12.3,12.3,11.4,11.2,11.3, 11.2,11.2
7250,12.5,12.5,12.5,12.3,12.3,12.3,11.4,11.2,11.2, 11.2,11.2
7500,12.5,12.5,12.5,12.3,12.3,12.3,11.4,11.2,11.2, 11.2,11.2
7750,0,0,0,0,0,0,0,0,0,0,0
8000,0,0,0,0,0,0,0,0,0,0,0
8250,0,0,0,0,0,0,0,0,0,0,0
8500,0,0,0,0,0,0,0,0,0,0,0
8750,0,0,0,0,0,0,0,0,0,0,0
9000,0,0,0,0,0,0,0,0,0,0,0

Hey Type-C, I discovered what you are talking about. I see now what is causing the error with the settings being saved and im taking care of it right now.

Jeff
Thanks :p

Maybe this should be 0.4 isn't of 1.4, or are you going to start over at ver 1 once you get it rock solid. Keep up the good work.

I don't know what I'm doing wrong... I have serial from UTEC to usb at laptop. Downloaded newest version tried every port, the only one that allows me to even try to connect is port 3, and when I do that it just says "syncronizing" and never connects. :( And I let it sit for over a minute to see if it would sync up.

The only thing I can think is that anything I use that is USB when I check the properties it says "Location 0" So maybe it's just that none of those com ports are looking at the USB connections?

Open up your Device manager and check to see what port it is configured to. It might just not be configured to any port at all. If you need further directions pm me and i'll attempt to guide you through it.

Jeff

I don't know what I'm doing wrong...

Try running the UTEC program with Hyper terminal first to make sure you connect, close it then run UTI. If that doesn't work try to use CTRL+ALT+DEL to close Hyper terminal then run UTI.
I've noticed when one of the UTEC programs crash, then I start up Hyper terminal the UTEC is running right were I left it in the crashed program. Log 1 will still be running. Just a suggestion, no idea if it will work.


The download link says I am downloading V1.4 not 1.5, the program itself still says V1.4 when downloaded from your V1.5 link.

Ok. Latest list of items. I can't keep up. I'm pretty sure I'm running 1.5 now. Was it available at 7 am this morning (ET)? That's the one.

Anyhoo. As soon as I start the program and hit connect I get a string of 6 error windows.

Error in RegenerateLogger1 Type Mismatch
Still ALT_Timer Object popping up if auto-log is selected and the conditions are met.

Still blank logs (ex: but I now get another file created that has info stored in it. I guess I have "save tables on shutdown" highlighted.

Tables-11-22-2005-6'52'09.csv

containing this...

Cell Hits
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,0.2,,,,,,,,,,,
1250,2.2,,,,,,,,,,,
1500,1.1,,,,,,,,,,,
1750,2.3,,,,,,,,,,,
2000,2.2,,,,,,,,,,,
2250,0.9,,,,,,,,,,,
2500,1.2,,,,,,,,,,,
2750,1.9,,,,,,,,,,,
3000,,,,,,,,,,,,
3250,,,,,,,,,,,,
3500,,,,,,,,,,,,
3750,,,,,,,,,,,,
4000,,,,,,,,,,,,
4250,,,,,,,,,,,,
4500,,,,,,,,,,,,
4750,,,,,,,,,,,,
5000,,,,,,,,,,,,
5250,,,,,,,,,,,,
5500,,,,,,,,,,,,
5750,,,,,,,,,,,,
6000,,,,,,,,,,,,
6250,,,,,,,,,,,,
6500,,,,,,,,,,,,
6750,,,,,,,,,,,,
7000,,,,,,,,,,,,
7250,,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


Air/Fuel Ratio
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
Tables-11-22-2005-6'52'09.csv

So it does speak to the file system, just not for logging yet. You are doing good. I wish I could create things like this... but if anyone needs a program to print "Hello World"... I'm your man! :cool:

Sorry guys, i forgot to update the actual link. Please revisit the site and download UTIv1.5.zip

My bad

Jeff

...So it does speak to the file system, just not for logging yet. You are doing good. I wish I could create things like this... but if anyone needs a program to print "Hello World"... I'm your man! :cool:

It is working, but the program saved an empty table. I have gotten the tables to fill in fine and save it perfect everytime. Its the table code that i've had very little problem with. I just did it the other day and had it configured to save the tables automatically upon close of program, and sure enough it saved it just as it was told with all the data in tact. If you still have problems with 1.5 please let me know.

Jeff

Hey everybody something is terribly wrong with 1.5, I am getting a truckload of errors. I have tried to make a quick fix to please redownload it if you have already downloaded it as of this moment. If you dont have any luck then please revert back to 1.4 until I can get a chance to fix it for good. Sorry its my anniversary so i cant be coding :-(

Jeff

You deserve a break by now. Besides, we don't want you to lose your computer in the divorce, so go make nice with the spouse :p (making an assumption based on the word "anniversary")

Well I brought my laptop to work today and I have made a bunch of changes to the code. I have found several little bugs that were semi-hard to find, but im re-reading every line of code and checking to make sure everything is good. I think I got the bugs out this time but there will always be something. I have re-sorted some code, simplifying the programming and restructuring some stuff. I was able to remove some redundant stuff, thus shrinking the program down in size somewhat.

If someone with a wrx without a tuner could capture their dashboard output in hyperterminal and then send me the text file then I can go ahead and program in compatability for you with the dashboard mode. Your logger-1 mode should work now even if you dont have the tuner and soon with your help the dashboard mode will too.

Hopefully i'll have a new version out today, I really want you all to have this one im working on now instead of the poop that i let out yesterday, it stunk!

Jeff

http://www.yourapainintheass.com/downloads/UTI5.jpg

Been like that since the start and nothing I can do about it.

fatray - thats because when the program launches, it sets its height to a certain value. In windows xp, the programs top bar where it says "UTEC Interface v1.5" is taller than in windows 98 or even in xp if you have it appear like windows98. I think I know of a way to fix it so i'll try to remember that when i get to coding.

Jeff

Hey all, big updates today. I have fixed some major issues. Some were from new stuff that I did for 1.5 and some were from previous versions. I found out why the log report wasnt saving, just a small typo.

Here is what I have tested just in the past hour while driving:

---Works---
Logger-1 mode
Dashboard Mode
Autolog popup window
autolog file saving
Pull report saving
Settings menu
Fast logging - always
Fast logging - just during pulls
Termination delay
Minimum lines requirement
Autolog conditions to intiate
Autolog conditions to save file
Tables
Auto-save tables on shutdown
auto-save pull report on shutdown


---Buggy---
Tables dont update once you save them


Thats about it for now. I think a solid version 1.5B is going to be out later today, expect very few bugs, as this version is actually ROAD TESTED, most of them I dont have time to and i "wing it" so to speak.

Jeff

Ok guys go try 1.5B, its out and road tested. As always keep me posted of any bugs, this version should be a good one though.

Jeff

Jeff: very cool that you're doing all this. Thanks!

Better! No errors and I got a couple of set of .csv table files. I like those a lot. A very good way to quickly peruse averages over a run (and easier than uploading a log to logmapper... which is also very cool.)

Still no log, but no errors while trying to create one. And this times I got 8 kb of nothing instead of 1kb of nothing. It's like its saving in invisible ink (actually it seems to just be saving line feeds).

At any rate. You are getting on top of it. Very sweet. Have a good thanksgiving.

so your autologs still dont work? I just used the program today and both the autologs and log reports save just fine. Perhaps it is because you have an sti..i'll see if I can find anything that could be causing this.

Please answer me these questions:

Do you have it set so the autolog pops up?
Does it actually pop up?
Does stuff show up in it?
Do you later see the pull in the pull report window?
Does the Pull Report Save work correctly?

Jeff

I have autolog checked but I don't think I had the autolog pop-up set. I have both knock alerts unchecked. I see the bottom of the window show that it's in record or delay mode once the critera for a log is met.

The pop-up was always showing a blank window with a cursor on the left side slowly moving down line by line 'til the timeout was over.

The report window has always been blank, but has the 3 buttons at the top to exit, save... or whatever the third option is. I've never hit the save since it's always been blank.

I'll go through my parameters tomorrow and see if something might be sending an odd signal. I don't think my auxillary solenoid is set to activate anymore. But it does send valid info and nothing locks it up now. The charts are acurate as far as I can tell, and they log well above where they were hanging before.

Here's a sample. The format is off outside of excel. In the spreadsheet it is layed out perfectly. These tables are really cool.

Cell Hits
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,12.4,,,,,,,,,,,
1250,279.6,1.5,,,,,,,,,,
1500,19.4,2.3,,,,,,,,,,
1750,15.4,0.2,,,,,,,,,,
2000,45.4,0.1,,,,,,,,,,
2250,60.2,2.2,,,,,,,,,,
2500,141.4,7.1,,,,,,,,,,
2750,396.5,8.2,0.6,,,,,,,,,
3000,361.9,11.8,2.2,,,,,,,,,
3250,640.3,37.3,4.8,0.1,,,,,,,,
3500,955,57.1,6.6,2.4,,,,,,,,
3750,981.7,92.2,14.1,8.9,1.9,0.8,,,,,,
4000,595.3,117.8,7.1,10.1,2.1,1.2,,,,,,
4250,213.5,93.3,4.9,4.6,0.1,,,,,,,
4500,37.5,55,3.3,3.4,1.8,0.3,0.5,0,,,,
4750,38.4,52.3,4.5,3.1,1.4,1.3,1.9,1,1,,,
5000,44.2,25,2.7,2,1.8,1.9,1.5,,2.2,1.2,,
5250,27,10.2,2.2,0.4,0.9,0.5,0.5,,1.6,2.6,,
5500,2.6,3.4,0.4,,,0.8,1.1,,0.4,3.8,,
5750,0.3,,1.4,,,0.2,0.5,0.6,3.8,1.4,,
6000,,,0.2,,,,,0.4,4.5,2.2,,
6250,0.1,,,,,,,,5.4,1.7,,
6500,1.9,0.8,,,,,,,7.1,1.1,,
6750,0.5,0.2,,,,,,,9.3,,,
7000,2.3,,,,,,,,1.7,,,
7250,0.2,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


Air/Fuel Ratio
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,15.13,,,,,,,,,,,
1250,14.95,19.11,,,,,,,,,,
1500,16.99,19.11,,,,,,,,,,
1750,17.03,20,,,,,,,,,,
2000,16.91,13.97,,,,,,,,,,
2250,15.81,14.03,,,,,,,,,,
2500,15.01,14.39,,,,,,,,,,
2750,14.68,14.66,16.54,,,,,,,,,
3000,15.05,15.69,16.04,,,,,,,,,
3250,14.85,14.94,15.05,14.45,,,,,,,,
3500,14.61,15.1,14.47,14.27,,,,,,,,
3750,14.72,14.97,13.92,13.53,13.14,13.34,,,,,,
4000,14.58,14.79,13.62,13.28,13.02,13.33,,,,,,
4250,14.46,14.56,13.69,13.29,13.02,,,,,,,
4500,14.74,13.81,13.62,13.26,13.03,13.23,12.03,11. 62,,,,
4750,14.25,13.4,13.11,13.15,12.51,12.44,12.09,11.6 2,11.7,,,
5000,14.26,13.42,12.95,12.7,12.04,11.72,11.86,,11. 65,11.47,,
5250,14.08,13.63,12.94,12,12,12.22,11.84,,11.22,11 .24,,
5500,12.33,14.48,12.3,,,14.33,11.49,,10.94,11.03,,
5750,12.46,,11.88,,,14.33,11.12,12.09,11.02,11,,
6000,,,11.56,,,,,12.09,11.03,11.08,,
6250,10.86,,,,,,,,11.13,11.16,,
6500,10.69,13.17,,,,,,,10.95,11.08,,
6750,12.84,13.17,,,,,,,10.96,,,
7000,11.39,,,,,,,,10.6,,,
7250,10.56,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


Injector (IDC)
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,2.3,,,,,,,,,,,
1250,1.9,26.6,,,,,,,,,,
1500,7.4,24,,,,,,,,,,
1750,10,16.8,,,,,,,,,,
2000,6.2,8.6,,,,,,,,,,
2250,6,8.9,,,,,,,,,,
2500,6.4,12.4,,,,,,,,,,
2750,7.5,7.7,10.8,,,,,,,,,
3000,7.2,8.6,11.6,,,,,,,,,
3250,6.6,9.2,13.8,17.2,,,,,,,,
3500,7.1,9.9,14.5,18.1,,,,,,,,
3750,7.7,11.4,15.4,19.3,20.3,24.9,,,,,,
4000,8.2,11.9,16.7,19.7,19,25,,,,,,
4250,8.4,12.6,16.9,22.1,30.8,,,,,,,
4500,8.8,15.8,21,25.2,32.5,38.3,42.9,49.6,,,,
4750,9.5,16.4,24.4,29,35.4,39.8,45.9,49.6,55.5,,,
5000,11,15.6,27.3,33.3,34.5,42.1,47.1,,58.3,58.8,,
5250,12.3,18.1,26,26.8,43.9,44.8,54.4,,59.7,60,,
5500,21.3,19.9,34.3,,,54,56.3,,62.5,62.9,,
5750,9.3,,27.4,,,54,58,61.1,63.6,65.4,,
6000,,,22,,,,,61.1,65.7,66.6,,
6250,39.1,,,,,,,,68,68.9,,
6500,26.1,6,,,,,,,70.6,69.6,,
6750,70.3,6,,,,,,,72.3,,,
7000,72.7,,,,,,,,73.6,,,
7250,72.4,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


Boost (PSI)
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,-9.4,,,,,,,,,,,
1250,-9.4,-8.9,,,,,,,,,,
1500,-9.3,-9,,,,,,,,,,
1750,-7.8,-9.3,,,,,,,,,,
2000,-7.7,-8.2,,,,,,,,,,
2250,-7.3,-6,,,,,,,,,,
2500,-7.8,-3.7,,,,,,,,,,
2750,-6.8,-3.2,1.2,,,,,,,,,
3000,-7.5,-3.5,1.4,,,,,,,,,
3250,-7.7,-3.4,2,3.5,,,,,,,,
3500,-6.7,-3.7,2.1,3.7,,,,,,,,
3750,-6.3,-2.9,1.5,4.5,6.6,8.3,,,,,,
4000,-6.9,-2.9,3,5.5,7.1,8.3,,,,,,
4250,-7.9,-3.6,2.3,4.7,4.4,,,,,,,
4500,-6.5,-2.2,0.8,3.7,3.8,3.3,7,10.6,,,,
4750,-5.6,-2.8,1.3,1.7,3.3,4.5,7.5,10.6,13.6,,,
5000,-5.8,-3.3,1.5,2.6,6.7,8.3,6.5,,14,17.4,,
5250,-5.2,-2.6,4,9.7,3.6,7.5,8.7,,12.5,19.1,,
5500,2.4,-3.6,1.7,,,3.3,8.4,,17.7,20,,
5750,-3.3,,1.9,,,3.3,7.2,5,18.1,20.7,,
6000,,,2.1,,,,,5,17,19.5,,
6250,17,,,,,,,,18,18.5,,
6500,17.2,10.1,,,,,,,18.6,19.6,,
6750,18.5,10.1,,,,,,,18.9,,,
7000,18.3,,,,,,,,18.6,,,
7250,18,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


Target AFR
,0,10,20,30,40,50,60,70,80,90,100,
500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12. 2,12,
750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12. 2,12,
1000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
1250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
1500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
1750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
2000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
2250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
2500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
2750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
3000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
3250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
3500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
3750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
4000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
4250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
4500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
4750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
5000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
5250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
5500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
5750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
6000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
6250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
6500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
6750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
7000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
7250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
7500,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
7750,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
8000,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,
8250,14.7,14.5,14,13.8,13.5,13.2,12.9,12.7,12.5,12 .2,12,


AFR Difference
,0,10,20,30,40,50,60,70,80,90,100,
750,,,,,,,,,,,,
1000,0.43,,,,,,,,,,,
1250,0.25,4.61,,,,,,,,,,
1500,2.29,4.61,,,,,,,,,,
1750,2.33,5.5,,,,,,,,,,
2000,2.21,-0.53,,,,,,,,,,
2250,1.11,-0.47,,,,,,,,,,
2500,0.31,-0.11,,,,,,,,,,
2750,-0.02,0.16,2.54,,,,,,,,,
3000,0.35,1.19,2.04,,,,,,,,,
3250,0.15,0.44,1.05,0.65,,,,,,,,
3500,-0.09,0.6,0.47,0.47,,,,,,,,
3750,0.02,0.47,-0.08,-0.27,-0.36,0.14,,,,,,
4000,-0.12,0.29,-0.38,-0.52,-0.48,0.13,,,,,,
4250,-0.24,0.06,-0.31,-0.51,-0.48,,,,,,,
4500,0.04,-0.69,-0.38,-0.54,-0.47,0.03,-0.87,-1.08,,,,
4750,-0.45,-1.1,-0.89,-0.65,-0.99,-0.76,-0.81,-1.08,-0.8,,,
5000,-0.44,-1.08,-1.05,-1.1,-1.46,-1.48,-1.04,,-0.85,-0.73,,
5250,-0.62,-0.87,-1.06,-1.8,-1.5,-0.98,-1.06,,-1.28,-0.96,,
5500,-2.37,-0.02,-1.7,,,1.13,-1.41,,-1.56,-1.17,,
5750,-2.24,,-2.12,,,1.13,-1.78,-0.61,-1.48,-1.2,,
6000,,,-2.44,,,,,-0.61,-1.47,-1.12,,
6250,-3.84,,,,,,,,-1.37,-1.04,,
6500,-4.01,-1.33,,,,,,,-1.55,-1.12,,
6750,-1.86,-1.33,,,,,,,-1.54,,,
7000,-3.31,,,,,,,,-1.9,,,
7250,-4.14,,,,,,,,,,,
7500,,,,,,,,,,,,
7750,,,,,,,,,,,,
8000,,,,,,,,,,,,
8250,,,,,,,,,,,,
8500,,,,,,,,,,,,


This CSV was created by 'UTEC Interface' BETA program
Created by Jeff C, Navybluesubaru at Nasioc.
I Can be contacted at cashioja@kennedy.navy.mil

2phless, does your LOGGER-1 box show the correct information? I am really curious why it doenst seem to autolog with an STi. Also, are you in Logger-1 mode or dashboard mode?

Jeff

Hey 2phless, I think I finally found the mistake that kept STi owners from logging. If you had your Logger-1 output set to the first option, "Leave both stock O2 and WBO2 readings in normal position" , then the program would check to see what your carmodel was set to. It was looking for either "WRX5" or "STI11c". Well, I screwed up there, because the correct variable value for those who are configured to an STI is "STI11C". So the code was checking what your carmodel was and it didnt match either one because it was looking for the wrong thing in the first place. I have fixed it now and you should see the program "wake up" so to speak. I hope this helps you out!

If you want a temporary work-around, try setting your Logger-1 output to the 2nd or 3rd position for now until i release the new version im working on.

Jeff

PS - Overboost, Overheating, and RPM audible warnings are in the works. They should be avail. in the next update.

Jeff

I do have the stock positions for wideband set. I'll go back and adjust that and see what happens. Should I go into the ini file and capitalize the 'c' in STI11c? Or is it deeper than that?

One thing I've noticed but never remembered to bring up. The "check mark" that appears beside the WRX or STi choices in that dropdown menu. It'll stay next to the WRX choice like it should. When I choose STi it shows a check, but it's gone the next time I drop that menu down. Once I chose STi, things started to work so I never put much weight on it. Might be related though.

Didn't mess with the 'c' <--> 'C" swap but trying the other two settings made things happen. Bad things mostly, but things. The line that looks like it is supposed to show data as it's recorded did, actually have data in it with the second O2 location selected. I thought "sweet!".

Then I switched from logging via dashboard to logger 1 (or perhaps vice versa ) and then all hell broke loose.

Errors out the ying yang and I was driving at this point so I couldn't see the errors. Had to reboot at one point and when it came back it didn't have full control over the cursor anymore. :huh: It was dancing all over my sign in screen and stayed haywire after I'd booted into my user profile, to the point of opening shortcuts randomly and moving the windows around. Like I'd gotten "remote assistance" from an epileptic. Crazy. Took a complete cold boot to bring the PC back to normalcy. So it must have written something whacky to some interesting memory addresses.

No big deal. Just hard to concentrate on driving when I'm fishing for my inverter to kill power :lol: .

I haven't had time to see what, if anything, recorded since we are rebuilding a bathroom for the holidays :mad: . But I'll check it out after my next trip to home depot.

I am having issues with the settings, as far as when to save to the file and when not to. I am going to re-organize it today so it doenst cause weird bugs. I wasnt going to recommend changing the letter in your ini file, although im not 100% sure what would happen. I dont know whats up with your computer going bonkers, that sounds pretty crazy!

I am also going to rework the connection and syncronization code because I was having problems myself syncing up to the utec, and while trying to do 1/4 mile runs! I was pissed to say the least. Anyways I think I know what I have to do, no biggie. I managed to run a 13.2@105.3 with a 1.93 '60. Not too bad, but i've pulled 107.6 in the past and that was making less power so I should've been going quite a bit faster but oh well who knows.

I'll keep everybody posted on the program, should have a re-worked version out tomorrow.

Jeff

Well the settings thing has been worked out i believe. I can test it tomorrow.
Also, Im working on the syncronization process, trying to make it more reliable and not just retarded like it is now. If you have no problems currently with syncronizing or you do have problems plz let me know, I am curious how hard it is for users to sync up.

Jeff

The first time I set and "update" all the settings after loading a new version, the sync never happens. Well, it says it's synchronized but nothing is going on in the info window. But I just exit and restart the app and it syncs right up from then on.

2phless, I was having the exact same problem. It was also happening to me because of a different issue in the new version im writing.

UPDATE - For all of those who wished that this would bridge the UTEC to your other external WBO2, your day is comming very soon. I am currently adding support into the program for it, and as soon as I get a log from somebody who has one then I can seal the deal.

Here's what you do: Sync up with your WBO2 via hyperterminal. Capture everything to a text file, just like when you are using the utec and logging. Capture everything that you do wiht the wbo2, starting from the moment you connect up through the point where it is logging on your screen. Once you get that, stop the capture and email me the file. With that I can analyze what's going on communication-wise and code appropriately.

Email to: cashionm@bellsouth.net

More things have been added, such as the ability to modify the logger-1 output by replacing the stock ignition value with your coolant temp or air intake temp. This only works when you are in dashboard mode and will move over the ecu ignition value to where your utec timing value is, whenever it would say "ECU". I have recently made it so that the autologger doesnt capture lines while you are in termination delay, but im going to make it an option in the settings. With it on you can use it to gauge how fast you shift or how low your boost drops or whatever else you might want to see it for.

Hopefully I'll have it out tomorrow, with or without the Bridge function. Its all up to you guys!

Jeff

:lol: :lol:
Sorry for being out of text. :banana:

Im giving Utec alot of consideration i mean alot im leaning on Ecutek though right after the seasons over.
Future plans for my wrx i have know ideal something in the stage 2 range with or without mods. <Big 16g :)

Ive even heard about some software that will eliminate AFR ratios thats being converted over or subarus only im skeptical of its uses stock or modded as much as the guy that will have his first sample in the next few weeks.



For those wrx owners without a tuner, when you are running rich does it say "RICH", or "Rich" or "rich"?? Also does it ever say "Lean" or anything like that? I cannot remember, its been too long. The quicker I get the answer to this the quicker I can program compatability into my program for you.

Jeff

Update: Ok guys, Version 1.6 is out on the site. Major bugs have been fixed and a lot has been re-vised, also new features have been added.

Please read the version history update on the site before you run the program. Also, you WILL NEED TO update your .ini File with the one provided and just re-do your settings the first time.

Road testing is complete, this version is golden! It syncs up in literally 1 second...switches from logger-1 to dashboard almost instantly, and auto-logs perfectly with any option enabled/disabled as you desire.

Please let me know how well this one works for you all!

Jeff

Most excellent! Looks like you're on top of it. Logs are functional and I dig the air temp option. Logger and dashboard connection is smooth. No errors. I haven't tried all the settings yet but I'll work through them soon.

3284 -10.0 2.0 0 00 00 8.0 4.6 ECU. -2.2 ECU. 1.6 20.0
3217 -10.0 1.9 8 00 00 8.0 13.0 ECU. -2.3 296.00 2.1 20.0
3214 -9.5 2.4 17 10 00 8.0 8.5 +29.1 -2.2 248.00 2.3 20.0
3255 -7.9 2.9 33 10 00 6.0 13.8 +29.1 -3.3 200.00 2.6 20.0
3264 -5.4 3.1 43 10 00 7.0 16.3 +28.9 -3.3 210.00 2.7 24.47
3271 -2.3 3.3 84 20 00 7.0 19.4 +21.6 -4.4 215.00 2.8 16.62
3333 +0.6 3.4 100 30 00 7.0 21.1 +15.7 -4.7 215.00 2.9 14.11
3356 +3.2 3.6 101 40 00 7.0 24.0 +14.0 -4.6 215.00 3.0 12.99
3415 +5.1 3.7 101 40 00 7.0 26.1 +14.0 -4.8 215.00 3.1 12.68
3439 +7.4 3.9 101 50 00 7.0 31.5 +14.0 -4.2 215.00 3.3 12.64
3565 +9.9 4.1 101 70 00 7.0 38.4 +13.9 -1.5 215.00 3.5 12.46
3671 +12.9 4.2 100 80 00 8.0 45.0 +13.0 -1.1 215.00 3.6 12.05
3720 +16.0 4.3 101 90 00 7.0 48.4 +12.3 -0.9 215.00 3.7 11.52
3753 +18.9 4.3 101 90 00 7.0 48.7 +12.7 -0.8 215.00 3.6 11.23
3935 +20.8 4.3 100 90 00 7.0 50.9 +13.2 -0.7 220.00 3.7 11.17
3926 +21.6 4.3 100 90 00 8.0 49.2 +13.6 -0.7 220.00 3.7 11.23
4105 +22.0 4.4 87 90 00 8.0 55.3 +14.1 -0.7 217.00 3.8 11.24
4050 +21.0 4.3 25 00 00 8.0 44.4 ECU. -3.0 232.00 2.4 11.17
4156 +16.9 2.7 15 00 00 7.0 8.9 ECU. -3.0 312.00 1.7 10.76
4089 +10.9 1.8 12 00 00 7.0 3.8 ECU. -3.2 ECU. 1.1 11.12
4100 +3.3 1.4 0 00 00 8.0 3.6 ECU. -3.0 ECU. 1.2 14.00
4120 -3.8 1.6 0 00 00 7.0 3.6 ECU. -3.0 ECU. 1.6 22.77

The 8.0 7.0 stuff in the middle is ait in celcius.

I'll try to remember and get some shots of it in action on the road tomorrow. Very very nice.

Works good:banana: except for the tables. They appear to be about 500 RPM's off. At ~750 and ~850 RPM there should be more logging at the 750 - 1000 RPM range instead of at the 1250 - 1500 RPM Range. How about UTEC Map Versioning with a GUI to make changes to maps and store them? Also how about a AFR offset to compensate for the lag in some Wideband sensors? Sometimes the true AFR lags maybe 2-3 lines behind.

I was going to mention being able to set the AFR offset, but I was gonna give him a break first. :lol: It'd really be offsetting the rest of the lines I'd guess.


I haven't checked the table-to-real life connection. I still have my settings kinda weird so I can get more recordings and pop-ups etc... I'm not concerned with much outside of function. I'll see if I can come up with the same issue a little later this morning.

Can you bump up the RPM warning to 8500, some of us do rev to 8,200 rpms once in a while.
You know how the UTEC has a shift light output. Well why don't you add a shift light to your program. Have the program window flash at certain RPMS.

fyi. The past 4 versions ive tried have had alignment problems:


http://njektd.com/subaru/uti_1.jpg

AaronWRX
Looks like you have some of the font settings under your display off a bit. Try playing around with the Display Properties.

2phless - you just reminded me; I forgot to make it so that if you replace your stock ignition value with something else, to move over the value of it whenever your running off of the stock timing. I see in your logs the utec timing says ECU but you have no idea what that is because its being replaced. I ment to do that and just forgot.

rainmanjam - I rescaled the tables a few versions back from 500-900 down to 750-8500. The reason was because they didnt fit in lower resolutions for those with carputers. I figured that what I removed was useless anyways. I think i might have forgotten to re-adjust where the data is logged at after doing that so they might very well be off by a row, i'll double check.

fatray - bumping up the rev limiter warning is no problem. I have thought of shift-lights but you cant really see the screen well enough for it to get your attention so I moved first for audible warnings. If you have an fm modulator or aux input in your stereo then you can hear it quite well.

Comming up in future versions is total audio immersion. Im talking like everything is spoken like "Syncronized" or "Auto-Logging" or "Log recorded" or "Shift" or "Overboost". Some things can be simple beeps but I want other things to be spoken. Im tossing ideas around in my head. Im thinking that if you have no screen then you could use the program blind literally and be totally ok. It will also be cool to be driving and have your car(my program) talk to you and tell you that its autologging or telling you when to shift.

Thanks for the input guys, i appreciate it.

AaronWRX - what rainmanjam said. It works fine if you dont touch your display settings.

Jeff

Sorry guys, I found the table error and it is drawing the information 2 rows down from where it should. This is a result of me removing the 250 and 500 rows. It is getting fixed as I type this.

Just fixed the deal with replacing the "ECU. " with the actual ecu timing value if you are replacing the stock value with air or H20 temp.

Just adjusted the rpm rev warning. From 6500 to 8500 it is in steps of 100rpm. Happy revving!

*The settings panel is going to get a slight overhaul soon. I want to widen everything to better fit the screen and allow for more options. I have a ton in my head that im toying with and I want you to all enjoy them.

Jeff

AaronWRX - what rainmanjam said. It works fine if you dont touch your display settings.

Jeff

hmm that did fix it. too bad though. I run my laptop display at 1400x1050. That gave me the realestate i needed and setting the font to "Large size 120 dpi" kept my eyes from going cross eyed. I guess i cant have my cake and use UTI too. :)

aaronwrx - im currently making it so that the settings panel is larger and easier to use. I am limited though to having the program work perfect in an 800x600 screen.

Jeff

Update: Version 1.6B is out. All the corrections mentioned above have been made. The settings panel is also re-done. This version is nearly the same to 1.6 just with the above mentioned tweaks.

Jeff

The speech is really comming around. I have 7 sounds so far. They sound pretty cool. There is going to be a tab in the settings window that you will use to turn it on/off. Perhaps it will be done by tomorrow.

Jeff

Well on my way to work today I tested out the speech functionality. It works just as designed. When I roll on the gas and meet my logging conditions, my laptop says "Logging". It also announced when It launched, Connected, and synchronized. Very very cool, the feedback is nice. I can just turn on the computer and not even open the screen. I will know that im sync'd up even if I cant see it. I think you will all get a kick out of this. Also, you can turn on/off each different sound so that you can custom tailor it to your needs/wants.

I'll probably release it this afternoon sometime. There is something I want to do with the audible warnings too so I have to do that as well, and I want to put in a sort of "Peak Boost" hold that retains what the max boost that you hit was, just like on any standard boost controller. I just dont know where to put it on the window. Well thats it for now....


Jeff

Just used your software to fix my x-over hesitation in one felled swoop. It wasn't bad before but I lost the slightest bit of power whenever the utec took over. Watching it happen live let me target the issue. Made it easier to wrap my head around than perusing a log and trying to remember the circumstances. Big number that transition smoothly is key.

I stopped in a parking lot, made what I though would be good corrections. And they were. Smooth sailing now. Very nice.

One idea. You have those substitutions of AIT and Water temp for a timing value. Can you add an option to have it just repeatedly place the map number there? I like to set a few similar maps up in different locations, then run some loops around town and try different ones on the fly. Then I get home and forget the order. Having the number on the map would help a lot on those occasions.

If that isn't hard, other things like the aux solenoid output, and all that dash stuff you can't get from hyperterminal very easily. They'd almost all be useful on occasion.

Otherwise it's working great. Thanks!

2phless - Great to hear your positive experience. I can have those item substitued, that is extremely easy; in fact its as easy as it was for you to type about it. The only thing is that in order for the map to be the same width I would have to make the item going in that spot be the same width as the stock ignition value, 5 characters. If I did otherwise and allowed it to be bigger then it might cause problems in other programs, but is still easy to code if users are willing to take that chance. I'll See what I can do, and the map position will work, it will just say "Map 1" which happens to be 5 characters so its no problem. Dont worry, I can make it work.

I tested the speech again today and it works great. I think you will all hail 1.7 just as much as 1.6B, it is finally comming together.

I'll post more later today.

Jeff

The thing about AFR offset is that you cant simply retain the afr value for a few lines, you have to retain the rest of the log instead. At any certain time, everything is correct except your afr, you are reading what happened in the past by anywhere from 1/10 of a second or more/less, but anyhow it was in the past. What you need to do is match it up with a logger-1 line that also happened in the past. What this will do is basically cause the program to lag behind. You will not see what the active data is because its being withheld to show later when the afr mixture reaches your sensor.

If a user is willing for everything to be delayed just to meet up with its proper afr reading then thats fine but that is how it is would have to be.

Jeff

Ok I added the ability to show the current switch position instead of stock ignition value. This obviously only works in dashboard mode.

I also fixed a small bug in drawing data in the tables.

I think that comming up soon will be audible shift commands which are programmable.
Also, im thinking of a built-in utility that will re-tune your maps for you. You will have to download the map you are running and let my program open it, then it will compare your afr with your target and update your map with its suggested value. Keep in mind that if my program is doing this then that means that im basically tuning your car. My initial idea is that if you are running 12:1 instead of 13:1, then 12-13 = -1, so minus 1 from your fuel map. While that may not be entirely accurate and im not saying by any means that it is how to tune a car or a good method, but to some degree it has truth behind it. If doing it takes you from 12:1 up to 12.5:1, then you are now closer to your target, no? So if you now have to minus 0.5 then you will be even closer. As long as it doesnt cause you to overshoot. I will obviously add in something that is like a "sensitivity" setting that modifies just how drastic the program changes your map, whether its 1:1 or 0.2:1 or whatever, you decide.

1.7 out in about 20 minutes

Jeff

+1 on the delay. I don't think i'll be doing any real time updates of my maps durning a pull.

How about making the value of the edit adjustable as well. some people may want to do a +/- .3 rather then a +/- 1. How about a range between .1 and 2. Or, even better, adjustable based on the difference in AFR like a
9:1 AFR in the log and a 12:1 AFR target will yield a -1 change in the fuel map but a 12.5:1 AFR in the log and a 12.3:1 AFR target will yield a +.1 change in the fuel map.

Delay feature will probably be in 1.8. I would guess another 2 days or so.

Jeff

UPDATE: Version 1.7 is out. Go get it!

I seriously think you will all get a kick out of the audibles. Do try it!

Jeff

No hot chick for the audio....damn....but the improvements are AWSOME.. Thanks...

Also, im thinking of a built-in utility that will re-tune your maps for you......it will compare your afr with your target and update your map with its suggested value
I would hesitate about going there if I were you. The logic for that isn't exact (x percent maf vs x percent fuel vs load), not to mention all the variables and the liability.

I for one wouldn't want it editing my maps. Now, if it showed suggestions, that would be great. Kinda like if asking for a favor vs pushing your gf's head in your lap; results could be devastating!

+1 on the delay. I don't think i'll be doing any real time updates of my maps durning a pull.

How about making the value of the edit adjustable as well. some people may want to do a +/- .3 rather then a +/- 1. How about a range between .1 and 2. Or, even better, adjustable based on the difference in AFR like a
9:1 AFR in the log and a 12:1 AFR target will yield a -1 change in the fuel map but a 12.5:1 AFR in the log and a 12.3:1 AFR target will yield a +.1 change in the fuel map.
And that depends on how you're scaling (or not scaling) your maf. Jus to reiterate, this can be extremely dangerous. And you know there is always someone who doesn't rtfm and blows their stuff up.

I just started it on my laptop not hooked to UTEC right now and the speach is playing non stop, ALL OF THEM at the same time. Can't stop it.


EDIT
Ok it stopped. Quiting and restarting fixed it.

And that depends on how you're scaling (or not scaling) your maf. Jus to reiterate, this can be extremely dangerous. And you know there is always someone who doesn't rtfm and blows their stuff up.

Oh I know.. Thats why I got a UTEC.. Read and ye shall know...

fatray - It does the same thing on my laptop if I disable the "UTI Launched" sound. On my desktop it doesnt do it though...weird.

Jeff

Just used your software to fix my x-over hesitation in one felled swoop. It wasn't bad before but I lost the slightest bit of power whenever the utec took over. Watching it happen live let me target the issue. Made it easier to wrap my head around than perusing a log and trying to remember the circumstances. Big number that transition smoothly is key.

I stopped in a parking lot, made what I though would be good corrections. And they were. Smooth sailing now. Very nice.

One idea. You have those substitutions of AIT and Water temp for a timing value. Can you add an option to have it just repeatedly place the map number there? I like to set a few similar maps up in different locations, then run some loops around town and try different ones on the fly. Then I get home and forget the order. Having the number on the map would help a lot on those occasions.

If that isn't hard, other things like the aux solenoid output, and all that dash stuff you can't get from hyperterminal very easily. They'd almost all be useful on occasion.

Otherwise it's working great. Thanks!

Can you give us more detail about what you did to fix your hesitation? Was it a timing issue as most suggest/believe or something else the interface let you see clearly?

****
9-2x project car web page: http://9-2x.dynamic-dyno.com

The map tuning thing is just a thing that will show you what the program suggest you tune your map to. It wont actually re-do your map and upload it or anything like that.

What I am going to add is something that shows you your overall tune, based off of how far off you are from your target afr, add all the cells up(absolute value for each) then divide by how many cells are populated. This will give you the average amount that you are off by, then score you based on that number. This way you can do some runs, see your tune quality, then adjust your map accordingly, do more pulls and check your new tune quality and see how much you improved. How cool is that?

Jeff

No hot chick for the audio....damn....but the improvements are AWSOME.. Thanks...

Expect to see a choice of voices in the near future...including a woman :cool:

Jeff

I would hesitate about going there if I were you. The logic for that isn't exact (x percent maf vs x percent fuel vs load), not to mention all the variables and the liability.

I for one wouldn't want it editing my maps. Now, if it showed suggestions, that would be great. Kinda like if asking for a favor vs pushing your gf's head in your lap; results could be devastating!

I agree with TypeC. Suggested map changes would be much safer for all involved although not nearly as cool as auto-tuning. With all the good work you've done I'd hate for you to lose interest in the UTEC/WRX community due to a lawsuit.

****
9-2x project car web page: http://9-2x.dynamic-dyno.com

There is no way to actually do real-time tuning with the UTEC. I can only make suggestions to your map.

Jeff

The version of "auto-tuning" I was picturing was not really real time but automated inputing of new values into the fuel map based on a log file. The fuel map would be changed and saved once without the user keying in the new values manually. A new log file would then be acquired and used to make a further "singular" adjustment to the map cells. This would still be dangerous territory to tread in. Suggestions, as you plan, without directly adjusting the maps sound great to me.

****
9-2x project car web page: http://9-2x.dynamic-dyno.com

Update: I just added a nice feature that I was talking about earlier. It analyzes your afr difference and in a nutshell it gives you a Tune Quality for your entire Table, not just the current logger-1 line. It sums up everything except the 0% column and gives you a final score, in real-time. This is very handy for logging pulls and getting a score, then re-tuning and doing more pulls then seeing if your score improved. I thought of this feature today because I wanted a way to tell if I made any real progress in my tuning efforts. I am going to try it out tomorrow when I test out the new map I made which was based on my programs table afr difference results.

Jeff

Good work Jeff, hopefully I'll have a chance to test it out tomorrow.

Of course a cold front would come through town today. It is going to throw off my afr by a bit so as to make it difficult for me to make a solid comparison of before/after with my new map. Anyhow Im sure to figure something out. I'll post up a revision this afternoon.

Jeff

So far so good. Everything is smooth, fast. The resolution on the setup screen got bigger, which is fine... don't know if that was on purpose. I only use that sitting still, so the smaller setup screen was fine too. Just my take on it though.

Thanks for the map number option. Perfect. Working on making an AFR reference table for my setup. I like it a bit richer. I'll post it up here once I get it smoothed out.

The voices are nifty. Problem is it plays through my stereo (along with the knock sensor audio also through the PC) so XM usually wins out over the drone of the detcan.

+1 for adding the sexy (female) voice, and a rap version :lol: . Japanese warnings would be extra jDm-TitE!1! :banana:

Although the current colors are very good and very easy to read at a glance.... maybe some skins options? I have my desktop set to kinda match my interior. (Lots of red and black and blue) (no pink!)

How long did you have it hooked up to the UTEC when you were driving NavyBlueSubaru? Happened to me 2 times yesterday. After about 10 minutes UTI froze then it was like I was right clicking the mouse on various parts of the screen really really fast over and over again. Then the computer just shut off. This also happened in an older build of UTI. Rebooting and plugging in my USB to Serial adapter caused the PC to shut down again. Only after removing the cord altogether from the TUNER and rebooting did it work again for my 10 minute drive home.
This never happened using Hyper-terminal, or Auto-Logger.

I just downloaded UTI.
I opened it up on my desktop and I can't see a full window like the screen shot you posted.
Is this because I don't have a Utec hooked up? Is there a way to resize the window?

TMS

when i launch this new version the audio goes into an very annoying garbled loop.

................

.....

AaronWRX - My laptop does the same thing if you dont have it set to play the "UTI Launched" sound. It doesnt do it on my desktop so I havnt figured it out yet. I slightly rewrote how sounds are played so that might have fixed it.

TheMadScientist - You must click on "Info" for it to bring up the information like rpm, boost, etc.

fatray - I have had it running for longer than that and I havnt had it crash on me yet. If I have data going into my usb/serial converter before windows boots up then it will crash when it closes the port, so what I do is have it plugged into the computer first, then when UTI launches, I plug in the serial plug and it will almost instantly synchronize. Try it in that order and see if you can get it to crash again.

2phless - I re-did the settings so that it was able to hold more stuff and to be bigger and easier for those with carputers to read.

The main form can be made to be skinnable, however its not like that now. It could come to the point where people actually are making skins for this, which would be pretty cool. I'll see if I can get that in the next version later today.

When I get home today I'll let everyone in on how its going and when to expect a new revision.

BTW, after using my program to better tune my fuel map, I tested it today to work and to where I am at now(eating lunch) and the car pulls much harder than before, it is definitely noticable. My co-worker commented on how the car was pulling considerably harder.

Jeff

Tuning Update: After analyzing my pulls, I came up with a tuning quality of 83.4%, up from 80% as of yesterday. This is just after 1 round of map adjustments. It is going to take 2 or 3 round of this to get it fully dialed in, but it was definitely pulling harder and throttle response was great. I am using the new feature I added last night that scores your tune in real-time, and also using my afr difference to make fueling changes in my utec map. Im working on getting some of your requests into the program right now and it will probably be available online around 4:30 or so.

Jeff

Future Updates:

*Realtime readout of horsepower, torque, and Thrust (G's)
- This feature is going to be kinda tricky but im laying it out in my mind just how it is going to work.

*Higher quality sounds for overboost/temp/rev warnings.

*Calculation of boost increase, given in psi/sec, to represent how fast you are building boost

*Peak boost hold/display. Possible that program will read out to you your peak boost after a pull(audible).

Many many more..those are just the ones I can remember for now.

Enjoy!

Jeff

Update: Version 1.7B is out. Please check over your settings before you use it!

Check the site for update information.

Let me know how it goes!

Jeff

I have the sound thing hapening with and without the "UTI Launched" checked.
Ver1.7B On my laptop.

TMS

Ver1.7
With the "UTI Launched" checked it is fine. Unchecked it plays all of the sounds. Again on the laptop.

TMS

My laptop goes screwy again, yet my desktop doesnt. It is hard for me to fix something like that when it is only on one computer! I'll keep Looking though.

Jeff

Ver1.7
With the "UTI Launched" checked it is fine. Unchecked it plays all of the sounds. Again on the laptop.

TMS

This is how I corrected it too.


p.s. UTI is not logging knocks for the sti utec.

Here is a log I played and no knock was detected:

4208 +11.0 3.9 102 60 00 +26.9 39.1 +14.4 +0.6 120.00 3.4 10.59
4317 +11.9 3.9 102 70 00 +26.7 42.9 +13.4 +0.9 120.00 3.5 10.99
4498 +12.1 4.0 102 70 00 +26.4 45.0 +13.9 +0.7 120.00 3.6 11.20
4649 +12.5 4.0 102 70 00 +27.5 47.9 +14.6 +0.5 120.00 3.6 11.20
4761 +12.7 4.1 102 70 00 +28.1 51.5 +15.6 +0.5 120.00 3.6 10.99
4982 +12.7 4.2 102 70 00 +29.5 50.7 +17.0 -1.9 120.00 3.6 10.67
5089 +13.1 4.2 102 70 00 +32.2 53.4 +17.0 -2.0 120.00 3.7 10.76
5341 +13.1 4.3 102 70 00 +31.4 56.5 +17.4 -1.9 120.00 3.8 10.99
5518 +13.1 4.4 102 70 00 +30.6 59.1 +18.1 -1.6 120.00 3.8 11.01
5640 +13.9 4.5 102 80 00 +31.0 61.9 +17.1 -1.6 120.00 3.9 11.05
5807 +14.3 4.5 102 80 00 +31.1 66.8 +17.9 -1.5 120.00 3.9 11.06
6105 +15.1 4.5 102 80 00 +31.4 69.7 +18.7 -1.3 120.00 4.0 10.96
6195 +16.1 4.6 102 90 00 +31.4 69.6 +18.5 -1.1 120.00 4.0 10.90
6385 +15.9 4.6 102 90 00 +31.0 73.0 +18.5 -1.0 120.00 4.1 10.87
6497 +16.6 4.7 18 00 01 +28.3 69.4 ECU. +0.4 ECU. 3.5 10.83
6093 +11.0 1.9 0 00 01 +23.2 6.8 ECU. +0.5 ECU. 1.7 10.89
5837 +3.5 1.8 0 00 00 +23.2 6.3 ECU. +0.2 ECU. 1.7 10.99
5428 -3.8 1.8 0 00 00 +23.5 6.1 ECU. +0.0 ECU. 1.7 11.34
5089 -11.6 1.8 0 00 00 +23.4 5.4 ECU. +0.0 ECU. 1.6 12.61


Also, is the "MOD" area supposed to show CLB values? (that's what mine shows)

Ver1.7
With the "UTI Launched" checked it is fine. Unchecked it plays all of the sounds. Again on the laptop.

TMS

when you update your UTI Version, did you remove everything including the INI file and start all over or did you just extract and overwrite the exe file? That might be the issue.

Ok guys I fixed the issue. It should not loop through them now. I tested it on my laptop and it works fine. I had to go back and add something in various places, this should work for everybody now. If you dont override your ini then just open up your settings and set the values, then close the program and re-open it again and you should be fine. You only have do to that the first time.

Go visit the site and re-download 1.7B if you have already gotten it as of 6:20pm EST.

Jeff

AaronWRX - Check this out:
If (Val(stKNK) > KT) And (stLOD > 0) Then
KnockMonitor 'Knock Alert and Reporter
End If


If the knock is not above your knock threshold and you are not above 0 Load then it wont respond. It only responds to knock that occurs in the 10-100 load columns. Trust me, it works, however I have not gotten any knock but during testing i enable the knock monitor during playback and i put a false knock event in there and the code detects it.

I'll check up on that CLB in the MOD area, thats interesting. Has it always been like that for you?

Jeff

...Also, is the "MOD" area supposed to show CLB values? (that's what mine shows)

Is this in Logger-1 Mode or Dashboard mode? also, does it appear like that in the logger-1 box at the top?

Jeff

AaronWRX - Check this out:
If (Val(stKNK) > KT) And (stLOD > 0) Then
KnockMonitor 'Knock Alert and Reporter
End If


If the knock is not above your knock threshold and you are not above 0 Load then it wont respond. It only responds to knock that occurs in the 10-100 load columns. Trust me, it works, however I have not gotten any knock but during testing i enable the knock monitor during playback and i put a false knock event in there and the code detects it.

I'll check up on that CLB in the MOD area, thats interesting. Has it always been like that for you?

Jeff

Yes it has. This was in Logger-1 mode. Should STI guys use Dashboard mode only?

Also, wouldnt that logic alway miss shift-knock? (a fairly common problem)...


edit:

I just tried to stack the deck with this log... no dice on the knock detection.

4135 +11.7 3.9 102 70 00 +27.8 42.3 +13.2 +1.1 100.00 3.5 10.42
4312 +12.1 4.0 101 70 00 +26.6 45.5 +13.2 +1.0 100.00 3.5 10.76
4510 +12.5 4.1 101 70 00 +26.8 46.2 +13.9 +0.7 100.00 3.6 11.02
4604 +12.9 4.1 101 70 00 +27.6 49.5 +14.5 +0.5 100.00 3.7 11.14
4803 +13.5 4.1 102 80 00 +28.5 54.5 +14.5 +0.0 100.00 3.7 10.93
5058 +14.1 4.3 102 80 00 +30.4 54.7 +16.5 -2.2 100.00 3.7 10.73
5216 +14.7 4.3 101 80 00 +31.3 57.1 +16.5 -1.9 100.00 3.8 10.86
5359 +15.5 4.4 101 90 00 +29.5 60.6 +16.0 -1.9 100.00 3.8 10.96
5500 +16.1 4.5 101 90 08 +29.4 64.2 +16.3 -1.8 100.00 3.9 11.05
5827 +16.6 4.5 102 90 00 +29.5 69.3 +17.3 -1.5 100.00 4.0 11.11
5920 +16.8 4.6 101 90 00 +29.4 71.8 +17.7 -1.5 100.00 4.0 11.12
6105 +17.2 4.6 101 90 00 +29.4 75.0 +18.3 -1.3 100.00 4.1 11.11
6242 +17.4 4.7 102 100 00 +29.3 74.5 +17.5 -1.0 100.00 4.1 11.06
6548 +18.0 4.7 102 100 00 +29.1 78.5 +17.5 -0.8 100.00 4.2 11.02
6720 +18.6 4.7 101 100 00 +29.4 82.9 +17.1 -0.8 100.00 4.2 11.01
6915 +18.8 4.8 102 100 00 +31.6 83.1 +17.0 -0.7 100.00 4.3 11.11
7062 +19.6 4.8 101 100 00 +31.9 82.7 +17.0 -0.6 100.00 4.2 11.23
7168 +18.0 4.7 0 00 00 +24.2 30.3 ECU. +0.5 ECU. 2.7 11.27
7077 +10.8 1.8 0 00 00 +23.1 7.6 ECU. +0.5 ECU. 1.8 11.28

Yes, it misses shift-knock. I only wanted it to detect actual knock that you get when actually under load.

Check your Knock Report. See if any knock shows up there. Also, check your knock threshold and and make sure that you have AutoLog Knocks on and the Knock popup on.

You arnt just playing back a log are you? This is in realtime right? In replay mode it doesnt trigger the knock detector anyway.

Jeff

I just saw a pic of the HKS Camp system and If I can get some good screen shots then I can make a gauge pack that looks exactly the same. I can show all the same info except speed (mph).

Jeff

http://www.scienceofspeed.com/products/interior_performance_products/NSX/HKS/default_sub.asp

Before anyone says it...i know the peak boost indicator popup window just shows "0". Why, I dont know but Im going to find out when I get home today. I am also going to add an option in the "Popup" menu that allows you to enable/disable this new peak boost indicator. It just slipped my mind when I was making it. To tell you the truth I got caught up in coding the AFR Delay and totally forgot to double-check the PBI. Well, how does everyone like the female voice? Not exactly sexy but as good as I could get for now.

BTW, after my 2nd map alteration based on my AFR difference table, my tune is up again from 83.8% to 90%. Possibly after doing it one more time it will be dialed in up in the high 90's. This just goes to show that the program does work in exactly the manner I had intended.

Jeff

I downloaded version 1.7 to supposedly install this weekend, but at the pace you're making changes :eek: I better wait to download and install version 10.0 on Saturday! :)


****
9-2x project car web page: http://9-2x.dynamic-dyno.com

Is this in Logger-1 Mode or Dashboard mode? also, does it appear like that in the logger-1 box at the top?

Jeff

i tried dashboard mode this morning and it fixed the display. MAP no longer reads CLB values. better let STI owners know they cant use logger-1 mode right now.

The peak boost indicator worked for me! Program is still crashing on me causing my pc to go nutzz. Here is a log of UTI crashing.
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 14.74
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 13.68
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 13.06
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 12.67
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 12.74
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 13.45
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 14.37
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 14.74
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 15.37
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 16.36
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 15.80
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 15.37
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 15.02
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 14.15
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 13.62
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 12.89
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 12.75
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 13.75
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 16.80
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.1 20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.120.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU. 1.20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.72
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.18
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU13.47
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU13.87
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.92
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.18
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.18
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.83
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.45
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.58
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.12
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.24
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU14.65
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU13.65
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU12.89
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU12.25
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU11.11
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU10.64
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU12.05
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU15.37
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 ECU20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 EC20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 E20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.0 20.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.020.0
746 -9.2 1.2 0 00 00 W/B 38.0 1.3 38.0 +0.20.0


and another
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E15.02
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.83
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.49
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.30
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.15
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.08
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.15
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.15
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.18
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.15
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E14.08
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.95
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.87
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.81
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.78
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.84
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.68
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.39
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E13.28
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E12.11
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E10.68
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E10.34
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E11.34
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E18.22
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 E20.0
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 19.27
1667 -11.8 1.4 0 00 00 W/B +21.6 2.8 ECU. +0.0 13.17
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.214.65
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.214.05
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.213.17
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.212.37
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.211.87
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.211.58
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.211.14
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.210.56
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.210.26
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.211.49
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.216.69
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.220.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 1.20.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 120.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 20.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 20.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU. 20.0
877 -8.9 1.3 0 00 00 W/B +4.4 1.7 ECU. +0.0 ECU.22.47
2896 -8.9 2.4 8 00 00 W/14.92
2896 -8.9 2.4 8 00 00 W/13.33
2896 -8.9 2.4 8 00 00 W/12.33
2896 -8.9 2.4 8 00 00 W/11.77
2896 -8.9 2.4 8 00 00 W/11.81
2896 -8.9 2.4 8 00 00 W/14.61
2896 -8.9 2.4 8 00 00 W/20.0
2896 -8.9 2.4 8 00 00 W20.0
2896 -8.9 2.4 8 00 00 20.0
2896 -8.9 2.4 8 00 00 20.0
2896 -8.9 2.4 8 00 0020.0
2896 -8.9 2.4 8 00 020.0

AaronWRX - thats weird. I looked over the code and I couldn't find anything that looked like it would cause the problem. The fact that it does it only in logger-1 mode will make it easier for me to track down whatever is doing it though.

fatray - its like the log is collapsing on itself. Are you in logger-1 mode or dashboard mode? Also, you have a wrx utec right? Im assuming so based on the "W/B" in the log, I just want to make sure you are running the program like that.

Jeff

AaronWRX - thats weird. I looked over the code and I couldn't find anything that looked like it would cause the problem. The fact that it does it only in logger-1 mode will make it easier for me to track down whatever is doing it though.

fatray - its like the log is collapsing on itself. Are you in logger-1 mode or dashboard mode? Also, you have a wrx utec right? Im assuming so based on the "W/B" in the log, I just want to make sure you are running the program like that.

Jeff

HEh.. come on STI guys!! help me out here! Am I the only STI guy testing this?

I didn't think about the UTEC version. I have the Aussy spec STI UTEC for a V7 STI It uses the exact same firmware as the USA UTEC but works with AVCS (more wires). I don't think it matters but you never know. I believe I was using dashboard mode.

fatray - I might have fixed your problem. It was something where when you are showing ">25:1" as your wb02, i was replacing it with "20:1" when it needed to be 5 characters, not 4. So now it will show 20.00 instead. I think this is going to fix your problem.

AaronWRX - Capture a few seconds worth of Logger-1 in hyperterminal and email me the text file to cashionm@bellsouth.net

I'll verify that my code is looking in the proper spots for the data.

Jeff

HEh.. come on STI guys!! help me out here! Am I the only STI guy testing this?


Sorry. Once I read there was a pop-up that wasn't an option, I didn't install this latest version. The pop-ups distract me too much so I gotta keep them off. The knock pop-up is nifty, but I can't do anything about it until I park and adjust the map... at which point I can check the logs anyway. The CEL lets me know what I need.

I went back to the standard windows theme and discovered the markings around the AFR bubble work (like too lean and too rich and the bars... previously invisible but it was my fault) So I modified my STi(ish) theme so they'd show up.

Keep in mind, this is only a 7 inch thouchscreen and I'm using Tablet PC and it's onscreen keyboard... which is why it's in all the screenshots. And that's why my icons are so big.

UTI with regular windows theme. (you've seen this before)

http://x12.putfile.com/12/33414090429.jpg

My latest STi theme desktop. It's a little more vivid... not as dark as this looks on my PC as I get ready to post it. But the red fonts are not ideal. Getting font colors layed over backgrounds that are functional in every application is kinda hard whe you want a certain look.

http://x12.putfile.com/12/33414075915.jpg

UTI with STi theme. I'm a dork and saved over the screen capture with the AFR bubble showing. :rolleyes: But it's white, with red text instead of white on white.

http://x12.putfile.com/12/33414084316.jpg

I'll keep tweaking it 'til it works well in most applications. Its not like I'm gonna write a thesis on the touchscreen anyway.

Oh, that blue, white and gray box is a software right left mouse buton toggle. It's always on top if you were wondering.

Update: Version 1.7C is now out. Go check it out!

2phless - what a coincidence, the peak boost indicator is now an option in the popup menu.

This version does not have a whole lot of updates, just a few tweaks. I am currently working on a big update that will include realtime readouts of Horsepower, Torque, MPH, Feet/Second, G's(acceleration). This is going to take me a little big longer, believe it or not. I think that the program is at a pretty good point right now, most of the things that I always wanted it to have are in there. There will always be something to add to it but for now I think its pretty solid.

Jeff

ok.. i just used 1.7c on the way home tonight
STI in Dashboard mode.

here is a snip from my pull report:

4844 +16.1 4.4 102 90 00 +24.4 61.7 +14.4 -0.6 120.00 3.9 10.52
5005 +15.9 4.4 102 90 00 +25.0 63.9 +14.6 -1.2 120.00 3.9 10.43
5042 +16.1 4.5 102 90 00 +25.4 64.6 +15.4 -2.2 120.00 4.0 10.56
5208 +16.1 4.6 102 90 00 +24.8 68.4 +15.8 -2.1 120.00 4.0 10.78
5274 +17.2 4.6 102 100 00 +24.7 70.6 +15.4 -1.8 120.00 4.1 10.89
5509 +18.2 4.7 102 100 00 +23.3 75.5 +16.0 -1.4 120.00 4.1 10.93
5564 +19.2 4.7 102 100 00 +22.7 74.9 +16.5 -1.5 120.00 4.1 10.90
5678 +20.4 4.7 102 100 00 +22.9 76.9 +16.8 -1.4 120.00 4.1 10.90
5817 +20.2 4.7 102 100 00 +22.8 78.2 +17.0 -1.3 120.00 4.2 10.90
5889 +20.2 4.7 102 100 00 +22.7 79.4 +17.0 -1.4 120.00 4.2 10.86
5973 +19.6 4.8 102 100 00 +22.8 79.3 +17.1 -1.1 120.00 4.2 10.76
6138 +19.0 4.8 102 100 00 +23.6 80.3 +17.3 -1.2 120.00 4.2 10.73
6184 +20.0 4.8 102 100 00 +24.1 82.6 +17.4 -1.1 120.00 4.2 10.73
6337 +20.6 4.8 102 100 00 +24.4 85.4 +17.5 -1.0 120.00 4.2 10.68
3138 +0.8 3.2 31 20 00 +36.5 21.3 +25.0 +1.8 ECU. 3.0 13.42


and here is a picture of my boost table:

http://njektd.com/subaru/boost_table.jpg


shouldnt those 20.6's be in the 100% column?

Good Call AaronWRX, I was wondering myself earlier why my 100% column had nothing in it but I didnt put much thought into it. Since you point it out I realized a boobo that i made in my code. I was telling to not draw the information into the table if the column wasnt less than 11, and it should have been 12. 1 thru 11 are valid, so to make it only good for 1 thru 10 was a mistake. I just fixed it and im uploading a new version right now.

Jeff

Update: Check the site, I fixed this bug and uploaded 1.7D.

Jeff

Hey all, i have version 5.0 on my u-tec and yesterday had it tuned a little. after a day of driving it goes back to runing like ****. I set the 2 step at 4500 and it works but now i cant rev over 5500 rpm. what is going on???

Logs the 'C' note now. Cool.

Suggestion. (Since you seem to be addicted) A large button that'll put the UTI into logging mode, for say 10 seconds.. or some settable amount... or a toggle.

If I run into issues, hesitations and the like, before/below the normal logging 'and' parameters are met, I'd like to be able to go back and check them out. Perhaps have them saved as a "manual log..... .txt" or something. If you need space for them I'd say the large table button could be moved to the top toolbar since it's not really an "on the fly" thing.

If I read the AFRs on that I hit trees... and they go lean real quick.

Perhaps an ECU table added to that .csv file. I really like those tables. Or chooseable options... TPS across the load sites would be good for quelling PTFB. But that would need to be a minimum recorded TPS per cell instead of an average to nail down the trouble spots. Probably ingnoring any TPS below 10 or nn amount to make it user settable.

I could keep going. :D

I was/am considering adding more tables to the mix. TPS and MAF are probably going in there.

I have considered having a setting that monitors your crossover and checks for stumbling or other erradic stuff, I just havnt had time and other things needed to come first.

What do you mean by "Logs the 'C' note now." ??

Jeff

I was/am considering adding more tables to the mix. TPS and MAF are probably going in there.

I have considered having a setting that monitors your crossover and checks for stumbling or other erradic stuff, I just havnt had time and other things needed to come first.

What do you mean by "Logs the 'C' note now." ??

Jeff

MAF is a good one because increased MAF indicates you are making more power.

Yea, MAF is what I use to gauge power to some degree. I am starting to see some 4.7's which is the highest i've ever attained. Im pulling solid 4.6's and every now and then a 4.7 will pop up. Im hoping to pull solid 4.7's when im done with my tuning.

Jeff

"C note" = slang for $100 bill... or in this case. The 100% column. Sorry. Slipped into an old gangster movie for a moment.

Oh ok, yea it logs the 100% column.

I just added a MAFv table and a TPS table. They are both averages, not min or max.

Jeff

Just so you all know, im working on a map editor as well, its a standalone for now.

Jeff

Ok, I finally got a chance to use this (before it would crash) and it's great! I didn't realize some of the things it does.

One thing that is wrong is that I changed my port to com 1 vs the standard 4 and it still shows "Port:4" on the bottom even accross sessions.

Just so you all know, im working on a map editor as well, its a standalone for now.

Jeff
Great. You might want to download "ULame". I use that and it's awesome.

Just so you all know, im working on a map editor as well, its a standalone for now.

Jeff

Will the upload and download function be built in?

Mine says com 4 instead of 1 sometimes... then sometimes it prints 1.

Will the upload and download function be built in?

Very easy to do. I didn't end up doing this because you have to have the motor off. The ultimate way would be to edit the load cells that have changed and not upload an entire map at once.

Very easy to do. I didn't end up doing this because you have to have the motor off. The ultimate way would be to edit the load cells that have changed and not upload an entire map at once.
Very true..but you should be able to limit not only when to make a change in bulk to the map but limit the amount of change to a value in the map based on the difference in the AFR.

Very true..but you should be able to limit not only when to make a change in bulk to the map but limit the amount of change to a value in the map based on the difference in the AFR.

Without external variables such as injector ccs/min at a givin pressure rate, fuel pressure, and RPM you cannot predict the AFR.

IMHO if you limit edits do it to what the UTEC limits otherwise you are in for a world of hurt trying to get the UTEC to accept stuff.

I think for now the user will be required to upload/download maps themselves, its just that mine will take in your current map as well as your "AFR Difference" table, and based upon your cars configuration, it will make the appropriate adjustments. My technique of adjusting my map directly based off of how far off I am with AFR has worked out really well. I went from 80% tune to 84% then 91%. Its not an exact science but its my car and i take responsibility for what happens and so far it is working fine.

Jeff

Mine says com 4 instead of 1 sometimes... then sometimes it prints 1.

This problem has just been fixed. I found the mistake and corrected it. I had not included the proper code to setup the status bar upon launch. It was just showing the default text that I see during creation.

Dont worry, even if it says "Com 4" upon launch, its still correctly at the right port, it just isnt updating the status bar when it launches.

I'll release this fix probably sometime today.

Jeff

Well the map program is really comming along. It opens up your utec map off of your hard drive, then also opens up a csv table log from UTEC Interface. It then combines the existing fuel map with your "AFR Difference" Values and makes a new fuel map for you. I have been doing this manually over the past few days and its a PITA but it is very very effective at getting my fueling dialed in just right.

Now I need to figure out how to calculate the checksums because turboxs probably wont tell me how they do it but im guessing its the sum of all the values in the map...we'll see! If anybody knows what it is and wants to help me out then please throw me a bone.

Jeff

Silly me............I downloaded today, dragged the executable from the unzip folder to my desktop, and wondered "why won't it connect?" :rolleyes:

It's working beautifully here :) Haven't run into a single bug yet.

http://forums.evolutionm.net/showthread.php?t=107095

Check out UCC...Looks hot.

What do you guys think about having the tables save and re-load automatically, instead of resetting after each use of the program? Then you will have a continuous flow of information into it. You will still be able to save it and reset it but this way it will be more filled with information.

Jeff

If you see any features that you would like in UTI let me know and i'll see what I can do. I just checked it out, it looks nice but obviously is for the EVO.

Jeff

That'll work but you should have an absolute min. about of data before changes are made.

You are referring to when the program changes your suggested map value?

Jeff

This problem has just been fixed. I found the mistake and corrected it. I had not included the proper code to setup the status bar upon launch. It was just showing the default text that I see during creation.

Dont worry, even if it says "Com 4" upon launch, its still correctly at the right port, it just isnt updating the status bar when it launches.

I'll release this fix probably sometime today.

Jeff

Yeah, I wasn't worried about it.

I think for now the user will be required to upload/download maps themselves, its just that mine will take in your current map as well as your "AFR Difference" table, and based upon your cars configuration, it will make the appropriate adjustments. My technique of adjusting my map directly based off of how far off I am with AFR has worked out really well. I went from 80% tune to 84% then 91%. Its not an exact science but its my car and i take responsibility for what happens and so far it is working fine.

Jeff

Be stupid careful with this and make sure people know they need to verify the map changes. This is a REALLY bad idea to trust blindly because the computer cannot make interpolative decisions and make the appropriate changes to load cells that are not part of your run and smoothness should be added which depends on injector scaling and injector size. Not to mention if you change a load cell you know that somewhere else on the map you might need to make a change as well and the autotunes CANNOT do this. If you release this again, make sure the user knows whats going on. I'd have them go through a double-confirm to enable it.

"Use at own risk" definitely applies here! It is going to be a seperate progam from UTI yet work directly with it. If you dont want to use it thats fine, but im writing it for me because im tired of doing it manually.

Jeff

Well until I can figure out how the heck they derive the checksum the map program is on hold. That is the only thing from holding me back. If you know the answer please chime in!


Jeff

Dont know if it'll help but this program has it figured out

http://www.wrxhackers.com/forums/showthread.php?t=2492&page=1&pp=10

...and go to the next page on that thread to find the regedit method to beat the "software out of date" issue. (posted by the author)

Be stupid careful with this and make sure people know they need to verify the map changes. This is a REALLY bad idea to trust blindly because the computer cannot make interpolative decisions and make the appropriate changes to load cells that are not part of your run and smoothness should be added which depends on injector scaling and injector size. Not to mention if you change a load cell you know that somewhere else on the map you might need to make a change as well and the autotunes CANNOT do this.
My thoughts exactly. Without knowing the injector scale, injector size, and MAF scale, how would you be able to predict the amount of fuel change needed to change AFR? You may have an algorithm that works for your setup, but there is no telling how close it will be to the next guy, which is what matters with distributed software.

Jeff to compute map checksum its easy

Total = 0

Add to your total all fuel map cells * 10 + 1001;
Add to your total all timing map cells * 10 + 1001;
Add to your total all boost map cells * 100 + 1;
Add to your total the ASCII value for each letter in the map name
Add to your total the ASCII value for each letter in the map comment
Reduce the total integer to 16 bits and print it in hex. Thats your checksum.

Here is a program I wrote over a year ago to compute the checksum in c:
http://www.cs.rit.edu/~cxv1089/utec/utecChecksum.c
http://www.cs.rit.edu/~cxv1089/utec/utecChecksum.exe

Awesome cdvma, thanks for the help. This program is now back on track!

Jeff

does that include even the hidden cells that arnt actually part of the map? there are like 2 extra on top and 4 below or something like that which arnt actually part of the usable map but they are in the text files.

Jeff

Yes. All cells included.

Sweet. Here is what I see in the future(couple days):

1. Person uses UTI for XX amount of days. Amasses a pretty decently filled in set of tables.

2. Runs UTI Map Editor, which automatically opens up the persistant tables from UTI. It also opens up your current map which you have downloaded from your utec. It combines the two and generates a new, more accurate fuel map based off of your observed AFRs and your current Fuel map values.

3. User Uploads this new map generated by UTI Map Editor and drives around, noticing that their "Tune Quality" as listed in UTI has risen from what it was before, thus their car is now better tuned.

4. User repeats process until their "Tune Quality" is at a high enough level (For me this is >95% TQ).

Any Questions?

Jeff

Sound great. Can you add a feature in the table that will allow you to click on a cell and see the lines that were used in the log to arrive at its results?

That would require saving every single line that is used to fill in the tables. You could/would end up with a 5 million line notepad document, and even if you did that it would probably be very slow to find the exact record.

It is a nice idea in theory but improbable.

On a brighter note, the map editor is really comming along. It does most of the basic stuff now, it opens up the tables and your map, combines the two and outputs a new map with the correct checksum.

The way that users will customize it is by adjusting the "Influence" and the "Confidence". The influence is basically a number that the AFR difference value is multiplied by. The confidence value is how many cell hits it takes for you to be 100% confident that the afr difference is appropriate. Then each cell hit is divided by this number that represents 100%(if higher than than the confidence value then it will just equal it to keep from going over 100%) and then that fraction will be multiplied by the previous calculations product. This keeps cells that have very few hits from actually influencing your map much, as they might not be too accurate, or just a fluke or something.

Jeff

Sound great. Can you add a feature in the table that will allow you to click on a cell and see the lines that were used in the log to arrive at its results?

Dosen't ULAME (http://forums.nasioc.com/forums/showthread.php?t=778263&highlight=ulame) do that?

It looks like it does. it operates in a different manner than mine does. I do not plan to use mine to actually make lots of adjustments myself to my map; instead it does it for me based on the AFR difference and what how I configure it to merge the existing map with the afr difference. I dont even need to make this a full-blown map editor because you dont have to do that anymore; those days are over. It does have standard cell editing anyways if you like to make your own adjustments and everything is colored based on value. I am going to be testing it today. I'll report back on how it works, hopefully the checksums are correct.

Jeff

Sometimes when I bring the program up, I'll drop down file, and undewr the source and logging options everything has a check beside it. WRX50 and STi1c are checked off, and then both logger and dashboard also have checks beside them. I've only had one instance where it wouldn't log/synchronize until I fixed it though, I think I had to close and open the program to get it to sync.

I'll check further a little later this morning to see what the .ini file reads, and if the problem comes back after a re-boot instead of a hibernate or what...

I guess the sync issue is just after hibernation. I just have to exit and restart the logger... that's fine. It even happens in hyperterminal sometimes. From a cold boot, UTI is loaded in startup and syncs up as long as the tuner and utec are ready for it.

Just an aside for those who might have issues. Most probably already know this. The Tuner wants to be turned on after the UTEC to set up the communications correctly. It's in the directions. Anyway... my solution for this was to hook up the tuners power to acc instead of ign. The UTEC fed ignition through the ecu harness of course.

This way, whenever I start the car the tuner comes on first in acc position, both are on in ign, and then the tuner loses power in the start position, lettign the UTEC "see through" the Tuner.

It's also useful when I'm having an issue on the fly, I can just push the key forward (but well before engaging the starter, just to the point where the radio turns off) and thet'll reset the tuner. Sometimes that clears a sync issue, even in hyperterminal.

I've been thinking about the possibliltiy of a minimum throttle posistion recording in the csv file. It'd have to have some means of recognising and ignoring certain instances. Quick off throttle would give a lot of zeros across some high load /rpm point that shouldn't count. (I have some high boost numbers in the 0 column/ high rpm rows every now and then that I know aren't really valid. They happened, but only for a split second.) Matter of fact, almost any time the TPS% is dropping, you probably wouldn't want to record the data. Maybe only if the TPS is stable or increasing for more than 2 seconds or so.

Also, how about a little utility program to stitch two of the .csv table files together, re-averaging the data into the same layout.

Still a great program. Has saved me a lot of "eyes on the road" time already which results in a lot of "not hitting deer" time. And that's always good.

I have made the program keep the tables over each run, so they are saved basically. It will be called "Tables.csv" and will always reside where the program is, just the the myAFRTable.csv file. This solves the problem of starting a fresh table each time.

I couldnt' release a new version yesterday because I was stuck on the boat the entire day on duty (dont ask).

Jeff

One thing I've noticed is that the software doesn't log my part-throttle knock at all (not to mention shift-knock, but that's been brought up).

The part throttle/cruise thing is a huge deal IMO. By observation, it appears that the knock report is a report of the knock recorded in a pull, which only records once your thresholds have been met. Well, for a part-throttle knock to be caught, it would constantly have to be recording.

Many users have requested this from UTEC: Constantly log and if knock occurs, record the event (And few lines before and after). If no knock is recorded, it overwrites. Ie, the buffer log wouldn't have to be big at all, but it would catch tip-in below thresholds, cruise knock and shift knock. This seems pretty easy to do.

-C

Many users have requested this from UTEC: Constantly log and if knock occurs, record the even (And few lines before and after). If no knock is recorded, it overwrites. Ie, the buffer log wouldn't have to be big at all, but it would catch tip-in below thresholds, cruise knock and shift knock. This seems pretty easy to do.

-C

<shameless plug>

You have my logger, just set the auto logging trigger to UTEC:KNOCK and the threshold be > 0. Do a single log file and it will log your knock line plus the number of lines you put in for hysteresis before and after the knock event in one file dated from the first knock event after the program starts.

<shameless plug>

You have my logger, just set the auto logging trigger to UTEC:KNOCK and the threshold be > 0. Do a single log file and it will log your knock line plus the number of lines you put in for hysteresis before and after the knock event in one file dated from the first knock event after the program starts.
What logger is yours? I have just about everyone out there on my desktop :lol:

[edit]Checked pm log, you never sent me the code I was requesting. :( You left me to use this VB app man when my Java app would have been done a while ago :)

Project802 Performance Logger.

Yea I know I haven't sent it. I'm also trying to find it....seems like I may have tossed the source.

Knock is monitored if you are greater than 10% load and the knock is higher than your knock threshold setting. It doesnt matter if you are doing a pull or not, its always listening for knock regardless.

Jeff

On a different note, im working on my map editor right now. I just now got it to actually make a file that the UTEC will accept as valid. From here on out I am going to polish the interface and make it bad@$$. On Friday I have to leave for 7 days for an Underway period...we are going to go do circles out in the ocean while new pilots learn how to land on a carrier...boring stuff. Anyhow, for that week I am going to be doing some serious coding so there should be some good stuff for you all when I get back on the 16th. I know I havnt released a new version of UTI in a few days, and it probably wont be until tomorrow, i've been really tied up with the map editor. It is well worth it though, you will all agree when you get your hands on it!

Jeff

any screen shot previews?

yea, maybe later tonight.

Jeff

On a different note, im working on my map editor right now. I just now got it to actually make a file that the UTEC will accept as valid. From here on out I am going to polish the interface and make it bad@$$. On Friday I have to leave for 7 days for an Underway period...we are going to go do circles out in the ocean while new pilots learn how to land on a carrier...boring stuff. Anyhow, for that week I am going to be doing some serious coding so there should be some good stuff for you all when I get back on the 16th. I know I havnt released a new version of UTI in a few days, and it probably wont be until tomorrow, i've been really tied up with the map editor. It is well worth it though, you will all agree when you get your hands on it!

Jeff

Can't you just tell the Navy you have more important obligations right now? :p

yea i wish. It will be good though, I'll seriously get a TON of coding done, probably 2x what I could if I was in port.

Here is a picture of what the fuel map looks like when opened. This just shows off the color coding.

http://www.dezignduo.com/UTI/fuelmap.jpg

And the timing map.
http://www.dezignduo.com/UTI/timingmap.jpg

Jeff

Knock is monitored if you are greater than 10% load and the knock is higher than your knock threshold setting. It doesnt matter if you are doing a pull or not, its always listening for knock regardless.

Jeff
But this doesn't catch knock in 0 column.

I believe I figured out my problem with UTI. 2 of my 3 USB ports on my laptop seem to have cold solder joints. Causing the connection to UTEC to go on and off.

TypeC - right. I had it like this because sometimes there was a glitch where the utec sent crazy info and it caused a "false knock" to trigger, even though there wasnt one. I think i've probably made it so this doesnt happen and i bet I can undo that safety feature so that users can see knock in the 0% column. Would that make everybody happy?

fatray - glad to hear your problem, sucks that its that bad. Can you just use the 3rd usb port instead?

Jeff

Update: Version 1.8 is finally out. Check out the site for all the updates. There are some good ones in there. I hope everything works, I havnt actually road-tested it yet. I am working on the map editor so thats why UTI has been slow to update in the past week.

http://www.dezignduo.com/UTI/

Jeff

Jeff,

I know you specified this for UTEC V5.0. I tried connecting with the older 4.3c software and it connected and the data looks correct. Is it OK to use with that version firmware?

Yea, its safer to use the logger-1 mode instead of dashboard but you can try both and if they show up ok then its fine.

Jeff

Update: Version 1.8 is finally out. Check out the site for all the updates. There are some good ones in there. I hope everything works, I havnt actually road-tested it yet. I am working on the map editor so thats why UTI has been slow to update in the past week.

http://www.dezignduo.com/UTI/

Jeff


Setting alarm 15 minutes earlier.... you bastard!... I mean thanks! :p

I have already found a few hiccups with 1.8 and i'll address them today. You will probably notice that the tables dissapear every 10 seconds...thats because they are being saved. Well I told the code to figure out which one you were looking at and to make it re-appear when its done saving and apparently its not doing that so i gotta take a look at why its not doing that properly. The reason I hide them when saving is because when you tell a flex-grid(table) to change cells at an extremely fast rate like when trying to read every cell in the table one by one, row by row, then it is slow to do that if you can actually see the table. If you hide it first then it literally takes place instantly. So by hiding it I can read the entire table in like 1/1000000 of a second, as opposed to 3 seconds if I leave it visible.

I'll post the update this afternoon.

Jeff

Ok, the bugs have been addressed and everything is ok. 1.8B is now available on the site. This is probably my last version for about 9 days. I have to go underway from this friday until the next friday. When I get back though I might have some nice things for you all, it depends on how much I feel like coding while out at sea.

Jeff

I am still seeing some goofy activity when opening/saving/resetting tables. I dont know quite what is going on yet but im trying to figure it out. If you have similar problems keep calm, im work'n on it!

Jeff

Well it seems to have gone away...if you have a hard time getting the tables to reset, just delete the tables.csv file and that should do the trick. Do it when the program is not open though.

Jeff

You know, a feature I'd really appreciate is to separate each pull log with an empty line. That way I can glance at it and determine which block is from what run. How it is now, if I have more than 2 runs, I have no idea what I'm looking at.

I thought about doing that, it would be really easy to impliment. If that is what the general consensus is then I can make it happen.

While im gone for a week im going to code the cool stuff like MPH,feet/second, and G's, HP, and TQ. It will all be real-time so while crusing on the highway you can see approx. how much horsepower you are generating just to maintain speed. I dont know how accurate it is going to be but i've done some experimental math and it appears to be doable.

Would anybody like the tables in UTI to be color-coded, like the afr table will have each cell change color depending on what value is inside it? It wouldn't be hard, i've practically already written the code for the map editor program I wrote. Let me know and i'll see what I can do.

Jeff

After using it a lot the last week I noticed that for some reason my knock report stopped working. It'll show a pull report that contains knock, but the knock report shows nothing.

Also, if I open a pull report and clear it, UTI stops generating any further pull reports until I close and reopen. :confused:

Well over the past couple days I've spent probably 20 combined hours coding. The program has seen several HUGE upgrades. I dont know If I could even list them all off the top of my head but basically, everybody's dreams have come true...Here are a couple things just to get you an idea....

1. Program is skin-able. You can now create your own skin in PS and use it.
2. Tables now are backed by arrays that store the data to .000001 accuracy.
3. Tables are now colored to represent the value in each different cell
4. Tables include MAFv and TPS
5. You can now choose where you want to save logs, the afr table, and the persistant tables.
6. Persistant tables are re-organized and better created.
7. Playback now goes up to >100 lines a second
8. CPU usage dropped dramatically during playback
9. Real-time graphing of boost, just like greddy E-01 boost controller, afr and others soon to come
10. AFR delay has been upped to 8 lines instead of just 4.
11. Playback now has "Play", "Pause", and "Stop" commands.
12. Telemetry: Real-time display of MPH, Feet/Second, Horsepower, Torque, and G's.
13. Several code enhancements that operate faster and more efficiently.

That is all I can think of off the top of my head, I know there is more but I hope this pleases many of you guys out there.

TypeC - I'll take a look into the code and see if I can find anything to support those problems.

I should be back on thursday so perhaps a new version will be out on friday. Have a nice night!

Jeff

If there was a Heisman Trophy for UTEC-related contributions, Jeff would get my vote for 2005.

:lol:

Type-C: Check your knock threshold in your settings panel. Also, make sure the dropdown Knock Autologs is checked. I tested the pull report and it works just fine for me, I can reset and it will still work just fine; all clicking on the "clear log" button does is erase the text in the box, thats it. I am back in town and I am going to comb through and continue to work on the program and aim for a friday release of version 1.9.

Zola: Thanks for the compliment, glad you like it!

Jeff

any chance for a release today?

I pushed back the release to tomorrow. I am trying to squeeze in some features at the last minute. I still have a few hurdles and ideas im tossing around. Here are some ideas that I havnt implimented but want to:

1. Pull History: This saves info like duration, start/stop rpm, peak boost, any knock, etc. This will just be something you can quickly look at and see the overall details of a pull without having to read the entire pull.

2. Multiple Realtime graphing items: right now I just graph boost, but to graph AFR and ignition would be nice. The graph flickers when it is updated and im trying to find a way around that but so far I have had no luck.

I dont know how to make a dialog box(open file/close file) allow you to select a folder as the appropriate item; it only lets you select files. Well I need to make a way for you to select what folder to save your logs in. Im sure i'll figure it out soon.

Ok well thats it, this version is worth the wait, trust me!

Jeff

Ok gang, here's a nice tidbit:

I Just updated the warnings sounds to something better than the generic "beep". The rpm warning can/should be used as an audible shift indicator. I am going to use an old laptop hooked up to my head unit via an aux->Stereo line cable for audio so that I can actually have UTI tell me when to shift. It is the Kenwood CA-C1AUX cable from crutchfield. Anyways, The sounds also have protection from being played too soon after just playing; RPM is 2 seconds, Overboost is 2 seconds, and overheating is 8 seconds. I am probably going to code in something that looks to see how fast your rpms are climbing and play the sound in advance so that by the time it plays, you will be at the rpm. This also makes it easier for you to shift on time; if it waited until 7k to sound off, then in first gear you would be screwed because it revs waaay too fast, but in higher gears, it takes a lot more time for you to rev from rpm A to rpm B. I have to check how fast you are logging, the time delay, and guestimate when the perfect time to do it is, but that wont take maybe 20 mins. to code in there. Because of this, you wont have to set your rpm warning prematurely just to hear it in time; the program auto-adjusts for you! Does your STi's stock shift indicator do that? I dont think so...............

Jeff

Does your STi's stock shift indicator do that? I dont think so...............

My ears do ;)

The easiest effective way of calculating lead time on RPMs is a learning algorithm. You can do guesses based on RPM delta but without a very large and linear sample rate (which the UTEC does not give) your prediction line will need some serious smoothing. Its possible to make it work "ok" easily, to work perfectly the UTEC doesn't give you enough info. Speed is pretty much all you need if the user tells the program what the final drive ratios are....

http://project802.net/images/logger/speed_rpm.jpg

If you are fast-logging then the sample rate is quite high(20 lines/second). Speed, as you well know, is directly proportional to your rpm, so to use one or the other is basically the same. UTI does have user input for gear ratios, so it does know how fast you are going, just not what gear you are in so it shows it for every gear. For the program to calculate horsepower and torque, I already have a very effective method of smoothening the rpm values, so I can use that to make good predictions as far as future rpm values. I am expecting an early afternoon release of 1.9, I am still working on it and was all night last night.

Jeff

Alright, the rpm-prediction is done. It uses a semi-advanced method of filtering the rpm values and smoothening them out. Then it uses those values to predict what rpm you will be at in 0.5 seconds, then if its >= your warning rpm, it will sound the alarm. I figured that 1/2 a second was a good amount of time for someone to react, so it should suit most people. Perhaps in the future i'll make it adjustable but for now its stuck at .5 seconds.

I'll be releasing this new version very soon, probaby under an hour from now.

Jeff

UPDATE: Version 1.9 is OUT!

If there are any serious issues i'll release a 1.9B tomorrow. I hope it works for everybody!

Jeff

I guess we'll have to wait until tomorrow. No data is populating in any of the fields. Tables, Info, Nowhere.

Also, I'd really like to include a timing map in the "tables" view.

The tables view is the MOST important thing in UTI IMO. It saves TONS of time when analysing logs and tuning because I don't have to read a 2D log and convert it to a 3D UTEC type plot. I can just open the log and UTEC at the same time and edit the maps.

Also, I think all of the windows should be resizable. The log window just barely doesn't fit in 800X600 and I can't resize it at all. This means if I want to see the data, I can't see the "save, clear, close" button at the button. It's hard to move the screeen around while driving :o

Lastly, +1 for the logging with a blank line between pulls. I can't see why anyone wouldn't want this. If you had this, then you wouldn't need that log summary you talked about.

Oh, and my knock report just plain doesn't work anyway. I have defaults for everything. Also the gauges don't work either. Both worked on a previous version, but not lately.

Godspeed. :cool:

rainmanjam - Did you follow the directions in the readme file? I have used it and so far it works fine for me. apparently Type-C can get it to work ok.

If the gauges dont work then you probably need to install macromedia flash on your computer. I dont know why the knock report doesnt work for you...i know it works on my computer just fine. I'll double-check the code again.

What do you mean by having a timing map?

Jeff

I figured that having a timing map was pointless because you are going to run exactly what is in your timing map, unlike your fuel map where its maf offset that results in an afr.

I just tested it on my 2nd laptop and everything works fine in playback mode, so I can only assume it works fine when sync'd up. The gauges, chart, tables, everything.

It is critical that you properly configure your settings and save, then EXIT the program and RESTART IT to ensure that everything loads properly. If you dont do this then the program will not work.

Jeff

For most people, if a skin isnt loaded, then RPM, ignition timing, and MAFv wont show up in the main area because the text is the same color as the background. Just assign one of the default skins, either red or blue and this will not be an issue.

I just checked the program and it seems to work fine for me. I got everything to work. Perhaps its just an STi issue but I dunno.

What operating system are you running, rainmanjam?

Jeff

XP sp2. Del D610 connected via serial to usb

Type-C: I moved around the tables form. Now the buttons are off to the side and so is the tune information. Those items are also enlargened and easier to use/read. This should please all those who use this on a touchscreen.

I am considering adding a table that records Knock. I could do timing but I really dont see the point. You run whatever is in your utec map, there is no surprise there.

Jeff

Ok, 1.9B is out. Just minor tweaks, check out the site for the full version update information.

http://www.dezignduo.com/UTI/

http://home.comcast.net/~tetsujin/UTI2.JPG

http://home.comcast.net/~tetsujin/UTI1.JPG

This is what I am getting. Any advice?

So that is what you see when it is running and nothing else works except the logger-1 Line? I'll take a look into that. I just so happened to log a pull from an STi today so i'll use that and verify the code that interprets the sti's logger-1 format.

Jeff

Anyone else with an STI having issues?

Anyone else with an STI having issues?

yes. Logger-1 has never worked for me. Only "Dashboard"


good to see another STI guy testing this with me! :)

Im on it. Expect to work tomorrow with version 1.9C.

Happy Tuning!

Jeff

AaronWRX... Both the Logger-1 and Dashboard has worked for me until 1.9. What are you doing differently?

AaronWRX... Both the Logger-1 and Dashboard has worked for me until 1.9. What are you doing differently?

are you sure logger 1 worked? I noticed the columns were off.. so it appeared to be working but all the data was wrong.

yes. Logger-1 has never worked for me. Only "Dashboard"


good to see another STI guy testing this with me! :)

What am I? Chopped liver?

This version returns nothing. No info. No logs. It synchronizes and gives data on the one line (as shown in the small window) but nothing with the window maximised, using loger or dashboard. I've set all the recording file/locations as per the new directions. But then I had to eat a pizza and have some beer...

So I'll have time in the morning to give some real feedback. There was a new button that returned a new error but I don't remember what the button said. Redskins won so I've celebrated a little too much.

In the mean time, I still see both wrx and sti, as well as both logger and dashboard checked at the same time in the drop down menu. When I set them both they look good and stay good until I close and re-open the program. Then when I drop it down again, I see them both checked again. This has happened for a few versions, but they have all worked dispite, until this one. (I've only tried 1.9B as I didn't drive the car during 1.9's limited release.)

Its funny that logger-1 quit working for rainmanjam in version 1.9 because I didnt touch the sti decoder code. I dont know what would make it do that but hopefully I can find it. Its hard because I dont have an STi to test it on...just my lil ol wrx.

Man you guys are killing me! Tomorrow hopefully you will have your 1.9C up and working *cross your fingers*

Jeff

rainmanjam - Did you follow the directions in the readme file? I have used it and so far it works fine for me. apparently Type-C can get it to work ok.
No, I'm still running the old version. I didn't get your update on Friday following his post.

Well..its something in the magic.

Thanks for pointing out the double-checking thing. I realize now why it does that. I have the default for wrx and logger-1 to be checked. If you are sti and dashboard then it checks those, and leaves the other 2 checked as well. I always use wrx and logger-1 so I never noticed this even happened. It will be fixed for today's release.

Jeff

As a matter of fact...all things that used the checks were doing the same thing. Oops...somehow that slipped through the cracks all the way until now. Good find, 2phless!

Jeff

Ok I found the bugs in the sti version of the logger-1 decoder. If you dont have a tuner pro then it would basically crash. Same with wrx, i never coded the provision for if you didnt have one. I thought I took care of it a long time ago but I had forgotten one checkpoint that needed a if..then statement.

My way for testing was to run a STi log through the playback and perform the same code stuff. Well it works fine for me so I think it will work fine for all of you STi guys.

Jeff

Update: Version 1.9C is out! Ok STi guys, let me know how it goes! If you have a good .ini file then just only over-write the .exe file. VERIFY YOUR SETTINGS!

Jeff

As a matter of fact...all things that used the checks were doing the same thing. Oops...somehow that slipped through the cracks all the way until now. Good find, 2phless!

Jeff

It's been doing that for a while, but everything worked so I figured it was just a little graphic tweak.

I took a screenshot of the error that pops when I click on the charts link. But then I didn't put the image on my thumb-drive. :rolleyes: I'm an idiot. It was calling for a missing file. I think it was a .ocx? file. Something with the word 'chart' in it.

I'll try the C version after my last 2 final exams. :banana:

If you are missing a mschrt20.ocx then you need to download it. You can probably find it on the web somewhere. Its weird because they work fine on my old laptop that has nothing on it but the original windows xp home, no sp's or anything.

Jeff

http://freeware.it-mate.co.uk/?Cat=OCX_Files#m

mschrt20.ocx

Who would like to try the map editor? I've had it for over a week and have yet to even release it. Anybody interested? Oh btw it tunes your map for you :)

On a side note, I seem to be having problems getting uti to log anything on my old laptop/carputer. It doesnt update anything, not even tables. Its kinda hard to figure out whats going on because there is no screen! ahh! Well i might be missing an OCX or something but who knows.

Jeff

Are you serious about it tuning your maps?