Users Manual M2000

Web to Wireless to Modbus Communication System

M2M Communications Corporation Boise Research Center 12554 W. Bridger Boise, ID 83713 208 947 9500 info@m2mcomm.com
Last revision: November 2007

Table of Contents
Introduction ________________________________________________________________ 4 Operation is Very Simple ______________________________________________________ 5 How it Works _______________________________________________________________ 5 Modbus Communication______________________________________________________ 6
Intelligent Modbus Master _______________________________________________________ 6 Intelligent Modbus Slave ________________________________________________________ 6 Web-to-Wireless Modem ________________________________________________________ 6 Monitoring Modbus I/O Points ____________________________________________________ 7 Monitoring Analog Values from Modbus Registers_____________________________________ 7 Monitoring Bit Packed Modbus Registers ____________________________________________ 8 Writing to Modbus Devices _______________________________________________________ 9

Automatic Analysis and Reporting _____________________________________________ 7

Web-to-Wireless Modem _____________________________________________________ 10 Reporting to the M2M Web Server _____________________________________________ 11

Time Scheduled Reports _______________________________________________________ 11 Reports on Request ___________________________________________________________ 11 Tech Support ________________________________________________________________ 12 Connecting the M2000 to a PC __________________________________________________ 13 Installing the Local Programmer on your PC ________________________________________ 13 File Menu ___________________________________________________________________ 14 Edit menu ___________________________________________________________________ 14 Device Tasks ________________________________________________________________ 15 View Menu __________________________________________________________________ 16 Help Menu __________________________________________________________________ 16 Read I/O points_______________________________________________________________ 16 Read Analog Registers_________________________________________________________ 18 Read Bit Packed Registers______________________________________________________ 20 Write Registers for M2000 Master devices ________________________________________ 22 Time Scheduled Reports _______________________________________________________ 24 Configuration ________________________________________________________________ 25

Getting Started ____________________________________________________________ 12 The M2000 Local Configuration Program _______________________________________ 13

Local Programmer Overview __________________________________________________ 13

Editing the Operating Parameters ______________________________________________ 16

Power Mode __________________________________________________ 25 Daily Call Limit ________________________________________________ 25 Modbus Settings _______________________________________________ 26 Master / Slave Selection _________________________________________ 26 M2000 Master Polling Frequency __________________________________ 26 Report RSSI to Modbus Register __________________________________ 27 Cellular Channel Selection _______________________________________ 27
M2000 Slave Mode Commands _______________________________________________ 28
An Explanation of Addressing in the M2000 Slave ____________________________________ 29

M2M Communications

M2000 Users Manual

M2000 Slave Mode Command Summary ________________________________________ 30 Sending & Receiving Data with the Web-to-Wireless Slave Modem ____________________ 31
Load Transmit Data into the M2000 _______________________________________________ 31 Send Transmit Data to the Web Server ____________________________________________ 34 Read Transmit Data from the M2000 ______________________________________________ 36 Read Transmit Result Code _____________________________________________________ 38 Read RSSI __________________________________________________________________ 39 Read M2000 Status ___________________________________________________________ 40 Read Data Received from the Web Server _________________________________________ 41 Clear Received Data Memory ___________________________________________________ 44 Write Digital I/O Data to the M2000 _______________________________________________ 46 Write Register Data to the M2000 ________________________________________________ 47 Write Bit Packed Register Data to the M2000 _______________________________________ 50 Send I/O, Register, or Bit Packed Registers to the Web Server __________________________ 52

Writing Data to the Intelligent M2000 Slave for Automatic Analysis and Reporting _________ 46

Exception Messages from the M2000 Slave ______________________________________ 54 Installing the M2000 ________________________________________________________ 57
Selecting an installation location _________________________________________________ 57 Testing the Receiver Strength ___________________________________________________ 57 Troubleshooting Tips __________________________________________________________ 58 Connecting to Modbus with RS232 _______________________________________________ 59 Connecting to Modbus with RS485 _______________________________________________ 59 Modbus Data Comm Setup _____________________________________________________ 60

RTU mode ___________________________________________________ 60 ASCII mode __________________________________________________ 61

Troubleshooting the Modbus Connection ___________________________________________ 61

M2M Network Operation Center _______________________________________________ 62 Using the Web Site _________________________________________________________ 64
Logging In ___________________________________________________________________ 64 Viewing Monitored Inputs _______________________________________________________ 64 Device Setup ________________________________________________________________ 64 User Notifications by Voice or E-Mail ______________________________________________ 65 Inbound Voice Report: 1-877-747-9500 ___________________________________________ 67 Device Activity Log ____________________________________________________________ 67 Send Commands from the Web Server to the M2000 _________________________________ 67 Create Custom Commands _____________________________________________________ 69 Data Exporting _______________________________________________________________ 70 LED Indicators _______________________________________________________________ 70 Daily Call Limits ______________________________________________________________ 72 Cellular Carrier Requirements ___________________________________________________ 72 Retry Algorithm _______________________________________________________________ 73 Antenna ____________________________________________________________________ 74 Cellular Radio ________________________________________________________________ 74 Power Supply / Enclosure Options ________________________________________________ 74 CPU / Memory _______________________________________________________________ 75 Environmental Considerations ___________________________________________________ 75 Part Numbers ________________________________________________________________ 75

Miscellaneous Operational Details ____________________________________________ 70

Hardware Specifications _____________________________________________________ 74

M2M Communications

M2000 Users Manual

Introduction

The M2M Wireless Communicator is a web-to-wireless remote monitoring and communication system. Its internal GSM cellular modem provides two-way communications to the automated M2M operations center and the www.m2mcomm.com web site. The GSM cellular network provides very wide spread coverage throughout North America with no requirement for a local cellular account. The small size and low cost make it suitable for a wide variety of general monitoring applications.

This users manual covers the M2000, which belongs to a family of several models: M2000 Monitors and controls other Intelligent Electronic Devices (IEDs) using a Modbus communication port. Directly monitors 10 digital inputs, which can be configured as alarms, counters, or counter/timers. There is no Modbus port. Combines both Monitor and control other Intelligent Electronic Devices (IEDs) using a Modbus port and monitor 10 direct connect digital inputs. Directly monitors 10 digital inputs and 3 analog inputs. Controls 3 relay outputs. There is no Modbus port.

M2500

M2510

M3000

The models M2500, M2510, and M3000 are covered in separate manuals.

M2M Communications

M2000 Users Manual

Operation is Very Simple

1. Set up the register values and I/O points to be read from and written to the Modbus device. 2. Connect the M2M Communicator to the device(s) to be monitored and turn it on. 3. The M2000 will automatically establish two-way communications over the public cellular network to the www.m2mcomm.com web site. 4. Log onto your private page on the web site to: View the last reported status of your equipment switch positions, diagnostic information, tank levels, temperature, pressure, number of pulses received. Request an up-to-date report from the unit. Configure selected events to trigger an immediate user notification by voice phone or Email.

5. Or Dial in to a toll-free number from any telephone to hear the status of your equipment.

How it Works
When an M2000 makes a call from anywhere in North America (where there is GSM cellular coverage), it is recognized locally as a roaming cell phone. As a part of the standard roaming registration protocol, the local cellular network automatically passes the module's identification numbers and data to the central cellular hub. The M2M module transmits your data in a normally non-utilized data field. This technique allows the transmission of an identification number and the time and date, plus 25 digits of customer specific data, all at a very low cost. At the M2M network operations center, the data is validated and processed for distribution to the end user. In addition, configuration and control information can be sent from the web server to the M2000. This is called cellular control channel communications. The primary advantages of this method are low cost and wide spread coverage throughout North America. The disadvantage is that the customer specific data packet is relatively small -- 25 digits per transmission. The control channel is best suited for applications that send a relatively small amount of data infrequently. The M2000 maximizes the potential of the control channel technology by internally testing the data from monitored devices and only transmitting data to the web server when a reportable event occurs. Reports are only generated when: A monitored register value or I/O point reaches a setpoint or limit, or A time scheduled report is due, or A report is requested from the web site

M2M Communications

M2000 Users Manual

Modbus Communication
The M2000 communicates directly with Intelligent Electronic Devices (IED) such as Programmable Logic Controllers, measuring instruments, annunciators, and displays. The M2000 includes both a RS232 and a RS485 serial port and communicates using the standard Modbus protocol. Data passed to the M2000 will be wirelessly transmitted to the www.m2comm.com web site where it can be stored, interpreted and displayed, or forwarded to another location.

The M2000 has three basic modes of communication with the IED: Intelligent Modbus Master As an intelligent Modbus Master, the M2000 polls and reads data from specified addresses in Modbus slave devices. It then compares this data to customer-defined setpoints and automatically reports when a specified condition exists or when one of the limits is exceeded. Intelligent Modbus Slave As an intelligent Modbus Slave, the M2000 is configured to receive commands and data from a Modbus Master device. The M2000 will then compare the data to customer-defined setpoints and automatically report when a specified condition exists or when one of the limits is exceeded. The primary difference between the Intelligent Modbus Master and Intelligent Modbus Slave is in how the transfer of data is initiated. Once the data is inside the M2000, it is analyzed and reported in the same way. Web-to-Wireless Modem In the Web-to-Wireless Slave Modem mode, the M2000 can be used as a completely flexible wireless modbus-to-cellular-to-web communication system, much like a simple modem. A Modbus Master device can load data into the M2000 and issue a transmit command. The M2000 does not analyze or format this data; it simply transmits the data to and from the web server. When the M2000 is configured as a slave device, it can be used in both the: (1) Intelligent mode for automatic analysis and reporting and (2) Web-to-Wireless modem mode. There are specific commands that are used for each mode and they do not conflict with each other. For example, some data values can be loaded into the M2000 to be monitored and tested, while other data can be directly transmitted to the web server without further processing or interpretation.

M2M Communications

M2000 Users Manual

Automatic Analysis and Reporting

When the M2000 is used as an Intelligent Master or Slave, there are three types of data that can be transferred to the M2000 for automatic analysis and alarm reporting.

Monitoring Modbus I/O Points The M2000 can monitor up to twelve digital inputs or outputs that have been read from Modbus devices. If configured as a Master device, the M2000 will repeatedly read the requested points at a specified polling rate of every 1-240 seconds. As a slave, the M2000 will receive the data points from a Modbus Master device. When an I/O point changes, and a specified alarm condition exists, the device will report the event to the M2M Network Operation Center. Alarm conditions can be specified for each digital point and can be defined as an open close, close open or both. A separate and independent trigger time can be specified for each direction, in seconds, from 1-65535.

The M2000 Master uses Modbus command 01, Read Coil Status, to read the ON/OFF status of discrete outputs. Outputs can be read from unit numbers ranging from 1-32 and addresses of 00001-09999. The M2000 Master uses Modbus command 02, Read Input Status, to read the ON/OFF status of discrete inputs. Inputs can be read from unit numbers ranging from 1-32 and addresses of 10001-19999. The Modbus Master device uses Modbus command 05, Force Single Coil to write the ON/OFF status of discrete inputs or outputs to the M2000 Slave.

Monitoring Analog Values from Modbus Registers The M2000 can monitor up to twenty 16-bit binary, or analog, registers from Modbus slave devices. The Master device will repeatedly read the requested registers at a specified polling rate of every 1-240 seconds. When a specified range change occurs, the device will report the event to the M2M Network Operation Center. For each register, up to three setpoints or limits can be specified plus a trigger time and a dead band. This creates up to four operating ranges such as low, normal, high, and alarm (or cold, cool, warm, and hot, etc.). When any range change is measured for the trigger time, a report can be made. The limits can be set at any value from 0-65535. Trigger times are 0-240 seconds and dead bands can be specified from 0-250.

M2M Communications

M2000 Users Manual

 The M2000 Master uses Modbus command 03, Read Holding Registers, to read the binary contents of holding registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 40001-49999. The M2000 Master uses Modbus command 04, Read Input Registers, to read the binary contents of input registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 30001-39999. The Modbus Master device uses Modbus command #6, Load Single Register, or #16, Load Multiple Registers, to write up to 20 values to the M2000 Slave.

Monitoring Bit Packed Modbus Registers The M2000 can monitor up to four bit-packed holding registers from Modbus slave devices. The Master device will repeatedly read the requested registers at a specified polling rate of every 1240 seconds. When a specified alarm condition exists, the device will report the event to the M2M Network Operation Center. For each of the four registers, all 16 bits can be independently tested as discrete bits. Alarm conditions can be specified for each bit and can be defined as an open close (1 0), close open (0 1), or both. A separate and independent trigger time can be specified for each direction, in seconds, from 1-65535. When any monitored bit change is detected for the trigger time, a report will be made.

