ALTA Monnit MNG2-4-CME-CCE-ND User manual

Remote Monitoring for Business
IMPORTANT!
For best results, please wait to power on your ALTA®IoT Gateway until after you have
created an iMonnit account and added the gateway and sensors to your new IoT network.
ALTA®IoT Gateway
USER GUIDE
PAGE I
IMPORTANT! Before purchasing. you need to
verify that your cellular provider is compatible with
our gateway. Please click the link below to view the
checklist you need to share with your provider.
Provider Requirements

Table of Contents
PAGE II
I. ABOUT THE ALTA®IoT GATEWAY 1
II. HOW YOUR GATEWAY WORKS 2
III. GATEWAY SECURITY 2
IV. GATEWAY REGISTRATION 3
V. USING THE IoT GATEWAY 3
USING THE COMMERCIAL IoT GATEWAY 3
UNDERSTANDING THE COMMERCIAL IoT GATEWAY LIGHTS 4
INDUSTRIAL POWER INTERRUPT SWITCH 4
SETTING UP AND POWERING ON THE INDUSTRIAL IoT GATEWAY 5
UNDERSTANDING THE INDUSTRIAL IoT GATEWAY LIGHTS 5
STANDARD POWER MODE OPERATIONS 6
BATTERY POWER MODE OPERATIONS 6
UTILITY BUTTON ACTIONS 6
VI. IoT GATEWAY SETTINGS IN iMONNIT 7
GENERAL SETTINGS 7
ETHERNET SETTINGS 8
CELLULAR SETTINGS 8
MANUAL SIM SETTINGS 9
COMMANDS 10
HTTP INTERFACE 10
VII. USING THE LOCAL INTERFACE 10
STATUS VIEW 11
ETHERNET LOCAL AREA NETWORK STATUS 11
CELLULAR NETWORK STATUS 11
GENERAL CONFIGURATIONS 12
ETHERNET NETWORK 13
CELLULAR NETWORK 13
MANUAL SIM SETTINGS 14
WIRELESS NETWORK 15
CELLULAR PROVIDER INFORMATION REQUEST 16
TROUBLESHOOTING 17
SUPPORT 20
WARRANTY INFORMATION 20
CERTIFICATIONS 21
SAFETY INFORMATION 23
COVERAGE MAPS 23

The Monnit ALTA®IoT Gateway uses 4G LTE CAT-M1/NB2 cellular technology to control ALTA®Wireless Sensor settings
without additional IT infrastructure. All you need is a power source and the iMonnit cloud platform to monitor your
environment and equipment using Monnit's industry-leading wireless devices. The ALTA IoT Gateway communicates with
ALTA Sensors and iMonnit to deliver data and send alerts about various machine, equipment, or area conditions.
The IoT Gateway and iMonnit work together to connect and configure ALTA Sensors over the Internet and make their data
accessible virtually anytime, anywhere. The IoT Gateway provides the crucial link that connects ALTA Sensors to iMonnit
using 4G LTE CAT-M1/NB2 (4G Long-Term Evolution Category M1/NarrowBand-Internet of Things (NB-IoT) 2) cellular
technology. The gateway is equipped with a 60-hour backup battery and will continue to communicate with iMonnit via
cellular transmission in the event of a power outage. Additionally, the IoT Gateway comes with an RJ-45 Ethernet jack
(commercial version only) for local device configuration. The IoT Gateway, however, is ideal for applications without a
wired Internet connection or where infrastructure is dedicated to other resources.
The IoT Gateway includes a GNSS location chipset supporting GPS, GLONASS, BeiDou, Galileo, and QZSS satellites.
With the proper gateway subscription enabled, gateway location data can be collected, viewed, and distributed to
additional software via an application programming interface (API). Location data functionality is only available when the
cellular technologies are enabled.
I. ABOUT THE GATEWAY
ALTA IoT GATEWAY FEATURES
- 4G LTE CAT-M1/NB2 cellular technology
- Wireless range of 1,200+ feet through 12+ walls1
- Frequency-Hopping Spread Spectrum (FHSS)
- Best-in-class interference immunity
- Encrypt-RF®Security (256-bit Diffie-Hellman Key Exchange + AES-128 CBC for sensor data messages)
- 32,000 sensor message memory2
- Over-the-air (OTA) updates (future-proof)
- True plug and play, no hassles for Internet configuration setup
- No PC required for operation
- Local status LEDs with transmission and online status indicators
- AC power supply
- Up to 60-hour battery backup in the event of a power outage
- RJ-45 10/100BASE-TX Ethernet jack for configuration and server connectivity (commercial version only)
- Location data subscription supported (GPS/GLONASS/BeuDou/Galileo/QZSS)
1 Actual range may vary depending on the environment.
2 Total messages in memory varies with sensor type. (32,000 is for Temperature Sensors. Additional
information is available at Monnit.com/Support/).
EXAMPLE APPLICATIONS
- Remote Location and Asset Monitoring
- Shipping and Transportation
- Agricultural Monitoring
- Vacant Property Management
- Vacation Home Property Management
- Construction Site Monitoring
- Data Center Monitoring
PAGE 1

