www.unisem.co.kr | [email protected] | +82.31.724.2548
4. Trouble Shooting
- If the device does not transmit normal data, trouble shooting can be done through debugging
method and log analysis method below.
- When debugging the device, if gsmSeq = 7 stops, check that the USIM is installed because it is
the result of missing or improperly inserted USIM.
- When debugging the device, if gsmSeq = 14 stops, the network connection cannot be made.
Check with the telecommunication company to check whether the USIM is registered or not, and
try again.
4.1 Device debugging method
The debugging messages are a message for easy identification of the cause when the device is
performing erratic behavior.
The following are the meanings of the debugging messages
.
II 2017/08/18 04:56:48 BSU(0:0:1) SM(0) BAT(4350)
The line is printed every second when the
device is operating.
II 2017/08/18 04:56:49 BSU(0:0:1) SM(0) BAT(4350)
Because USB is connected, it stays on without
entering the sleep-state.
II 2017/08/18 04:56:50 BSU(0:0:1) SM(0) BAT(4350)
II 2017/08/18 04:56:51 BSU(0:0:1) SM(0) BAT(4350)
BAT (4350) means a battery value of 4.35 volts.
II 2017/08/18 04:56:52 BSU(0:0:1) SM(0) BAT(4350)
II 2017/08/18 04:56:53 BSU(0:0:1) SM(0) BAT(4350)
PN532Begin: PN532 Begin ....
Ready for NFC
SAMConfig: SAMConfig
writeCommand: [PN532] PN532 Wakeup
Power on NFC
writeCommand: [PN532] Write: readAckFrame: [PN532] Ack: readAckFrame: OK
readResponse: [PN532] Read: readResponse: length0 = 0x02, length1 = 0xFE