Diagnostic mode is NOT supported on devices 23xx, 25xx, 2425, 2430
On other devices, diagnostic mode is supported in firmware versions dated 22.06.2021 and newer
¶ Enabling Diagnostic Mode
To enable diagnostic mode, make sure that the device model supports this function and is running firmware dated 22.06.2021 or newer.
After that, you need to:
- enable diagnostic cellular network event generation;
- enable the parameter for storing (and transmitting to the server) diagnostic information.
To do this, send the following command to the terminal:
*!EDITS SYSTEM:DEBUG(1),PROTOCOL:FLEX(30,&125[1]206[1])
After configuration, the terminals monitor modem operation with the network and, in case of abnormal situations, generate an event with code 41044.
On the Wialon server, the "event code" parameter has the tag
event_code.
Information about the nature of the issue is written to FLEX protocol parameter No. 206, first byte.
On the Wialon server, the diagnostic information parameter can be found under the name
diag.
¶ Wialon Configuration
Template for Wialon with an example of sensor and validator configuration.
After importing the template into the monitoring system, go to the sensor settings and re-configure the validator, because when importing, it may not register)
- Create a validator sensor by parameter
event_code=41044.
- Create a sensor to receive the value of the first byte of the
diagparameter and set the validator created earlier for it.
In the Parameter field, enter the formula:
diag:1+
(diag:2*const2)+
(diag:3*const4)+
(diag:4*const8)+
(diag:5*const16)+
(diag:6*const32)+
(diag:7*const64)+
(diag:8*const128)
And to hide the validator, untick the checkbox next to it.
¶ Results Analysis
¶ Analysis in Wialon
To view the diagnostic results, you need to open the list of messages from the device in the Sensor values mode
The result will be like this:
¶ Analysis by SMS
You can request the last 9 diagnostic error codes for working with the network from the device via SMS.
¶ Request/Command
- Format:
*?DIAG<s><type> - Description:
<s>- parameter separator - space;
<type>- type of diagnostic information:
1 - network diagnostics. - Example:
*?DIAG 1
¶ Response
-
Format:
M:115
<code>:<time> -
Description:
M:115- message type;
<code>- error code (list of codes and their meanings is given below in the guide)
<time>- date and time of the event (UTC) in thehhmmssDDMMYYformat. -
Example:
M:115
39:082223160621
39:081945160621
39:081701160621
39:081424160621
39:081144160621
39:080906160621
39:080628160621
39:080347160621
39:080105160621
¶ Error Code Table
| Code | Value |
|---|---|
| 0 | No errors |
| 1 | Initial initialization not completed. SIM card may be missing |
| 2 | IMEI not received (AT+GSN) |
| 3 | No SIM card (AT+CPIN?) |
| 4 | SIM card unique number request failed (AT+CCID) |
| 5 | Final initialization not completed. SIM card issues are possible |
| 6 | Registration not received (AT+CREG?, ALL_BAND) |
| 7 | Signal level request failed (AT+CSQ) |
| 8 | Operator list request failed (AT+COPS=?) |
| 9 | No available roaming operators (by code) |
| 10 | Failed to switch to a roaming operator (AT+COPS=1,2,x, by code) |
| 11 | Roaming registration not received (AT+CREG?, by code) |
| 12 | Roaming registration completed on an additional SIM card, required SIM card is unavailable (by code) |
| 13 | "need_init" status received during initialization |
| 14 | Error during SIM card storage initialization (AT+CPMS) |
| 15 | SIM card removed during operation (AT+CPIN?) |
| 16 | Registration lost (AT+CREG?) |
| 17 | Signal lost (AT+CSQ) |
| 18 | Reboot in roaming if the device is not operating on the optimal operator (by code) |
| 19 | Reboot according to SIM card priority algorithms |
| 20 | SMS waiting timeout expired for a SIM card that cannot operate in roaming |
| 26 | Error while disconnecting from GPRS (AT+CGATT=0) |
| 27 | Error while disabling "multi-server" mode (AT+CIPMUX=0) |
| 28 | Error while enabling "multi-server" mode (AT+CIPMUX=1) |
| 29 | Error while connecting to GPRS (AT+CGATT=1) |
| 30 | Error while setting access point parameters (AT+CSTT) |
| 31 | Error while requesting IP (AT+CIICR) |
| 32 | Error while connecting to server 1 and registration was lost (AT+CIPSTART) |
| 33 | Error while connecting to server 1 and closing the session (AT+CIPSHUT) |
| 34 | Error while connecting to server 1 (AT+CIPSTART) |
| 35 | Handshake error on server 1 |
| 36 | Error while connecting to server 2 and registration was lost (AT+CIPSTART) |
| 37 | Error while connecting to server 2 and closing the session (AT+CIPSHUT) |
| 38 | Error while connecting to server 2 (AT+CIPSTART) |
| 39 | Handshake error on server 2 |
| 40 | Error while connecting to server 3 and registration was lost (AT+CIPSTART) |
| 41 | Error while connecting to server 3 and closing the session (AT+CIPSHUT) |
| 42 | Error while connecting to server 3 (AT+CIPSTART) |
| 43 | Handshake error on server 3 |
| 44 | Error while connecting to the service server and registration was lost (AT+CIPSTART) |
| 45 | Error while connecting to the service server and closing the session (AT+CIPSHUT) |
| 46 | Error while connecting to the service server (AT+CIPSTART) |
| 47 | Handshake error on the service server |
| 48 | Registration not received (AT+CREG?, BAND_EGSM) |
| 49 | Registration not received (AT+CREG?, BAND_DCS) |
| 50 | "SEND OK" not received from server 1 |
| 51 | "SEND OK" not received from server 2 |
| 52 | "SEND OK" not received from server 3 |
| 53 | "SEND OK" not received from the service server |
| 54 | Socket with server 1 closed |
| 55 | Socket with server 2 closed |
| 56 | Socket with server 3 closed |
| 57 | Socket with the service server closed |
| 58 | Failed attempt to send archive data to server 1 |
| 59 | Failed attempt to send archive data to server 2 |
| 60 | Failed attempt to send archive data to server 3 |
| 61 | Registration not received (AT+CREG?, GSM_ONLY) |
| 62 | Registration not received (AT+CREG?, WCDMA_ONLY) |
| 63 | Registration not received (AT+CREG?, LTE_ONLY) |
| 64 | SIM operation error (AT+SWITCHSIM) |
| 65 | PIN is set |
| 66 | PUK is set |