II. HOW YOUR GATEWAY WORKS
The ALTA IoT Gateway manages communication between ALTA Sensors and iMonnit. When running, the IoT Gateway
will periodically transmit data on a Heartbeat (a preset interval in minutes). The gateway will receive data from all sensors
assigned to the network (within range) and store the data it receives from the sensors until its next Heartbeat.
The ALTA IoT Gateway is a cellular (LTE-M or CAT-M1) gateway. It uses its connection to relay data received from ALTA
Sensors to iMonnit cloud-based software. Sensors communicate with the gateway, then the gateway relays information to
iMonnit.
For your wireless sensors to work optimally, orient all antennas for your sensors and gateways in the same direction
(typically vertical). Sensors must also be at least three feet away from other sensors and the wireless gateway in order to
function properly.
III. GATEWAY SECURITY
The ALTA IoT Gateway is designed and built to manage
data from the sensors monitoring your environment and
equipment securely. The same methods used by financial
institutions to transmit data are also used in Monnit security
infrastructure. The IoT Gateway's security features include
tamper-proof network interfaces, data encryption, and
bank-grade security.
Monnit?s proprietary sensor protocol uses low transmit
power and specialized radio equipment to share application
data. Packet-level encryption and verification are vital in
ensuring traffic isn?t altered between sensors and
gateways. All data is transmitted securely from your
devices, with a best-in-class range and power consumption
protocol.
SENSOR COMMUNICATION SECURITY
Wireless devices listening on open communication protocols cannot eavesdrop on ALTA Sensors. Monnit's sensor-to-gateway data
communication implements Encrypt-RF® encryption technology. This creates a secure wireless tunnel, generated using ECDH-256
(Elliptic Curve Diffie-Hellman) public key exchange to develop a unique symmetric key between each pair of devices. Sensors and
gateways use this link-specific key to process packet-level data with hardware-accelerated 128-bit AES encryption. This minimizes
power consumption to optimize battery life. Thanks to this combination, Monnit offers robust bank-grade security at every level.
For more information, reference the security section with this link:
DATA SECURITY ON THE GATEWAY
The ALTA IoT Gateway prevents prying eyes from accessing the data stored on the sensors. The ALTA IoT Gateway doesn't run on an
off-the-shelf, multi-function operating system. Instead, it runs a purpose-specific, real-time embedded state machine that can't be
hacked to run malicious processes. There are also no active interface listeners that can be used to gain access to the device over the
network. The fortified gateway secures data from attackers and protects the gateway from becoming a relay for malicious programs.
For more information on Monnit gateway security, reference this link:
SERVER COMMUNICATION SECURITY
Communication between your ALTA IoT Gateway and iMonnit is secured by packet-level encryption with Encrypt-RF. Similar to the
security between the sensors and the gateway, the gateway and the server also establish a unique key using ECDH-256 for encrypting
data. The packet-level data is encrypted end to end, removing additional requirements to configure specialized cellular VPNs for
privacy. The gateway can still operate within a VPN, if it is present.
PAGE 2

PAGE 3
IV. GATEWAY REGISTRATION
REGISTERING THE ALTA IoT GATEWAY
You will need to enter the Device ID and the Security Code (SC) from the ALTA IoT Gateway in the corresponding text boxes. Use the
camera on your smartphone to scan the QR code on your gateway. If you don't have a camera on your phone, or are accessing iMonnit
through a desktop computer, you may enter the Device ID and SC manually.
- The Device ID is a unique number located on each device label.
- Next, you?ll be asked to enter the SC on your device. The SC will be all letters, no numbers. It can also be found on the barcode
label of the gateway.
When completed, select the Submit button.
IMPORTANT: Add the gateway and all sensors to iMonnit so that on boot, the gateway can download and whitelist the sensors from the account.
If this is your first time using the iMonnit online portal, you'll need to create a new account. If you have already created an account,
start by logging in. For instructions on how to register for an iMonnit account, please consult the iMonnit User Guide.
V. USING THE IoT GATEWAY
1. Attach the cellular and ALTA antennas to the back of the gateway.
2. Plug the power supply cord into an outlet.
3. Slide the power switch on.
4. After the three LEDs switch to green, your gateway is ready to use.
FRONT BACK
USING THE COMMERCIAL IoT GATEWAY

