Description:
This article contains basic instructions on how to interpret information inside our device log.
Notes:
- All timestamps are displayed as UTC standard and in GMT time zone.
- Copy the command exactly as it is stated inside the quotation marks.
Recommended tools:
Application | Download link |
Notepad++ |
Check the device IMEI
Search for "IMEI"
Note: It will be shown on two occasions, one time during modem bootup and periodically during modem info.
[2022.03.01 11:21:20|2]-[ATE]->IMEI: 863940058306930
IMEI: 863940058306930
Check Device Information and Firmware/CFG versions
Search for "DEVICE INFO"
From time to time, the device outputs its current GSM modem status, it contains several helpful information.
Note: If this information is not available in the log, as for the client to record a new terminal log for 10 min.
[info.dev]->DEVICE INFO
Device reset source: 14
Device UpTime: 70470 s
VERSIONS:
Bootloader version: 0x50 0x2d
Firmware version: 00.03.76.05
Branch version: SCI33fa7e03
Hardware: FMP415
CFG INFO:
CFG ver: 00.03.32.05
FWver: 00.03.76.05
BRver: SCI33fa7e03
CFG source: CFG
FirstTS: 0
LastTS: 1560773000
Target device: Pr04
Custom text:
CRC: 0
HWrev: FMP415
Check if the device is connected to Power Supply
Search for "ID:29"
Note: This value will only be shown if the IO 29 - Power Supply Voltage was enabled in the device configuration and if the device has GPS fix (default configuration).
In this case, the device was connected to a power supply that was outputting 29VDC.
ID:29 29078
Note: Sometimes ID:29 might not display voltage if device has low battery level and immediately turns off, in such cases try to search for word "Voltage" if you find mention in the logs "Critical voltage conditions!" it might display last received voltage before going off.
In example below device had low voltage from power supply - 2,9V
[2023.06.08 19:51:51|3]-[VOLT.MEASURE]->Critical voltage conditions! Bat:3500, Vin:2914, Usb:0
Battery Voltage(Bat): 3500mV = 3,5V
External Voltage(Vin): 2914mV = 2,9V
USB Voltage(USB): 0mV = 0V
Check current GNSS modem state
Search for "[gps]->State:"
[2022.06.07 10:48:58|1]-[gps]->State: 1
[2022.06.07 10:49:02|1]-[gps]->State: 2
[2022.06.07 11:12:26|1]-[gps]->State: 3
[2000.01.01 00:07:55|5]-[gps]->State: 6
Note: When GNSS modem is disabled, date will be 2000.01.01
Existing states:
Current GNSS state. The values can be the following:• 1 – off• 2 – on with no fix• 3 – on with fix• 4 – not responding• 5 – sleep• 6 – disabled• 7 – waking up from Sleep
Check if SIMCARD was properly inserted
Search for "CPIN"
If the status is different than "READY", then the device cannot read the SIMCARD
<-AT+CPIN?c->+CPIN: READY
If status is "SIM PIN" it means that the device cannot find a stored PIN number to enable the SIM card. It must be inputted manually using the Advanced Configurator, more information on: SIMCARD PIN and PUK codes
<-AT+CPIN?c->+CPIN: SIM PIN
If status is "CME ERROR: 10" it means that the SIM card is not physically detected; it is either not inserted, damaged, not touching device pins properly, or the device pins are damaged and cannot connect SIM card. Trying an alternative SIM card is advised.
<-AT+CPIN?
i->+CME ERROR: 10
Check SIMCARD carrier internal IP address
Search for "QIACT:"
c->+QIACT: 1,1,1,"10.100.115.201"
IP Address: 10.100.115.201
Check the SIMCARD IMSI/ICCID inserted in the device
Search for "IMSI"
Search for "ICCID"
Note: Both information is only available when the GSM modem is booting up.
IMSI
c->204047112196334[AT]->IMSI Read: 204047112196334
ICCID
<-AT+QCCIDc->89551805400560034410[2021.04.13 12:14:20|1]-[AT]->ICCID Read: 89551805400560034410
If the device configuration has "Lock FM device to SIM card" enabled and it detects that the ICCID is not the same as the one it is locked to, the following message will appear (and device will refuse to use the SIM card):
[SIM lock]->Device locked to different SIM card!
Check APN configuration
Note: this is as AT command that our Firmware issues to the GSM modem, it will only be shown during power up or if the APN configuration is changed, either via SMS/GPRS or Device Center.
4th Gen
Search for "QIREGAPP"
<-AT+QIREGAPP="zap.vivo.com.br","vivo","vivo123"
This can be translated as:
APN: zap.vivo.com.br
User: vivo
Password: vivo123
5th Gen
Search for "QICSGP" or "MIPCALL"
<-AT+QICSGP=1,1,"zap.vivo.com.br","vivo","vivo",3
This can be translated as:
APN: zap.vivo.com.br
User: vivo
Password: vivo
Check GSM modem status
Search for "MODEM HEALTH"
From time to time, the device outputs its current GSM modem status, it contains several helpful information.
Note: If this information is not available in the log, as for the client to record a new terminal log for 10 min.
[2022.02.26 10:18:23|5]-[MODEM HEATH]
Mdm st: ready (3)
GSM st: registered, roaming (5)
GSM sign: 25
GSM op format: 2
GSM op num: 64005
GPRS: 1
Link st: 1
Conn st: 10
LAC: 110
Cell ID: 11432
Access technology: GSM
PIN st: ready (0)
Phone functionality: 1
Phone st: ready (0)
Mdm temp: 35
Jamming st: 0
Check GSM state
Search for "GSM st"
[2022.02.26 09:23:27|5]-[AT]->GSM st: 5 (Regd,Roaming), LAC: 110, Cell: 11433[2022.02.26 10:23:54|5]-[AT]->GSM st: 2 (NotRegd,Search), LAC: 0, Cell: 0[2000.01.01 00:02:49|5]-[AT]->GSM st: 1 (Regd,homeNet), LAC: 5101, Cell: 18082
Existing states:
0 - not registered, ME is not searching for network (for troubleshooting, see HERE)1 - Registered, Home Network2 - Not Registered, Searching3 - 4 - 5 - Registered, Roaming255 - Undefined (usually because modem is off or out of order)
Check GSM signal strength
Search for "GSM sign"
Search for "+CSQ:"
GSM signal strength ranges from 0 to 31.
02 to 09 - Marginal
10 to 14 - OK
15 to 19 - Good
20 to 31 - Excellent
Proper signal reading:
GSM sign: 12
c->+CSQ: 12,99
Not usual signal reading:
GSM sign: 99c->+CSQ: 99,99GSM sign: 255
Check if the device is connected to a 2G, 3G, or 4G/LTE network
Search for "Access technology"
If it is connected to 2G:
Access technology: GSM
If it is connected to 3G:
Access technology: 3G
If it is connected to 4G/LTE:
Access technology: LTE
Check GPRS states
Search for "gprs"
The device will try to open a GPRS connection using its APN settings 5 times, if it fails at all times the GSM modem will be powered off and reinitialized.
[2022.02.08 09:14:38|2]-[gprs]->Attaching to GPRS[2022.02.08 09:14:40|2]-[gprs]->GPRS attaching failed. Retries: 1[2022.02.08 09:14:45|2]-[gprs]->Attaching to GPRS[2022.02.08 09:14:47|2]-[gprs]->GPRS attaching failed. Retries: 2[2022.02.08 09:14:52|2]-[gprs]->Attaching to GPRS[2022.02.08 09:14:54|2]-[gprs]->GPRS attaching failed. Retries: 3[2022.02.08 09:14:59|2]-[gprs]->Attaching to GPRS[2022.02.08 09:15:01|2]-[gprs]->GPRS attaching failed. Retries: 4[2022.02.08 09:15:06|2]-[gprs]->Attaching to GPRS[2022.02.08 09:15:08|2]-[gprs]->FAILED to Open GPRS[2022.02.08 09:15:08|2]-[gsm]->GPRS task fail: 4[2022.02.08 09:15:09|2]-Modem power off
If the failed GPRS attachment attempts are followed by CME ERROR: 133, it means one of the following “Requested service option not subscribed”.
[2000.01.01 00:26:20|5]-[gprs]->Attaching to GPRS 11:51:22.744>
<-AT+CGATT=1 11:51:22.744>
c->OK 11:51:22.808>
<-AT+QICSGP=1,1,"avl.iot.attmex.mx","","",0 11:51:22.808>
c->OK 11:51:22.808>
<-AT+QIACT=1 11:51:22.808>
c->+CME ERROR: 133 11:51:24.248>
[2000.01.01 00:26:21|5]-[AT]->errorHandler: 133 11:51:24.248>
[2000.01.01 00:26:21|5]-[gprs]->FAILED to Open GPRS
Likely culprits: incorrect APN name, bad data plan on the SIM, not enough credit on the SIM.
Check the Server Configuration
Search for "QISTATE:"
4th Gen
c->+QISTATE: 0, "TCP", "193.193.165.165", 20956,"CONNECTED"
c->+QISTATE: 1, "TCP", "92.62.134.34",9015,"INITIAL"
c->+QISTATE: 2,"","",,"INITIAL"
c->+QISTATE: 3,"","",,"INITIAL"
c->+QISTATE: 4,"","",,"INITIAL"
c->+QISTATE: 5,"","",,"INITIAL"
This can be translated as:
Protocol: TCP
IP1: 193.193.165.165
Port1: 20956
IP2: 92.62.134.34
Port2: 9015
5th Gen
Search for "QISTATE:"
c->+QISTATE: 0,"TCP","107.155.111.23",5040,5771,2,1,0,0,"uart1"
c->+QISTATE: 1,"TCP","92.62.134.34",9015,16007,2,1,1,0,"uart1"
This can be translated as:
Protocol: TCP
IP1: 107.155.111.23
Port1: 5040
IP2: 92.62.134.34
Port2: 9015
or "MIPOPEN":
<-AT+MIPOPEN=1,,"92.62.134.34",9015,0
This can be translated as:
Protocol: TCP
IP1: 92.62.134.34
Port1: 9015
IP2:
Port2:
Check if the device is not able to open a SOCKET to server
Search for "gprs-socket"
Search for "Open link fail"
[2022.02.08 09:13:59|2]-[gsm]->Open link fail: 3/4
[2022.02.08 09:13:59|2]-[gprs-socket]->FAILED to Open link [0]!
Check if Records are being generated and saved to internal flash memory
Search for "[NewRec]"
Important note: With the default configuration, NO record will be generated until the device acquires GPS fix, if it is your case, the device will continue to trigger a new record to be generated, but the firmware will suppress the generation and a message will be outputted in the log with the respective Input Trigger, like this:
[EVT]->rec not gen: 415
UTC Stamp is the current date/time that the record was generated, you can copy the value and paste it in this website to get in a Human-Readable format.
Epoch converter - https://www.epochconverter.com/
New RecAddr represents the address in the device's internal flash memory where this record is saved, every record has its own address and is unique, until it gets deleted after the data is sent to the server when using UDP protocol, and deleted after the server replies with an ACK when using TCP protocol.
[NewRec]
[UTC Stamp]->: 1641981270
[UTC Stamp]-> ext: 0
Record ext: 0x22
Priority: 0
Longitude: 120874800
Latitude: 576755266
Altitude: 874
Angle: 8640
Satellites: 17
Speed: 0
HDOP: 60
Record on evt: 159
ID:92 0
ID:114 0
ID:210 0
[2022.01.12 09:54:30|2]-[RECORD][0]->New RecAddr:1658496 len:45
Check communication between DEVICE <-> SERVER
Search for "rx id:" when you want to see the command sent by the server to the device
Search for "tx id:" when you want to see the command sent by the device to the server
In the example below the device sent a command 68 (Extended record) to the server and after the server receive the record and check its CRC16, the server sends an Acknowledgement, with command 100 (Extended record) to the device saying that the record was well-received.
[2022.01.12 09:54:46|2]-[rnp-client]->tx id: 068, size: 0296
[2022.01.12 09:54:46|2]-[rnp-client]->rx id: 100, size: 0001
In case the device is configured with TCP protocol and it does not receive an ACK from the server, no new record will be sent until the device properly receives the ACK from the server. The device will wait for some time and try to send again the same record. If again the server does not respond, the device will wait for a longer time and try to send again the same record, this wait time will increase after each unsuccessful try.
In case the device receives ACK, the device proceeds to delete the record from its internal flash memory.
[2022.01.12 09:54:46|2]-[REC]->RecSize cleared at Addr: 1658240
This does not happen when the device is configured with UDP protocol, the device send the record and after that, it will automatically delete the record from its internal flash memory.
Check if Profile Switch happened
Search for "profile-switch"
Search for "PRF"
Search for "PRF_SW"
[profile-switch]->current operator: 21601
[profile-switch]->list: 1, operator: 28401
[profile-switch]->list: 1, operator: 28403
[profile-switch]->list: 1, operator: 28405
[profile-switch]->list: 1, operator: 28406
[profile-switch]->list: 1, operator: 21601
[profile-switch]->matching operator found (list 1, operator 21601)
[2022.02.08 09:12:35|2]-[PRF_SW]->Swap by op. switch_to=1, evt=0
[2022.02.08 09:12:35|2]-[profile-switch]->start (1)
[2022.02.08 09:12:36|2]-[PRF]->prof1 crc_main:1 crc_bckp:1
Prof1_sz=2925
[2022.02.08 09:12:36|2]-[PRF]->prof1 loaded
[2022.02.08 09:12:36|2]-[profile-switch]->end (1)
Check all OPERATOR CODE was triggered
Search for "GSM op num"
Search for "COPS"
Check if JAMMING was triggered
Search for "Jamming st"
Search for "QJDR"
When jamming is not detected:
i->+QJDR: NOJAMMINGJamming st: 0
When Jamming is detected:
i->+QJDR: JAMMEDJamming st: 1
TACHO - Check TACHO status
Search for "TDSM:"
Search for "Tacho sts:"
[TDSM]->Tacho sts 0
[TDSM]->Tacho sts 1
[TDSM]->Tacho sts 2
TACHO - Check if the server is requesting the correct information from the Tachograph
Search for "ATR->"
[TACHO.API] ATR->wtr=0x39, st=1627560734, end=1635509534
What To Read => wtr=0x39
0x39 in HEX represents 00111001 in BINARY, reading from right to left, the:
- 1st bit as 1 is asking to retrieve the Tachograph data
- 2nd bit as 0 is NOT asking to retrieve the Driver Card data in Slot 1
- 3rd bit as 0 is NOT asking to retrieve the Driver Card data in Slot 1
- 4th bit as 1 is asking to retrieve Events and faults from the tachograph.
- 5th bit as 1 is asking to retrieve Detailed speed from the tachograph.
- 6th bit as 1 is asking to retrieve Technical data from the tachograph. - 7th bit - unknwon- 8th bit - unknwon
Start Time (FROM) => st=1627560734
1627560734 = 2021-07-29T12:12:14
End Time (TO) => end=1635509534
1635509534 = 2021-10-29T12:12:14
To convert from HEX to BIN use: https://www.asciitohex.com/
To convert timestamp use: https://www.epochconverter.com/
TACHO - Check Negative Response Error Code
Search for "rxerr_RespDiagSession->" or "err_resp_obj->"
When something fails in the communication between the device and the tachograph, an error code is generated.
Example (error code is bolded):
[TACHO.API] rxerr_RespDiagSession-> 0x7F 0x10 0x22 (st=0 l=003)
[TACHO.API] err_resp_obj-> 0x7F 0x22 0x22 (st=0 l=003)
Information on the meaning of each code can be found in Confluence:
---------------------------------------------------------------------------
Title
Search for "argument"