Page 4
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.
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.
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.
Page 9
Calculate and estimate the network throughput and response times when loaded by your application. Perform a bench-test with 3-5 sets of RipEX's and SCADA equipment (Chapter 5, Bench test). Design the addressing and routing scheme of the network (Chapter 2, RipEX in detail and RipEX App notes, Address planing Preconfigure all RipEX's (Section 5.4, “Basic setup”).
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.
Page 11
• 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.
Page 12
- 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 built- in GPS...
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: ○...
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.
Page 15
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).
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 communic- ation. 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.
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.
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.
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.
Page 22
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.
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.
Step 3 RTU1 processes the request and 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.
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.
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)
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.
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).
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.
• 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.
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.
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.
“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”...
Page 39
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.
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 be- cause 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.
ETH/USB ADAPTER 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.
This rugged connector connects to a power supply and it contains control signals. A Plug with screw- terminals 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 mm...
Page 48
30 V DC, 1 A 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 SI AI - + A0 + triggered, HW ALARM OUTPUT is internally connected to GND.
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.
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.
Page 51
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).
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 de- pressing the button.
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 (dis- connecting 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.
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.
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. 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.
Page 68
All the values above are guaranteed for temperatures from -30 to +60 °C (-22 to +140 °F) and for all frequency channels. 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.
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.
Page 70
II 3G Ex ic IIC T4 Gc 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.
Page 71
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 –...
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.
Page 73
Fig. 4.19: WiFi adapter 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“...
Page 74
Product • Outside dimension: 455 × 365 × 185 mm • Weight approx. 4 kg (excluding the RipEX and M!DGE units) L-bracket Installation L bracket for vertical mounting. For details on use see chapter Mounting and chapter Dimensions. Fig. 4.21: L-bracket L - bracket Fig.
Page 79
Product 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.
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.
Page 81
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.
Page 82
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.
Page 83
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 au- thorisation to import the certificate into your computer. The certificate is signed by the certification authority Racom s.r.o.
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.
(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.
Page 86
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.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.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.
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.
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.
(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.
Page 92
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.
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.
Page 95
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.
Page 96
When Auto Toggle mode is On (HW button on front panel), controller automatically switches- over 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.
Page 97
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.
Page 98
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.
Page 99
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.
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"...
Page 103
"forward"). When this happens, you have to use the Reset button on the bottom side of the misconfigured RipEX (keep it pressed for 15 sec.) in order to set Default access. It restores the default Ethernet IP, default password, sets the L3 Firewall to Off, sets ARP proxy&VLAN settings to Off and Ethernet speed to Auto.
Page 104
L3 Firewall settings do not impact packets received and redirected from/to Radio channel. The problem described in NOTE 2 will not happen when the affected RipEX router is a radio repeater, i.e. when it uses solely the radio channel for both the input and output.
Page 106
When "On", the Hardware Alarm Output indicates the full functionality of the RipEX. The Hardware Alarm Output is down only when the RipEX is not powered or it is booting. When SNMP Trap and/or Detail Graphs are ticked in the Unit ready line, the respective action is taken after every Hardware Alarm Output state change (and also when the Apply button is activated after a recon- figuration).
Page 107
RipEX is always on, no special power saving modes are active. Save Mode When a RipEX is switched to the SAVE mode, it can be in one of two states – the SAVE state or the ACTIVE state. In the SAVE state, the RipEX functionality is limited to listening to the Radio channel in order to minimize the power consumption (approx.
Page 108
NOTE: HW wake-up With any fw version higher than or equal to 1.2.1.0 you can take a RipEX in Save state, cycle the power and during the boot-up (approx. 48 sec.) the LED Status starts to flash quickly in green for approx. 10 sec. When Reset button is pressed for approx. 1 sec.
Page 109
List box: Off, On Default = On When "On", RipEX management can be executed over WiFi using the W1 - WIFI/USB adapter from RipEX accessories. This equipment must be plugged into RipEX USB interface. You just switch on WiFi in your device (notebook, tablet, smartphone…) and connect it to the RipEX WiFi network.
Page 111
The Neighbours table displays Watched values from RipEX and from all its neighbours. (Neighbour = RipEX, which can be accessed directly over the radio channel, i.e. without a repeater). There is statistic information about the traffic volume in the Statistic table.
Page 112
Logged Neighbours' IPs Default = 0.0.0.0 Up to 5 IP addresses of neighbouring units can be set. (Neighbour = RipEX, which can be ac- cessed directly over the radio channel, i.e. without a repeater). Watched values from these units are stored in the graph files and can be displayed afterwards.
Page 114
Command Line Interface is accessible via the SSH protocol. If "Off", CLI is inaccessible. The SSH keys are unique for each individual RipEX Serial number. The public key is downloaded in RipEX, for the private key kindly contact RACOM and provide the RipEX S/N.
Advanced Configuration 7.3.2. Radio There are 2 different Operation modes in RipEX: Bridge and Router with 3 different protocols on Radio channel: Transparent used in Bridge mode, Flexible and Base driven used in Router mode. Radio channel protocols configuration differs for each of the protocols: ■...
Page 117
** These items have to be set in accordance with the license issued by the respective radio regulatory authority Mode** RipEX allows multiple settings of modulation parameters for every channel spacing to enable different regulations which apply in different countries to be met. Naturally different limits on transmitted signal parameters result in different Modulation rates.
Page 118
Each frame transmitted on Radio channel from this RipEX has to be acknowledged by the receiving RipEX, using the very short service packet (ACK), in order to indicate that it has received the packet successfully. If ACK is not received, RipEX will retransmit the packet according to its setting of Retries.
Page 119
Maintenance/Miscel- laneous/BRC Radio MAC button. ARP reply packet refreshes the respective records in neighbouring units. This is ne- cessary e.g. when a RipEX unit has been replaced by a spare one with the same Radio IP address. Radio protocol List box: Transparent, Flexible, Base driven Possible values in list box are dependent on the Operating mode setting.
Page 120
Repeater List box: Off, On Default = Off Each RipEX may work simultaneously as a Repeater (Relay) in addition to the standard Bridge operation mode. If "On", every frame received from Radio channel is transmitted to the respective user interface (ETH,COM1,2) and to the Radio channel again.
Page 121
After transmitting to or receiving from the Radio channel, further transmission (from this RipEX) is blocked for a period calculated to prevent collision with a frame transmitted by a Repeater. Furthermore, a copy of every frame transmitted to or received from the Radio channel is stored (for a period).
Page 122
Frame acknowledgement, retransmissions and CRC check, guarantee data delivery and integrity even under harsh interference conditions on the Radio channel NOTE: The Flexible protocol was the only Radio protocol used in the RipEX with Router mode for fw ver. lower than 1.6.x.x (1.5.7.0).
Page 123
Advanced Configuration Default = 120 RSS (Received Signal Strength) limit for access to Radio channel. RipEX does not start transmitting when a frame is being received and the RSS is better than the set limit or when the destination MAC address of the frame is its own.
Page 132
Advanced Configuration NOTE: Max. RF power for RipEX-470 is 8 W. (Even if there was 10W in list box for fw ver. 1.3.x.x and older) ■ Optimization* List box: On, Off Default = Off Optimization is applicable in Router mode for packets directed to Radio channel. It watches packets on individual radio links and optimizes both the traffic to the counterpart of a link and the sharing of the Radio channel capacity among the links.
Page 133
When a packet to be transmitted from the Radio interface is longer than the MTU (Maximum Transmission Unit) set, the RipEX router performs standard IP fragmentation. A packet longer than the configured size is split into the needed number of fragments, which are then independently transmitted - the first packet(s) is (are) transmitted fragment-size long, the last packet contains the remaining bytes.
Mask, Gateway) in connected DHCP clients. They have to be connected to the same LAN as the ETH interface of RipEX. The Mask set is the same as on RipEX ETH, the Gateway is the IP address of ETH interface of RipEX. Typical DHCP client is e.g. a PC used for configuration of RipEX.
Page 135
ETH interface. If "On", specified volume of Data [Bytes] in specified Period [s] is allowed to enter the RipEX from ETH interface. The first packet which exceeds the limit is stored in the buffer and transmitted when new Period starts.
Page 136
TCP port used for Modbus TCP in RipEX. TCP Inactivity [s] Default = 120 TCP socket in RipEX is kept active after the receipt of data for the set number of seconds. Broadcast** List box: On, Off Default = Off Some Master SCADA units send broadcast messages to all Slave units.
Page 137
COM2 or Terminal servers 1-5 (TS1-TS5) or Modbus TCP (MBTCP) can be used or UDP port can be set manually. If the destination IP address belongs to a RipEX and the UDP port is not assigned to COM1(2) or to a Terminal server or to any special daemon running in the destination RipEX, the packet is discarded.
Page 138
■ Terminal servers* Generally a Terminal Server (also referred to as a Serial Server) enables connection of devices with serial interface to a RipEX over the local area network (LAN). It is a virtual substitute for devices used as serial-to-TCP(UDP) converters.
Page 139
TCP Inactivity [s] Default = 120 Timeout in sec for which the TCP socket in RipEX is kept active after the last data reception or transmission. IP address or interval of IP addresses (e.g.: 192.168.20.20 – 192.168.20.26) for which the TCP/UDP conversion is done.
Page 140
(i.e. the default gateway cannot be configured), the narrowest possible subnet should be con- figured on the respective Eth interface of the RipEX connected to it and the ARP proxy switched on. The RipEX then answers ARP requests for all IP addresses routed to its radio interface.
Page 141
When ticked, the respective interface generates ARP responses for all IP addresses which are routed to the Radio interface according to the Routing table (in this specific RipEX unit). Be very careful when using this feature, ARP proxy can disable all traffic in the LAN !
Page 142
Advanced Configuration NOTE 1: When two RipEX units are connected via their Ethernet ports in the same LAN, their IP networks defined on Radio interface must not overlap (both units would reply to the same ARP request). NOTE 2: It is highly recommended to activate ARP proxy as the last change when all the other settings are done.
* Active only when Router mode The COM ports in RipEX are served by special daemons, which are connected to the IP network through a standard Linux socket. Consequently a COM port can be accessed using any of the two IP addresses (either ETH or Radio interface) used in a RipEX and the respective UDP port number.
RTS/CTS (Request To Send / Clear To Send) hardware flow control (handshake) between the DTE (Data Terminal Equipment) and RipEX (DCE - Data Communications Equipment) can be enabled in order to pause and resume the transmission of data. If RX buffer of RipEX is full, the CTS goes down.
Page 146
Router mode), however they are not acknowledged on Ethernet. When the 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. It can be delivered to COM1(2) port daemon, where the datagram is decapsulated and the data received on the serial interface of the source unit are forwarded to COM1(2).
Page 147
Some Master SCADA units sends broadcast messages to all Slave units. SCADA application typically uses a specific address for such messages. RipEX (Protocol utility) converts such message to a customized IP broadcast and broadcasts it to all RipEX units resp. to all SCADA units within the network.
Page 148
COM2 or Terminal servers 1-5 (TS1-TS5) or Modbus TCP (MBTCP) can be used or UDP port can be set manually. If the destination IP address belongs to a RipEX and the UDP port is not assigned to COM1(2) or to a Terminal server or to any special daemon running in the destination RipEX, the packet is discarded.
Page 149
C24 is a serial polling-type communication protocol used in Master-Slave applications. When a RipEX radio network runs in the Router mode, multiple C24 Masters can be used within one Radio network and one Slave can be polled by more than one Master.
Page 150
Cactus is a serial polling-type communication protocol used in Master-Slave applications. When a RipEX radio network runs in the Router mode, multiple Cactus Masters can be used within one Radio network and one Slave can be polled by more than one Master.
Page 151
Each frame in the DNP3 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in terms of the RipEX configuration. The DNP3 allows both Master-Slave polling as well as spontaneous communication from remote units.
Page 152
IEC 870-5-101 is a serial polling-type communication protocol used by Master-Slave application. When RipEX radio network run in Router mode, more IEC 870-5-101 Masters can be used within one Radio network and one Slave can be polled by more Masters.
Page 153
First Slave Address Default = 1 Slave addresses are not defined in the ITT Flygt protocol. However Slave addresses have to be defined in the RipEX network. This is the First Slave address in decimal format. Number of Slaves Default = 1 Since the ITT Flygt protocol Master (centre) polls the Slaves (remotes) one by one without any addressing, number of slaves has to be defined.
Page 154
RDS protocol is a protocol used in MRxx networks. It supports network communication; any node in the network can talk to any other (unlike Master-Slave type of protocols). The RDS protocol should only be used when combining RipEX and MRxx networks or SCADA networks adapted to MRxx networks.
Page 155
RP570 is a serial polling-type communication protocol used in Master-Slave applications. When a RipEX radio network runs in the Router mode, multiple RP570 Masters can be used within one Radio network and one Slave can be polled by more than one Master.
Page 156
○ RB Response timeout [ms] Default = 500 (maximum=8190) The RipEX expects a response to the RB packet within the set timeout. If it is not received, the RipEX does not respond to RB packets from the Master received over the Radio channel.
Page 157
"SCADA address" as in UNI protocol. There is a handshake STX(0x02) – DLE(Ox10) on the start of communication and DLE+ETX – DLE on the end. This handshake is performed by RipEX locally, it is not transferred over the RipEX network.
Page 158
Peer IP and Peer IP mask defines Subnet, which is routed into SLIP on respective COM. NOTE: Peer IP and Peer IP mask defines IP subnet which is automatically routed to respective COM. This subnet can not overlap with any other subnet in RipEX defined on Radio, ETH or VLAN. http://dictionary.reference.com/browse/Internet%20Protocol http://dictionary.reference.com/browse/Ethernet...
Page 159
Advanced Configuration ■ UNI UNI is the 'Universal' protocol utility designed by RACOM. It is supposed to be used when the ap- plication protocol is not in the RipEX list and the addressed mode of communication is preferable in the network (which is a typical scenario). The key condition is that messages generated by the...
Page 160
This feature is used to enable smooth mi- gration from a legacy to the new RipEX based networks. See Migration solution The "Flow control" parameter must be disabled to enable the "CTS Envelope" to function.
Routing table is active only when Router mode (Settings/Device/Operating mode) is set. In such a case 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 then processed according the Routing table.
7.4.3. Backup RipEX is capable to test path between two RipEX IP addresses (even behind a repeater or LAN). When the connection fails, RipEX automatically uses alternative gateway(s) defined in the Alternative paths column with the priority according to the line sequence. The system always tries to use the route with the highest priority, e.g.
Page 163
; (Semicolon) ■ Peer IP IP address of the RipEX (either its Radio or Ethernet interface) on the remote end of the Backup path (Hello packet is sent there). Only RipEX IP of Radio or the main Ethernet interface can be used, no Subnets.
Page 164
NOTE 2: When Optimization (Settings/Radio/Optimization) is "On", UDP packets with both source and destination port 8886 are not transferred over the network, they are discarded in the end RipEX. UDP packets with source port 8903 are not optimized, even if Optimization is "On".
Internet Layer of the Internet Protocol Suite. There are 2 modes of operation: Transport and Tunnel; RipEX only offers Tunnel mode. In Tunnel mode, the entire IP packet is encrypted and authenticated. It is then encapsulated into a new IP packet (ESP - Encapsulating Security Payloads) with a new IP header.
Page 166
IPsec also functions in HotStandby mode. When in passive mode, IPsec is turned off. IPsec is started on transition to active mode. New SA (security associations) are opened. On the peer side: the new SA replaces the SA belonging to the RipEX which has transitioned to passive mode.
Page 170
The PFS (Perfect Forward Secrecy) feature is performed using the Diffie-Hellman group method. PFS increases IKE SA key exchange security. The RipEX unit load is seriously affected when key exchange is in process. The "legacy" marked methods are recognized as unsafe. Peer configuration must match.
From the point of view of the transferred traffic, the GRE tunnel is one hop There are 2 modes of GRE operation: TUN (Tunnel mode) or TAP (L2 transparent connection) with SW bridge. RipEX implementation covers only the TUN mode Packets passing the GRE tunnel are not protected against loss and are not encrypted.
Page 174
Configuration settings for the other side of the GRE tunnel must take this into consideration. The RipEX Radio IP will only be selected as a source if the backup route contains a routing rule for the address range of the Radio network (in the "Routes" table).
Page 177
There is a possibility to display history logs using standard buttons. They are placed on the left side of the button bar. The Refresh button displays the latest log values. Top bar • Date Information about the actual date and time in the RipEX. It can be set in Settings/Device/Time menu. • Log start Date and time when the log has been cleared and started.
Page 178
MAC addresses of Radio interface are used for link layer communication on Radio channel. When RipEX knows the IP address corresponding with the MAC address (the IP has been the destination IP of a packet transferred), IP address is displayed. If the IP address is not known, the MAC address is displayed.
IP addresses of RipEXes who transport them. ETH Protocol packets for TCP proxy are counted on "TCP socket", i.e. between RipEX Ethernet and Host device. Rx from Host device to RipEX, Tx from RipEX to Host. 7.6.2. Graphs Graphs functions as well as meanings of Overview, Detail, Sampling period are described in the help Settings/Device.
Page 181
Available files List box: possible values Default = the newest file There is a list of files, which are saved in RipEX and which can be displayed. Date and time corres- ponds with the start of the file. • 1st IP...
(round trip time - the time from transmission to reception) and records any packet loss. The source IP address of Ping in RipEX is always the IP address of Ethernet interface (Settings/ETH/IP). While using Ping, be sure that correct routing between source and destination IP addresses exists.
Page 183
The length of user data, the range from 8 to 4096 Byte. Some overhead to this Length is always added like these: ICMP - 28 bytes RSS - 43 bytes for IP+UDP+RACOM header + 8 bytes (Trace-RSS and DQ) per each radio hop + 4 bytes (marking in server) RSS ping can not be longer than 3/4 MTU.
Page 186
There is RSS (Received Signal Strength) and DQ (Data Quality) information from the radio hop with lowest RSS, separately for both directions (To and From the destination RipEX). DQ value is optimally 200 - 255, more in Network planning.
COM2), some internal interfaces between software modules 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. Please find Internal interfaces explanation later in this description.
Page 188
RADIO or Terminal Server) and vice versa. When an external interface (e.g. COM:phy) is monitored, the Tx also means packets being transmitted from the RipEX over the respective interface (Rx means "received"). Understanding the directions over the internal interfaces may not be that straightforward, please consult the diagram below for clarification.
Page 190
Advanced Configuration • Off – only frames which are normally received by this unit, i.e. frames whose Radio IP des- tination equals to Radio IP address of this RipEX unit and broadcast frames are processed further by monitoring filters. •...
Page 191
The File Status button refreshes the status of the file which is stored in RipEX and of the recording process. It is recommended to use this button whenever you can not be sure whether your browser is synchronized with the server in the RipEX.
Master key. There are two ways to input the SW key into RipEX: Fill in the key you have received from RACOM or your distributor in the Key box using copy/paste or the SW key can be uploaded from a file. Fill in the SW Key file, or browse your disk in order to find the file.
Folder /home/… in Linux When you need to reset the device access parameters (the login, password, Ethernet IP etc.) to defaults, press the RESET button on the bottom-side of RipEX enclosure for 15 sec. See the User manual for details.
Page 201
When more than one fw files is on the flash disk, the most recent version is uploaded. The most recent version on the flash disk can not be older than in the RipEX; downgrade from flash is not supported. Upload from the flash is equivalent to Maintenance/Firmware/Upload to Archive plus Maintenance/Firm- ware/Versions=All plus Maintenance/Firmware/Archive to Active.
BRC Radio MAC – when pressed, an ARP reply packet is broadcasted over the Radio channel. When e.g. a RipEX unit has been replaced by a spare one with the same Radio IP, but different Radio MAC address, the neighbouring RipEXes update their ARP tables only after their respective timeout expires.
It is possible to use own security keys for this communication. NOTE: It is not possible to use the Fast remote access between two RipEX units with different Remote access keys. When you want to change the Remote access key in a network, start from the most remote unit.
During this time period RipEX transmits after Start button is executed. 7.7.9. Technical support package Technical support package is the file where some internal events are recorded. It can be used by RACOM technical support when a deeper diagnostic is required. The most recent part of it can be downloaded to the local PC.
CLI “login” and “password” are the same as those for web access via browser. Access using ssh keys is also possible. Keys are unique for each individual RipEX Serial number. The public key is downloaded in RipEX, for the private key kindly contact RACOM and provide RipEX S/N.
Page 206
COM break length: 1000 chars COM protocol: Modbus (mod) The CLI is a powerful tool for advanced management of RipEX, especially suited for automated tasks. It is best learned through its own help system, hence it is not described in further detail here.
• Alternatively, you can reset your RipEX to default access by pressing the Reset button for a long time, see Section 4.2.6, “Reset button” . Afterwards, you can use the IP 192.168.169.169/24 to connect to the RipEX. Note that, in addition to resetting access parameters to defaults, your firewall rules will be cleared as well.
Page 209
-d * Then you can ping the newly connected RipEX again. I have assigned the RipEX a new IP address and my PC lost connection to it. • Change the PC’s IP address so that it is on the same subnet as the RipEX.
Minimum Safety Distance tables below, calculated for different antennas and RipEX power levels. The distances were calculated according to EN 50 385 and EN 50 383 and apply to the far-field region only. Whenever the result is comparable or smaller than the actual size of the respective antenna, the field intensity is even smaller than the far-field based calculation and the safety limit is never exceeded.
10.3. High temperature If the RipEX is operated in an environment where the ambient temperature exceeds 55 °C, the RipEX must be installed within a restricted access location to prevent human contact with the enclosure heatsink. 10.4. RoHS and WEEE compliance...
• The antenna has to be installed outside the hazardous zone. • Do not manipulate the RipEX (e.g. plug or unplug connectors) unless powered down or the area is known to be non-hazardous. • Only USB equipment dedicated for hazardous locations shall remain connected permanently.
Only undermentioned manufacturer is entitled to repair any devices. 10.7. Important Notifications Sole owner of all rights to this operating manual is the company RACOM s. r. o. (further in this manual referred to under the abbreviated name RACOM). All rights reserved. Drawing written, printed or repro- duced copies of this manual or records on various media or translation of any part of this manual to foreign languages (without written consent of the rights owner) is prohibited.
Page 217
Everyone can copy and spread word-for-word copies of this license, but any change is not permitted. The program (binary version) is available for free on the contacts listed on http://www.racom.eu. This product contains open source or another software originating from third parties subject to GNU General Public License (GPL), GNU Library / Lesser General Public License (LGPL) and / or further author li- cences, declarations of responsibility exclusion and notifications.
С настоящото RACOM s.r.o. декларира, че този тип радиосъоръжение RipEX-160, RipEX-300, RipEX-400 е в съответствие с Директива 2014/53/ЕС. Por la presente, RACOM s.r.o. declara que el tipo de equipo radioeléctrico RipEX-160, RipEX-300, RipEX-400 es conforme con la Directiva 2014/53/UE. Tímto RACOM s.r.o. prohlašuje, že typ rádiového zařízení RipEX-160, RipEX-300, RipEX-400 je v souladu se směrnicí...
Page 220
RACOM s.r.o. niniejszym oświadcza, że typ urządzenia radiowego RipEX-160, RipEX-300, RipEX-400 jest zgodny z dyrektywą 2014/53/UE. O(a) abaixo assinado(a) RACOM s.r.o. declara que o presente tipo de equipamento de rádio RipEX- 160, RipEX-300, RipEX-400 está em conformidade com a Diretiva 2014/53/UE.
Nove Mesto na Morave, 25 of April 2015 Jiri Hruska, CEO RACOM s.r.o. • Mirova 1283 • 592 31 Nove Mesto na Morave • Czech Republic www.racom.eu Tel.: +420 565 659 511 • Fax: +420 565 659 512 • E-mail: racom@racom.eu ver.
The serviced equipment shall be returned by RACOM to the customer by prepaid freight. If circumstances do not permit the equipment to be returned to RACOM, then the customer is liable and agrees to reim- burse RACOM for expenses incurred by RACOM during servicing the equipment on site. When equipment does not qualify for servicing under warranty, RACOM shall charge the customer and be reimbursed for costs incurred for parts and labour at prevailing rates.
OID mappings Appendix A. OID mappings RipEX internal SNMP server messages (answers) contain OID according to RFC1157. "MIB tables", and whole file "OID mappings" can be downloaded from: http://www.racom.eu/eng/products/radio-modem-ripex.html#download More details are described in Application note: See RipEX App notes, SNMP http://www.racom.eu/eng/products/m/ripex/app/snmp.html...
Revision 1.1 2011-08-31 First issue Revision 1.2 2011-12-31 PoE is not supported in RipEX from 1.1.2012, so all information about PoE has been removed. Revision 1.3 2011-01-26 Added information about Monitoring Upgraded information about Terminal servers (IP port dynamical changes support) New serial SCADA protocols - RP570, C24 Melsec, ITT Flygt, Cactus Revision 1.4...
Page 234
Base driven radio protocol Individual link option in Flexible radio protocol New serial SCADA protocol – PR2000 Migration solution Upgraded chapters: RipEX – Radio router, RipEX in detail, Network planning, Accessories, Advanced Configuration Revision 1.15 2016-12-12 Update of the firmware upgrade via USB Revision 1.16...
Need help?
Do you have a question about the RipEX and is the answer not in the manual?
Questions and answers