RomRaider

I thought that EcuFlash was fixed for this, maybe in a more recent version than you are using. Did you happen to try clicking in a cell of the table and using the cursor down key to navigate/scroll the table?

If the only workaround is to edit the table in RomRaider Editor then you will need to create a RomRaider style definition for the Editor to use. You can use the LTV def that I posted above and add to it.

• To start you will need a copy of the official ECU defs posted on the forum.
• Next locate the MAF scaling table name for the non-SD version of your ROM in the official def, start your search on the non-SD CAL ID to locate the appropriate <rom> section.
• Copy the entire <table ... /> entry from the official def into the LTV def in your SD <rom> section. Just paste it on a new line after the FLKC table entries.
• Go back to the official def. You need to know the exact name of the MAF scaling table, the part between the quotes of the name= attribute.
• Copy the quotes and the name for that entry.
• Move to the top of the def file and search down for 32BITBASE
• Search again this time for the MAF table name, the name you copied, so paste that name in the search field from the clipboard.
• This should bring you to the MAF table definition. Copy all 7 lines starting with <table ... including the line </table> just after the description line.
• Move to your LTV def and scroll to the 32BITBASE section in it.
• Paste the lines you copied after the last table entry.
• Save the file.
• Open the Editor and make sure that the LTV def is added to the Definition Manager window and make sure it is the first item in the list, Save the change.
• Open the SD ROM and you should get the MAF scaling table in the tree on the left.
• Edit, save and flash the ROM as you need.

Soon you will be an XML and definition wizard!

Holy moly! That makes my head spin just thinking about it. I am going to give it a shot though and no ecuflash does not scroll even if I use the arrow keys.

OK, as a less complex option you could just paste the <rom... </rom> info from the LTV only def I provided into the official ecu_defs.xml. Just paste this code above the last line of the ecu_defs.xml file:

Make sure ecu_defs.xml is in the Editor Def manager at the top of the list. Then open the SD ROM and you should see all the tables as if it was a non-SD ROM.

This will also enable the Learning Tables View feature in the Logger to work properly.

No worries! I'm glad you brought it up so that it can be fixed. Unfortunately the time just wasn't in the cards this week. I'll be updating the build process when I start to integrate CEL flashing into the free roms, but a decision needs to be made regarding fixing RR's definition mess or to just keep polishing a turd.

Thanks for helping him out Dale.

I thought the consensus was to work toward a def style with single file per ROM in a directory hierarchy and integrate the logger ECU specific information into the def as well. That's what I believe was last proposed.
There's just quite a bit to change. So I think it's still the plan, just time is the enemy.
BTW: Scott has managed to provide units switching for tables in the Editor so the user can choose metric or standard on the fly, that's some progress which will eliminate multiple units specific def files.

Using those defs you posted D, can one use romraider editor to edit Merps sd roms?? This would be awesome if it all worked rather than having to use this or that or the other to do the map editing.

No. There would need to be a migration of the SD table definitions into the RomRaider style definition first. It's not that difficult once you know what needs to be copied over to the BASE def and which element and attribute names need to be changed. But once finished it would be easy to migrate more ROMs over if someone was inclined to do so.

I'm in a similar bind, I downloaded the LTV template dschults posted and edited it for my rom A8DK100Y, also tried adding the code to my RR logger definitions, however the LV function still won't work, and whines about no proper ecu defs present.

I've probably done something wrong, but can't figure it out.

I'm able to check the CEL via the Logger Software, but am not able to remove them via the ECU RESET function, the same CEL is still on in the cluster, even though the software says the ECU has been RESET.

I'd appreciate any help massively.

If you can provide the ECU def for your current ROM I'll fix up something you can use.


FYI: I'm and 1/4 the way through adding support for the SD ROMs into the logger def.

I'm not sure if I got what you meant, but here's the ecu_defs.xml im using (opens the SD rom in RR just fine)

That should work assuming that the ECUID in your def is the same as the one reported by the RR Logger.
What does the Logger say in the lower right of the window?
If it says CALID: unknown then you have no valid ECU def defined in the Editor settings.

Today it decided to work, don't know why it wouldn't work yesterday, but at least it's working now, and got the CELs cleared.

Thanks.

How have SD ROMs changed to not be compatible with it?

SD Roms haven't changed at all. RR started enforcing a DTD check for empty parameters. I went throught and fixed all of the ones published in my git repo, so everything should work again with the latest files.

Hey guys I need help. I have a 2004 Sti and I copy and pasted all my tables over to the Merp Mod A2ZJ710J and flashed it to my car. Everything is all good, but I cant figure out how to get the logging to work right. CL/OL is way out of whack (almost like a counter) along with manifold absolute pressure 4 byte I believe. I have searched, and found some things, but I have no idea what I am doing with the definitions. I no nothing about programming language. Will someone help me?