This product is not intended for life safety applications.
Do not install this product in hazardous or classified locations.
The installer is responsible for conformance to all applicable codes.
Leviton, ModHopper are trademarks of Leviton
Other brand and product names are trademarks or registered trademarks of their respective holders.
U.S. Government Restricted Rights: Use, duplication or disclosure by the Government is subject to restrictions set forth in subparagraph (a) through (d)
of the Commercial Computer Restricted Rights clause at FAR 52.227-19 when applicable, or subparagraph (c) (1) (ii) of the Rights in Technical Data and
Computer Software clause at DFARS 252.227-7013, and in similar clauses in the NASA FAR Supplement.
Limited Warranty
LEVITON IS PROVIDING THIS WARRANTY IN LIEU OF ALL OTHER EXPRESS OR IMPLIED WARRANTIES, INCLUDING ANY WARRANTY
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THIS WARRANTY IS BUYER'S EXCLUSIVE REMEDY FOR ALL
CLAIMS AGAINST LEVITON. LEVITON SHALL NOT BE LIABLE FOR ANY CONSEQUENTIAL OR INCIDENTAL DAMAGES. LEVITON'S
TOTAL LIABILITY FOR ALL CLAIMS SHALL BE LIMITED TO THE PRICE PAID FOR ITS PRODUCT.
Leviton promises buyer that any standard product manufactured by Leviton shall be free from all material defects in design, material, or manufacturing for
a period of 2 years from the manufacture date; provided, however, that the warranty shall not extend to ordinary wear and tear or to normally replaceable
components (e.g., batteries). During the warranty period, Leviton may repair or replace (in its sole discretion) any product suffering from a warranty defect
and returned freight prepaid by buyer, with no charge to buyer for any warranty repair or replacement. The warranty shall remain in full force and effect for
such 2 year period, provided that the product: (1) was installed, operated, and maintained properly; (2) has not been abused or misused; (3) has not been
repaired, altered, or modified outside of Leviton's authorized facilities; (4) has not been sold subject to other warranty terms specified at the time of sale;
and (5) is still owned by the original purchaser. This warranty provides specific legal rights that may be varied by state law. Leviton's products are not
designed for life or safety applications.
Product Application Limitation
Leviton strongly believes in continuous improvement, therefore we must reserve the right to change specifications and product offerings without notice.
Where possible, we will substitute products with equivalent functionality when necessary.
FCC Part 15 Information
Note: This equipment has been tested by the manufacturer and found to comply with the limits of a class A digital device, pursuant to part 15
of the FCC rules. These limits are designed to provide reasonable protection against interference when the equipment is operated in a
commercial environment. 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. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
Modifications of this product without the express authorization of Leviton nullify this statement.
Markings and Symbols: ............................................................................................................................................................. 3
Model Information ..................................................................................................................................................................... 5
R9120 Features and Specifications ...................................................................................................................................... 6
System settings ..................................................................................................................................................................... 8
Status LEDs.......................................................................................................................................................................... 8
Signal Strength Test ............................................................................................................................................................. 8
Modbus Features ...................................................................................................................................................................... 12
Modbus Register List ......................................................................................................................................................... 12
The ModHopper™ wireless Modbus/pulse transceiver is designed to allow systems integrators the ability to communicate
with remote locations while avoiding the costs associated with running low voltage wiring to multiple locations in a single
or between multiple buildings. To meet these requirements, the ModHopper™ provides the installer with all the tools
necessary to install and configure the hardware and software with a minimum of time and investment.
Applications
The R9120 wireless Modbus/pulse transceiver has several applications. These include:
Energy Monitoring.
Solar PV Power Generation monitoring
Malls, office buildings, and other tenant energy monitoring applications.
Installation Checklist
A ModHopper™ system installation has the following components:
Required hardware
Two or more ModHopper R9120 transceivers.
Note: the R1920 transceivers must be the same radio type. e.g. R9120-3 must be used with another R9120-3;
R9120-5 must be used with another R9120-5.
External hardware
RS485 Modbus master system such as an A8812 EMH Hub™ or a Modbus compatible PLC.
Optional: RS485/Modbus slave devices such as power meters or IO modules.
Optional: Pulse output transducers for measuring gas, electricity, water, etc. from existing meters and sensors.
Make sure to obtain the pulse output scale, or multiplier for each device you will be using.
Low voltage wire for attaching pulse or Modbus devices to the R9120, typically 18-24gauge
Before proceeding with the installation, verify the hardware is Rev C. It is important to use the correct manual that matches
the hardware being installed.
As per SIPCO LLC, this product may be used in a system and employ or practice certain features and/or methods of one or
more of the following patents:
SIPCO, LLC
U.S. Patent No. 7,103,511
U.S. Patent No. 6,914,893
U.S. Patent No. 6,891,838
U.S. Patent No. 5,714,931
U.S. Patent No. 6,233,327
U.S. Patent No. 7,397,907
U.S. Patent No. 6,618,578
U.S. Patent No. 7,079,810
U.S. Patent No. 7,295,128
U.S. Patent No. 7,263,073
U.S. Patent No. 7,480,501
U.S. Patent No. 6,437,692
U.S. Patent No. 7,468,661
U.S. Patent No. 7,053,767
U.S. Patent No. 7,650,425
U.S. Patent No. 7,739,378
60MHz Arm7 embedded CPU
3 x RF, 2 x RS 485, 2 x pulse, Alive, Alarm
Modbus RTU
Modbus address may be set from 1 to 247 via Dipswitch. Included class 2
Power supply requires 100-240VAC, 50/60Hz 0.5A
(power supply not included in models with -T option)
2 pulse inputs, dry contact
Monitor consumption/rate/min/max
Pulse rate/width user selectable to 10Hz, 50Hz, 100Hz, or 250Hz. Pulse
rate option: 10Hz, minimum pulse width 50ms
Pulse rate option: 50Hz, minimum pulse width 10ms
Pulse rate option: 100Hz, minimum pulse width 5ms
Pulse rate option: 250Hz, minimum pulse width 2ms
Contact closure threshold 100 to 2.5k user selectable
Pulse count values are stored in non-volatile memory.
RS-485 (+,-, S), 9600/19200 baud, N, 8, 1, two wire.
Supports up to 32 external devices per ModHopper. (expandable)
Frequency Hopping, ISM band, see table below.
North America: Temperature 0º – 50ºc 3, 0 – 95% humidity, non-condensing.
Pollution Degree 2, Altitude up to 2000M.
For indoor and outdoor use when used in an appropriate enclosure.
The R9120 must be mounted inside a NEMA rated electrical enclosure for safety and isolation
requirements when used outdoors.
FCC (USA): Part 15.247, Class A
Step 1 - Unpack materials: Remove all materials from shipping box and verify all required components are available
Step 2 - Mount the ModHopper to a wall or inside the electrical enclosure if required. When mounting the ModHopper and
the antenna inside an enclosure, a non-metallic enclosure will be required. Metal enclosures restrict RF communications. If
a metal enclosure is required, use an external antenna and an RF antenna cable.
Step 3 - Connect the pulse output devices. For KYZ pulse output meters, attach the normally-open circuit to the
ModHopper. These are usually the K and Z terminals.
Step 4 - Connect the RS485 Modbus network loop as shown in the wiring diagram. Follow the manufacturer’s instructions
for installing and powering other Modbus devices. Verify that the Modbus address settings are unique for each device (i.e.,
no two devices with the same address). Connect each device in the chain by “daisy-chaining” the devices together . Observe
+ and - polarity on the Modbus devices.
Do not ground the RS485 shield inside an electrical panel. All RS485 and 24VDC power wires, including the shield should
be insulated to prevent accidental contact to high voltage conductors.
The pulse, RS485 and power cable should be mechanically secured where it enters the electrical panel.
The wire used to provide pulse and RS485 communications should be insulated to meet requirements of the voltages present
inside any box the wire is mounted within. For example, Belden 1120A has a 600v insulation rating and can be used in
many applications. Check with your electrical installer for details as local code requirements may vary.
WARNING: After wiring the ModHopper, remove all scraps of wire or foil shield from the electrical panel.
This could be dangerous if wire scraps come into contact with high voltage wires.
Step 5 – Attach the antenna to the ModHopper. When using an antenna cable, avoid sharp bends; kinks in the
antenna cable will degrade performance.
Step 6 – Attach the power to the ModHopper and apply power. Observe the LEDs to confirm the device is operating.
Alive (green): blinks once per second while the system is operating correctly.
RS485 RX: The RX led should blink whenever a modbus query is sent on the RS485 loop. (regardless of
the target address of the query). If the ModHopper is attached to an EMH Hub, the RX led should blink
about once per second.
RS485 TX: The TX LED will blink when the R9120 responds to a modbus query.
Note: If cleaning is required, use a dry towel to remove dust from the ModHopper. Do not use fluids to clean the
ModHopper.
Before the ModHopper can be used, you must set the Modbus address of the ModHopper.
This address must be unique among all Modbus devices in the system including all devices
that are connected on remote wireless links. Address 0 (all switches off) is not allowed.
Select an address, and set the dipswitches to match.
The sum of the value of the switches is the address. In the example to the right, address 52
is set by placing switch 4, 16 and 32 to the on position.
Note: 4 + 16 + 32 = 52
System settings
For most systems, set all of the system switches to the "off" position.
Radio channel: This option selects the channel number that can be used to isolate a group
of ModHoppers. This option may be set for channels 0 to 6. Channel 7 (all 3 switches on)
is not allowed.
Programming: Set the “Prog Enable” to Off for normal operation.
485 Termination Enable: Set the “485 Term En” to ON to enable a 120ohm termination
resistor on the RS485 network. This should be used when the ModHopper is on the end of a
485 wiring run. Set this switch to OFF when the ModHopper is in the middle of an RS485
wiring run.
Port RS232 or RS485: Set the switch to the “off” position for RS485 operation. The
ModHopper can communicate via the RS232 connection however most Modbus devices will need 485 terminals. .
Baud Rate: This option sets the serial port speed for the Modbus devices connected to the ModHopper. Set this option to
“off” for 19200. Set the switch to “on” for 9600 baud.
Reserved: Set this option to Off.
Status LEDs
The device should power up and be ready in a few seconds. The LEDs should blink in the following manner.
The "Alive" LED should start to blink about once per second.
The Alarm LED will blink when transmission errors occur.
The RF TX/RX LEDs will blink when the radio is receiving or transmitting data.
The RS485 LEDs will blink for local Modbus activity.
The Pulse input LEDs will light when the corresponding pulse input terminals are closed.
If the device has the -SN option, the 400MHz LED will blink when an RF packet from a 400MHz sensor transmitter is
received.
Signal Strength Test
When the ModHopper is operating, the Test Button can be used to report the signal strength received by the ModHopper
from another unit.
Press and hold down the test button. The status LEDs will light up as a bar graph display. Each LED is approximately 10%
of scale. For example if PULSE 1 and 2 are on, the received strength is approximately 20% to 29%.
For useful signal reporting, it is important to turn off all but one other ModHopper. When reporting the signal strength, the
most recent wireless transmission received is displayed. If two ModHoppers are transmitting, the display will only show the
most recently received packet, and the user will not be able to determine which ModHopper the signal strength being
reported.
Note: the normal operation of the ModHopper is suspended while the test button is pressed. Modbus communications and
wireless transmissions are not processed.
The ModHopper has several data points that may be read using the Modbus protocol.
For each of the two pulse inputs, the ModHopper reports a value for consumption and rate. Rate fields are provided for the
average rate during the log period (block demand), the instantaneous rate, and the min/max instantaneous rate observed
during the log period. The pulse counts for each input are stored in non-volatile memory to preserve the count when power
is removed. For more information on the specific Modbus registers used for the pulse inputs, refer to the Modbus register
section of this manual.
When configuring a Modbus Master such as a PLC, TCP Gateway, or computer software, you must increase the timeout on
the RS485 port of your system. The ModHopper adds about 500mS of delay per hop. In a complex system with multiple
ModHoppers, a 1 to 2 second round trip time is not uncommon.
EMH Hub Data Display Page:
When using the ModHopper with the EMH Hub data acquisition server, the EMH Hub will read the pulse input data from
the ModHopper and provide configuration menus for all of the ModHopper options.
The EMH Hub will display will report all the data values present on the ModHopper. In addition, the instantaneous
min/max rate values will be cleared after each logging interval. Click the Configure button to set up pulse input names, unit
of measure and multipliers as needed.
The EMH Hub setup and configuration page includes an advanced configuration page to set all of the ModHopper features
with a convenient web page interface.
In this setup page, there are several options available.
Serial port timeout, and protocol configuration. When a request comes in over the wireless mesh network and is
sent out on the ModHopper RS485 serial port, the ModHopper must wait for the attached modbus device to reply
to the query. The timeout option controls how long the ModHopper will wait before giving up on the attached
Modbus device and discarding the query. Most Modbus devices will respond in 150ms or less.
Pulse input contact closure threshold: allows you to set a maximum resistance to be counted as a “closed” contact.
This is helpful when using intrinsic barrier devices. Default of 500 ohms will work in most applications.
Pulse input maximum count frequency. For most pulse meters, 10Hz is adequate. Faster counting of mechanical
relays may result in “relay bounce” and give an incorrect count. Consult the pulse output device for information on
maximum expected pulse output rate.
Data log control: enable/disable EMH Hub data logging for the ModHopper. Note: this is an internal EMH Hub
feature, and does not set any registers on the ModHopper.
In addition to the configuration options, some further details about the ModHopper are provided. These include the serial
number, firmware version, uptime, RF/RS485 packet counters, and internal temperature and power supply monitor.
For further information configuration and status registers, refer to the Modbus section in this manual.
The EMH Hub data acquisition server has additional diagnostic features that assist with ModHopper deployments. The
most useful is the ModHopper route map. Select the ModHoppers menu from the Wireless section in the EMH Hub menu
tree as shown below.
The graph will draw a blue box for each ModHopper that is attached to the system. The blue number inside the box icon is
the Modbus address of the ModHopper. To the side of each icon, three lines of information will be shown.
The device list name will be shown to the side of each ModHopper icon
The link quality, hops and round trip time (rtt) will be printed under the ModHopper name.
A list of attached Modbus device addresses will be shown on the third line. This is a list of addresses that the
ModHopper has automatically detected on the local RS485 port.
The graph will print strong links in thick green lines. Lines progress from green, to yellow, to red to indicate weak links.
These should be sufficient to perform all operations (read many values, make single change, and identify). In addition the
device will respond to with Modbus exceptions for invalid function, value, and register if out of bound requests are made.
Modbus function 0x11 Slave ID function will respond with id=49 and one of the following id text values:
"Leviton, ModHopper, R9120-5"
Modbus Register List
All modbus registers are read-only unless otherwise noted.
Data points:
offset point type desc
------- ------- ------- ------------------
040001 UINT32 (N/V) pulse count 1 MSW
140002 UINT32 (N/V) pulse count 1 LSW
240003 UINT32 (N/V) pulse count 2 MSW
340004 UINT32 (N/V) pulse count 2 LSW (same format as pulse count 1)
440005 UINT16 inst pulse 1 time (seconds)
540006 UINT16 inst pulse 2 time (seconds)
640007 UINT16 (R/W) min pulse 1 time (seconds) (write clears min/max)
740008 UINT16 (R/W) min pulse 2 time (seconds)
8 40009 UINT16 (R/W) max pulse 1 time (seconds)
940010 UINT16 (R/W) max pulse 2 time (seconds)
1040011 UINT16 (R/W, N/V) inst pulse count size. (default 5)
10040101 UINT16 Serial Number (bytes 1,2) (serial number)
101 40102 UINT16 Serial Number (bytes 3,4)
10240103 UINT16 Serial Number (bytes 5,6)
10340104 UINT16 firmware version (e.g. v1.03, high byte=major,
lowbyte=minor, 0x8000 flag set for Beta)
10440105 UINT16 boot count
10540106 UINT32 mfg date MSW
10640107 UINT32 mfg date LSW
10740108 UINT16 radio group id setting (0-6)
10840109 UINT16 alarm flags (0x01 = boot from watchdog)
10940110 UINT16 max packet buffers used.
11040111 UINT32 Radio up time (seconds) MSW
11140112 UINT32 Radio up time (seconds) LSW
11240113 UINT16 RF short packets. write 0 to clear stat counters.
15740158 UINT16 Max allowed software RF channel setting. 0=not available.
(firmware 2.06 or later)
71240713 UINT16 bitmap of known radios (16 registers) LSB, MSB order.
bit0=n/a, bit1=addr1, etc.
Register Functions
Pulse Count: The pulse count is stored as an unsigned 32bit integer. This allows for 2^32 pulses (4.2billion) to be counted
before rollover. On Modbus systems that do not allow you to read 32bit values, you can calculate the pulse count as
follows:
count = (MSW * 65536) + LSW
or
count = (MSW << 16) | LSW [bit shift high order word by 16 bits and xor against low order word ]
Pulse count registers accumulate a total number of pulses received on each pulse input. The pulse count totals always
increment and cannot be cleared or set to an arbitrary value to prevent tampering. All pulse count totals are stored in nonvolatile memory to preserve counts during power failure. The unsigned 32 bit counter values can accumulate up to 4.29
billion (2^32) pulses before rollover.
All 32 bit data point values are encoded in 2 Modbus registers (16bits each). Modbus master systems should always query
the A8332-8F2D using a single query to read an entire block of registers. Never use two queries to read one register and
then combine the two results into a single 32 bit value. Doing so will allow the pulse count to increment in the middle of the
two Modbus queries, and will cause intermittent data readings that are incorrect.
For example, a pulse input has a count of 65534. This is represented as a 32 bit hex number 0x0000FFFE. The first 4 digits
are the MSW register, the second 4 digits are the LSW register. The Modbus Master reads the first (MSW) register and gets
0x0000. In between the two readings, the pulse input counts 2 more pulses, making the total 65536 or 0x00010000 in hex.
Next the Master reads the second (LSW) register and gets 0x0000. When the two registers are combined, the result is
0x00000000. The proper way to handle this situation is to simply read both registers in a single Modbus query.
Instantaneous Pulse Rate: The pulse rate values for instantaneous, min and max rates are calculated based on the time
between arriving pulses. For example, if InstPulse1 = 30, and inst pulse count size is 5, then the average rate for the last 5
pulses is 6 seconds per pulse. To convert the register values (in seconds) to a rate value, use the following formula.
RatePerHour = (N * 60 * 60 / Inst_Register)
Where InstRegister is any of the 6 register values 4 through 9. N is the instantaneous pulse count size at offset 10.
Min/Max pulse rate: These 4 registers are calculated from the instantaneous pulse rate. These latching registers are
updated whenever the minimum or maximum rate fields are exceeded by the instantaneous rate. These 4 registers may be
cleared by writing a zero to the register. Writing to one min/max register clears all four min/max registers.