UNDERSTANDING THE COMMERCIAL IoT GATEWAY LIGHTS
The gateway will enter three stages as it powers on:
Power-on stage: The gateway analyzes electronics and programming. The LEDs will flash red and green, before turning green for two
seconds. In case of a hardware failure, the light sequence will repeat continually. Please contact technical support if the LEDs aren?t
green after five minutes.
Connection stage: The gateway will attempt to start the cellular gateway service and wireless network connections. See diagram
below to decode the three LEDs and the states the LEDs indicate.
Operational stage: If the Gateway Power Mode is set to "Forced High Power" or "Standard Power" and line power is present, all of the
LEDs will remain green while powered externally, unless reporting activity on a connection, or if there is an issue. If the Gateway Power
Mode is set to "Forced Low Power," or "Standard Power," without line power being present, the gateway will only use the active light
sequence when the gateway is communicating to the server. Otherwise, the LEDs are powered off.
Steady Green: ALTAwireless network online
Blinking Green: Active communication with wireless sensors
Steady Red: Network reform in progress or network offline
Steady Green: Last communication with Monnit?s server was good
Blinking Green: Active communication with Monnit?s server
Steady Red: Last communication with Monnit?s server was unsuccessful
Steady Green: Internet connection ready
Single Blink Green: Cellular connection idle
Double Blink Green: Scanning for tower
Triple Blink Green: Requesting data session and IP Address
Solid Green with Single Red Blink: Low signal report
Solid Red with One Second Flashing Red/Green: SIM Fault
Solid Red with Single Green Blink: Limited or no Internet
Flashing Red for One Second: Cellular module startup fault
Flashing Red for Three Seconds: Cellular fault (Tower rejection)
Flashing Green for One Second: Cellular FOTA download in progress
Flashing Green for Three Seconds: Cellular FOTA upgrading
SENSOR COMMUNICATION LED
GATEWAY SERVICE LED
CELLULAR LINK LED
Note: When setting up the gateway, initial tower connections may take 2?20 minutes depending on
the carrier/SIM specific setup and the number of cellular bands enabled. Subsequent connections
are typically faster.
INDUSTRIAL POWER INTERRUPT SWITCH
The ALTA Industrial IoT Gateway comes with a power interrupt control operated by a
magnetic reed switch. The power interrupt control disconnects both the main power
supply and battery backup. Use this feature if you need to force a reset of the gateway
without opening the waterproof seal. When magnetic contact is made, the gateway
status lights will turn off, indicating successful power interruption.
Note: Power is only interrupted while the magnet is on the
touchpoint. Once the magnet is removed, power is returned.
PAGE 4

Blinking Green: Active communication with Monnit?s server
PAGE 5
SETTING UP AND POWERING ON THE INDUSTRIAL IOT GATEWAY
1. Connect your antennas to the gateway as seen in the below diagram.
2. Plug the power supply cord into an outlet.
3. After the three LED lights switch to green, your network is ready to use.
PAGE 4
Cellular
Antenna Radio Antenna
The gateway will enter three stages as it powers on:
Power-on stage: The gateway will analyze electronics and programming. The LED lights will flash red and green, before all becoming
green for one second. In case of failure, the light sequence will repeat after ten seconds. Please contact technical support if the lights
aren?t green after two minutes.
Connection stage: The gateway will attempt to settle all operational connections. As the gateway first connects to the network, all
other lights will be dark. A blinking green light indicates the gateway is attempting to make a tower connection. A flashing red light is a
signal the cellular connection has encountered a problem.
Operational stage: All of the lights will remain green while powered externally, unless there is an issue. A blinking cellular link light is a
signal that the gateway has encountered an issue in the cellular network.
Steady Red: Sensor communication problem
Steady Green: Communication with sensors is OK
Blinking Green: Active communication with sensors
Steady Red: Last communication with Monnit?s server was
unsuccessful
Steady Green: Last communication with Monnit?s server was OK
Sensor Data
Internet
Server
Cellular
Service
UNDERSTANDING THE INDUSTRIAL IoT GATEWAY LIGHTS
Steady Green: Internet connection ready
Single Blink Green: Cellular connection idle
Double Blink Green: Scanning for tower
Triple Blink Green: Requesting data session and IP Address
Solid Green with Single Red Blink: Low signal report
Solid Red with One Second Flashing Red/Green: SIM Fault
Solid Red with Single Green Blink: Limited or no Internet
Flashing Red for One Second: Cellular module startup fault
Flashing Red for Three Seconds: Cellular fault (Tower rejection)
Flashing Green for One Second: Cellular FOTA download in progress
Flashing Green for Three Seconds: Cellular FOTA upgrading

