Set command

Syntax:

%MDMEV=<n>

The set command parameter and its defined values are the following:

<n>

0 – Unsubscribe modem domain event notifications

1 – Subscribe modem domain events notifications

2 – Subscribe modem domain warning and informational events

The unsolicited notification syntax descriptions are as follows:

Mobile Equipment (ME) is overheated and therefore modem is deactivated:

%MDMEV: ME OVERHEATED

Battery voltage is low and therefore modem is deactivated:

%MDMEV: ME BATTERY LOW

Modem indicates status of ongoing light search:

%MDMEV: SEARCH STATUS 1

SEARCH STATUS 1 indicates light search performed. This event gives the application a chance to stop the modem from using more power on searching networks from possibly weaker radio condition. Before sending this event, the modem searches the cells based on previous cell history, measures the radio conditions, and makes assumptions on where networks might be deployed. This event means that the modem has not found a network that it could select based on the 3GPP network selection rules from those locations. It does not mean that there are no networks to be found in the area. The modem continues more thorough searches automatically after sending this status. The modem can be deactivated, for example, with +CFUN=4, to stop it from using more power on the search.

Modem indicates completed status of search:

%MDMEV: SEARCH STATUS 2

SEARCH STATUS 2 indicates search performed. The modem has found a network that it can select according to the 3GPP network selection rules or all frequencies have been scanned and a suitable cell has not been found. In the latter case, the modem enters normal limited service state functionality and performs scans for service periodically.

Modem has detected a reset loop:

%MDMEV: RESET LOOP

RESET LOOP indicates that the modem restricts Attach attempts for the next 30 minutes. The timer does not run when the modem has no power or while it stays in the reset loop. The modem counts all the resets where the modem is not gracefully deinitialized with +CFUN=0.

If there are more than five resets, reset loop restriction is activated.

If there are more than seven resets, reset loop restriction is activated.

For more information on reset loop, see Modem Reset Loop Restriction.

Modem has detected that International Mobile (Station) Equipment Identity (IMEI) has not been written with the Production Test Image (PTI) firmware:

%MDMEV: NO IMEI

Mandatory AFC calibration (%XRFTEST) or TX self-calibration (%TXSELFCAL) or both have not been executed with the PTI firmware. :

%MDMEV: RF CALIBRATION NOT DONE

Modem indicates the selected CE level for RACH procedure:

%MDMEV: PRACH CE-LEVEL <ce-level>

The notification parameter and its defined values are the following:

<ce-level>

0 – CE Level 0. No repetitions or small number of repetitions.

1 – CE Level 1. Medium number of repetitions.

2 – CE Level 2. Large number of repetitions. Narrowband Internet of Things (NB-IoT) only.

3 – CE Level 3. Very large number of repetitions (not supported).

Modem detects a conflicting band lock and operator restrictions in at least one system which indicates that there are no usable bands in that system:

%MDMEV: INVALID BAND CONFIGURATION <status_emtc> <status_nbiot>

The notification parameters and their defined values are the following:

<status_emtc>

0 – Usable LTE bands are available in the system.

1 – There are no usable LTE bands available in the system.

2 – System support is not configured.

<status_nbiot>

0 – Usable LTE bands are available in the system.

1 – There are no usable LTE bands available in the system.

2 – System support is not configured.

The following command example subscribes %MDMEV notifications:

AT%MDMEV=1
OK