The M2000 Master uses Modbus command 03, Read Holding Registers, to read the contents of holding registers. Holding registers can be read from unit numbers ranging from 1-32 and addresses of 40001-49999. The M2000 Master uses Modbus command 04, Read Input Registers, to read the contents of input registers. Input registers can be read from unit numbers ranging from 1-32 and addresses of 30001-39999. A Modbus Master device uses Modbus command #6, Load Single Register, or #16, Load Multiple Registers, to write the bit packed registers to the M2000 slave.

M2M Communications

M2000 Users Manual

Writing to Modbus Devices A M2000 Master can receive up to 20 unique data commands from the web server and then pass them to pre-assigned holding registers or output points in a Modbus slave. Write operations can be one-time events based on a unique command sent from the web site, or can be repeated continually at a specified frequency of every 1-240 seconds. A M2000 Slave can receive up to 300 different data commands from the web server and then pass them to a Modbus master upon request. One-time commands are useful as remote output commands to turn a machine on or off or as configuration changes such as setpoint changes. The data to be written can be predefined (with the local programming utility) as: A fixed value of 0 or 1 to outputs in addresses 00001 to 09999, or A fixed value of 0-65535 to holding registers in addresses 40000 to 49999, or

each piece of write data can also be read from one device or address and then written to a specified output or holding register. If the write data is to be read from another device, there are four ways to do it:

1) The M2000 Master uses Modbus command 01, Read Coil Status, to read the ON/OFF status of discrete outputs. Discrete outputs can be read from unit numbers ranging from 1-32 and addresses of 00001-09999. 2) The M2000 Master uses Modbus command 02, Read Input Status, to read the ON/OFF status of discrete inputs. Discrete inputs can be read from unit numbers ranging from 1-32 and addresses of 10001-19999. 3) The M2000 Master uses Modbus command 03, Read Holding Registers, to read the binary contents of holding registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 40001-49999. 4) The M2000 Master uses Modbus command 04, Read Input Registers, to read the binary contents of input registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 30001-39999. NOTE: If data is read from registers and then written to I/O points, the data in the registers must be equal to 0 or 1, or the slave device will reject it. Regardless of whether the write data is fixed or dynamic, it is written in one of two ways: 1) The M2000 Master uses Modbus command 05, Force Single Coil, to set a single output to ON or OFF. Control outputs (0 or 1) can be written to unit numbers ranging from 1-32 and addresses of 00001-09999. 2) The M2000 Master uses Modbus command 06, Preset Single Register, to write to a single holding register. Registers can be written in unit numbers ranging from 1-32 and addresses of 40001-49999.

M2M Communications

M2000 Users Manual

Web-to-Wireless Modem
In the Slave Modem Mode, the M2000 can be used as a completely flexible wireless modbus-tocellular-to-web communication system, much like a simple modem. In the slave modem mode, an intelligent modbus master such as a Personal Computer or Programmable Logic Controller (PLC) can pass 24 digits of data to the M2000 and then tell the M2000 to transmit that data (plus the cellular identification number and the date and time) to the web site. The M2000 does not know or care what the data is or means; it simply passes the data through the cellular network to the M2M Network Operations Center. At the M2M web server, the 24 digits can be interpreted and displayed based on customer-designed rules or it can be exported to another location. Up to 300 unique commands or data values can also be sent to the M2000 from the M2M web site. This data can be read from the M2000 by the modbus master at any time, and can be used for control or configuration purposes as desired.

All standard Modbus transmissions include either a LRC or CRC checksum as well as parity bits. This guide assumes that the user has a basic knowledge of the Modus protocol, and does not attempt to explain the use of RTU and ASCII modes, parity checks, and CRC or LRC checksum generation. These topics are fully explained in the MODBUS Over Serial Line Specification and Implementation Guide Version 1.0 (filename: modbus_over_serial_line_V1.pdf). This file can be downloaded from www.modbus.org or can be requested from M2M Communications tech support. Only Modbus RTU mode is supported by the M2000 slave mode. (ASCII mode is not supported). Baud rate, parity, and the number of stop bits are programmable. Both RS232-DB9 and RS485-RJ45 communication ports are provided.

M2M Communications

10

M2000 Users Manual

Reporting to the M2M Web Server

The M2000 is a wireless remote monitoring device that communicates over the cellular networks using the cellular control channel. It can transmit a report for several reasons. Some of the features and reports are configurable and can be enabled or disabled by M2M and/or the user. (1) The unit may be configured to send time scheduled status reports at a specified frequency. (2) A report can be requested at any time from the web site. (3) When powered on, the unit will report Initial Power On, either as a registration call or a power on call. (4) Reports will be sent when an IED register or I/O point changes to a new range. The M2000 can send several different types of reports. The reports have been designed to maximize the use of the data packet. Each report sends different register data as follows: Power-On, registration, and configuration information The range (1-4) and value (0-65535) of Registers 1-3 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 4-6 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 7-9 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 10-12 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 13-15 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 16-18 plus twelve I/O points (0 or 1) The range (1-4) and value (0-65535) of Registers 18-20 plus twelve I/O points (0 or 1) The 16 bits of Bit Packed Registers 1-4 Modem Report User Defined Data

HINT: When selecting which of your Modbus registers are mapped to which M2000 registers, try to group them according to function so that the related registers are reported together. For example, if a change to register #1 triggers a report, the report will include the values of registers 2 and 3, so use these three registers to report related information.

Time Scheduled Reports Any or all of the reports (except the Power On call) can be time scheduled at a predefined frequency. Call frequencies can be set anywhere from once every hour to once every 240 hours (10 days). The factory default is disabled. Note that when this option is enabled, reports will begin at the specified time (for example, one hour) after the unit is powered on. To schedule daily calls at a specific time, leave this setting disabled and then schedule the time-scheduled reports to be enabled from the web site at a specific time. Daily status or heartbeat type calls should normally be scheduled in the off-peak hours (10pm to 3am). Reports on Request In addition to automatic reports based on events or alarms and time-scheduled reports, you can request an individual report from the web site at any time. See the Send Commands function in the web site discussion for operating details. In the same Local Configuration Program setup screen where time scheduled reports are defined, there is also an individual check box option to include the report in the Report All list. This is a convenient one-click command from the web site that will cause the M2000 to send all reports that are on the list.

M2M Communications

11

M2000 Users Manual

Getting Started
Setting up your M2000 is a three-step process. 1. Configure the unit for your specific reporting requirements. Set up the unit as a Modbus master or slave device. Specify the I/O points and registers to be monitored. Specify the conditions (limits and trigger times) to initiate automatic reports. 2. Connect to the Modbus device(s) that you want to monitor. If the M2000 is set up as a slave, configure the Master device to send the data to be monitored. 3. Set up your private page on the M2M (www.m2mcomm.com) web site. Enter descriptive labels for the data registers or I/O points to be monitored. Set up rules that will initiate user notifications by voice or E-mail for alarms or other important events.

This manual gives you the information you need to get set up. There are two primary sections: Programming, installing, and using the M2000 Communicator, and Using the M2M web site.

Tech Support For assistance, questions, suggestions, or just to praise the product designers, feel free to contact us. Official office hours are 8-5 Monday-Friday, although there is a very good chance that someone helpful will be working on the weekend. The contact number is 208-947-9500. For prompt answers by E-mail, please describe the problems carefully. The address is info@m2mcomm.com.

M2M Communications

12

M2000 Users Manual

The M2000 Local Configuration Program

The M2000 Communicator arrives from the factory programmed with basic default settings. Unless you are incredibly lucky, some of these settings will need to be adjusted to work properly with your setup.

Connecting the M2000 to a PC The upper RS232 serial port provides a connection to a Windows based PC. Use a standard 9-pin serial cable to connect the upper RS232-DB9 connector to a PC serial port. The baud rate and other communication settings between the PC, Local Programmer and the M2000 are predefined. The only exception is the selection of the computers COMM port. This can be selected with the File | Comm Port menu of the Local Configuration Program. The Local Programmer can be used to create, edit and save profiles on the PC without being connected to the M2000. Obviously, data cannot be uploaded or downloaded to the unit until its connected.

Installing the Local Programmer on your PC The Local Programmer is a Visual Basic utility program that you will use to configure the M2000 Communicator. It can be found in the Local Programmer directory of the CD that is included with the M2000 and must be installed on your PC or laptop. It will then be used to create, display, edit, and save your configuration information. It can also be used to test the radio signal strength and the connection to your Modbus device. To install the Local Programmer, insert the M2M CD into your CD drive and run the M2000_SETUP.EXE program that is located in the Local programmer directory. This will install the utility on your computer. (The CD also includes useful documentation and application notes.)

Local Programmer Overview

The program is a standard Windows based program. Along the top of the screen is the primary menu. Below that are seven tabs that can be selected to display specific information. The data shown here in the main area of the screen is sample data for the Read Register window.

M2M Communications

13

M2000 Users Manual

File Menu The File Menu can be used to create a new profile, open a saved profile or to save a profile that you have edited. (A profile is a list of the programmable parameters and settings.)

It can also be used to download an entirely new Operating System to the M2000 when new features are available. It can also be used to specify the correct computer communication port or to exit the program

Edit menu When a row in the data grid is selected, you can use the Edit menu to open the edit screen for that row. An easier way is to just double click on the desired row to open it.

M2M Communications

14

M2000 Users Manual

Device Tasks The three Device Tasks under this menu heading will initiate an immediate command to a M2000, so these should be run only when connected to a powered-up unit (unless you REALLY like watching the little hourglass). Clear all Timers and Counters For the M2000, clicking on this button will clear the Daily Call Count. This is useful when the unit has reached its daily maximum call limit and you wish to reset the count to zero. This Clear Call Count command can also be sent from the web site. Write Data to a Slave IED This choice allows you to locally tell the M2000 Master to write data to an attached IED. Clicking this button will pop up a second screen that looks a lot like this:

Use this screen to select one or more of the 20 predefined write functions and to send them to the IED now. The actual write functions will be explained later in the Write Register section. This screen is disabled if the M2000 is configured as a slave device. Restore Factory Defaults The third choice under the Device Task menu heading reloads the default profile for you. The same task can be accomplished with the File | New Profile selection. The new profile must then be downloaded to the unit using the File | Download Profile to Device.

M2M Communications

15

M2000 Users Manual

View Menu This selection sends an immediate request to the M2000 asking for all monitored data including I/O data, register data, and system configuration data. The Configuration Data includes the current Radio Signal Strength Indicator (RSSI). When the data is received, it will be displayed on the computer. This is very useful for locally verifying the radio signal strength and all IED data readings. Help Menu Displays the current software revision number of the utility program

Editing the Operating Parameters

There are seven tabs that are used to display and edit specific information. The basic functionality is the same for all of them. Open the window by clicking on the tab. A data grid for that selection shows all of the current settings. Double click on any row to open the row for editing.

Master / Slave Mode Note: In the following screens, the addresses and unit numbers to be polled are only used if the M2000 is configured as a Modbus master. If it is a slave, the data will be passed from the Master to the M2000 and so there is no need to enter the addresses where the data is stored in the IED.

Digital Inputs This screen is used to set up any direct connect digital inputs. Since the M2000 has no direct connect inputs, this window will be disabled.

Read I/O points This screen shows the 12 digital inputs or outputs that can be monitored from a Modbus IED (Intelligent Electronic Device). Double click on one of the rows to open it. Use this screen to configure the IED reads.

M2M Communications

16

M2000 Users Manual

The Unit # and Address represent the slave location to be polled for data by the Master Mode and they are not used if the M2000 is configured as a slave device, since the unit never polls the Master device for data.

For Master mode devices only: Modbus rules say that Outputs (Coil Status) are stored in memory locations 00001-09999 and Inputs are stored in 10001-19999. The M2000 master can read the status of either inputs or outputs. Either one will be read as a 0 or 1, where Open = 0 = Off and Closed = 1 = On. If you request data from an address of 00001-09999, the unit will request an Output Value from the IED slave. The actual command used is Modbus function 1. If you enter an address of 10001-19999, it will request an Input Value from the IED. The actual command is Modbus function 2. The memory addresses must be selected to match those that are available in the Modbus slave. The Unit # is the Modbus slave #. It can be set from 1-32. There is no broadcast address 0.

