Monnit ALTA User manual

ALTA Wireless Sensors
and Ethernet Gateway
User’s Guide
For Use With iMonnit Online Software
and iMonnit Express PC Software
Wireless Ethernet Gateway Quick Start
• Create a Monnit user account with assigned wireless gateways and sensors.
• Attach the antenna to the antenna connector on the back panel of the Ethernet gateway
(make sure the connection is snug, but do not overtighten).
• Plug an Ethernet cable with internet connectivity into the gateway.
• Plug the power supply into a power outlet then connect to the gateway.
• Once all three lights turn green, your network is ready to bring sensors online.

I. CREATE AN IMONNIT USER ACCOUNT
If this is your rst time using the iMonnit online system site, you will need to create a new
account. If you have already created an account, you can skip to the “Logging into the
Online System” section. The following instructions will guide you through the account.
1. Open iMonnit in your mobile app or web browser.
2. Navigate your cursor down to the bottom of the login box and select “Add Account”.
3. Next you will be asked to enter your account information in the following elds.
Note: If this is a Free Trial, you may not have recieved a subscription code yet. Leave the box blank and proceed.
4. When completed, select the “Next” button.
5. This step will complete the user registration process and lead you into registering your
device. You will be able to log out and log back in with your credentials to complete the
setup at any time.
LOGGING INTO THE ONLINE SYSTEM
1. Open iMonnit in your mobile app or web browser.
2. Enter your user name and password.
3. Select the “Login” button.
REGISTERING THE DEVICE
1. You will need to enter the Device ID and the Security Code from your device in the text
boxes.
2. Use the camera on your smartphone to scan the QR code on your device.
3. If you do not have a camera on your phone, or the system is not accepting the QR code,
you may enter the Device ID and Security Code manually.
• The Device ID is a unique number logated on each device label. It will be labeled
as “ID” on your device.
• Next you’ll be asked to enter the Security Code (SC) on your device. A security
code will be all letters, no numbers. It can also be found on the barcode label of
your device.
4. When completed, select the “Submit” button.
PAGE 3PAGE 2

II. USING THE MONNITLINK ETHERNET GATEWAY
PAGE 4 PAGE 5
1. Understanding the Ethernet Gateway Lights
Front of Ethernet Gateway
1 2 3
Light 1 - Indicates the Ethernet cable is plugged in. A green light indicates ready
and working, a red light indicates there is a problem.
Light 2 - Indicates the Ethernet has internet connectivity and can reach the online
monitoring system. A green light indicates ready and working, a red light indicates
there is a problem. A ashing green light indicates network trafc to the internet.
Light 3 - Indicates sensor network activity. A green light indicates ready and work-
ing, a red light indicates there is a problem. A ashing green light indicates radio
trafc from the sensors.
For help troubleshooting Ethernet gateway lights view:
http://www.monnit.com/support/hardware/gateways/ethernet/troubleshooting-a-mon-
nitlink-ethernet-gateway
2. Ethernet Gateway Controls
RP SMA Antenna ConnectorEthernet PortPower Plug Control Button
Back Panel
Using the Control Button:
1) A short press will trigger the gateway to immediately send all stored sensor
messages to the online system and download any pending system messages
to deliver to the sensors. (The default heartbeat for the Ethernet gateway is 5
minutes.)
2) Press and hold to reset the gateway to factory settings. Factory settings will be
reset to defaults, including the heartbeat setting of 5 minutes on both the gateway
and in the online system. DHCP, server addressing and port are all restored to
default settings, for example. You will need to login to the online system after
resetting the gateway to recongure the gateway to your desired settings.
Note: If your gateway powers up with the lights scrolling from left to right, it has entered into boot loader
mode accidentally. Make sure the button is free from obstruction and reboot the gateway by removing the
power plug, waiting for 10 seconds then reinserting the power plug.
3. Conguring The Ethernet Gateway
The Ethernet Gateway collects data from all sensors within range and is precongured to
batch deliver the sensor messages to the online system every 5 minutes.
The Ethernet Gateway uses DHCP (Dynamic Host Conguration Protocol) to
automatically acquire a network address from the LAN (Local Area Network). In the
event that it needs to have an address manually assigned to it, you can assign an IP
address as well as a gateway mask and default DNS through the online interface. For
more information on conguring the Monnit Ethernet Gateway please view the support
documentation at http://www.monnit.com/pdf/Ethernet_Gateway_Conguration.pdf.
Note: This advanced conguration is NOT required in most instances. In the event that it is required, you can initialize
the gateway on a network that uses the default DHCP settings, or you can follow the instructions for changing the
conguration settings on a PC, which are included later in this User’s Guide.
Upon logging into the online system as an administrator, select “My Account” then choose
the edit icon next to your sensor network. From there you can alter the heartbeat of the
Ethernet Gateway as well as edit any other congurations available. There is also a
quick link to reset all gateway settings to factory defaults.
4. Insert Batteries Into Wireless Sensors
Important: Make sure your sensors are at least 3ft. away from the wireless sensor
adapter.
Insert batteries into commercial type sensors or use switch on industrial type sensors to
power them on.
Note: It will take 10 - 20 seconds for the sensor to power up. Congurations for your sensors can be changed in
iMonnit. Your new modications will take effect on the next heartbeat. More immediate results can be achieved
by power cycling the sensor. Power cycling is accomplished by removing then re-inserting batteries or using the
power switch to cycle the power.