Attempt Back-off Time Between Attempts Cumulative Time Attempting Communication
0 N/A 0 minutes
1 0 minute 2 minutes
2 0 minute 4 minutes
3 1 minute 7 minutes
4 2 minute 11 minutes
5 5 minutes 18 minutes
6 10 minutes 30 minutes
7 15 minutes 47 minutes
8+ random 20?40 minutes ...22?42 minutesadded on every failure
PAGE 6
"Standard" or "Forced-high" power mode operations
While the gateway is powered normally or configured to "Forced-high" power mode, the gateway will remain fully active and ready to
communicate with the server. All LED indicators will be kept active (as described above), The Ethernet and cellular interfaces will stay
connected, and GPS location services will remain active.
GPS locations services are permitted to acquire satellite data for up to nine minutes. If a suitable location calculation is not achieved
during that time, the gateway will report the lack of a location-fix and the gateway will wait for the next Location Heartbeat to re-acquire
a location fix.
The gateway will attempt to communicate with the server for up to one minute for every interface enabled (default is two minutes). If the
gateway is unable to connect with the server using either the Ethernet or cellular interface, the gateway will begin to retry connectivity
based on the following sequence:
B
On "Battery" or "Forced-low" power mode operations
If the gateway is running off of battery power or the device has been switched to a "Forced-low power" mode, all lights are typically off.
The sensor data light will blink green when data is received by the gateway. The Internet server light will blink every five seconds,
indicating the status of the last connection. If the light is green, the communication was good. If the light is red, the communication
failed. In this mode, the Ethernet connectivity is powered down and the HTTP interface is not available.
Gateway Heartbeats, Polls, and GPS location services are limited to a minimum of 15 minutes during low power events. However, if a
wireless device signals that an urgent communication is required to be delivered to the server, the gateway will power up Ethernet,
cellular, and GPS services temporarily during a server connection. If the gateway is unable to connect with the server using either the
Ethernet or cellular interface, the gateway will begin to retry connectivity based on the following sequence:
Utility button actions: The utility button can be used during the operational stage to perform a configuration reset or a full-factory
reset. The configuration reset will erase all of your unique settings and return the gateway to factory default settings, while saving any
data collected by the sensors prior to the reset. The full-factory reset will not only restore default settings, but will also erase any data
on the gateway.
To perform a configuration reset, the utility button is pressed for 5 to 10 seconds and released during that time. After pressing the utility
button for more than five seconds, all of the LEDs turn solid red. Releasing the button during this LED display will result in the
configuration reset.
If the utility button is held for more than 10 seconds, all of the LEDs will begin to blink red. Releasing the utility button when all of the
LEDs are blinking red will result in a full factory reset of the gateway, restoration of default settings, and the loss of all data in memory.
Attempt Back-off Time Between Attempts Cumulative Time Attempting Communication
0 N/A 0 minutes
1 5 minute 7 minutes
2 5 minute 14 minutes
3 5 minutes 21 minutes
4 5 minutes 28 minutes
5+ random 20?40 minutes ...22?42 minutesadded on every failure

Access IoT Gateway settings by selecting Gateways in the main navigation panel. Choose the IoT Gateway from the list of gateways
registered to your account. Select the Settings tab to edit the gateway.
GENERAL SETTINGS
VI. IOT GATEWAY SETTINGS IN iMONNIT
A. Gateway Name assigns your gateway a unique title. By
default, the gateway name will be the type followed by the
Device ID.
B. Heartbeat Minutes configures the interval that the
gateway periodically delivers data to the server. The default
is 15 minutes, meaning the gateway will report to the Primary
Server every 15 minutes.
C. Poll Rate Minutes configures the interval that the
gateway periodically checks in with the server. If the server
has urgent commands or notification for wireless sensors,
the Primary Server will signal the gateway for a full data
dialog (Heartbeat). The default is 0 minutes, meaning the
gateway poll feature is disabled.
D. Connection Preferences enables the selection of how
the server sends messages to the Primary Server. Options
are Ethernet Preferred (default), Ethernet Only, and
Cellular Only. Ethernet Preferred is also "Ethernet with
Cellular Backup." When either Ethernet Preferred or
Cellular Only are selected, the location (GPS/GNSS) data
generator capability are enabled. Ethernet Only will disable
the location data generator.
E. On Aware Messages configuration indicates if the Aware
Message arrival event will Trigger Heartbeat (default) or
Wait for Heartbeat.When the switch is toggled to Trigger
Heartbeat, the gateway is configured to immediately report
to the server. When toggled to Wait for Heartbeat,
messages are stored until the gateway is scheduled to
communicate before connecting with the Primary Server.
F. On Server Loss configuration indicates if the wireless
network on the gateway will stay active and Log Sensor
Data (default) or if the gateway will Disable Wireless
network. In networks with multiple gateways, forcing the
sensors to switch to an active gateway will enable more
timely delivery of data to the server.
G. Gateway Power Mode enables the selection between
Standard power (default), Force Low Power, and Force
High Power, from a drop-down menu. Standard means that
the gateway will keep lights and cellular transmission active
when plugged into an outlet. On battery power, the gateway
will power down lights and the cellular connection between
communications. Force Low Power means the gateway will
always power down the lights and the cellular connection
when not talking to the server. Force High Power means the
gateway will keep the lights and cellular module active,
regardless of whether or not the gateway is plugged in.
H. Primary Server shows the configured URL:PORT of the server. If the Gateway is "UNLOCKED," this configuration changes to a
modifiable text-box.
I. Location Heartbeat Minutes is only visible if the gateway has been "LOCATION UNLOCKED" and is used to configure the periodic
delivery of location (GPS/GNSS) data to the Primary Server. Location data functionality is only available when the cellular
technologies are enabled (See Connection Preferences "D" ).
PAGE 7

