RomRaider

It may be to late or maybe already discuss. It would be nice if we could choose what we fields to use for real time tuning. Example. Say I want to work on the timing. I could choose to use only the components to do timing in real time. Then when I got the timing done I could unchoose those features and the choose something else like fuel. It would make it allot easier to street tune. As you go along using different fields you save those. I realize you cannot have all the area of the ecu real time. So if you could choose what you wanted to use as real time would be excellent.

The RamTune rom code already support this possibility, however that is the easy part. The hard part is that it would be much more difficult to develop the user interface in RomRaider for dynamic map selection v. static map seleciton. Since we don't have a whole lot of java developers that can devote a lot of their free time to working on RomRaider development, you kind of have to shoot for a goal that would be feasible given the current state of the project. That would be static map selection with on-the-fly rom/ram switching. This would still allow you to change the map assortment, but it would require you to flash the change.

I understand. Maybe something like this later. Can't wait for the new version. I wish I knew all this programing stuff so I can help. Keep up the good work!

I don't think you will see RamTune any time soon. Development has slowed down quite a bit as we don't have as many java developers working on the RomRaider project as we did before or they aren't able to devote as much of their free time to the project since everyone has lives (and real jobs) outside of RomRaider and that can get hectic at times. So, really depends if there are new java developers willing to devote time or existing developers find they have more free time in the future as to whether or not RamTune will get off the ground. Same with Launch control and per gear wg comp which were all planned to be integrated with RamTune. While the rom code is pretty much done, the hard part -> the UI for RomRaider, is not.

What sorts of user-interface operations would be needed to support launch control?

I assume there's a bit that would need to be toggled, and an RPM value that would need to be configured... anything else?

Any basic feature, like LC or per gear wg comp, would need the following added to RomRaider:
1. A method to identify that a rom file is equipped with features and display/hide relevant tables as needed.
2. The ability to patch an exisiting rom for features that would take into account the original factory values for all previous versions. This is necessary in case a user wants to return to stock or skips a version when updating. Versions meaning as the features rom code is improved upon. Releasing roms that are already patched for download is not feasible given the number of models, years, and markets.

Have you considered decoupling this from RomRaider while it gets off the ground? For example, create a command-line ROM patching utility that just applies the ram-tuning changes to a stock ROM, based on the XML that was discussed in the other thread. Then create a standalone utility that reads and writes only a few specific addresses, for example to support launch control.

Then integrate the core logic with RomRaider after the utilities have demonstrated that all of the ideas are sound. Or, if there are any surprises, this stuff can rewritten from scratch, leaving no trace on the RomRaider code base.

Such utilities could be developed independently of RomRaider itself, by contributors who don't have the time/energy to get familiar with the RomRaider code base.

The ROM patching should probably be done in Java to make it easy to bake it into RomRaider. But the SSM utility won't have any complex logic in it, it just needs to read and write a few addresses to prove that the RAM-tuning plans are mature enough to justify the work required to give it a proper UI in RomRaider.

I'm not volunteering for the ROM patching utility, but I can help out with a dialog box that does what's necessary for launch control.

I've been thinking about making launch control a standalone feature that would not have to be real-time tunable. Something like this:
1. To deactivate LC, rev motor within 500 rpm of LC threshold and hit defogger switch (you also would have to be under the veh. speed threshold).
2. When deactivated, you can set a new LC threshold. Rev motor (tranny in nuetral, veh. speed=0) to new desired LC rpm and hit defogger switch. LC is now active and set at new rpm. Likely there would be some minimum (2500 rpm), to avoid accidently setting a new threshold.
3. Post-reset, LC defaults to deactive or could default to active with a constant defining the default LC rpm.

32-bit ecu could use some of cruise control buttons to accomplish this. The only problem is trying to figure out two separate input sequences for LC and Ramtune on-the-fly map switching for the 16-bit ECU.

I have been thinking about writing something in visual basic that will handle the testing for patching and RamTune. For RamTune, it could be setup to read any rom based on the current ecu defs and the write the RT specific tables to ram. So, to test you would open RomRaider, make you changes, save to a specific file name and use the utility to write the changes to ram from that file for your RamTune equipped ECU.

Ramtune is definitely something that has to be integrated into the UI to properly use it, but I don't see any reason the other stuff can't be done without it.

Also, why not just release patched roms? People without the skills to transfer all of their table changes to a different code base probably shouldn't be messing with tuning LC and PGWG anyway.