If the Enabled box is clicked, the address will be read and tested. If the Enabled box is not checked, this address will not be read, tested, or reported. (1) You can specify that a change should only be reported on open state changes, or both, or neither. close or close open

(2) The unit will report the state of all 12 I/O points when any point changes state for longer than the programmable trigger time. The trigger time of each point is programmable on this screen and can be varied from a minimum of 1 second to a maximum of 65535 seconds (~ 18.2 hours). A different time can be specified for each input and each direction (open-closed and closedopen). Any change that does not remain stable for the specified trigger time will be ignored. The factory default trigger time is 5 seconds for both directions.

M2M Communications

17

M2000 Users Manual

When an I/O state change occurs (open to close or close to open) for longer than the trigger time, the new condition will be reported to the web site using Report # 1. (This report reports all 12 IED points plus registers 1,2,and 3.) Entering a value in the Description field is optional and for your convenience only. It is saved on the hard disc with the profile, but is not passed to the unit or to the web site.

Read Analog Registers This screen shows the 20 analog registers that can be monitored from a Modbus IED. Double click on one of the rows to open it. Use this screen to configure the register reads.

The Unit # and Address represent the slave location to be polled for data by the Master Mode and they are not used if the M2000 is configured as a slave device, since the unit never polls the Master device for data.

For Master mode devices only: Modbus rules say that Holding Registers are stored in locations 40001-49999 and Input Registers are stored in 30001-39999. The unit can read either type. Either one will be read as a value from 0 65535. The data read from each register may represent an actual 16-bit value such as a temperature or pressure or it may represent 16 bits of I/O data. If you request data from an address of 40001-49999, the unit will request a Holding Register Value from the IED (Modbus function 3). If you enter an address of 30001-39999, the unit will request an Input Register Value from the IED (Modbus function 4). The memory addresses must be selected to match those that are present in the Modbus device. The Unit # is the slave unit #. It can be set from 1-32. There is no broadcast address 0.

M2M Communications

18

M2000 Users Manual

If the Enabled box is clicked, the address will be read and tested. If the Enabled box is not checked, this address will not be read, tested, or reported. There are three setpoints (limits) available for each register reading. You can enter one, two, or three limits. If you enter only one limit, put it in limit 1. If you enter two limits, use limits 1 & 2. An entry of 0 means that setpoint is disabled. If the actual value read becomes equal to or greater than a setpoint, it will change into the higher range. If it drops below a setpoint, it will be reported in the lower range. Three setpoints creates four ranges. For example, if monitoring a temperature, you might define four ranges called cold, cool, warm, and hot. When a range change occurs for longer than the trigger time, both the new range and the new value will be reported to the web site.

SP# 1 SP# 2 SP# 3 --------------------- | --------------------- | -------------------- | --------------------Range 1 Range 2 Range 3 Range 4 Cold Cool Warm Hot

One data packet contains enough data to report all of the 12 I/O points plus three register values and current range. When registers 1, 2, or 3 change range, registers 1, 2, and 3 will be reported When registers 4, 5, or 6 change range, registers 4, 5, and 6 will be reported When registers 7, 8, or 9 change range, registers 7, 8, and 9 will be reported When registers 10, 11, or 12 change range, registers 10, 11, and 12 will be reported When registers 13, 14, or 15 change range, registers 13, 14, and 15 will be reported When registers 16, 17, or 18 change range, registers 16, 17, and 18 will be reported When registers 19 or 20 change range, registers 18, 19, and 20 will be reported

You may want to group your registers together if they have similar or related meanings to you. Then, if one of them changes, all three will be reported together.

The deadband, or hysterisis, value can be used to prevent a value form oscillating between ranges. It is subtracted from a setpoint only when the range is decreasing. Example: Say that setpoint #1 is 1000 and the deadband is 50. If the value is initially less than 1000, the range will = 1. If the value increases to equal or above 1000, the range will change to #2 and the new value will be reported to the web site. To return to range #1, the value must drop to below 1000-50 = 950.

Entering a value in the Description field is optional and for your convenience only. It is saved on the hard disc with the profile, but is not passed to the unit or to the web site.

M2M Communications

19

M2000 Users Manual

Read Bit Packed Registers This screen shows the 4 bit packed registers that can be monitored from a Modbus IED. Double click on one of the rows to open it. Use this screen to configure the register bit reads.

Any holding or input register can be tested as a bit-packed register. In this mode, all 16 bits can be independently tested as discrete bits. When a bit changes, and a specified alarm condition exists, the device will report the event to the M2M Network Operation Center. The M2000 can test up to four bit-packed holding registers from Modbus slave devices. The Unit # and Address represent the slave location to be polled for data by the Master Mode and they are not used if the M2000 is configured as a slave device, since the unit never polls the Master device for data.

M2M Communications

20

M2000 Users Manual

Alarm conditions can be specified for each bit and can be defined as an open close (1 0), close open (0 1), or both. A separate and independent trigger time can be specified for each direction, in seconds, from 1-65535. When any monitored bit change is detected for the trigger time, a report will be made.

For Master mode devices only: The M2000 Master will repeatedly read the requested registers at a specified polling rate of every 1240 seconds. The M2000 uses Modbus command 03, Read Holding Registers, to read the binary contents of holding registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 40001-49999 The memory addresses must be selected to match those that are present in the Modbus device. The Unit # is the slave unit #. It can be set from 1-32. There is no broadcast address 0.

If the Enabled box is clicked, the address will be read and tested. If the Enabled box is not checked, this address will not be read, tested, or reported. Entering a value in the Description field is optional and for your convenience only. It is saved on the hard disc with the profile, but is not passed to the unit or to the web site. When any monitored bit in any bit packed register changes, all four bit packed registers will be reported at one time.

M2M Communications

21

M2000 Users Manual

Write Registers for M2000 Master devices This screen shows the 20 values that can be written to a Modbus Slave. Double click on one of the rows to open it. Use this screen to configure the writes.

Write functions are based on predefined definitions. There are several variations. The following screen shows how a write function can be defined to write a specific (fixed) value to a Modbus register. This is useful for remotely controlling a slave device, or in this case, changing a Setpoint #1 to 220.

At the web site, you can create your own Custom Commands. Label each command with the same description (that makes sense to the user) and specify the command number that matches the locally defined Write Function. When the command number is sent from the web site, the corresponding command (the write that you have defined locally) will be sent to the slave device.

M2M Communications

22

M2000 Users Manual

Another Example: Set up Command # 3 to: Write a value of 1 to slave unit # 4, address 0123. We will assume that this write will turn on a Pump # 5. You will assign the label Turn on Pump # 5 to Command # 3 at the web site and locally using this Write Register tab.

Modbus rules say that Single Coils (outputs) are written to locations 00001-99999 and registers written to 40001-49999. The M2000 can write to either type of data to the IED. Outputs can be written as a 0 or 1. (The meaning of a 0 or 1 will be determined by the IED). Registers can be written as a value from 0 65535. If you enter an address of 40001-49999, it will write a single register value to the IED (Using Modbus function 6). If you enter an address of 00001-09999, it will write a single output to the IED (Using Modbus function 5).

In addition to writing a fixed value to a Modbus register, it is also possible to read a value from one device or address and then write it to a specified output or holding register in another device or address.

This is useful for transferring data between slave devices. In some cases, the data that is being moved may also be used to trigger a reportable event in the M2000. This predefined read and write operation can be remotely triggered at any time from the web site (or from the Local Programmer). In addition, if the Enable Automatic Write button is clicked, the M2000 will repeatedly read and write the data at every polling time (every 1-240 seconds). This results in a constantly updating operation. If the write data is to be read from another device, there are four ways to do it:

M2M Communications

23

M2000 Users Manual

1) The M2000 uses Modbus command 01, Read Coil Status, to read the ON/OFF status of discrete outputs. Discrete outputs can be read from unit numbers ranging from 1-32 and addresses of 00001-09999. 2) The M2000 uses Modbus command 02, Read Input Status, to read the ON/OFF status of discrete inputs. Discrete inputs can be read from unit numbers ranging from 1-32 and addresses of 10001-19999. 3) The M2000 uses Modbus command 03, Read Holding Registers, to read the binary contents of holding registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 40001-49999. 4) The M2000 uses Modbus command 04, Read Input Registers, to read the binary contents of input registers. Registers can be read from unit numbers ranging from 1-32 and addresses of 30001-39999. Regardless of whether the write data is fixed or dynamic, it is written in one of two ways: 1) The M2000 uses Modbus command 05, Force Single Coil, to set a single output to ON or OFF. Control outputs (0 or 1) can be written to unit numbers ranging from 1-32 and addresses of 00001-09999. 2) The M2000 uses Modbus command 06, Preset Single Register, to write to a single holding register. Registers can be written in unit numbers ranging from 1-32 and addresses of 40001-49999.

The Unit # is the slave unit #. It can be set from 1-32. There is no broadcast address 0. Entering a value in the Description field is optional and for your convenience only. It is saved on the hard disc with the profile, but is not passed to the unit or to the web site. If the Enabled box is clicked, the address will be written to when requested. If the Enabled box is not checked, it will not.

Time Scheduled Reports This screen allows you to enable any of the reports (except the Power On call) as time scheduled reports. Double click on one of the rows to open the selected report. Use this screen to enable the time-scheduled reports.

M2M Communications

24

M2000 Users Manual

Checking the Include with the Report All website command will also add the report to the list of reports that are reported with one click of the Report All button.

Any of the reports can be scheduled at a predefined frequency. When time scheduled reports are enabled, the M2000 will call at set intervals to report its current readings, with the first call coming at the specified amount of time after the unit is powered up. Call frequencies can be set anywhere from once every one hour to once every 240 hours (10 days). To schedule a report at a specific time of day, fill in the frequency, but leave the Enabled box unchecked and then use the web site to initiate the first call at a specific time. All calls that follow the initial call will be at the programmed frequency and starting at that point. Note that all daily status or heartbeat type calls should be scheduled during the off-peak hours (10 pm to 3 am).

Configuration This screen allows you to define the system configuration settings.

Power Mode The M2000 always operates in the normal (always on) mode so this function is disabled. Daily Call Limit To reduce the number of calls that might result from over-active inputs or power cycling conditions, the number of event-based calls per day can be limited. Time scheduled calls and user requested status calls will continue to be placed even after this limit has been reached. The daily call limit should normally be selected so that the total number of calls is limited to no more than 20 calls per day and no more than 400 calls per month. The daily limit can be set from 1 to 20. The unlimited selection is for test and demo purposes only. The factory default setting is 10.

M2M Communications

25

M2000 Users Manual

Modbus Settings All settings that control how the M2000 communicates with Modbus device(s) are selected from this window. These settings must match those of the Modbus device(s) or the devices will not communicate. The M2000 Master mode can communicate in either RTU or ASCII mode. The M2000 Slave mode always operates in the RTU mode. The parity setting can be Even, Odd, or None. The RS232 / RS485 selection chooses which serial port will be used. The baud rate can be set to: 1200, 2400, 4800, 9600, 19200, or 38400 bps.

There are also some not-so-obvious details that should be adhered to on the Modbus device: If RTU mode is used, the Modbus device should be set to 8 data bits and 1 start bit. If ASCII mode is used, the Modbus device should be set to 7 data bits & 1 start bit. If Even or Odd parity is selected, there is always 1 stop bit. If No parity is selected, there will be normally be 2 stop bits. However, this can be set to 1 stop bit if necessary

Master / Slave Selection The M2000 can be configured as either for Master or Slave mode. This is a very significant choice and affects many other parts of the M2000 operation. As an intelligent Modbus Master, the M2000 polls and reads data from Modbus slave devices. It then compares this data to customer-defined setpoints and automatically reports when a specified condition exists or when one of the limits is exceeded. As an intelligent Modbus Slave, the M2000 is configured to accept commands and data from a Modbus Master device. The M2000 will then compare the data to customer-defined setpoints and automatically report when a specified condition exists or when one of the limits is exceeded. The primary difference between the Intelligent Modbus Master and Intelligent Modbus Slave is in how the transfer of data is initiated. Once the data is inside the M2000, it is analyzed and reported in the same way. As a Master device, the M2000 supports both the RTU and the ASCII modes. As a Slave device, the M2000 supports only the RTU mode. If Slave mode is selected, you should also specify the slave unit # address that is to be assigned to the M2000. If the master mode is selected, there is no unit #.