A. The Global System for Mobile
Communications utilizes a 15-digit IMSI
(International Mobile Subscriber Identity) number
as the primary mode to identify the country,
mobile network, and subscriber. It is formatted
as MCC-MNC-MSIN. MCC is the Mobile Country
Code. MNC is the Mobile Network Code
attached to the cellular network. MSIN is a serial
number making the IMSI unique to the
subscriber.
B. The ICCID is the 19-digit unique identification
number corresponding to the cellular SIM card.
C. IMEI (International Mobile Equipment Identity)
is a number exclusive to your IoT Gateway to
identify the gateway to the cell tower. The Global
System for the Mobile Communications network
stores the IMEI numbers in their database (EIR -
Equipment Identity Register) containing all valid
cellular equipment.
D. Carrier Preference permits the selection of
Auto (default) or Manual. Auto permits the
gateway to use standard gateway SIM
identification rules to automatically preconfigures
the gateway's cellular service. Manual is useful if
that gateway does not reliably and in a timely
manner connect to a tower, or a non-supported
carrier SIM is used. PAGE 8
ETHERNET SETTINGS (Commercial Version Only)
Choose the Ethernet Settings tab under Settings to open up the
configuration page for the Local Area Network (LAN). The LAN is used
for local configuration options when server connectivity is not possible.
This page includes the ability to switch your network Internet Protocol
(IP) Address from DHCP assigned to Static. A DHCP assigned address
will be the default network IP Address.
Static IP - A static IP Address is a numerical sequence assigned to a
computer by a network administrator. This is different from a Dynamic IP
Address. A Static IP doesn?t periodically change and remains constant.
Network Mask - Also known as a ?subnet mask,?this number hides the
network half of an IP Address.
Default Gateway - This is the forwarding host the gateway uses to relay data
to the Internet, typically your router IP Address.
Default DNS Server - DNS Servers take alphanumerical data (like a URL
address) and returns the IP Address for the server containing the information
you need.
To change your IP Address to a Static IP, navigate to the network IP
option and switch it from DHCP to Static. Then input your data for the
Static IP, Network Mask, Default Gateway, and Default DNS Server.
NOTE: Please consult your your Network Administrators to obtain the
correct "Static" setting for your network.
CELLULAR SETTINGS
C
D
A
B

Manual Settings and Options (expanded)
The Manual setting permits additional settings to become
available (i.e. Carrier APN, SIM Authentication Type, Carrier
Active Bands).
Using Cellular Provider Information
Cellular Access Point Name (APN) - Enables access to the
cellular network and public or private Internet access. These APNs
are unique to the cellular network or sub-network designated for
the SIM. The following two options are supported:
- Unspecified APN - If the field is left blank, the APN is
requested from the tower on connection
- Specified APN - if the field is not left blank, the cellular
connection is pre-configured with this APN prior to
requesting a tower connection and Internet access
SIM Authentication Type - To create authenticated connections,
APNs may have a username/password setting and use a specific
security protocol to send a username and password. The following
options are supported:
- "None" - No username or password required and no
username and password are available
- "PAP" or "CHAP" - Password Authentication Protocol
(PAP) or Challenge Handshake Authentication Protocol
(CHAP) is used to send the username and password and
the following fields become visible:
Cellular Bands - Different networks and locations will have
different cellular bands available: CAT-M1 (M-Enabled) and
NB-IoT (NB-Enabled) connections:
When a checkbox is unmarked, the band will not used
When a checkbox is marked, the band will be used
Confirm Connectivity
After saving the configurations, the gateway will reboot and attempt
these settings. You can see the successful cellular settings:
If the bottom gateway indicator is green and stable, the cellular connection is active.
View "status.htm" and verify the cellular status is connected.
If the gateway is not connecting after saving and applying the information from the cellular provider, then additional, advanced
troubleshooting steps need to be taken.
Note:
- If either NB or M technologies are not used, disable the
technology by not checking any bands
- If no bands are enabled, then the page will prompt you to specify
at least one band
- If many bands and technologies are selected, the gateway will
take a long time to scan for a tower
PAGE 9

PAGE 10
COMMANDS
Choose the Commands tab located just under Settings to access the Commands page.
A. The Auto Reset field is the amount of time in hours that the
Local Interface will automatically reboot. Setting this to 0 will
disable the feature. The maximum setting is 8760 hours.
B. Selecting the Reform Network command will trigger the
gateway to remove all sensors from the internal whitelist, and
then request a new sensor list from the server. This command will
force all sensors to reinitialize their connection with the gateway.
Reforming the network cleans up communication when multiple
networks are in range of each other so they are all in sync. This is
especially useful if you must move sensors to a new network, and
would like to clear these sensors from the gateway?s internal list.
Reforming the network will place a new list of sensors that will
continue to exchange data.
C. If there are updates available for your gateway firmware, the
Update Gateway Firmware button will appear, giving you the
option to select it and install the latest firmware.
D. Choosing the Reset Gateway to Factory Defaults button will
erase all of your unique settings and return the gateway to factory
default settings.
HTTP INTERFACE (Commercial Ethernet Version Only)
A. The IoT Gateway has a local HTTP configuration Interface.
The HTTP Interface may be enabled so that it is accessible to
change settings within its timeout window, discussed below, or to
simply display status and settings information. The HTTP
Interface may also be disabled so that it is inaccessible.
B. The Configuration Timeout sets the amount of time the HTTP
Interface may be used to change settings on the IoT Gateway
after startup or a utility button press. Options are "Read Only"
(default), "1 minute," "5 minutes," "30 minutes," or "Always
Available." After this time, the HTTP Interface is only available to
display status and settings information.
VII. USING THE LOCAL INTERFACE (COMMERCIAL ETHERNET VERSION ONLY)
AB
C
A
B
D
If using iMonnit is not an option, you can set up your gateway settings through the local interface.
-Connect the gateway Ethernet cord by one of the following methods:
-AUTO-IP Method: Plug the cable directly into a PC and disable other networking interfaces. After 60 seconds, most PCs will
default to randomly generated IP settings.
-Network Method: Plug the cable into a router or switch.
-Plug in the gateway to a power outlet.
-Power on the gateway. While booting, the lights will scroll red and green. At the end of the boot process, all of the lights will be
green for two seconds.
-While the lights are green, quickly press and hold the utility button until the lights change to all red. Release the button and the
local configuration page will be temporarily enabled and writable.
-If using the Network Method: Use a PC on the local network to access your router?s configuration page first (see your router
documentation). Use your router?s web interface to determine the IP address it assigns to your gateway.
-Use your web browser to connect to your gateway using the assigned IP address or AUTO-IP "http://169.254.100.1". You should
be redirected to the Gateway Status page. Note - Using https:// will result in connection failure.
-Once the gateway interface has been reached, head over to the Settings tab and select the Ethernet Network option from the
left-hand menu. Under the HTTP Interface Settings, enable the HTTP Interface and select an appropriate timeout time, from "1
Minute" to "Always Available" from the HTTP Configuration Timeout. Select Save Changes when completed.
-Note that each time a page is refreshed or every time the gateway restarts, the HTTP interface time resets. After it times out, the
web interface will be disabled until either the gateway restarts with a non-zero timeout value, or the special restart mode is
enabled using the utility button.

