Software » Campo

Alarms/Alerts¶

Devices should indicate issues; e.g.:

• Battery low
• I2C problems
• Buffer overflow

Object structutre¶

Room is a bit specifik to the timeout-shutdown-thing. subindex
Setting ambient light has the same issue.

Categorie:
USB, UART, System

Type:
Critical, Warning, Info, Event

Events:
Simple integer code which can be send via logging * Buffer overflow * I2C issue

Events vs. Alerts¶

Events can be integrated into logging. They can be used anywhere in the code like ISRs. An Event has no output value.

bWarningE( EV_BUFFER_OVERFLOW | EV_UART, "Buffer overflow: %d", cnt);

Alarms are send explicitly as system errors in the main event loop. An Alarm has an concrete value.

sendAlarm( Tdt::EAlarm::OverTemperature,
                 Tdt::EUnit::centiCelsius, Tdt::SValue { ._int=temperature } );
sendAlarm( Tdt::EAlarm::UnderVoltage,
                 Tdt::EUnit::milliVolt, Tdt::SValue { ._int=voltage } );