M2000 Master Polling Frequency The M2000 Master can read up to 12 digital inputs or outputs and up to 20 binary and 4 bitpacked registers from Modbus slave devices. The M2000 will read the requested values at a specified polling rate of every 1-240 seconds.

M2M Communications

26

M2000 Users Manual

Note that there is an important relationship between the polling frequency and the selected trigger times. There are several ways that you can set up these two times to give undesired results. (1) The IED is read only at the specified polling frequency. Changes that occur between the readings will not be detected. If the reading is being made at a rate of once every 30 seconds, a change lasting 5-10 seconds can easily be missed. (2) Assume again that the IED values are read at a polling frequency of once every 30 seconds. If a trigger time is set to a lower value such as 5 seconds, the trigger time for any detected change will always expire 5 seconds after a reading is taken because the value is only being tested once every 30 seconds. But in reality, the alarming value may have only existed for the one second when it was being read. The easy and correct solution is to make the polling frequency much shorter than the trigger times. For example, if the trigger times were set to one minute, a polling frequency of 10 seconds would give you 6 readings during the testing period. On the other hand, the trigger times should be set long enough so that all registers and I/O points can be read before the next read starts. If a large number of readings are being taken at a slow baud rate like 1200 bps, it can take several seconds to read them all. It is easy to watch the bottom LED (LED3) and see that all how long all the readings are taking.

Report RSSI to Modbus Register The M2000 Master can be configured to send the latest Radio Strength Signal Indication to a Modbus slave device and address. The RSSI value will typically range from 8-40 where: < 8 8-12 13-16 17-24 25-32 > 33 Inadequate Weak Adequate Good Excellent Awesome

To convert the RSSI to dB, add the number to 114.

Cellular Channel Selection The M2000 can be configured to operate on either cellular channel A or B. In addition, it can be programmed to automatically select the correct channel for control channel operation. If configured for auto selection, the unit will determine the proper cellular channel for operation each time it is powered on. The process starts by sending a registration call to the M2M Comm web server on Channel B (the most commonly used channel). If the unit receives an acknowledgement from the web server, it will remain on that channel. However, if after one minute, it has not received an acknowledgement, it will repeat the process on Channel A. The program will continue to alternate channels until an acknowledgement is received. This cycle will normally find the correct channel on the first try and will repeat only once. If it continues, the web site is not receiving or responding to the units registration call.

M2M Communications

27

M2000 Users Manual

The unit is shipped in the Automatic mode. For fixed locations, it is usually best to determine the correct cellular channel and set it to that. This will eliminate the cost of an ACK call at every power on. Clicking the Default button will restore the factory default configuration settings.

M2000 Slave Mode Commands

As a slave device, the M2000 will never attempt to poll or query a Master device for data. All data transfers are initiated by the Master device. As an Intelligent Modbus Slave, the M2000 is configured to receive commands and data from a Modbus Master device. The M2000 will then compare the data to customer-defined setpoints and automatically report when a specified condition exists or when one of the limits is exceeded. The primary difference between the Intelligent Modbus Master and Intelligent Modbus Slave is in how the transfer of data is initiated. Once the data is inside the M2000, it is analyzed and reported in the same way. In the Web-to-Wireless Slave Modem mode, the M2000 can be used as a completely flexible wireless modbus-to-cellular-to-web communication system, much like a simple modem. A Modbus Master device can load data into the M2000 and issue a transmit command. The M2000 does not analyze or format this data; it simply transmits the data to and from the web server. When the M2000 is configured as a slave device, it can be used in both the: (1) Intelligent mode for automatic analysis and reporting and (2) Web-to-Wireless modem mode. There are specific commands that are used for each mode and they do not conflict with each other. For example, some data values can be loaded into the M2000 to be monitored and tested, while other data can be directly transmitted to the web server without further processing or interpretation. Note: Some of the data shown in the Local Configuration program is only used when in the Master Mode. The IED I/O, Read Register, and Read Register Bits windows include a Unit # and Address. These are the data addresses that are to be polled by the Master Mode and are not used in the slave mode, since the unit never polls the Master device for data. The Write Register window is used to define Write operations from the M2000 Master to slave devices and is disabled if the M2000 is configured as a slave device.

M2M Communications

28

M2000 Users Manual

An Explanation of Addressing in the M2000 Slave

In the world of Modbus, the address range indicates the type of data that is being used. The M2000 slave supports several types of data and so several address ranges. The following table shows the relevant Modbus memory ranges and the associated data types, as well as the equivalent addressing in the M2000: The following values are in the decimal format.

Modbus Address 00001 09999 10001 19999 30001 39999 40001 49999

Data Type Discrete Outputs 0 or 1 Discrete Inputs 0 or 1 Input Registers 16 bit Holding Registers 16 bit

M2000 Address 0 - 9998 0 - 9998 0 - 9998 0 - 9998

In each case, to convert the Modbus address to the M2000 address, subtract the ten thousands digit and then subtract one. For example, a Modbus address of 40002 will equal a M2000 address of: 40002 40000 1 = 0001. This is the standard method that Modbus devices use to send addresses, so if you are using a standard Modbus PLC, controller, or other device, this conversion will probably be done automatically. It may appear that the M2000 is storing several types of data at the same address, but dont worry! The function number that is used (such as 3, 5, 6, or 16) also tells the M2000 where to physically store the data) If you are writing a custom driver and dont care about Modbus conventions, simply send the M2000 address.

M2M Communications

29

M2000 Users Manual

M2000 Slave Mode Command Summary

The M2000 supports several write and read functions that can be used to reliably send and receive data to and from the www.m2mcomm.com web server.

Sending & Receiving Data with the Web-to-Wireless Modem M2000 Address Write Functions Using Modbus Command # 6 or 16 Load Transmit Data into the M2000 Send Data to Web Server Now Clear Received Data Memory 00 11 12 14 40001 40012 40013 40015 Equivalent Modbus Address

Read Functions Using Modbus Command # 3 Read Transmit Data from the M2000 Read the Transmit Result Code Read RSSI (Radio Signal Strength) Read M2000 Status Read Received Data 00 11 12 16 17 18 37 40001 40012 40013 40017 40018 40019 40038

Automatic Analysis and Reporting Mode Commands Equivalent Modbus Address 00001 00012 or 10001 10012

Write Functions Write Digital I/O Data into the M2000 for auto analysis & reporting Using Modbus Command # 5 Write Register Values into the M2000 for auto analysis & reporting Using Modbus Command # 6 or 16 Write Bit Packed Register Values into the M2000 for auto analysis & reporting Using Modbus Command # 6 or 16

M2000 Address 00 11

2000 2019

42001 42020

2020 2023

42021 42024

The next section explains the operation of each of these functions.

M2M Communications

30

M2000 Users Manual

Sending & Receiving Data with the Web-to-Wireless Slave Modem

Load Transmit Data into the M2000 M2000 Address 0000 0011 Modbus Address 40001 40012

The cellular modem radio always transmits 24 numerical digits. Therefore all data to be transmitted should be loaded into the M2000 as a string of 24 digits. Use this command to load the digits into the M2000 prior to sending them. A digit = 0-9 only. No hex characters (A-F) or * or # are allowed All data transmissions are 24 digits long. The transmit data is cleared to 0 at power up. If you have not specifically cleared or loaded all of the transmit data registers, this function will send whatever was last stored in those registers. A Modbus register is equal to 16 bits, or 2 bytes The digits are sent to the M2000 as two digits per register (one digit per byte) The transmit data is stored as 24 digits (in 12 registers) starting at the M2000s memory address 0000 (corresponds to Modbus address 40001). The 24 digits can be loaded in one single command or can be loaded as individual or multiple registers (with 2 digits per register). The data can be loaded all at once or over time as physical events occur. The data can remain in the M2000 indefinitely (but is not saved during a power failure). The data that has been loaded into the M2000 can be sent to the web site at any time with the Send Transmit Data command. It can also be requested from the web site with a single web site command or it can be set up as a time scheduled report. As a time scheduled report, whatever is loaded into the M2000 will be sent to the web site at the specified frequency (every 1-240 hours). This data report is referred to as Report #11 or Modem Report at the web site and in the local programmer utility. The M2000s unit (slave) address can be set to any number from 1-32 Use Modbus function # 6 or 16 to write the registers to the M2000.

Example #1 of Load Transmit Data - using Modbus function 16 Pass 24 digits of data to the slave M2000 (addressed here as unit # 17 or 11 Hex) The data is string is: 123456789012345678901234 There are actually 24 digits packed in 12 data registers. Field Name Slave Address Function Starting Address Hi Example (in hex) 11 10 00 comments unit # 17 in decimal command # 16 in decimal

M2M Communications

31

M2000 Users Manual

Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data 1 Hi Data 1 Lo Data 2 Hi Data 2 Lo Data 3 Hi Data 3 Lo Data 4 Hi Data 4 Lo Data 5 Hi Data 5 Lo Data 6 Hi Data 6 Lo Data 7 Hi Data 7 Lo Data 8 Hi Data 8 Lo Data 9 Hi Data 9 Lo Data 10 Hi Data 10 Lo Data 11 Hi Data 11 Lo Data 12 Hi Data 12 Lo Error Check (LRC or CRC)

00 00 0C 18 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 --

12 registers in decimal 24 total bytes in decimal

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No of Registers Hi No of Registers Lo Error Check (LRC or CRC) Example (hex) 11 10 00 00 00 0C --

(2 bytes)

Example #2 of Load Transmit Data -- Using Modbus function 16: Pass 4 digits of data to address 06 (Modbus address 40007) of the M2000 addressed as unit # 1. The data string is: 6789 Field Name Slave Address Example (in hex) 01 comments unit # 1

M2M Communications

32

M2000 Users Manual

Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data 1 Hi Data 1 Lo Data 2 Hi Data 2 Lo Error Check (LRC or CRC) Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No of Registers Hi No of Registers Lo Error Check (LRC or CRC)

10 00 06 00 02 04 06 07 08 09 --

command # 16 in decimal starting address = 6 2 registers in decimal 4 total bytes in decimal

(2 bytes)

Example (hex) 01 10 00 06 00 02 --

(2 bytes)

Example #3 of Load Transmit Data - using Modbus function 6: Pass one register of data to address 0001 (Modbus address 40002) of the M2000 slave addressed as unit # 9. The data string is 2345. Uses Modbus function 6. Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Normal Response: Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 09 06 00 01 23 45 -Example (in hex) 09 06 00 01 23 45 -comments unit # 9 command # 6 address = 0001

(2 bytes)

(2 bytes)

M2M Communications

33

M2000 Users Manual

Send Transmit Data to the Web Server M2000 Address 00012 Modbus Address 40013

Command the M2000 to transmit the previously loaded data to the web server. To initiate a transmission, load a value of 5A5A into register 0012, which is Modbus address 40013. All data transmissions are 24 digits long. The transmit data registers are cleared to 0 at power up. If you have not specifically loaded all of the transmit data registers, this function will send whatever was last in those registers. The M2000 slave unit address can be set to any number from 1-32 Its a good idea to check the Radio Signal Strength Indicator (RSSI) before transmitting. The unit will not transmit unless the RSSI is > 7. The command register can be combined and loaded as a 13th register in the Load Transmit Data function. This allows you to issue one command to load and send the data. Use Modbus function # 6 or 16

Example #1 of Send Transmit Data - Using Modbus function 16: Pass the transmit command, 5A5A, to address 0012 (Modbus address 40013) of the M2000 slave unit # 1. Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data Hi Data Lo Error Check (LRC or CRC) Example (hex) Comments 01 10 00 0C 00 01 02 5A 5A -Slave Unit # 1

Starting Address 12 in decimal Write 1 register 2 total bytes in decimal

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Error Check (LRC or CRC) Example (hex) 01 10 00 0C 00 01 --

(2 bytes)

M2M Communications

34

M2000 Users Manual

Example #2 of Send Transmit Data - using Modbus function 6: Pass the transmit command, 5A5A, to address 0012 (Modbus address 40013) of the M2000 slave unit # 9. Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (in hex) 09 06 00 0C 5A 5A -comments unit # 9 command # 6 address = 0012

(2 bytes)

Normal Response: Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 09 06 00 0C 5A 5A --

(2 bytes)

M2M Communications

35

M2000 Users Manual

