[406Special]

Disagree Kevin. A basic std spec RB engine of a specific
configuration ought to run using the same IP program (Mapping) for
another similar/same RB engine just in a modern EFI set up for any
same engine. The Bosch LH2.4 system used on my Volvo motor as an
example works with tolerances for variables around a basic map.
Provide a better basic (more optimised) map from say Fred's Chips and
it still "learns" how to optimise dependent on fuel octane rating,
temperature, etc, all the time it is in use. MSEFI is also an
intelligent EFI system with configuration alterations to suite a
specific engine whether highly customised or say a std RB 383 with
set config. If someone has already generated a baseline map for that
engine which suits the config, then the variables and settings (from
MSEFI and other sources) can be shared. Just like Fred's Chips for
the Bosch system, as long as the engine config is within certain
tolerances, the mapping will optimise and work. Otherwise every
install has to be customised. That's why many of the MS dealers
round the globe have pre-packaged MS solutions (IPR) of specific maps
against set engines and configs. It is in that sense I define IPR -
the map that is loaded into the MSEFI system. From all MS info read,
once the hardware is set up the time is taken creating a decent
mapping solution. I have an interesting article by the Swede who
owns Fred's Chips (they do lots of different types of engines). If
interested I can post it as a guide to what it takes to manage EFI.

Clyde