ALTA GS-H2S Wireless Hydrogen Sulfide Sensor User Guide

GS-H2S Wireless Hydrogen Sulfide Sensor
User Guide

ABOUT THE WIRELESS H²S SENSOR

ALTA Wireless Hydrogen Sulfide (H2S) Sensors monitor the presence of toxic gas in the atmosphere. Combined with the iMonnit Online System, the sensor will deliver up-to-date readings to notify you the second gas levels breach a set threshold. Readings can be viewed online through graphs and downloadable spreadsheets. Event notifications can be set in iMonnit through the easy-to-use online interface available on mobile devices.

ALTA WIRELESS H2S SENSOR FEATURES

• Wireless range of 1,200+ feet through 12+ walls *

• Frequency-Hopping Spread Spectrum (FHSS)

• Interference immunity

• Power management for longer battery life **

• Encrypt-RF® Security (Diffie-Hellman Key Exchange + AES-128 CBC for sensor
  data messages)

• Onboard data memory stores up to hundreds of readings per sensor:
  – 10-minute heartbeats = 22 days
  – 2-hour heartbeats = 266 days

• Over-the-air updates (future proof)

• Free iMonnit basic online wireless sensor monitoring and notification system to configure sensors, view data, and set alerts via SMS text and email

• Actual range may vary depending on the environment.
  ** Battery life is determined by sensor reporting frequency and other variables. Other power options are also available.

EXAMPLE APPLICATIONS

• Crude oil production
• Natural gas production
• Wastewater treatment
• Utility facilities
• Sewers
• Additional applications

ORDER OF OPERATIONS

It is important to understand the order of operations for activating your sensor. If performed out of sequence, your sensor may have trouble communicating with iMonnit.  Please perform the steps below in the order indicated to make sure you are performing your set-up correctly.

1. Create an iMonnit Account (If new user).

2. Register all sensors and gateways to a network in iMonnit.
   Sensors can only communicate with gateways on the same iMonnit network.

3. Connect/power on the gateway and wait till it checks into iMonnit.

4. Power on the sensor and verify it checks into iMonnit.
   We recommend powering the sensor near the gateway then moving to the installation location, checking signal strength along the way.

5. Configure sensor for use (This can be done at any point after step 2)

6. Install the sensor in the final location.

Note: For information on setting up iMonnit and the gateway refer to the iMonnit User Guide and the gateways user guide.
Note: Device-specific setup is covered in more detail in the following sections.

SETUP AND INSTALLATION

If this is your first time using the iMonnit online portal, you will need to create a new account. If you have already created an account, start by logging in. For instructions on how to register and set up your iMonnit account, please consult the iMonnit User Guide.
STEP 1: ADD DEVICE

1. Add the sensor on iMonnit.
   Add the sensor to your account by choosing Sensors in the main menu.
   Navigate to the Add Sensor button.

2. Find the device ID. See Figure 1.
   The Device ID (ID) and Security Code (SC) are necessary to add a sensor.
   These can both be located on the label on the side of your device.

3. Adding your device. See Figure 2.
   You will need to enter the Device ID and the Security Code from your Sensor in the corresponding text boxes.
   Use the camera on your smartphone to scan the QR code on your device. 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 located on each device label.
   • Next, you’ll be asked to enter the Security Code from your device. A security code consists of letters and must be entered in upper case (no numbers). It can also be found on the barcode label of your device.
   When completed, select the Add Device button.

STEP 2: SETUP
Select your use case. See Figure 3.
Unlike most sensors, choosing a use case in Step 2 of adding this sensor does not give you the option to customize your settings.
These will need to be adjusted in the settings tab for your device. See page 9 for instructions.
Select the Skip button when completed.

STEP 3: VALIDATION
Check your signal. See Figure 4.
The validation checklist will help you ensure your sensor is communicating with the gateway properly and you have a strong signal.
Checkpoint 4 will only complete when your sensor achieves a solid connection to the gateway. Once you insert the batteries (or flip the switch on an industrial sensor) the sensor will communicate with the gateway every 30 seconds for the first few minutes.
Select the Save button when completed.

STEP 4: ACTIONS
Choose your actions. See Figure 5.
Actions are the alerts that will be sent to your phone or email in the event of an emergency. Low battery life and device inactivity are two of the most common actions to have enabled on your device.
See page 12 for how to set actions for your sensor.
Select the Done button when completed.

SETTING UP YOUR H²S SENSOR