III. USING THE IMONNIT ONLINE WIRELESS SENSOR SYSTEM
UNDERSTANDING THE ONLINE INTERFACE
When you log into the online system, the default view shows all of your sensors last
recorded data.
Menu System
Details - Displays a graph of recent sensor data.
History - List of all past hearbeats and readings.
Events - List of all events attached to this sensor.
Settings - Editable levels for your sensor.
Calibrate - Reset readings for select sensors (Not available for all sensor types).
Scale - Change the scale of readings for your sensor (Not available for all sensor types).
Sensor Overview
Directly under the tab bar is an overview of your sensor. This allows you to see the signal
strength and the battery level of the selected sensor.
• inticates the sensor is checking in and within user dened safe parameters.
• indicates the sensor has met or exceeded a user dened threshold or triggered event.
• indicates that no sensor readings are being recorded, rendering the sensor inactive.
Note: The data shown on the chart, event, history, and export le is based on the date range indicated on the
upper right side of the sensor detail information. To change the date range, click the inside of the date box.
HISTORY VIEW
Clicking on the “History” tab within the tab bar allows you to view the sensor’s data history
as time stamped data.
PAGE 7PAGE 6

CONFIGURING SENSOR SETTINGS
To edit the operational settings for a sensor, choose the “Sensor” option in the main navigation
menu then select the “Settings” tab to access the conguration page.
The sensor edit panel allows you to set the primary congurations for the sensor. When you
have nished making changed, press the “Save” button at the bottom of this section.
Note: Be sure to select the “Save” button anytime you make a change to any of the sensor parameters. All changes
made to the sensor settings will be downloaded to the sensor on the next sensor heartbeat (check-in). Once a
change has been made and saved, you will not be able to edit that sensor’s conguration again until it has down-
loaded the new setting.
SENSOR AND/OR GATEWAY NOTIFICATION(S)
Notications for a single sensor or gateway can be created, deleted, and edited by clicking
the “Events” tab in the senor tab bar.
You can toggle the Event Trigger on or off by selecting the switch under Current Event
Triggers.
Creating an Event
Events are triggers or alarms set to let you know when a sensor reading identies that
immediate attention is needed. Types of events include sensor readings, battery level,
device inactivity, and scheduled data. Any one of these can be set to send a notication
or trigger an action in the system. This guide will walk you through creating two types
of events. First a sensor reading notication for a temperature sensor, then an inactivity
notication congured for all sensors.
1. Select Events in the main navigation menu.
2. A list of previously created events will display on the screen. From here, you have the
ability to lter, refresh, and add new events to the list.
Note: If this is your rst time adding an event, the screen will be blank. PAGE 9
PAGE 8

