What a generic timer is for
Lots of tuning decisions depend on time, not just on RPM or load. How long since the car launched? How long has the fan been running? Has this switch been held for two seconds? A generic timer answers questions like that. It counts time once a condition you choose becomes true, and the result becomes a channel you can use elsewhere in ESP.
The classic use is drag racing, where boost, timing or torque targets change with time since launch. It's just as handy for adding a delay to a custom output, so something only switches on after a condition has been true for a while.
Setting one up
On the Wiring tab, give the timer a Custom Name. Pick something descriptive, like "Time Since Launch", because that's the name you'll search for when you go to use it in a table or another function.
On the Settings tab you build three conditions. Each one follows the same pattern: pick an ECU channel, pick a comparison, and enter a value.
| Condition | What it does | Our advice |
|---|---|---|
| Start | Starts the timer counting when the chosen channel meets the comparison | Use a clean, definite event, like a launch switch releasing or vehicle speed rising above zero |
| Pause | Optional (switch it on with Enabled). Freezes the count while its condition is true | Useful if you want the timer to ignore a period, such as time spent on a gear change |
| Reset | Zeros the timer and re-arms it, so it can start again the next time the start condition is met | Pick something that happens between runs, like the car stopping or the launch switch being armed again |
The Maths dropdown offers six comparisons: Equal To and Not Equal To, Greater Than and Greater Than Or Equal To, and Less Than and Less Than Or Equal To. Value is the number the channel is compared against.
A worked example
Say you want a timer that counts from the moment the car leaves the line:
- Start: vehicle speed Greater Than 0.
- Pause: left disabled.
- Reset: vehicle speed Equal To 0, so it zeros once you've stopped at the end of the run and is ready for the next pass.
Now you can use that channel as an axis on a boost or ignition table and shape the power delivery through the run. Log the timer alongside the channels it's based on for the first few passes, to confirm it starts and resets exactly when you expect.
If the reset condition is also true during the run, the timer will keep zeroing and never count properly. Keep start and reset conditions clearly apart.
Generic timers pair naturally with a generic channel when you need to combine several conditions into one trigger. For boost by time, see boost control. On a Nexus ECU, the equivalent feature is the generic timer in NSP.