When you are finished adding the sensor to your account, the next step is to insert the battery. The type of battery you use will depend on the category of your sensor. ALTA Wireless H2S Sensors are powered by AA batteries.

INSTALLING BATTERIES
ALTA commercial sensors are powered by AA batteries. Monnit encourages customers to recycle all old batteries.

The standard version of this sensor is powered by two replaceable 1.5 V AA- sized batteries (included with purchase). The typical battery life is up to 10 years.
This sensor is also available with a line power option. The line-powered version of this sensor has a barrel power connector allowing it to be powered by a standard 3.0?3.6 V  power supply. The line-powered version also uses two standard 1.5 V AA batteries as backup for uninterrupted operation in the event of a line power outage.
Power options must be selected at the time of purchase, as the internal hardware of the sensor must be changed to support the selected power requirements.

Place batteries in the device by first taking the sensor and sliding the battery door open.
Insert fresh AA batteries in the carriage, then shut the battery door.
Complete the process by opening up iMonnit and selecting Sensors from the main navigation menu. Verify that iMonnit is showing the sensor has a full battery level.

ANTENNA ORIENTATION
In order to get the best performance out of your ALTA Wireless Sensors, it is important to note proper antenna orientation and sensor positioning. Antennas should all be oriented in the same direction, pointing vertically from the sensor. If the sensor is mounted flat on its back on a horizontal surface, you should bend the antenna as close to the sensor housing as possible giving you the most amount of antenna pointing vertically. You should make the antenna wire as straight as possible, avoiding any kinks and curving of the wire. Sensors must be at least 3 ft. away from other sensors and the wireless gateway to function.

SENSOR OVERVIEW IN iMONNIT

Select Sensors from the main navigation menu on iMonnit to access the sensor overview page and begin making adjustments to your Hydrogen Sulfide Sensor.

MENU SYSTEM

A. Details – Displays a graph of recent sensor data
B. History – List of all past heartbeats and readings
C. Events – List of all events attached to this sensor
D. Settings – Editable levels for your sensor
E. Calibrate – Set your sensor to read more accurately
F. Scale – Change the scale of readings for your sensor

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. A colored dot in the left corner of the sensor icon denotes its status.

• Green indicates the sensor is checking in and within user-defined safe parameters.
• Red indicates the sensor has met or exceeded a user-defined threshold or triggered event.
• Gray indicates that no sensor readings are being recorded, rendering the sensor inactive.
• Yellow indicates that the sensor reading is out of date, due to perhaps a missed heartbeat check-in.

Details View
The Details View will be the first page you see upon selecting which sensor you would like to modify.

A. The sensor overview section will be above every page. This will consistently display the present reading, signal strength, battery level, and status.
B. The Recent Readings section below the chart shows your most recent data received by the sensor.
C. This graph charts how the sensor fluctuates throughout a set date range. To change the date range displayed in the graph, navigate up to the top of the Readings Chart section in the right-hand corner to change the form and/or to date.

Readings View
Selecting the Readings Tab within the tab bar allows you to view the sensor’s data history as time-stamped data.

• On the far right of the Sensor History Data is a cloud icon. ( ) Selecting this icon will export an Excel file 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 previous day by default. Only the first 2,500 entries in the selected date range will be exported.

The data file will have the following fields:
MessageID: Unique identifier of the message in our database.
Sensor ID: If multiple sensors are exported, you can distinguish between the sensors using this number? even if the names 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.
Raw Data: Raw data as it is stored from the sensor.
Sensor State: Binary field is represented as an integer containing information about the state of the sensor when the message was transmitted. (See ? Sensor State? explained below.)
Alert Sent: Boolean indicating if this reading triggered a notification to be sent from the system.

Sensor State
The value 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)) fields.
When broken into individual bits, the State byte contains the following information: aaaabcde
STS: This value is specific to the sensor profile and is often used to indicate error states and other sensor conditions.
UNUSED: This sensor does not use these bits.
AWARE: Sensors become aware when critical sensor-specific conditions are met. Going aware can cause the sensor to trigger and report before the heartbeat and cause the gateway to forward the data to the server immediately resulting in near-immediate transmission of the data.
TEST: This bit is active when the sensor is first powered on or reset and remains active for the first 9 messages when using default configurations.
STS Specific Codes:
0 = No problems, the sensor is functioning normally.
1 = Open circuit detected in lead.
2 = Short circuit detected in lead.
3 = Range error. Temperature is reading outside of -40 F and 257 F (-40 C and 125 C).

