Message 513 Is Reported When Devices Are Connected to the IoT Platform
After being powered on, devices initiate a TUP registration flow to the IoT platform. TUP is a Huawei proprietary protocol over CoAP. TUP is similar to LWM2M. HiSilicon chipsets set that the TUP registration cannot exceed 4s. If the TUP registration is not completed within 4 seconds, a 513 message is reported.
When a 513 message is reported, perform the following operations:
- When a 513 message is reported due to poor network performance, contact the NB-IoT network carrier to check the network status.
- When service data is sent by running AT+NMGS, registration is triggered. If the t/d resources (receiving and sending service data resources) are not received within 4 seconds, an error is returned, but the registration is continued based on the CoAP-layer retransmission. If subscription to the t/d resources is not received after 160 seconds, the IoT platform determines that the registration fails. The 160-second duration is sufficient for device registration. If an error message is returned after 4 seconds, only the data of the first packet is discarded. You are advised to restart the device and run AT+NMGS to trigger the registration.
You can run AT+NMSTATUS? to query registration status. If +NMSTATUS:MO_DATA_ENABLED is returned, the registration is successful.
Device Development FAQs
- Registered Devices Cannot Connect to the IoT Platform
- Message 513 Is Reported When Devices Are Connected to the IoT Platform
- DTLS Encryption Algorithms Supported by the IoT Platform
- What Does CTNB Mean
- How to Select PSM, DRX, and eDRX
- Devices Cannot Receive Commands from the IoT Platform
- IoT Platform Does Not Receive Data Reported by Devices
- Historical Data Does Not Contain Data Reported By Devices While No Error Occurs
- Duration for Devices to Receive Commands
- Devices Fail to Receive Data Reporting Responses
- Data Reporting Is Successful at One Position But Fails at Another Position
- Command Status Is Not Changed to Successful After a Device Reports the Command Execution Result
- Whether the IoT Platform Can Switch Between the Big-Endian and Little-Endian
- Commands Fail to Be Delivered When a Device in DRX Mode Does Not Report Data in One to Two Days
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore