Page 1
User manual
www.racom.eu
RACOMs.r.o. •Mirova1283•59231NoveMestonaMorave•CzechRepublic
Tel.:+420565659511•Fax:+420565659512•E-mail: racom@racom.eu
.
RipEX
Radio modem & Router
.
version 1.20
08/16/2017
fw 1.7.x.x
Page 2
Page 3
Table of Contents
Important Notice .................................................................................................................................. 7
Quick guide ......................................................................................................................................... 8
1. RipEX – Radio router .................................................................................................................... 10
1.1. Introduction ......................................................................................................................... 10
1.2. Key Features ...................................................................................................................... 10
2. RipEX in detail ............................................................................................................................... 13
2.1. Applications ........................................................................................................................ 13
2.2. Bridge mode ....................................................................................................................... 13
2.2.1. Detailed Description ................................................................................................ 14
2.2.2. Functionality example .............................................................................................. 14
2.2.3. Configuration examples ........................................................................................... 16
2.3. Router mode ....................................................................................................................... 19
2.3.1. Router - Flexible, Detail description ......................................................................... 20
2.3.2. Router - Flexible, Functionality example ................................................................. 20
2.3.3. Router - Flexible, Configuration examples .............................................................. 21
2.3.4. Router - Flexible, Addressing hints .......................................................................... 23
2.3.5. Router - Base driven, Detail description .................................................................. 24
2.3.6. Router - Base driven, Functionality example ........................................................... 24
2.3.7. Router - Base driven, Configuration example ......................................................... 25
2.4. Serial SCADA protocols ..................................................................................................... 27
2.4.1. Detailed Description ................................................................................................ 27
2.5. Combination of IP and serial communication ..................................................................... 28
2.5.1. Detailed Description ................................................................................................ 28
2.6. Diagnostics & network management .................................................................................. 29
2.6.1. Logs ......................................................................................................................... 29
2.6.2. Graphs ..................................................................................................................... 29
2.6.3. SNMP ...................................................................................................................... 29
2.6.4. Ping ......................................................................................................................... 30
2.6.5. Monitoring ................................................................................................................ 30
2.7. Firmware update and upgrade ........................................................................................... 30
2.8. Software feature keys ......................................................................................................... 31
3. Network planning ........................................................................................................................... 32
3.1. Data throughput, response time ......................................................................................... 32
3.2. Frequency .......................................................................................................................... 33
3.3. Signal budget ..................................................................................................................... 34
3.3.1. Path loss and fade margin ....................................................................................... 35
3.4. Multipath propagation, DQ ................................................................................................. 35
3.4.1. How to battle with multipath propagation? .............................................................. 36
3.5. Network layout .................................................................................................................... 38
3.6. Hybrid networks .................................................................................................................. 40
3.7. Assorted practical comments ............................................................................................. 40
3.8. Recommended values ........................................................................................................ 41
4. Product .......................................................................................................................................... 43
4.1. Dimensions ......................................................................................................................... 43
4.2. Connectors ......................................................................................................................... 46
4.2.1. Antenna ................................................................................................................... 46
4.2.2. Power and Control ................................................................................................... 47
4.2.3. ETH ......................................................................................................................... 49
4.2.4. COM1 and COM2 .................................................................................................... 49
4.2.5. USB ......................................................................................................................... 50
4.2.6. Reset button ............................................................................................................ 52
3© RACOM s.r.o. – RipEX Radio modem & Router
Page 4
RipEX
Radio modem & Router
4.2.7. GPS ......................................................................................................................... 53
4.3. Indication LEDs .................................................................................................................. 54
4.4. Technical specification ........................................................................................................ 55
4.4.1. Detailed Radio parameters ...................................................................................... 59
4.5. Model offerings ................................................................................................................... 69
4.5.1. Ordering code (Part No’s) ........................................................................................ 69
4.6. Accessories ........................................................................................................................ 72
5. Bench test ..................................................................................................................................... 80
5.1. Connecting the hardware ................................................................................................... 80
5.2. Powering up your RipEX .................................................................................................... 80
5.3. Connecting RipEX to a programming PC ........................................................................... 80
5.4. Basic setup ......................................................................................................................... 84
5.5. Functional test .................................................................................................................... 84
6. Installation ..................................................................................................................................... 85
6.1. Mounting ............................................................................................................................. 85
6.1.1. DIN rail mounting ..................................................................................................... 85
6.1.2. Flat mounting ........................................................................................................... 87
6.1.3. 19" rack mounting .................................................................................................... 88
6.1.4. IP51 mounting ......................................................................................................... 88
6.2. Antenna mounting .............................................................................................................. 88
6.3. Antenna feed line ............................................................................................................... 89
6.4. Grounding ........................................................................................................................... 89
6.5. Connectors ......................................................................................................................... 89
6.6. Power supply ...................................................................................................................... 90
7. Advanced Configuration ................................................................................................................ 91
7.1. Menu header ...................................................................................................................... 91
7.2. Status ................................................................................................................................. 93
7.2.1. Device, Radio, ETH&COM ...................................................................................... 93
7.2.2. Diagnostic ................................................................................................................ 93
7.3. Settings ............................................................................................................................... 94
7.3.1. Device ...................................................................................................................... 94
7.3.2. Radio ..................................................................................................................... 116
7.3.3. ETH ....................................................................................................................... 134
7.3.4. COM ...................................................................................................................... 143
7.3.5. Protocols ................................................................................................................ 145
7.4. Routing ............................................................................................................................. 161
7.4.1. Interfaces ............................................................................................................... 161
7.4.2. Routes ................................................................................................................... 162
7.4.3. Backup ................................................................................................................... 162
7.5. VPN .................................................................................................................................. 165
7.5.1. IPsec ...................................................................................................................... 165
7.5.2. GRE ....................................................................................................................... 173
7.6. Diagnostic ......................................................................................................................... 176
7.6.1. Neighbours and Statistic ........................................................................................ 176
7.6.2. Graphs ................................................................................................................... 180
7.6.3. Ping ....................................................................................................................... 182
7.6.4. Monitoring .............................................................................................................. 187
7.7. Maintenance ..................................................................................................................... 199
7.7.1. SW feature keys .................................................................................................... 199
7.7.2. Configuration ......................................................................................................... 200
7.7.3. Firmware ................................................................................................................ 200
7.7.4. Administrator account ............................................................................................ 202
RipEX Radio modem & Router – © RACOM s.r.o.4
Page 5
RipEX
Radio modem & Router
7.7.5. Miscellaneous ........................................................................................................ 202
7.7.6. SSL certificate ....................................................................................................... 202
7.7.7. Remote access keys ............................................................................................. 203
7.7.8. RF transmission test .............................................................................................. 204
7.7.9. Technical support package .................................................................................... 204
8. CLI Configuration ........................................................................................................................ 205
8.1. CLI Examples ................................................................................................................... 205
9. Troubleshooting ........................................................................................................................... 208
10. Safety, environment, licensing ................................................................................................... 210
10.1. Frequency ...................................................................................................................... 210
10.2. Safety distance ............................................................................................................... 210
10.3. High temperature ............................................................................................................ 214
10.4. RoHS and WEEE compliance ........................................................................................ 214
10.5. Hazardous locations ....................................................................................................... 215
10.6. Conditions of Liability for Defects and Instructions for Safe Operation of Equipment .... 216
10.7. Important Notifications .................................................................................................... 216
10.8. EU Declaration of Conformity ......................................................................................... 218
10.9. Simplified EU declaration of conformity .......................................................................... 219
10.10. ATEX Certificate ........................................................................................................... 221
10.11. Compliance Federal Communications Commission ..................................................... 224
10.12. Country of Origin .......................................................................................................... 225
10.13. Warranty ....................................................................................................................... 226
10.14. RipEX maintenance ...................................................................................................... 227
A. OID mappings ............................................................................................................................. 228
B. Abbreviations .............................................................................................................................. 229
Index ................................................................................................................................................ 231
C. Revision History .......................................................................................................................... 233
List of Tables
4.1. Pin assignment ........................................................................................................................... 47
4.2. Ethernet to cable connector connections ................................................................................... 49
4.3. COM1, 2 pin description ............................................................................................................. 50
4.4. USB pin description .................................................................................................................... 50
4.5. Key to LEDs ............................................................................................................................... 54
4.6. Technical parameters ................................................................................................................. 55
4.7. Recommended Cables ............................................................................................................... 58
4.8. Unlimited 50 kHz ........................................................................................................................ 59
4.9. CE 50 kHz .................................................................................................................................. 60
4.10. CE 25 kHz ................................................................................................................................ 61
4.11. CE 12.5 kHz ............................................................................................................................. 62
4.12. CE 6.25 kHz ............................................................................................................................. 63
4.13. FCC 50 kHz .............................................................................................................................. 64
4.14. FCC 25 kHz .............................................................................................................................. 64
4.15. FCC 25 kHz RipEX-928, RipEX-215 ........................................................................................ 65
4.16. FCC 12.5 kHz ........................................................................................................................... 66
4.17. FCC 6.25 kHz ........................................................................................................................... 66
4.18. Narrow 25 kHz .......................................................................................................................... 67
10.1. Minimum Safety Distance 160 MHz ....................................................................................... 210
10.2. Minimum Safety Distance 216–220 MHz ............................................................................... 212
10.3. Minimum Safety Distance 300–400 MHz ............................................................................... 212
10.4. Minimum Safety Distance 928–960 MHz ............................................................................... 214
5© RACOM s.r.o. – RipEX Radio modem & Router
Page 6
RipEX
Radio modem & Router
10.5. Maximum voltage and current of individual interfaces ........................................................... 216
10.6. Compliance Federal Communications Commission .............................................................. 224
RipEX Radio modem & Router – © RACOM s.r.o.6
Page 7
Important Notice
Important Notice
Copyright
© 2017 RACOM. All rights reserved. COM’s
Products offered may contain software proprietary to RACOM s. r. o. (further referred to under the abbreviated name RACOM). The offer of supply of these products and services does not include or infer
any transfer of ownership. No part of the documentation or information supplied may be divulged to
any third party without the express written consent of RACOM.
Disclaimer
Although every precaution has been taken in preparing this information, RACOM assumes no liability
for errors and omissions, or any damages resulting from the use of this information. This document or
the equipment may be modified without notice, in the interests of improving the product.
Trademark
All trademarks and product names are the property of their respective owners.
Important Notice
• Due to the nature of wireless communications, transmission and reception of data can never be
guaranteed. Data may be delayed, corrupted (i.e., have errors), or be totally lost. Significant delays
or losses of data are rare when wireless devices such as the RipEX are used in an appropriate
manner within a well‐constructed network. RipEX should not be used in situations where failure to
transmit or receive data could result in damage of any kind to the user or any other party, including
but not limited to personal injury, death, or loss of property. RACOM accepts no liability for damages
of any kind resulting from delays or errors in data transmitted or received using RipEX, or for the
failure of RipEX to transmit or receive such data.
• Under no circumstances is RACOM or any other company or person responsible for incidental,
accidental or related damage arising as a result of the use of this product. RACOM does not provide
the user with any form of guarantee containing assurance of the suitability and applicability for its
application.
• RACOM products are not developed, designed or tested for use in applications which may directly
affect health and/or life functions of humans or animals, nor to be a component of similarly important
systems, and RACOM does not provide any guarantee when company products are used in such
applications.
•
The equipment should be used in hazardous locations under conditions according to Section 10.5,
“Hazardous locations” only.
7© RACOM s.r.o. – RipEX Radio modem & Router
Page 8
Antenna
IndicatorLEDs'
SleepInput
HW AlarmInput
-GND
+
HW AlarmOutput
Supply+10to+30V
-GND
Ethernet
USB
COM1
RS232
COM2
RS232/485
Default/Reset
-
-
+
+
SI
AI
AO
10–30VDC
ETH
USB
ANT
COM1
COM2
Quick guide
Quick guide
RipEX is a widely configurable compact radio modem, more precisely a radio IP router. All you have
to do to put it into operation is to connect it to an antenna and a power supply and configure it using a
PC (tablet, smart phone) and a web browser.
Fig. 1: RipEX radio router
RipEX access defaults: username: admin, password: admin
Ethernet
RipEX default IP is 192.168.169.169/24, so set a static IP 192.168.169.x/24 on your PC, power on the
RipEX and wait approximately 48 seconds for the RipEX OS to boot. Connect your PC to RipEXs' ETH
interface, start your browser and type https://192.168.169.169 in the address line.
Before attempting to do any configuration, make sure your RipEX is the only powered-up unit around.
Since all units coming from factory share the same default settings ex factory, you could be accessing
a different unit over the air without being aware of it.
USB/ETH adapter
When accessing over the optional “XA” USB/ETH adapter, your PC will get its IP settings from the builtin DHCP server and you have to type https://10.9.8.7 in your browser. You do not need to worry about
other RipEX'es, you will be connected to the local unit in all cases.
Wifi adapter
When accessing over the optional “W1” Wifi adapter, connect your PC (tablet, smart phone) to the
RipEX Wifi AP first. Its default SSID is “RipEX + Unit name + S/N”
Your PC will get its IP settings from the built-in DHCP server and you have to type http://10.9.8.7 in
your browser. Remaining steps are the same and you do not need to worry about other RipEX'es, since
you will be connected to the local unit in all cases.
RipEX Radio modem & Router – © RACOM s.r.o.8
Page 9
Quick guide
SCADA radio network step-by-step
Building a reliable radio network for a SCADA system may not be that simple, even when you use such
a versatile and easy-to-operate device as the RipEX radio modem. The following step-by-step checklist
can help you to keep this process fast and efficient.
1. Design your network to ensure RF signal levels meet system requirements.
2. Calculate and estimate the network throughput and response times when loaded by your application.
3.
Perform a bench-test with 3-5 sets of RipEX's and SCADA equipment (Chapter 5, Bench test).
4.
Design the addressing and routing scheme of the network (Chapter 2, RipEX in detail and RipEX
App notes, Address planing1)
5. Preconfigure all RipEX's (Section 5.4, “Basic setup”).
6. Install individual sites
1. Mount RipEX into cabinet (Section 6.1, “Mounting”).
2. Install antenna (Section 6.2, “Antenna mounting”).
3. Install feed line (Section 6.3, “Antenna feed line”).
4. Ensure proper grounding (Section 6.4, “Grounding”).
5. Run cables and plug-in all connectors except from the SCADA equipment (Section 4.2,
“Connectors”)
6. Apply power supply to RipEX
7. Test radio link quality (Section 5.5, “Functional test”).
8. Check routing by the ping tool (Section 7.6.3, “Ping”) to verify accessibility of all IP addresses
with which the unit will communicate.
9. Connect the SCADA equipment
7. Test your application
1
http://www.racom.eu/eng/products/m/ripex/app/routing.html
9© RACOM s.r.o. – RipEX Radio modem & Router
Page 10
RipEX – Radio router
1. RipEX – Radio router
1.1. Introduction
RipEX is a best-in-class radio modem, not only in terms of data transfer speed. This Software Defined
Radio with Linux OS has been designed with attention to detail, performance and quality. All relevant
state-of-the-art concepts have been carefully implemented.
RipEX provides 24×7 reliable service for mission-critical applications like SCADA & Telemetry for Utilities, SmartGrid power networks or transaction networks connecting lottery terminals, POS or ATM’s.
Any unit can serve as the central master, repeater, remote terminal, or all of these simultaneously, with
a configuration interface easily accessible from a web browser.
Anybody with even basic knowledge of IP networking can set up a RipEX within a matter of minutes
and maintain the network quite easily.
1.2. Key Features
• Exceptional data speeds on the radio channel
- >200 kbps / 50 kHz, >100 kbps / 25 kHz, >50 kbps / 12.5 kHz, >25 kbps / 6.25 kHz
• 1× ETH, 2× COM, 1× USB, 5× virtual COM
- Simultaneously on radio channel. COM1-RS232, COM2-RS232 or RS485, software configurable.
Virtual COM ports over ETH controlled by Terminal servers. USB for independent service access
via USB/ETH adapter and for automatic FW and SW keys upgrade.
• Wifi management
- Any smart phone, tablet or notebook can be used as a RipEX portable display.
• 135–174; 215–240; 300–360; 368–512; 928–960 MHz
- Licensed radio bands
- Software-selectable channel spacing 50, 25, 12.5 or 6.25 kHz
• 10 watts
- Transmission output control, nine stages from 0.1 to 10 W. Hence QAM modulations (the highest
data speed) require a very linear RF power amplifier, max. 2 W is available for them.
• Energy saving
- Sleep mode – 0.1 W, controlled via a digital input.
- Save mode – 2 W, wakes up by receiving a packet from the Radio channel
• Extended temperature range
−40 to +70 ºC
• Easy to configure and maintain
- Web interface,
- Wizards,
- On-line help,
- Balloon tips,
- Fastest web access to remote units
RipEX Radio modem & Router – © RACOM s.r.o.10
Page 11
RipEX – Radio router
• Fast remote access
- Only the effective data are transferred from remote RipEX over the air, html page is downloaded
from the local unit.
• Bridge or Router
- RipEX is a device with native IP support which can be set as a standard bridge or router.
• Modbus, IEC101, DNP3, PR2000, Siemens 3964(R), Comli, RP570, C24, DF1, Profibus, SLIP,
Async Link, Cactus, ITT Flygt, RDS, UNI, Modbus TCP, IEC104, DNP3 TCP etc.
- Unique implementation of industrial protocols enables a secure addressed transmission of all
packets in all directions
• Three protocols on Radio channel
- Fully Transparent (Bridge)
- Flexible (Router) - for meshing networks providing unlimited footprint coverage without base stations
- Base driven (Router) - optimized for TCP/IP applications like IEC104 making them reliable and
stable even with a high number of RTUs.
• Backup routes
- When tested path between two RipEX IP addresses (even behind repeater or LAN) fails, automatic
switch-over to backup gateway behind Radio or Ethernet interfaces
- Unlimited number of prioritized backup gateways
- Instructional video http://www.racom.eu/ripex-backup
• VPN
- IPsec is a network protocol suite that authenticates and encrypts the packets of data sent over a
network.
- GRE is a tunneling protocol that can encapsulate a wide variety of network layer protocols inside
virtual point-to-point links over an Internet Protocol network.
• Optimization
– 3× higher throughput
- Optimization method which joins short packets, compresses data, optimises both the traffic to the
link peer and the sharing of the radio channel capacity among the links.
• TCP proxy
- Eliminates a transfer of TCP overhead over Radio channel when TCP overhead run locally between
connected device and RipEX on LAN. I.e. only payload (user) data are transferred further as UDP
(over Radio channel)
- Higher RipEX network bandwidth, no more problems with TCP timeouts
- Instructional video http://www.racom.eu/ripex-tcp-proxy
• ARP proxy
- RipEX can simulate any IP address (it may reply to any ARP request)
- This feature is typically used when RTU addresses behind different RipEX units are within the
same IP subnet and RTUs do not provide routing capabilities (neither default GW)
- Instructional video http://www.racom.eu/ripex-arp-proxy
• VLAN & Subnets
- RipEX can simulate any IP address (it may reply to any ARP request)
- Unlimited number of virtual Ethernet interfaces (IP aliases) can be set
• Embedded diagnostic & NMS
- Real time and historical (20 periods, e.g. days) statistics and graphs for the unit and its neighbours.
11© RACOM s.r.o. – RipEX Radio modem & Router
Page 12
RipEX – Radio router
- SNMP including generation of TRAP alarms when preset thresholds are exceeded
- on-line/off-line (recorded to a file in the RipEX) monitoring of all interfaces
• Security
- 256 AES encryption, the most secure encryption meets FIPS 140 2 requirements
- 2048 (1024, 512) bit SSL certificate (even your own one) for https web configuration
• SW feature keys
Software authorization keys allow you to add advanced features when needed: Router mode, 166/83
(The two highest Data rates for 25 and 50 kHz channel spacing), COM2, 10 W, Backup routes
- Free Master-key trial – (all coded features) for 30 days in every RipEX
• Reliability
- 3 years warranty, rugged die cast aluminium case, military or industrial components
- Every single unit tested in a climatic chamber as well as in real traffic
• RipEX - HS
- Redundant hot standby chassis
- Two hot-stand-by standard RipEX units inside
- Automatic switchover capability on detection of failure
- Suitable for Central sites, Repeaters or Important remote sites where no single point of failure is
required
• Internal calendar time
- Can be set manually or synchronized via NTP (Network Time Protocol)
- Any RipEX also runs as a NTP server automatically
- NTP synchronization via Ethernet or over the Radio channel from another RipEX or from the builtin GPS
- Powered from internal long life Lithium Manganese battery, so it is accurate even when RipEX is
powered off
• Flash memory
- All configuration parameters are saved in flash memory
• External Flash disc
- Automatic firmware upgrade, SW keys upload, configuration backup/restore, ssl certificate and
ssh keys upload and configuration, tech-support package download
RipEX Radio modem & Router – © RACOM s.r.o.12
Page 13
RipEX in detail
2. RipEX in detail
2.1. Applications
Radio modem RipEX is best suited for transmission of a large number of short messages where a
guaranteed delivery is required, i.e. for mission critical applications.
RipEX has the following basic uses:
○ Polling
In poll-response networks a central master unit communicates with a number of remote radiomodems
one at a time. The master unit exchanges data with the currently connected remote radio, and when
finished, it establishes a new connection with the next remote radio according to the polling order.
○ Report-by-exception
In report-by-exception networks remote units can be contacted similarly to polling networks. In addition, any remote unit can spontaneously send data to the master unit (typically an alarm).
○ Mesh
In mesh type networks any radio modem in the network can access any other radio modem randomly
and spontaneously. Mesh network can also host polling or report-by-exception applications, even
in several instances.
To be able to satisfy different types of applications, RipEX offers multiple options for building a radio
network. There are 2 different Operation modes, Bridge and Router with 3 different protocols on Radio
channel:
• Transparent used in Bridge mode
• Flexible used in Router mode
• Base driven used in Router mode
2.2. Bridge mode
Bridge mode with fully transparent Radio protocol is suitable for all polling (request-response) applications
with star network topologies, however repeater(s) are possible.
A packet received through any interface is broadcast to the appropriate interfaces of all units within the
network. Packets received on COM are broadcast to both COM1 and COM2 at remote sites, allowing
you to connect 2 RTUs to any radio modem.
Any unit can be configured as a repeater. A repeater relays all packets it receives through the radio
channel. The network implements safety mechanisms which prevent cyclic loops in the radio channel
(e.g. when a repeater receives a packet from another repeater) or duplicate packets delivered to the
user interface (e.g. when RipEX receives a packet directly and then from a repeater).
Beside standard packet termination by an "Idle" period on the serial port (a pause between received
bytes) the bridge mode also offers "streaming". While in streaming mode, transmission on the radio
channel starts immediately, without waiting for the end of the received frame on COM => zero latency.
13© RACOM s.r.o. – RipEX Radio modem & Router
Page 14
RipEX in detail
Note
Limited broadcast 255.255.255.255 and Direct broadcast e.g. 192.168.255.255 as well as
Multicast (224.0.0.0 through 239.255.255.255) on Ethernet are supported and transferred
over the network.
You can see an instructional video explaining the Bridge mode functionality here: http://www.racom.eu/ripex-bridge-mode
2.2.1. Detailed Description
Bridge mode is suitable for Point-to-Multipoint networks, where Master-Slave applications with pollingtype communication protocol are used. RipEX in bridge mode is as easy to use as a simple transparent
device, while providing communication reliability and spectrum efficiency by employing a sophisticated
protocol in the radio channel.
In bridge mode, the radio channel protocol does not solve collisions. There is a CRC check of data integrity, however, i.e. once a message is delivered, it is 100% error free.
All the messages received from user interfaces (ETH&COM) are immediately transmitted to the radio
channel.
ETH - The whole network of RipEX radiomodems behaves as a standard Ethernet network bridge.
Each ETH interface automatically learns which devices (MAC addresses) are located in the local LAN
and which devices are accessible over the radio channel. Consequently, only the Ethernet frames addressed to remote devices are physically transmitted on the radio channel. This arrangement saves
the precious RF spectrum from extra load which would be otherwise generated by local traffic in the
LAN (the LAN to which the respective ETH interface is connected).
One has to be very careful when RipEX in Bridge mode is connected to LAN, because all LAN traffic
is then broadcast to the Radio channel.
COM1,COM2 - All frames received from COM1(2) are broadcast over the radio channel and transmitted
to all COM ports (COM1 as well as COM2) on all radio modems within the network, the other COM on
the source RipEX excluding.
There is a special parameter TX delay (Adv. Config., Device), which should be used when all substations
(RTU) reply to a broadcast query from the master station. In such case massive collisions would ensue
because all substations (RTU) would reply at nearly the same time. To prevent such collision, TX delay
should be set individually in each slave RipEX. The length of responding frame, the length of radio
protocol overhead, modulation rate have to be taken into account.
2.2.2. Functionality example
In the following, common acronyms from SCADA systems are used:
• FEP - Front End Processor, designates the communication interface equipment in the centre
• RTU - Remote Telemetry Unit, the terminal SCADA equipment at remote sites
The single digits in illustrations are “site names” and do not necessarily correspond with actual addresses
of both the RipEX's and SCADA equipment. Address configuration examples are given in the next
chapter.
RipEX Radio modem & Router – © RACOM s.r.o.14
Page 15
RipEX in detail
Step 1
Polling cycle starts:
FEP sends a request packet for RTU3 through COM1 to
the connected RipEX.
Step 2
FEP’s RipEX broadcasts this packet on Radio channel.
RipEX3 and RipEX1 receive this packet.
RipEX2 doesn’t receive this packet, because it is not within
radio coverage of FEP’s RipEX.
Step 3
RipEX3 and RipEX1 send the received packet to their
COM1 and COM2.
Packet is addressed to RTU3, so only RTU3 responds.
RipEX1 is set as a repeater, so it retransmits the packet
on Radio channel. Packet is received by all RipEXes.
Step 4
RipEX2 sends repeated packet to its COM1 and COM2.
RTU2 doesn’t react, because the packet is addressed to
RTU3.
RipEX3 and FEP’s RipEX do not send the repeated
packet to their COM ports, because it has already been
sent (RipEX3) or received (FEP’s RipEX) on their COM
(anti-duplication mechanism).
RTU3 sends the reply packet.
Step 5
RipEX3 broadcasts the reply packet from RTU3 on Radio
channel.
Packet is received by RipEX1 and FEP’s RipEX.
15© RACOM s.r.o. – RipEX Radio modem & Router
Page 16
RipEX in detail
Step 6
FEP’s RipEX sends the packet (the reply from RTU3) to
FEP through COM1.
RipEX1 sends this packet to RTU1. RTU1 doesn’t react,
because the packet is addressed to FEP.
RipEX1 repeats the packet on Radio channel.
All RipEXes receive the packet.
Step 7
RipEX2 sends repeated packet to its COM1 and COM2.
RTU2 doesn’t react, because the packet is addressed to
FEP.
RipEX3 and FEP’s RipEXes do not send the repeated
packet to their COM ports, because it has been handled
already.
FEP processes the reply from RTU3 and polling cycle
continues…
2.2.3. Configuration examples
You can see an example of IP addresses of the SCADA equipment and RipEX's ETH interfaces in the
picture below.
In Bridge mode, the IP address of the ETH interface of RipEX is not relevant for user data communication. However it is strongly recommended to assign a unique IP address to each RipEXs' ETH interface,
since it allows for easy local as well as remote service access. Moreover, leaving all RipEX's with the
same (= default) IP on the ETH interface may cause serious problems, when more RipEX's are connected to the same LAN, even if by accident (e.g. during maintenance).
RipEX Radio modem & Router – © RACOM s.r.o.16
Page 17
192.168.5.51/24
192.168.5.50/24
192.168.5.12/24
192.168.5.2/24
192.168.5.3/24
192.168.5.11/24
192.168.5.1/24
192.168.5.13/24
3
FEP
50
1
2
REPEATER
RipEX in detail
Fig. 2.1: Bridge mode example
Repeater
Because using the bridge mode makes the network transparent, the use of repeaters has certain limitations. To keep matters simple we recommend using a single repeater. However, if certain rules are
observed, using multiple repeaters in the same network is possible.
The total number of repeaters in the network is configured for every unit individually under Bridge mode
parameters. This information is contained in every packet sent. All units that receive such packet will
resume transmission only after sufficient time has been allowed for the packet to be repeated. The
packets received from user ports remain buffered and are sent after the appropriate time passes. This
prevents collisions between remote radio modems. There can be no repeater collisions if only one repeater is used.
Where two or more repeaters are used, collisions resulting from simultaneous reception of a repeated
packet must be eliminated. Collisions happen because repeaters repeat packets immediately after reception, i.e. if two repeaters receive a packet from the centre, they both relay it at the same time. If
there is a radiomodem which is within the range of both repeaters, it receives both repeated packets
at the same time rendering them unreadable.
Examples:
17© RACOM s.r.o. – RipEX Radio modem & Router
Page 18
Centre RPT1 RPT2 Remote
1 2 3
X
COLLISION!
1
1
2
2
WRONG
CEN RPT1 RPT2 REM
GOOD
Coveragearea
1 2 3
CEN RPT1 RPT2 REM
1
2
Good
CEN RPT1 REM
RipEX in detail
1. Repeaters connected serially
A packet is transmitted and repeated
in steps 1, 2, 3.
In improperly designed networks collisions happen
if a remote radio modem lies in the range of two
repeaters (see the image): the packet sent from
the centre (1) is received by both repeaters. It is
repeated by them both (2) causing a collision at
the remote. In other words – there should not be
more than one repeater where the centre and remotes' coverage areas overlap.
Solution 1.
Adjust signal coverage so that RPT2 is out of range
of the centre and RPT1 is out of the range of the
remote radio modem. This can be achieved for
example by reducing the output power or using a
unidirectional antenna.
Solution 2.
Use a single repeater. (Whenever network layout
allows that.)
RipEX Radio modem & Router – © RACOM s.r.o.18
Page 19
2. Parallel repeaters
Centre
Repeater1
Remote1
1
2
1
2
Remote2
Repeater2
X
COLLISION!
GOOD
WRONG
1
2
1
2
CEN
CEN
RPT1
RPT1
REM1
REM1
1
2
1
2
REM2
REM2
RPT2
RPT2
2
RipEX in detail
Improperly designed network:
- RipEX REM1 is within the range
of two repeaters (RPT1 and RPT2).
The repeaters receive a packet (1)
from the centre (CEN) and repeat
it at the same time (2) causing a
collision at REM1.
Well-designed network:
- A remote is only in the range of a
single repeater (REM1-RPT1,
REM2-RPT2).
There is always only one repeater
where the centre and remote coverage areas overlap.
2.3. Router mode
RipEX works as a standard IP router with 2 independent interfaces: Radio and ETH. Each interface
has its own MAC address, IP address and mask.
IP packets are processed according to routing table rules. You can also set the router’s default gateway
(applies to both interfaces) in the routing table.
The COM ports are treated as standard host devices, messages can be delivered to them as UDP
datagrams to selected port numbers. The destination IP address of a COM port is either the IP of ETH
or the IP of a radio interface. The source IP address of outgoing packets from COM ports is always the
IP of the ETH interface.
The additional Virtual COM ports and Terminal server can act as other IP router ports. This enables
Serial and TCP based RTUs to be combined in one network.
Two different Radio protocols are available in the Router mode: Flexible and Base driven.
• Flexible
Suitable for master or even multi master-slave polling and report by exception from remotes concurrently. No limits in network design – each radio can work as base station, a repeater, a remote, or
• Base driven
all of these simultaneously
This protocol is optimized for TCP/IP traffic and/or 'hidden' Remotes in report-by-exception networks,
when a Remote is not be heard by other Remotes and/or different Rx and Tx frequencies are used.
It is suitable for a star network topology with up to 255 Remotes under one Base station, where
each Remote can simultaneously work as a Repeater for one or more additional Remotes.
19© RACOM s.r.o. – RipEX Radio modem & Router
Page 20
RipEX in detail
2.3.1. Router - Flexible, Detail description
Router mode with Flexible protocol is suitable for Multipoint networks of all topologies with unlimited
number of repeaters on the way, and all types of network traffic where Multi-master applications and
any combination of simultaneous polling and/or report-by-exception protocols can be used
Each RipEX can access the Radio channel spontaneously using sophisticated algorithms to prevent
collisions when transmitting to the Radio channel. Radio channel access is a proprietary combination
of CSMA and TDMA; the Radio channel is deemed to be free when there is no noise, no interfering
signals and no frames being transmitted by other RipEX stations. In this situation, a random selection
of time slots follows and a frame is then transmitted on the Radio channel.
Frame acknowledgement, retransmissions and CRC check, guarantee data delivery and integrity even
under harsh interference conditions on the Radio channel.
2.3.2. Router - Flexible, Functionality example
In the following example, there are two independent SCADA devices connected to RipEX's two COM
ports. One is designated RTU (Remote Telemetry Unit) and is assumed to be polled from the centre
by the FEP (Front End Processor). The other is labelled PLC (Programmable Logic Controller) and is
assumed to communicate spontaneously with arbitrary chosen peer PLCs.
Step 1
FEP sends a request packet for RTU1 through COM2 to
its connected RipEX.
Simultaneously PLC2 sends a packet for PLC1 to RipEX2
through COM1.
Step 2
FEP’s RipEX transmits an addressed packet for RTU1 on
Radio channel.
RipEX1 receives this packet, checks data integrity and
transmits the acknowledgement.
At the same time packet is sent to RTU1 through COM2.
RipEX3 receives this packet too. It doesn’t react, because
this packet is directed to RipEX1 only.
Step 3
RipEX2 waits till previous transaction on Radio channel is
finished (anti-collision mechanism).
Then RipEX2 transmits on Radio channel the addressed
packet for PLC1.
RipEX1 receives this packet, checks data integrity and
transmits acknowledgement.
At the same time packet is sent to PLC1 through COM1.
Simultaneously the reply packet from RTU1 for FEP is received on COM2.
RipEX Radio modem & Router – © RACOM s.r.o.20
Page 21
RipEX in detail
Step 4
RipEX1 transmitts the reply packet from RTU1 for FEP on
Radio channel.
All RipEXes receive this packet. This packet is addressed
to FEP’s RipEX, so only FEP’s RipEX reacts. It checks
data integrity and transmits the acknowledgement to
RipEX1.
At the same time the packet is sent to FEP through COM2.
Step 5
FEP receives the response from RTU1 and polling cycle
continues…
However any PLC or RTU can spontaneously send a
packet to any destination anytime.
2.3.3. Router - Flexible, Configuration examples
As it was mentioned above, RipEX radiomodem works as a standard IP router with two independent
interfaces: radio and ETH. Each interface has got its own MAC address, IP address and mask.
The IP router operating principles stipulate that every unit can serve as a repeater.. Everything what
is needed is the proper configuration of routing tables.
Radio IP addresses of the RipEX’s required to communicate over the radio channel must share the
same IP network. We recommend planning your IP network so that every RipEX is connected to a
separate sub-network over the Ethernet port. This helps to keep the routing tables clear and simple.
Note
Even if the IP addresses of all RipEXes in a radio channel share a single IP network, they
may not be communicating directly as in a common IP network. Only the RipEXes that are
within the radio range of each other can communicate directly. When communication with
radio IP addresses is required, routing tables must include even the routes that are within
the same network (over repeaters), which is different from common IP networks. The example
configuration below does not show such routing rules for the sake of simplicity (they are not
needed in most cases).
21© RACOM s.r.o. – RipEX Radio modem & Router
Page 22
10.10.10.50/24
192.168.50.2/24
RoutingtableRipEX50:
192.168.1.0/24 10.10.10.1
192.168.2.0/24 10.10.10.1
192.168.3.0/24 10.10.10.3
DefaultGW192.168.50.2
è
è
è
192.168.2.2/24
Routingtable :
192.168.1.0/24 10.10.10.1
RipEX2
192.168.50.0/24 10.10.10.1
192.168.3.0/24 10.10.10.1
è
è
è
10.10.10.3/24
192.168.3.2/24
RoutingtableRipEX3:
192.168.50.0/24 10.10.10.50
192.168.1.0/24 10.10.10.50
192.168.2.0/24 10.10.10.50
è
è
è
10.10.10.1/24
192.168.1.1/24
192.168.1.2/24
Routingtable :
192.168.2.0/24 10.10.10.2
RipEX1
192.168.50.0/24 10.10.10.50
192.168.3.0/24 10.10.10.50
è
è
è
192.168.3.1/24
3
50
FEP
1
192.168.50.1/24
RadioIP
ETHIP
FEP IP
10.10.10.2/24
2
192.168.2.1/24
RipEX in detail
Fig. 2.2: Router - Flexible, Addressing
Formal consistency between the last byte of the radio IP address and the penultimate byte of the Ethernet address is not necessary but simplifies orientation. The “Addressing” image shows a routing table
next to every RipEX. The routing table defines the next gateway for each IP destination. In radio
transmission, the radio IP of the next radio-connected RipEX serves as the gateway.
Example of a route from FEP (RipEX 50) to RTU 2:
• The destination address is 192.168.2.2
• The routing table of the RipEX 50 contains this record:
• Based on this record, all packets with addresses in the range from 192.168.2.1 to 192.168.2.254
• Because RipEX 50’s radio IP is 10.10.10.50/24, the router can tell that the IP 10.10.10.1 belongs
• The packet is received by RipEX 1 with the address 10.10.10.1 where it enters the router
• The routing table of RipEX 1 contains the record:
• The packet is received by RipEX 2
• The router compares the destination IP 192.168.2.2 with its own Ethernet address 192.168.2.1/24
Destination 192.168.2.0/24 Gateway 10.10.10.1
are routed to 10.10.10.1
to the radio channel and sends the packet to that address over the radio channel
Destination 192.168.2.0/24 Gateway 10.10.10.2
based on which the packet is routed to 10.10.10.2 over the radio channel
and determines that the packet’s destination is within its ETH network and sends the packet over
the Ethernet interface – eventually, the packet is received by RTU 2.
RipEX Radio modem & Router – © RACOM s.r.o.22
Page 23
10.10.10.50/24
192.168.50.2/24
RoutingtableRipEX50:
192.168.0.0/22 10.10.10.1
192.168.4.0/22 10.10.10.4
DefaultGW192.168.50.2
è
è
10.10.10.2/24
192.168.2.1/24
192.168.2.2/24
Routingtable :
192.168.0.0/16 10.10.10.1
RipEX2
è
10.10.10.4/24
192.168.4.2/24
RoutingtableRipEX4:
192.168.0.0/16 10.10.10.50
è
10.10.10.1/24
192.168.1.1/24
192.168.1.2/24
Routingtable :
192.168.2.0/24 10.10.10.2
RipEX1
192.168.0.0/16 10.10.10.50
è
è
192.168.4.1/24
4
50
FEP
1
2
RadioIP
ETHIP
FEP IP
192.168.50.1/24
RipEX in detail
2.3.4. Router - Flexible, Addressing hints
In large and complex networks with numerous repeaters, individual routing tables may become long
and difficult to comprehend. To keep the routing tables simple, the addressing scheme should follow
the layout of the radio network.
More specifically, every group of IP addresses of devices (both RipEX's and SCADA), which is accessed
via a repeater, should fall in a range which can be defined by a mask and no address defined by that
mask exists in different part of the network.
A typical network consisting of a single centre and number of remotes has got a tree-like layout, which
can be easily followed by the addressing scheme – see the example in the Figure Optimised addressing
below.
Fig. 2.3: Router - Flexible, Optimised addressing
The default gateway is also a very powerful routing tool, however be very careful whenever the default
route would go to the radio interface, i.e. to the radio channel. If a packet to non-existing IP destination
came to the router, it would be transmitted over the radio channel. Such packets increase the load of
the network at least, cause excessive collisions, may end-up looping etc. Consequently the default
route should always lead to the ETH interface, unless you are perfectly certain that a packet to nonexisting destination IP may never appear (remember you are dealing with complex software written
and configured by humans).
23© RACOM s.r.o. – RipEX Radio modem & Router
Page 24
RipEX in detail
2.3.5. Router - Base driven, Detail description
All traffic over the Radio channel is managed by the Base station. Radio channel access is granted by
a deterministic algorithm resulting in collision free operation regardless of the network load. Uniform
distribution of Radio channel capacity among all Remotes creates stable response times with minimum
jitter in the network.
All communication on Radio channel is controlled by the Base station; all frames inside the radio network
have to be routed through the Base station. Appropriate routing has to be set.
Base station can communicate with different Modulation data speeds and different FEC settings.
Any Remote can work as a Repeater for another Remote. Only one Repeater is possible between Base
station and Remote, however a number of Remotes can use the same Repeater.
There is no need to set any routes in Routing table(s) for Remote stations located behind Repeater.
Forwarding of frames from the Base station over the Repeater in either direction is serviced transparently
by the Base driven protocol.
When Remote to Remote communication is required, respective routes via the Base station must be
set in Routing tables in the Remotes.
Frame acknowledgement, retransmissions and CRC check, guarantee data delivery and integrity even
under harsh interference conditions on the Radio channel.
2.3.6. Router - Base driven, Functionality example
A star topology with one repeater is used in the following example of a SCADA network using a polling
and report by exception combination. The Repeater is also serving as a Remote radio. The packets’
acknowledgement on Radio channel is used for transmissions in both directions in the example
Step 1
Base RipEX regularly checks the
queue status of remote RipEX
radios for which it has no
queueing information. The feedback enables the Base station to
manage time allocations for all
Remotes to transmit.
Step 2
FEP sends a request packet to
RTU1 via Base RipEX; Base
RipEX packet transmits in
shortest possible time. Remote
RipEX1 receives the packet and
hands it over to RTU1, simultaneously acknowledging packet receipt to the Base RipEX.
Fig. 2.4: Router - Base driven, Functionality example
sends the reply to Remote RipEX1. During the checking process the Base RipEX detects a prepared
packet in the queue of RipEX1 and subsequently allots a Radio channel for transmission of the packet.
RipEX Radio modem & Router – © RACOM s.r.o.24
Step 3
RTU1 processes the request and
Page 25
RipEX in detail
Remote RipEX 1 transmits the packet. If the Base RipEX successfully receives the packet, it sends an
acknowledgement and then the Remote RipEX1 clears the packet from the queue. A part of the relation
includes a hand over of information about the number of packets waiting in the queue.
Step 4
RTU2 is connected to Remote RipEX2 behind Repeater RipEX1, which manages all communication
between the Base RipEX and Remote RipEX2.
2.3.7. Router - Base driven, Configuration example
As already mentioned, RipEX works as a standard IP router with two independent interfaces: Radio
and ETH. Each interface has its own MAC address, IP address and mask.
When Base driven protocol is used, Radio IP addresses for all RipEX units must share the same IP
subnet.
The Base driven protocol routing table for each Remote RipEX can be simplified to a default gateway
route rule directed to Base RipEX Radio IP. Only one record with respective IP address/mask combination for each remote station is needed in the Base RipEX routing table.
The repeaters are not considered in routing in Base driven protocol. Each Remote RipEX uses its own
Radio IP address as a gateway in the routing table of the Base RipEX.
See chapter Advanced Configuration/ Settings/ Radio/ Base driven for more.
Fig. 2.5: Router - Base driven, Addressing
Important
For those accustomed to using the Flexible Radio protocol:
Settings for radios connected over a repeater differ considerably in Base driven protocol.
25© RACOM s.r.o. – RipEX Radio modem & Router
Page 26
RipEX in detail
NOTE: When only serial protocols are used (and Optimization is not active), there is no need to use
Routing tables. Instead of using Routing tables records, Address translation in COM protocol settings
is used. Serial protocol address to IP address translation rules apply where the Radio IP addresses
are used. Radio IP addresses will only be used for maintenance in such circumstances.
Fig. 2.6: Router - Base driven, Addressing - Serial
RipEX Radio modem & Router – © RACOM s.r.o.26
Page 27
RipEX in detail
2.4. Serial SCADA protocols
Even when the SCADA devices are connected via serial port, communication remains secured and
address-based in all directions (centre-RTU, RTU-centre, RTU-RTU).
In router mode, RipEX utilises a unique implementation of various SCADA protocols (Modbus, IEC101,
DNP3, PR2000, Comli, RP570, C24, DF1, Profibus). In this implementation SCADA protocol addresses
are mapped to RipEX addresses and individual packets are transmitted as acknowledged unicasts.
Polled remote units respond to the unit that contacted them (multi master network possible) using secure
packets. When needed, RTU-RTU parallel communication is also possible.
2.4.1. Detailed Description
Each SCADA protocol, such as Modbus, DNP3, IEC101, DF1, etc., has its own unique message format,
and more importantly, its unique way of addressing remote units. The basic task for protocol utility is
to check whether a received frame is in the correct protocol format and uncorrupted. Most of the SCADA
protocols use some type of error detection codes (Checksum, CRC, LRC, BCC, etc.) for data integrity
control, so RipEX calculates this code and check it with the received one.
RipEX radio network works in IP environment, so the basic task for the protocol interface utility is to
convert SCADA serial packets to UDP datagrams. Address translation settings are used to define the
destination IP address and UDP port. Then these UDP datagrams are sent to RipEX router, processed
and typically forwarded as unicasts over the radio channel to their destination. If the gateway defined
in the routing table belongs to the Ethernet LAN, UDP datagrams are rather forwarded to the Ethernet
interface. After reaching the gateway (typically a RipEX router), the datagram is again forwarded according to the routing table.
Above that, RipEX is can to handle even broadcast packets from serial SCADA protocols. When
broadcasts are enabled in the respective Protocol settings, the defined packets are treated as broadcast
(e.g. they are not acknowledged on Radio channel). On the Repeater station, it is possible to set
whether broadcast packets shall be repeated or not.
Note
Broadcast packets are supported only on serial interfaces. Neither broadcast nor mul-
1.
ticast are supported on Ethernet when in Router mode.
2. UDP datagrams can be acknowledged on the radio channel (ACK parameter of router
mode) but they are not acknowledged on the Ethernet channel.
When a UDP datagram reaches its final IP destination, it should be in a RipEX router again (either its
ETH or radio interface). It is processed further according its UDP port. Either it is delivered to COM1(2)
port daemon, where the datagram is decapsulated and the data received on serial interface of the
source unit is forwarded to COM1(2), or the UDP port is that of a Terminal server or any other special
protocol daemon on Ethernet like Modbus TCP etc. Then the datagram is processed by that daemon
accordingly to the respective settings.
RipEX uses a unique, sophisticated protocol on the radio channel. It guaranties data integrity even
under heavy interference or weak signal conditions due to the 32 bit CRC used, minimises the likelihood
of a collision and retransmits frames when collision happens, etc. These features allow for the most
efficient SCADA application arrangements to be used, e.g. multi-master polling and/or spontaneous
communication from remote units and/or parallel communication between remote units, etc.
27© RACOM s.r.o. – RipEX Radio modem & Router
Page 28
RipEX in detail
Important
The anti-collision protocol feature is available only in the router mode. The bridge mode is
suitable for simple Master-Slave arrangements with polling-type application protocol.
2.5. Combination of IP and serial communication
RipEX enables combination of IP and serial protocols within a single application.
Five independent terminal servers are available in RipEX. A terminal server is a virtual substitute for
devices used as serial-to-TCP(UDP) converters. It encapsulates serial protocol to TCP(UDP) and vice
versa eliminating the transfer of TCP overhead over the radio channel.
If the data structure of a packet is identical for IP and serial protocols, the terminal server can serve as
a converter between TCP(UDP)/IP and serial protocols (RS232, RS485).
RipEX also provides a built-in converter Modbus RTU – Modbus TCP, where data structure is not the
same, so one application may combine both protocols, Modbus RTU and Modbus TCP.
You can see an instructional video explaining the Terminal server functionality here: http://www.racom.eu/ripex-terminal
2.5.1. Detailed Description
Generally, a terminal server (also referred to as serial server) enables connection of devices with a
serial interface to a RipEX over the local area network (LAN). It is a virtual substitute for the devices
used as serial-to-TCP(UDP) converters.
Examples of the use:
A SCADA application in the centre should be connected to the radio network via serial interface, however,
for some reason that serial interface is not used. The operating system (e.g. Windows) can provide a
virtual serial interface to such application and converts the serial data to TCP (UDP) datagrams, which
are then received by the terminal server in RipEX. This type of connection between RipEX and application provides best results when:
• There is no hardware serial interface on the computer
• Serial cable between RipEX and computer would be too long. E.g. the RipEX is installed very close
to the antenna to reduce feed line loss.
• LAN already exists between the computer and the point of installation
Important
The TCP (UDP) session operates only locally between RipEX and the central computer,
hence it does not increase the load on the radio channel.
In special cases, the terminal server can reduce network load from TCP applications . A TCP session
can be terminated locally at the terminal server in RipEX, user data extracted from the TCP messages
and processed as if it came from a COM port. When the data reaches the destination RipEX, it can be
transferred to the RTU either via the serial interface or via TCP (UDP), using the terminal server again.
Please note, that RipEX Terminal server implementation also supports the dynamical IP port change
in every incoming application datagram. In such case the RipEX sends the reply to the port from which
the last response has been received. This feature allows to extend the number of simultaneously
RipEX Radio modem & Router – © RACOM s.r.o.28
Page 29
RipEX in detail
opened TCP connections between the RipEX and the locally connected application up to 10 on each
Terminal server.
2.6. Diagnostics & network management
RipEX radiomodem offers a wide range of built-in diagnostics and network management tools.
2.6.1. Logs
There are ‘Neighbours’ and Statistic logs in RipEX. For both logs there is a history of 20 log files
available, so the total history of saved values is 20 days (assuming the default value of 1440 min. is
used as the Log save period).
Neighbours
The ‘Neighbours’ log provides information about neighbouring units (RipEX’s which can be accessed
directly over the radio channel, i.e. without a repeater). Every RipEX on the network regularly broadcasts
its status, the set of so called “Watched values”: the probability of packet loss when transmitting data
over the radio channel, current supply voltage, internal temperature, measured RF output power, the
Voltage Standing Wave Ratio on the antenna feed line and the total number of packets received from
/ transmitted to ETH, COM1, COM2 interfaces. In addition, the RipEX that records this data in its log
also keeps track of how many times it listened to its neighbouring unit as well as of the RSS and DQ
recorded. See Adv. Conf., Diagnostic for more.
Statistic
The ‘Statistic’ log provides information about the volume of data traffic on all interfaces: radio, ETH,
COM1, COM2. It offers detailed information about the number of transmitted packets, their size and
the throughput per second. Moreover, a detailed division into user and service packets is available for
the radio channel. See chapter Adv. Conf., Diagnostic for more.
2.6.2. Graphs
An independent database periodically stores the Watched values (see 'Neighbours' log above) from
up to five neighbouring RipEX's and from the local one, there including most important values from the
Statistic log. All these values can be displayed as graphs.
The graphs are available in summary and detailed versions. Detailed logging is triggered on when a
threshold value has been reached for the specific item to enable a more detailed investigation into the
units’ operation when an alarm event occurs. Each graph can display two different elements at once,
including their set thresholds. Each of the values may originate from a different RipEX unit.
See chapter Adv. Conf., Graphs for more.
2.6.3. SNMP
RipEX implements an SNMPv1/v2c and SNMPv3. The values provided by RipEX are shown in the
MIB table, its Severity level is 3. RipEX also allows generating SNMP traps when thresholds have been
reached for the monitored values: RSScom, DQcom, TXLost[%], Ucc, Temp, PWR, VSWR, ETH[Rx/Tx],
COM1[Rx/Tx], COM2[Rx/Tx], HW Alarm Input and/or for some internal warnings and errors.
29© RACOM s.r.o. – RipEX Radio modem & Router
Page 30
COM PORTS
MODULE
ROUTER
&
BRIDGE
MODULE
TERMINAL & MODBUS TCP
SERVERS
& TCP PROXY
RADIO
CHANNEL
MODULE
COM1
COM2
ETH
RADIO
virtual com/TCP ethernet
Radio Modem Unit
Rx
Tx
Rx
MP1
MP6
MP5MP3
MP7
MP2
MP4
Rx RxRx
Rx
Rx
Tx
Tx TxTx
Tx
Tx
COM: phy COM: rou RF: rou RF: phy
RipEX in detail
See chapter RipEX App notes, SNMP for RACOM RipEX1for more.
MIB table can be found there too.
2.6.4. Ping
To diagnose the individual radio links RipEX is equipped with an enhanced Ping tool. In addition to the
standard info such as the number of sent and received packets or the round trip time, it provides the
overall load, the resulting throughput, BER, PER and specific data about the quality of the radio transmission, RSS and DQ for the weakest radio link on the route.
See chapter Adv. Conf., Ping for details.
2.6.5. Monitoring
Monitoring is an advanced on-line diagnostic tool, which enables a detailed analysis of communication
over any of the interfaces of a RipEX router. In addition to all the physical interfaces (RADIO, ETH,
COM1, COM2), some internal interfaces between software modules (e.g. Terminal servers, Modbus
TCP server etc.) can be monitored when such advanced diagnostics is needed.
Monitoring output can be viewed on-line or saved to a file in the RipEX (e.g. a remote RipEX) and
downloaded later.
Fig. 2.7: Interfaces
See chapter Adv. Conf., Monitoring for details.
2.7. Firmware update and upgrade
Occasionally RipEX firmware update or upgrade is released. An update improves functionality and/or
fix software bugs. Updates can be downloaded for free from www.racom.eu2.
1
http://www.racom.eu/eng/products/m/ripex/app/snmp.html
2
http://www.racom.eu
RipEX Radio modem & Router – © RACOM s.r.o.30
Page 31
RipEX in detail
A firmware upgrade implements significant improvements and new functions which take the product
to a new level. Downloading and applying a firmware upgrade is the same as with firmware update.
However a software key may have to be purchased and applied to activate the new functionality or the
upgrade itself (see the next chapter).
See chapter Adv. Conf., Firmware for more.
2.8. Software feature keys
Certain advanced RipEX features are activated with software keys. SW feature keys enable the users
to initially purchase only the functionality they require and buy additional functions as the requirements
and expectations grow. Similarly, when some features (e.g. COM2) are required on certain sites, the
corresponding key can be activated only where needed.
• Keys protect the investment into hardware. Thanks to SDR-based hardware design of RipEX no
physical replacement is necessary – the user simply buys a key and activates the feature.
• For evaluation and testing, Time-limited keys can be supplied. These keys activate the coded feature
for a limited operational (power on) time only. Free Master-key trial for 30 days is in every RipEX.
• Software keys are always tied to a specific RipEX production code.
See chapter Model offerings SW feature keys for more.
31© RACOM s.r.o. – RipEX Radio modem & Router
Page 32
Network planning
3. Network planning
The significance of planning for even a small radio network is often neglected. A typical scenario in
such cases goes as follows – there's not enough time (sometimes money) to do proper planning, so
the network construction is started right away while decisions on antennas etc. are based mainly on
budget restrictions. When the deadline comes, the network is ready but its performance does not meet
the expectations. Finally the (expensive) experts are invited to fix the problem and that fix costs ten
times more than a proper design process done beforehand would have.
The following paragraphs are not a guide to network planning – that is a topic far beyond the scope of
a product manual. What is provided is the essential RipEX data needed plus some comments on
common problems which should be addressed during the planning process.
3.1. Data throughput, response time
A UHF radio network provides very limited bandwidth for principal reasons. Hence the first and very
important step to be taken is estimating/calculating the capacity of the planned network. The goal is to
meet the application bandwidth and time-related requirements. Often this step determines the layout
of the network, for example when high speed is necessary, only near-LOS (Line-of-sight) radio hops
can be used.
RipEX offers an unprecedented range of data rates. The channel width available and signal levels expected/measured on individual hops limit the maximum rate which can be used. The data rate defines
the total capacity of one radio channel in one area of coverage, which is shared by all the radio modems
within the area. Then several overhead factors, which reduce the total capacity to 25-90% of the "raw"
value, have to be considered. They are e.g. RF protocol headers, FEC, channel access procedures
and number of store-and-forward repeaters. There is one positive factor left – an optimum compression
(e.g. IP optimization) can increase the capacity by 20-200%.
All these factors are heavily influenced by the way the application loads the network. For example, a
simple polling-type application results in very long alarm delivery times – an event at a remote is reported
only when the respective unit is polled. However the total channel capacity available can be 60-95%
of the raw value, since there are no collisions. A report-by-exception type of load yields much better
application performance, yet the total channel capacity is reduced to 25-35% because of the protocol
overhead needed to avoid and solve collisions.
The basic calculations of network throughput and response times for different RipEX settings can be
done at www.racom.eu1.
Let us add one comment based on experience. Before committing to the actual network design, it is
very wise to do a thorough bench-test with real application equipment and carefully monitor the load
generated. A difference against the datasheets, which may be negligible in a LAN environment, may
have fundamental consequences for the radio network design. To face that "small" difference when
the network is about to be commissioned may be a very expensive experience. The bench test layout
should include the application centre, two remotes (at least) and the use of a repeater. See the following
picture for an example.
1
http://www.racom.eu/eng/products/radio-modem-ripex.html#calculation
RipEX Radio modem & Router – © RACOM s.r.o.32
Page 33
Centre
RTU
config.PC
RTU
dummy
antenna
Fig. 3.1: Application bench test
3.2. Frequency
Network planning
Often the frequency is simply given. If there is a choice, using the optimum frequency range can make
a significant difference. Let us make a brief comparison of the most used UHF frequency bands.
160 MHz
The best choice when you have to cover a hilly region and repeaters are not an option. The only frequency of the set of options which can possibly make it to a distant valley, 20 km from your nearest
point-of-presence, it can reach a ship 100 km from the shore base. The penalty you pay is tremendous
– high level of noise in urban and industry areas, omnipresent multi-path propagation, vulnerability to
numerous special propagation effects in troposphere etc. Consequently this frequency band is suitable
for low speeds using robust modulation techniques only, and even then a somewhat lower long-term
communication reliability has to be acceptable for the application.
350 MHz
Put simply, character of this band is somewhere between 160 and 450 MHz.
450 MHz
The most popular of UHF frequency bands. It still can get you slightly “beyond the horizon”, while the
signal stability is good enough for 99% (or better) level of reliability. Multi-path propagation can be a
problem, hence high speeds may be limited to near-LOS conditions. Urban and industrial noise does
not pose a serious threat (normally), but rather the interference caused by other transmissions is quite
frequent source of disturbances.
900 MHz
This band requires planning the network in “microwave” style. Hops longer than about 1 km have to
have “almost” clear LOS (Line-of-sight). Of course a 2–5 km link can handle one high building or a
bunch of trees in the middle, (which would be a fatal problem for e.g. an 11 GHz microwave). 900 MHz
also penetrates buildings quite well, in an industrial environment full of steel and concrete it may be
the best choice. The signal gets “everywhere” thanks to many reflections, unfortunately there is bad
33© RACOM s.r.o. – RipEX Radio modem & Router
Page 34
TX
output
RX
input
feedline
loss
feedline
loss
pathloss
TX
antenna
gain
RX
antenna
gain
+ +
Network planning
news attached to this - the reliability of high speed links in such environment is once again limited.
Otherwise, if network capacity is your main problem, then 900 MHz allows you to build the fastest and
most reliable links. The price you pay (compared to lower frequency bands) is really the price – more
repeaters and higher towers increase the initial cost. Long term reliable performance is the reward.
The three frequency bands discussed illustrate the simple basic rules – the higher the frequency, the
closer to LOS the signal has to travel. That limits the distance over the Earth's surface – there is no
other fundamental reason why shorter wavelengths could not be used for long distance communication.
On the other hand, the higher the frequency, the more reliable the radio link is. The conclusion is then
very simple – use the highest frequency band you can.
3.3. Signal budget
For every radio hop which may be used in the network, the signal level at the respective receiver input
has to be calculated and assessed against requirements. The fundamental requirements are two – the
data rate, which is dictated by total throughput and response times required by the application, and the
availability, which is again derived from the required reliability of the application. The data rate translates
to receiver sensitivity and the availability (e.g. 99,9 % percent of time) results in size of the fade margin.
The basic rule of signal budget says, that the difference between the signal level at the receiver input
and the guaranteed receiver sensitivity for the given data rate has to be greater than the fade margin
required:
RX signal [dBm] – RX sensitivity [dBm] >= Fade margin [dB]
To calculate the RX signal level, we follow the RF signal path:
Fig. 3.2: Signal path
example:RX signal [dBm] =
dBm (TX output 1 W)+30.0+ TX output [dBm]
dB (20m cable RG-213 U, 400 MHz)-2.5- TX antenna feeder loss [dB]
RipEX Radio modem & Router – © RACOM s.r.o.34
dBi (half-wave dipole, 0 dBd)+2.1+TX antenna gain [dBi]
dB (calculated from field measurement)-125.0- Path loss [dB]
dBi (7-el Yagi antenna, 7.6 dBd)+9.7+ RX antenna gain [dBi]
dB (10 m cable RG-58 CU, 400 MHz)-3.1- RX antenna feeder loss [dB]
dBm Received Signal Strength (RSS)= -88.8
Page 35
Network planning
The available TX output power and guaranteed RX sensitivity level for the given data rate have to be
declared by the radio manufacturer. RipEX values can be found in Table 4.6, “Technical parameters”
and Chap Section 4.4.1, “Detailed Radio parameters”. Antenna gains and directivity diagrams have to
be supplied by the antenna manufacturer. Note that antenna gains against isotropic radiator (dBi)
are used in the calculation. The figures of feeder cable loss per meter should be also known. Note that
coaxial cable parameters may change considerably with time, especially when exposed to an outdoor
environment. It is recommended to add a 50-100 % margin for ageing to the calculated feeder loss.
3.3.1. Path loss and fade margin
The path loss is the key element in the signal budget. Not only does it form the bulk of the total loss,
the time variations of path loss are the reason why a fade margin has to be added. In reality, very often
the fade margin is the single technical figure which expresses the trade-off between cost and performance of the network. The decision to incorporate a particular long radio hop in a network, despite that
its fade margin indicates 90 % availability at best, is sometimes dictated by the lack of investment in a
higher tower or another repeater. Note that RipEXs Auto-speed feature allows the use of a lower data
rate over specific hops in the network, without the need to reduce the rate and consequently the
throughput in the whole network. Lower data rate means lower (= better) value of receiver sensitivity,
hence the fade margin of the respective hop improves. See the respective Application note to learn
more on the Auto-speed feature. Apart of Auto-speed, there is a possibility from fw ver. 1.6 to set certain
Radio protocol parameters individually for a specific radio hop (Individual link options). For more see
Section 7.3.2, “Radio”
When the signal path profile allows for LOS between the TX and RX antennas, the standard formula
for free-space signal loss (below) gives reliable results:
Path loss [dB] = 20 * log10 (distance [km]) + 20 * log10 (frequency [MHz]) + 32.5
In the real world the path loss is always greater. UHF radio waves can penetrate obstacles (buildings,
vegetation), can be reflected from flat objects, can bend over round objects, can disperse behind sharp
edges – there are numerous ways how a radio signal can propagate in non-LOS conditions. The additional loss when these propagation modes are involved (mostly combined) is very difficult to calculate.
There are sophisticated methods used in RF design software tools which can calculate the path loss
and its variations (statistical properties) over a computer model of terrain. Their accuracy is unfortunately
very limited. The more obstacles on the path, the less reliable is the result. Such a tool can be very
useful in the initial phase of network planning, e.g. to do the first network layout for the estimate of total
throughput, however field measurements of every non-LOS radio hop should be done before the final
network layout is designed.
Determining the fade margin value is even more difficult. Nevertheless the software tools mentioned
can give some guidance, since they can calculate the statistical properties of the signal. Generally the
fade margin (for given availability) is proportional to the difference between the real path loss and the
LOS path loss over the same distance. Then it is about inversely proportional to frequency (in the UHF
range at least). To give an example for 10 km, non-LOS, hop on 450 MHz, fade margin of 20 dB is a
bare minimum. A field test may help again, provided it is run for longer period of time (hours-days).
RipEX diagnostic tools (ping) report the mean deviation of the RSS, which is a good indication of the
signal stability. A multiple of the mean deviation should be added to the fade margin.
3.4. Multipath propagation, DQ
Multipath propagation is the arch-enemy of UHF data networks. The signal coming out of the receiving
antenna is always a combination of multiple signals. The transmitted signal arrives via different paths,
by the various non-LOS ways of propagation. Different paths have different lengths, hence the waveforms
35© RACOM s.r.o. – RipEX Radio modem & Router
Page 36
TXantenna
Network planning
are in different phases when hitting the receiving antenna. They may add-up, they may cancel each
other out.
Fig. 3.3: Multipath propagation
What makes things worse is that the path length changes over time. Since half the wavelength – e.g.
0.3 m at 450 MHz - makes all the difference between summation and cancellation, a 0.001% change
of a path length (10 cm per 10 km) is often significant. And a small change of air temperature gradient
can do that. Well, that is why we have to have a proper fade margin. Now, what makes things really
bad is that the path length depends also on frequency. Normally this dependency is negligible within
the narrow channel. Unfortunately, because of the phase combinations of multiple waveforms, the
resulting signal may get so distorted, that even the sophisticated demodulating techniques cannot read
the original data. That is the situation known to RF data network engineers – signal is strong enough
and yet “it” does not work.
That is why RipEX reports the, somewhat mystic, figure of DQ (Data Quality) alongside the RSS. The
software demodulator uses its own metrics to assess the level of distortion of the incoming signal and
produces a single number in one-byte range (0–255), which is proportionate to the “quality” of the signal.
Though it is very useful information, it has some limitations. First, it is almost impossible to determine
signal quality from a single packet, especially a very short one. That results in quite a jitter of DQ values
when watching individual packets. However when DQ keeps jumping up and down it indicates a serious
multipath problem. In fact, when DQ stays low all the time, it must be noise or permanent interference
behind the problem. The second issue arises from the wide variety of modulation and data rates RipEX
supports. Though every attempt has been made to keep the DQ values modulation independent, the
differences are inevitable. In other words, experience is necessary to make any conclusions from DQ
reading. The less experience you have, the more data you have to collect on the examined link and
use other links for comparison.
The DQ value is about proportional to BER (bit error ratio) and about independent of the data rate and
modulation used. Hence some rule-of-thumb values can be given. Values below 100 mean the link is
unusable. For a value of 125, short packets should get through with some retransmissions, 150–200
means occasional problems will exist (long term testing/evaluation of such link is recommended) and
values above 200 should ensure reliable communication.
3.4.1. How to battle with multipath propagation?
The first step is the diagnosis. We have to realize we are in trouble and only a field measurement can
tell us that. We should forget about software tools and simply assume that a multipath problem may
appear on every non-LOS hop in the network.
These are clear indicators of a serious multipath propagation problem:
RipEX Radio modem & Router – © RACOM s.r.o.36
Page 37
TXantenna
better
multipath
Network planning
• directional antennas "do not work", e.g. a dipole placed at the right spot yields a better RSS than
a long Yagi, or rotating the directional antenna shows several peaks and troughs of the signal and
no clear maximum
• RSS changes rapidly (say 10 dB) when antenna is moved by less than a meter in any direction
• ping test displays the mean deviation of RSS greater than 6 dB
• DQ value keeps "jumping" abnormally from frame to frame
Quite often all the symptoms mentioned can be observed at a site simultaneously. The typical "beginner"
mistake would be to chase the spot with the best RSS with an omnidirectional antenna and installing
it there. Such a spot may work for several minutes (good luck), sometimes for several weeks (bad luck,
since the network may be in full use by then). In fact, installing in such a spot guaranties that trouble
will come - the peak is created by two or more signals added up, which means they will cancel out
sooner or later.
The right strategy is to find an arrangement where a single signal becomes dominant, possibly the
most stable one. "Sweeping" a directional antenna around the place (in different heights and with different polarization) can tell us where the signals come from. If individual signals come from different
directions, there is a good chance a long yagi can solve the problem by selecting just one of the bunch.
Finding a spot where the unwanted signal is blocked by a local obstacle may help as well (e.g. installing
at a side of the building instead of at the roof).
Fig. 3.4: Antenna location
When the multiple signals come from about the same direction, a long yagi alone would not help much.
We have to move away from the location, again looking for a place where just one of the signals becomes
dominant. 20–50 metres may save the situation, changing the height (if possible) is often the right
solution. Sometimes changing the height means going down, not up, e.g. to the base of the building
or tower.
We have to remember our hop has two ends, i.e. the solution may be to change antenna or its placement
at the opposite end. If everything fails, it is better to use another site as a repeater. Even if such problematic site seems to be usable after all (e.g. it can pass commissioning tests), it will keep generating
problems for ever, hence it is very prudent to do something about it as early as possible.
Note
Never design hops where a directional antenna is used for a direction outside its main lobe.
However economical and straightforward it may seem, it is a dangerous trap. Enigmatic
cases of drop-outs lasting couple of minutes every other day, over a clear LOS hops were
created exactly like that. They look like interference which is very difficult to identify and ,
37© RACOM s.r.o. – RipEX Radio modem & Router
Page 38
combiner
correctly
incorrectly
Network planning
alas, they are caused by pure multipath propagation, a self-made one. So always use a
combiner and another directional antenna if such arrangement is needed. Always.
Fig. 3.5: Main lobe
3.5. Network layout
In general a radio network layout is mostly (sometimes completely) defined by the application. When
the terrain allows for direct radio communication from all sites in the network, the designer can not do
too much wrong. Unfortunately for RF network designers, the real world is seldom that simple.
The conditions desireable for every single radio hop were discussed in previous paragraphs. If we are
lucky, assuming different layouts meeting those conditions are possible, we should exploit those layouts
for the benefit of the network operation. The following options should be considered when defining the
layout of a radio network:
• Placing a single repeater, which serves most of the network, on the top of a hill is a straightforward
and very common option. Sometimes it is the only feasible option. However, there are a few things
we must consider with this design. First, a dominant hilltop site is exposed to interference from a
large area; second, these sites are typically crowded with radio equipment of all kinds and it’s a
dynamic radio environment, so local interference may appear anytime; third, it makes the majority
of communication paths dependent on a single site, so one isolated failure may stop almost the
RipEX Radio modem & Router – © RACOM s.r.o.38
Page 39
M
Repeater
Centre
M
Centre
Network planning
entire network. We need to be careful that these hill top systems are well engineered with appropriate
filtering and antenna spacing so that the repeater radios operate under the best possible conditions.
Hot standby repeaters can also improve the repeater integrity. Here is an analogy… It’s hard to
have a quiet conversation when a crowd is shouting all around you. So, make sure you give your
RiPEX repeaters the chance to communicate in a reasonable RF environment. Sometimes a different
layout can significantly reduce the vulnerability of a radio network.
• When total throughput is important, as is typical in report-by-exception networks, splitting the network
into several independent or only slightly overlapping areas of coverage can help. The placement
of repeaters which serve the respective areas is crucial. They should be isolated from each other
whenever possible.
Fig. 3.6: Dominant repeater – straightforward layout
Fig. 3.7: Isolated branches – more robust layout
39© RACOM s.r.o. – RipEX Radio modem & Router
Page 40
Network planning
• in report-by-exception networks the load of hops connecting the centre to major repeaters forms
the bottle-neck of total network capacity. Moving these hops to another channel, or, even better, to
a wire (fibre, microwave) links can multiply the throughput of the network. It saves not only the load
itself, it also significantly reduces the probability of collision. More on that in the following chapter
3.6..
3.6. Hybrid networks
If an extensive area needs to be covered and multiple retranslation would be uneconomical or unsuitable,
RipEX’s can be interconnected via any IP network (WLAN, Internet, 3G, etc.). This is quite simple because RipEX is a standard IP router with an Ethernet interface. Consequently interconnecting two or
more RipEX's over a nested IP network is a standard routing issue and the concrete solution depends
on that network.
3.7. Assorted practical comments
Let us mention few issues, whose influence on network reliability or performance is sometimes neglected
by less experienced planners:
• Both vegetation and construction can grow. Especially when planning a high data rate hop which
requires a near-LOS terrain profile, take into consideration the possible future growth of obstacles.
• When the signal passes a considerable amount of vegetation (e.g. a 100m strip of forest), think of
the season. Typically the path loss imposed by vegetation increases when the foliage gets dense
or wet (late spring, rainy season). Hence the fade margin should be increased if your field measurements are done in a dry autumn month. The attenuation depends on the distance the signal must
penetrate through the forest, and it increases with frequency. According to a CCIR, the attenuation
is of the order of 0.05 dB/m at 200 MHz, 0.1 dB/m at 500 MHz, 0.2 dB/m at 1 GHz. At lower frequencies, the attenuation is somewhat lower for horizontal polarization than for vertical, but the difference
disappears above about 1 GHz.
• Though being a rare problem, moving metallic objects may cause serious disruptions, especially
when they are close to one end of the radio hop. They may be cars on a highway, blades of a wind
turbine, planes taking off from a nearby airport runway etc.
• Even when the signal is very strong, be careful when considering various cheap whips or more
generally any antennas requiring a ground plane to function properly. A tempting scenario is to use
the body of the metallic box, where the radio modem and connected application equipment (often
a computer) is installed, as the ground plane, which leads to never-ending problems with locally
RipEX Radio modem & Router – © RACOM s.r.o.40
Page 41
incorectly
correctly
Powersupply
RTU
Network planning
generated noise. The ground plane forms an integral part of such an antenna, hence it has to be
in a safe distance (several metres) from any electronic equipment as well as the antenna itself. A
metallic plate used as shielding against interference must not form a part of the antenna.
Fig. 3.8: Antenna mounting
• Do not underestimate ageing of coaxial cables, especially at higher frequencies. Designing a 900
MHz site with 30 m long antenna cable run outdoors would certainly result in trouble two years later.
• We recommend to use vertical polarization for all radio modem networks.
3.8. Recommended values
To check individual radio link quality run Ping test with these settings: Ping type - RSS, Length [bytes]
equal to the longest packets in the networks. Use Operating mode Bridge, when Router, ACK set to
Off. Switch off all other traffic on the Radio channel used for testing. The test should run at least hours,
preferably day(s). The values below should guarantee a reliable radio link:
• Fade margin
Min. 20 dB
Fade margin [dB] = RSS (Received Signal Strength) [dBm] – RX sensitivity [dBm].
Respective RX sensitivity for different data rates can be found in Section 4.4.1, “Detailed Radio
parameters”.
41© RACOM s.r.o. – RipEX Radio modem & Router
Page 42
Network planning
• DQ (Data Quality)
Min. 180
• PER (Packet Error Rate)
Max. 5 %
RipEX Radio modem & Router – © RACOM s.r.o.42
Page 43
Product
4. Product
RipEX is built into a rugged die-cast aluminium casing that allows for multiple installation possibilities,
see Section 6.1, “Mounting”.
4.1. Dimensions
Fig. 4.1: RipEX dimensions
43© RACOM s.r.o. – RipEX Radio modem & Router
Page 44
DIN35Rail
DINRailClip
134
150
118
58
50
Product
Fig. 4.2: RipEX dimensions – bottom
Fig. 4.3: RipEX with DIN rail
RipEX Radio modem & Router – © RACOM s.r.o.44
Page 45
Product
Fig. 4.4: RipEX dimensions with connectors
For more information see Section 6.1.1, “DIN rail mounting” and Section 6.1.2, “Flat mounting”
45© RACOM s.r.o. – RipEX Radio modem & Router
Page 46
HW ALARMOUTPUT
HW ALARMINPUT
+ –
SLEEP INPUT
COM1
COM2
ETH
MANAGEMENT
WiFi ADAPTER
ETH/USB ADAPTER
ANTENNA
10–30VDC
+
+
ETH
Product
4.2. Connectors
All connectors are located on the front panel. The upper side features an LED panel. The RESET button
is located in an opening in the bottom side.
Fig. 4.5: Connectors
Warning – hazardous locations
Do not manipulate the RipEX (e.g. plug or unplug connectors) unless powered down or the
area is known to be non-hazardous.
4.2.1. Antenna
An antenna can connect to RipEX via TNC female 50Ω connector.
A model with two antenna connectors can be supplied to order,
in which the Rx and Tx antennas are separate. This model is
typically used on communication towers where one Rx and one
Tx antennas are common for most devices.
See chapter Section 4.5, “Model offerings”.
Note
Frequency split (different Rx and Tx frequency) is independent from the presence of two
antenna connectors. It can be set even on standard RipEX with one antenna connector.
RipEX Radio modem & Router – © RACOM s.r.o.46
Fig. 4.6: Antenna connector TNC
Page 47
Warning – hazardous locations
Antenna has to be installed outside of the hazardous zone.
Product
Fig. 4.7: Separated Rx and Tx antennas
Warning: RipEX radio modem may be damaged when operated without an antenna or a dummy load.
4.2.2. Power and Control
This rugged connector connects to a power supply and it contains control signals. A Plug with screwterminals and retaining screws for power and control connector is supplied with each RipEX. It is Tyco
7 pin terminal block plug, part No. 1776192-7, contact pitch 3.81 mm. The connector is designed for
electric wires with a cross section of 0.5 to 1.5 mm2. Strip the wire leads to 6 mm (1/4 inch). Isolated
cables should receive PKC 108 or less end sleeves before they are inserted in the clip. Insert the cables
in the wire ports, tightening securely.
Tab. 4.1: Pin assignment
signallabeledpin
SLEEP INPUTSI1
HW ALARM INPUTAI2
−(GND) – for SLEEP IN, HW ALARM INPUT−3
+(POWER) – for HW ALARM OUTPUT+4
HW ALARM OUTPUTAO5
+POWER (10 to 30 V)+10–30VDC6
−POWER (GND)−10–30VDC7
Pins 3 and 7, 4 and 6 are connected internally.
47© RACOM s.r.o. – RipEX Radio modem & Router
Page 48
1 2 3 4 5 6PinNo.: 7
SI AI - + A 0
+
-
10–30VDC
Wire
Ports(7)
Retaining
Screws(2)
Lead
Binding
Screws(7)
1 2 3 4 5 6PinNo.: 7
SI AI - + A 0
+
-
10– 30V DC
SleepInput
1 2 3 4 5 6PinNo.: 7
SI AI - + A 0
+
-
10– 30V DC
AlarmInput
1 2 3 4 5 6PinNo.: 7
SI AI - + A 0
+
-
10– 30V DC
AlarmOutput
max.30VDC,1 A
Product
Warning – hazardous locations
The unit must be powered with an intrinsic save power source for use in hazardous locations.
Fig. 4.8: Supply connector
Fig. 4.9: Power and Control - cable plug
SLEEP INPUT
SLEEP INPUT is the digital input for activating the Sleep mode.
When this pin is grounded (for example when connected to pin
3), the RipEX switches into the Sleep mode. Using Power management (Advanced Config.), the Entering the Sleep mode can
be delayed by a set time. Disconnecting SLEEP INPUT from
GND (-) ends the Sleep mode. Note that RipEX takes 48 seconds
to wake up from the Sleep mode.
SLEEP INPUT can be also used for the wake-up from the Save
state. For details see chapter (Advanced Config., Power management)
HW ALARM INPUT
HW ALARM INPUT is a digital input. If grounded (e.g. by connecting to PIN 3), an external alarm is triggered. This alarm can be
used for example to transmit information using SNMP trap, informing for instance about a power outage or RTU problem. For
details about Alarm management see chapter Advanced Config-
uration.
HW ALARM OUTPUT
HW ALARM OUTPUT is a digital output. It can be activated
in Alarm management settings, chapter Advanced Configuration.
It may be used for instance to inform the connected RTU about
a RipEX alarm or about the Unit ready status. If an alarm is
triggered, HW ALARM OUTPUT is internally connected to GND.
RipEX Radio modem & Router – © RACOM s.r.o.48
Page 49
Product
If the external device requires connection to positive terminal of
the power supply, PIN 4 should be used.
POWER
The POWER pins labelled + and - serve to connect a power supply 10–30 VDC. The requirements for
a power supply are defined in Section 6.6, “Power supply” and Section 4.4, “Technical specification”.
4.2.3. ETH
Standard RJ45 connector for Ethernet connection. RipEX has 10/100 BaseT Auto MDI/MDIX interface
so it can connect to 10 Mbps or 100 Mbps Ethernet network. The speed can be selected manually or
recognised automatically by RipEX. RipEX is provided with Auto MDI/MDIX function which allows it to
connect over both standard and cross cables, adapting itself automatically.
Pin assignment
Tab. 4.2: Ethernet to cable connector connections
Crossed cableDirect cableSignalPIN
green – whiteorange – whiteTX+1
greenorangeTX−2
orange – whitegreen – whiteRX+3
blueblue—4
blue – whiteblue – white—5
orangegreenRx−6
brown – whitebrown – white—7
brownbrown—8
Fig. 4.10: RJ-45F
4.2.4. COM1 and COM2
RipEX provides two serial interfaces COM1 and COM2 terminated by DSUB9F connectors. COM1 is
always RS232, COM2 can be configured as RS232 or RS485 (more in Adv. Conf., COM).
RipEX‘s RS232 is a hard-wired DCE (Data Communication Equipment) device. Equipment connected
to the RipEX’s serial ports should be DTE (Data Terminal Equipment) and a straight-through cable
should be used. If a DCE device is connected to the RipEX‘s serial ports, a null modem adapter or
cross cable has to be used.
49© RACOM s.r.o. – RipEX Radio modem & Router
Page 50
1 2 3 4
Product
Tab. 4.3: COM1, 2 pin description
COM2 – RS485COM1, 2 – RS232DSUB9F
In/ OutsignalIn/ Outsignalpin
—OutCD1
In/Outline BOutRxD2
In/Outline AInTxD3
—InDTR4
GNDGND5
—OutDSR6
—InRTS7
—OutCTS8
———9
RipEX keeps pin 6 DSR at the level of 1 by RS232 standard permanently.
Fig. 4.11: Serial connector
4.2.5. USB
RipEX uses USB 1.1, Host A interface. USB interface is wired as standard:
Tab. 4.4: USB pin description
wiresignalUSB pin
red+5 V1
whiteData(−)2
greenData (+)3
blackGND4
The USB interface is designed for the connection to an – external ETH/USB adapter or a Wifi adapter.
They are optional accessories to RipEX, for more details see Section 5.3, “Connecting RipEX to a
programming PC”. The adapters are used for service access to RipEX’s web configuration interface.
The USB interface can also be used for an external flash disc connection, which has been specifically
designed to simplify complex maintenance tasks, so that these tasks can be performed by unqualified
personnel in the field by simple plugging-in an USB stick and waiting until a LED flashes.
The USB connector also provides power supply (5 V/ 0.5 A). It can be used to temporarily power a
connected device, for instance a telephone. The USB connector should not be used as permanent
source of power supply.
Fig. 4.12: Serial connector
Note – hazardous locations
Only USB equipments dedicated for hazardous locations shall remain connected permanently.
External USB flash disc
An external USB flash disc can be used for firmware upgrade, SW keys upload, configuration backup
and restore, ssl certificate and ssh keys upload and tech-support package download. Any common
USB stick with several megabytes of free space can be used for these tasks.
RipEX Radio modem & Router – © RACOM s.r.o.50
Page 51
Product
Note
The flash disc has to contain the FAT32 file system (the most common one at the time of
writing). Any other file system will be simply ignored by the RipEX. When in doubt, consult
your IT expert.
Once the RipEX recognizes a flash disc inserted into the USB interface, the status LED starts blinking
slowly, alternating red and green colors. That indicates the start of the upload/download of files. The
LED flashing may change during the process, the successful completion of the recording is indicated
by fast alternating green and red flashes (about 3 times per second). Note that it may take up to 10
minutes (when an FW upgrade is performed).
Warning
NEVER unplug the USB disc before the proper (fast) flashing of the status LED starts! You
may damage your disc otherwise.
Following a successful detection of a USB flash disc, the RipEX writes the tech-support package, log
files and the configuration text file to it. Then the README.txt file, which contains all the necessary
information on the structure and names of files and directories, is written into the root directory of the
disc. Please follow the detailed instructions in that file, or read it below:
Required FLASH structure:
■ for single radiomodem upgrade:
firmware package(s), newest version is used/ra1-RACOM-<VERSION>.cpio
directory with SW keys/swkey/
SW key(s)*_<SERNO>_*.txt
new configuration in text form/config.txt
new Web certificate (complete or first part)/web.pem
second part of Web certificate (if necessary)/web.key
new CLI key/admin.pub
new remote access key/rmtaccess.key
■ for upgrade of multiple radiomodems:
firmware package, newest version is used/ra1-RACOM-<VERSION>.cpio
directory with SW keys/swkey/
SW key(s)*_<SERNO>_*.txt
directory with new configurations/cnf/
new configuration(s) in text form<SERNO>_*_config.txt
new Web certificate (complete or first part)/web.pem
second part of Web certificate (if necessary)/web.key
new CLI key/admin.pub
new remote access key/rmtaccess.key
51© RACOM s.r.o. – RipEX Radio modem & Router
Page 52
Product
All files/directories are optional, depending on the scope of upgrade. If no files are present, only data
gathering will be performed.
Note
Whenever an FW file (.cpio) is found in the root directory of the disc, the upgrade is executed
automatically, regardless of the version of the currently active FW. If more than one FW file
is found, the latest version is used. Remember to remove the FW files from the disk root
when you do not intend to perform an upgrade. The same principles apply to a configuration
update from the disc.
Created files:
README file/RipEX_README.txt
directory with archived configurations/cnf_archive/
archived configuration(s) in text form<SERNO>_<NAME>_config.txt
directory with log files/logs/
log file(s)log_<SERNO>.txt
directory with technical support packages/tech_support/
technical support package(s)<SERNO>_<NAME>_tsupport.tgz
4.2.6. Reset button
A reset button is situated on the underside of each RipEX unit. The button support multiple functions.
Each function is activated dependant on how long the reset button is depressed. The Physical security
parameter in Settings/Device/Management menu dictates the behavior features available when depressing the button.
Fig. 4.13: Reset button
RipEX Radio modem & Router – © RACOM s.r.o.52
Page 53
Physical security = Off:
When button is depressed
Physical security = On:
When button is depressed
Product
Action if button releasedStatus LED actionTime [seconds]
—Goes dark0 - 5
Device rebootFlashes Green5 - 15
Default access settings, rebootFlashes Green faster15 - 18
Factory Settings, rebootFlashes Red faster30 - 33
Action if button releasedStatus LED actionTime [seconds]
—Goes dark0 - 5
Device rebootFlashes Green5 - 15
Total purge, rebootFlashes Green faster15 - 18
Default access settings:
ETH IP and Mask:
ETH Default GW:
ETH Speed:
DHCP:
ARP proxy & VLAN:
Firewall:
Hot Standby:
Routing table:
Management:
Username:
Password:
Note
To reset the RipEX only use the RESET button as described above or use the button in
RipEX’s web configuration, see Adv. Conf., Maintenance. Never use a power cycling (disconnecting and reconnecting power supply) to reset it. While power cycle resets, or rather
reboots the RipEX, its software will not terminate correctly resulting in logs, statistics and
graphs not being saved properly.
192.168.169.169/24
0.0.0.0
Auto
Off
Off
Off
Off
Deleted
Default (Web server=HTTP+HTTPS, CLI=SSH)
admin
admin
4.2.7. GPS
RipEX can be equipped with an internal GPS, see Section 4.5,
“Model offerings”. The GPS module is used for time synchronisation
of the NTP server inside RipEX. See Adv. Conf., Time for more. In
this case the front panel contains a SMA female 50 ohm connector
for connecting the GPS antenna.
• active or passive antenna
• 3.3 VDC supply
Fig. 4.14: GPS Connector SMA
53© RACOM s.r.o. – RipEX Radio modem & Router
Page 54
Product
4.3. Indication LEDs
Tab. 4.5: Key to LEDs
DescriptionColor
Fig. 4.15: Indication LEDs
STATUS
TX
RX
COM2
COM1
Green
Green flashes slowly
Green flashes quickly
Green
blinks with a period of 1 sec
Green
Yellow
The RipEX OS (Linux) is running
successfully
Reset button has been pressedDark
reset after five-seconds pressing
the Reset button
default access after 15-seconds
pressing the Reset button
EmergencyRed flashes quickly
AlarmRed
GPS module synchronized,
for RipEX-xxxG model only
transmitting to radio channelRed
receiver is synchronised to a
packet
there is a signal stronger than
−80 dBm on Radio channel
data receivingGreen
data transmittingYellow
data receivingGreen
data transmittingYellow
100 Mb/s speedYellow ON
ETH
PWR
Alarm – is “On” when any controlled item in Alarm management, (see Adv. Conf., Alarm man-
agement for more) is in alarm status (out of thresholds) and “SNMP Trap", "HW Alarm
Output" or "Detail graphs start” for any line in the Alarm configuration table are checked.
Emergency – Emergency status is an undefined RipEX status either because of a SW or HW problem
when RipEX does not function properly. Maintenance web page is mostly accessible
even in Emergency status. If the problem cannot be eliminated after a power cycle, send
the unit to RACOM for repair.
RipEX Radio modem & Router – © RACOM s.r.o.54
10 Mb/s speedYellow OFF
connectedGreen ON
Ethernet dataGreen flashes
powered successfullyGreen
Save modeBlinks with a period of 1 sec
Sleep modeFlashes once per 3 sec
Page 55
4.4. Technical specification
Tab. 4.6: Technical parameters
Radio parameters
Product
Frequency bands
Channel spacing
Modulation
Data speed (up to)
Transmitter
RF Output power
(Both Carrier and Modulated)
135–154; 154–174; 215–240; 300–320; 320–340; 340–360;
368–400; 400–432; 432–470; 470–512; 928–960 MHz
6.25 / 12.5 / 25 / 50 kHz
[1]
±1.0 ppmFrequency stability
QAM (linear): 16DEQAM, D8PSK, π/4DQPSK, DPSK
FSK (exponential): 4CPFSK, 2CPFSK
> 200 kbps@50 kHz; >100 kbps@25 kHz; >50 kbps@12.5 kHz;
>25 kbps@6,25 kHz
[2]
On/Off, ¾ Trellis code with Viterbi soft-decoderFEC (Forward Error Correction)
QAM: 0.5 - 1.0 - 2.0 W
FSK: 0.1 - 0.2 - 0.5 - 1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 10 W
[3]
ContinuousDuty cycle
< 1.5 msRx to Tx Time
> 40 dBIntermodulation Attenuation
< −36 dBmSpurious Emissions (Conducted)
< −36 dBmRadiated Spurious Emissions
< −60 dBcAdjacent channel power
< −60 dBcTransient adjacent channel power
Receiver
see detailsSensitivity
50 kHz @ −3 dB BWAnti-aliasing Selectivity
< 1.5 msTx to Rx Time
20 dBm (100 mW)Maximum Receiver Input Power
< −57 dBmRx Spurious Emissions (Conducted)
< −57 dBmRadiated Spurious Emissions
see detailsBlocking or desensitization
> 70 dBSpurious response rejection
[1]
50 kHz channel spacing is HW dependent. Units with older version boards are still in production.
50 kHz channel spacing requirement kindly specify in your order.
6.25 kHz channel spacing is not available for RipEX-928.
[2]
This is gross data speed in above table. User data speed varies and depends heavily
on the data structure, optimization effectivity, protocol on Radio channel, signal budgets
and many other parameters of the network. Practical tests are recommended.
[3]
For output power 10 W it is recommended to use input power above 11 VDC.
RipEX-470, RipEX-928 – max. RF Output power 8 W.
55© RACOM s.r.o. – RipEX Radio modem & Router
Page 56
Product
Electrical
10 to 30 VDC, negative GNDPrimary power
5 W/13.8 V; 4.8 W/24 V; (Radio part < 2 W)Rx
Power consumptionRF power
13.8 V 24V
Tx - Exponential - FSK
(4CPFSK, 2CPFSK)
Tx - Linear - QAM
(16DEQAM, D8PSK,
π/4DQPSK)
Interfaces
COM 1
COM 2
0.5 W
1 W
2 W
13.8 W 13.2 W0.1 W
15.2 W 14.4 W1 W
33.1 W 31.2 W5 W
41.4 W 38.4 W10 W
30.4 W 30 W
0.1 WSleep mode
2 WSave mode
RJ4510/100 Base-T Auto MDI/MDIXEthernet
DB9FRS232
300–115 200 bps
DB9FRS232/RS485 SW configurable
300–115 200 bps
Host AUSB 1.1USB
TNC female50 ΩAntenna
LED panel
Environmental
IP Code (Ingress Protection)
Mechanical
SW
User protocols on COM
Power, ETH, COM1, COM2, Rx, Tx, Status7× tri-color status LEDs
IP40, IP51*
* See Section 6.1.4, “IP51 mounting” for details.
> 900.000 hours (> 100 years)MTBF (Mean Time Between Failure)
−40 to +70 °C (−40 to +158 °F)Operating temperature
5 to 95 % non-condensingOperating humidity
−40 to +85 °C (−40 to +185 °F) / 5 to 95 % non-condensingStorage
Rugged die-cast aluminiumCasing
50 H × 150 W × 118 mm D (1.97× 5.9 × 4.65 in)Dimensions
1.1 kg (2.4 lbs)Weight
DIN rail, L-bracket, Flat-bracket, 19" Rack shelfMounting
Bridge / RouterOperating modes
Modbus, IEC101, DNP3, PR2000, UNI, Comli, DF1, RP570,
Profibus, …
RipEX Radio modem & Router – © RACOM s.r.o.56
Page 57
Protocol on Radio channel
Product
Modbus TCP, IEC104, DNP3 TCP, Comli TCP, Terminal server…User protocols on Ethernet
Modbus RTU / Modbus TCP, DNP3 / DNP3 TCPSerial to IP convertors
YesMulti master applications
YesReport by exception
YesCollision Avoidance Capability
YesRemote to Remote communication
Addressed & acknowledged serial
SCADA protocols
Diagnostic and Management
Watched values (Can be broadcast
to neighbouring units. Received info
displayed in Neighbours table)
Statistics
Graphs)
SNMP
Yes
CRC 32Data integrity control
AES256Encryption
up to 3× higher throughputOptimization
Yes (ping with RSS, Data Quality, Homogeneity)Radio link testing
Device – Ucc, Temp, PWR, VSWR, *HW Alarm Input.
Radio channel – *RSScom, *DQcom, TXLost[%]
User interfaces – ETH[Rx/Tx], COM1[Rx/Tx], COM2[Rx/Tx]
* not broadcast
For Rx/Tx Packets on User interfaces (ETH, COM1, COM2) and
for User data and Radio protocol (Repeats, Lost, ACK etc.) on
Radio channel
For Watched values and StatisticsGraphs
20 periods (configurable, e.g. days)History (Statistics, Neighbours,
SNMPv1, SNMPv2c, SNMPv3
Trap / Inform alarms generation as per settings
Monitoring
Real time/Save to file analysis of all physical interfaces (RADIO,
ETH, COM1, COM2) and some internal interfaces between
software modules (e.g. Terminal servers, Modbus TCP server
etc.)
57© RACOM s.r.o. – RipEX Radio modem & Router
Page 58
Product
Standards
CE, FCC, ATEX
Spectrum (art 3.2)
EMC (electromagnetic compatibility)
(art 3.1.b)
ment
Safety (art 3.1.a)
Explosive atmospheres
Tab. 4.7: Recommended Cables
ETSI EN 300 113-2 V1.5.1
ETSI EN 302 561 V1.3.2
FCC Part 90, FCC Part 101
ETSI EN 301 489-1 V1.9.2
ETSI EN 301 489-5 V1.3.1
IEEE 1613:2009 Class 1Electric power substations environ-
EN 60950-1:2006
EN 60950–1:2006/A11:2009,
EN 60950–1:2006/A12:2011,
EN 60950–1:2006/A1:2010
EN 61373:1999Vibration & shock
IEC 980:1989 (seismic category 1a)Seismic qualification
II 3G Ex ic IIC T4 Gc
EN 60079-0:2012
EN 60079-11:2012
LengthRecommended cables and accessoriesPort
Max. 3 mV03VH-H 2×0,5DC terminals – Power
Max. 3 mV03VH-H 1×0,5SI (Sleep Input)
Max. 3 mV03VH-H 1×0,5AI (Alarm Input)
Max. 3 mV03VH-H 1×0,5AO (Alarm Output)
Max. 3 mLiYCY 4×0,14COM1
Max. 3 mLiYCY 4×0,14COM2
Max. 3 mUSB to 10/100 Ethernet Adapter ADE-X5USB
As neededSTP CAT 5eETH
Note – hazardous locations
The cross sections mentioned in above table are the minimal cross sections used under
hazardous location conditions.
RipEX Radio modem & Router – © RACOM s.r.o.58
Page 59
Product
4.4.1. Detailed Radio parameters
The very first parameter which is often required for consideration is the receiver sensitivity. Anyone
interested in the wireless data transmission probably aware what this parameter means, but we should
regard it simultaneously in its relation to other receiver parameters, especially blocking and desensitization. Today’s wireless communication arena tends to be overcrowded and a modern radio modem,
which is demanded to compete with others in that environment, should have good dynamic range that
is defined by the parameters listed above. Receiver of a radio modem, which is designed purely for
optimum sensitivity, will not be able to give proper performance. However, the main receiver parameters
determining its dynamic range go against each other and a clear trade-off between the sensitivity and
the blocking is therefore an essential assumption. Then, from the viewpoint of a logical comparison,
the consequence of better receiver sensitivity can be easily seen – a lower power level of the blocking
and degradation parameters generally.
Blocking or desensitization values were determined according to the standards EN 302 561 V1.2.1 for
50 kHz channel, EN 300 113-1 V1.7.1 for 25 and 12.5 kHz channels, and ETSI 301 166-1 V1.3.2 for
channel 6.25 kHz.
Tab. 4.8: Unlimited 50 kHz
Unlimited 50 kHz Rx
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-2
ModulationFECkbps
BER 10
BER 10
-3
-6
±10 MHz±5 MHz±1 MHzBER 10
-14-14-16-107-111-1142CPFSK0.7515.62
-14-15-16-106-110-1132CPFSK1.0020.83
-18-18-19-101-105-1084CPFSK0.7531.25
-18-19-19-100-104-1074CPFSK1.0041.67
-9-10-12-105-109-112DPSK0.7531.25
-9-11-12-104-108-111DPSK1.0041.67
-3-4-4-100-104-107π/4-DQPSK0.7562.49
-4-5-5-99-103-106π/4-DQPSK1.0083.33
-8-8-8-94-98-101D8PSK0.7593.75
-8-8-8-93-97-100D8PSK1.00125.00
-5-6-6-91-95-9816DEQAM0.75125.00
-5-6-6-90-94-9716DEQAM1.00166.67
Unlimited 50 kHz Tx
Classification
EmissionModulationkbps
26 dB BandwidthOBW 99% [kHz]
30.622.124K0F1DBN2CPFSK20.83
31.723.924K0F1DDN4CPFSK41.67
51.045.145K0G1DBNDPSK41.67
51.044.845K0G1DDNπ/4-DQPSK83.33
51.345.345K0G1DEND8PSK125
51.044.745K0D1DEN16DEQAM166.67
59© RACOM s.r.o. – RipEX Radio modem & Router
Page 60
Product
Tab. 4.9: CE 50 kHz
ModulationFECkbps
BER 10
CE 50 kHz Rx
-2
BER 10
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-3
-6
±10 MHz±5 MHz±1 MHzBER 10
-14-14-16-107-111-1142CPFSK0.7515.62
-14-15-16-106-110-1132CPFSK1.0020.83
-18-18-19-101-105-1084CPFSK0.7531.25
-18-19-19-100-104-1074CPFSK1.0041.67
-15-15-15-105-109-112DPSK0.7526.04
-15-15-15-104-108-110DPSK1.0034.72
-17-21-21-100-104-107π/4-DQPSK0.7552.08
-17-21-21-99-103-106π/4-DQPSK1.0069.44
-15-21-20-96-99-102D8PSK0.7578.12
-16-21-20-95-98-101D8PSK1.00104.17
Classification
CE 50 kHz Tx
EmissionModulationkbps
-14-17-17-95-98-10116DEQAM0.75104.17
-15-1717-94-97-10016DEQAM1.00138.89
26 dB BandwidthOBW 99% [kHz]
30.622.124K0F1DBN2CPFSK20.83
31.723.924K0F1DDN4CPFSK41.67
45.539.340K0G1DBNDPSK34.72
45.639.240K0G1DDNπ/4-DQPSK69.44
44.839.540K0G1DEND8PSK104.17
45.139.140K0D1DEN16DEQAM138.89
RipEX Radio modem & Router – © RACOM s.r.o.60
Page 61
Tab. 4.10: CE 25 kHz
ModulationFECkbps
BER 10
CE 25 kHz Rx
-2
BER 10
Product
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-3
-6
±10 MHz±5 MHz±1 MHzBER 10
-5-6-8-111-115-1182CPFSK0.757.81
-7-8-10-110-114-1172CPFSK1.0010.42
-7-9-9-107-112-1154CPFSK0.7515.63
-9-11-11-104-110-1134CPFSK1.0020.83
-5-6-6-107-112-114DPSK0.7515.62
-7-8-8-106-111-113DPSK1.0020.83
-3-4-4-106-110-113π/4-DQPSK0.7531.25
-5-6-6-104-108-111π/4-DQPSK1.0041.66
-8-8-8-98-103-106D8PSK0.7546.87
-9.5-10-10-95-101-104D8PSK1.0062.49
Classification
CE 25 kHz Tx
EmissionModulationkbps
-5-6-6-95-101-10416DEQAM0.7562.49
-7-8-8-93-99-10216DEQAM1.0083.32
26 dB BandwidthOBW 99% [kHz]
19.613.813K8F1DBN2CPFSK10.42
18.114.214K2F1DDN4CPFSK20.83
27.123.524K0G1DBNDPSK20.83
27.223.924K0G1DDNπ/4-DQPSK41.67
26.923.524K0G1DEND8PSK62.49
27.323.924K0D1DEN16DEQAM83.32
61© RACOM s.r.o. – RipEX Radio modem & Router
Page 62
Product
Tab. 4.11: CE 12.5 kHz
ModulationFECkbps
BER 10
CE 12.5 kHz Rx
-2
BER 10
-3
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-3-4-6-113-117-1202CPFSK0.753.91
-5-6-8-112-116-1192CPFSK1.005.21
-5-6-6-108-114-1174CPFSK0.757.81
-7-8-8-105-112-1154CPFSK1.0010.42
-3-4-4-110-114-116DPSK0.757.81
-5-6-6-109-113-115DPSK1.0010.42
-2-3-3.5-109-113-115π/4-DQPSK0.7515.62
-3-4-4-106-111-114π/4-DQPSK1.0020.83
-5-6-6-101-106-109D8PSK0.7523.44
-7-8-8-98-104-107D8PSK1.0031.25
Classification
CE 12.5 kHz Tx
EmissionModulationkbps
-2-3-3-99-104-10716DEQAM0.7531.25
-4-5-5-96-102-10516DEQAM1.0041.67
26 dB BandwidthOBW 99% [kHz]
9.66.97K00F1DBN2CPFSK5.21
8.56.87K00F1DDN4CPFSK10.42
13.611.911K9G1DBNDPSK10.42
13.611.811K9G1DDNπ/4-DQPSK20.84
13.411.811K9G1DEND8PSK31.25
13.511.811K9D1DEN16DEQAM41.66
RipEX Radio modem & Router – © RACOM s.r.o.62
Page 63
Tab. 4.12: CE 6.25 kHz
ModulationFECkbps
BER 10
CE 6.25 kHz Rx
-2
BER 10
-3
Product
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
+5.5+1.0-0.5-114-120-1222CPFSK0.751.96
+4.0-1.0-2.5-113-119-1212CPFSK1.002.61
+5.0-0.0-1.5-111-116-1194CPFSK0.753.91
+3.0-1.5-3.5-108-114-1174CPFSK1.005.21
7.01.50.0-113-118-121DPSK0.753.91
5.0-0.5-2.0-112-117-119DPSK1.005.21
6.03.0+1.0-112-115-117π/4-DQPSK0.757.82
4.01.0-0.5-110-113-116π/4-DQPSK1.0010.42
4.01.0-1.0-104-109-111D8PSK0.7511.72
2.0-1.0-3.0-104-109-111D8PSK1.0015.63
Classification
CE 6.25 kHz Tx
EmissionModulationkbps
1.5-2.0-7.5-103-107-11016DEQAM0.7515.63
0.0-3.5-5.5-99-104-10716DEQAM1.0020.83
26 dB BandwidthOBW 99% [kHz]
4.352.953K00F1DBN2CPFSK2.61
3.923.173K00F1DDN4CPFSK5.21
6.715.916K00G1DBNDPSK5.21
6.818.946K00G1DDNπ/4-DQPSK10.42
6.685.936K00G1DEND8PSK15.62
6.745.816K00D1DEN16DEQAM20.83
63© RACOM s.r.o. – RipEX Radio modem & Router
Page 64
Product
Tab. 4.13: FCC 50 kHz
ModulationFECkbps
BER 10
FCC 50 kHz Rx
-2
BER 10
-3
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-15-16-16-108-112-1152CPFSK0.7515.62
-15-16-17-107-111-1132CPFSK1.0020.83
-15-21-21-103-107-1104CPFSK0.7531.25
-16-21-21-102-106-1094CPFSK1.0041.67
-15-15-15-105-109-112DPSK0.7526.04
-15-15-15-104-108-110DPSK1.0034.72
-17-21-21-100-104-107π/4-DQPSK0.7552.08
-17-21-21-99-103-106π/4-DQPSK1.0069.44
-15-21-20-96-99-102D8PSK0.7578.12
-16-21-20-95-98-101D8PSK1.00104.17
Classification
Tab. 4.14: FCC 25 kHz
ModulationFECkbps
EmissionModulationkbps
BER 10
FCC 50 kHz Tx
FCC 25 kHz Rx
-2
BER 10
-3
-14-17-17-95-98-10116DEQAM0.75104.17
-15-1717-94-97-10016DEQAM1.00138.89
26 dB BandwidthOBW 99% [kHz]
37.028.028K0F1D4CPFSK41.67
45.539.340K0G1DDPSK34.72
45.639.240K0G1Dπ/4-DQPSK69.44
44.839.540K0G1DD8PSK104.17
45.139.140K0D1D16DEQAM138.89
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-0-1-3-108-113-1164CPFSK0.7515.63
-1-2-5-105-111-1144CPFSK1.0020.83
-1-2-4-107-111-114π/4-DQPSK0.7526.04
-2-4-6-105-109-112π/4-DQPSK1.0034.72
-5-7-9-99-105-108D8PSK0.7539.06
-7-9-11-96-103-106D8PSK1.0052.08
-8-9-12-96-103-10616DEQAM0.7552.08
-10-12-14-94-101-10416DEQAM1.0069.44
RipEX Radio modem & Router – © RACOM s.r.o.64
Page 65
Classification
Product
FCC 25 kHz Tx
EmissionModulationkbps
Tab. 4.15: FCC 25 kHz RipEX-928, RipEX-215
FCC 25 kHz Rx RipEX-928, RipEX-215
-2
ModulationFECkbps
BER 10
BER 10
26 dB BandwidthOBW 99% [kHz]
23.618.518K6F1D4CPFSK20.83
22.819.719K8G1Dπ/4-DQPSK34.72
22.619.819K8G1DD8PSK52.08
22.619.919K8D1D16DEQAM69.44
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-3
-6
±10 MHz±5 MHz±1 MHzBER 10
-8-8-8-106-112-1154CPFSK0.7515.63
-10-10-10-104-110-1134CPFSK1.0020.83
-9-9-9-108-112-115π/4-DQPSK0.7520.84
-11-11-11-105-110-113π/4-DQPSK1.0027.78
-8-8-8-101-107-110D8PSK0.7531.25
-9-9-9-98-105-108D8PSK1.0041.67
-11-11-11-96-103-10616DEQAM0.7541.67
FCC 25 kHz Tx RipEX-928, RipEX-215
Classification
-13-13-13-94-101-10416DEQAM1.0055.56
EmissionModulationkbps
26 dB BandwidthOBW 99% [kHz]
22.615.916K0F1D4CPFSK20.83
18.215.916K0G1Dπ/4-DQPSK27.78
18.015.916K0G1DD8PSK41.67
18.115.916K0D1D16DEQAM55.56
65© RACOM s.r.o. – RipEX Radio modem & Router
Page 66
Product
Tab. 4.16: FCC 12.5 kHz
ModulationFECkbps
BER 10
FCC 12.5 kHz Rx
-2
BER 10
-3
FCC 12.5 kHz Tx
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-4-5-5-108-114-1174CPFSK0.757.81
-6-7-7-105-112-1154CPFSK1.0010.42
-2-2-2-109-113-115π/4-DQPSK0.7513.02
-3-4-4-106-111-114π/4-DQPSK1.0017.36
-5-6-6-101-106-109D8PSK0.7519.53
-7-8-8-98-104-107D8PSK1.0026.04
-2-3-3-99-104-10716DEQAM0.7526.04
-4-5-5-96-102-10516DEQAM1.0034.72
Classification
Tab. 4.17: FCC 6.25 kHz
ModulationFECkbps
EmissionModulationkbps
BER 10
FCC 6.25 kHz Rx
-2
BER 10
-3
26 dB BandwidthOBW 99% [kHz]
11.38.68K60F1D4CPFSK10.42
11.39.8310K0G1Dπ/4-DQPSK17.36
11.29.8710K0G1DD8PSK26.04
11.39.8810K0G1D16DEQAM34.72
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-2-2-2-112-117-1204CPFSK0.753.91
-3-4-4-109-115-1184CPFSK1.005.21
-2-3-3-113-116-118π/4-DQPSK0.756.51
-4-5-5-111-114-117π/4-DQPSK1.008.68
-2-2-2-105-110-112D8PSK0.759.77
-3-4-4-102-107-110D8PSK1.0013.02
-2-3-3-103-107-11016DEQAM0.7513.02
-4-5-5-100-105-10816DEQAM1.0017.36
RipEX Radio modem & Router – © RACOM s.r.o.66
Page 67
Classification
Product
FCC 6.25 kHz Tx
Tab. 4.18: Narrow 25 kHz
ModulationFECkbps
EmissionModulationkbps
BER 10
Narrow 25 kHz Rx
-2
BER 10
-3
26 dB BandwidthOBW 99% [kHz]
5.013.553K60F1D4CPFSK5.21
5.634.895K00G1Dπ/4-DQPSK8.68
5.564.885K00G1DD8PSK13.02
5.634.875K00G1D16DEQAM17.36
Blocking or
desensitization [dBm]Sensitivity [dBm]Classification
-6
±10 MHz±5 MHz±1 MHzBER 10
-5-6-8-111-115-1182CPFSK0.757.81
-7-8-10-110-114-1172CPFSK1.0010.42
-7-9-9-107-112-1154CPFSK0.7515.63
-9-11-11-104-110-1134CPFSK1.0020.83
-6-7-7-109-114-116DPSK0.7510.41
-7-8-8-108-113-115DPSK1.0013.89
-8-8-8-107-111-113π/4-DQPSK0.7520.84
Narrow 25 kHz Tx
Classification
EmissionModulationkbps
26 dB BandwidthOBW 99% [kHz]
19.613.813K8F1DBN2CPFSK10.42
18.114.214K2F1DDN4CPFSK20.83
18.215.915K9G1DBNDPSK13.89
18.215.915K9G1DDNπ/4-DQPSK27.78
18.015.915K9G1DEND8PSK41.67
18.115.915K9D1DEN16DEQAM55.56
Note
All the Sensitivities above are guaranteed ones, i.e. every single unit has got typically
1.
even better values for 0–4 dB.
-8-8-9-106-110-112π/4-DQPSK1.0027.78
-8-8-9-101-105-108D8PSK0.7531.25
-9-10-10-100-104-107D8PSK1.0041.67
-9-9-11-99-103-10616DEQAM0.7541.67
-9-10-11-95-101-10416DEQAM1.0055.56
2. BER (Bit Error Rate) is calculated from PER (Packet Error Rate) when packet size was
60 Bytes.
67© RACOM s.r.o. – RipEX Radio modem & Router
Page 68
Product
3. All the values above are guaranteed for temperatures from -30 to +60 °C (-22 to +140 °F)
and for all frequency channels.
4. The RipEX spurious response rejection is defined as "better than 70 dB", where 70 dB
is the limit defined by ETSI EN 300 113. We confirm that the real measured values of
this parameter are better than 75 dB.
5. The radio circuits in RipEX were designed to provide protection from the output of the
power amplifier and no oscillation, no damage into infinite VSWR at any phase angle
occurs.
6. OBW 99% (Occupied BandWidth) - the bandwidth containing 99% of the total integrated
power of the transmitted spectrum, centered on the assigned channel frequency.
7. "26 dB Bandwidth" - the bandwidth where, beyond its lower and upper limits, any discrete
spectrum component or the power spectral density is attenuated by at least 26 dB, relative to a given and predetermined zero dB level.
8. Please contact RACOM for current status of official test reports for CE, FCC and other
standards for different models (frequencies) and different channel spacings.
9. "Unlimited 50 kHz" channel mask is slightly wider than the relevant CE or FCC requirements, " Narrow 25 kHz" is slightly narrower than the relevant CE requirement. If necessary contact RACOM for more details.
RipEX Radio modem & Router – © RACOM s.r.o.68
Page 69
Product
4.5. Model offerings
RipEX radio modem has been designed to have minimum possible number of hardware variants. Different HW models are determined by frequency, internal GPS and separate connectors for RX and TX
antennas.
Upgrade of functionality does not result in on-site hardware changes – it is done by activating software
feature keys (see chapter RipEX in detail and Adv. Config., Maintenance).
4.5.1. Ordering code (Part No’s)
Trade name: RipEX
Type (according to bands): RipEX-160, RipEX-200, RipEX-300, RipEX-400, RipEX-900.
Code (according to the tuned frequency and specific HW models): e.g. RipEX-368, RipEX-432DG etc.
XXX – base frequency
Code Tuning freq. range
RipEX-135 135–154 MHz
RipEX-154 154–174 MHz
RipEX-215 215–240 MHz
RipEX-300 300–320 MHz
RipEX-320 320–340 MHz
RipEX-340 340–360 MHz
RipEX-368 368–400 MHz
RipEX-400 400–432 MHz
RipEX-432 432–470 MHz
RipEX-470 470–512 MHz
RipEX-928 928–960 MHz
yyy – HW models
empty – basic model
D – separate connectors for RX and TX antennas (Part No. RipEX-HW-DUAL)
G – internal GPS module (Part No. RipEX-HW-GPS)
S – Up to 50 kHz channel spacing (Part No. RipEX-HW-50kHz). "S" is used, because units with older
version radio boards (lower than 1.1.90.0 or 1.2.50.0.) don't support 50 kHz channel spacing.
P - Ingress Protection level IP51 - see Section 6.1.4, “IP51 mounting” for IP51 mounting details
Code examples:
RipEX-368 = RipEX for frequencies from 368 to 400 MHz
RipEX-400G = RipEX for frequencies from 400 to 432 MHz, with GPS module
RipEX-432DG = RipEX for frequencies from 432 to 470 MHz, with separate Rx and Tx antenna con-
nectors, with GPS module
RipEX-154S = RipEX for frequencies from 154 to 174 MHz, together with standard 6.25, 12.5, 25
kHz also 50 kHz channel spacing supported
SW feature keys
ROUTER – enables Operating mode Router. If not activated, only Bridge mode is available
(Part No. RipEX-SW-ROUTER)
69© RACOM s.r.o. – RipEX Radio modem & Router
Page 70
Product
SPEED – enables the two highest Data rates for 50 and 25 kHz channel spacings
(Part No. RipEX-SW-SPEED)
COM2 – enables the second serial interface configurable as RS232 or RS485
(Part No. RipEX-SW-COM2)
10W – enables RF output power 10 W for CPSK modulations
(Part No. RipEX-SW-10W)
BACKUP
ROUTES
MASTER – enables all functionalities of all possible SW feature keys
Software keys are always tied to a specific RipEX Serial number (S/N). When SW key is ordered later
and not together with RipEX unit, this S/N must be given.
Ex feature key
Ex – authorization for use in hazardous location
Ex key is always tied to a specific RipEX Serial number (S/N). When Ex key is ordered later and not
together with RipEX unit, this S/N must be given. Ex keys are available only for units produced after
1st of January 2014.
Standard RipEX package in paper box contents:
– enables Backup routes
(Part No. RipEX-SW-BACKUP ROUTES)
(Part No. RipEX-SW-MASTER)
II 3G Ex ic IIC T4 Gc
Important
Since SW feature key can be activated anytime within RipEX, it is not a part of the Code.
• RipEX – 1pc
• Removable sticker plate – 1pc
• Power and Control plug connector (counterpart) – 1pc
• DIN set (a pair of DIN rail clips + screws) – 1pc
Accessories
Power supplies
PWS-AC/DC-AD-155A – Power supply with back-up 90–260 VAC/13.8 VDC/150 W
PWS-AC/DC-DR-75-12 – Power supply 85–264 VAC/12 VDC/75 W DIN
PWS-AC/DC-MS2000/12 – Power supply with back-up 230 VAC/13.8 VDC/70 W
PWS-SOLAR-MSU120 – Power supply for solar panel 12 VDC 50–120 W /10.5–14.7 VDC
BAT-12V/5Ah – Battery 12 V, 5.0 Ah (for RipEX_DEMO_CASE)
BAT-12V/7.2Ah – Battery 12 V, 7.2 Ah (for RipEX-HSB)
Holders
RipEX_F_BRACKET – Flat-bracket, for flat mounting
RipEX_L_BRACKET – L-bracket, for vertical mounting
19‘ rack mounting
RipEX_D_RACK_230 – 19" rack shelf double, incl. 2× PS 100–256 VAC / 24 VDC
RipEX Radio modem & Router – © RACOM s.r.o.70
Page 71
Product
RipEX_D_RACK_48 – 19" rack shelf double, incl. 2× PS 48 VDC / 24 VDC
RipEX_S_RACK_MS – 19" rack shelf single, incl. MS2000/12 + AKU 7.2 Ah
RipEX_S_RACK_230 – 19" rack shelf single, incl. PS 100–256 VAC / 24 VDC
RipEX_S_RACK_48 – 19" rack shelf single, incl. PS 48 VDC / 24 VDC
Others
RipEX_X5 – ETH/USB adapter
RipEX_W1 – Wifi adapter
RipEX_DEMO_CASE – Demo case (without radio modems)
RipEX_DUMMYLOAD – Dummy load antenna
RipEX_C_NM_50 – Feedline cable, RG58, 50 cm, TNC Male – N Male
OTH-VHF50HN – Coaxial overvoltage protection 100–512 MHz, N female/N female
RipEX-HS – 19" Hot standby chassis, RipEX units excl., pow.supplies incl. (has got its own ordering
codes, see RipEX-HS User manual)
RipEX-HSB – 19" Battery pack chassis for RipEX-HS, batteries excl.
71© RACOM s.r.o. – RipEX Radio modem & Router
Page 72
Product
4.6. Accessories
1. RipEX Hot Standby
RipEX-HS is redundant hot standby chassis. There are two hot-stand-by standard RipEX units
inside. In case of a detection of failure, automatic switchover between RipEX units sis performed.
RipEX-HS is suitable for Central sites, Repeaters or Important remote sites where no single point
of failure is required.
Fig. 4.16: RipEX-HS
Fig. 4.17: RipEX-HS dimensions
For more information see RipEX-HS datasheet or User manual on www.racom.eu1.
2. ETH/USB adapter
ETH/USB adapter for service access to the
web interface via USB connector. Includes a
built-in DHCP server which provides up to 5
leases. To access the RipEX always use the
fixed IP 10.9.8.7. For details on use see Section 5.3, “Connecting RipEX to a programming
PC”.
OTH-XA-ETH/USB requires FW 1.7.1.0 or
Fig. 4.18: Adapter ETH/USB
higher. The previous model OTH-X5-ETH/USB
is supported in all FW versions.
1
http://www.racom.eu
RipEX Radio modem & Router – © RACOM s.r.o.72
Page 73
3. Wifi adapter
Wifi adapter for service access to the web interface via USB connector. Includes a built-in
DHCP server which provides up to 5 leases.
To access the RipEX always use the fixed IP
10.9.8.7. For details on use see Section 5.3,
“Connecting RipEX to a programming PC”.
Product
4. Demo case
A rugged plastic case for carrying up to three RipEX's and one M!DGE 3G SCADA router. It also
contains all the accessories needed to perform an on-site signal measurement, complete application
bench-test or a functional demonstration of both radiomodems and the 3G router. During a field
test, units can be powered from the backup battery and external antenna can be connected to one
of the RipEX units through „N“ connector on the case.
Fig. 4.20: Demo case
Fig. 4.19: WiFi adapter
Content:
• Brackets and cabling for installation of three RipEXes and one M!DGE (units are not part of
the delivery)
• 1× power supply Mean Well AD-155A (100-240 V AC 50-60 Hz/13.8 V DC)
• 1× Backup battery (12V/5Ah, FASTON.250), e.g. Fiamm 12FGH23
• 1× Power cable (European Schuko CEE 7/7 to IEC 320 C13)
• 1× Ethernet patch cable (3 m, UTP CAT 5E, 2× RJ-45)
• Quick start guide
RipEX accessories:
• 3× Dummy load antennas
• 1× L-bracket, 1x Flat-bracket samples
• 1× ETH/USB adapter
• 1× Wifi adapter
M!DGE accessories:
• Stick antenna (900–2100 MHz, 2.2 dBi, vertical)
Mechanical properties of case
73© RACOM s.r.o. – RipEX Radio modem & Router
Page 74
133
124
60
122
L -bracket
32
100
Product
• Outside dimension: 455 × 365 × 185 mm
• Weight approx. 4 kg (excluding the RipEX and M!DGE units)
5. L-bracket
Installation L bracket for vertical mounting. For
details on use see chapter Mounting and
chapter Dimensions.
Fig. 4.21: L-bracket
Fig. 4.22: RipEX with L-bracket
6. Flat-bracket
Installation bracket for flat mounting. For details
on use see chapter Mounting.
Fig. 4.23: Flat bracket
RipEX Radio modem & Router – © RACOM s.r.o.74
Page 75
95
174
184
Flat-bracket
134
150
118
58
50
70
Fig. 4.24: RipEX with Flat-bracket
95
174
184
8
70
75,4
2×o4,5 4×M3
/
101
Product
Fig. 4.25: Flat-bracket dimensions
7. 19" rack shelf – single
• 1,6U (70 mm) high
• Ready for assembly with one RipEX
• Weight 2.5 kg (without power supply and RipEX)
• Can be assembled with power supply
○ 100 – 256 V AC / 24 V DC
○ 230 V AC / 24 V DC
○ 48 V DC / 24 V DC
○ MS2000/12 + back up battery 7.2 Ah
75© RACOM s.r.o. – RipEX Radio modem & Router
Page 76
Product
Fig. 4.26: 19" Rack shelf
Fig. 4.27: 19" Rack shelf – dimensions
8. 19" rack shelf – double
• 1,6U (70 mm) high
• Ready for assembly with two RipEX’es
• Can be assembled with power supplies
○ 100 – 256 V AC / 24 V DC
○ 230 V AC / 24 V DC
○ 48 V DC / 24 V DC
○ MS2000/12 + back up battery 7.2 Ah
RipEX Radio modem & Router – © RACOM s.r.o.76
Page 77
Fig. 4.28: 19" Rack shelf – double
Product
Fig. 4.29: 19" Rack shelf–double – dimensions
77© RACOM s.r.o. – RipEX Radio modem & Router
Page 78
Product
9. Dummy load antenna
Dummy load antenna for RipEX is
used to test the configuration on a
desk. It is unsuitable for higher
output – use transmitting output of
1.0 W only.
10. Coaxial overvoltage protection
Frequency range 100-512 MHz,
connectors N(female) / N(female).
Fig. 4.30: Dummy load antenna
11. Feedline adapter cable
Feedline cable is 50 cm long and
is made from the RG58 coaxial
cable. There are TNC Male (RipEX
side) and N Male connectors on
the ends. It is intended for use
between RipEX and cabinet panel.
12. Automatic antenna switch
An Automatic antenna switch is
mainly used for migrating legacy
to RipEX networks. It automatically
manages antenna switching: when
one base station transmits, the
other one is disconnected from the
common antenna.
Fig. 4.31: Overvoltage protection
Fig. 4.32: Feedline adapter cable
Fig. 4.33: Automatic antenna switch
RipEX Radio modem & Router – © RACOM s.r.o.78
Page 79
13. Migration serial cable
This is an RS232 crossing cable (null-modem) for connection of legacy base station to RipEX.
There is also ‘Carrier On’ contact available for legacy base station keying (Relay Dry Contact),
managed by CTS envelope from RipEX.
Product
Fig. 4.34: Cable connection Fig. 4.35: Migration serial cable
14. Others
For other accessories (Power supplies, Antennas, Coaxial overvoltage protection etc.) kindly visit
http://www.racom.eu/eng/products/radio-modem-ripex.html#accessories
79© RACOM s.r.o. – RipEX Radio modem & Router
Page 80
Center
RTU
RTU
24VDC
24VDC
24VDC
config.PC
Bench test
5. Bench test
5.1. Connecting the hardware
Before installing a RipEX network in the field, a bench-test should be performed in the lab. The RipEX
Demo case is great for this as it contains everything necessary: 3 RipEX’s, Power supply, dummy load
antennas, etc.
If you use your own installation for lab tests, don’t forget:
• A dummy load or an actual antenna with 50 ohm impedance should be connected to the RipEX
• The minimum RF output must be set to avoid overloading the dummy antenna and to keep the received signal at reasonable level, between -40 and -80 dBm.
• The power supplies must meet the requirements given in the specifications, Table 4.6, “Technical
parameters”. Make sure the power supplies do not generate interference in the radio channel and
that they can handle very fast changes in the load when RipEX switches from reception to transmission and back.
Fig. 5.1: Bench test
5.2. Powering up your RipEX
Switch on your power supply. LED PWR flashes quickly and after 8 seconds it switches to a green
light. After approximately 30 seconds your RipEX will have booted and will be ready; the STATUS LED
shines. You’ll find the description of the individual LED states in Section 4.3, “Indication LEDs”.
5.3. Connecting RipEX to a programming PC
To configure a RipEX you can connect it to your PC in three ways:
RipEX Radio modem & Router – © RACOM s.r.o.80
Page 81
1. Using the external Wifi adapter
https://192.168.169.169
PC192.168.169.250
https://10.9.8.7
PCDHCP
https://10.9.8.7
PCDHCP
2. Using the external ETH/USB adapter
3. Directly over the Ethernet interface
Bench test
Fig. 5.2: Connecting to a PC over ETH and over WiFi or ETH/USB adapter
1. PC connected via Wifi adapter
We recommend using the "W1" - external Wifi adapter (an optional accessory of the RipEX).
Connect your PC or tablet or smart phone to RipEX Wifi AP first. Its default SSID is “RipEX + Unit
name + S/N”. The W1 contains a built-in DHCP server, so if you have a DHCP client in your PC
(as most users do), you don’t need to set anything up. The RipEX’s IP address for access over
the ETH/USB adapter is fixed: 10.9.8.7.
Go to 4 Login to RipEX
2. PC connected via ETH/USB adapter
We recommend using the "X5" - external ETH/USB adapter (an optional accessory of the RipEX).
The ETH/USB contains a built-in DHCP server, so if you have a DHCP client in your PC as most
users, you don’t need to set anything up. The RipEX’s IP address for access over the ETH/USB
adapter is fixed: 10.9.8.7.
Go to 4 Login to RipEX
3. PC connected directly to ETH port
Set a static IP address in PC, example for Windows XP:
81© RACOM s.r.o. – RipEX Radio modem & Router
Page 82
Bench test
Start > Settings > Network Connections > Local Area Connections
Right Click > Properties > General
select Internet Protocol (TCP/IP) > Properties > General
IP address 192.168.169.250 - for RipEX in the default state
Subnet mask 255.255.255.0
Default gateway leave empty
OK (Internet Protocol Properties window)
OK (Local Area Properties window)
Some Operating systems may require you to reboot your PC.
Fig. 5.3: PC address setting
Important
When you change the RipEX ETH address from the default value later on and the new
IP network does not include the default one, you will have to change your PC's static
IP again to be able to continue configuring the RipEX.
4. Login to RipEX
Start a web browser (Mozilla Firefox, Internet Explorer - JavaScript enabled) on your PC and type
the RipEX’s default IP in the address line default IP address in the address line field:
• 10.9.8.7 – when connected via external ETH/USB or Wifi adapter. IP address 10.9.8.7 is fixed
and cannot be changed; it is independent of the IP address of the RipEX’s Ethernet interface.)
• 192.168.169.169 – when connected directly to ETH
Note
https - For security reasons the http protocol with ssl encryption can be used for the
communication between the PC and RipEX. The https protocol requires a security
RipEX Radio modem & Router – © RACOM s.r.o.82
Page 83
certificate. You must install this certificate into your web browser (Mozilla Firefox, Internet
Explorer). The first time you connect to the RipEX, your computer will ask you for authorisation to import the certificate into your computer. The certificate is signed by the
certification authority Racom s.r.o. It meets all security regulations and you need not
be concerned about importing it into your computer. Confirm the import with all warnings
and exceptions that your browser may display during installation.
The login screen appears:
Fig. 5.4: Authentication
The default entries for a new RipEX are:
User name: admin
Password: admin
Click OK.
Bench test
Initial screen should appear then:
Fig. 5.5: Status Menu
83© RACOM s.r.o. – RipEX Radio modem & Router
Page 84
Bench test
Warning: Before you start any configuration, make sure only one unit is powered ON. Otherwise,
a different radio modem could reply to your requests! (All units share the same IP address and
are in Bridge mode when in factory settings.)
5. IP address unknown
If you don’t have the adapter or you have forgotten the password, you can reset the access parameters to defaults, see Section 4.2.6, “Reset button”.
5.4. Basic setup
For the first functionality test we recommend that you use the setup wizard. The wizard will guide you
through basic functionality setup. Simply select Wizard in the web interface and proceed according to
the information on the screen. Repeat for all RipEX’s in the test network.
If you want to test applications which require a more complex setup, see Chapter 7, Advanced Config-
uration. To setup the IP addresses you can use the examples in Section 2.3.3, “Router - Flexible,
Configuration examples” as your models, or the RipEX-App. notes, Address planing1.
5.5. Functional test
To test radio communication between the RipEX’s you can use the Ping test, under Diagnostic/Ping
menu. Setting up and the output of this test are described in chapter Adv. Conf., Tools.
If the radio communication between RipEX’s is functional, you can proceed with a test of communication
between the connected devices.
You can monitor the status of configuration using the diodes on the LED panel, see Section 4.3, “Indication LEDs”.
1
http://www.racom.eu/eng/products/m/ripex/app/routing.html
RipEX Radio modem & Router – © RACOM s.r.o.84
Page 85
Installation
6. Installation
Step-by-step checklist
1. Mount RipEX into cabinet (Section 6.1, “Mounting”).
2. Install antenna (Section 6.2, “Antenna mounting”).
3. Install feed line (Section 6.3, “Antenna feed line”).
4. Ensure proper grounding (Section 6.4, “Grounding”).
5. Run cables and plug-in all connectors except from the SCADA equipment (Section 4.2, “Connectors”).
6. Apply power supply to RipEX
7. Connect configuration PC (Section 5.3, “Connecting RipEX to a programming PC”).
8.
Configure RipEX (Chapter 7, Advanced Configuration).
9. Test radio link quality (Section 5.5, “Functional test”).
10. Check routing by the ping tool (Section 7.6.3, “Ping”) to verify accessibility of all IP addresses with
which the unit will communicate.
11. Connect the SCADA equipment.
12. Test your application.
Note – hazardous locations
Installation in hazardous locations has to be done according to standard
EN 60079-25 Explosive atmospheres Intrinsically safe electrical systems.
6.1. Mounting
6.1.1. DIN rail mounting
The radio modem RipEX is directly mounted using clips to the DIN rail. The mounting can be done
lengthwise (recommended) or widthwise; in both cases with the RipEX lying flat. The choice is made
by mounting the clips, one M4 screw per clip. RipEX is delivered with two clips, two screws and four
threaded holes. Only use the M4×5 mm screws that are supplied. Use of improper screws may result
in damage to the RipEX mainboard!
Fig. 6.1: Flat lengthwise mounting to DIN rail – recommended
85© RACOM s.r.o. – RipEX Radio modem & Router
Page 86
Installation
Fig. 6.2: Flat widthwise mounting to DIN rail
When tightening the screw on the clip, leave a 0,5 mm gap between the clip and the washer.
Fig. 6.3: Clip mounting
For vertical mounting to DIN rail, L-bracket (optional accessory) is used. Only use the M4×5 mm screws
that are supplied. Use of improper screws may result in damage to the RipEX mainboard!
Fig. 6.4: Vertical widthwise mounting to DIN rail
Fig. 6.5: Vertical lengthwise mounting to DIN rail
For more information see Section 4.6, “Accessories” – L-bracket.
RipEX Radio modem & Router – © RACOM s.r.o.86
Page 87
Installation
6.1.2. Flat mounting
For flat mounting directly to the support you must use the Flat bracket (an optional accessory). Only
use the M4×5 mm screws that are supplied. Use of improper screws may result in damage to the RipEX
mainboard!
Fig. 6.6: Flat mounting using Flat bracket
Fig. 6.7: Flat mounting using Flat bracket
For more information see Section 4.6, “Accessories” – Flat-bracket.
87© RACOM s.r.o. – RipEX Radio modem & Router
Page 88
Installation
6.1.3. 19" rack mounting
For installation into the 19" rack you can use the 19" rack shelf – single or 19" rack shelf- double for
one or two RipEXes. 19" rack shelf is an optional accessory delivered with/without a power supply.
Fig. 6.8: Rack shelf
6.1.4. IP51 mounting
To meet IP51 protection requirements, two conditions must be met:
○ RipEX unit must host the "IP51 protection" option which is indicated by the letter "P" in the order
code (e.g. RipEX-400SP).
○ RipEX unit must be physically installed with the connectors facing downward.
6.2. Antenna mounting
The type of antenna best suited for the individual sites of your network depends on the layout of the
network and your requirements for signal level at each site. Proper network planning, including field
signal measurements, should decide antenna types in the whole network. The plan will also determine
what type of mast or pole should be used, where it should be located and where the antenna should
be directed to.
The antenna pole or mast should be chosen with respect to antenna dimensions and weight, to ensure
adequate stability. Follow the antenna manufacturer’s instructions during installation.
The antenna should never be installed close to potential sources of interference, especially electronic
devices like computers or switching power supplies. A typical example of totally wrong placement is
mount a whip antenna directly on top of the box containing all the industrial equipment which is supposed
to communicate via RipEX, including all power supplies.
RipEX Radio modem & Router – © RACOM s.r.o.88
Page 89
Installation
Additional safety recommendations
Only qualified personnel with authorisation to work at heights are entitled to install antennas on masts,
roofs and walls of buildings. Do not install the antenna in the vicinity of electrical lines. The antenna
and brackets should not come into contact with electrical wiring at any time.
The antenna and cables are electrical conductors. During installation electrostatic charges may build
up which may lead to injury. During installation or repair work all open metal parts must be temporarily
grounded.
The antenna and antenna feed line must be grounded at all times.
Do not mount the antenna in windy or rainy conditions or during a storm, or if the area is covered with
snow or ice. Do not touch the antenna, antenna brackets or conductors during a storm.
6.3. Antenna feed line
The antenna feed line should be chosen so that its attenuation does not exceed 3 to 6 dB as a rule of
thumb, see Chapter 3, Network planning. Use 50 Ω impedance cables only.
The shorter the feed line, the better. If RipEX is installed close to antenna, the data cable can be replaced
by an Ethernet cable for other protocols utilising the serial port, see Advanced Configuration, Terminal
server. This arrangement is recommended especially when the feed line would be very long otherwise
(more than 15 meters) or the link is expected to operate with low fading margin.
Always follow the installation recommendations provided by the cable manufacturer (bend radius, etc.).
Use suitable connectors and install them diligently. Poorly attached connectors increase interference
and can cause link instability.
6.4. Grounding
To minimise the odds of the transceiver and the connected equipment receiving any damage, a safety
ground (NEC Class 2 compliant) should be used, which bonds the antenna system, transceiver, power
supply, and connected data equipment to a single-point ground, keeping the ground leads short.
The RipEX radio modem is generally considered adequately grounded if the supplied flat mounting
brackets are used to mount the radio modem to a properly grounded metal surface. If the radio modem
is not mounted to a grounded surface, you should attach a safety ground wire to one of the mounting
brackets or a screw on the radio modem’s casing.
A lightning protector should be used where the antenna cable enters the building. Connect the protector
to the building grounding, if possible. All grounds and cabling must comply with the applicable codes
and regulations.
6.5. Connectors
RipEX uses standard connectors. Use only standard counterparts to these connectors.
You will find the connectors’ pin-outs in chapter Section 4.2, “Connectors”.
89© RACOM s.r.o. – RipEX Radio modem & Router
Page 90
10–30VDC
+
+
+10to+30V
Installation
6.6. Power supply
We do not recommend switching on the RipEX’s power supply before connecting the antenna and
other devices. Connecting the RTU and other devices to RipEX while powered increases the likelihood
of damage due to the discharge of difference in electric potentials.
RipEX may be powered from any well-filtered
10 to 30 VDC power source. The supply must be capable
of providing the required input for the projected RF output.
The power supply must be sufficiently stable so that
voltage doesn’t drop when switching from receiving to
transmission, which takes less than 1.5 ms. To avoid radio
channel interference, the power supply must meet all
relevant EMC standards. Never install a power supply
close to the antenna. Maximal supply cable length is 3 m.
Fig. 6.9: 10–30 VDC Supplying
Warning – hazardous locations
The unit must be powered with an intrinsic save power source for use in hazardous locations.
RipEX Radio modem & Router – © RACOM s.r.o.90
Page 91
Advanced Configuration
7. Advanced Configuration
This chapter is identical with the content of Helps for individual menu.
7.1. Menu header
RipEX can be easily managed from your computer using any web browser (Mozilla Firefox, Microsoft
Internet Explorer, etc.). If there is an IP connection between the computer and the respective RipEX,
you can simply enter the IP address of any RipEX in the network directly in the browser address line
and log in. However it is not recommended to manage an over-the-air connected RipEX in this way,
because high amounts of data would have to be transferred over the Radio channel, resulting in quite
long response times.
When you need to manage an over-the-air connected RipEX, log-in to a RipEX, which your computer
is connected to using either a cable (via LAN) or a high speed WAN (e.g. Internet). The RipEX which
you are logged-in to in this way is called Local. Then you can manage any remote RipEX in the network
over-the-air in a throughput-saving way: all the static data (e.g. Web page graphic objects) is downloaded
from the Local RipEX and only information specific to the remote unit is transferred over the Radio
channel. RipEX connected in this way is called Remote.
When in Router mode, the IP address of either the Radio or Ethernet interface in the remote unit can
be used for such remote management. IP routing between source (IP of ETH interface in Local RipEX)
and destination IP (either Radio or ETH interface in Remote RipEX) has to exist.
When in Bridge mode, IP addresses of Ethernet interfaces are used for both the Local and Remote
units. Be careful, each RipEX MUST have its unique IP address and all these IP addresses have to
be within the same IP network (defined by the IP Mask) when remote management is required in Bridge
mode.
Fig. 7.1: Menu Header
• Values from
The Unit name (Settings/Device/Unit name) of the RipEX from which data is currently displayed
and which is currently managed.
• Remote IP
IP address of the remotely connected RipEX. After filling-in the Connect button shall be pressed.
• Connect
Action button to connect to the remote RipEX, which is specified by the IP address in the Remote
box. The Unit name in "Values from" box is changed accordingly afterwards.
• Disconnect
91© RACOM s.r.o. – RipEX Radio modem & Router
Page 92
Advanced Configuration
When a Remote RipEX is successfully connected, the Disconnect button shows up. When the
Disconnect process is executed, the Local RipEX (IP address in the Local box) can be managed
and the Unit name in the "Values from" box changes accordingly.
• Logout
Use the Logout link in the top right corner of the screen to logout the current user from the Local
unit.
Web browser tab description
Fig. 7.2: Web browser
To facilitate management of multiple RipEX units at the same time, Web Browser tab names change
dynamically.
The tab name contains:
• IP address
• RipEX Ethernet interface IP address or IP address if connected via IP tunnel
• UDP port number if connected via IP tunnel
• ">" mark when Fast remote connection is used (optional)
• /Menu name "Unit name"
RipEX Radio modem & Router – © RACOM s.r.o.92
Page 93
7.2. Status
Advanced Configuration
Fig. 7.3: Menu Status
7.2.1. Device, Radio, ETH&COM
This part of Status page displays basic information about the RipEX (e.g. Serial No., MAC addresses,
HW versions etc.) and overview of its most important settings. Configurable items are underlined and
one click can take you to the respective Settings menu.
7.2.2. Diagnostic
The current state of Watched values is displayed in the Diagnostic part of the Status page. Watched
values are values of parameters, which are continuously monitored by RipEX itself.
On-line help for each individual item is provided by balloon tips (when cursor is placed over an item
name). When an item goes red, it means that the item is monitored for alarm and its value is in the
alarm range (see Settings/Device/Alarm management)
Refresh - complete refresh of displayed values is performed.
93© RACOM s.r.o. – RipEX Radio modem & Router
Page 94
Advanced Configuration
7.3. Settings
Fig. 7.4: Menu Settings
7.3.1. Device
■ Unit name
Default = NoName
Each Unit may have its unique name – an alphanumeric string of up to 32 characters. UTF8 is
supported. Following characters are not allowed:
" (Double quote)
` (Grave accent)
\ (Backslash)
$ (Dollar symbol)
; (Semicolon)
Important
Unit name is solely for the user's convenience, no DNS (Domain Name Server) is used
in the RipEX network.
RipEX Radio modem & Router – © RACOM s.r.o.94
Page 95
Advanced Configuration
■ Operating Mode
List box: Bridge, Router
Default = Bridge
Operating mode defines whether the RipEX unit acts as a simple transparent device (Bridge mode)
or Ethernet router (Router mode).
Bridge
Bridge mode is suitable for Point-to-Multipoint networks, where Master-Slave application with
polling-type communication protocol is used. RipEX in Bridge mode is as easy to use as a simple
transparent device, while allowing a reasonable level of communication reliability and spectrum
efficiency in small to medium size networks.
In Bridge mode, the protocol on the Radio channel does not have collision avoidance capability.
There is CRC check of data integrity, i.e. once a message is delivered, it is 100% error free.
All the messages received from user interfaces (ETH&COM) are immediately transmitted to
Radio channel, without any checking or processing.
ETH: The whole network of RipEX units behaves like a standard Ethernet network bridge, so
the Ethernet interface IP address itself is not significant. Each ETH interface automatically learns
which devices (MAC addresses) lie in the local LAN and which devices are accessible via the
Radio channel. Consequently only the Ethernet frames addressed to remote devices are physically transmitted on the Radio channel. This arrangement saves RF spectrum from extra load
which would otherwise be generated by local traffic in the LAN (the LAN to which the respective
ETH interface is connected).
COM1, COM2: all frames received from COM1(2) are broadcast over Radio channel and
transmitted to all COM ports (COM1 as well as COM2) on all units within the network, the other
COM on the source RipEX excluding.
Router
Router mode is suitable for Multipoint networks. Two different Radio protocols (Flexible and
Base driven) are available to offer best performance dependent on type of application. These
protocols can transmit both unicast and broadcast frames. They have collision avoidance capability, use frame acknowledgement and retransmissions, a CRC check to guarantee data delivery
and integrity, even under harsh interference conditions on the Radio channel.
RipEX works as a standard IP router with 2 independent interfaces: Radio and ETH. Each interface has its own MAC address, IP address and Mask.
IP packets are processed according to the Routing table. There is also a possibility to set a
router Default gateway (applies to both interfaces) in the Routing table.
The COM ports are treated in the same way as router devices, messages can be delivered to
them as UDP datagrams to selected port numbers. Destination IP address of COM port is either
the IP of ETH or the IP of Radio interfaces.
95© RACOM s.r.o. – RipEX Radio modem & Router
Page 96
Advanced Configuration
■ Hot Standby
When RipEX unit is used in RipEX-HS and Hot Standby is "On" there are some limitations with it.
Specifically, CD pin on COM1 and HW alarm Input and Output are used internally and not available
to the user. Neither Save nor Sleep modes can be activated. Please refer RipEX-HS User manual.
All settings below are valid only for RipEX units in RipEX-HS equipment, where two units in Hot
Standby mode are running. Both units MUST have the same settings! Only Unit names should be
different as this parameter is used in SNMP to recognize the sender of SNMP traps. In order to
ensure that the settings of both units are identical, it is recommended to set unit "A", thereafter save
its settings into a file (Maintenance/Configuration/Save to file) and use these settings for unit "B".
(Maintenance/Configuration/Restore/File path/Upload) Finally, a unique Unit name should be assigned
to Unit B.
List box: Off, On
Default = Off
When "On", HW switching from RipEX unit "A" to RipEX unit "B" is performed based on the HW
Alarm Output settings in Settings/Alarm management. RipEX "A" is the primary unit, , Unit "B" is
activated if there is HW alarm on unit "A" or unit "A" power source is down or when Auto Toggle
Period expired. When mentioned events passed, RipEX "A" goes to be active again.
MAC
Both units in RipEX-HS are using the same MAC addresses (MAC cloning). Whichever unit is
active (either "A" or "B"), RipEX Ethernet interface will use this MAC address. This MAC address
has to be unconditionally set to the same value in both units used in RipEX-HS. Otherwise, the
switching between units will not function properly.
Read own – it is possible to download the MAC address of this unit. The value in the second
unit has to be manually set to the same value then
Auto Toggle mode
When Auto Toggle mode is On (HW button on front panel), controller automatically switchesover to RipEX "B", even if "A" doesn't have any alarm and uses "B" for a set time in order to
confirm that RipEX "B" is fully ready-to-operate.
Start Date [YYYY-MM-DD]
RipEX Radio modem & Router – © RACOM s.r.o.96
Page 97
■ Time
Advanced Configuration
Fill in the Date in the required format when Auto Toggle mode starts.
Start Time [HH:MM:SS]
Fill in the Time in the required format when Auto Toggle mode starts on "Start Date" day.
Period [min.]
Minimum value 60 min.
Within this period units "A" and "B" will change their activities over. Unit "A" starts to operate
at "Start Date and Time". When "Period" minus "Unit B" time expires, controller switches to
unit "B".
Unit B [min.]
Minimum value 5 min.
Time when unit "B" will be active within "Period". It has to be shorter than Period by 5 min.
List box: Manual, NTP
Default = Manual
Internal calendar time of RipEX can be set manually or synchronized via NTP (Network Time Protocol).
Manual
RipEX internally uses the Unix epoch time (or Unix time or POSIX time) - the number of seconds
that have elapsed since January 1, 1970. When RipEX calendar time is set, the Unix epoch time
is calculated based on filled in values (Date, Time) and the time zone, which is set in operating
system (computer), where the browser runs.
Current Date&Time
Information about the actual date and time in the RipEX
97© RACOM s.r.o. – RipEX Radio modem & Router
Page 98
Advanced Configuration
Date [YYYY-MM-DD]
Fill in Local Date in required format
Time [HH:MM:SS]
Fill in Local Time in required format
RipEX Time zone
Select RIPEX Time zone from list box.
Default = (GMT +1:00) Central Europe
This time zone is used for conversion of internal Unix epoch time to "human readable
date&time" in RipEX logs.
Daylight saving
List box: On, Off
Default = On
If On, Daylight saving is activated according the respective rules for selected RipEX Time
zone.
NTP
Internal calendar time in RipEX is synchronized via NTP and RipEX also acts as a standard
NTP server simultaneously.
Current Date&Time
Information about the actual date and time in RipEX
Time source
List box: NTP server, Internal GPS
Default = NTP server
NTP server – The source of time is a standard NTP server. This server can be connected
either via the Ethernet interface or over the Radio channel (any RipEX runs automatically
as a NTP server).
Internal GPS – The source of time is the internal GPS. In this case only RipEX Time
zone and Daylight saving parameters below are active.
Source IP
Default = empty
IP address of the NTP server, which provides Time source. Date and Time will be requested
by RipEX from there. More NTP servers can be configured, the more servers, the better time
accuracy. If the Time source is a RipEX over Radio channel, only one source server is recommended, since the Radio channel could be overloaded.
Minimum polling interval
List box: 1min to 2h 17min
RipEX polls the source server in order to synchronize itself in the set period or later.
RipEX Time zone
Select RipEX Time zone from list box.
Default = (GMT +1:00) Central Europe
This time zone is used for conversion of internal Unix epoch time to "human readable
date&time" in RipEX logs..
Daylight saving
List box: On, Off
RipEX Radio modem & Router – © RACOM s.r.o.98
Page 99
Advanced Configuration
Default = On
If On, Daylight saving is activated according the respective rules for selected RipEX Time
zone.
RipEX NTP server
Information about the status of internal NTP server in the RipEX
State
not synced - not synchronized
synced to GPS - synchronized to internal GPS
synced to NTP - synchronized to NTP server
Stratum
1 to 16 (1=the best, 16=the worst, 8=when internal time in RipEX is set manually)
The stratum represents the quality and accuracy of time, which the NTP server provides.
Delay [ms] This is the delay of packet (1/2 round trip time), which RipEX received from the
NTP server while asked for synchronization. This delay is compensated in the RipEX NTP
server.
Jitter [ms]
The Jitter of received times when RipEX asked for time synchronization from NTP server(s).
99© RACOM s.r.o. – RipEX Radio modem & Router
Page 100
Advanced Configuration
■ SNMP
You can read more about SNMP in RipEX (MIB table description incl.) in Application note "RipEX
SNMP Configuration Guide" here: http://www.racom.eu/eng/products/m/ripex/app/snmp.html
List box: Off, v1/v2c/v3, v3 only
Default = Off
When enabled, RipEX works as a standard SNMP agent, i.e. it responds to "SNMP GET Request"
packets received from even several SNMP managers on any of its IP addresses. It transmits SNMP
Traps or SNMP Informs as per its configuration (Settings/Device/Alarm management or Routing/Backup).
The "v3 only" option can be enabled if the higher security is required.
SNMP v1/v2c
Community name
Default = public
This string is used for authentication with SNMP manager. Max. length is 32 chars. Following
characters are not allowed:
" (Double quote)
` (Grave accent)
\ (Backslash)
$ (Dollar symbol)
; (Semicolon)
RipEX Radio modem & Router – © RACOM s.r.o.100
Loading...