This article is designed to provide useful information for enabling the debugging of the Automated Monitoring Node while communicating with the cellular network.
We assume that the device is a cellular-enabled node, with a version of the firmware for cellular units, and that the modem and SIM card have been activated. If you have any questions please reach out to our support team.
When a node is turned on, it will attempt to perform measurements of the sensors and sync the corresponding data to the server. It is important to note that every installation location is unique and there may be issues connecting to the server to send data. In order to understand if the issue is related to the network connection or otherwise, it will be necessary to connect to the equipment to perform diagnostics. When it has been determined that the node is operating normally but unable to sync data to the API then network debugging should be considered to determine what is the exact cause
The typical configuration does not have verbose modem debugging enabled, as it can be quite overwhelming to see when under normal operation and testing. The default output without debugging enabled appears as follows:
Power: 3V3_SW power enabled
Modem: Initializing..
Modem: Powered on!
Modem: Powered on!
.Modem: Powered on!
.Modem: Powered on!
.Modem: Powered on!
.
Modem: RSSI -120 SQ 0
Modem: Failed to disconnect from network!
Modem: Failed to turn deregister from network!
Modem: Failed to enable GPS!
In any of the potential issues listed above, it is important to understand what is causing the problem so that it can be remedied. The best way to do this is to connect to the node with a USB cable and serial terminal program to perform diagnostics. This guide will provide some steps to perform to enable diagnostics and will attempt to highlight common problems. For further assistance, please send these logs to our support team so we can assist further.
After opening the terminal, obtain a prompt by pressing C during the startup
Press 'C' to stop booting and configure..........
neatMon Main Menu
1: Network Config
2: Sensor Config
3: Utilities
x: < Save & Quit
>1
Network Config
1: HTTP Server: "api.neatmon.io"
2: HTTP Path: "/api/device/81a8e7b1-43e7-358f-d48afcae82c4"
3: HTTP Port: 1330
4: API Setup
5: Sync rate: 15m
6: APN Network: "vzwinternet"
7: APN Username: ""
8: APN Password: ""
9: Next page....
x: <Back
>
Network Config
1: HTTP Server: "api.neatmon.io"
2: HTTP Path: "/api/device/81a8e7b1-43e7-358f-d48afcae82c4"
3: HTTP Port: 1330
4: API Setup
5: Sync rate: 15m
6: APN Network: "vzwinternet"
7: APN Username: ""
8: APN Password: ""
9: Next page....
x: <Back
>9
Network Config Continued...
1: Enable modem debugging
2: Network Registration Type: "AUTO"
3: Select Modem Type: "LE910Cx"
4. Select Modem Firmware: "1"
5: Alert sync rate: 5m
x: <Back
>1
Modem: debugging enabled
After enabling debugging, save and continue to have the new settings take effect
Network Config
1: HTTP Server: "api.neatmon.io"
2: HTTP Path: "/api/device/81a8e7b1-43e7-358f-d48afcae82c4"
3: HTTP Port: 1330
4: API Setup
5: Sync rate: 15m
6: APN Network: "vzwinternet"
7: APN Username: ""
8: APN Password: ""
9: Next page....
x: <Back
>x
Exiting...
neatMon Main Menu
1: Network Config
2: Sensor Config
3: Utilities
x: < Save & Quit
>x
Quitting...
The modem will attempt to connect to the wireless network however in low signal areas it may be unable to gain a connection to the network. Be sure that the signal strength is better than -90db
otherwise the node will have difficulty communicating on the network.
The Automated Monitoring Node was shipped with a configuration sheet displaying the modem type, firmware, and port configuration. If the device has had is configuration reset it may be configured incorrectly. Please refer to the configuration sheet, or contact our support team for assistance if needed
An unresponsive modem can be caused by a number of things. Be sure to check:
Below is an shortened example of an unresponsive modem, note that after power is turned on, the modem receives an AT
command and never responds OK
Power: 3V3_SW power enabled
Modem: Initializing..
Modem: Powered on!
AT
AT
AT
AT
AT
Modem: Powered on!
AT
AT
AT
AT
AT