How to Quickly Debug NB‑IoT Data Reporting and Use Huawei’s Demo Tools

To help developers quickly self‑service NB‑IoT solution integration and debugging, the following frequently encountered issues are categorized and summarized.

Data Reporting FAQ

Q: What is data reporting?

A: Data reporting is the most basic IoT operation where terminal devices send collected data over NB‑IoT to the Huawei OceanConnect platform, which can be retrieved by northbound applications via RESTful APIs or pushed by the platform.

Q: Can data reporting use transparent transmission?

A: Transparent transmission is not supported on the OceanConnect platform; data must be parsed in the codec plugin.

Q: Can I report data without real devices?

A: Yes, Huawei provides a complete demo and simulator for a zero‑code, zero‑device NB‑IoT experience. See the demo link for details.

Q: I have purchased an NB module, how can I quickly experience the data‑reporting flow?

A: Use Huawei’s demo to connect the module to OceanConnect and follow the provided link for step‑by‑step instructions.

Q: After executing AT+NMGS=N,XXXXXX the data is not visible on OceanConnect?

A: Follow the step‑by‑step troubleshooting guide on the provided Huawei forum link.

Developer Portal FAQ

Q: What is the Developer Portal?

A: The OceanConnect Developer Portal helps application and device developers quickly perform online development and debugging.

Q: How to obtain a Developer Portal account?

A: Two ways: (1) Apply to join the IoT solution partner program and receive platform resource access after approval; (2) Reserve a remote lab environment on the Huawei developer community.

Q: What is the difference between NB and non‑NB device simulators?

A: NB simulator mimics hex streams of NB‑IoT devices for data upload to the cloud‑gateway plugin; non‑NB simulator uses JSON messages for northbound application debugging.

Q: Why does the non‑NB simulator show “value out of range” for int/float fields?

A: Ensure the input values are within the defined range or specify the range in the development profile.

Profile Development FAQ

Q: Can profile fields be customized?

A: Profile fields cannot be customized; the example “value” corresponds to the paraName field.

Q: Do devices need to be re‑bound after updating services?

A: No, as long as manufacturerId, model, deviceType, etc., remain unchanged, only the updated profile and codec plugin need to be uploaded.

Q: Why does uploading a profile file report “invalid resource file format”?

A: Common causes include illegal characters in JSON (e.g., °C) or hidden illegal files in a zipped profile package. Validate JSON and remove hidden files.

SoftRadio FAQ

Q: What is SoftRadio?

A: SoftRadio is a PC software that enables NB‑IoT device and app server debugging without physical chips, modules, base stations, or core networks, improving development efficiency.

Q: SoftRadio localhost:8090 not reachable?

A: Clear browser cache and restart; also ensure the download was complete without interruptions.

Q: SoftRadio COM configuration not showing ports?

A: COM settings require a successfully bound device; use a virtual COM port created by appropriate tools.

Q: SSCOM commands not received by SoftRadio?

A: Verify that commands end with a newline/return character.

For more detailed answers, refer to the original FAQ links provided in the article.