Read Transmit Data from the M2000 M2000 Address 00000 00011 Modbus Address 40001 40012 Use this command to read back the transmit data that you have previously loaded. Digits are packed two to a register The M2000 slave unit address can be set to any number from 1-32. Transmit Data is stored in 12 registers starting at memory address 0000, which is Modbus address 40001. One or more (up to 13) registers can be read using this function. Just specify the starting register and the number of registers to be read. The 12 registers of transmit data plus the Transmit Result Code can be read with one command by reading 13 registers starting at register 0000. Use Modbus function #3 (Read Holding Registers)

Example of Read Transmit Data: Read thirteen registers (12 registers of transmit data plus the result code) from unit # 1 Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Points, Hi No. of Points, Lo Error Check (LRC or CRC) Example (hex) Comments 01 03 00 00 00 0D -Unit # 1

Starting Address Read 13 registers (26 digits) (2 bytes)

Normal Response: Field Name Slave Address Function Byte Count Data Hi (Register 40001) Data Lo (Register 40001) Data Hi (Register 40002) Data Lo (Register 40002) Data Hi (Register 40003) Data Lo (Register 40003) Data Hi (Register 40004) Data Lo (Register 40004) Data Hi (Register 40005) Data Lo (Register 40005) Data Hi (Register 40006) Example (hex) 01 03 1A 01 02 03 04 05 06 07 08 09 00 01 Comments

26 bytes of data

M2M Communications

36

M2000 Users Manual

Data Lo (Register 40006) Data Hi (Register 40007) Data Lo (Register 40007) Data Hi (Register 40008) Data Lo (Register 40008) Data Hi (Register 40009) Data Lo (Register 40009) Data Hi (Register 40010) Data Lo (Register 40010) Data Hi (Register 40011) Data Lo (Register 40011) Data Hi (Register 40012) Data Lo (Register 40012) Data Hi (Register 40013) Data Lo (Register 40013) Error Check (LRC or CRC)

02 03 04 05 06 07 08 09 00 01 02 03 04 00 00 --

Result Code = 0 Result Code =0 (2 bytes)

M2M Communications

37

M2000 Users Manual

Read Transmit Result Code M2000 Address 0012 Modbus Address 40013 After sending data, test the Transmit Result Code to verify a successful transmission. The Transmit Result Code is a two digit number stored in one register at memory address 0012 -- which is Modbus Address 40013. After transmitting data, the M2000 will change the transmit command (5A5A) to a Result Code. This may take from 4-12 seconds depending on how long it takes for the cell tower to acknowledge the transmission. If the transmission fails, the M2000 will automatically begin a series of retries. This retry process can take up to 5 minutes if all the retries fail. During this time, the unit is busy and will not respond to Modbus queries. The 12 registers of transmit data plus the Transmit Result Code can be read with one command by reading 13 registers starting at register 0000. Use Modbus function #3 (Read Holding Registers)

Transmit Result Codes: Transmit Successful Transmit Failed 5 times Aborted Not sent - Daily Call Limit has been reached Not Sent - Radio is Disabled Inadequate RSSI Waiting for better signal 0001 0003 0020 0021 0023

Example of Read Transmit Result Code Read one register # 0015 from unit # 32 (20 hex) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Points, Hi No. of Points, Lo Error Check (LRC or CRC) Example (hex) 20 03 00 0C 00 01 -Comments

12 decimal

(2 bytes)

Normal Response: Field Name

(Transmit Successful) Example (hex) 20 03 02 00 01 --

Slave Address Function Byte Count Data Hi (Register 40013) Data Lo (Register 40013) Error Check (LRC or CRC)

Transmit Successful (2 bytes)

M2M Communications

38

M2000 Users Manual

Read RSSI M2000 Address 0016 Modbus Address 40017 RSSI (Radio Signal Strength Indicator) is a two digit decimal (BCD) number stored at memory address 0016, which is Modbus Address 40017 The Master Modbus device can read the RSSI at any time. The RSSI number can be converted to db by adding it to 114. The meaning of the RSSI is: Decimal <8 8 -15 16-19 20-27 28-35 >35 Description Inadequate Weak Adequate Good Excellent Awesome Result Unit will not transmit Ok Ok Ok Ok Ok

There may be a time delay of up to one second before the reply message. Use Modbus function #3 (Read Holding Registers)

Example of Read RSSI Read one register # 0016 from unit # 02 (02 hex) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Points, Hi No. of Points, Lo Error Check (LRC or CRC) Example (hex) 02 03 00 10 00 01 -Comments

16 decimal

(2 bytes)

Normal Response: Assuming RSSI = 21 hex Field Name Slave Address Function Byte Count Data Hi (Register 40017) Data Lo (Register 40017) Error Check (LRC or CRC) Example (hex) 02 03 02 00 33 --

33 decimal = -81 dB (2 bytes)

M2M Communications

39

M2000 Users Manual

Read M2000 Status M2000 Address 0017 Modbus Address 40018 The M2000 Status Code is a two digit number stored at memory address 0017, which is Modbus Address 40018 The Master Modbus device can read the Status Code at any time to determine whether or not new data has arrived from the web site. Reading the received data will clear it to 0. The codes are: 00 02 Waiting for instructions, No new data received New data has been received from the web site

Use Modbus function #3 (Read Holding Registers)

Example of Read M2000 Status Read one register # 0017 from unit # 01 (01 hex) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Points, Hi No. of Points, Lo Error Check (LRC or CRC) Example (hex) 01 03 00 11 00 01 -Comments

17 decimal

(2 bytes)

Normal Response: (New data received) Field Name Slave Address Function Byte Count Data Hi (Register 40018) Data Lo (Register 40018) Error Check (LRC or CRC) Example (hex) 01 03 02 00 02 --

New data has been received (2 bytes)

M2M Communications

40

M2000 Users Manual

Read Data Received from the Web Server M2000 Address 0018 - 0037 Modbus Address 40019 - 40038

From the M2M web server, up to 300 unique commands and data values can be sent to the M2000 Slave device, and then passed to the Master device. Each of these data transmissions counts as one message toward your monthly billing, so they should be used carefully. Each Received Data packet from the web server is a single 3-digit number ranging from 100-399. Multiple data packets can be sent as required for control or configuration purposes. The M2000 will store the last twenty Received Data packets starting at memory location 18 (Modbus 40019). One register (two bytes) is used to hold one Received Data packet. The data is right justified, so the most significant nibble of the first byte will always = 0, such as 0123. At power-up, the received data memory will be cleared to 0. If the application expects data to be sent from the web site, the master should check regularly for new data from the web site using the Read M2000 Status message. If there is a new (unread) data message, the status will equal 2. Any full or partial read of the received data will clear the M2000 status to 0. After the master reads the Received Data, it should issue a command to Reset the Received Data. This will zero all 20 registers of Received Data, reset the memory pointer to the first register, and clear the M2000 status message. This is the only way to reset the pointer. The M2000s storage buffer is filled in a circular manner. If the 20th memory location becomes full, the pointer will roll over to the first register so that the next Received Data will be stored at the first register, overwriting existing data. The M2000 slave unit address can be set to any number from 1-32. One or more (up to 20) registers can be read using this function. Just specify the starting register and the number of registers to be read. Any read of any data will reset the M2000 status to 0. Use Modbus function #3 (Read Holding Registers)

M2M Communications

41

M2000 Users Manual

Example #1 of Read Received Data: Read 20 received data packets in 20 registers # 0018-0037 from unit # 1 starting at address 0018 (Modbus address 40019) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers, Hi No. of Registers, Lo Error Check (LRC or CRC) Example (hex) Comments 01 03 00 12 00 14 --

18 decimal 20 decimal (2 bytes)

Normal Response: Field Name Slave Address Function Byte Count Data Hi (Register 40019) Data Lo (Register 40019) Data Hi (Register 40020) Data Lo (Register 40020) Data Hi (Register 40021) Data Lo (Register 40021) Data Hi (Register 40022) Data Lo (Register 40022) Data Hi (Register 40023) Data Lo (Register 40023) Data Hi (Register 40024) Data Lo (Register 40024) Data Hi (Register 40025) Data Lo (Register 40025) Data Hi (Register 40026) Data Lo (Register 40026) Data Hi (Register 40027) Data Lo (Register 40027) Data Hi (Register 40028) Data Lo (Register 40028) Data Hi (Register 40029) Data Lo (Register 40029) Data Hi (Register 40030) Data Lo (Register 40030) Data Hi (Register 40031) Data Lo (Register 40031) Data Hi (Register 40032) Data Lo (Register 40032) Data Hi (Register 40033) Data Lo (Register 40033) Example (hex) Comments 01 03 28 00 01 02 03 00 04 01 06 02 03 03 04 00 77 22 01 00 85 01 23 01 11 02 03 00 04 01 06 00 03

40 bytes in decimal Received Data 1 = 0001 Received Data 2 = 0203 Received Data 3 = 0004 Received Data 4 = 0106 Received Data 5 = 0203 Received Data 6 = 0304 Received Data 7 = 0077 Received Data 8 = 0221 Received Data 9 = 0085 Received Data 10 = 0123 Received Data 11 = 0111 Received Data 12 = 0203 Received Data 13 = 0004 Received Data 14 = 0106 Received Data 15 = 0003

M2M Communications

42

M2000 Users Manual

Data Hi (Register 40034) Data Lo (Register 40034) Data Hi (Register 40035) Data Lo (Register 40035) Data Hi (Register 40036) Data Lo (Register 40036) Data Hi (Register 40037) Data Lo (Register 40037) Data Hi (Register 40038) Data Lo (Register 40038) Error Check (LRC or CRC)

02 04 02 39 01 91 02 15 02 45 --

Received Data 16 = 0204 Received Data 17 = 0239 Received Data 18 = 0191 Received Data 19 = 0215 Received Data 20 = 0245 (2 bytes)

Example #2 of Read Received Data: Read 2 received data packets in 2 registers at # 0018 from unit # 1 starting at address 0018 (Modbus address 40019) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers, Hi No. of Registers, Lo Error Check (LRC or CRC) Example (hex) Comments 01 03 00 12 00 02 --

18 decimal Read 2 registers (2 bytes)

Normal Response: Field Name Slave Address Function Byte Count Data Hi (Register 40019) Data Lo (Register 40019) Data Hi (Register 40020) Data Lo (Register 40020) Error Check (LRC or CRC) Example (hex) Comments 01 03 04 02 91 02 03 --

4 bytes Received Data 1 = 0291 Received Data 2 = 0203 (2 bytes)

M2M Communications

43

M2000 Users Manual

Clear Received Data Memory M2000 Address 0014 Modbus Address 40015 Command the M2000 to zero all Received Data registers and reset the memory pointer to the first register. After the master reads a Received Data packet from the web site, it should issue a command to Reset the Received Data. This will zero all 10 registers of Received Data, reset the memory pointer to the first register, and clear the M2000 status message. To initiate the Reset function, load a value of 0505 into register 0014 which is Modbus address 40015 The M2000 slave unit address can be set to any number from 1-32 See Read Received Data for additional information on this function Use Modbus function # 6 or 16

Example #2 of Clear Received Data: -- Using Modbus function # 16 to slave unit # 19 (13 hex) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data Hi Data Lo Error Check (LRC or CRC) Example (hex) Comments 13 10 00 0E 00 01 02 05 05 -Unit # 19 in decimal

Address = 0014

2 total bytes in decimal

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Error Check (LRC or CRC) Example (hex) 13 10 00 0E 00 01 --

(2 bytes)

M2M Communications

44

M2000 Users Manual

Example #2 of Clear Received Data - using Modbus function 6:

Pass the Clear Data command, 0505, to address 0014 (Modbus address 40015) of the M2000 slave unit # 9.

Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC)

Example (in hex) 09 06 00 0E 05 05 --

comments unit # 9 command # 6 address = 0014

(2 bytes)

Normal Response: Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 09 06 00 0E 05 05 --

(2 bytes)

M2M Communications

45

M2000 Users Manual

Writing Data to the Intelligent M2000 Slave for Automatic Analysis and Reporting
Write Digital I/O Data to the M2000 M2000 Address 00 11 Modbus Address 00001 00012

Use this command to set or clear a single I/O bit in the M2000 for analysis and automatic alarm reporting Up to 12 bits can be loaded into the M2000 for auto monitoring & analysis. I/O data consists of 1-bit values, 0 or 1. All data is cleared to 0 at power up. The M2000s unit (slave) address can be set to any number from 1-32 Use Modbus function # 5 to write a 0 or 1 to the M2000 bit. Sending a value of FF 00 sets one bit to 1 or ON. Sending a value of 00 00 clears one bit to 0 or OFF.

