RomRaider

Yeah, I can leave the core functionality for map switching and it would be a simple matter to add the on-the-fly switching capability latter without having to change anything. That way, I can add it after I figure out how to flash the CEL.

I won't go meth until I can switch maps on the fly via a hardware input (failsafe/disarm switch).

I want fuel, timing and boost tables for each mode.

The current method of cutting boost to WG is a hack.

So something that gets me closer to this functionality is what I'd vote for.

all you need is a failsafe hooked up to your bcs so you can run wastegate pressure in case the systems fails. why worry about switching maps when you can have something simple and effective?

I don't think its a hack, but it definitely isn't as streamlined as a true map switching setup.

It would be as simple as changing the switching code to look at the binary input rather than the subroutine (right?) that checks for the sequence.

I think the best option is #2 without the button sequencing at first.

Maybe the location of the switch bit could be set up as a RomRaider or RamWriter table/option, with some kind of protection for basic users. Then we could list locations for various binary inputs (TGV's, etc), although, it might be tedious to find those locations for all the roms..

I think that is something that can possibly be supported later, but the initial release should be as simple as possible so the core functionality can be fully tested.

do you think switching fuel and timing tables in the middle of a pull is a good idea?



i'm going to go with a hell f*** no on that one!

It sounds like he wants it soley for a failsafe rather than a hydramist style setup. I don't see any issues in switching to a pump map from a meth map in the middle of a pull when it fails. Although I would still run the bcs disable code in addition to the map switch, encase there is an error in the map switch.

I've started on the overall design (no coding just adding controls), so I can get a better idea of what's involved. It turns out that version 3 is not going to be any more difficult than version 2 in developing RamWriter, so I'll likely go with version 3. The upside is that I don't have to mess with adding the LUT to the upper flash area, meaning it could be used for something else and this also makes ROM patching simplier. The downside would be a slight reduction in the RAM hole available for tables (probably about 80 bytes or so including checksum for LUT).

This is how it would work (tabbed control):
Table Profiles - here you would create table profiles based on a specific ROM revision and the map assortment you want. This has nothing to do with an actual ROM file - you just select your ROM revision (say A4SGE01C 02 USDM WRX), then select the tables you want (within the allowable space/number of tables for that revision), and save it with your own description. You can create and save as many different profiles as you want.

Patch ROM File - this would simply allow you to patch your ROM (if supported) with the RT code (and other integrated features like LC and per gear wg comp).

Write to RAM - This would take a source ROM file, a table profile (new or existing), and copy the specific RT tables from the ROM file to ECU RAM thereby updating your tune (and possibly a new map assortment).

I want it as both a failsafe and a disarmed mode via switch. When I'm not on meth/WI I want the car to run like it doesn't have meth. Normal fuel/ign & boost. It's failed, The tank has run out, or I want to save some for later.

Same could be used for nitrous.

That shouldn't be a problem, The switch and failsafe would be wired parallel, and the ecu would look at the binary input instead of the ram bit, and look for a closed circuit to switch back to the rom (non-meth) maps.

Good to hear things are getting started.

Sorry to dwell on this one in the past.. but... do you know of a way to do this? I like the idea until something more elaborate can be developed.

Run the output of the failsafe relay to a solenoid on the wastegate vaccum lines... when it cuts, you're down to wg spring pressure.

Exactly. Just route all flow to the wastegate and you will run wastegate pressure. If you want to be super safe, go into you fuel map for those load sites that correspond to that boost pressure and richen them up a bit.

merchgod, thanks again for your idea. I've got it running on the Evo. So the sequence is - edit maps in Ecuflash which are in a ROM "shadow" area (which is copied once to RAM when the ECU is restarted but not when the engine is restarted), save to file, my application reads the file and writes the ROM shadow area to RAM using DMA and reads it back to verify. It is working for a 1k block and does the whole thing in 0.33 secs. When I do 2k I get a timeout that I need to fix. To make the changes permanent we just reflash the whole file to the ECU.

Awesome! How are you handling data integrity? That is, what happens if the write fails?