If the user has calibrated the sensor, the Calibrate Active field is set to 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 are represented as 18(16+2 because both the bit in the 16 value is set and the bit in the 2 value is set).
Settings View
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 configuration page.

A. Sensor Name is a unique name you give the sensor to easily identify it in a list and in any notifications.
B. The Heartbeat Interval is how often the sensor communicates with the gateway if no activity is recorded.
C. Aware State Heartbeat is how often the sensor communicates with the gateway while in an Aware State.
D. Below is the minimum reading the sensor should record before entering an Aware State.
E. Above is the maximum reading the sensor should record before entering an Aware State.
F. The Aware State Buffer is a buffer to prevent Standard Operation and Aware State when the sensor from bouncing between assessments are very close to a threshold. For example, if a Maximum Threshold is set to 90° and the buffer is 1°, once the sensor takes an assessment of 90.1° it will remain in an Aware State until dropping to 89.0°.
The default heartbeat interval is 120 minutes or two hours. It is recommended that you do not lower your heartbeat level too much because it will drain the battery.
Finish by selecting the Save button.

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 configuration again until it has downloaded the new setting.

Calibrate View

If a sensor type has readings that need to be reset, the ? Calibrate? tab will be available for selection in the sensor tab bar.
To calibrate a sensor, ensure that the environment of the sensor and other calibration devices are stable. Enter the actual (accurate) reading from the calibration device into the text field. If you need to change the unit of measurement you can do that here.
Press Calibrate.

To ensure that the calibration command is received prior to the sensor’s 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 specified 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 configuration. 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 effect 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).

Creating a Calibration Certificate
Creating a sensor calibration certificate will mask the calibration tab from those who should not have permission to adjust these settings. Permissions for self-certifying a  calibration must be enabled in user permissions.
Directly below the calibrate button is the selection to “Create Calibration Certificate.

A. The Calibration Facility Field will be filled. Select the dropdown menu to change your facility.
B. The?Certificate Valid Until? the field must be set one day after the data contained in the “Date Certified” field.
C. “Calibration Number” and “Calibration Type” are unique values to your certificate.
D. If necessary, you can reset the heartbeat interval here to 10 minutes, 60 minutes, or 120 minutes. By default, this will be set to no change.
E. Choose the “Save” button before moving on.

Calibration for your H2S Sensor is done in three steps. It’s important to perform these steps in the order indicated.

1. Zero Calibration: Press the zero button. Keep the sensor in the 0 PPM environment and wait for a full two data points to come in after this command is accepted(red x on status icon clears) for this process to complete, don’t send any other calibration or configuration changes before this process completes. After this step is complete the sensor should read near 0 ppm.
2. H2S Span Calibration: This step calibrates the sensor according to a ppm reading above 100 ppm. It is recommended to calibrate the sensor in an environment above the maximum expected H2S concentration in the environment. This step is complete as soon as the red x clears.
3. Temperature Calibration: Submit actual Temperature Once these steps are complete, choose the ? Calibrate? button.
   When the new certificate is accepted, the Calibration tab will change to a Certificate tab.

You will still be able to edit the certificate by choosing the Certificate Tab and navigating down to “Edit Calibration Certificate.”
The tab will revert back to “Calibrate” after the period for the certificate ends.

Scale View

If the sensor settings are influenced by temperature, the scale option will be available in the tab bar. To change the temperature unit of measurement from Fahrenheit to Celsius or vice versa, select the Scale tab.
Choose the text box to trigger a pop-up window allowing you to change the scale. Select the scale you prefer and push? Set.? Press the? Save? button to complete your adjustment.
Changing units here will also change units on the sensor physical display. Units changed locally on the sensor itself will not be changed in this setting in iMonnit.

ACTIONS OVERVIEW

Device notifications can be created, deleted, and edited by selecting the Actions Tab in the tab bar.
You can toggle the Action Trigger on or off by selecting the switch under Current Action Triggers. See Figure 16.

CREATING AN ACTION

• Actions are triggers or alarms set to notify you when a sensor reading identifies that immediate attention is needed. Types of actions include sensor readings, device inactivity, and scheduled data. Any one of these can be set to send a notification or trigger an action in the system.

Choose Actions in the main navigation menu.

• A list of previously created actions will display on the screen. From here, you have the ability to filter, refresh, and add new actions to the list.

