Product specifications
Table Of Contents
- 1.0 ABOUT THIS MANUAL
- 2.0 PRODUCT DESCRIPTION
- 2.1 Transceiver Features
- 2.2 Model Number Codes
- 2.3 Spread Spectrum Radios— How Are They Different?
- 2.4 Typical Applications
- Multiple Address Systems (MAS)
- Point-to-Point System
- Adding a Tail-End Link to an Existing Network
- Extending a TransNET Network with a Repeater
- 2.5 Accessories
- 3.0 INSTALLATION PLANNING
- 3.1 General Requirements
- 3.2 Site Selection
- Terrain and Signal Strength
- Conducting a Site Survey
- 3.3 A Word About Radio Interference
- 3.4 Antenna & Feedline Selection
- Antennas
- Feedlines
- Antenna System Ground
- 3.5 How Much Output Power Can be Used?
- 4.0 INSTALLATION
- 4.1 Transceiver Installation
- 4.2 Configuring Multiple Remote Units
- 4.3 Tail-End Links
- 4.4 Configuring a Network for Extensions
- 5.0 OPERATION
- 5.1 Initial Start-up
- 5.2 Performance Optimization
- Antenna Aiming
- Antenna SWR Check
- Data Buffer Setting—Modbus Protocol
- Hoptime Setting
- TotalFlow™ Protocol at 9600 with Sleep Mode
- Operation at 115200 bps
- Baud Rate Setting
- Radio Interference Checks
- 6.0 RADIO PROGRAMMING
- 6.1 Radio Programming Methods
- Terminal Interface
- PC-Based Configuration Tool
- 6.2 User Commands
- Entering Commands
- 6.3 Detailed Command Descriptions
- ADDR [1–65000]
- AMASK [0000 0000–FFFF FFFF]
- AT [ON, OFF]
- ASENSE [HI/LO]
- BAUD [xxxxx abc]
- BAND [A, B, C]
- BUFF [ON, OFF]
- CODE [NONE, 1…255]
- CSADDR [1–65000, NONE]
- CTS [0–255]
- CTSHOLD [0–60000]
- DEVICE [DCE, CTS KEY]
- DLINK [xxxxx/ON/OFF]
- DKEY
- DTYPE [NODE/ROOT]
- FEC [ON, OFF]
- HOPTIME [7, 28]
- INIT
- HREV
- KEY
- LED [ON, OFF]
- LPM [1, 0]
- LPMHOLD [0–1000]
- MODE [M, R, X]
- MRSSI [NONE, –40...–90]
- OT [ON, OFF]
- OWM [xxxxx]
- OWN [xxxxx]
- PORT [RS232, RS485]
- PWR [20–30]
- REPEAT [0–10]
- RETRY [0–10]
- RSSI
- RTU [ON, OFF, 0-80]
- RX [xxxx]
- RXD [0–255]
- RXTOT [NONE, 0–1440]
- SAF [ON, OFF]
- SETUP
- SER
- SHOW CON
- SHOW PWR
- SHOW SYNC
- SKIP [NONE, 1...8]
- SLEEP [ON, OFF]
- SREV
- STAT
- TEMP
- TX [xxxx]
- UNIT [10000–65000]
- XADDR [0–31]
- XMAP [00000000-FFFFFFFF]
- XPRI [0–31]
- XRSSI [NONE, –40...–120]
- ZONE CLEAR
- ZONE DATA
- 7.0 TROUBLESHOOTING
- 7.1 LED Indicators
- 7.2 Alarm Codes
- Checking for Alarms—STAT command
- Major Alarms versus Minor Alarms
- Alarm Code Definitions
- 7.3 Troubleshooting Chart
- 7.4 Performing Network-Wide Remote Diagnostics
- 7.5 Internal Fuse Replacement
- 8.0 RADIO FIRMWARE UPGRADES
- 8.1 Obtaining New Firmware
- Saving a Web-Site Firmware File Onto Your PC
- 8.2 Installing Firmware Into Your Radio
- 9.0 OPERATING PRINCIPLES AND CONFIGURATION
- 9.1 SAF Operation with Extension Radios
- Simple Extended SAF Network
- Extended SAF Network
- Retransmission and ARQ Operation
- SAF Configuration Example
- 9.2 Synchronizing Network Units
- Synchronization Messages
- 9.3 Using AT Commands
- 9.4 Configuration Parameters for Store-and-Forward Services
- 9.5 Using the Radio’s Sleep Mode (Remote Units Only)
- Sleep Mode Example
- 9.6 Low-Power Mode (LPM)—Master Enabled
- Setup Commands
- Reading RSSI and Other Parameters with LPM Enabled
- Power Consumption Influence by HOPTIME and SAF Settings
- 9.7 Low-Power Mode versus Remote’s Sleep Mode
- 9.8 Mobile Operation Support
- Introduction
- Operational Influences—Hoptime & SAF
- 9.9 MIRRORED BITS™ Protocol Support
- 9.10 Seamless Mode Emulation
- Master Station Configuration
- Antenna System for Co-Located Master Stations
- 10.0 TECHNICAL REFERENCE
- Pin Descriptions—RS/EIA-232 Mode
- Pin Descriptions—RS/EIA-422/485 Mode
- Using the I/O Points with InSite™ NMS Software
- Application Example—Digital Input and Output at a Remote