3. From the Events page, tap “Add Event” in the left hand corner.
4. The dropdown menu will have the following options for Event Types:
• Sensor Reading: Set alerts based
on sensor activity or reading.
• Battery Level: This is where you can
set to be notied whend the battery
level drops below a percentage. 15%
is the default setting.
• Device Inactivity: Alerts when the
device doesn’t communicate for an
extended period of time.
• Advanced: Alerts based on
advanced rules, such as comparing
past data points with current ones.
• Scheduled: These are notications
that re at a time set basis.
5. Select Sensor Reading from the dropdown menu.
6. A second dropdown menu will appear. From here, you will be able to see a list of the
different type of sensors registered to your account. Choose Temperature in the dropdown
menu.
7. Next, you will be asked to input the trigger
settings. You have the option of setting this trigger
for greater than or less than a temperature reading
8. Press the “Save” button.
If you don’t have a temperature sensor, the option in this
example won’t be available, select any variable output
sensor and follow along.
Variable output sensors can have multiple event triggers
created.
Example: A temperature sensor used in a freezer.
You may want to be notied if the temperature goes
below 0° or above 30° Fahrenheit. You would create
two events.
• Event 1- Trigger Set for temperatures LESS THAN
0°F.
• Event 2 - Trigger set for temperatures GREATER
THAN 30° F.
9. The Event Information page has a series of tabs across the top.
A. History: A table of all past alert notications for this specic event.
B. Schedule: Here you can schedule the event only to be active at certain times or
certain days.
C. Trigger: This is where you can review your trigger settings.
D. Actions: Where you set the action you want to happen when an alert state is
triggered.
10. Choose the Trigger tab.
11. The Trigger Sensors section sits below “Trigger Conditions.” If you have multiple
sensors for the same type (Example: ve temperature sensors), this is where they will be
listed. There should be at least one sensor in this section.
12. By default, the sensor(s) will not be assigned to the event conditions you’ve just set. To
assign a sensor, nd the device(s) you want to designate for this event and select. Selected
sensor boxes will turn green when activated. Choose the sensor box again to unassign the
sensor from the event.
13. Continue toggling the sensor(s) corresponding to this new event until you are satised
with your selection. These can be adjusted later by returning to this page.
14. Press the “Save” button.
15. Select the Actions tab.
16. Press the Add Action button under the Event Information header and available action
types are presented in a select list.
• Notication Action: Specify account users to recieve notications when this event
triggers.
• System Action: Assign actions for the system to process when this event triggers.
17. Choose Notication Action from the notication list.
PAGE 10 PAGE 11

A. Congure the subject for the notication.
B. Customize the message body.
C. Save button commits any changes to message
content elds.
D. Recipient list identies who will recieve the
notication.
• Select the icon next to a user to congure
how they will be notied
• Choose if you want notications sent
immediately when triggered or if you want
a delay before it is sent and press Set.
• A green icon indicates the users that will
not recieve the notications.
• If a delay has been selected, the delay
time will display beside the icon.
18. Select System Action from the select list under the Event Information header.
19. Scroll down to the System Action section.
20. The Action to be Done select list has the
following options.
• Acknowledge: Automatically signal
that you have been notied of an
event and take action. When an
event has been triggered, actions will
continue processing until the event
returns to a value that no longer
triggers an event.
• Full Reset: Reset your trigger so it
is armed for the next reading.
• Activate: Enable an event trigger.
• Deactivate: Disable an event trigger.
EXPORTING SENSOR DATA
1. Select Sensors from the main navigation menu.
2. Choose the sensor you need an export for in the list.
3. Pick the History tab.
4. On the far right of the sensor history data is a cloud icon. Selecting this icon will
export an excel le for your sensor into your download folder.
Note: Make sure you have the date range for the data you need input in the “From” and “To” text boxes. This will be
the most recent week by default. Only the rst 2,500 entries in the selected date range will be exported.
The data le will have the following elds:
MessageID: Unique identier of the message in our database.
SensorID: If multiple sensors are exported you can distinguish which reading was from
which using this number even if the names for some reason are the same.
Sensor Name: The name you have given the sensor.
Date: The date the message was transmitted from the sensor.
Value: Data presented with transformations applied but without additional labels.
Formatted Value: Data transformed and presented as it is shown in the monitoring portal.
Battery: Estimated life remaining of the battery.
Raw Data: Raw data as it is stored from the sensor.
Sensor State: Binary eld represented as an integer containing information about the state
or the sensor when the message was transmitted. (See “Sensor State Explained” below).
Gateway ID: The Identier of the gateway that relayed the data from the sensor.
Alert Sent: Boolean indicating if this reading triggered a notication to be sent from the
system.
Signal Strength: Strength of communication signal between the sensor and the gateway,
shown as percentage value.
Voltage: Actual voltage measured at the sensor battery used to calculate battery percent-
age, similar to Received Signal you can use one or the other or both if they help you.
State
The integer presented here is generated from a single byte of stored data. A
byte consists of 8 bits of data that we read as Boolean (True (1)/False (0)) elds.
PAGE 13PAGE 12

