RomRaider

ok, so I am having a hell of a time with the OP2.0 standalone support. seems so many things are just plain wrong information wise... but am slowly wading through it. I am fixing all the incorrect things on my logcfg, but in getting all the information I ran into a question.

there seem to be different hex values for 1 byte, 2 byte, and 4 byte values. my impression was that the hex value corrisponded to a sensor, or switch, or one specific thing and was then parsed, scaled, and mathematically altered to give a understandable value. but with a different hex for each type, is there something else in the works? in the standalone OP2.0 logging parameters, you can set 8, 16, or 32 bit to get your desired resolution... but I suppose my next question is if it needs to match the specific hex, or can i just change the bit rate to what I like? if it has to be a specific setting, does anyone know what value corresponds to which type? was guessing ECUBIT (0-5?) or maybe ecubyteindex.... but not sure.

finally, if anyone is familiar with the standalone setup... is there a way to format it properly, instead of having all the long numbers? I can do it in Excel anyhow, but would be nice if I could write it in like RR does.

The app you are working with is out of date with the parameters that the OP2 wants in the config file. No longer do you specify the bit length for values that are floating point, you use a keyword instead. If you use the site I suggested you can get a working base file, then modify it as required. Using the RR Logger while connected to the ECU, you can hover over the items and get the parameter#, P or E, etc. Then look them up in the def for the required conversion and address. All addresses should be stated in 6 hex bytes.

Why not just update your logcfg.exe from this link? I've been using it for ages now, parses everything correctly.

http://forums.openecu.org/viewtopic.php?f=57&t=4396#p22315

I would love to use the app... but that requires a settings.XML file that I can never attain. Tried on two computers now.

You need to set up Romraider to have the application and and find the settings.xml file (by default it is set up in \Program Files\Romraider\ directory on setup).

I see Dale already answered that in the other thread you started - did that not help? Have you tried running it with administrative rights - or maybe try and pop the settings.xml file from the romraider directory into the directory where you have logcfg.exe?

The OP2 cfg app looks in this directory. If you are using 64 bit Windows you will need to make the directory and copy the setting.xml to it. But before you do that you need to completely setup RomRaider with ECU defs for your car and a working Logger configuration. The OP2 app requires this so it can read the appropriate files as defined in the settings.xml.

I understand this.... the rub is that on two computers now I have installed RR.... copied over the latest logger, ecu, and cars xml files. run and configured RR, opened and even made adjustments to my rom, opened the logger, connect to and was shown the values for various parameters of my car when running.... no settings.xml file exists on either computer... one computer has it installed in the (x86) program files, the other in standard program files...

I fully comprehend and understand what you are saying.... unless there is something more that I am missing I have no idea what else I can do to "setup" RR in order to spawn this elusive settings.xml file. I've run in admin, standard, under different user accounts and even safe mode for grins.... there has to be something else.... I've re-installed 5 times now between the two computers.

Dschults - regarding the float... I take it those that have the parameter of [storagetype="float"]. so, no bit rate needed, but still a RPN scaling correct? I think I finally have it worked out, lab went to hell today so didnt have time to test my last version to see if I had it right or not, but didn't check for float variables... will double check it, rewrite and then test tomorrow. hell, by the end of this I will have learned how it's all programmed and wont even need the program... maybe for the best anyhow.

oh, regarding float again, in the op2.0 it says the 1 value defaults to 32 bit... are ALL float parameters logged in 32 bit? does it matter?

Oops, dumb me, I forgot to mention that the settings.xml is now in the users home directory. In the Logger go to Help - Debugging Level - Open Debug Log Location. The file you need is there. Place a copy in the \Program Files\RomRaider\ directory and OP2 app should be happy.


Have you reviewed any of the sample configs provided in:
C:\Program Files\OpenECU\EcuFlash\samples\logging\

Yes all float are 32bits in length. Just indicate the parameter isFloat=1
Scaling is only needed if you wish to convert the return value to something other than the ECU native units (i.e.: temperature is in Celsius). Here's a sample with various types of length and scaling:

heh, knew it had to be something else.... all is working now. the ironic thing.... my new logCFG.txt from the app was only wrong in one location compared to the one i was working on just by pouring over the logger.xml file... so good learning experience for sure...but this makes it SO much faster, and at least I know how to troubleshoot it if it does not output properly.

thanks for the help dschultz.