MDS 05-2708A01, Rev. E MDS TransNET Ref. Manual 55
All Remotes synchronize to a corresponding Master. This can be the “real
Master” (the
MODE M unit), or it can be a repeater “Extension” that derives
synchronization from the “real Master.”
Payload polls/packets broadcast from the network Master will be repeated to
all levels of the network, either directly to Remotes, or through network
repeaters—the Extension station. The targeted Remote responds to the poll
following the same path back to the Master.
Synchronization Messages
Remotes acquire synchronization and configuration information via
SYNC
messages. They can synchronize to the Master (the
MODE M unit) or to any
valid Extension (a
MODE X unit).
The Master will always transmit
SYNC messages. An Extension will only
start sending
SYNC messages after synchronization is achieved with its
Master.
The ability to synchronize to a given radio is further qualified by the sender’s
Extended Address (
XADDR) and by the receiver’s Synchronization Qualifiers
(
XMAP, XPRI, and XRSSI).
When a primary is specified (
XPRI is 0...31), a radio will always attempt to
find the primary first. If 30 seconds elapses and the primary is not found, then
the radio attempts to synchronize with any non-primary radio in the
XMAP
list.
Once every 30 minutes, if a primary is defined, the radio will check its
synchronization source. If the radio is synchronized to a unit other than the
primary, then the current
RSSI value is compared to the XRSSI value. If RSSI
is less than
XRSSI (or if XRSSI is NONE) the radio will force a
loss-of-synchronization, and hunt for the primary again (as described in the
previous paragraph).
By default, Extensions (and the Master) begin with
XADDR 0. Synchroniza-
tion qualifiers are set to
XMAP 0, XPRI 0, and XRSSI NONE, respectively. This
default configuration allows any radio to hear the Master. When an Extension
is added, the extended address of the Extension radio must be set to a unique
value. All Remotes that need to hear that extension can specify this either by
designating the extension as the primary (
XPRI), or by including it in their list
of valid synchronization sources (
XMAP).
9.3 Using AT Commands
A TransNET network may be configured to support protocols employing
Hayes-Compatible modem commands through the radio’s AT Mode. In this
mode, TransNET units can provide a communications replacement for
dial-up modems where the RTUs and the protocol do not contain address-
ability, and the establishment of a direct-communications link is the only way
to determine if the RTU has data ready to be sent. This requirement is
common in many older SCADA systems which were developed for direct










