RomRaider

Learning Table Values Tool in the RomRaider Logger...
This LTV reader requires a logger.xml with Extended parameters defined for your ECU ID. In addition it also requires an ECU definition for your CAL ID be set in the RomRaider Editor Definition Manager listing before you launch the Logger. The ECU definition provides information for these tables (ECU dependent):

• A/F Learning #1 Airflow Ranges or A/F Learning Airflow Ranges
• Fine Correction Columns (Load)
• Fine Correction Rows (RPM)

Caveat: Some early 32-bit ECUs (typically those ROMs 512kb in size) do not allow for reading portions of the ROM via SSM. This can impact reading the A/F Learning airflow ranges and the FLKC load and RPM ranges which results in display of 0s for the ranges.

I need some feedback to assist with the determination of the FLKC data table location in RAM. For ROMs where calculating the address doesn't work I've reserved a new Extended parameter ID (E173) to specify the address.

Vehicle Information alternate units of measure. The units for parameters displayed follow the units selected on the Data tab of the Logger.

For Subaru there's also a SSM based DTC Reader and a Global Timing & RPM adjuster too.

Supports BMW MS4x DME too!

EDIT: test files removed as there was a problem with refreshing the display after subsequent reads. This feature is in version 0.5.7 and higher.

Excellent work!! Can't wait to test it out.

I'm curious, why the secret development (not on git)? This is a perfect use case for a branch and snapshot.

Tested on A8DH202X, everything seems to be working proper.

It's not secret, the only part that's not committed remotely yet is the Learning Tables update, the rest is there already.

I don't think you understood correctly. I was referring to the private development and release build, not the actual code itself which is obviously public after releasing the jar. This is incredibly odd for a FOSS project that uses GIT for SCM, hence my curiosity. It's just really weird to have the right tools at your disposal and ignore them, especially after what happened the last time this was implemented. Is there some benefit to this process I am missing?

<3 - dschultz pm me your paypal

I tried to get it working tonight but ran into some issues. I havent tinkered with romraider in a while so I downloaded the latest 0.5.6 RC6 .zip and replaced all of the files in the rr folder. I downloaded your zip and renamed the .jar to .jar.old and dropped your .jar and def in the folder. I tried launching the logger and set the def you provided as the logger def, but when I hit f6 I got an error about ecu defs in the editor. I opened the editor and pointed to the new dtd defs. I tried the logger/f6 again but got the same error.

https://plus.google.com/photos/103956328804038432798/albums/5903293510342922177?authkey=CPOL5Kah5PWCQg

I might just be failing to do something correctly in the process. Any ideas?

Car: 2012 USDM WRX

You need to have the def for your ECU listed in the Editor's Definition Manager...not the DTD file.
In your picture you see CAL ID unknown beside the ECU ID in the lower right of the Logger, this means no ECU def's are set.

merp pointed that out on irc last night and I fixed it. I hadnt messed with romraider since last fall so I completely uninstalled and deleted the dir, and then reinstalled. I set the right ecu defs xml in the editor (tried eric's tp defs, and also tried pasting my ae5k500l section from his tp defs into the std ecu defs from the forums)and can open my ae5k500l rom, but i still get the same error about ecu defs when i hit f6 in the logger.

Please send me your rr_system.log and the def you are trying to use and I'll have a look to see what's up.

Here are the ecu and logger defs I am using, and the log file.

The rr_system.log states:

17853 INFO [Thread-5] - J2534/ISO9141 connection initialised
18113 INFO [Thread-5] - ECU ID = 8112585007
18115 INFO [AWT-EventQueue-0] - CAL ID: null, Car: null
18309 INFO [AWT-EventQueue-0] - Loading logger config for new ECU ID: 8112585007, loaded SSM: 117 parameters, 40 switches from def version 155.

Checking the ecu_def.xml you provided there is no match in it for ECU ID: 8112585007
You need to download the ECU def I linked in my previous post for your car and add it to the Definition Manager in the Editor before attempting to use the Learning Table Values tool. The ECU specific def is needed as it contains the location for the AF Learning and FLKC tables, without it the logger doesn't know where the tables are in memory.

Oh I must have overlooked the inline link to the defs. I will try this out shortly.

Ok lv is working now and the data looks correct.

Thanks for your work on this new lv and the help getting things working again.

Good news.

For the other problem please start a new thread to keep this one on topic.
thanks