utec logger configuration and use

ride5000 · **Joined:** Thu Aug 03, 2006 10:40 am **Posts:** 1934

so i've finally got my mitts on kascade and tgui's code for enabling utec logging with the RomRaider logger.

and, Hallelujah, it works!

however, one thing i've noticed is that the entire list of utec logged fields are not showing. for example, this is a screenshot of my RomRaider logger once the utec logger is started and polling:

http://www.ken-gilbert.com/ftpupload/screencap.JPG

as you can see in the bottom left i get the following utec fields:

knock
psi
wideband
test data

now, one thing i should point out that may be affecting things is that i run my utec in speed density mode. the columns are defined as follows:

Code:

     DATA1

    ,     ,    ,   ,Load,Knock,    ,      ,      , Mod,  Map ,     , Mod,  WB 
 RPM,  MAP, MAF,TPS,Site,Count, AFR, Ign#1, Inj#1, Ign,   VE ,Boost, MAF,  AFR
    ,  psig, V , % ,    ,     ,    ,  deg , duty , deg,   %  ,(OL) ,  V ,
  836, -9.4,1.3,  0, 00,   00,  14.8,+12.7,   1.6,ECU. , 88  ,ECU.  ,1.3, .....
  839, -9.4,1.3,  0, 00,   00,  14.8,+12.8,   1.6,ECU. , 88  ,ECU.  ,1.2, .....
  832, -9.2,1.3,  0, 00,   00,  14.9,+12.8,   1.6,ECU. , 88  ,ECU.  ,1.2, .....
  828, -9.4,1.3,  0, 00,   00,  14.8,+11.4,   1.6,ECU. , 88  ,ECU.  ,1.2, .....

the following appears in the utec.properties file:

Code:

utec.sound=true
utec.commandTransmissionPauseMS=500
utec.dataTransmissionPauseMS=1
utec.afrIndex=13
utec.psiIndex=1
utec.knockIndex=5
utec.startLogging=33
utec.startMapDownload=101,*,19,19
utec.startMapUpload=101,*,21,13,*,13
utec.resetUtec=24,24,24
utec.loggerIndexes=0,1,5,6,7,13
utec.loggerTitles=RPM,PSI,KNOCK,IGN,DUTY,AFR
utec.loggerDataRanges=0<>7500,-14.7<>26,0<>10,0<>80,0<>110,0<>16
utec.fuelMapMin=-8.0
utec.fuelMapMax=8.0
utec.timingMapMin=10.0
utec.timingMapMax=40.0
utec.boostMapMin=0.0
utec.boostMapMax=500.0

utec.boostLimitWarningMaxAcceptable=19.0
utec.injectorCycleWarningMaxAcceptable=99.0
utec.knockCountWarningMaxAcceptable=0.0

it LOOKS like the three fields i get in the logger are enumerated here:

Code:

utec.afrIndex=13
utec.psiIndex=1
utec.knockIndex=5

those fields are defined, positionally, by the following line:

Code:

utec.loggerIndexes=0,1,5,6,7,13

and labeled here:

Code:

utec.loggerTitles=RPM,PSI,KNOCK,IGN,DUTY,AFR

now, i COULD be way off base (it wouldn't be the first time) but it seems to me that i could turn on and turn off the various utec fields by altering the three above-mentioned lines of code.

yes?

ken

ps. this program is a godsend... i'm very excited to start logging and tuning with it. one stop tuning FTW.

Tgui · **Joined:** Tue Jul 11, 2006 9:25 pm **Posts:** 1025

Wel, haha, the issue is that its a half assed test program. Your interpretation of the config file is close. utec.indexAfr (etc) is for the integration of my software with kascades logger. Everything else you wrote is spot on :-)

I have not made and intelligent way to log other logger #1 attributes other than altering the java code. At this time you should be able to modify the utec.Afrindex* values to use other logger #1 data.

What would really help is for you to define a config file that works the way you think it should, and I'll try to code against it. Since this 2 year old test program (yes, that old) has only been tied to my car, I need someone to monkey with it and suggest functional changes.

Also, there should be 3 additional values available for logging. I added them before I sent you the build. At least I thought I did. The codes at work, so any further updates will have to wait till later in the week. Also, the next release will be using that new tuning entity GUI I've been working on. Lots nicer than that test program crap.

PS the simple dashboard can only handle between 6 and 6 attributes

Don't expect too much.

RomRaider

Forum rules

utec logger configuration and use

Who is online