Network diagnostic mode is not supported:
- on 2425 device with any firmware version;
- on other devices with firmware version older than 22.06.2021.
¶ Enabling Diagnostics
To enable the diagnostic mode, you need to make sure that the device model supports this function and has firmware version from 22.06.2021 or later.
After that, you need to follow a few steps:
- Enable generation of events for network diagnostics by sending SMS/GPRS command:
*!EDITS SYSTEM:DEBUG(1),PROTOCOL:FLEX(30,&125[1]206[1])
After configuration, the device will control the modem operation with the network and, in case of abnormal situations, generate an event with the code 41044.
On Wialon, the event code parameter has the
event_codetag.
Information about the nature of the problem is written to the FLEX protocol parameter #206 in the first byte.
On Wialon server, the parameter for diagnostic information can be seen 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 | Meaning |
|---|---|
| 0 | No error. |
| 1 | Initialization failed. Probably there is no SIM card |
| 2 | IMEI not received (AT+GSN) |
| 3 | No SIM card (AT+CPIN?) |
| 4 | Request for a unique SIM card number (AT + CCID) did not work |
| 5 | End of initialization failed. Possible problems with the SIM card |
| 6 | Registration not received (AT+CREG?, ALL_BAND) |
| 7 | Signal level request failed (AT+CSQ) |
| 8 | Operators list request failed (AT+COPS=?) |
| 9 | No available operators in roaming (by code) |
| 10 | Failed to switch to an operator in roaming (AT+COPS=1,2,x, by code) |
| 11 | Roaming registration not received (AT+CREG?, by code) |
| 12 | Registration in roaming performed on an additional card, the required one is not available (by code) |
| 13 | Status "need_init" received during initialization |
| 14 | Error Initializing SIM Storage (AT+CPMS) |
| 15 | SIM card removed during operation (AT+CPIN?) |
| 16 | Lost registration (AT+CREG?) |
| 17 | Lost signal (AT+CSQ) |
| 18 | Restart in roaming if we do not work on the optimal operator (by code) |
| 19 | Reboot according to SIM priority algorithms |
| 20 | Timeout for waiting for SMS expired for a card that cannot be used in roaming |
| 26 | Error when disconnecting from GPRS (AT+CGATT=0) |
| 27 | Error when disabling multi-server mode (AT+CIPMUX=0) |
| 28 | Error when enabling "multi-server" mode (AT+CIPMUX=1) |
| 29 | Error connecting to GPRS (AT+CGATT=1) |
| 30 | Error setting access point parameters (AT+CSTT) |
| 31 | IP request error (AT+CIICR) |
| 32 | Error connecting to the 1st server with lost registration (AT+CIPSTART) |
| 33 | Error connecting to the 1st server with closing the session (AT+CIPSHUT) |
| 34 | Error connecting to the 1st server (AT+CIPSTART) |
| 35 | Error during handshake on the 1st server |
| 36 | Error connecting to the 2nd server with lost registration (AT+CIPSTART) |
| 37 | Error connecting to the 2nd server with closing the session (AT+CIPSHUT) |
| 38 | Error connecting to the 2nd server (AT+CIPSTART) |
| 39 | Error during handshake on the 2nd server |
| 40 | Error connecting to the 3rd server with lost registration (AT+CIPSTART) |
| 41 | Error connecting to the 3rd server with closing the session (AT+CIPSHUT) |
| 42 | Error connecting to the 3rd server (AT+CIPSTART) |
| 43 | Error during handshake on the 3rd server |
| 44 | Error connecting to the service server with lost registration (AT+CIPSTART) |
| 45 | Error connecting to the service server with closing the session (AT+CIPSHUT) |
| 46 | Error connecting to the service server (AT+CIPSTART) |
| 47 | Error during handshake on the service server |
| 48 | Registration not received (AT+CREG?, BAND_EGSM) |
| 49 | Registration not received (AT+CREG?, BAND_DCS) |
| 50 | Not received "SEND OK" from the 1st server |
| 51 | Not received "SEND OK" from the 2nd server |
| 52 | Not received "SEND OK" from the 3rd server |
| 53 | Not received "SEND OK" from the service server |
| 54 | Closed socket with the 1st server |
| 55 | Closed socket with the 2nd server |
| 56 | Closed socket with the 3rd server |
| 57 | Closed socket with the service server |
| 58 | Unsuccessful attempt to send the archive to the 1st server |
| 59 | Unsuccessful attempt to send the archive to the 2nd server |
| 60 | Unsuccessful attempt to send the archive to the 3rd server |