Note: If this is your first time adding an action, the screen will be blank.
From the Actions page, tap Add Action in the left-hand corner.

Step 1: What triggers your action?
The drop-down menu will have the following options for Action Types (See Figure 19):

• Sensor Reading: Set actions based on activity or reading.
• Device Inactivity: Actions when the device doesn’t communicate for an extended period of time.
• Advanced: Actions based on advanced rules, such as comparing past data points with current ones.
• Scheduled: These actions are performed on a time-set basis.
• Select Sensor Reading from the drop-down menu.
• A second drop-down menu will appear. From here, you will be able to see a list of the different types of sensors registered to your account. Choose H2S Meter in the drop-down menu.
•  Next, you will be asked to input the trigger settings. You have the option of setting this trigger to detect greater than or less than the desired reading.

Press the Save button.

Step 2: Actions

• Press the Add Action button under the information header, available action types will then be presented in a select list.
• Notification Action: Specify account users to receive a notification when this event triggers.
• System Action: Assign actions for the system to process when this event triggers.
• Choose Notification Action from the notification list.

|
---|---

A. Input the subject for the notification. See Figure 21.
B. Customize the message body for the notification. See Figure 21.
C. Recipient list identifies who will receive the notification. See Figure 22.

• Select the icon next to a user to specify how they will be notified.
• Choose if you want notifications sent immediately when triggered, or if you want a delay before sending and press Set.
• A green icon indicates the users that will receive the notifications.
• If a delay has been selected, the delay time will display beside the icon.

Select System Action from the Add Action list. See Figure 23

• Scroll down to the System Action section.
• The Action to be done select list has the following options:

Acknowledge: Automatically signals that you have been notified of an action.
When an action has been triggered, alerts will continue processing until the action returns to a value that no longer triggers an action.
Full Reset: Reset your trigger so it is armed for the next reading.
Activate: Enable an action trigger.
Deactivate: Disable an action trigger.

Step 3: Action Name and Devices

• By default, the sensor(s) will not be assigned to the action conditions you?ve just set. To assign a sensor, find the device(s) you want to designate for this action and select.
  Selected sensor boxes will turn green when activated. Choose the sensor box again to unassign the sensor from the action. See Figure 24.

• Continue toggling the sensor(s) corresponding to this new action until you are satisfied with your selection.
  These can be adjusted later by returning to this page.

Press the Check-mark button to complete the process.

SECURITY

Data security and integrity is paramount at Monnit. Each layer of the system is secured using encryption and protocols designed to protect customer data and information. The system consists of a sensor(s), gateway(s), and iMonnit software. One or more sensors communicate with iMonnit software through a gateway.

SENSOR TO GATEWAY
Sensor and gateway radio modules are purpose-built devices with proprietary unreadable firmware, which means the sensor cannot be physically hacked or re- purposed for malicious purposes. This adds a strong level of inherent security even before considering encryption. Data transmission between the sensor and gateway are secured using Encrypt-RF Security (Diffie-Hellman Key Exchange + AES-128 CBC for sensor data messages). Beyond the encryption, data transmissions are also structurally verified and CRC checked before they are passed up to iMonnit or down to the sensor, this ensures the integrity of the data itself.
GATEWAY TO IMONNIT
Data transmissions between the gateway and iMonnit software are secured using 256-bit, bank-level encryption.
Monnet
Access is granted through the iMonnit user interface or an Application
Programming Interface (API) safeguarded by 256-bit Transport Layer Security (TLS 1.2) encryption. TLS is a blanket of protection to encrypt all data exchanged between iMonnit and you. The same encryption is available to you whether you are a Basic or Premiere user of iMonnit. You can rest assured that your data is safe with iMonnit.
SENSOR PRINTS
Sensor prints utilize a shared key between the software and the sensor to ensure that once the data comes to iMonnit it is guaranteed to be from the device identified by the sensor print. If this feature is purchased for the device (via iMonnit software) the device’s data becomes impossible to spoof by any malicious device.

SUPPORT

For technical support and troubleshooting tips please visit our support library online at monnit.com/support/. If you are unable to solve your issue using our online support,  email Monnit support at support@monnit.com with your contact information and a description of the problem and a support representative will call you within one business day.
For error reporting, please email a full description of the error to support@monnit.com.

WARRANTY INFORMATION

