[warnings]

The warnings section provides a means to add warnings that will be generated when the limits provided are breached. Each warning is defined as follows:

<attribute name>=<warningid>,<low limit>,<high limit>,<use low limit>,<use high limit>,<engine must be running>

Where:

<attribute name> is the name of the attribute whose value should be used to check against the specified limits.
<low limit> is the limit below which the value must fall to generate a warning
<high limit> is the limit above which the value must rise to generate a warning
<use low limit> is a value 1 or 0 to indicate if the low limit should be used (1=yes)
<use high limit> is a value 1 or 0 to indicate if the high limit should be used (1=yes)
<engine must be running> is a value 1 or 0 to indicate if a check for rpm>0 should be included in the limit check (1=yes)

Example:

[warnings]
oilpressure=1190,35,70,1,1,1

This sets a limit on the oil pressure attribute. If the oil pressure falls below 35 or rises above 70 and the engine is running (rpm>0) then warning id 1190 will be generated (this is the system low oil pressure warning). If the current page contains a composite tagged as a warning with warning id 1190 then the composite will appear on the page.

You can in fact use any Warning ID you wish if you want to add new warnings. You are not limited to the system warnings.

On a canbus rebroadcast implementation, SDC devices receiving data from main source over the canbus may react slightly differently in terms of when warnings are generated (and may even miss situations where the limit is briefly breached) since the data over the bus is usually throttled. You can change the throttling for an important data item if necessary, but you must be careful not to flood the bus.