A.TheMoTeC ADLhasvery sophisticated alarm functions that allow the Team Engineertocreate warnings for the driver and pit crew based on a userdefined set of conditions. Traditionally, logging systems use a simplethreshold value to determine when a warning is given.

While the MoTeC For Example:Insteadof the Oil Pressure alarm being triggered when the pressure dropsbelowasingle value, the oil pressure value that will trigger an alarm can bedependant on the engine RPM. I.e.: there is a varying alarm thresholdthat changes with RPM. This can be done using a 2D table to create an‘oil pressure alarmthreshold’ channel –a‘General Purpose’ pressurechannel has been used for this purpose in the example,below.

Thisnew channel is then used in the alarm condition below. It is evenpossible to use a 3D table instead of the 2D table to introduceanotherchannel (such as Engine Oil Temp) to modify the oil pressure alarmvalue. Beyond this, alarms can be generated based on:combinations oflogical AND/OR arguments, a range of comparison methods(greater than,less than equal to, etc.) or time dependency (i.e.: a channel mustholda value for a certain period of time before triggering analarm).

Thedisplaypossibilities are equally flexible using a combination of a warninglight and message displays.

Someteams have demonstrated the creative use of this in the past. One usedthe message ‘$$$$$$$$$’ to indicate an engine overrev whilst anotherused ‘SLOW!!!’ for some inappropriatedriver behaviour.