SARA-R42 - Application note
UBX-20050829 - R02
Monitoring module status
Page 34 of 58
C1-Public
9
Monitoring module status
9.1
Retrieve and interpret diagnostic information
It is recommended to track the module status in the host application. Such diagnostic information
allows detection of specific scenarios and implementation of proper handling and countermeasures
in the host application.
The module status can be returned by AT command responses and unsolicited result codes (URCs).
Depending on the host application architecture, URCs, periodic polling, or both, can be used. URCs
provide the most updated information and, in some cases, diagnostic information which is not
available via polling. For AT commands that enable URCs, they might also return the same
information when polled, as indicated below.
Some commands store the setting of the URC reporting in NVM, so they are referred to as persistent
settings.
Some AT commands provide a choice on how to handle the URCs when the AT interface is busy; for
all other AT commands, URC is issued at the return into command mode, as explained in SARA-R4
series AT command manual
, in the “URCs presentation deferring” section.
URCs and AT command responses are presented with their generic syntax because parameters
names are quite explanatory; for precise meaning, see the SARA-R4 series AT command manual