Using a temperature sensor as an example.
If the sensor is using factory calibrations the Calibrate Active eld is set True (1) so the bit
values are 00010000 and it is represented as 16.
If the sensor is outside the Min or Max threshold, the Aware State is set True (1) so the bit
values are 00000010 and it is represented as 2.
If the customer has calibrated the sensor this eld the Calibrate Active eld is set False
(0) AND the sensor is operating inside the Min and Max Thresholds, the bits look like
00000000 this is represented as 0.
If the sensor is using factory calibrations and it is outside the threshold the bit values are
00010010 and it is represented as 18 (16 + 2 because both the bit in the 16 value is set
and the bit in the 2 value is set).
Note: These two are the only bits that typically observed outside of our testing procedures.
CALIBRATING SENSOR DATA
Certain wireless sensors can be calibrated for more accurate readings (Example: For
Temperature sensors). If calibration is possible for a sensor, the “Calibrate” tab will be
visible in the tab bar.
A. Go to the tab to open the sensor calibration settings window.
B. To calibrate a sensor, you will want to ensure that the environment of the sensor and
other calibration device is stable. Note the “Expected Next Check-in” time for the sensor
you are calibrating and take a reading from your calibration device a few minutes prior to
the sensors next check-in.
C. Enter the actual (accurate) reading from the calibration device into the text eld.
D. If you need to change the unit of measurement you can do that here.
E. Press “Calibrate”.
To ensure that the calibration command is received prior to the sensors next check-in,
press the control button on the back of the gateway, once, to force communication (Cellular
and Ethernet gateways).
After pressing the "Calibrate" button and choosing the gateway button, the server will send
the command to calibrate the specied sensor to the gateway. When the sensor checks-in,
it will send the pre-calibration reading to the gateway, then receive the calibration command
and update it’s conguration. When the process is completed, it will send a “Calibration
Successful” message. The server will display the sensor’s last pre-calibrated reading for
this check-in, then all future readings from the sensor will be based on the new calibration
setting.
It is important to note that after calibrating the sensor, the sensor reading returned to the
server is based on pre-calibration settings. The new calibration settings will take affect on
the next sensor heartbeat.
Note: If you would like to send the changes to the sensor right away, please remove the battery(s) for a full 60
seconds, then re-insert the battery(s). This forces the communication from the sensor to the gateway and this the
message to make a change from the gateway back to the sensor. (If the sensors are industrial sensors, turn the
sensor off for a full minute, rather than removing the battery).
MANAGE SENSOR NETWORKS
To view or edit information about your wireless sensor network(s), select the Networks box
in the account overview page.
The following network list page allows you to edit details, create new sensor tetworks, and
manage wireless gateways and sensors for your network(s). Find the network you wish to
modify in the list and select it to be taken to to the network edit page.
The network edit page will give the option of
changing the name of your network, enable
notications, enable holding, and review the
Install Tech Access Cut-off Date.
Remember, you must press the “Save”
button after making any changes in this
section.
Below this section is a list of sensors and
gateways attached to the account. Choosing
the icon of a trashcan beside each sensor
will delete it from the network. Selecting
the icon directly above the sensor section
will allow new devices to be added to the
network. Review the steps on registering a
new device on page 3 of this user guide.
Note: A sensor or gateway cannot be recovered once it
has been deleted from the network. It is reccomended that
you export a sensor’s data history before clearing it from
the list.
PAGE 14 PAGE 15

