RomRaider

I'm certain RomRaider can support this... I didn't even realize RomRaider handles switches differently. I just re-used the way EcuFlash handles OBD2 code enable/disable.... Looking at the way those are done in the RR definition file, I'm pretty sure it will work. You'd just create a separate table for each switch. These switches are one byte, 01 for enabled, 00 for disabled, so the table XML would be:

<table type="Switch" name="Enable Feedback" category="NSFW - Rev Matching" sizey="1" storageaddress="9087C">
<state name="on" data="01"/>
<state name="off" data="00"/>
</table>

<table type="Switch" name="Enable Calibration Feedback" category="NSFW - Rev Matching" sizey="1" storageaddress="9087D">
<state name="on" data="01"/>
<state name="off" data="00"/>
</table>

I don't have RR installed on the laptop I'm using now so I can't confirm. But give it a try, and compare the files you get when turning the switches on and off in RomRaider and EcuFlash. I bet they come out the same.

I actually prefer RomRaider's UI, but EcuFlash definition XML is just easier to deal with because the files are so much smaller. Thanks for porting this over.

Thanks! I didn't know I could use two different addresses. That makes it simple.

I can post my romraider xml files for A2WC522N and A2WC540F once I finish and confirm they are accurate.

On a separate note, dschultz has a simple tool that converts rr to ecuflash. I haven't looked at the code to see how simple it would be to create one that goes the other way.

Here are xml files formatted for Romraider. I've included both my A2WC522N and the current A2WC540F.

Thanks!

This is almost too cool to be true... I'm even on A2WC522N.
After I wrap my head around what it takes to get this goodness into my life and maybe I'll flash it over this weekend.

I was gonna say just apply the patch... And then I looked for it. And found out that I forgot to post it.

I'll add it tonight or tomorrow.

Didn't you post a stock A2WC522N that was patched to A2WC540F?

Can't we just copy our tables from our rom to that?

Would it be easier to just patch our current rom?

Thanks.

Copying tables works, patching just takes less time. The resulting file will be identical either way.

I should also add that there's one more version coming, and patch-unpatch-repatch will be a lot easier than copying all of your tables twice.

I still want to allow multiple brakeless downshifts with just one tap of the cruise-cancel switch. I've been meaning to do it all week but haven't found the time yet. Hopefully this weekend, though.

Cool. Thanks. I've never patched a rom before so I'll have to read up. Is the information on that in the forum regarding patch.exe?

[Edit - I've removed this version of the patch, and added a newer version further down in the thread.]

At some point I changed my local copy of RomPatch.exe, so I'm including that here too. The version in the RomPatch thread can't apply the patch file. Not sure what's different in my current copy but I'll dig into that later.

Usage is still exactly as described in the RomPatch thread:
viewtopic.php?f=32&t=7892

I should really get on board with newer tools like Merp's SharpTune at some point.

As noted above, non-braking downshifts require one tap of the cruise-cancel switch per downshift. I plan to allow consecutive downshifts after a single tap of the cruise-cancel switch in the next release, but that's the last change I have planned.

Yes, RomPatch doesn't know how to fix the checksum after applying a patch.

I did a quick search and saw it so I deleted my post.

I patched and flashed but I don't seem to be able to get it to enable. I also pulled a LV and the ecu is still labeled as A2WC522N. Is there a table I should have enabled first? I'm not home but I'll dig in to the rom again when I get home.

Learning view looks at the other id, 2F12785606, which isn't changed by the patch.

Try making a data log that shows these parameters:

Rev Match State - this will indicate whether it is being enabled or not
Rev Match Cruise Flags - this will show clutch, brake, etc
Engine Speed
Rev Match Target Upshift RPM
Rev Match Target Downshift RPM

If the state and target-RPM values are just zero, then the patch wasn't applied... if they're above and below the actual engine speed, then the patch is there, and the question is what's preventing it from being turned on.

Speaking of which, it won't actually work until the coolant temperature is up to 160F, so after a cold start you'll probably have to drive for 5 minutes or so. That threshold is adjustable (Rev Matching, Minimum Coolant Temperature Thresold), but the idea behind it was to avoid high revs until the engine is fully warmed up. It takes oil another 5 minutes or so to catch up to coolant temps, so keep that in mind as well. Unfortunately there's no sensor for oil temp though, so coolant temp was the next best thing.

Also, read these if you haven't yet:

https://github.com/LegacyNsfw/EcuHacks/ ... v-Matching

https://github.com/LegacyNsfw/EcuHacks/ ... v-Matching

Nevermind....I'm dumb. I had misread enable instructions. I thought it was cruise on/off switch rather than cruise cancel.