a. Monnit warrants that Monnit-branded products (Products) will be free from defects in materials and workmanship for a period of one (1) year from the date of delivery with respect to hardware and will materially conform to their published specifications for a period of one (1) year with respect to software. Monnit may resell sensors manufactured by other entities and are subject to their individual warranties; Monnit will not enhance or extend those warranties. Monnit does not warrant that the software or any portion thereof is error Monnit will have no warranty obligation with respect to Products subjected to abuse, misuse, negligence or accident. If any software or firmware incorporated in any Product fails to conform to the warranty set forth in this Section, Monnit shall provide a bug fix or software patch correcting such non-conformance within a reasonable period after Monnit receives from Customer (i) notice of such non-conformance, and (ii) sufficient information regarding such non-conformance so as to permit Monnit to create such bug fix or software patch. If any hardware component of any Product fails to conform to the warranty in this Section, Monnit shall, at its option, refund the purchase price less any discounts, or repair or replace nonconforming Products with conforming Products or Products having substantially identical form, fit, and function and deliver the repaired or replacement Product to a carrier for land shipment to the customer within a reasonable period after Monnit receives from Customer (i) notice of such non- conformance, and (ii) the non-conforming Product provided; however, if, in its opinion, Monnit cannot repair or replace on commercially reasonable terms it may choose to refund the purchase price. Repair parts and replacement Products may be reconditioned or new. All replacement Products and parts become the property of Monnit. Repaired or replacement Products shall be subject to the warranty, if any remains, originally applicable to the product repaired or replaced. The customer must obtain from Monnit a Return Material Authorization Number (RMA) prior to returning any Products to Monnit. Products returned under this Warranty must be unmodified.

Customers may return all Products for repair or replacement due to defects in original materials and workmanship if Monnit is notified within one year of the customer’s receipt of the product. Monnit reserves the right to repair or replace Products at its own and complete discretion. The customer must obtain from Monnit a Return Material Authorization Number (RMA) prior to returning any Products to Monnit. Products returned under this Warranty must be unmodified and in original packaging. Monnit reserves the right to refuse warranty repairs or replacements for any Products that are damaged or not in original form. For Products outside the one-year warranty period, repair services are available at Monnit at standard labor rates for a period of one year from the Customer’s original date of receipt.

b. As a condition to Monnit’s obligations under the immediately preceding paragraphs, the Customer shall return Products to be examined and replaced to Monnit’s facilities, in shipping cartons that clearly display a valid RMA number provided by Monnit. The customer acknowledges that replacement Products may be repaired, refurbished or tested and found to be complying. The customer shall bear the risk of loss for such return shipment and shall bear all shipping costs. Monnit shall deliver replacements for Products determined by Monnit to be properly returned, shall bear the risk of loss and such costs of shipment of repaired Products or replacements, and shall credit the Customer’s reasonable costs of shipping such returned Products against future purchases.

c. Monnit’s sole obligation under the warranty described or set forth here shall be to repair or replace nonconforming products as set forth in the immediately preceding paragraph, or to refund the documented purchase price for non-conforming Products to the Customer. Monnit’s warranty obligations shall run solely to the Customer, and Monnit shall have no obligation to customers of the Customer or other users of the Products.

Limitation of Warranty and Remedies.
THE WARRANTY SET FORTH HEREIN IS THE ONLY WARRANTY APPLICABLE TO PRODUCTS PURCHASED BY CUSTOMERS. ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. MONNIT’S LIABILITY WHETHER IN CONTRACT, IN TORT, UNDER ANY WARRANTY, IN NEGLIGENCE, OR OTHERWISE SHALL NOT EXCEED THE PURCHASE PRICE PAID BY THE CUSTOMER FOR THE PRODUCT. UNDER NO CIRCUMSTANCES SHALL THE MONITOR BE LIABLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES. THE PRICE STATED FOR THE PRODUCTS IS A CONSIDERATION IN LIMITING MONNIT’S LIABILITY. NO ACTION, REGARDLESS OF FORM, ARISING OUT OF THIS AGREEMENT MAY BE BROUGHT BY CUSTOMER MORE THAN ONE YEAR AFTER THE CAUSE OF ACTION HAS ACCRUED.

