RomRaider

It does have learning view functionality but it does not work with modded ecu ids i.e. merps sd roms. Attached.

I am one of the unfortunate few who have one of those ecus that do not reset when I flash a map so I need some sort of utility to reset my ecu everytime I flash a map. Learning view does not recognize the ecu id either.

FYI: You can still use the ECU Reset Function without clicking on 'Connect'

You can also Reset the ECU from the RomRaider Logger Tools menu.

With a minimal RomRaider ECU Def that defines the tables needed for the AFR ranges and the FLKC ranges then you can use the Logger to get the same Learning info.
Here's a sample of what you need to use. Set the RR Editor Def Manager to use this def and the CAL ID: should then be reported in the Logger lower right of the screen along with the ECU ID.

I would but the newest version of romraider logger 5.7 r2 does not work with any of merps modded sd roms. If I point it to the proper xml definition in an older romraider version it logs all of the parameters just fine. If I do it in the newest version it keeps insisting I go online to get the latest romraider ecu defs.

It would be a time consuming task uninstalling an older version of romraider, installing the latest one, cutting and pasting files over, just to get a learning view? Do you understand what I am saying? With the sd roms it is a catch 22, yes the latest romraider has the capability to do a LTV but it cannot log with merps modded roms.

How do we fix this???

No not really...

Here's how it is suppose to work...
Logger starts up and checks the definition file version (i.e.: <logger version="185"> ). If the version is not found or is too old you get a warning. There's two ways to fix this 1) add the version string to the logger.xml you are using or 2) copy the SD parameters info to the most current logger.xml and add the unique SD ROM ECU ID to the XML. How do I add it you ask? Find/replace the non-SD ECU ID with the SD ECU ID.

Now the Logger has a good def and does not complain about the version. All the SD parameters are there since you just added them. With that the Logger connects to the ECU and gets the init string. From within the init string the Logger parses out the ECU ID. With the ECU ID the Logger can now filter the logger.xml and present to you all the compatible parameters to log.

If you get a CAL ID: unknown then you don't have an ECU def defined in your Editor Definition Manager. In the RomRaider definition for your ROM your need these two things, 1) the ECU ID that you are using and the CAL ID that it cross references to.

In the sample I posted above you can adjust them as required for your SD ROM. Once you do this then point the Editor Def Manager at your new RomRaider def file (Note: EcuFlash def files will NOT work as they don't contain all the required info for RomRaider). The next time you start the Logger, if all cross references correctly then your should get an ECU & CAL ID in the Logger window. If not then go back and fix-up the defs as I describe above.

Once you get the ECU ID & CAL ID to show up correctly AND you are using a def version of 155 or higher (which contains DTC info for the DTC reader to work) then you should be able to use the Learning Table View feature in the Logger tools.

Give it a try and if you still can't make it work then post up the files you are using and a copy of the rr_system.log (with TRACE level detail) in a new thread so we can see what's going on under the hood.

This is one of the most helpful posts I have ever seen on RR. When I get back to my tuning this weekend I will sit down and go through each step on all 3 of my logging netbooks. I want to be up to date with everything so it all works the way it should.

Thank you for taking the time to walk a "non-it" guy through the steps so that I can understand and accomplish them. I will test it this weekend and get back to you.

I've confirmed that 0.5.7 has broken all of the SD defs. I'll see if I can get you a fix before the weekend. It's ridiculous for an end user to have to go through all this to fix a bug caused by lack of communication between the developers.

Thanks Merp. No hurry. I got everything except for learning view working on your sd roms for both the baja turbo and 05 sti.

Interesting as I just described how RomRaider has worked from the very beginning. How have SD ROMs changed to not be compatible with it?
The addition of DTC reading is purely SSM so that should not change anything.
The addition of Learning Table Values only relies on ECU ID -> CAL ID -> RomRaider Editor def for the CAL ID. This hasn't changed either, only enhanced to support LTV.

Please show me where it's breaking down.

I looked this over and confirmed that the steps I outlined above will allow you to use all the functions of the latest version of RomRaider Logger. You just need to build your own RomRaider style ECU def as none is provided as part of the SD patch process.
Another anomaly I noticed is that the logger defs provided with the SD patches have <ecuparam> elements defined with missing <ecu id="##########"> elements. This violates the DTD check as at least one <ecu> element must be present. It will also through an exception when the def is parsed upon loading.

Here's a working set for a patched A2ZJB11J ROM so you can follow along.

Yep, ecuparams with no ecu element throw an exception that barfs the whole definition since https://github.com/RomRaider/RomRaider/ ... 6e4f578b75

Yes EcuAddressImpl.java was changed back in May to support non-contiguous SSM addresses for multi-byte parameters for TCU queries by adding an additional function. The functions check for a null address and throw an exception.

The simplest solution at the moment is to delete all <ecuparam > elements that have no defined <ecu> element from the logger def file as per the DTD.
Using the XML Tools plugin of Notepad++, it's easy to validate, locate and correct XML errors.

It's much simpler to add a well directed try catch to preserve the compatibility with files that work perfectly fine aside from adhering to a previously unenforced pedantic standard belonging to an atrocious xml schema that should be binned asap anyway.

Sure we can add additional error checking to handle malformed XML data. I'll add it to the list for the next update.

I did not mean to start a spat between developers and am sorry if I did so. It is just something I noticed while using the wonderful programs/mods you have created and am thankful for. This allows me to be free from paying cobb royalties on a 25 dollar gameboy that sells for 600. With that being said I have another query you can perhaps help me with.

Now that I have converted both of my subies over to Merps wonderful sd roms I am having trouble viewing the entire maf scale in ecuflash. The normal workaround for this prior to the sd roms was to open them with Romraider ecu editor, edit the maf scale there, save it, and then open it with ecuflash. Is there a way to open Merps sd roms in romraider ecu editor? Is there a way to create a scrolling screen in ecuflash??? I am using ecuflash version 1.32, windows 7 home premium, and vagcom cables in both of my subies with great success. My 05 STI is on full speed density and after I build another motor for the baja I would love to utilize speed density as well. Until then, I am stuck on the maf scale for the baja so I need to be able to see then entire scale on the screen to edit it.

Thoughts? Workarounds?

Thanks for your valuable time.