Question 1

Sensor Not Connecting to Gateway

Accepted Answer

If a Sensor is not connecting to its Gateway

Q: Sensor Not Connecting to Gateway

<h1 id="ifasensorisnotconnectingtoitsgateway">If a Sensor is not connecting to its Gateway</h1> <p>|| <strong>Note:</strong> In the event a sensor requires repair, best-effort troubleshooting steps must be taken prior to the issuance of the Return Material Authorization form (RMA) required when returning a device to Monnit for diagnosis and/or repair.</p> <h4 id="whenasensorwillnotconnecttoagateway">When a sensor will not connect to a gateway:</h4> <p>With the exception of Monnit MoWi (WiFi) sensors, all Monnit sensors require a gateway to which they transmit data to be relayed to the data endpoint (generally iMonnit.com). You may find that your Monnit Commercial or Alta sensor is unable to communicate with it's corresponding gateway (when first setting up, or after it has already been communicating). If you find yourself with this issue, please follow the steps below to diagnose and troubleshoot the issue.</p> <h2 id="summaryofsteps">Summary of Steps</h2> <ul> <li>Check compatibility of sensor/gateway.</li> <li>Confirm the gateway and sensor have been added <em>to the same sensor network.</em></li> <li>Confirm the gateway is checking in.</li> <li>Through the iMonnit Online Portal, reset the sensor to the Default settings using the gray Default button under the Settings tab in the iMonnit Online Portal.</li> <li>Press and immediately release the Utility/Reset button on the gateway once (to download sensor ID's).</li> <li>Examine the sensor for damage or signs of liquid ingress and corrosion.</li> <li>Eliminate environmental variables by placing the sensor 10-15 feet from the gateway line of sight when possible (the sensor should not be tested closer than the minimum dista</li> </ul>

|| Note: In the event a sensor requires repair, best-effort troubleshooting steps must be taken prior to the issuance of the Return Material Authorization form (RMA) required when returning a device to Monnit for diagnosis and/or repair.

When a sensor will not connect to a gateway:

With the exception of Monnit MoWi (WiFi) sensors, all Monnit sensors require a gateway to which they transmit data to be relayed to the data endpoint (generally iMonnit.com). You may find that your Monnit Commercial or Alta sensor is unable to communicate with it's corresponding gateway (when first setting up, or after it has already been communicating). If you find yourself with this issue, please follow the steps below to diagnose and troubleshoot the issue.

Summary of Steps

Check compatibility of sensor/gateway.
Confirm the gateway and sensor have been added to the same sensor network.
Confirm the gateway is checking in.
Through the iMonnit Online Portal, reset the sensor to the Default settings using the gray Default button under the Settings tab in the iMonnit Online Portal.
Press and immediately release the Utility/Reset button on the gateway once (to download sensor ID's).
Examine the sensor for damage or signs of liquid ingress and corrosion.
Eliminate environmental variables by placing the sensor 10-15 feet from the gateway line of sight when possible (the sensor should not be tested closer than the minimum dista

Question 2

Unlocking and Pointing a gateway to a custom host or IP address (Enterprise/Express/MINE)

Accepted Answer

If you need to Unlock and/or Point a gateway to a custom host or IP address such as iMonnit Enterprise, iMonnit Express, or Monnit MINE

||| Note: Before you can point a gateway to your custom host or IP address, you need to unlock the gateway if this has not already been purchased. Gateway Unlock codes can be purchased from https://www.monnit.com/Product/MNA-GW-UL/. If your gateway is not already Unlocked, it will need to communicate with the iMonnit Online portal through the Internet on outbound port 3000 to receive the Unlock command.

Unlocking and pointing supported gateways:

Monnit calls the interface through which data is transmitted to Monnit software the Default Interface. Monnit Ethernet Gateway 4, Ethernet Gateway 3, 4G LTE Gateway, 3G Cellular Gateway, and 2G Cellular Gateway are supported by the SetHost tool (USB Gateways and Wireless Sensor Adapters may display an error, and a request to Unlock them along with an Unlock Code should be sent to support@monnit.com). This tool will allow you to Unlock and Point the gateway to a local Enterprise, Express, or MINE server (gateways can transmit data to only a single destination at a time using the Default Interface). Once you have the gateway in-hand, and have received an Unlock Code, you can follow the steps below to Unlock and Point your gateway to your local server.

Summary of Steps

_${color}[#730d0d](You must be signed into your iMonnit Online account in order to view the imonnit.com/SetHost site, o

Question 3

Updating a Gateway's Firmware for Ethernet or Cellular Gateways

Accepted Answer

How to update the firmware on a gateway through iMonnit Online for Ethernet or Cellular gateways

Keeping the gateway's firmware is an important step to resolving some unexpected issues. Firmware updates for Ethernet and cellular gateways are made available periodically through the iMonnit Online portal. In order for a gateway to update firmware, it must be communicating with the iMonnit Online portal (there is no manner by which a gateway's firmware can be updated locally or through iMonnit Enterprise/Express/MINE). This article will advise how to perform a gateway firmware update for Ethernet or Cellular gateways.

Updating a gateway's firmware

||| Note: ${color}#bc2929 Updating the gateway's firmware may reset the gateway's configurations to default settings. If you have your gateway programmed with a static IP address, this may be cleared out and DHCP (re)enabled. You should be prepared to reconfigure the gateway on a network with DHCP enabled if you perform an update on a gateway with a static IP address. Likewise, if you are using a 3G or 2G Cellular Gateway with your own carrier which requires a custom APN, this APN will need to be resent to the gateway as per the steps at the following link: https://monnit.azureedge.net/content/documents/quickstart/MQS024-Monnit-International-CGW-Quick-Start.pdf . _This applies to all EGW3, 2G Cellular, and 3G Cellular gateways with firmware up to version 1.4.3.0, and EGW4 firmware earlier than 1.0.5.8.

Question 4

Sensor not Accepting Configuration Change - "Fields waiting to be written"

Accepted Answer

If a Sensor is not accepting a configuration change

When a sensor configuration is not updating:

When a configuration change is made in the iMonnit software, this configuration is sent to the gateway and queued for delivery to the sensor. While this change is pending, you may see the message "Fields waiting to be written to sensor are not available for edit until transaction is complete." This indicates the change is pending, and should be accepted on the subsequent sensor check in; however, there are cases where the sensor may not accept the configuration change. This article will provide information on this scenario.

Fields waiting to be written

Summary of Steps

Confirm gateway firmware is up to date.
Confirm the sensor is currently communicating with the gateway.
Check for Local Alert of Control Unit pending messages.
Power the sensor off for 60 seconds, then back on.
Reform the gateway's network.

* Power cycle the sensor once more.

Confirm the gateway's firmware is up to date

Check to see if the gateway is due for a firmware update. If it is, see the steps at the following article to update the gateway firmware: Updating a Gateway's Firmware for Ethernet or Cellular Gateways .

Confirm the sensor is communicating with the gateway

In order for a sensor to accep

Question 5

Ethernet Gateway 4 - Accessing local configuration page (HTTP Interface) Locally

Accepted Answer

If you are attempting to configure your gateway using the local configuration page (HTTP Interface) of an Ethernet Gateway 4 Locally

|| Note: The Ethernet Gateway 4 has DHCP enabled by default. As there is no default IP address for this gateway (which differs from the Ethernet Gateway 3), it must be connected to a network that supports DHCP in order to first access the local configuration page. In order to do this, you will need to find the IP address that is assigned to the gateway via DHCP from your network. This often requires you to view the IP assignment in your DHCP server (router).

Accessing the local configuration page (HTTP Interface) of an Ethernet Gateway 4.

The Ethernet Gateway 4 offers a local configuration page through which you can modify gateway configurations locally. The page is accessible through a web browser by visiting the gateway's IP address. The Interface is disabled by default, so it must first be activated to access it. The interface does have an option which will allow you to activate the interface permanently if so desired. This article will provide information on the functionality and steps to access this interface. .

Summary of Steps

Connect the gateway to a network that supports IP assignment via DHCP.
Activate the HTTP Interface (local configuration page).
Access the gateway's local configuration page through a web browser.

* Configure the gateway.

Connect the gateway to a network that supports IP assignment vi

Question 6

Using the Ethernet Gateway 4 on a private MODBUS TCP or SNMP Network

Accepted Answer

If you are using your Ethernet Gateway 4 on a private MODBUS TCP or SNMP network (Default Interface disabled)

Using the Ethernet Gateway 4 on a private MODBUS TCP or SNMP network

The Ethernet Gateway 4 offers MODBUS TCP and SNMP Interfaces which you can poll to receive sensor data for retrieval in MODBUS TCP or SNMP networks. These interfaces are disabled by default, but they can be enabled through iMonnit software or through the local configuration page (HTTP Interface) of the gateway when a static IP address has been configured on the gateway. The Default Interface (iMonnit Online) is always enabled by default, but can be disabled if operating the gateway on a private network on which Monnit software is not being used (iMonnit Online, iMonnit Enterprise, iMonnit Express, or Monnit MINE). When enabling these interfaces for use when the gateway cannot communicate with Monnit software, there are special considerations. This article will provide insight into these considerations and steps for operating your gateway with this configuration.

Disabling the gateway's Default Server Interface

Note: the gateway's firmware should always be updated prior to disabling the gateway's Default Interface to ensure the gateway's most up to date interface operation. In order for the gateway to continue to receive sensor data and respond to polling on the MODBUS TCP/SNMP Interface while

Frequently Read Articles

Browse All Categories