IN ADDITION TO THE WARRANTIES DISCLAIMED ABOVE, MONNIT SPECIFICALLY DISCLAIMS ANY AND ALL LIABILITY AND WARRANTIES, IMPLIED OR EXPRESSED, FOR USES REQUIRING FAIL-SAFE PERFORMANCE IN WHICH FAILURE OF A PRODUCT COULD LEAD TO DEATH, SERIOUS PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE SUCH AS, BUT NOT LIMITED TO, LIFE SUPPORT OR MEDICAL DEVICES OR NUCLEAR APPLICATIONS. PRODUCTS ARE NOT DESIGNED FOR AND SHOULD NOT BE USED IN ANY OF THESE APPLICATIONS.

CERTIFICATIONS

United States FCC
This equipment has been tested and found to comply with the limits for a Class B digital devices, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user  is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

WARNING: Changes or modifications not expressly approved by Monnit could void the user’s authority to operate the equipment.

RF Exposure
WARNING: To satisfy FCC RF exposure requirements for mobile transmitting devices, the antenna used for this transmitter must not be co-located in conjunction with any antenna or transmitter.

Monnit and ALTA Wireless Sensors:
This equipment complies with the radiation exposure limits prescribed for an uncontrolled environment for fixed and mobile use conditions. This equipment should be installed and operated with a minimum distance of 23 cm between the radiator and the body of the user or nearby persons.

All ALTA Wireless Sensors Contain FCC ID: ZTL-G2SC1. Approved Antennas
ALTA devices have been designed to operate with an approved antenna listed below, and have a maximum gain of 14 dBi. Antennas having a gain greater than 14 dBi are strictly prohibited from use with this device. The required antenna impedance is 50 ohms.

• Xianzi XQZ-900E (5 dBi Dipole Omnidirectional)
• HyperLink HG908U-PRO (8 dBi Fiberglass Omnidirectional)
• HyperLink HG8909P (9 dBd Flat Panel Antenna)
• HyperLink HG914YE-NF (14 dBd Yagi)
• Specialized Manufacturing MC-ANT-20/4.0C (1 dBi 4? whip)

Canada (IC)
Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the Equivalent Isotropically Radiated Power (E.I.R.P.) is not more than that necessary for successful communication.
The radio transmitters (IC: 9794A-RFSC1, IC: 9794A-G2SC1, IC: 4160a-CNN0301, IC: 5131A-CE910DUAL, IC: 5131A-HE910NA, IC: 5131A-GE910 and IC: 8595A2AGQN4NNN) have been approved by Industry Canada to operate with the antenna types listed on the previous page with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device.
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and  (2) this device must accept any interference, including interference that may cause undesired operation of the device.

SAFETY RECOMMENDATIONS – READ CAREFULLY

Be sure the use of this product is allowed in the country and in the environment required.
The use of this product may be dangerous and has to be avoided in the following areas:

• Where it can interfere with other electronic devices in environments such as hospitals airports, aircraft, etc.
• Where there is a risk of explosion such as gasoline stations, oil refineries, etc.
  It is the responsibility of the user to enforce the country’s regulations and the specific environmental regulation.

Do not disassemble the product; any mark of tampering will compromise the warranty validity. We recommend following the instructions of this user guide for the correct setup and use of the product.
Please handle the product with care, avoiding any dropping and contact with the internal circuit board as electrostatic discharges may damage the product itself. The same precautions should be taken if manually inserting a SIM card, checking carefully the instruction for its use. Do not insert or remove the SIM when the product is in power-saving mode.
Every device has to be equipped with a proper antenna with specific characteristics. The antenna has to be installed with care in order to avoid any interference with other electronic devices and has to guarantee a minimum distance from the body (23 cm). In case this requirement cannot be satisfied, the system integrator has to assess the final product against the SAR regulation.
The European Community provides some Directives for the electronic equipment introduced on the market. All the relevant information is available on the European Community website: http://ec.europa.eu/enterprise/sectors/rtte/documents/
Additional Information and Support
For additional information or more detailed instructions on how to use your Monnit Wireless Sensors or the iMonnit Online System, please visit us on the web at monnit.com .

Monnit Corporation
3400 South West Temple Salt Lake City, UT 84115 801-561-5555
www.monnit.com
Monnit, Monnit Logo and all other trademarks are property of Monnit, Corp.
© 2020 Monnit Corp. All Rights Reserved.

References

• Remote Monitoring Solutions with Wireless Sensors for IoT
• Monnit Support Options: FAQs, Knowledgebase, Videos, Docs, & More
• Wireless Hydrogen Sulfide Sensor to Remotely Measure H2S Gas
• Wireless Hydrogen Sulfide Sensor to Remotely Monitor H2S Gas

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>