Example of Load I/O Bits: Set I/O bit #4 =1 in the M2000 slave addressed as unit # 1. Field Name Slave Address Function Starting Address Hi Starting Address Lo Force Data Hi Force Data Lo Error Check (LRC or CRC) Example (in hex) 01 05 00 03 FF 00 -comments unit # 1 command # 5 starting address = 0003 FF00 sets the bit to 1 (2 bytes)

The Normal Response is an echo of the query: Field Name Slave Address Function Starting Address Hi Starting Address Lo Force Data Hi Force Data Lo Error Check (LRC or CRC) Example (hex) 01 05 00 03 FF 00 -unit # 1 command # 5 starting address = 0003 FF00 sets the bit to 1 (2 bytes)

M2M Communications

46

M2000 Users Manual

Write Register Data to the M2000 M2000 Address 2000 2019 Modbus Address 42001 42020 Use this command to load operational data into the M2000 registers for automatic analysis and alarm reporting Up to 20 registers can be loaded into the M2000 for monitoring & analysis. All register data consists of 16 bit values = two bytes. (0000-FFFF hex) All data is cleared to 0 at power up. The M2000s unit (slave) address can be set to any number from 1-32 Use Modbus function # 16 to write either a single or multiple registers to the M2000. Modbus function # 6 can be used to write a single register to the M2000.

Note that all M2000 automatic alarms have both setpoints and a trigger time. For example, the M2000 can be configured so that a range change may trigger a report if a setpoint is crossed for more than one minute. If this is the case, it would be advisable for the Master device to update the monitored value to the M2000 several times per minute. If you were to only update the value say, once every 2 minutes, then every momentary change that is reported to the M2000 would last more than one minute and would be reported.

Example #1 of Write Register Data

-- Using Modbus function 16

Pass 20 register values (40 bytes) of data to address 2000 thru 2019 (Modbus register addresses 42001 thru 42020) in the slave M2000 (addressed here as unit # 17 or 11 Hex). Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data 1 Hi Data 1 Lo Data 2 Hi Data 2 Lo Data 3 Hi Data 3 Lo Data 4 Hi Data 4 Lo Data 5 Hi Data 5 Lo Data 6 Hi Data 6 Lo Data 7 Hi Data 7 Lo Data 8 Hi Data 8 Lo Example (in hex) 11 10 07 D0 00 14 28 01 2C FF 04 05 CD 07 08 1B 00 01 E2 B3 04 05 06 comments unit # 17 decimal command # 16 decimal starting address = 2000

20 registers 40 total bytes

M2M Communications

47

M2000 Users Manual

Data 9 Hi Data 9 Lo Data 10 Hi Data 10 Lo Data 11 Hi Data 11 Lo Data 12 Hi Data 12 Lo Data 13 Hi Data 13 Lo Data 14 Hi Data 14 Lo Data 15 Hi Data 15 Lo Data 16 Hi Data 16 Lo Data 17 Hi Data 17 Lo Data 18 Hi Data 18 Lo Data 19 Hi Data 19 Lo Data 20 Hi Data 20 Lo Error Check (LRC or CRC) Normal Response:

07 08 09 00 01 02 03 A4 05 06 07 08 C9 10 1D 02 03 04 05 06 07 08 09 1F --

(2 bytes)

Field Name Slave Address Function Starting Address Hi Starting Address Lo No of Registers Hi No of Registers Lo Error Check (LRC or CRC)

Example (hex) 11 10 07 D0 00 14 --

(2 bytes)

Example #2 of Write Register Data

- Using Modbus function 16:

Pass 2 registers of data to address 2012 & 2013 (Modbus address 42013 & 42014) of the M2000 slave addressed as unit # 1. The data registers are: 678A and 12B0. Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Example (in hex) 01 10 07 DC 00 02 comments unit # 1 command # 16 in decimal starting address = 2012 2 registers in decimal

M2M Communications

48

M2000 Users Manual

Byte Count Data 1 Hi Data 1 Lo Data 2 Hi Data 2 Lo Error Check (LRC or CRC)

04 67 8A 12 B0 --

4 total bytes in decimal

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No of Registers Hi No of Registers Lo Error Check (LRC or CRC) Example (hex) 01 10 07 DC 00 02 --

(2 bytes)

Example #3 of Write Register Data - using Modbus function 6: Pass one register of data to address 2001 (Modbus address 42002) of the M2000 slave addressed as unit # 4. The data is 678A. Uses Modbus function 6. Field Name Slave Address Function Starting Address Hi Starting Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (in hex) 04 06 07 D1 67 8A -comments unit # 4 command # 6 starting address = 2001

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 04 06 07 D1 67 8A --

(2 bytes)

M2M Communications

49

M2000 Users Manual

Write Bit Packed Register Data to the M2000 M2000 Address 2020 2023 Modbus Address 42021 42024

Use this command to load bit packed operational data into the M2000 registers for automatic analysis and alarm reporting Up to 4 bit packed registers can be loaded into the M2000 for analysis. All register data consists of 16 bit values = two bytes (0000-FFFF hex) All data is cleared to 0 at power up. The M2000s unit (slave) address can be set to any number from 1-32 Use Modbus function # 6 or 16 to write the registers to the M2000.

Example #1 of Write Bit Packed Register Data - Using Modbus function 16 Pass 2 registers of bit packed data to address 2020 & 2021 (Modbus address 42021 & 42022) of the M2000 slave addressed as unit # 1. The data registers are: 678A and 12B0 Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data 1 Hi Data 1 Lo Data 2 Hi Data 2 Lo Error Check (LRC or CRC) Example (in hex) 01 10 07 E4 00 02 04 67 8A 12 B0 -comments unit # 1 command # 16 in decimal starting address = 2020 2 registers in decimal 4 total bytes in decimal

(2 bytes)

Normal Response:

Field Name Slave Address Function Starting Address Hi Starting Address Lo No of Registers Hi No of Registers Lo Error Check (LRC or CRC)

Example (hex) 01 10 07 E4 00 02 --

(2 bytes)

M2M Communications

50

M2000 Users Manual

Example #2 of Write Bit Packed Register Data - using Modbus function 6:

Pass one register of data to address 2020 (Modbus address 42021) of the M2000 slave addressed as unit # 7. The data is 3456. Uses Modbus function 6.

Field Name Slave Address Function Starting Address Hi Starting Address Lo Data Hi Data Lo Error Check (LRC or CRC)

Example (in hex) 07 06 07 E4 34 56 --

comments unit # 7 command # 6 starting address = 2020

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 07 06 07 E4 34 56 --

(2 bytes)

M2M Communications

51

M2000 Users Manual

Send I/O, Register, or Bit Packed Registers to the Web Server M2000 Address 00012 Modbus Address 40013 I/O and register data can be sent to the web server for several reasons: - When a reportable event occurs - On a time schedule, or - Upon request from the web server. The transmission of I/O or register data can also be initiated by the Master Modbus device using this command. Use this function to command the M2000 to transmit the previously loaded I/O or register data to the web server. To initiate a transmission, load one of the following values into register 0012, which is Modbus address 40013. Command hex 5A03 5A04 5A05 5A06 5A07 5A08 5A09 5A0A decimal 23043 23044 23045 23046 23047 23048 23049 23050 #3 #4 #5 #6 #7 #8 #9 #10 Registers 1-3 plus twelve I/O points Registers 4-6 plus twelve I/O points Registers 7-9 plus twelve I/O points Registers 10-12 plus twelve I/O points Registers 13-15 plus twelve I/O points Registers 16-18 plus twelve I/O points Registers 18-20 plus twelve I/O points Bit Packed Registers 1-4 Report Description

The M2000 slave unit address can be set to any number from 1-32 Its a good idea to check the Radio Signal Strength Indicator (RSSI) before transmitting.
The unit will not transmit unless the RSSI is > 7.

Use Modbus function # 6 or 16 Wait at least 15-20 seconds between transmissions to allow enough time for each
report to be sent and acknowledged by the cell tower. If the M2000 is already transmitting when this command is sent, a busy message will be returned, and the message will be discarded.

LED2 is the Cellular Radio Transmit LED. The normal LED2 operation for a transmission will be two green blinks. Before transmitting, the unit checks for (1) Cellular Service Available and (2) adequate radio signal strength. If successful, there will be a short green blink. Then, after about 2-5 seconds, a longer green light (lasting ~ 1 second) will indicate that the cell tower has successfully received and acknowledged the report.

If a transmission attempt fails, the red LED will light for 0.6 seconds and then the M2000
will retry after 30 seconds.

M2M Communications

52

M2000 Users Manual

If the daily call limit is reached, the red LED2 will continue to blink on and off every 1 second until the 24-hour timer has expired. During this time, all event-based calls are disabled, but time scheduled and user requested calls continue to function normally.

Example #1 of Send Register Data - Using Modbus function 16: Pass the transmit command, 5A03, to address 0012 (Modbus address 40013) of the M2000 slave unit # 1. This will cause the M2000 to transmit the preloaded contents of Registers 1-3 plus twelve I/O points.

Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Byte Count Data Hi Data Lo Error Check (LRC or CRC)

Example (hex) Comments 01 10 00 0C 00 01 02 5A 03 -Slave Unit # 1

Starting Address 12 in decimal Write 1 register 2 total bytes in decimal

(2 bytes)

Normal Response: Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Registers Hi No. of Registers Lo Error Check (LRC or CRC) Example (hex) 01 10 00 0C 00 01 --

(2 bytes)

Example #2 of Send Register Data - using Modbus function 6: Pass the transmit command, 5A0A, to address 0012 (Modbus address 40013) of the M2000 slave unit # 9. This will cause the M2000 to transmit the preloaded contents of Bit Packed Registers 1-4. Field Name Slave Address Function Example (in hex) 09 06 comments unit # 9 command # 6

M2M Communications

53

M2000 Users Manual

Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC)

00 0C 5A 0A --

address = 0012

(2 bytes)

Normal Response: Field Name Slave Address Function Address Hi Address Lo Data Hi Data Lo Error Check (LRC or CRC) Example (hex) 09 06 00 0C 5A 0A --

(2 bytes)

Exception Messages from the M2000 Slave

When a master device sends a message to the M2000 slave, it should expect to receive a response. There are four possibilities: (1) If the M2000 receives the query without a communication error (and the parity bit and the checksum matches), and the address matches the address of the M2000, it will return a response. (2) If the M2000 does not receive a proper message addressed to its unit #, it will not respond. The master should time out and retry. (3) If the M2000 receives the query properly but cannot handle it (such as because it requests a memory location that does not exist or requests a function that is not supported), the M2000 will return an exception response. The exception response message has two fields that differentiate it from a normal response. (1) In a normal response, the M2000 echoes the function code of the original query. In an exception response, the M2000 will set the most significant bit of the function code to 1. This makes the function code 80H higher than it would normally be. (2) In a normal response, the M2000 returns data or statistics in the data field. In an exception response, the M2000 will return an exception code in the data field.

There are several exception codes:

Code

Name

Meaning

M2M Communications

54

M2000 Users Manual

01 02 05

Illegal Function Illegal Data Address Acknowledge

The function code is not supported The data address is not supported The M2000 has accepted the request and is processing it, but some time will be required to complete it. The M2000 is busy in a long duration program. The Master should re- transmit the message later.

06

Slave Device Busy

M2M Communications

55

M2000 Users Manual

Example of an Exception Response:

Read one register # 40011 from unit # 01 (01 hex) Field Name Slave Address Function Starting Address Hi Starting Address Lo No. of Points, Hi No. of Points, Lo Error Check (LRC or CRC) Example (hex) Comment 01 03 03 54 00 01 --

Incorrect Address

(2 bytes)

Exception Response:

(Illegal Data Address)

Field Name Slave Address Function Exception Code Error Check (LRC or CRC)

Example (hex) 01 83 02 --

Illegal data address (2 bytes)

M2M Communications

56

M2000 Users Manual

Installing the M2000

The installation process for the M2000 can be divided into three steps: Select an installation location. Test the devices ability to send and receive data. Attach the device to between one and thirty-two Modbus based Intelligent Electronic Devices (IEDs).