PAGE 11
STATUS VIEW
ETHERNET LOCAL AREA NETWORK STATUS
This is a Read-Only section listing the current
conditions for your Local Area Network.
Gateway MAC Address - This is the media
access control address of your gateway to
exclusively identify the device to a Network
Interface Controller.
Gateway IP Address - This is a numerical
identifier for your gateway when it is connected to
the Internet.
Router IP Address - This is a numerical identifier
for your router when it is connected to the Internet.
Network Mask - Also known as a "Subnet Mask,"
this masks the IP Address by dividing it up into the
network address and the host address.
DNS Address - A Domain Name System address
is the method employed by a URL to translate the
alphabetic entry in an address bar into a numerical
address associated with a server.
CELLULAR NETWORK STATUS
Link - Defines whether your Cellular Network is
connected.
IMEI - (International Mobile Equipment Identity) is
a number exclusive to your IoT Gateway to identify
the gateway to the cell tower. The Global System
for Mobile Communications network stores the
IMEI numbers in their database (EIR - Equipment
Identity Register) containing all valid cellular
equipment.
ICCID - The 19-digit unique identification number
corresponding to the cellular SIM card. It is
possible to change the information contained on a
SIM (including the IMSI), but the identity of the
SIM itself remains the same.
IMSI - The Global System for Mobile
Communications utilizes a 15-digit IMSI (International Mobile Subscriber Identity) number as the primary mode to identify the country,
mobile network, and subscriber. It is formatted as MCC-MNC-MSIN. MCC is the Mobile Country Code. MNC is the Mobile Network
Code attached to the cellular network. MSIN is a serial number making the IMSI unique to a subscriber.
Carrier - The cellular carrier for your network.
Signal - This is the signal strength of the cellular network. Values range from 0?31. Values less than 4 means low signal.
Interface Status
The HTTP Interface shows the status of the default server for the HTTP interface, as hosted on the IoT Gateway, and whether the
default server is ON or OFF.
Location (GPS/GNSS) interface shows the current status of the GPS/GNSS interface.
Wireless Network Status
Data cache used - The percentage of your default server cache used by data from your wireless devices.
Total wireless devices - The total number of wireless devices reporting to this gateway.
Wireless devices list - Table lists or slot. The total number of wireless devices reporting to this gateway.

PAGE 12
GENERAL CONFIGURATIONS
Gateway Settings
Power Mode - As discussed above,
this setting allows the user to choose
Standard, which keeps lights and
cellular transmission active when
plugged into an outlet, or, when on
battery power, powers down lights
and the cellular connection between
communications. The user may also
choose Force Low Power, so the
gateway always powers down the
lights and the cellular connection
when not talking to the server, or
Force High Power, so the gateway
always keeps the lights and cellular
transmission active.
GNSS/GPS Heartbeat Minutes is
only visible if the gateway has been
"LOCATION UNLOCKED" and is
used to configure the periodic delivery
of location (GPS/GNSS) data to the
Default Server. Location data
functionality is only available when
the cellular technologies are enabled
(See Connection Preferences).
Default Server Settings
Heartbeat Minutes - Defines the
report interval between the IoT
Gateway and the server that receives
its sensor data.
Poll Rate Minutes -Configures the
interval that the gateway periodically
checks in with the server. If the server
has urgent commands or notifications
for wireless sensors, the Primary
Server will signal the gateway for a
full data dialog (Heartbeat). The
default is 0 minutes, meaning the
gateway poll feature is disabled.
On Aware Messages - Determines whether the IoT Gateway will "Trigger Heartbeat" or "Wait for Heartbeat" when a sensor in the
network maintained by the gateway informs the gateway that this sensor has entered an Aware State. This determines whether the
gateway can wait until its next scheduled Heartbeat report to convey this information to the server providing access to the sensor data.
On Server Loss - Configures the IoT Gateway to either "Disable Wireless Network" or maintain the network and "Log Sensor Data"
while the server is unavailable. By default, the gateway is configured to maintain its wireless network and save sensor reports on its
local memory until the connection with the server is restored. In networks with more than one gateway, disabling the network allows
sensors to jump to connected gateways and deliver data to the server in a more timely manner.
Connection Preferences enables the selection of how the server sends messages to the Primary Server. Options are Ethernet
Preferred (default), Ethernet Only, and Cellular Only. Ethernet Preferred is also "Ethernet with Cellular Backup." When either
Ethernet Preferred or Cellular Only are selected, the location (GPS/GNSS) data generator capability are enabled. Ethernet Only will
disable the location data generator.
Default Server Name/IP and Server Port are the configured URL:PORT of the server and only visible when the Gateway is
"UNLOCKED."
Auto Reboot Settings
Reboot Period - Defines the number of hours before the Local Interface automatically reboots, up to a maximum of 8760 hours. Setting
this to 0 will disable the feature.

