Description
This is an informative article regarding critical processes that have higher priority on execution over others.
Example from a terminal log of an SMS command being ignored while a critical process is running (in this case Tacho process):
[sms.proc]->cmd IGNOR, TACHO proc run
[sms.proc]->now is going critical proc
[2022.03.04 09:56:38|4]-[sms.proc]->Dev busy critical proc
Example of an SMS response that you will be receiving after you send an SMS command to the device while a critical process is running:
The device is busy with critical process. Please try again later.
Critical Process:
Firmware Update (~20 min)*
Configuration Update (~5 min)*
Sleep state (see below).
Profile Switching (either by IO or Operator) (~1 min)*
Boot process (Modem reset, GNSS reset, device reset) (~5 min)*
Tacho communication (between FMdevice and VU) (~20 min)*
Tacho read
SmartCard read
* These times are only an average estimate
Examples of processes that will not be executed while a Critical Process is running:
Record generation
Can affect driver assignation in TT2 or Third-party server, as the new record with the iButton ID will not be generated
Can cause straight lines to be drawn on the map, as new records will not be generated while a critical process is running
SMS command (in custom Sleep mode, if Modem is set to Disabled, no SMS will be received or answered, if it is set to Sleep, it will answer SMS but not send data).
Driver Registration
Most likely the driver registration works on the device, but it will not generate a high priority event and generate a new record
DOUT actuation
As SMS is not executed, you will not be able to actuate DOUTs from SMS command.