User manual . RipEX Radio modem & Router . version 1.4 10/26/2012 fw 1.2.x.x RACOM s.r.o. • Mirova 1283 • 592 31 Nove Mesto na Morave • Czech Republic Tel.: +420 565 659 511 • Fax: +420 565 659 512 • E-mail: racom@racom.eu www.racom.
Table of Contents Getting started ..................................................................................................................................... 7 1. RipEX – Radio router ...................................................................................................................... 9 1.1. Introduction ........................................................................................................................... 9 1.2. Key Features ...................................
RipEX Radio modem & Router 9. Troubleshooting ........................................................................................................................... 124 10. Safety, environment, licensing ................................................................................................... 126 10.1. Frequency ...................................................................................................................... 126 10.2. Safety distance ......................................
RipEX Radio modem & Router 5.2. Connecting to a PC over ETH and over ETH/USB adapter ....................................................... 61 5.3. PC address setting ..................................................................................................................... 62 5.4. Authentication ............................................................................................................................. 63 5.5. Status Menu .........................................................
Getting started Getting started 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 and a web browser. Antenna Sleep Input HW Alarm Input - GND + HW Alarm Output Supply +10 to +30 V - GND Indicator LEDs' ANT SI AI - + AO + - 10 – 30VDC ETH Default/Reset USB Ethernet COM 1 USB COM 2 COM1 RS232 COM2 RS232/485 Fig.
Getting started 2. 3. 4. 5. 7. Install antenna (Section 6.2, “Antenna mounting”). Install feed line (Section 6.3, “Antenna feed line”). Ensure proper grounding (Section 6.4, “Grounding”). 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.
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 – Radio router • Modbus, IEC101, DNP3, Comli, RP570, C24, DF1, Profibus, Modbus TCP, IEC104, DNP3 TCP etc.
RipEX – Radio router ETSI EN 301 489-5 V1.3.1 Electrical Safety (art 3.1.a) EN 60950-1:2006 EN 60950–1:2006/A11:2009, EN 60950–1:2006/A12:2011, EN 60950–1:2006/A1:2010 IP rating IP40 ETH IEEE 802.3i IEEE 802.3u IEEE 802.3af RS232 EIA-232-F RS485 EIA RS-485 IEC101 IEC 60870-5-101 IEC104 IEC 60870-5-104 DNP3 IEEE 1815-2010 Profibus DP IEC 61158 Type 3 © RACOM s.r.o.
RipEX in detail 2. RipEX in detail 2.1. Modes of operation Radio modem RipEX is best suited for transmission of a large number of short messages where a guaranteed delivery time 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.
RipEX in detail All the messages received from user interfaces (ETH&COM's) 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.
RipEX in detail 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.
RipEX in detail 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.
RipEX in detail 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: 1.
RipEX in detail 2. Parallel repeaters 1 2 Remote2 Improperly designed network: WRONG Repeater2 REM2 2 1 CEN RPT2 1 Centre 2 1 RPT1 2 2 REM1 X Repeater1 - 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.
RipEX in detail 2.3.2. 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.
RipEX in detail 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. 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..
RipEX in detail 10.10.10.3/24 Routing table RipEX3: 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 192.168.3.1/24 3 192.168.3.2/24 Radio IP 10.10.10.50/24 Routing table RipEX2: 192.168.1.0/24 è 10.10.10.1 192.168.50.0/24 è 10.10.10.1 192.168.3.0/24 è 10.10.10.1 10.10.10.2/24 Routing table RipEX50: 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 Default GW 192.168.50.2 192.168.2.1/24 2 192.168.2.2/24 ETH IP 192.168.50.
RipEX in detail 2.3.4. 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.
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, Comli, RP570, C24, DF1, Profibus). In this implementation SCADA protocol addresses are mapped to RipEX addresses and individual packets are transmitted as acknowledged unicasts.
RipEX in detail 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.
RipEX in detail 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).
RipEX in detail 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 TMonitoring 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.
RipEX in detail 83 – enables two highest Data rates COM2 – enables the second serial interface configurable as RS232 or RS485 10W – enables 10 W RF output power for CPSK modulation MASTER – enables all functionalities of all possible SW feature keys See chapter Adv. Conf., Firmware for more. 2.8. Software feature keys Certain advanced RipEX features are activated with software keys.
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.
Network planning dummy antenna RTU Centre config. PC RTU Fig. 3.1: Application bench test 3.2. Frequency 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.
Network planning 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 news attached to this - the reliability of high speed links in such environment is once again limited.
Network planning - RX antenna feeder loss [dB] -3.1 dB (10 m cable RG-58 CU, 400 MHz) = -88.8 dBm Received Signal Strength (RSS) 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.
Network planning 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 are in different phases when hitting the receiving antenna. They may add-up, they may cancel each other out. TX antenna Fig. 3.
Network planning 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: • • • • directional antennas "do not work", e.g.
Network planning lematic 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.
Network planning • dominant radio sites (e.g. telco towers on hill tops) should be avoided whenever possible. Placing a single repeater which serves most part of the network from the top of a hill is a straightforward but worst alternative, which makes the whole network very vulnerable.
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.
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. incorectly correctly Power supply RTU Fig. 3.8: Antenna mounting • Do not underestimate ageing of coaxial cables, especially at higher frequencies.
Network planning • DQ (Data Quality) Min. 180 • PER (Packet Error Rate) Max. 5 % © RACOM s.r.o.
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 150 58 50 118 DIN Rail Clip 134 DIN 35 Rail Fig. 4.1: RipEX dimensions, see more 133 122 60 124 2×o4,5 / 4×M3 Flat - bracket 8 L - bracket 70 122 95 175 Fig. 4.2: L-bracket and Flat-bracket, see more 38 RipEX Radio modem & Router – © RACOM s.r.o.
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. + + 10 – 30VDC ETH +– ALARM OUT. ALARM INPUT SLEEP - WAKE UP ANTENNA COM1 ETH/USB ADAPTER COM2 data equipment, RTU ETH data equipment, RTU LAN, control PC Fig. 4.3: Connectors 4.2.1. Antenna An antenna can connect to RipEX via TNC female 50Ω connector.
Product Fig. 4.5: 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 2 electric wires with a cross section of 0.
Product Lead Binding Screws (7) SI AI - + A0 + - 10–30VDC Pin No.: 1 2 3 4 5 6 7 Fig. 4.6: Supply connector Wire Ports (7) Retaining Screws (2) Fig. 4.7: 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.
Product 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 assignement Tab. 4.
Product 4.2.5. USB RipEX uses USB 1.1, Host A interface. USB interface is wired as standard: Tab. 4.4: USB pin description USB pin signal wire 1 +5 V red 2 Data(−) white 3 Data (+) green 4 GND black 1 2 3 4 Fig. 4.10: Serial connector The USB interface is designed for the connection to the "X5" – external ETH/USB adapter. The "X5" is an optional accessory to RipEX, for more see Section 5.3, “Connecting RipEX to a programming PC”.
Product 4.3. Indication LEDs Tab. 4.
Product 4.4. Technical specification Tab. 4.6: Technical parameters Radio parameters Frequency bands 135–154; 154–174; 300–320; 320–340; 340–360; 368–400; 400–432; 432–470; 928–960* MHz Channel spacing 6.25/12.5/25 kHz Frequency stability ±1.0 ppm Modulation Linear: 16DEQAM, D8PSK, π/4DQPSK, DPSK Exponencial (FM): 4CPFSK, 2CPFSK Detail 25 kHz Lin.: 83.33 – 62.50 – 41.67 kbps Exp.: 20.83 – 10.42 kbps max. 2 W max. 10 W 12.5 kHz 41.67 – 31.25 – 20.83 kbps 10.42 – 5.21 kbps max. 2 W max.
Product Spurious response rejection > 70 dB * not available yet, ** For output power 10 W it is recommended to use input power above 11 VDC Electrical Primary power 10 to 30 VDC, negative GND Rx 5 W/13.8 V; 4.8 W/24 V; (Radio part < 2 W) RF power Tx 4CPFSK, 2CPFSK Tx 16DEQAM, D8PSK, π/4DQPSK Power consumtion 13.8 V 24V 0.1 W 13.8 W 13.2 W 1W 15.2 W 14.4 W 5W 33.1 W 31.2 W 10 W 41.4 W 38.4 W 0.5 W 30.4 W 30 W 1W 30.4 W 30 W 2W 30.4 W 30 W Sleep mode 0.
Product Operating modes Bridge / Router User protocols on COM Modbus, IEC101, DNP3, UNI, Comli, DF1, RP570, Profibus… User protocols on Ethernet Modbus TCP, IEC104, DNP3 TCP, Comli TCP Terminal server… Serial to IP convertors Modbus RTU / Modbus TCP, DNP3 / DNP3 TCP Protocol on Radio channel Multi master applications Yes Report by exception Yes Collision Avoidance Capability Yes Remote to Remote communication Yes Addressed & acknowledged serial SCADA protocols Yes Data integrity control CRC
Product Tab. 4.7: Recommended Cables Port Recommended cables and accessories Lenght DC terminals – Power V03VH-H 2×0,5 Max. 3 m SI (Sleep Input) V03VH-H 1×0,5 Max. 3 m AI (Alarm Input) V03VH-H 1×0,5 Max. 3 m AO (Alarm Outout) V03VH-H 1×0,5 Max. 3 m COM1 LiYCY 4×0,14 Max. 3 m COM2 LiYCY 4×0,14 Max. 3 m USB USB to 10/100 Ethernet Adapter ADE-X5 Max. 3 m ETH STP CAT 5e As needed 48 RipEX Radio modem & Router – © RACOM s.r.o.
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.
Product Tab. 4.9: CE 12.5 kHz CE 12.5 kHz Classification kbps FEC Modulation Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 Blocking or desensitization [dBm] ±1 MHz ±5 MHz ±10 MHz 3.91 0.75 2CPFSK 7K00F1DCN -120 -117 -113 -6 -4 -3 5.21 1.00 2CPFSK 7K00F1DBN -119 -116 -112 -8 -6 -5 7.81 0.75 4CPFSK 7K00F1DDN -117 -114 -108 -6 -6 -5 10.42 1.00 4CPFSK 7K00F1DDN -115 -112 -105 -8 -8 -7 7.81 0.75 DPSK 11K9G1DCN -116 -114 -110 -4 -4 -3 10.42 1.
Product Tab. 4.11: FCC 25 kHz FCC 25 kHz Classification kbps FEC Modulation Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 Blocking or desensitization [dBm] ±1 MHz ±5 MHz ±10 MHz 15.63 0.75 4CPFSK 18K6F1DDN -116 -113 -108 -3.5 -1.0 -0.0 20.83 1.00 4CPFSK 18K6F1DDN -114 -111 -105 -5.0 -2.5 +1.5 26.04 0.75 π/4-DQPSK 19K8G1DDN -114 -111 -107 -4.5 -2.0 -0.5 34.72 1.00 π/4-DQPSK 19K8G1DDN -112 -109 -105 -6.5 -4.0 -2.0 39.06 0.
Product Note There are no official test report for CE 6.25 kHz and FCC 25 kHz as yet. When you want to set these respective modulations, select Type approval “Others” in Settings/Modulation rate. 52 RipEX Radio modem & Router – © RACOM s.r.o.
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.
Product Note Since SW feature key can be activated anytime within RipEX, it is not a part of the Code. 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.
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.14: RipEX-HS 1 For more information see RipEX-HS datasheet or User manual on www.racom.eu . 2.
Product Fig. 4.16: Demo case Contents: • 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.
Product 142 55 79 88 150 Fig. 4.17: Assembly dimensions with fan 5. L-bracket Installation L bracket for vertical mounting. For details on use see chapter Mounting and chapter Dimensions. Fig. 4.18: L-bracket 6. Flat-bracket Installation bracket for flat mounting. For details on use see chapter Mounting and chapter Dimensions. 7. Fig. 4.19: Flat bracket 19" rack shelf – single • 1,6U (70 mm) high • Ready for assembly with one RipEX • Weight 2.
Product Fig. 4.20: 19" Rack shelf 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 Fig. 4.21: 19" Rack shelf – double 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 0.1 W only. Fig. 4.22: Dummy load 10.
Product 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. For the part numbers of individual accessories for your orders please see chapter Model offerings. © RACOM s.r.o.
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.
Bench test 1. Using the "X5" - external ETH/USB adapter 2. Directly over the ethernet interface https://10.9.8.7 PC DHCP https://192.168.169.169 PC 192.168.169.250 Fig. 5.2: Connecting to a PC over ETH and over ETH/USB adapter 1. 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.
Bench test Fig. 5.3: PC address setting Note: 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. 3. 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 of RipEXfield: • 10.9.8.
Bench test Fig. 5.4: Authentication The default entries for a new RipEX are: User name: admin Password: admin Click OK. Initial screen should appear then: Fig. 5.5: Status Menu 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.) 4.
Bench test 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 Configuration. To setup the IP addresses you can use the examples in Section 2.3.
Installation 6. Installation Step-by-step checklist 1. 2. 3. 4. 5. Mount RipEX into cabinet (Section 6.1, “Mounting”). Install antenna (Section 6.2, “Antenna mounting”). Install feed line (Section 6.3, “Antenna feed line”). Ensure proper grounding (Section 6.4, “Grounding”). 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.
Installation Fig. 6.3: Vertical widthwise mounting to DIN rail Fig. 6.4: Vertical lengthwise mounting to DIN rail 6.1.2. Flat mounting For flat mounting directly to the support you must use the Flat bracket (an optional accessory). Fig. 6.5: Flat mounting using Flat bracket 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.
Installation Fig. 6.6: Rack shelf 6.1.4. Fan kit In extreme temperatures you can install an external fan kit for additional cooling. The fan kit installs using three screws driven into the openings on the bottom side of the RipEX. Use M4×8 screws. Fig. 6.7: Fan kit mounting The fan kit may be controlled using the Alarm Output (Control and Power connector, Section 4.2.
Installation Fan Kit Fan Kit SI AI - Pin No.: black black red SI AI - + A0 + 10–30VDC 1 2 3 4 5 6 7 Fig. 6.8: Fan kit using Alarm Output, recommended Pin No.: red + A0 + 10–30VDC 1 2 3 4 5 6 7 Fig. 6.9: Fan kit, always on 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.
Installation The shorter the feed line, the better. RipEX can be installed right next to the antenna and an ethernet cable can be used to connect it to the rest of the installation and to power the RipEX . An ethernet cable can also be used 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.
Advanced Configuration 7. Advanced Configuration This chapter is identical with the content of Helps for individual menu. 7.1. Menu header 7.1.1. Generally 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.
Advanced Configuration 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 When a Remote RipEX is sucessfully 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. 7.2. Status Fig. 7.2: Menu Status 7.2.1.
Advanced Configuration Refresh - complete refresh of displayed values is performed. 7.3. Settings Fig. 7.3: Menu Settings 7.3.1. Device Unit name Default = NoName Each Unit may have its unique name – an alphanumeric string of up to 16 characters. Although UTF8 is supported, ASCII character has to be used on the first position in the Unit name. Following characters are not allowed: " (Double quote) ` (Grave accent) \ (Backslash) $ (Dollar symbol) ; (Semicolon) Note: Unit name is solely for the user's conv
Advanced Configuration Bridge Bridge mode is suitable for Point-to-Multipoint networks, where Master-Slave application with pollingtype communication protocol is used. RipEX in Bridge mode is as easy to use as a simple transparent device, while allowing for a reasonable level of communication reliability and spectrum efficiency in small to medium size networks.po In Bridge mode, the protocol on Radio channel does not have the collision avoidance capability. There is CRC check of data integrity, i.e.
Advanced Configuration Default = 0 It delays forwarding of all frames from user interfaces (ETH&COM's) to the Radio channel for the set time. The set value should be equal to the transmitting time of the longest message. • This should be used when e.g. all sub-stations (RTU's) reply to a broadcast query from the master station. In such a case a massive collisions would take place, because all sub-stations (RTU's) would reply more or less in the same instant.
Advanced Configuration Default = On ○ On 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 its setting of Retries.
Advanced Configuration 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 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.
Advanced Configuration • 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).
Advanced Configuration • • • • Connection state – state-firewall active only for TCP protocol. New – rrelates to the first packet when a TCP connection starts (Request from TCP client to TCP server for opening a new TCP connection). Used e.g. for allowing to open TCP only from RipEX network to outside. Established – relates to an already existing TCP connection. Used e.g. for allowing to get replies for TCP connections created from RipEX network to outside.
Advanced Configuration • • • • List box: Default, Manual, Default = Default Default – Default (recommended) values are set and can not be edited. Manual – Thresholds can be set manually. SNMP Alarm List box: Off, On. Default = Off If “On”, SNMP Alarm trap is activated. The SNMP trap message is sent both when a parameter value exceeds the alarm threshold and when it returns back within its “normal” range. Remember to set the IP destination address for SNMP trap messages. Port number is always 162.
Advanced Configuration • When On, RipEX remains on for the set seconds from the moment of its wake-up. ○ Timeout from wake-up [sec.] Default = 300 [240 - 64 800] RipEX stays on for the set time from the moment of its wake-up. ○ Reset timeout on received packets List box: On, Off Default = Off If On, the Timeout from wake-up is reset with each packet received Sleep Mode Sleep Mode is controlled via the digital input on Power and Control connector.
Advanced Configuration i.e. without a repeater. The graph data is stored in files, each file contains 60 samples of all values. The sampling period can be configured. There are two types of graphs- Overview and Detail. Overview graphs cover a continuous time interval back from the present, they use relatively long sampling period. Detail graph is supposed to be used in case of a special event, e.g. an alarm, and the sampling period is much shorter. ○ Logged Neighbour IP’s Default = 0.0.0.
Advanced Configuration 7.3.2. Radio Fig. 7.5: Menu Radio * Active only when in Router mode ** These items have to be set in accordance with the license issued by the respective radio regulatory authority IP* Default = 10.10.10.169 IP address of Radio interface Mask* Default = 255.255.255.0 Network Mask of Radio interface TX frequency** Transmitting frequency. Format MHz.kHz.Hz. Step 5 (for 25 kHz channel spacing) or 6.25 kHz (for 12.5 or 6.25 kHz channel spacing).
Advanced Configuration RF power [W]** List box: possible values Default = 5 W The range of values in the list box is limited to 2 W for high Modulation rates. 10 W is available only for lower Modulation rates (CPFSK) and only when the corresponding SW feature key is active. Channel spacing [kHz]** List box: possible values Default = 25 kHz The wider the channel the higher the posible Modulation rate.
Advanced Configuration 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. On an individual link the optimizer supervises the traffic and it tries to join short packets when opportunity comes. However in case of heavy load on one link (e.g.
Advanced Configuration 7.3.3. ETH * Active only when Router mode Fig. 7.6: Menu Ethernet IP Default = 192.168.169.169 IP address of ETH interface Mask Default = 255.255.255.0 Mask of ETH interface Default GW Default = 0.0.0.0 The default gateway (applies to whole RipEX). It can be set only in the Routing menu while Router mode.
Advanced Configuration End IP DHCP server assigns IP addresses to clients from the range defined by Start IP and End IP (inclusive). No of leases Default = 5 [1 - 255] Maximum number of DHCP client(s) which can RipEX simultaneously serve. It can not be more than the number of addresses available in the Start IP - End IP range. Lease timeout [DD:HH:MM:SS] Default = 1 day (max.
Advanced Configuration • • • • • • My TCP port Default = 502 [1 - 65 535] TCP port used for Modbus TCP in RipEX. TCP Keepalive [sec.] Default = 120 [0 - 16 380] 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. SCADA application typically uses a specific address for such messages.
Advanced Configuration assigned to COM1(2) or to a Terminal server or to any special daemon running in the destination RipEX, the packet is discarded. ○ Table The Address translation is defined in a table. There are no limitations like when the Mask translation is used. If there are more SCADA units on RS485 interface, their “Protocol addresses” translate to the same IP address and UDP port pair. . There are 3 possibilities how to fill in aline in the table: − One "Protocol address" to one "IP address" (e.
Advanced Configuration Note: The TCP (UDP) session operates only locally between the RipEX and the central computer, hence it does not increase the load on Radio channel. In some special cases, the Terminal server can be also used for reducing the network load from applications using TCP. A TCP session can be terminated locally at the Terminal server in RipEX, user data extracted from TCP messages and processed like it comes from a COM port.
Advanced Configuration Fig. 7.7: Menu COM Type List box: possible values Default = RS232 COM1 is always RS232, COM2 can be configured to either RS232 or RS485. Note: The settings of Data rate, Data bits, Parity and Stop bits of COM port and connected device must match. Baud rate [bps] List box: standard series of rates from 300 to 115200 bps Default = 19200 Select Baud rate from the list box: 300 to 115200 bps rates are available.
Advanced Configuration Wikipedia: Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Idle [bytes] Default = 5 [0 - 2000] This parameter defines the maximum gap (in bytes) in the received data stream. If the gap exceeds the value set, the link is considered idle, the received frame is closed and forwarded to the network.
Advanced Configuration 7.3.5. Protocols Fig. 7.8: Menu Protocols COM Generally Each SCADA protocol like Modbus, DNP3, IEC101, DF1 etc. has its unique message format, most importantly its unique way of addresing of remote units. The basic task for protocol utility is to check whether received frame is within protocol format and it is not corrupted. Most of the SCADA protocols are using some type of Error Detection Codes (Checksum, CRC, LRC, BCC, etc.
Advanced Configuration used, e.g. multi-master polling and/or spontaneous communication from remote units and/or parallel communication between remote units etc. Note: These Radio protocol features are available only in the Router mode. The Bridge mode is suitable for simple Master-Slave arrangement with a polling-type application protocol. Common parameters The parameters described in this section are typical for most protocols. There is only a link to them in description of the respective Protocol.
Advanced Configuration • 94 − only one SCADA device to one COM port can be connected, even if the RS485 interface is used • Base IP Default = IP address of ETH interface When the IP destination address of UDP datagram, in which serial SCADA message received from COM1(2) is encapsulated, is created, this Base IP is taken as the basis and only the part defined by Mask is replaced by 'Protocol address'. • Mask Default = 255.255.255.
Advanced Configuration Messages from serial interface are processed in similar way as at Master site, i.e. they are encapsulated in UDP datagrams, processed by router inside the RipEX and forwarded to the respective interface, typically to Radio channel. ○ Broadcast accept List box: On, Off Default = On If On, broadcast messages from the Master SCADA device to all Slave units are accepted and sent to connected Slave SCADA unit. Protocols implemented: None All received frames from COM port are discarded.
Advanced Configuration List box: Format1,Format2,Format3,Format4,Format5 Default = Format1 One of the possible C24 Frames formats can be selected. According to the C24 protocol specification, it is possible to set Frames formats 1-4 for Protocol frames 1C-3C and formats 1-5 for 4C. Note: The RipEX accepts only the set Protocol frames and Frames format combination. All other combinations frames are discarded by the RipEX and not passed to the application.
Advanced Configuration Master Address translation Table Mask Slave DF1 Only the full duplex mode of DF1 is supported. Each frame in the Allen-Bradley DF1 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in the Full duplex mode in terms of RipEX configuration. • • Block control mode List box: BCC, CRC Default = BCC According to the DF1 specification, either BCC or CRC for Block control mode (data integrity) can be used.
Advanced Configuration IEC 870-5-101 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. IEC 870-5-101 protocol configuration is using all parameters described in Common parameters. Mode of Connected device Master Broadcast - only On, Off.
Advanced Configuration Note: There is not a possibility to set the Broadcast address, since ITT Flygt broadcast messages always have the address 0xFFFF. Hence when the Broadcast is On, packets with this destination are handled as broadcasts. • • 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.
Advanced Configuration Mode of Connected device Master Broadcast Address translation Table Mask Slave Broadcast accept RP570 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. Underlined parameters are described in Common parameters.
Advanced Configuration Table Mask Slave Slave • Local simulation RB List box: Off, On Default = Off The RP570 Slave expects to receive RB packets from the Master. When the Local simulation RB on the Master is On, the RB packets are transferred over the Radio channel only in the RB Net period (see Master settings). The Local simulation RB has to be set the same (On or Off) on all sites in the network, i.e. on the master as well as all slaves.
Advanced Configuration Mode of Connected device Master • • • • Address mode List box: Binary (1 B), ASCII (2 B), Binary (2B LSB first). Binary (2B MSB first). Default = Binary (1 B) RipEX reads the Protocol address in the format and length set (in Bytes). The ASCII 2-Byte format is read as 2-character hexadecimal representation of one-byte value. E.g. ASCII characters AB are read as 0xAB hex (10101011 binary, 171 decimal) value.
Advanced Configuration Broadcast Address translation Table Mask Slave Broadcast accept © RACOM s.r.o.
Advanced Configuration 7.4. Routing 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. The COM ports are treated in the standard way as router devices, messages can be delivered to them as UDP datagrams to selected UDP port numbers.
Advanced Configuration the network defined by IP and Mask of one of the interfaces (Radio, ETH), otherwise the packet is discarded. Each line in the routing table defines a Gateway (the route, the next hop) for the network (group of addresses) defined by Destination IP and Mask. When the Gateway for the respective destination IP address is not found in the Routing table, the packet is forwarded to the Default gateway. When Default gateway is not defined (0.0.0.0), the packet is discarded.
Advanced Configuration 7.5. Diagnostic 7.5.1. Neighbours and Statistic Fig. 7.10: Menu Neighbours Neighbours and Statistics follow the same pattern. Most importantly, they share a common time frame. One Log save period and one Difference log (pair of Clear and Display buttons) apply to both logs. 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 Log save period).
Advanced Configuration • Notice, that the Log start, Last upd. and Log uptime labels at the top change to Diff. start, Diff. upd. and Diff. uptime when the Difference log is displayed. They show the respective values for Difference log. History 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.
Advanced Configuration • • • • red background indicates, that the item is monitored for alarm and its average value is in the alarm range (Settings/Device/Alarm management) when the value of RSS, DQ, Ucc, Temp, PWR, VSWR is not known, N/A is displayed. These N/A values are not displayed in Graphs Ucc, Temp, PWR, VSWR are refreshed every 1s.
Advanced Configuration Statistic Fig. 7.11: Menu Statistic Statistic log provides information about communication on all interfaces: Radio, ETH, COM1, COM2. Balloon tips provide on line help for all column names. These tips explain the meanings and the way of calculation of individual values. Meaning of IP addresses listed: Rx - for received (Rx) packets, the IP source address from UDP header is displayed.
Advanced Configuration Fig. 7.12: Menu Graphs • • • • • Sampling period Here just for information, to be set in Settings/Graphs. File period File period corresponds to the time, for which the values have been recorded in the file. The 60 samples per graph file result in (depending on the Sampling period) 60 (2d 11:00:00), 120 (4d 23:00:00), 240 (9d 23:00:00) or 720 (29d 23:00:00) hours recorded in each file.
Advanced Configuration • • • • • There is a list of values, which can be displayed. These values are also recorded in Neighbours or Statistic files. Their meanings can be found in help Neighbours&Statistic. 2nd IP, 2nd line It is possible to display two values from the same unit or from two different ones. Show thresholds You can show thresholds for the displayed value which are set in the unit (Settings/Device/Alarm management).
Advanced Configuration 7.5.3. Tools Ping Fig. 7.13: Menu Ping Ping (Packet InterNet Groper) is a utility used to test the reachability of a particular host on an IP network. It operates by sending echo request packets to the target host and waiting for an echo response. In the process it measures the rtt (round trip time - the time from transmission to reception) and records any packet loss.
Advanced Configuration • • • • • • This is a standard ICMP (Internet Control Message Protocol) ping. It can be used against either RipEX or any device connected to RipEX Radio network. ○ RSS RSS Ping Type uses a special UDP packets and provides extension report which includes: ■ RSS and DQ information for each radio hop for each individual ping ■ RSS and DQ statistic (average, min., max.
Advanced Configuration "131 bytes from 192.168.131.243: seq=1 rtt=0.805s" "10.10.10.241-->10.10.10.242 :56/209[RSS/DQ]-->10.10.10.243:51/225[RSS/DQ]->192.168.131.243" "192.168.131.243-->10.10.10.242 :46/214[RSS/DQ]-->10.10.10.241 :57/213[RSS/DQ]->10.10.10.241" 131 bytes = RSS packet size (RACOM header + data + trace) 10.10.10.242 = repeater IP 192.168.131.
Advanced Configuration • There is the distribution of rtt (round trip times) of received pings. Time intervals in the table are 1/4 of the Timeout set in ping parameters. The XXXX... characters at the end of the line form a simple bar chart. Buttons Start - starts pinging Stop - stops pinging, Statistic report is displayed afterwards Clear - clears the reports on the screen Monitoring Fig. 7.
Advanced Configuration RADIO, COM1, COM2, ETH, Internal When ticked, the setting for the respective interface(s) is enabled. When the "Internal" interface is ticked, another set of interface tick-boxes appears as follows: • Internal: RADIO, COM1, COM2, TS1, TS2, TS3, TS4, TS5, Modbus TCP When ticked, the setting for the respective internal interface(s) is enabled (see the description below). Common parameters for all interfaces: Destination IP address ○ Rx ○ Tx Tick boxes.
Advanced Configuration The Radio IP source address of the frame has to be within the range defined: aaa.bbb.ccc.ddd/mask. ○ Radio IP dst The Radio IP destination address of the frame has to be within the range defined: aaa.bbb.ccc.ddd/mask. ○ Headers: List box: None, Radio Link, Data Coding, Both Default = None ■ None – only the Radio Link Protocol data is displayed ■ Radio Link – Radio Link Control Header is displayed. It contains e.g. frame type, No., Radio MAC addresses etc.
Advanced Configuration • • • Default=Off When Off, datagrams to and from HTTPS, HTTP and SSH ports in this unit are not monitored. This avoids monitoring loop under normal circumstances, i.e. when the on-line monitoring is viewed on local PC connected via the ETH interface. ○ Advanced parameters: ■ User rule The standard tcpdump program is used for ETH monitoring. An arbitrary user rule in tcpdump syntax can be written in the text box.
Advanced Configuration • Start (File Start) button has been gray. Clicking the Apply button enforces the configuration change (e.g. adding one more interface) to the running monitoring process Internal interfaces description Internal interfaces are the interfaces between a SW module and the central router module. All these interfaces can be located in Fig.
Advanced Configuration 7.6. Maintenance 7.6.1. SW feature keys Fig. 7.16: Menu SW feature keys Certain advanced RipEX features have to be activated by software keys. On the right side one may see the list of available keys and their respective status values. Possible status values are: • • • • • Not present Active Active (timeout dd:hh:mm:ss) – the key can be time limited. For such a key, the remaining time of activity is displayed (1d 07:33:20).
Advanced Configuration 7.6.2. Configuration Fig. 7.17: Menu Maintenance Configuration • UNIT ○ Back up – Back up saves the active configuration into a backup file in the unit. ○ Restore – configuration saved in the backup file in the unit is activated and the unit reboots itself. ○ Factory settings – sets the factory defaults and activates them. Neighbours, Statistic and Graphs databases are cleared. The unit reboots afterwards.
Advanced Configuration Note it is recommended to do this only over reliable Ethernet connections and not over the Radio channel. • • Archive to Active – when pressed, the Active firmware is substituted by the Archive firmware. Either “All” or only “Only the different” versions are replaced according to the Versions list box setting. The unit reboots itself afterwards. Copy Archive to Other unit – he Archive firmware package can be copied to another unit typically over Radio channel.
CLI Configuration 8. CLI Configuration CLI interface (Command Line Interface) is an alternative to web access. You can work with the CLI interface in text mode using an appropriate client, either ssh (putty) or telnet. 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. Private key is downloaded in RipEX, for public key kindly contact RACOM and provide RipEX S/N.
Troubleshooting 9. Troubleshooting 1. 2. I don’t know what my RipEX’s IP is – how do I connect? • Use the "X5" – external ETH/USB adapter and a PC as a DHCP client. Type 10.9.8.7 into your browser’s location field. • 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.
Troubleshooting arp -d 192.168.169.169 or delete the entire table by typing: arp -d * 5. 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. 6. • Change the PC’s IP address so that it is on the same subnet as the RipEX. I entered the Router mode and lost connection to the other RipEX’s. 7. • Enter correct data into the routing tables in all RipEX’s. The RSS Ping test shows low RSS for the required speed. • 8.
Safety, environment, licensing 10. Safety, environment, licensing 10.1. Frequency The radio modem must be operated only in accordance with the valid frequency license issued by national frequency authority and all radio parametres have to be set exactly as listed. Important Use of frequencies between 406.0 and 406.1 MHz is worldwide-allocated only for International Satellite Search and Rescue System.
Safety, environment, licensing 160 MHz/2 m band – 5 W RF power SA160.3 5 element directional Yagi 8.0 6.3 200 90 SA160.5 9 element directional Yagi 12.5 17.8 330 150 160 MHz/2 m band – 4 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV160.1 single dipole 4.6 2.9 120 60 OV160.2 stacked double dipole 7.6 5.8 170 80 SA160.3 5 element directional Yagi 8.0 6.3 180 80 SA160.5 9 element directional Yagi 12.5 17.
Safety, environment, licensing 160 MHz/2 m band – 0.5 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV160.1 single dipole 4.6 2.9 45 20 OV160.2 stacked double dipole 7.6 5.8 60 30 SA160.3 5 element directional Yagi 8.0 6.3 70 30 SA160.5 9 element directional Yagi 12.5 17.8 110 50 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] Tab. 10.
Safety, environment, licensing 300–400 MHz/70 cm band – 4 W RF power SA380.9 9 element directional Yagi 12.5 17.8 200 90 300–400 MHz/70 cm band – 3 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV380.1 single dipole 4.6 2.9 70 30 OV380.2 stacked double dipole 7.6 5.8 100 45 SA380.3 3 element directional Yagi 7.6 5.8 100 45 SA380.5 5 element directional Yagi 8.7 7.4 110 50 SA380.9 9 element directional Yagi 12.5 17.
Safety, environment, licensing 300–400 MHz/70 cm band – 0.5 W RF power SA380.3 3 element directional Yagi 7.6 5.8 40 20 SA380.5 5 element directional Yagi 8.7 7.4 45 20 SA380.9 9 element directional Yagi 12.5 17.8 70 30 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.
Safety, environment, licensing • • • • • Liability for defects does not apply to any product that has been used in a manner which conflicts with the instructions contained in this operator manual, or if the case in which the radio modem is located has been opened, or if the equipment has been tampered with.
Safety, environment, licensing cences on contacts listed on http://www.racom.eu. This product also includes software developed by the University of California, Berkeley and its contributors. 10.7.
OID mappings Appendix A. OID mappings "MIB tables", and whole file "OID mappings" can be downloaded from: 1 http://www.racom.eu/eng/products/radio-modem-ripex.html#download 1 http://hnilux.racom.cz:3004/eng/products/radio-modem-ripex.html#download © RACOM s.r.o.
OID mappings RipEX Name RIPEX Language SMIv2 Contact Racom s.r.o Mirova 1283 592 31 Nove Mesto na Morave Czech Republic Tel: +420 565 659 511 Fax: +420 565 659 512 E-mail: racom@racom.eu Description The MIB module defines management objects for product Ripex. OID MAPPINGS: comIdle 1.3.6.1.4.1.33555.2.2.5.2.1.2 column COM interface idle in bytes. comIndex 1.3.6.1.4.1.33555.2.2.5.2.1.1 column A unique index for each interface. comMtu 1.3.6.1.4.1.33555.2.2.5.2.1.
OID mappings RipEX stComTable 1.3.6.1.4.1.33555.2.3.4.2 table stRadio 1.3.6.1.4.1.33555.2.3.1 node A list of COM port entries. stRadioRemEntry 1.3.6.1.4.1.33555.2.3.1.3.1 row stRadioRemNumber 1.3.6.1.4.1.33555.2.3.1.2 scalar A radio remote station entry. The number of remote stations. stRadioRemTable 1.3.6.1.4.1.33555.2.3.1.3 table A list of remote station entries. stRadioTotBytesRX 1.3.6.1.4.1.33555.2.3.1.1.10 scalar Remote station total RX bytes counter. stRadioTotBytesTX 1.3.6.1.
OID mappings RipEX swVerDriver 1.3.6.1.4.1.33555.2.1.1.7.3 scalar Driver firmware version. swVerSDDR 1.3.6.1.4.1.33555.2.1.1.7.2 scalar SDDR firmware version. swVermodem 1.3.6.1.4.1.33555.2.1.1.7.1 scalar Modem firmware version. swVersions 1.3.6.1.4.1.33555.2.1.1.7 node system 1.3.6.1.4.1.33555.2.1.2 node tsComProtType 1.3.6.1.4.1.33555.2.2.4.3.1.8 column Terminal server COM user protocol type. tsEnable 1.3.6.1.4.1.33555.2.2.4.3.1.2 column Terminal server interface on/off.
OID mappings RipEX trpCom1Pr 1.3.6.1.4.1.33555.2.10.11 notification COM1 Rx/Tx packet ratio out of range. trpCom2Pr 1.3.6.1.4.1.33555.2.10.12 notification COM2 Rx/Tx packet ratio out of range. trpDq 1.3.6.1.4.1.33555.2.10.2 notification DQ of remote station is out of range. trpHotStby 1.3.6.1.4.1.33555.2.10.14 notification Modem becomes active in Hot-Standby. trpHwIn 1.3.6.1.4.1.33555.2.10.13 notification HW input in alarm state. trpLanPr 1.3.6.1.4.1.33555.2.10.
OID mappings RFC1213-MIB Name RFC1213-MIB Language SMIv1 Contact Description OID MAPPINGS: at 1.3.6.1.2.1.3 node atEntry 1.3.6.1.2.1.3.1.1 row Each entry contains one NetworkAddress to `physical' address equivalence. column The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of IfIndex. column The NetworkAddress (e.g.
OID mappings RFC1213-MIB egpNeighInErrMsgs 1.3.6.1.2.1.8.5.1.8 column The number of EGP-defined error messages received from this EGP peer. egpNeighInErrs 1.3.6.1.2.1.8.5.1.5 column The number of EGP messages received from this EGP peer that proved to be in error (e.g., bad EGP Checksum). egpNeighInMsgs 1.3.6.1.2.1.8.5.1.4 column The number of EGP messages received without error from this EGP peer. egpNeighIntervalHello 1.3.6.1.2.1.8.5.1.
OID mappings RFC1213-MIB icmpOutAddrMasks 1.3.6.1.2.1.5.25 scalar The number of ICMP Address Mask Request messages Sent. icmpOutDestUnreachs 1.3.6.1.2.1.5.16 scalar The number of ICMP Destination Unreachable messages sent. icmpOutEchoReps 1.3.6.1.2.1.5.22 scalar The number of ICMP Echo Reply messages sent. icmpOutEchos 1.3.6.1.2.1.5.21 scalar The number of ICMP Echo (request) messages sent. icmpOutErrors 1.3.6.1.2.1.5.
OID mappings RFC1213-MIB ifLastChange 1.3.6.1.2.1.2.2.1.9 column The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a zero Value. ifMtu 1.3.6.1.2.1.2.2.1.4 column The size of the largest datagram which can be sent/received on the interface, specified in octets.
OID mappings RFC1213-MIB ipAdEntBcastAddr ipAdEntIfIndex 1.3.6.1.2.1.4.20.1.4 1.3.6.1.2.1.4.20.1.2 column The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface.
OID mappings RFC1213-MIB ipInDiscards 1.3.6.1.2.1.4.8 scalar The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. ipInHdrErrors 1.3.6.1.2.1.4.
OID mappings RFC1213-MIB ipReasmReqds 1.3.6.1.2.1.4.14 scalar The number of IP fragments received which needed to be reassembled at this entity. ipReasmTimeout 1.3.6.1.2.1.4.13 scalar The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity. column The number of seconds since this route was last updated or otherwise determined to be correct.
OID mappings RFC1213-MIB ipRouteMetric5 ipRouteNextHop 1.3.6.1.2.1.4.21.1.12 1.3.6.1.2.1.4.21.1.7 column An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1. column The IP address of the next hop of this route.
OID mappings RFC1213-MIB snmpInGenErrs 1.3.6.1.2.1.11.12 scalar The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `genErr'. snmpInGetNexts 1.3.6.1.2.1.11.16 scalar The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol Entity. scalar The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP Protocol entity.
OID mappings RFC1213-MIB snmpOutTooBigs 1.3.6.1.2.1.11.20 scalar The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `tooBig.' snmpOutTraps 1.3.6.1.2.1.11.29 scalar The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity. scalar The textual identification of the contact person for this managed node, together with information on how to contact this person. sysContact 1.3.6.1.2.1.1.
OID mappings RFC1213-MIB tcpConnEntry 1.3.6.1.2.1.6.13.1 row Information about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED State. column The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used. tcpConnLocalAddress 1.3.6.1.2.
OID mappings RFC1213-MIB tcpRtoMax 1.3.6.1.2.1.6.3 scalar The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
OID mappings RS-232-MIB Name RS-232-MIB Language SMIv2 Contact Bob Stewart Postal: Xyplex, Inc. 295 Foster Street Littleton, MA 01460 Tel: 508-952-4816 Fax: 508-952-4887 E-mail: rlstewart@eng.xyplex.com Description The MIB module for RS-232-like hardware devices. OID MAPPINGS: rs232 1.3.6.1.2.1.10.33 node A control for the port's ability to automatically sense input speed. rs232AsyncPortAutobaud 1.3.6.1.2.1.10.33.3.1.
OID mappings RS-232-MIB Identification of a hardware signal, as follows: rs232OutSigName 1.3.6.1.2.1.10.33.6.1.2 column rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector rs232OutSigPortIndex 1.3.6.1.2.1.10.33.6.1.
OID mappings RS-232-MIB rs232SyncPortInterruptedFrames 1.3.6.1.2.1.10.33.4.1.6 column Total number of frames that failed to be received or transmitted on the port due to loss of modem signals since system re-initialization and while the port state was 'up' or 'test'. rs232SyncPortMinFlags 1.3.6.1.2.1.10.33.4.1.14 column The minimum number of flag patterns this port needs in order to recognize the end of one frame and the start of the next. Plausible values are 1 and 2.
Abbreviations Appendix B. Abbreviations ACK Acknowledgement MDIX Medium dependent interface crossover AES Advanced Encryption Standard MIB Management Information Base ATM Automated teller machine NMS Network Management System BER Bit Error Rate N.C. Normally Closed CLI Command Line Interface N.O.
Abbreviations TCP Transmission Control Protocol TS5 Terminal server 5 TX Transmitter UDP User Datagram Protocol VSWR Voltage Standing Wave Ratio WEEE Waste Electrical and Electronic Equipment 154 RipEX Radio modem & Router – © RACOM s.r.o.
Index Symbols 10. Feedline cable, 58 A accessories, 55 addressing bridge, 15 router, 19 alarm in/out, 41 management, 78 antenna, 39 dummy load, 58, 60 mounting, 68 separated, 53 B basic setup, 64 bench test, 60 brc COM, 93 diagnostic, 80 TCP, 86 bridge, 12, 72 C COM parameters, 89 protocols, 92 config.
Index N neighbours, 80, 107 network example, 21 layout, 33 planning, 27 networkt management, 23 O consumption, 46, 79 SW feature keys, 120 T technical parameters, 45 technical support, 122 Terminal server, 89 time, 76 troubleshooting, 124 ordering code, 53 output hw, 41 U P W part number, 53 password, 122 ping menu, 112 pooling, 12 power management, 79 product code, 53 Conformity, 132 protocols COM, 92 USB adapter, 55 WEEE compliance, 130 R radio parameters, 49, 82 router, 9 repeater bridge,
Revision History Appendix C. Revision History Revision This manual was prepared to cover a specific version of firmware code. Accordingly, some screens and features may differ from the actual unit you are working with. While every reasonable effort has been made to ensure the accuracy of this publication, product improvements may also result in minor differences between the manual and the product shipped to you. Revision 1.1 First issue 2011-08-31 Revision 1.