PAGE 13
ETHERNET NETWORK
Local Area Network Settings
From the Ethernet Network tab, you can modify the settings
for your IP Address, Network Mask, Default Gateway, and DNS
Server.
IP Address - A unique number typically formatted as
XXX.XXX.XXX.X. It can be dynamic, meaning the IP Address is
constantly changing, or static, meaning the IP Address stays
the same.
Router IP Address - This is a unique number identifying your
router to the default server.
Subnet Mask - This number hides the network half of an IP
Address. The most common Subnet Mask number is
255.255.255.0.
DNS Server - DNS Servers take alphanumerical data (like a
URL address) and return the IP Address for the server
containing the information you?re looking for.
HTTP Interface Settings
HTTP Interface - The local HTTP Interface may be enabled so
that it is either available to configure settings of the IoT
Gateway or available to display status and settings information
in a Read-Only state. Alternatively, the local HTTP Interface may be disabled, so it becomes inaccessible.
HTTP Configuration Timeout - This drop-down menu allows you to set a predefined amount of time of "1 Minute," "5 Minutes," or "30
Minutes" during which the local HTTP Interface can be used to configure settings on the IoT Gateway after startup. After this time, the
HTTP Interface cannot change settings on the gateway and only displays status and settings information. The gateway must be
submitted to a factory reboot, or reconfigured in iMonnit, so that the HTTP Interface can change settings again during the timeout
window. The timeout window is refreshed each time the Interface page is refreshed or every time the gateway restarts the HTTP
Interface. The timeout may also be set to "Always Available," so there is no timeout window on the Interface's ability to change settings,
and "Read Only," which prevents the HTTP Interface from changing settings immediately.
CELLULAR NETWORK
The Cellular Network Configuration holds a
drop-down menu to select your cell Carrier
Preferences, concerning the APN and the
active bands enabled for CAT-M1/LTE
CAT-M/LTE-M and NB-IoT communication with a
cellular tower. In most situations, Auto
Configuration should be selected to allow the
pre-configured SIM card shipped with the IoT
Gateway to handle configuration of the APN and
active bands.

PAGE 14
Manual Settings and Options (expanded)
The Manual setting permits additional settings to become
available (i.e. Carrier APN, SIM Authentication Type, Carrier
Active Bands).
Using Cellular Provider Information
Cellular Access Point Name (APN) - Enables access to the
cellular network and public or private Internet access. These
APNs are unique to the cellular network or sub-network
designated for the SIM. The following two options are
supported:
- Unspecified APN - If the field is left blank, the APN is
requested from the tower on connection
- Specified APN - if the field is not left blank, the cellular
connection is pre-configured with this APN prior to
requesting a tower connection and Internet access
SIM Authentication Type - To create authenticated
connections, APNs may have a username/password setting
and use a specific security protocol to send a username and
password. The following options are supported:
- "None" - No username or password required and no
username and password are available
- "PAP" or "CHAP" - Password Authentication
Protocol (PAP) or Challenge Handshake
Authentication Protocol (CHAP) is used to send the
username and password and following fields become
visible:
Cellular Bands - Different networks and locations will have
different cellular bands available: CAT-M1 (M-Enabled) and
NB-IoT (NB-Enabled) connections:
When a checkbox is unmarked, the band will not used
When a checkbox is marked, the band will be used
Confirm Connectivity
After saving the configurations, the gateway will reboot and attempt these settings. You can see the successful cellular settings:
If the bottom gateway indicator is green and stable, the cellular connection is active.
View "status.htm" and verify the cellular status is connected.
If the gateway is not connecting after saving and applying the information from the cellular provider, then additional, advanced
troubleshooting steps need to be taken.
Note:
- If either NB or M technologies are not used, disable the
technology by not checking any bands
- If no bands are enabled, then the page will prompt you to specify
at least one band
- If many bands and technologies are selected, the gateway will
take a long time to scan for a tower

