RomRaider

This post explains how to get the RR LTV working, of course, substitute the appropriate values for your particular rom:

So I would replace the bold with my ECU/ car info?

The MerpMod.gratis... is the RR Logger definitions that came with the MOD. So I copy and past this into the official ecu_defs just before the last line? Just making sure I am doing this right. File size should be 512kb, yes? Because I am working with the A2ZJ710J SD rom.

I changed the ROM ID back to what my ECU was before I flashed it so it is not the custom ID that it had after patching. I got learning view to work, but some of the parameters I try to log in RR logger are all out of whack. Such as CL/OL, it counts up to maybe 200 then resets quickly.. No idea what data it is reading.


<rom base="A2ZJB11J">
<romid>
<xmlid>A2ZJB11J.MeRpMoD.Gratis.Testing.v13.4.29.1236</xmlid>
<internalidaddress>E1000</internalidaddress>
<internalidstring>A2ZJB11J.MeRpMoD.Gratis.Testing.v13.4.29.1236</internalidstring>
<ecuid>134291236F</ecuid>
<year>05</year>
<market>USDM</market>
<make>Subaru</make>
<model>Impreza</model>
<submodel>STi</submodel>
<transmission>MT</transmission>
<memmodel>SH7058</memmodel>
<flashmethod>sti05</flashmethod>
<filesize>1024kb</filesize>
</romid>
</rom>

so is there a useable learning view? I am trying to read DTC's...

For DTC reading you either use an OBD scanner, or switch to the latest official logger.xml which contains the DTC info for the RR Logger to read DTCs. You can switch back to your SD logger def after.

There's this option too, if you don't have an OBD scanner and your ECU supports CAN logging:
viewtopic.php?t=9401, see Note #4. This is still valid for the latest version of RomRaider, you don't have to down grade.

I've added the <dtcodes> to the logger definitions, available @ https://github.com/Merp/SubaruDefs/tree/MerpMod

I'm not sure if they'll work without adding the customized stub discussed above to ecu_defs though.. Dale?

I'll have a go at it tonight in any case.

Writing some code to output all current defs to ecu_defs.xml is in the works for interim support and should knock out all of the compatibility issues with LTV/DTC views.

thanks merp, i know it takes alot of time to rewrite code. It's too easy just to repoint def's to read DTC's though...

The DTC feature is not ECU dependent but it does require a version attribute in the logger element or it will nag you to update the logger.xml. I suggest this version syntax for SD logger defs: viewtopic.php?t=10291&start=3
Only Learning Tables is ECU dependent as it relies on ECU specific ROM addresses so there has to be a way to look it up per ECU ID.

For Learning the dependency paths are as follows:
1) Ecu init -> ECU ID -> logger.xml -> AFR Correction & IAM ECU specific addresses
2) Ecu init -> ECU ID -> ecu_def.xml -> CAL ID -> ecu_def.xml -> FLKC Table Load Columns & RPM Rows

Tested this out and DTC stuff works fine.

I don't like the idea of a version string in the definitions. Well, at least for this purpose. This kind of compatibility check should be handled by the actual content of the file rather than a single attribute that can be fudged.

Right now it's a trade-off between compatibility and flexibility. I opted for the flexibility option as the other would have left zero support for SD ROMs. It will be easy to switch to compatibility checking once the definitions catch up to the feature support.

I disagree. That may be the case for an all-or-nothing DTD check (bad idea for this purpose), but for a well thought out check, it's quite the opposite. First load definitions as they are, then check for the dependencies when they are needed. If a dependency isn't met while loading new feature X, throw exception -> warning.

In any case, its not a big deal now and I can't say I've never done anything quick & dirty myself Thanks again for all the hard work!

And that's exactly how it is coded. The exception/warning is presented to the user in a way that they can attempt to locate a fix with some tangible information, i.e.: a version number in this case.
I agree it's not the best. It can be easily fixed (the message removed) when the defs catch up and become consolidated.

I think I missed something, but why is it when I try to use the supplied logger definitions for the merp mod with romraider it says the definition is not configured?

I'm able to load the latest definition for A2ZJ710J MerpMod without issues on RR 0.5.7 RC2. I still see the warning regarding logger xml version, but I'm not seeing the 'Logger definition not configured' message. Try updating everything if you're not on 0.5.7 RC2 or haven't downloaded the definition today.

I will try to uninstall and re install RR. I was confident I had the most recent one.. And the earlier post with the code I would use for the RR ecu editor to load up the SD rom correct?

The stub might let you open up the OEM tables, but there aren't any definitions for MerpMod tables in the RR editor. The main purpose is to enable learning table view. If you're not sure what to copy over to that xml stub, open the rom in ecuflash and look at the 'ROM info' section. Also filesize should be 512kb.