RomRaider

I've taken a crack at adding OBD logging support to the RomRaider Logger.
With OBD query mode 1 you should be able to log any vehicle that supports OBD on CAN.

There's still much to be done, no error checking, etc...

User logging profiles will be overwritten if you re-save an existing one, so backup all your logging profiles so you can restore them after you finish playing.

To use OBD mode you must use the latest Logger definition files and select OBD protocol in the Logger Settings menu.
You must use a J2534 compatible cable.

Also, disable the "Control File Logging With Defogger Switch" setting in the Logger as there is no parameter to monitor the defogger switch at this time.

Great...

Starting with mode1 and adding the other modes someday
I will test this weekend.

Dale, if you need a translation of the PIDs, give me a shoot...

Sure I'll do that once I have them all defined.

Please let me know of any PIDs that report incorrect data from what is expected and provide a log of the parameters and a rr_system.log with DEBUG enabled only if there's a problem. Also check each of the conversion units too, i.e.: lambda/AFR/VDC, °C/°F...

OBD PIDs are routinely traced in the code and most of them are calculated similar\together with SSM values ( if applicable ).

My concern with PID item accuracy is not on the ECU side but in the logger.xml def where 'word' and 'dword' splitting is required to get the correct information for the final calculation, not the calculation itself. For example, PID25...

I've linked a new test version (2) in the first post. It has some corrected Logger code (including MIL/ECU reset) and a new logger.xml with some corrected parameters and a number of new parameters, all to be verified, including each parameter conversion.

Excellent work!!

Couldn´t get a proper connection to EURO4 and EURO5 Diesel ECUs:

But behaviour is differened:
- on E4 ECU, I get Cal-ID and Rom-ID displayed in RomRaider but a failed connection to log values.

- on E5 ECU the Cal-ID and Rom-ID aren´t displayed and also I got no connection to log values.

If I take a look in the system.log in both cases, there is a connection and both IDs are read.

But take a look on your own:
(Maybe compare the E5 connection to the CAN-sniffs of workshop OBD connection)

Jochen

Please try again but disable the "Control File Logging With Defogger Switch" setting.
The responses in the logs appear correct exception for the defogger switch.

That is the solution: without choosing "Control File Logging With Defogger Switch", I can sample the OBD-values
Great !

Thinking about this "problem", the reason is very clear. So in OBD-Mode, you need to ignore this commant and you need to start logging in a other trigger.

One problem still exsists:

on E5 ECU the Rom- and Cal-ID isn´t displayed, but I can see them in the system.log. On E4 ECU it is fine

Today I only do some onbenech tests. Nearly all values look good.
Only Railpressure also needs to be displayed in MPa, too

See attached the systems.log, if anything interesting in:

Jochen

You have no ECU definition XML defined in the Editor for the E5 ECU. Add the definition and it will display the ECU ID.

I've linked a new test version (3) in the first post. It has more corrected Logger code and a new logger.xml with some corrected parameters and a number of new parameters, all to be verified, including each parameter conversion.
Conversions can be added as required. Please list the PID as displayed in the text tip for the parameter.

Lastes update works proper with both diesel ECUs

No problems or wrong skaling of the values, with are supported by the Diesel-ECUs

I ran it today. It works great as far as I can tell. I haven't checked out the log yet, but I did watch some of the parameters live on my laptop. This is on an FR-S. Good job!

Awesome work - thank you! Tried this on my BRZ and it worked.

I am however not able to see IAM or FBKC or FLKC ect. I am a nob with this sort of thing. Is this normal and prehaps coming later as this is developed?