Selecting an installation location The installation location will likely be determined to a great extent by the type and location of IEDs that you want to monitor or control. The recommended operating temperature range is -22 to 140 degrees F (-30 to 60 C). The recommended relative humidity range is 5 - 95% non-condensing. Antennas are available to match the environment and signal conditions. An external SMA connector provides the connection to a direct-mount 50-ohm antenna. If desired, a remote antenna can be attached to the connector. The antenna should be located outside of any metal box or cabinet.

Testing the Receiver Strength After you have selected an installation location, it is a good idea to test the devices ability to transmit and receive before performing the actual installation. (The M2000 must be connected to power in order to carry out this test.) The Radio Signal Strength Indication (RSSI) can be tested in two different ways. (1) If the unit is able to transmit, the RSSI will be reported to the website in the Power On call. (2) If a computer is connected and the Local Programmer utility is running, the RSSI can be read and displayed by clicking the View | View Data button. The RSSI will be shown under the System Info tab. If the signal is weak, try re-orienting the antenna or changing the mounting location. Note that it may be possible to improve inadequate signal strength with a directional or high gain antenna. High gain Yagi and omni-directional antennas with the correct cellular frequency are available from M2M Communications. After maximizing the signal strength, proceed with the installation.

M2M Communications

57

M2000 Users Manual

Troubleshooting Tips The LEDs can be useful in troubleshooting and system testing, but they do have several patterns that can sometimes be hard to understand. See the LED Indicator section for more details.

Troubleshooting Transmission or Reception Problems The M2000 should normally operate anywhere there is cell coverage. Both the M2000 and the cellular/Internet transport system have proven to be very reliable and repeatable. In general, once the installation is set up and working, there are no ongoing problems. Experience has shown that there are two categories of installation problems: inadequate signal strength and too much signal strength. Inadequate Signal Strength This is the simplest to understand. If the unit is being installed in a very remote location, there may not be enough signal. In this case, the RSSI will be less than 8 (less than 106 db). This is actually a rare problem in North America. A variety of higher gain and/or directional antennas are available. Too much Signal Strength an odd problem, related to installations that are very close to cell towers and/or environments with nearby metal structures. Common examples are installations inside metal buildings or in buildings with internal metal structures or large metal objects nearby. The problem occurs when the units transmission echoes from the nearby metal and effectively sends many simultaneous messages (echoes) to the cell tower. The cell tower says What the? and rejects the call. The solution to this is to move the antenna to a different location inside or outside of the building until a good transmission point is found. Often movement of only a few inches will help.

If the green LED indicates a good transmission If the unit receives a positive ACK from the cell tower and lights the middle green LED (LED2) for one second, it has done its job. The data has been sent, received, and acknowledged by the cellular network. If the data does not appear at the M2M web site, the data may be getting lost in the carrier network. This is highly unusual but does sometimes happen in new installations. Contact M2M Technical Support and we can contact the carrier to track it down for you.

M2M Communications

58

M2000 Users Manual

Connecting to Modbus with RS232 Connections can be made to one Modbus device with the RS232 connector. RS232 should normally only be used for point-to-point connections over short distances (under 20 meters). The factory default condition is for the RS232 port to be wired internally as DCE. An internal jumper block, JP2, on the printed circuit board can be moved to change the M2000 to a DTE configuration if required. This jumper swaps lines 2 and 3.

Default Wiring Connections for RS232

(= DCE)

Female (Front view)

Male (Front view)

Pin Number 2 3 5

Function Tx Rx Gnd

Connection Connects to the IED Rx Connects to the IED Tx Connects to the IED Gnd (pin 3 on a PC) (pin 2 on a PC) (pin 5 on a PC)

Connecting to Modbus with RS485 Up to 32 Modbus devices can be connected with the RS485 connector. Cables can be up to 1000 meters long, assuming adequate cable size. AWG24 cable is always sufficient for Modbus data. Modbus serial line cable should be shielded. At one end of each cable, the shield should be connected to protective ground. If a connector is used at this end, the shell of the connector is connected to the shield of the cable.

M2M Communications

59

M2000 Users Manual

Pin Number 5 4 8

Function A = = D0 B = + = D1 Ground

Connection Modbus A, , or D0 Modbus B, + , or D1 Connects to the IED Ground or Common

The M2000 RS485 port is called a two-wire Modbus port (but all three wires must be connected!) It includes a internal polarization pull-up resistor of 4.7K ohms to +5 VDC on the B (or D1) line and a pull-down resistor of 4.7K ohm to ground on the A (or D0) line. A 120-ohm termination resistor can be added between lines A and B if necessary by moving jumper JP1 on the printed circuit board. The factory default condition is for the termination resistor to be off (not in the circuit). This resistor is only recommended if the data line is very long (over 100 feet).

Modbus Data Comm Setup The M2000 can be configured as a Modbus master or slave device. There can only be one master device in the system. It is important to ensure that there are not two slave devices on the bus with the same unit address. If there is, abnormal behavior of the serial bus can occur and it may be impossible for the Master to communicate with the slaves. As a Master device, the M2000 supports both the RTU and the ASCII modes. As a Slave device, the M2000 supports only the RTU mode. There are also three parity options: Even, Odd, and None. The data communication options match the standard Modbus rules, as follows: The slave devices must be set up to match these combinations of settings: RTU mode Select the same baud rate, such as 9600 bps 8 data bits 1 start bit Even or Odd parity with 1 stop bit - Or None parity with 2 stop bits (default) or 1 stop bit if required

M2M Communications

60

M2000 Users Manual

ASCII mode Select the same baud rate, such as 9600 bps 7 data bits 1 start bit Even or Odd parity with 1 stop bit - Or None parity with 2 stop bits (default) or 1 stop bit if required

Troubleshooting the Modbus Connection The bottom red/green LED (LED3) can be used to monitor the Modbus communications. When the M2000 transmits data to the IED, the green LED will blink. When the IED sends data to the M2000, the red LED will blink. In a normal conversation, this will result in a series of very fast green and red blinks If only the green or red LED lights up, then one device is not responding. There are several reasons why this might occur. A slave device will not respond unless it receives a valid request that is addressed to its assigned Modbus device number. The request includes a parity bit test as well as a checksum. If any of these are wrong, it may not respond. (1) Ensure that the parity is the same on all units (Even, Odd, or None). (2) Ensure that all units are using the same Modbus mode (RTU or ASCII). (3) Ensure that no two slave devices are assigned to the same address. (4) Each of these modes (RTU and ASCII) has specific numbers of start, data, and stop bits and they must match on all devices. (5) Ensure that the slaves are set to the same baud rate as the M2000. (6) Ensure that the Modbus slave address matches the one that is being sent. (7) The wires may not be connected properly. The ground wire must be connected. Swapping the two data lines will not damage the unit, but it they are reversed, the IED will not respond. If the green LED blinks and the red LED stays on for about 2-3 seconds, the IED may be responding with an error message. The M2000 will report a value of 9999 if this occurs. One common problem is that the M2000 Master is set up to request data from an address that does not exist in the slave. This will usually generate an error message from the slave. Note that if you request reads from a large number of bad addresses, the unit can become tied up waiting for 2-3 seconds for each of these bad data requests to time out. So it is always important to confirm that the conversation is going properly fast green and red blinks for every polling period.

M2M Communications

61

M2000 Users Manual

M2M Network Operation Center

At the M2MComm data center, the data received from field units is validated and processed for distribution to the end user. In addition, configuration information can be sent from the M2M data center to the field module The central web site records and displays all incoming status messages and depending on the customer's instructions, will: Notify the customer of the reported event via e-mail or telephone, and/or Pass the data to the customers designated e-mail or IP address.

After entering a unique user ID and password: Both current and historical data can be viewed for all units. Displays can be customized with applicable labels. Data exporting options can be defined. Reporting options and user notification messages can be created and maintained. Time scheduled reports can be set up. Custom control commands can be designed that can be remotely written to the Modbus IED.

The M2000 web site supports three types of predefined data: 1. IED Digital Inputs and Outputs These are digital I/O points that are read from the IED and are displayed here. Up to 12 maximum data points. They report on/off, open/closed, etc.

M2M Communications

62

M2000 Users Manual

2. IED Register Values These are 16-bit positive (not negative) analog values that have been read from the IED registers and are displayed here. Up to 20 maximum register values. Editable Description labels.

3. IED Bit Packed Registers Sometimes the application will need to send digital I/O status points packed into a 16bit register. The 16-bit number can be expanded on the web site to show the separate I/O points. Each of the 16 bits (I/O points) is shown in its own row. Each bit represents a digital input or output and has a description label and a Current Condition label (on/off, open/closed, etc).

The web server can also receive, interpret, and display user created data strings from the webto-wireless modem mode.

M2M Communications

63

M2000 Users Manual

Using the Web Site

The M2M Comm web site, www.m2mcomm.com, gives you access to the data from your M2M units 24 hours a day, seven days a week, from any computer that has access to the internet. You can use the site to set up monitoring functions, to request a report from a device, and to set up automatic event notifications. Logging In To log in to your secure account on the web site, enter the user name and password that were sent to you with your unit(s). When you click the Login button, the Device List will be displayed.

The Device List gives a quick overview of the status of each device. It shows the date and time of the last call, and what that call reported. If you only have one device, the Device List will be skipped and you will go directly to the Current Status screen for your unit. For complete information on a specific device, go to the Current Status page. Click on a Device ID in the Device list and the Current Status page for that device will be displayed.

Viewing Monitored Inputs Once the M2000 is installed and turned on, it immediately begins to monitor its inputs. Within a few seconds after an input changes state, the device makes a call over the cellular network and reports the change. This data is immediately available on the M2M Communications web site. (You will need to click the Refresh link to update your screen.) The Current Status page gives the status of each input at the time of the last report. Several other links provide setup and information: Device Setup These steps are used to create custom labels, enter customer specific information, and to create user notifications. For example the following Customize Display screen allows you to define labels, units, offsets, and scale factors for the analog values and ranges reported from Modbus registers. The offsets and scale factors can often be used to convert raw data into

M2M Communications

64

M2000 Users Manual

more meaningful units. Offsets can range from 1000 to +1000 and scalars can vary from 0.001 to 1000. Offsets are added to the raw value while scalars are multiplied times the raw value. The result will be displayed. The four ranges are used to trigger calls at the unit level and to define a category at the web site level. For example, as the level of a hydraulic trash crusher moves through each of the four ranges and changes from empty to full to full to full, a call can be made. The raw value will be reported and classified into one of the four ranges. As the dumpster becomes full, more urgent notifications can be sent out to the trash guy.

An important column (not shown here) is the Visible column. Clicking on this check box does two things for the related register, input, or output. (1) To only display the registers and I/O points that are actually being used, click on the Visible button for those rows, Then select Status Summary from the Device Setup | Assign or Modify Device Data page. Only the selected items will be displayed. To see all items, select the Detailed Status Screen. (2) When using the Inbound Voice system to check the status of your device, only the status of the items selected as Visible will be spoken.

User Notifications by Voice or E-Mail One of the more advanced features of the M2M Comm web site is to allow the user to create rules that will automatically send out a notification of an alarm or other important event. For example, a rule might be created to specify that If motor 1 input reports OFF, send a custom voice message to Siegfred. These rules can also be more complex so that two conditions must be met before the action takes place. For example, If temperature set point #2 has been reached AND Fan #1 is on, send an e-mail to Roy. To create these rules, the M2M Comm web site has a step-by-step process that leads you through the process. After logging in to the web site, select the Device Setup link from the Welcome page or from the Current Status screen.

M2M Communications

65

M2000 Users Manual

On the Create Event Based Actions screen there will be a list of any User Notifications that have already been created. These can be edited at any time by clicking on the Description. An unlimited number of notification messages, rules, and recipients can be set up for any unit. To set up a User Notification, you first select the IF condition(s) that will trigger the notification, and then set up the recipient and message for the notification. There can be one AND or one OR condition for each rule. Before creating your first User Notification you must first have at least one Message and one Recipient created for use in your notification. Notification messages are sent to email addresses or phone numbers. An Internet email address can be used to send someone a regular email message that will appear in his or her email inbox, or a pager email address can be used to send a text page directly to a pager. Most modern pagers and cell phones have the ability to receive emailed pages. . Voice messages can be created in the same way. However, since the phone is more immediate and interactive, it also allows for acknowledgements. Up to 11 names and phone numbers can be entered into a call list. The system will call the first number and play your predefined text message using a sexy text-to-speech robot voice. It will then ask the recipient to press a key as an acknowledgement. If you are an answering machine or you just dont want to press the