PAGE 17PAGE 16
V. Advanced Settings and Interfacing with the Monnit Ethernet
Gateway Through iMonnit.
1. Navigate to the main menu and select “Gateways.”
When you enter the gateway page, you will see all the gateways registered to your account.
The settings for any of these can be adjusted and edited by choosing the gateway you wish
to edit.
2. Choose the Enterprise Gateway.
The page will open to the history tab. This is where you can view all previously recorded
data for the Enterprise Gateway.
3. Select the “Settings” tab.
General Settings will be the rst elds open for
editing. The gateway name can be changed
to whatever you prefer. The heartbeat and poll
rate minutes are also adjustable here. This will
automatically be set to force transmit on an Aware
State. The heartbeat is the interval in minutes
when your Enterprise Gateway communicates
with the server. Exceptions to this include Aware
State messages received from your sensors.
Remember to press the “Save” button after
making your changes or they will not take effect.
The Local Area Network is where you can view the MAC
Address and change your IP Address. Your IP Address
will be set to “Dynamic” by default. To set it to “Static”
drag the switch to the left, then ll in the text boxes for
Static IP, Nework Mask, Default Gateway, and Default
DNS Server. Then press the “Save” button.
Interface Activation is where SNMP, Modbus, and Real Time TCP Interfaces can be activated.
Upon activation, setttings for these will appear in the above menu. Multiple interfaces can be
active at one time. All interfaces require the DHCP to set to a static IP address.
Real Time TCP Interface
Poll on the gateway’s assigned port to retrieve gateway and sensor data. The default port is
3500, but can be edited.
Modbus TCP Interface
Use Modbus TCP software to pull in gateway and sensor data. Monnit provides a register
map. The Modbus TCP Interface will store all data values in 16-bit registers. The registers
and their data elds are mapped below:
Field Description Register Data
Address
GATEWAY Gateway ID_High The rst 16 bytes of a 32 byte
serial ID number
40001 0
REGISTERS Gateway ID_Low The last 16 bytes of a 32 bytes
serial ID number
40002 1
Gateway Version The version of gateway
rmware on the device
40003 2
Gateway Device
Count
The number of devices (sensors &
gateways) in its network
40004 3
SENSOR Sensor ID_High The rst 16 bytes of a 32 byte
serial ID number
40101 100
REGISTERS Sensor ID_Low The last 16 bytes of a 32 bytes
serial ID number
40102 101
Device Type The unique type identier for the
sensor prole
40103 102
Data Age The number of seconds that have
elapsed since the last data was
retrieved
40104 103
Is Device Active 0 indicates no data for this slot 40105 104
Is Aware Becomes aware when a sensor
threshold has been breached
40106 105
Voltage Battery voltage 40107 106
RSSI Signal Strength indicator
0-100%
40108 107

Data 1 Sensor Data Field 1 40109 108
Data 2 Sensor Data Field 2 40110 109
Data 3 Sensor Data Field 3 40111 110
Data 4 Sensor Data Field 4 40112 111
Data 5 Sensor Data Field 5 40113 112
Data 6 Sensor Data Field 6 40114 113
Data 7 Sensor Data Field 7 40115 114
Data 8 Sensor Data Field 8 40116 115
SNMP Poll and Trap Interface
Use SNMP software to pull in gateway and sensor data. Monnit provides a .MIB le. There
are four available interfaces. Set the SNMP Interface Address for each one the address of
the device sending the SNMP request). Mark the interface Active and Save.
The MIB le is available through here:
resources.monnit.com/content/downloads/MonnitEGW-MIB_v1
Ethernet Gateway MIB tree with a short description of each eld:
EGW Data Description
*GW Section Gateway Section
*GW Serial Gateway Serial ID
*Version Gateway Firmware Version
*WD Count Wireless Device Count
*WNetSection Wireless Network Seciont
*WD Entry Wireless Device Entry
*Index Index Number
*Serial Wireless Device Serial ID
*Type Device Type (eg temp, water, motion sensor, etc)
*Age Number of seconds since last data recording
*Active Indicates if the wireless device is reporting in as expected
*Alarming Indicates if the wireless device has detected data that is urgent or
breaches a threshold
*Voltage Battery voltage recorded at the time of data reading
*RFSignal Signal Strength recorded on data reading delivery
*Data1 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data2 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data3 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data4 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data5 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data6 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data7 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)
*Data8 Data recorded by wireless device (eg temperature, water detect-
ed, motion detected, etc)