PAGE 15
WIRELESS NETWORK
Add Device to Network
This is an alternative way to add
devices to communicate with your
gateway. Any wireless device added
here will continue to display on your
iMonnit account. However, once you
have added one or more devices to
your gateway's network here, the
network should be reformed to inform
the gateway.
Device ID - This is a unique 6-digit
number located on the back label of
your device beside the QR code.
Security Code - A 6-letter code
beginning with "IM" located on the
back label of your device.
Slot Index - Optional text field to enter
the slot where your wireless device will
be stored can be between 1 - 256
characters.
Remove Device from Network
This is an alternative way to remove
devices from your gateway's network
so that they will no longer
communicate with your network.
However, once you have removed one
or more devices from your gateway's
network here, the network should be
reformed to inform the gateway.
Reform Network
Selecting the Reform Now button will
trigger the gateway to remove all of
the sensors from the internal whitelist,
and then request a new sensor list
from the server. This command will
force all of the sensors to reinitialize
their connection with the gateway.
Reforming the network cleans up communication when multiple networks are in range of each other so they are all in sync. This is
especially useful if you must move sensors to a new network, and would like to clear these sensors from the gateway?s internal list.
Reforming the network will place a new list of sensors that will continue to exchange data.
Create Network Backup and Restore Network Backup
Backup creates an export of the Network List in XML. Restoring the Network Backup takes the file and overrides the current Network
List results back to the previous settings pulled from an uploaded file.

CELLULAR PROVIDER INFORMATION REQUEST
IMPORTANT!
To customize any of the cellular settings in Manual Mode, the following questions must be answered
by your cellular provider:
- Does the cellular provider support LTE-M (CAT-M1) or NB-IoT (CAT-NB2)?
- If yes, do you use specific SIMs with these technologies?
- What LTE-M cellular bands should I use at my location?
- None, if not used or specify?
- What NB-IoT (NB2) Cellular Bands should I use at my location?
- None, if not used or specify?
- What APN should be used with this SIM/Network?
- Does the network support unspecified or network-provided APNs?
- Does this SIM support Authentication?
- If so,
- What is the type: PAP or CHAP?
- What is the username?
- What is the password?
PAGE 16
More detailed information can be found here.

ADVANCED CELLULAR TROUBLESHOOTING
Troubleshooting Setup
To set up the IoT Gateway for Advanced Cellular Troubleshooting:
- The SIM card must be placed in the SIM card holder in side the gateway
- The Ethernet interface must be connected
- The Connection Preferences must be either "Ethernet Preferred" or "Cellular Only"
- The HTTP Interface Settings must be "Enable" and "Always Available"
On "lte.htm," the following link can be selected to access the LTE Module Console Viewer "lcon.htm."
The LTE Module Console Viewer is the page where advanced cellular troubleshooting steps are executed. The page permits
commands to be sent directly to the cellular module and for responses to be displayed.
View of "lan.htm"
View of "lcon.htm"
PAGE 17

Steps for Troubleshooting
STEP COMMAND EXPECTEDRESULT
1+CPIN? +CPIN:READY
Result: The SIM is correctly installed and inserted.
2+GSN xxxxxxxxxxxxxxx
Result: The IMEI of the Module isreported.
3+CIMI xxxxxxxxxxxxxxx
Result: The IMSI of the SIM isreported.
4+QCCID +QCCID:xxxxxxxxxxxxxxxxxxxx
Result: The ICCID of the SIM is reported.
5+QPRTPARA=3 OK
Result: The Module will learn the BAND and APN settingsfrom the SIM card.
6+CFUN=1,1 OK
Result: Reboot the Module and apply the settings learned from +QPRTPARAcommand.
Note: The next command should run between 5 and 15 secondsafter this one.
7E0;+COPS=2;+CEREG=2 OK
Result: Halt Module,remove command echoes,and enable tower identification.
8+QCFG="band" +QCFG: "band",0x0,0x80a,0x80a
Result: Thisshows that Bands2,4,and 12 are recognized by the SIM by default.
Note: This isan AT&TExample. Other bandscan be decoded from the databelow.
If the results need to change,the command format isas follows:
+QCFG="band",0x0,<M BAND MASK>,<NBBAND MASK>
Example for setting Band 5 and 13:+QCFG="band",0x0,0x1010,0x1010
9+QCFG="iotopmode",0
or
+QCFG="iotopmode",1
or
+QCFG="iotopmode",2
OK
Result: Set Technology to:0 = M1 only (auto-default) ,1 = NBonly,2 = Both M1/NB2.
Note: Choose which command and send one only.
The following table outlines the commands and expected responses for each step of troubleshooting. If the result does
not match the expected, record the result and share with Monnit Technical Support ([email protected]). This
information is also helpful to identify the required settings to add automatic cellular provider support to future gateway
firmware. Record the command and results you get and share with Monnit Technical Support ([email protected]).
B1
0x1 B2 0x2 B3 0x4 B4 0x8
B5
0x10 B6 0x80 B12 0x800 B13 0x1000
B14
0x2000 B18 0x20000 B19 0x40000 B20 0x80000
B25
0x1000000 B26 0x2000000 B27 0x4000000 B28 0x8000000
B31
0x40000000 B66 0x20000000000000000 B71 0x400000000000000000 B72 0x800000000000000000
B73
0x1000000000000000000 B85 0x1000000000000000000000 All Bands(M) 0x400182000000000F0E389F All Bands(NB) 0x4001C2000000004E0E189F
PAGE 18