RomRaider

I was thinking about creating a standalone utility that would allow users to select from a variety of different unit conversions and then it would generate the RomRaider ECU defs to those specifications. For example, for fueling values, you may want them displayed in lambda instead of AFR or for compensation tables, you may want them displayed as a multiplier instead of a percentage. The following is what I've thought of, so far, as options. Wanted to know if there is anything else that should be considered (note: I'm not looking to add every possible conversion that could be thought of, but those that would typically be desired by tuners):

1. Manifold Pressure
Psi relative sea level (default for standard) or Bar absolute (default for metric)
Psi absolute or Bar relative sea level
Psi relative with user defined atmopheric pressure (user could enter their avg. local atmos. pressure and defs would reflect this)
Bar relative with user defined atmospheric pressure
mmHg absolute

2. Fueling
Estimated AFR (default)
Lambda
Equivalence Ratio

3. Compensation tables
Percentage (default)
Multiplier

4. Injector Flow Scaling
estimated cc/min (default)
microseconds/g (the "raw" ecu value)
ms/g

5. Tip-in Enrichment
ms (default - this is changing for 0.8.1b ecu defs)
microseconds ("raw" ecu value)

6. Temp
F or C (the utility will allow for mixing of imperial and metric units. For example, you could have your temps displayed in C and your boost in psi).

7. IAM (16-bit ECU only)
raw ecu value (default)
multiplier

8. Vehicle Speed
mph or kmh

Sounds like a good idea, however wouldn't it be easier to store these conversions in a file that could be read by RomRaider and then simply add a tag to each table that allows for a dropdown that does conversion on the fly (refresh table view)? Similar to what the logger does now.

That would be nice, but it would be a decent amount of work and with the lack of java developers, probably not realistic any time soon. What I'm talking about is a standalone utility (along the lines of Learning View - .net app) that will generate the custom ECU defs until better functionality is possibly added to RomRaider down the road (if ever). This utility is relatively easy to develop in contrast to integrating multiple scalings into RomRaider (which I can't do because I don't s*** about Java).

Then I would say go for it since it will benefit people who want custom definition views for their conversion preferences. At some point in the future when someone wants to tackle the integrated version of on-the-fly conversions all of the information will be available.

I'm definitely doing it. The feedback I'm looking for is whether there are additional conversions that tuners would find useful than what is listed. I need to know now because I'll make some changes to the upcoming ECU/logger release to prepare for the conversion utility. For example, if If I'm going to add the option of "equivalence ratio" for fueling to the utility, I'd like the logger defs to already have this option as well.

Understood. The only one I would use in day-to-day use would be the Fueling table conversion to lambda or enrichment percentage.

I don't know whether the RomRaider-supported XML can do this, but it would be useful for many if Tip-in enrichment could be displayed as a percentage. You'd take the raw Tip-in value and divide it by the raw injector scale value, yielding Tip-in enrichment percentage.

Also some US-trained engineers prefer to work with F/A ratio instead of A/F ratio. And, technically, lambda is formally called the air/fuel equivalence ratio. It's inverse, the fuel/air equivalence ratio, is usually represented by the lower case Greek letter phi.

PS. I am not trying to suggest that we introduce lowercase Greek letters into the definitions, like mu for micro, lambda, phi, etc.. RomRaider already has a big localization problem as it is.

Wouldn't be possible with RomRaider currently.


I should specify it is the fuel/air equivalence ratio that was my intention in the list.

Are you considering supporting EcuFlash definitions with your PreferredUnits tool?

Perhaps, although Colby was talking about adding multiple units capability to Ecuflash so I might wait to see if that is going to happen.

Merch,

As far as fuelling is concerned wouldn't it be possible to display the fuel map in Injector ms. I think this is what the ECU inside must be using. Based on the set scalar and latencies a calculation is done as a certain pulsewith is generated at a certain cell in the map. Some of the MUCH MORE advanced ECUs do all the fuelling in RAW injector pulsewitdh in milliseconds.

Let me know what the options are.

Cheers,

Jasper.

I'm sure some other ECUs do fuel maps as raw injector puslewidths, but it's NOT because they are MUCH MORE advanced. Such values are meaningless to an engineer because they change with injector size. Think of all the work you'd have to do if you installed larger injectors. The Subaru ECUs essentially store fuel/air equivalence ratio as the raw fuel table values. Thus, a raw value of 0.25 means turn on the injector 25% longer than its opening would be for stoichiometric fueling.