M2M Communications

66

M2000 Users Manual

button, the system will call the next person on the list. This will continue until the call is acknowledged or you reach the end of the call-out list.

Inbound Voice Report: 1-877-747-9500 Dial this toll-free number, enter your unique PIN number, and the system will speak the status of your monitored devices to you. The data to be spoken is the items that are selected at the web site using the Visible checkbox on the Customize Display window. These items should be those that are most important to you (since you may have to listen to them all to get to the information you really want). These same items will also be displayed on the Current Status Summary screen. The lady will speak the custom description that you have entered, the current condition, and the normal or alarm status. Device Activity Log This a complete history log for the unit. All commands sent to the unit and all reports received are saved in the database. The history report can display all calls or only the calls from a certain time period. When you click the Device Activity link, the history screen initially displays all calls for the past two months. Click the Date Range button to choose a different time period to view.

Send Commands from the Web Server to the M2000 From the Send Commands screen you can request an updated status report from the device at any time. To request a report, click the desired report from the pull down list and click the Send button. A status request will immediately be sent to the device and it will respond by sending back the requested report. Within 30 seconds you should be able to click the Refresh link at the bottom of the screen and see that the unit has reported a state change for any of the inputs. You can also go to the History screen and see that the Status Report has been received. In a similar manner, you can send a variety of configuration commands to the unit at any time. An acknowledgement report will be sent back from the unit verifying each change. The following list shows the pre-set web commands for the M2000 Send Report #1 Configuration Data Send Report #3 12 IED digital I/O points and registers 1, 2 & 3 Send Report #4 12 IED digital I/O points and registers 4, 5 & 6 Send Report #5 12 IED digital I/O points and registers 7, 8, & 9 Send Report #6 12 IED digital I/O points and registers 10, 11, & 12 Send Report #7 12 IED digital I/O points and registers 13, 14, & 15 Send Report #8 12 IED digital I/O points and registers 16, 17, & 18 Send Report #9 12 IED digital I/O points and registers 18, 19, & 20 Send Report #10 Bit Packed Registers 1, 2, 3, & 4 Send Report #11 Web to Wireless Mode Modem Report Send All Selected Reports (Using the Report All List) Enable time scheduled report #3 Enable time scheduled report #4 Enable time scheduled report #5

M2M Communications

67

M2000 Users Manual

Enable time scheduled report #6 Enable time scheduled report #7 Enable time scheduled report #8 Enable time scheduled report #9 Enable time scheduled report #10 Enable time scheduled report #11 Disable time scheduled report #3 Disable time scheduled report #4 Disable time scheduled report #5 Disable time scheduled report #6 Disable time scheduled report #7 Disable time scheduled report #8 Disable time scheduled report #9 Disable time scheduled report #10 Disable time scheduled report #11 Add Report Add Report Add Report Add Report Add Report Add Report Add Report Add Report Add Report # 3 to Report All list # 4 to Report All list # 5 to Report All list # 6 to Report All list # 7 to Report All list # 8 to Report All list # 9 to Report All list # 10 to Report All list # 11 to Report All list

Remove Report # 3 from Report All list Remove Report # 4 from Report All list Remove Report # 5 from Report All list Remove Report # 6 from Report All list Remove Report # 7 from Report All list Remove Report # 8 from Report All list Remove Report # 9 from Report All list Remove Report # 10 from Report All list Remove Report # 11 from Report All list

M2M Communications

68

M2000 Users Manual

Create Custom Commands Use this screen to create custom commands or data transfers to the M2000. Label each command with the description matching the one that was defined at the unit (using a label that makes sense to the user) and specify the command number that matches the locally defined Write Function. When you save the new command, it will appear on the drop down list of the Send Commands function. In addition to the list of predefined, fixed remote commands, the user can create up to 20 (master mode) or 300 (slave mode) commands or data values to be sent from the web site to the M2000. When the command number is sent from the web site (using the Send Command function), the corresponding action (the write that you have defined locally) will be carried out. Example: Set up Command # 3 to: Write a value of 1 to Modbus Unit # 4, Address # 40123. We will assume that this write will tell a PLC to turn on a Pump # 5. You will enter the label Turn on Pump # 5 both at the web site and locally at the unit using the Local Programmer Write Register tab. At the unit, you will also define write operation 3 to mean Write a value of 1 to Modbus Unit # 4, Address # 4012. The command Turn on Pump # 5 will then appear on the pull down list of web site commands. The user can then click on the label and cause the command number 3 to be sent, either immediately or scheduled in the future. At the M2000, the command number 3 will be received. In the Master mode, this command #3 will initiate the Write Operation #3 which was defined in the Local Programming operation. The write operation can pass any specified data to any slave unit and any address. In this example, it will set up to write a value of 1 to Modbus Unit # 4, Address # 4012

In the slave mode, up to 20 different commands or data packets can be received from the web site. The Master device should poll the slave M2000 to retrieve the data. An ACK report, including a pass / fail code, will be returned to the web server when the data is received by the M2000.

M2M Communications

69

M2000 Users Manual

Data Exporting Some users do not even view their data on the M2M web site. Instead they set up the system to immediately export all data to their own web site or to an email account. Or you can do both -store and view the data at the M2M site and export it. Click on the Data Export link to set up the standard E-mail based exporting options. Incoming data for either specific unit(s) or for all units can be exported to an e-mail address. Other customized exporting options such as XML can be arranged. Contact M2M for more details.

Miscellaneous Operational Details

LED Indicators There are three bi-color (red / green) LEDs: LED1 (the top one) indicates normal operation and cellular signal. LED2 (the middle one) indicates radio (cellular) transmissions. LED3 (the bottom one) indicates Modbus communications.

LED1 indicates normal operation When the unit first powers up, the blink will be red until the radio boots up and registers with the cell tower. This process normally takes 10-12 seconds. In normal operation, LED1 will blink green on and off, changing once per second. If the LED is steady on or off, the unit is not operating normally. If LED1 blinks red on and off every second, there is no cellular service available or there is inadequate radio signal strength. The red blinks will continue until service is available. Verify the antenna connection or relocate the unit if it continues. When service becomes available and/or signal strength increases, the green LED will begin to blink.

LED2 is the Cellular Radio Transmit LED (1) The normal LED2 operation for a transmission will be two green blinks. Before transmitting, the unit checks for (1) Cellular Service Available and (2) adequate radio signal strength. If successful, there will be a short green blink. Then, after about 2-5 seconds, a longer green light (lasting ~ 1 second) will indicate that the cell tower has successfully received and acknowledged the report. After each transmission, there will then be a 10 second delay before another call can be placed. During this delay time, the red LED2 will blink on and off every second.

M2M Communications

70

M2000 Users Manual

(2) If a transmission attempt fails, the red LED will light for 0.6 seconds. (3) If the daily call limit is reached, the red LED2 will continue to blink on and off every 1 second until the 24-hour timer has expired. During this time, all event-based calls are disabled, but time scheduled and user requested calls continue to function normally. (4) When the unit is first powered on, it will begin a routine in which it determines the proper channel for control channel operation. The process starts by sending a registration call to the server on Channel B (the most commonly used channel). If the unit receives an acknowledgement from the server, it will remain on that channel. However, if after one minute, it has not received an acknowledgement, it will repeat the process on Channel A. While waiting for the registration ACK from the web site on B channel, there will be a green blink at a rate of second on and second off. While waiting for the registration ACK from the web site on A channel, there will be a red blink at a rate of second on and second off. This cycle will normally repeat only once. If it continues, the web site is not receiving or responding to the units registration call. (5) When the unit receives a command from the web site, the green LED will light for 0.2 seconds.

LED3 indicates Modbus communications LED3 will blink green when the unit sends data or a request to a Modbus unit. LED3 will blink red when it receives a command or response from a Modbus unit. In normal operation, the LED3 will blink once green and red at a rapid rate for each read/write operation. If the LED3 only blinks green, then the Modbus device is not answering at all. If the red LED3 stays on for 2-3 seconds, then the device is not responding as expected and is timing out.

Other LED Indications (1) If LED2 alternates red & green on and off, the radio is not communicating with the processor. This will typically be corrected automatically by internally retrying the communication. If the lights continue to alternate read and green, there is a problem with the unit. (2) If all three LEDs are solid ON red, the unit is not loaded with valid operating parameters. Download a new profile to the unit. (3) While communicating with the Local Programmer, all three LEDs will be green. When the communication is completed or the computer is unplugged, the three LEDs should resume normal operation.

M2M Communications

71

M2000 Users Manual

Daily Call Limits To reduce the number of calls that might result from over-active inputs or power cycling conditions, the number of event-based calls per day can be limited. Time scheduled calls and user requested status calls will continue to be placed even after this limit has been reached. The daily call limit is set in the Local Programmer Configuration screen and should be selected so that the total number of calls is limited to no more than 20 calls per day and no more than 400 calls per month. The daily limit can be set from 1 to 20. The factory default setting is 10.

Cellular Carrier Requirements There are several specifications and operating requirements that must be met prior to commercial deployment. These are all included in the requirements specification for the unit. Several may be apparent to the user so are worthy of mention here: The M2000 is software limited to a specified number of event-based change reports per day. The call limit is user-programmable and can be adjusted from 1-20 calls per day. If the daily call limit is reached, the red LED2 will continue to blink on and off every 1 second until the 24-hour timer has expired. During this time, all event-based calls are disabled, but time scheduled and user requested calls will continue to function normally. After each transmission, there will then be a 10 second delay before another call can be placed. During this delay time, the red LED2 will blink once per second. The unit will not attempt to transmit unless service is available and the RSSI exceeds 106 dB. Antennas should be half wave. The use of quarter wave antennas is discouraged

M2M Communications

72

M2000 Users Manual

Retry Algorithm The unit will delay at least 30 seconds between retries after a failed transmission. After five unsuccessful transmission attempts, the processor will reset the radio and then retry 5 more times. After a total of 10 unsuccessful attempts, the unit will discard the current data being reported. It will then wait one hour and then attempt to send the same report with new current status information. After five unsuccessful transmission attempts, the processor will power cycle the radio and then retry 5 more times. If ten tries are again unsuccessful, the unit will wait 2 hours and repeat this process. If ten tries are again unsuccessful, the unit will wait 6 hours and repeat the process. If ten tries are again unsuccessful, the unit will wait 18 hours and repeat the process. If ten tries are again unsuccessful, the unit will abandon the data and stop trying. If other reportable events or time-scheduled reports are initiated during the retry process, they will restart the process. A successful transmission of any call will terminate the retry process.

M2M Communications

73

M2000 Users Manual

Hardware Specifications
Antenna The standard antenna is a direct-connect wave 50-ohm AMPS rubber duck cellular antenna. An external SMA RF connector provides the connection to the antenna. A remote antenna can be attached to the connector if desired. If the M2000 is located inside a metal cabinet, the antenna MUST be located outside that cabinet. Cellular Radio Operating Specifications The GSM / GPRS digital cellular modem has the following specifications:
GPRS Class 10 operation Packet data up to 85.6K bps Embedded TCP/IP stack

Power Supply / Enclosure Options The standard M2000 operates from 8- 30 VDC. The power supply must be capable of providing a regulated voltage in this range and a peak current of 1.6 Amps during transmission. The M2000 power connector is a 2-pin removable plug with screw terminals. The standard enclosure is 6 x 3 x 2 and made of black anodized extruded aluminum.

The small size and low cost make it suitable for a wide variety of general monitoring applications. This configuration requires that the user will install the units in a waterproof and safe environment. External waterproof enclosures and/or 120 VAC powered units are also available. These enclosures are waterproof, gray aluminum boxes with integrated mounting flanges.

M2M Communications

74

M2000 Users Manual

CPU / Memory The CPU is a Microchip PIC 18F6720 product. Non-volatile (EEPROM) and FLASH memory is used to store configuration and operational data. The operating system is stored in FLASH memory and can be updated at any time through the Local Programmer.

Environmental Considerations The recommended operating temperature range is -22 to 140 degrees F (-30 to 60 C). The recommended relative humidity range is 5 - 95% non-condensing.

Part Numbers Powered by 8-30 VDC M2000DC_Int M2000DC_Ext Powered by 120 VAC M2000AC_Int M2000AC_Ext Aluminum Housing (for indoor use) Exterior NEMA 4 Enclosure Aluminum Housing (for indoor use) Exterior NEMA 4 Enclosure

M2M Communications

75

M2000 Users Manual