1) what tools do we need (for example det cans, knock sensors, EGT probes, accelerometers etc) to be able to setup the ignition maps well?
Basic tools for mapping are:
Good Laptop with long battery life.
16bit Emulator with 35ns max data speed and at least 8mb internal memory. (To run 2x 4mb roms at once)
Battery backup system for emulator that is capable of storing the run map and feeding the ecu with this rom for 1hour solid to get you home should the laptop or emulator fail out in service.
(Remember, your ecu has no chip in it
)
Wideband fuel monitor that ideally shows both Fuel AND Oxygen.
Its nice also to have both AFR and Lambda displayed.
Knock cans of some form, to enable you to hear engine noise from within the cockpit.
Accurate boost gauge for forced induction engines.
EGT monitoring is very usefull on Turbocharged cars.
G-Meter is usefull but not strictly a necessity.
A mobile phone to call RAC
2) and what are we looking to do in all areas of the maps?
Basically, you need to drive the car and trace log the most commonly used areas. Once youve ascertained what areas are most commonly accesed during normal running, you want to be optimising these for fuelling. The lambda input needs disabling one way or another to do this. Id rather not go into too much detail as to what mixtures we use for the various modes of engine operation as im risking giving away slightly too much there, remember, this is my living folks, but im happy to chat about general stuff.
As for spark, we need to be advancing to either peak torque, knock, or oxygen input, whatever comes first and then back to adetermined safe level back away from this peak. Again, i have my own feelings on whats safe to retard back to and its not for public consumption. Sorry
Next...
