RomRaider

RomRaider mostly runs well on my Windows 11 laptop and communicates well with my ecu. Ecu parameters plot and log as expected -- except for the VANOS group (0b90). The Motor Values (group 0b03) graph and log as expected, so that shows me that RR can handle parameter groups properly, but what is wrong with the VANOS group escapes me. I've carefully studied the logger definition file (v370) multiple times, but can't detect what might be causing the problem.

Both the attached debug file and a captured USB sniffer file (not attached) show that a logging parameter request for group 0b90 is never sent to the ecu, even though various VANOS parameters have been selected in the UI. As you can see from the screenshot, part of RR knows a VANOS parameter has been selected, but displays an implausible value (namely 0, when it should be around -100). The IAT value in the plot is plausible (car is cold in the morning).

Other apps have no problem getting results from 0b90 requests. For instance, the MS4X Flasher Command Sender returns 1211a0a0a09efc80007878780d80004dfa

The command to query the VANOS group is not present in the log. Did you try logging just a VANOS parameter on its own?
Please provide the log when you do so.

No, I didn't. I'm away from home for a few days and I didn't bring my K+DCAN cable. I'll be able to try that in a couple of days.

After searching in the source code, I think I may have found the root of the problem (starting at line 173 of src/main/java/com/romraider/logger/ecu/comms/io/connection/DS2LoggerConnection.java):



I'm hoping maybe inserting will solve the problem.

To test that out will require rebuilding RomRaider with modified source code. It'll take me a couple of days to figure out how to do that.

Success!

Adding that one line in my last post above fixed the problem.

For the build with the modified code, I followed the instructions from Walter Stypula on Github https://github.com/RomRaider/RomRaider/blob/master/docs/Building_RomRaider_VSCode.md and used the resulting standalone app to see that the VANOS parameters were being handled as expected.

As far as this issue is concerned, there is no need for further troubleshooting.

Thanks for catching that, I'll add it and publish a new release.

Hello folks! I have the exact same issue. I was looking for a new release, but I did not find anything. Am I missing something?

Please find below a snapshot (ignore wideband value, the decimal is one spot off) and the debug file.

Could you please help me, so I could log Vanos values?

Thank you!

I guess I forgot to cut the new release. I'll post when it's ready.

Thank you very much!

Since I might not get to issuing the release quickly, you can use this patch to correct the VANOS query issue.
Copy the contents of the ZIP file into your "C:\Program Files (x86)\RomRaider\" directory. You can overwrite the existing .jar file or back up the original first if you wish.

Thank you very much, during the weekend I will try it!

It works perfectly, thank you very much!