Racom RIPEX-154 VHF NARROWBAND RADIOMODEM User Manual RipEX Radio modem Router
Racom VHF NARROWBAND RADIOMODEM RipEX Radio modem Router
Racom >
User Manual
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.eu Table of Contents Getting started ..................................................................................................................................... 7 1. RipEX – Radio router ...................................................................................................................... 9 1.1. Introduction ........................................................................................................................... 9 1.2. Key Features ........................................................................................................................ 9 1.3. Standards ........................................................................................................................... 10 2. RipEX in detail ............................................................................................................................... 12 2.1. Modes of operation ............................................................................................................. 12 2.2. Bridge mode ....................................................................................................................... 12 2.3. Router mode ....................................................................................................................... 17 2.4. Serial SCADA protocols ..................................................................................................... 22 2.5. Combination of IP and serial communication ..................................................................... 23 2.6. Diagnostics & network management .................................................................................. 23 2.7. Firmware update and upgrade ........................................................................................... 25 2.8. Software feature keys ......................................................................................................... 26 3. Network planning ........................................................................................................................... 27 3.1. Data throughput, response time ......................................................................................... 27 3.2. Frequency .......................................................................................................................... 28 3.3. Signal budget ..................................................................................................................... 29 3.4. Multipath propagation, DQ ................................................................................................. 31 3.5. Network layout .................................................................................................................... 33 3.6. Hybrid networks .................................................................................................................. 35 3.7. Assorted practical comments ............................................................................................. 35 3.8. Recommended values ........................................................................................................ 36 4. Product .......................................................................................................................................... 38 4.1. Dimensions ......................................................................................................................... 38 4.2. Connectors ......................................................................................................................... 39 4.3. Indication LEDs .................................................................................................................. 44 4.4. Technical specification ........................................................................................................ 45 4.5. Model offerings ................................................................................................................... 53 4.6. Accessories ........................................................................................................................ 55 5. Bench test ..................................................................................................................................... 60 5.1. Connecting the hardware ................................................................................................... 60 5.2. Powering up your RipEX .................................................................................................... 60 5.3. Connecting RipEX to a programming PC ........................................................................... 60 5.4. Basic setup ......................................................................................................................... 64 5.5. Functional test .................................................................................................................... 64 6. Installation ..................................................................................................................................... 65 6.1. Mounting ............................................................................................................................. 65 6.2. Antenna mounting .............................................................................................................. 68 6.3. Antenna feed line ............................................................................................................... 68 6.4. Grounding ........................................................................................................................... 69 6.5. Connectors ......................................................................................................................... 69 6.6. Power supply ...................................................................................................................... 69 7. Advanced Configuration ................................................................................................................ 70 7.1. Menu header ...................................................................................................................... 70 7.2. Status ................................................................................................................................. 71 7.3. Settings ............................................................................................................................... 72 7.4. Routing ............................................................................................................................. 104 7.5. Diagnostic ......................................................................................................................... 106 7.6. Maintenance ..................................................................................................................... 120 8. CLI Configuration ........................................................................................................................ 123 © RACOM s.r.o. – RipEX Radio modem & Router RipEX Radio modem & Router 9. Troubleshooting ........................................................................................................................... 124 10. Safety, environment, licensing ................................................................................................... 126 10.1. Frequency ...................................................................................................................... 126 10.2. Safety distance ............................................................................................................... 126 10.3. High temperature ............................................................................................................ 130 10.4. RoHS and WEEE compliance ........................................................................................ 130 10.5. Conditions of Liability for Defects and Instructions for Safe Operation of Equipment .... 130 10.6. Important Notifications .................................................................................................... 131 10.7. Product Conformity ......................................................................................................... 132 A. OID mappings ............................................................................................................................. 133 B. Abbreviations .............................................................................................................................. 153 Index ................................................................................................................................................ 155 C. Revision History .......................................................................................................................... 157 List of Figures 1. RipEX radio router ........................................................................................................................... 7 2.1. Bridge mode example ................................................................................................................ 15 2.2. Addressing ................................................................................................................................. 20 2.3. Optimised addressing ................................................................................................................. 21 2.4. Monitoring ................................................................................................................................... 25 3.1. Application bench test ................................................................................................................ 28 3.2. Signal path ................................................................................................................................. 29 3.3. Multipath propagation ................................................................................................................. 31 3.4. Antenna location ......................................................................................................................... 32 3.5. Main lobe .................................................................................................................................... 33 3.6. Dominant repeater ...................................................................................................................... 34 3.7. Isolated branches ....................................................................................................................... 34 3.8. Antenna mounting ...................................................................................................................... 36 4.1. RipEX dimensions, see more ..................................................................................................... 38 4.2. L-bracket and Flat-bracket, see more ........................................................................................ 38 4.3. Connectors ................................................................................................................................. 39 4.4. Antenna connector TNC ............................................................................................................. 39 4.5. Separated Rx and TX antennas ................................................................................................. 40 4.6. Supply connector ........................................................................................................................ 41 4.7. Power and Control - cable plug .................................................................................................. 41 4.8. RJ-45F ........................................................................................................................................ 42 4.9. Serial connector ......................................................................................................................... 42 4.10. Serial connector ....................................................................................................................... 43 4.11. Reset ........................................................................................................................................ 43 4.12. GPS Connector SMA ............................................................................................................... 43 4.13. Indication LEDs ........................................................................................................................ 44 4.14. RipEX-HS ................................................................................................................................. 55 4.15. X5 adapter ETH/USB ............................................................................................................... 55 4.16. Demo case ............................................................................................................................... 56 4.17. Assembly dimensions with fan ................................................................................................. 57 4.18. L-bracket .................................................................................................................................. 57 4.19. Flat bracket ............................................................................................................................... 57 4.20. 19" Rack shelf .......................................................................................................................... 58 4.21. 19" Rack shelf – double ........................................................................................................... 58 4.22. Dummy load ............................................................................................................................. 58 5.1. Bench test .................................................................................................................................. 60 RipEX Radio modem & Router – © RACOM s.r.o. 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 ............................................................................................................................... 63 6.1. Flat lengthwise mounting to DIN rail – recommended ............................................................... 65 6.2. Flat widthwise mounting to DIN rail ............................................................................................ 65 6.3. Vertical widthwise mounting to DIN rail ...................................................................................... 66 6.4. Vertical lengthwise mounting to DIN rail ..................................................................................... 66 6.5. Flat mounting using Flat bracket ................................................................................................ 66 6.6. Rack shelf ................................................................................................................................... 67 6.7. Fan kit mounting ......................................................................................................................... 67 6.8. Fan kit using Alarm Output, recommended ................................................................................ 68 6.9. Fan kit, always on ....................................................................................................................... 68 6.10. 10–30 VDC Supplying .............................................................................................................. 69 7.1. Menu Header .............................................................................................................................. 70 7.2. Menu Status ............................................................................................................................... 71 7.3. Menu Settings ............................................................................................................................ 72 7.4. Menu Alarm management .......................................................................................................... 78 7.5. Menu Radio ................................................................................................................................ 82 7.6. Menu Ethernet ............................................................................................................................ 85 7.7. Menu COM ................................................................................................................................. 90 7.8. Menu Protocols COM ................................................................................................................. 92 7.9. Menu Routing ........................................................................................................................... 104 7.10. Menu Neighbours ................................................................................................................... 106 7.11. Menu Statistic ......................................................................................................................... 109 7.12. Menu Graphs .......................................................................................................................... 110 7.13. Menu Ping .............................................................................................................................. 112 7.14. Menu Monitoring ..................................................................................................................... 115 7.15. Monitoring ............................................................................................................................... 119 7.16. Menu SW feature keys ........................................................................................................... 120 7.17. Menu Maintenance Configuration .......................................................................................... 121 7.18. Menu Maintenance Firmware ................................................................................................. 121 7.19. Menu Maintenance Password ................................................................................................ 122 7.20. Menu Maintenance Configuration .......................................................................................... 122 List of Tables 4.1. Pin assignement ......................................................................................................................... 40 4.2. Ethernet to cable connector connections ................................................................................... 42 4.3. COM1,2 pin description .............................................................................................................. 42 4.4. USB pin description .................................................................................................................... 43 4.5. Key to LEDs ............................................................................................................................... 44 4.6. Technical parameters ................................................................................................................. 45 4.7. Recommended Cables ............................................................................................................... 48 4.8. CE 25 kHz .................................................................................................................................. 49 4.9. CE 12.5 kHz ............................................................................................................................... 50 4.10. CE 6.25 kHz ............................................................................................................................. 50 4.11. FCC 25 kHz .............................................................................................................................. 51 4.12. FCC 12.5 kHz ........................................................................................................................... 51 4.13. FCC 6.25 kHz ........................................................................................................................... 51 10.1. Minimum Safety Distance 160 MHz ....................................................................................... 126 10.2. Minimum Safety Distance 300–400 MHz ............................................................................... 128 © RACOM s.r.o. – RipEX Radio modem & Router 6 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. 1: RipEX radio router RipEX access defaults: IP 192.168.169.169/24, username: admin, password: admin Set a static IP 192.168.169.x/24 on your PC, power on the RipEX and wait approximately 25 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. When accessing RipEX for the first time, you have to accept the https security certificate issued by Racom. Before attempting to do any configuration, make sure your RipEX is the only powered-up unit around. Since all units coming from factory share the same default settings ex factory, you could be accessing a different unit over the air without being aware of it. When accessing over the optional “X5” USB/ETH adapter, your PC will get its IP settings from the builtin DHCP server and you have to type https://10.9.8.7 in your browser. Remaining steps are the same and you do not need to worry about other RipEX's, you will be connected to the local unit in all cases. SCADA radio network step-by-step Building a reliable radio network for a SCADA system may not be that simple, even when you use such a versatile and easy-to-operate device as the RipEX radio modem. The following step-by-step checklist can help you to keep this process fast and efficient. 1. 2. 3. 4. 5. 6. Design your network to ensure RF signal levels meet system requirements. 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”). Install individual sites 1. Mount RipEX into cabinet (Section 6.1, “Mounting”). http://www.racom.eu/eng/products/m/ripex/app/routing.html © RACOM s.r.o. – RipEX Radio modem & Router 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. Check routing by the ping tool (the section called “Ping”) to verify accessibility of all IP addresses with which the unit will communicate. 9. Connect the SCADA equipment Test your application RipEX Radio modem & Router – © RACOM s.r.o. RipEX – Radio router 1. RipEX – Radio router 1.1. Introduction RipEX is a best-in-class radio modem, not only in terms of data transfer speed. This Software Defined Radio with Linux OS has been designed with attention to detail, performance and quality. All relevant state-of-the-art concepts have been carefully implemented. RipEX provides 24×7 reliable service for mission-critical applications like SCADA & Telemetry for Utilities, SmartGrid power networks or transaction networks connecting lottery terminals, POS or ATM’s. Any unit can serve as the central master, repeater, remote terminal, or all of these simultaneously, with a configuration interface easily accessible from a web browser. Anybody with even basic knowledge of IP networking can set up a RipEX within a matter of minutes and maintain the network quite easily. 1.2. Key Features • Exceptional data speeds on the radio channel - 83 kbps / 25 kHz, 42 kbps / 12.5 kHz, 21 kbps / 6.25 kHz • 1× ETH, 2× COM, 1× USB, 5× virtual COM - Simultaneously on radio channel. COM1-RS232, COM2-RS232 or RS485, software configurable. Virtual COMs over ETH controlled by Terminal servers. USB for independent service access via USB/ETH adapter. • 135–175; 300–360; 368–470; 928–960 MHz - Licensed radio bands - Software-selectable channel spacing 25, 12.5 or 6.25 kHz • 10 watts - Transmission output control, nine stages from 0.1 to 10 W (max. 2 W for linear modulations). • Energy saving - Sleep mode – 0.1 W, controlled via a digital input. - Save mode – 2.3 W, wake up by receiving a packet from the radio channel • Extended temperature range −40 to +70 ºC • Easy to configure and maintain - Web interface, - Wizards, - On-line help, - Balloon tips, - Fastest web access to remote units • Bridge or Router - RipEX is a device with native IP support which can be set as a standard bridge or router. © RACOM s.r.o. – RipEX Radio modem & Router RipEX – Radio router • Modbus, IEC101, DNP3, Comli, RP570, C24, DF1, Profibus, Modbus TCP, IEC104, DNP3 TCP etc. - Unique implementation of industrial protocols enables a secure addressed transmission of all packets in all directions • Anti-collision protocol on radio channel - Allows multi polling & report-by-exception concurrently for several independent applications simultaneously • Optimization – 3× higher throughput - Optimization method which joins short packets, compresses data, optimises both the traffic to the link peer and the sharing of the radio channel capacity among the links. • Embedded diagnostic & NMS - Real time and historical (20 periods, e.g. days) statistics and graphs for the unit and its neighbours. - SNMP including generation of TRAP alarms when preset thresholds are exceeded - on-line/off-line (recorded to a file in the RipEX) monitoring of all interfaces • 256 AES encryption - The most secure encryption meets FIPS 140 2 requirements • Pay only for what you need - Software authorization keys allow you to add advanced features when needed (Router mode, 83 kbps, COM2, 10 W) - Free Master-key trial – (all coded features) for 30 days in every RipEX • Reliability - 3 years warranty, rugged die cast aluminium case, military or industrial components - Every single unit tested in a climatic chamber as well as in real traffic • RipEX - HS - Redundant hot standby chassis - Two hot-stand-by standard RipEX units inside - Automatic switchover capability on detection of failure - Suitable for Central sites, Repeaters or Important remote sites where no single point of failure is required • Internal calendar time - Can be set manually or synchronized via NTP (Network Time Protocol) - Any RipEX also runs as a NTP server automatically - NTP synchronization via Ethernet or over the Radio channel from another RipEX - Powered from internal long life Lithium Manganese battery, so it is accurate even when RipEX is powered off • Flash memory - All configuration parameters are saved in flash memory - Configuration and other parameters are safely saved even when RipEX is powered off 1.3. Standards Spectrum (art 3.2) ETSI EN 300 113-2 V1.5.1 FCC Part 90 EMC (art 3.1.b) 10 ETSI EN 301 489-1 V1.9.2 RipEX Radio modem & Router – © RACOM s.r.o. 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 Radio modem & Router 11 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. The master unit exchanges data with the currently connected remote radio, and when finished, it establishes a new connection with the next remote radio according to the polling order. • Report-by-exception In report-by-exception networks remote units can be contacted similarly to polling networks. In addition, any remote unit can spontaneously send data to the master unit (typically an alarm). • Mesh In mesh type networks any radio modem in the network can access any other radio modem randomly and spontaneously. Mesh network can also host polling or report-by-exception applications, even in several instances. 2.2. Bridge mode A packet received through any interface is broadcast to the appropriate interfaces of all units within the network. Packets received on COM are broadcast to both COM1 and COM2 at remote sites, allowing you to connect 2 RTU's to any radio modem. Any unit can be configured as a repeater. A repeater relays all packets it receives through the radio channel. The network implements safety mechanisms which prevent cyclic loops in the radio channel (e.g. when a repeater receives a packet from another repeater) or duplicate packets delivered to the user interface (e.g. when RipEX receives a packet directly and then from a repeater). Beside standard packet termination by an "Idle" period on the serial port (a pause between received bytes) the bridge mode also offers "streaming". While in streaming mode, transmission on the radio channel starts immediately, without waiting for the end of the received frame on COM => zero latency. The bridge mode is suitable for all polling applications. 2.2.1. Detailed Description Bridge mode is suitable for Point-to-Multipoint networks, where Master-Slave applications with pollingtype communication protocol are used. RipEX in bridge mode is as easy to use as a simple transparent device, while providing communication reliability and spectrum efficiency by employing a sophisticated protocol in the radio channel. In bridge mode, the radio channel protocol do not solve collisions. There is a CRC check of data integrity, however, i.e. once a message is delivered, it is 100% error free. 12 RipEX Radio modem & Router – © RACOM s.r.o. 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. This arrangement saves the precious RF spectrum from extra load which would be otherwise generated by local traffic in the LAN (the LAN to which the respective ETH interface is connected). COM1,COM2 - All frames received from COM1(2) are broadcast over the radio channel and transmitted to all COM's (COM1 as well as COM2) on all radio modems within the network, the other COM on the source RipEX excluding. There is a special parameter TX delay (Adv. Config., Device), which should be used when all substations (RTU's) reply to a broadcast query from the master station. In such case massive collisions would ensue because all substations (RTU's) would reply at nearly the same time. To prevent such collision, TX delay should be set individually in each slave RipEX. The length of responding frame, the length of radio protocol overhead, modulation rate have to be taken into account. 2.2.2. Functionality example In the following, common acronyms from SCADA systems are used: • • FEP - Front End Processor, designates the communication interface equipment in the centre RTU - Remote Telemetry Unit, the terminal SCADA equipment at remote sites The single digits in illustrations are “site names” and do not necessarily correspond with actual addresses of both the RipEX's and SCADA equipment. Address configuration examples are given in the next chapter. Step 1 Polling cycle starts: FEP sends a request packet for RTU3 through COM1 to the connected RipEX. Step 2 FEP’s RipEX broadcasts this packet on Radio channel. RipEX3 and RipEX1 receive this packet. RipEX2 doesn’t receive this packet, because it is not within radio coverage of FEP’s RipEX. © RACOM s.r.o. – RipEX Radio modem & Router 13 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. RipEX3 and FEP’s RipEX do not send the repeated packet to their COM ports, because it has already been sent (RipEX3) or received (FEP’s RipEX) on their COM (anti-duplication mechanism). RTU3 sends the reply packet. Step 5 RipEX3 broadcasts the reply packet from RTU3 on Radio channel. Packet is received by RipEX1 and FEP’s RipEX. Step 6 FEP’s RipEX sends the packet (the reply from RTU3) to FEP through COM1. RipEX1 sends this packet to RTU1. RTU1 doesn’t react, because the packet is addressed to FEP. RipEX1 repeats the packet on Radio channel. All RipEXes receive the packet. Step 7 RipEX2 sends repeated packet to its COM1 and COM2. RTU2 doesn’t react, because the packet is addressed to FEP. RipEX3 and FEP’s RipEXes do not send the repeated packet to their COM ports, because it has been handled already. FEP processes the reply from RTU3 and polling cycle continues… 14 RipEX Radio modem & Router – © RACOM s.r.o. 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. Moreover, leaving all RipEX's with the same (= default) IP on the ETH interface may cause serious problems, when more RipEX's are connected to the samX5e LAN, even if by accident (e.g. during maintenance). 192.168.5.13/24 192.168.5.3/24 192.168.5.12/24 192.168.5.2/24 192.168.5.51/24 192.168.5.50/24 50 REPEATER FEP 192.168.5.11/24 192.168.5.1/24 Fig. 2.1: Bridge mode example Repeater Because using the bridge mode makes the network transparent, the use of repeaters has certain limitations. To keep matters simple we recommend using a single repeater. However, if certain rules are observed, using multiple repeaters in the same network is possible. The total number of repeaters in the network is configured for every unit individually under Bridge mode parameters. This information is contained in every packet sent. All units that receive such packet will resume transmission only after sufficient time has been allowed for the packet to be repeated. The packets received from user ports remain buffered and are sent after the appropriate time passes. This prevents collisions between remote radio modems. There can be no repeater collisions if only one repeater is used. © RACOM s.r.o. – RipEX Radio modem & Router 15 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. Repeaters connected serially Centre A packet is transmitted and repeated in steps 1, 2, 3. RPT1 RPT2 Remote WRONG COLLISION! CEN RPT1 RPT2 REM GOOD CEN RPT1 RPT2 REM In improperly designed networks collisions happen if a remote radio modem lies in the range of two repeaters (see the image): the packet sent from the centre (1) is received by both repeaters. It is repeated by them both (2) causing a collision at the remote. In other words – there should not be more than one repeater where the centre and remotes' coverage areas overlap. Solution 1. Adjust signal coverage so that RPT2 is out of range of the centre and RPT1 is out of the range of the remote radio modem. This can be achieved for example by reducing the output power or using a unidirectional antenna. Coverage area Solution 2. Use a single repeater. (Whenever network layout allows that.) Good CEN 16 RPT1 REM RipEX Radio modem & Router – © RACOM s.r.o. RipEX in detail 2. Parallel repeaters Remote2 REM2 Repeater2 Improperly designed network: WRONG CEN RPT2 Centre RPT1 REM1 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. COLLISION! Remote1 GOOD REM2 Well-designed network: RPT2 CEN RPT1 REM1 - A remote is only in the range of a single repeater (REM1-RPT1, REM2-RPT2). There is always only one repeater where the centre and remote coverage areas overlap. 2.3. Router mode RipEX works as a standard IP router with two interfaces (radio and ethernet) and two COM port devices. There is a sophisticated anti-collision protocol on the radio channel, which checks and verifies every single packet. Being an IP router, each unit can simultaneously work as a store-and-forward repeater and deliver packets to the connected equipment. The router mode is suitable for all uses. In contrast to the bridge mode, a packet reception is confirmed over the radio channel even in very simple polling type applications, and if necessary the packet is retransmitted. 2.3.1. Detailed Description Router mode is suitable for multipoint networks, where multi-master applications with any combination of polling and/or spontaneous data protocols can be used. The proprietary link-layer protocol on the radio channel is very sophisticated, it can transmit both unicast and broadcast frames, it has collision avoidance capability, it uses frame acknowledgement, retransmissions and CRC checks to guarantee data delivery and integrity even under harsh interference conditions on the radio channel. RipEX works as a standard IP router with 2 independent interfaces: radio and ETH. Each interface has its own MAC address, IP address and mask. IP packets are processed according the routing table rules. You can also set the router’s default gateway (applies to both interfaces) in the routing table. The COM ports are treated as standard host devices, messages can be delivered to them as UDP datagrams to selected port numbers. The destination IP address of a COM port is either the IP of ETH or the IP of a radio interface. The source IP address of outgoing packets from COM ports is always the IP of the ETH interface. © RACOM s.r.o. – RipEX Radio modem & Router 17 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. Simultaneously PLC2 sends a packet for PLC1 to RipEX2 through COM1. Step 2 FEP’s RipEX transmits an addressed packet for RTU1 on Radio channel. RipEX1 receives this packet, checks data integrity and transmits the acknowledgement. At the same time packet is sent to RTU1 through COM2. RipEX3 receives this packet too. It doesn’t react, because this packet is directed to RipEX1 only. Step 3 RipEX2 waits till previous transaction on Radio channel is finished (anti-collision mechanism). Then RipEX2 transmits on Radio channel the addressed packet for PLC1. RipEX1 receives this packet, checks data integrity and transmits acknowledgement. At the same time packet is sent to PLC1 through COM1. Simultaneously the reply packet from RTU1 for FEP is received on COM2. Step 4 RipEX1 transmitts the reply packet from RTU1 for FEP on Radio channel. All RipEXes receive this packet. This packet is addressed to FEP’s RipEX, so only FEP’s RipEX reacts. It checks data integrity and transmits the acknowledgement to RipEX1. At the same time the packet is sent to FEP through COM2. 18 RipEX Radio modem & Router – © RACOM s.r.o. 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.. Everything what is needed is the proper configuration of routing tables. Radio IP addresses of the RipEX’s required to communicate over the radio channel must share the same IP network. We recommend planning your IP network so that every RipEX is connected to a separate sub-network over the ethernet port. This helps to keep the routing tables clear and simple. Note Even if the IP addresses of all RipEXes in a radio channel share a single IP network, they may not be communicating directly as in a common IP network. Only the RipEXes that are within the radio range of each other can communicate directly. When communication with radio IP addresses is required, routing tables must include even the routes that are within the same network (over repeaters), which is different from common IP networks. The example configuration below does not show such routing rules for the sake of simplicity (they are not needed in most cases). © RACOM s.r.o. – RipEX Radio modem & Router 19 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 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 192.168.2.2/24 ETH IP 192.168.50.1/24 FEP IP 192.168.50.2/24 50 Routing table RipEX1: 192.168.2.0/24 è 10.10.10.2 192.168.50.0/24 è 10.10.10.50 192.168.3.0/24 è 10.10.10.50 10.10.10.1/24 FEP 192.168.1.1/24 192.168.1.2/24 Fig. 2.2: Addressing Formal consistency between the last byte of the radio IP address and the penultimate byte of the ethernet address is not necessary but simplifies orientation. The “Addressing” image shows a routing table next to every RipEX. The routing table defines the next gateway for each IP destination. In radio transmission, the radio IP of the next radio-connected RipEX serves as the gateway. Example of a route from FEP (RipEX 50) to RTU 2: • • • • • • • • 20 The destination address is 192.168.2.2 The routing table of the RipEX 50 contains this record: Destination 192.168.2.0/24 Gateway 10.10.10.1 Based on this record, all packets with addresses in the range from 192.168.2.1 to 192.168.2.254 are routed to 10.10.10.1 Because RipEX 50’s radio IP is 10.10.10.50/24, the router can tell that the IP 10.10.10.1 belongs to the radio channel and sends the packet to that address over the radio channel The packet is received by RipEX 1 with the address 10.10.10.1 where it enters the router The routing table of RipEX 1 contains the record: Destination 192.168.2.0/24 Gateway 10.10.10.2 based on which the packet is routed to 10.10.10.2 over the radio channel The packet is received by RipEX 2 The router compares the destination IP 192.168.2.2 with its own ethernet address 192.168.2.1/24 and determines that the packet’s destination is within its ETH network and sends the packet over the ethernet interface – eventually, the packet is received by RTU 2. RipEX Radio modem & Router – © RACOM s.r.o. 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. More specifically, every group of IP addresses of devices (both RipEX's and SCADA), which is accessed via a repeater, should fall in a range which can be defined by a mask and no address defined by that mask exists in different part of the network. A typical network consisting of a single centre and number of remotes has got a tree-like layout, which can be easily followed by the addressing scheme – see the example in the Figure Optimised addressing below. Routing table RipEX4: 192.168.0.0/16 è 10.10.10.50 10.10.10.4/24 192.168.4.1/24 Routing table RipEX2: 192.168.0.0/16 è 10.10.10.1 192.168.4.2/24 Radio IP 10.10.10.50/24 10.10.10.2/24 Routing table RipEX50: 192.168.0.0/22 è 10.10.10.1 192.168.4.0/22 è 10.10.10.4 Default GW 192.168.50.2 192.168.2.1/24 192.168.2.2/24 ETH IP 192.168.50.1/24 FEP IP 192.168.50.2/24 50 10.10.10.1/24 Routing table RipEX1: 192.168.2.0/24 è 10.10.10.2 192.168.0.0/16 è 10.10.10.50 FEP 192.168.1.1/24 192.168.1.2/24 Fig. 2.3: Optimised addressing The default gateway is also a very powerful routing tool, however be very careful whenever the default route would go to the radio interface, i.e. to the radio channel. If a packet to non-existing IP destination came to the router, it would be transmitted over the radio channel. Such packets increase the load of the network at least, cause excessive collisions, may end-up looping etc. Consequently the default route should always lead to the ETH interface, unless you are perfectly certain that a packet to nonexisting destination IP may never appear (remember you are dealing with complex software written and configured by humans). © RACOM s.r.o. – RipEX Radio modem & Router 21 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. Polled remote units respond to the unit that contacted them (multi master network possible) using secure packets. When needed, RTU-RTU parallel communication is also possible. 2.4.1. Detailed Description Each SCADA protocol, such as Modbus, DNP3, IEC101, DF1, etc., has its own unique message format, and more importantly, its unique way of addressing remote units. The basic task for protocol utility is to check whether a received frame is in the correct protocol format and uncorrupted. Most of the SCADA protocols use some type of error detection codes (Checksum, CRC, LRC, BCC, etc.) for data integrity control, so RipEX calculates this code and check it with the received one. RipEX radio network works in IP environment, so the basic task for the protocol interface utility is to convert SCADA serial packets to UDP datagrams. Address translation settings are used to define the destination IP address and UDP port. Then these UDP datagrams are sent to RipEX router, processed and typically forwarded as unicasts over the radio channel to their destination. If the gateway defined in the routing table belongs to the ethernet LAN, UDP datagrams are rather forwarded to the ethernet interface. After reaching the gateway (typically a RipEX router), the datagram is again forwarded according to the routing table. Above that, RipEX is can to handle even broadcast packets from serial SCADA protocols. When broadcasts are enabled in the respective Protocol settings, the defined packets are treated as broadcast (e.g. they are not acknowledged on Radio channel). On the Repeater station, it is possible to set whether broadcast packets shall be repeated or not. Note: UDP datagrams can be acknowledged on the radio channel (ACK parameter of router mode) but they are not acknowledged on the ethernet channel. When a UDP datagram reaches its final IP destination, it should be in a RipEX router again (either its ETH or radio interface). It is processed further according its UDP port. Either it is delivered to COM1(2) port daemon, where the datagram is decapsulated and the data received on serial interface of the source unit is forwarded to COM1(2), or the UDP port is that of a Terminal server or any other special protocol daemon on Ethernet like Modbus TCP etc. Then the datagram is processed by that daemon accordingly to the respective settings. RipEX uses a unique, sophisticated protocol on the radio channel. It guaranties data integrity even under heavy interference or weak signal conditions due to the 32 bit CRC used, minimises the likelihood of a collision and retransmits frames when collision happens, etc. These features allow for the most efficient SCADA application arrangements to be used, e.g. multi-master polling and/or spontaneous communication from remote units and/or parallel communication between remote units, etc. Note: The anti-collision protocol feature is available only in the router mode. The bridge mode is suitable for simple Master-Slave arrangements with polling-type application protocol. 22 RipEX Radio modem & Router – © RACOM s.r.o. 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. If the data structure of a packet is identical for IP and serial protocols, the terminal server can serve as a converter between TCP(UDP)/IP and serial protocols (RS232, RS485). RipEX also provides a built-in converter Modus RTU – Modus TCP, where data structure is not the same, so one application may combine both protocols, Modus RTU and Modus TCP. 2.5.1. Detailed Description Generally, a terminal server (also referred to as serial server) enables connection of devices with a serial interface to a RipEX over the local area network (LAN). It is a virtual substitute for the devices used as serial-to-TCP(UDP) converters. Examples of the use: A SCADA application in the centre should be connected to the radio network via serial interface, however, for some reason that serial interface is not used. The operating system (e.g. Windows) can provide a virtual serial interface to such application and converts the serial data to TCP (UDP) datagrams, which are then received by the terminal server in RipEX. This type of connection between RipEX and application provides best results when: • • • There is no hardware serial interface on the computer Serial cable between RipEX and computer would be too long. E.g. the RipEX is installed very close to the antenna to reduce feed line loss. LAN already exists between the computer and the point of installation Note: The TCP (UDP) session operates only locally between RipEX and the central computer, hence it does not increase the load on the radio channel. In special cases, the terminal server can reduce network load from TCP applications . A TCP session can be terminated locally at the terminal server in RipEX, user data extracted from the TCP messages and processed as if it came from a COM port. When the data reaches the destination RipEX, it can be transferred to the RTU either via the serial interface or via TCP (UDP), using the terminal server again. Please note, that RipEX Terminal server implementation also supports the dynamical IP port change in every incoming application datagram. In such case the RipEX sends the reply to the port from which the last response has been received. This feature allows to extend the number of simultaneously opened TCP connections between the RipEX and the locally connected application up to 10 on each Terminal server. 2.6. Diagnostics & network management RipEX radiomodem offers a wide range of built-in diagnostics and network management tools. © RACOM s.r.o. – RipEX Radio modem & Router 23 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). Every RipEX on the network regularly broadcasts its status, the set of so called “Watched values”: the probability of packet loss when transmitting data over the radio channel, current supply voltage, internal temperature, measured RF output power, the Voltage Standing Wave Ratio on the antenna feed line and the total number of packets received from / transmitted to ETH, COM1, COM2 interfaces. In addition, the RipEX that records this data in its log also keeps track of how many times it listened to its neighbouring unit as well as of the RSS and DQ recorded. See Adv. Conf., Diagnostic for more. Statistic The ‘Statistic’ log provides information about the volume of data traffic on all interfaces: radio, ETH, COM1, COM2. It offers detailed information about the number of transmitted packets, their size and the throughput per second. Moreover, a detailed division into user and service packets is available for the radio channel. See chapter Adv. Conf., Diagnostic for more. 2.6.2. Graphs An independent database periodically stores the Watched values (see 'Neighbours' log above) from up to five neighbouring RipEX's and from the local one, there including most important values from the Statistic log. All these values can be displayed as graphs. The graphs are available in summary and detailed versions. Detailed logging is triggered on when a threshold value has been reached for the specific item to enable a more detailed investigation into the units’ operation when an alarm event occurs. Each graph can display two different elements at once, including their set thresholds. Each of the values may originate from a different RipEX unit. See chapter Adv. Conf., Graphs for more. 2.6.3. SNMP RipEX implements an SNMP client ver. 1. The values provided by RipEX are shown in the MIB table. RipEX also allows generating SNMP traps when thresholds have been reached for the monitored values: RSScom, DQcom, TXLost[%], Ucc, Temp, PWR, VSWR, ETH[Rx/Tx], COM1[Rx/Tx], COM2[Rx/Tx], HW Alarm Input. See chapter RipEX App notes, SNMP for RACOM RipEX for more. 2.6.4. Ping To diagnose the individual radio links RipEX is equipped with an enhanced Ping tool. In addition to the standard info such as the number of sent and received packets or the round trip time, it provides the http://www.racom.eu/eng/products/m/ripex/app/snmp.html 24 RipEX Radio modem & Router – © RACOM s.r.o. 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.g. Terminal servers, Modus 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. RipEX Rx Rx Rx COM1 Tx COM PORTS MODULE Rx Tx Tx ROUTER BRIDGE MODULE COM2 Tx Rx RADIO CHANNEL MODULE RADIO Tx Rx ETH Tx Tx Rx virtual com eth TERMINAL & MODBUS TCP SERVERS Fig. 2.4: Monitoring See chapter Adv. Conf., Monitoring for details. 2.7. Firmware update and upgrade Certain advanced RipEX features are activated with software keys. SW feature keys enable the users to initially purchase only the functionality they require and buy additional functions as the requirements and expectations grow. Similarly, when some features (e.g. COM2) are required on certain sites, the corresponding key can be activated only where needed. • Keys protect the investment into hardware. Thanks to SDR-based hardware design of RipEX no physical replacement is necessary – the user simply buys a key and activates the feature. • For evaluation and testing, Time-limited keys can be supplied. These keys activate the coded feature for a limited operational (power on) time only. Free Master-key trial for 30 days is in every RipEX. Software keys are always tied to a specific RipEX production code. A list of possible SW feature keys and their functionalities is given below: ROUTER – enables Operating mode Router. If not activated, only Bridge mode is available © RACOM s.r.o. – RipEX Radio modem & Router 25 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. SW feature keys enable the users to initially purchase only the functionality they require and buy additional functions as the requirements and expectations grow. Similarly, when some features (e.g. COM2) are required on certain sites, the corresponding key can be activated only where needed. • Keys protect the investment into hardware. Thanks to SDR-based hardware design of RipEX no physical replacement is necessary – the user simply buys a key and activates the feature. • For evaluation and testing, Time-limited keys can be supplied. These keys activate the coded feature for a limited operational (power on) time only. Free Master-key trial for 30 days is in every RipEX. Software keys are always tied to a specific RipEX production code. A list of possible SW feature keys and their functionalities is given below: See chapter Adv. Conf., SW feature keys for more. 26 RipEX Radio modem & Router – © RACOM s.r.o. Network planning 3. Network planning The significance of planning for even a small radio network is often neglected. A typical scenario in such cases goes as follows – there's not enough time (sometimes money) to do proper planning, so the network construction is started right away while decisions on antennas etc. are based mainly on budget restrictions. When the deadline comes, the network is ready but its performance does not meet the expectations. Finally the (expensive) experts are invited to fix the problem and that fix costs ten times more than a proper design process done beforehand would have. The following paragraphs are not a guide to network planning – that is a topic far beyond the scope of a product manual. What is provided is the essential RipEX data needed plus some comments on common problems which should be addressed during the planning process. 3.1. Data throughput, response time A UHF radio network provides very limited bandwidth for principal reasons. Hence the first and very important step to be taken is estimating/calculating the capacity of the planned network. The goal is to meet the application bandwidth and time-related requirements. Often this step determines the layout of the network, for example when high speed is necessary, only near-LOS (Line-of-sight) radio hops can be used. RipEX offers an unprecedented range of data rates. The channel width available and signal levels expected/measured on individual hops limit the maximum rate which can be used. The data rate defines the total capacity of one radio channel in one area of coverage, which is shared by all the radio modems within the area. Then several overhead factors, which reduce the total capacity to 25-90% of the "raw" value, have to be considered. They are e.g. RF protocol headers, FEC, channel access procedures and number of store-and-forward repeaters. There is one positive factor left – an optimum compression (e.g. IP optimization) can increase the capacity by 20-200%. All these factors are heavily influenced by the way the application loads the network. For example, a simple polling-type application results in very long alarm delivery times – an event at a remote is reported only when the respective unit is polled. However the total channel capacity available can be 60-95% of the raw value, since there are no collisions. A report-by-exception type of load yields much better application performance, yet the total channel capacity is reduced to 25-35% because of the protocol overhead needed to avoid and solve collisions. The basic calculations of network throughput and response times for different RipEX settings can be done at www.racom.eu . Let us add one comment based on experience. Before committing to the actual network design, it is very wise to do a thorough bench-test with real application equipment and carefully monitor the load generated. A difference against the datasheets, which may be negligible in a LAN environment, may have fundamental consequences for the radio network design. To face that "small" difference when the network is about to be commissioned may be a very expensive experience. The bench test layout should include the application centre, two remotes (at least) and the use of a repeater. See the following picture for an example. http://www.racom.eu/eng/products/radio-modem-ripex.html#calculation © RACOM s.r.o. – RipEX Radio modem & Router 27 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. The only frequency of the set of options which can possibly make it to a distant valley, 20 km from your nearest point-of-presence, it can reach a ship 100 km from the shore base. The penalty you pay is tremendous – high level of noise in urban and industry areas, omnipresent multi-path propagation, vulnerability to numerous special propagation effects in troposphere etc. Consequently this frequency band is suitable for low speeds using robust modulation techniques only, and even then a somewhat lower long-term communication reliability has to be acceptable for the application. 450 MHz The most popular of UHF frequency bands. It still can get you slightly “beyond the horizon”, while the signal stability is good enough for 99% (or better) level of reliability. Multi-path propagation can be a problem, hence high speeds may be limited to near-LOS conditions. Urban and industrial noise does not pose a serious threat (normally), but rather the interference caused by other transmissions is quite frequent source of disturbances. 350 MHz Put simply, character of this band is somewhere between 160 and 450 MHz. 900 MHz This band requires planning the network in “microwave” style. Hops longer than about 1 km have to have “almost” clear LOS (Line-of-sight). Of course a 2–5 km link can handle one high building or a 28 RipEX Radio modem & Router – © RACOM s.r.o. 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. Otherwise, if network capacity is your main problem, then 900 MHz allows you to build the fastest and most reliable links. The price you pay (compared to lower frequency bands) is really the price – more repeaters and higher towers increase the initial cost. Long term reliable performance is the reward. The three frequency bands discussed illustrate the simple basic rules – the higher the frequency, the closer to LOS the signal has to travel. That limits the distance over the Earth's surface – there is no other fundamental reason why shorter wavelengths could not be used for long distance communication. On the other hand, the higher the frequency, the more reliable the radio link is. The conclusion is then very simple – use the highest frequency band you can. 3.3. Signal budget For every radio hop which may be used in the network, the signal level at the respective receiver input has to be calculated and assessed against requirements. The fundamental requirements are two – the data rate, which is dictated by total throughput and response times required by the application, and the availability, which is again derived from the required reliability of the application. The data rate translates to receiver sensitivity and the availability (e.g. 99,9 % percent of time) results in size of the fade margin. The basic rule of signal budget says, that the difference between the signal level at the receiver input and the guaranteed receiver sensitivity for the given data rate has to be greater than the fade margin required: RX signal [dBm] – RX sensitivity [dBm] >= Fade margin [dB] To calculate the RX signal level, we follow the RF signal path: TX output TX feed line antenna loss gain RX feed line antenna loss gain path loss RX input Fig. 3.2: Signal path RX signal [dBm] = + TX output [dBm] example: +30.0 dBm (TX output 1 W) - TX antenna feeder loss [dB] -2.5 dB (20m cable RG-213 U, 400 MHz) +TX antenna gain [dBi] +2.1 dBi (half-wave dipole, 0 dBd) - Path loss [dB] + RX antenna gain [dBi] © RACOM s.r.o. – RipEX Radio modem & Router -125.0 dB calculated from field measurement) +9.7 dB (7-al Yagi antenna, 7.6 dBd) 29 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. Note that antenna gains against isotropic radiator (dBi) are used in the calculation. The figures of feeder cable loss per meter should be also known. Note that coaxial cable parameters may change considerably with time, especially when exposed to an outdoor environment. It is recommended to add a 50-100 % margin for ageing to the calculated feeder loss. 3.3.1. Path loss and fade margin The path loss is the key element in the signal budget. Not only does it form the bulk of the total loss, the time variations of path loss are the reason why a fade margin has to be added. In reality, very often the fade margin is the single technical figure which expresses the trade-off between cost and performance of the network. The decision to incorporate a particular long radio hop in a network, despite that its fade margin indicates 90 % availability at best, is sometimes dictated by the lack of investment in a higher tower or another repeater. Note that RipEXs Auto-speed feature allows the use of a lower data rate over specific hops in the network, without the need to reduce the rate and consequently the throughput in the whole network. Lower data rate means lower (= better) value of receiver sensitivity, hence the fade margin of the respective hop improves. See the respective Application note to learn more on the Auto-speed feature. When the signal path profile allows for LOS between the TX and RX antennas, the standard formula for free-space signal loss (below) gives reliable results: Path loss [dB] = 20 * log10 (distance [km]) + 20 * log10 (frequency [MHz]) + 32.5 In the real world the path loss is always greater. UHF radio waves can penetrate obstacles (buildings, vegetation), can be reflected from flat objects, can bend over round objects, can disperse behind sharp edges – there are numerous ways how a radio signal can propagate in non-LOS conditions. The additional loss when these propagation modes are involved (mostly combined) is very difficult to calculate. There are sophisticated methods used in RF design software tools which can calculate the path loss and its variations (statistical properties) over a computer model of terrain. Their accuracy is unfortunately very limited. The more obstacles on the path, the less reliable is the result. Such a tool can be very useful in the initial phase of network planning, e.g. to do the first network layout for the estimate of total throughput, however field measurements of every non-LOS radio hop should be done before the final network layout is designed. Determining the fade margin value is even more difficult. Nevertheless the software tools mentioned can give some guidance, since they can calculate the statistical properties of the signal. Generally the fade margin (for given availability) is proportional to the difference between the real path loss and the LOS path loss over the same distance. Then it is about inversely proportional to frequency (in the UHF range at least). To give an example for 10 km, non-LOS, hop on 450 MHz, fade margin of 20 dB is a bare minimum. A field test may help again, provided it is run for longer period of time (hours-days). RipEX diagnostic tools (ping) report the mean deviation of the RSS, which is a good indication of the signal stability. A multiple of the mean deviation should be added to the fade margin. 30 RipEX Radio modem & Router – © RACOM s.r.o. 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.3: Multipath propagation What makes things worse is that the path length changes over time. Since half the wavelength – e.g. 0.3 m at 450 MHz - makes all the difference between summation and cancellation, a 0.001% change of a path length (10 cm per 10 km) is often significant. And a small change of air temperature gradient can do that. Well, that is why we have to have a proper fade margin. Now, what makes things really bad is that the path length depends also on frequency. Normally this dependency is negligible within the narrow channel. Unfortunately, because of the phase combinations of multiple waveforms, the resulting signal may get so distorted, that even the sophisticated demodulating techniques cannot read the original data. That is the situation known to RF data network engineers – signal is strong enough and yet “it” does not work. That is why RipEX reports the, somewhat mystic, figure of DQ (Data Quality) alongside the RSS. The software demodulator uses its own metrics to assess the level of distortion of the incoming signal and produces a single number in one-byte range (0–255), which is proportionate to the “quality” of the signal. Though it is very useful information, it has some limitations. First, it is almost impossible to determine signal quality from a single packet, especially a very short one. That results in quite a jitter of DQ values when watching individual packets. However when DQ keeps jumping up and down it indicates a serious multipath problem. In fact, when DQ stays low all the time, it must be noise or permanent interference behind the problem. The second issue arises from the wide variety of modulation and data rates RipEX supports. Though every attempt has been made to keep the DQ values modulation independent, the differences are inevitable. In other words, experience is necessary to make any conclusions from DQ reading. The less experience you have, the more data you have to collect on the examined link and use other links for comparison. The DQ value is about proportional to BER (bit error ratio) and about independent of the data rate and modulation used. Hence some rule-of-thumb values can be given. Values below 100 mean the link is unusable. For a value of 125, short packets should get through with some retransmissions, 150–200 means occasional problems will exist (long term testing/evaluation of such link is recommended) and values above 200 should ensure reliable communication. © RACOM s.r.o. – RipEX Radio modem & Router 31 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. a dipole placed at the right spot yields a better RSS than a long Yagi, or rotating the directional antenna shows several peaks and troughs of the signal and no clear maximum RSS changes rapidly (say 10 dB) when antenna is moved by less than a meter in any direction ping test displays the mean deviation of RSS greater than 6 dB DQ value keeps "jumping" abnormally from frame to frame Quite often all the symptoms mentioned can be observed at a site simultaneously. The typical "beginner" mistake would be to chase the spot with the best RSS with an omnidirectional antenna and installing it there. Such a spot may work for several minutes (good luck), sometimes for several weeks (bad luck, since the network may be in full use by then). In fact, installing in such a spot guaranties that trouble will come - the peak is created by two or more signals added up, which means they will cancel out sooner or later. The right strategy is to find an arrangement where a single signal becomes dominant, possibly the most stable one. "Sweeping" a directional antenna around the place (in different heights and with different polarization) can tell us where the signals come from. If individual signals come from different directions, there is a good chance a long yagi can solve the problem by selecting just one of the bunch. Finding a spot where the unwanted signal is blocked by a local obstacle may help as well (e.g. installing at a side of the building instead of at the roof). multipath TX antenna better Fig. 3.4: Antenna location When the multiple signals come from about the same direction, a long yagi alone would not help much. We have to move away from the location, again looking for a place where just one of the signals becomes dominant. 20–50 metres may save the situation, changing the height (if possible) is often the right solution. Sometimes changing the height means going down, not up, e.g. to the base of the building or tower. We have to remember our hop has two ends, i.e. the solution may be to change antenna or its placement at the opposite end. If everything fails, it is better to use another site as a repeater. Even if such prob- 32 RipEX Radio modem & Router – © RACOM s.r.o. 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. Enigmatic cases of dropouts lasting couple of minutes every other day, over a clear LOS hops were created exactly like that. They look like interference which is very difficult to identify and , alas, they are caused by pure multipath propagation, a self-made one. So always use a combiner and another directional antenna if such arrangement is needed. Always. correctly combiner incorrectly Fig. 3.5: Main lobe 3.5. Network layout Certainly the network layout is mostly (sometimes completely) defined by the application. When the terrain allows for direct radio communication among all sites in the network, the designer can do neither too good nor too bad a job. Fortunately for RF network designers, the real world is seldom that simple. The conditions every single radio hop has to meet were discussed in previous paragraphs. If we are so lucky, that different layouts meeting that conditions are possible, we should exploit that for the benefit of the network. The following rules should be followed when defining the layout of radio hops: © RACOM s.r.o. – RipEX Radio modem & Router 33 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. First, a dominant site is exposed to interference from a large area; second, such site is typically crowded with radio equipment of all kinds, which keeps being added, moved (also failing to work properly), so local interference may appear anytime; third, it makes the majority of communication paths dependent on a single site, so one isolated failure may stop almost the entire network. • when total throughput is important, typically in report-by-exception networks, splitting the network into several independent or only slightly overlapping areas of coverage can help. The placement of repeaters which serve the respective areas is crucial. They should be isolated from each other whenever possible. incorrectly Repeater Centre Fig. 3.6: Dominant repeater Centre Fig. 3.7: Isolated branches 34 RipEX Radio modem & Router – © RACOM s.r.o. Network planning • in report-by-exception networks the load of hops connecting the centre to major repeaters forms the bottle-neck of total network capacity. Moving these hops to another channel, or, even better, to a wire (fibre, microwave) links can multiply the throughput of the network. It saves not only the load itself, it also significantly reduces the probability of collision. More on that in the following chapter 3.6.. 3.6. Hybrid networks If an extensive area needs to be covered and multiple retranslation would be uneconomical or unsuitable, RipEX’s can be interconnected via any IP network (WLAN, Internet, 3G, etc.). This is quite simple because RipEX is a standard IP router with an ethernet interface. Consequently interconnecting two or more RipEX's over a nested IP network is a standard routing issue and the concrete solution depends on that network. 3.7. Assorted practical comments Let us mention few issues, whose influence on network reliability or performance is sometimes neglected by less experienced planners: • Both vegetation and construction can grow. Especially when planning a high data rate hop which requires a near-LOS terrain profile, take into consideration the possible future growth of obstacles. • When the signal passes a considerable amount of vegetation (e.g. a 100m strip of forest), think of the season. Typically the path loss imposed by vegetation increases when the foliage gets dense or wet (late spring, rainy season). Hence the fade margin should be increased if your field measurements are done in a dry autumn month. The attenuation depends on the distance the signal must penetrate through the forest, and it increases with frequency. According to a CCIR, the attenuation is of the order of 0.05 dB/m at 200 MHz, 0.1 dB/m at 500 MHz, 0.2 dB/m at 1 GHz. At lower frequencies, the attenuation is somewhat lower for horizontal polarization than for vertical, but the difference disappears above about 1 GHz. • Though being a rare problem, moving metallic objects may cause serious disruptions, especially when they are close to one end of the radio hop. They may be cars on a highway, blades of a wind turbine, planes taking off from a nearby airport runway etc. • Even when the signal is very strong, be careful when considering various cheap whips or more generally any antennas requiring a ground plane to function properly. A tempting scenario is to use the body of the metallic box, where the radio modem and connected application equipment (often a computer) is installed, as the ground plane, which leads to never-ending problems with locally © RACOM s.r.o. – RipEX Radio modem & Router 35 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. Designing a 900 MHz site with 30 m long antenna cable run outdoors would certainly result in trouble two years later. • We recommend to use vertical polarization for all radio modem networks. 3.8. Recommended values To check individual radio link quality run Ping test with these settings: Ping type - RSS, Length [bytes] equal to the longest packets in the networks. Use Operating mode Bridge, when Router, ACK set to Off. Switch off all other traffic on the Radio channel used for testing. The test should run at least hours, preferrably day(s). The values below should guarantee a reliable radio link: • 36 Fade margin Min. 20 dB Fade margin [dB] = RSS (Received Signal Strenght) [dBm] – RX sensitivity [dBm]. Respective RX sensitivity for different data rates can be found in Section 4.4.1, “Detailed Radio parameters”. RipEX Radio modem & Router – © RACOM s.r.o. Network planning • DQ (Data Quality) Min. 180 • PER (Packet Error Rate) Max. 5 % © RACOM s.r.o. – RipEX Radio modem & Router 37 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 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. A model with two antenna connectors can be supplied to order, in which the Rx and Tx antennas are separate. See chapter Section 4.5, “Model offerings”. Fig. 4.4: Antenna connector TNC © RACOM s.r.o. – RipEX Radio modem & Router 39 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 electric wires with a cross section of 0.5 to 1.5 mm . Strip the wire leads to 6 mm (1/4 inch). Isolated cables should receive PKC 108 or less end sleeves before they are inserted in the clip. Insert the cables in the wire ports, tightening securely. Tab. 4.1: Pin assignement pin labeled signal SI SLEEP INPUT AI HW ALARM INPUT − −(GND) – for SLEEP IN, HW ALARM INPUT +(POWER) – for HW ALARM OUTPUT AO HW ALARM OUTPUT + 10–30VDC +POWER (10 to 30 V) − 10–30VDC −POWER (GND) Pins 3 and 7, 4 and 6 are connected internally. 40 RipEX Radio modem & Router – © RACOM s.r.o. 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. Disconnecting SLEEP INPUT from GND (-) ends the Sleep mode. Note that RipEX takes 25 seconds to wake up from the Sleep mode. Sleep Input Pin No.: 1 2 3 4 5 6 7 HW ALARM INPUT HWALARM INPUT is a digital input. If grounded (e.g. by connecting to PIN 3), an external alarm is triggered. This alarm can be used for example to transmit information using SNMP trap, informing for instance about a power outage or RTU problem. For details about Alarm management see chapter Advanced Configuration. HW ALARM OUTPUT HW ALARM OUTPUT is a digital output. It can be activated in Alarm management settings, chapter Advanced Configuration. It may be used for instance to switch on the Fan kit if the preset maximum internal temperature is exceeded or to inform the connected RTU about a RipEX alarm. If an alarm is triggered, HW ALARM OUTPUT is internally connected to GND. If the external device requires connection to positive terminal of the power supply, PIN 4 should be used. + A0 + 10–30VDC SI AI - Alarm Input SI AI - Pin No.: + A0 + 10–30VDC 1 2 3 4 5 6 7 Alarm Output max. 30 V DC, 1 A SI AI - Pin No.: + A0 + 10–30VDC 1 2 3 4 5 6 7 POWER The POWER pins labelled + and - serve to connect a power supply 10–30 VDC. The requirements for a power supply are defined in Section 6.6, “Power supply” and Section 4.4, “Technical specification”. © RACOM s.r.o. – RipEX Radio modem & Router 41 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.2: Ethernet to cable connector connections PIN Signal Direct cable Crossed cable TX+ orange – white green – white TX− orange RX+ green – white orange – white — blue blue — blue – white blue – white Rx− green orange — brown – white brown – white — brown green Fig. 4.8: RJ-45F brown 4.2.4. COM1 and COM2 RipEX provides two serial interfaces COM1 and COM2 terminated by DSUB9F connectors. COM1 is always RS232, COM2 can be configured as RS232 or RS485 (more in Adv. Conf., COM's). RipEX‘s RS232 is a hard-wired DCE (Data Communication Equipment) device. Equipment connected to the RipEX’s serial ports should be DTE (Data Terminal Equipment) and a straight-through cable should be used. If a DCE device is connected to the RipEX‘s serial ports, a null modem adapter or cross cable has to be used. Tab. 4.3: COM1,2 pin description DSUB9F COM1, 2 – RS232 COM2 – RS485 pin signal In/ Out signal In/ Out CD — RxD line B I/O TxD line A I/O DTR GND — GND DSR — RTS — CTS — — — — Fig. 4.9: Serial connector RipEX keeps pin 6 DSR at the level of 1 by RS232 standard permanently. 42 RipEX Radio modem & Router – © RACOM s.r.o. 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 +5 V red Data(−) white Data (+) green GND black 2 3 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”. The adapter is used for service access to RipEX’s web configuration interface. The USB connector also provides power supply (5 V/ 0.5 A). It can be used to temporarily power a connected device, for instance a telephone. The USB connector should not be used as permanent source of power supply. 4.2.6. Reset button RipEX’s bottom-side enclosure includes a reset button accessible through an opening. When this button is pressed, the STATUS diode on the LED panel goes dark (indicating that the button has been pressed). If you hold the button for 5 seconds, the STATUS diode starts flashing slowly indicating that the reset is complete. If you continue to hold the button for 15 or more seconds (the STATUS diode starts flashing quickly) and then release it, you will reset the device’s access information to default: parameters such as the login, password and ethernet IP will be reset to their defaults. Resetting access parameters to defaults also sets the Ethernet speed to Fig. 4.11: Reset „Auto“ and results in clearing all firewall rules (which may have been blocking the access by accident). Remember to re-install your firewall if you are using one. Note To reset the RipEX only use the RESET button as described above or use the button in RipEX’s web configuration, see Adv. Conf., Maintenance. Never use a power cycling (disconnecting and reconnecting power supply) to reset it. While power cycle resets, or rather reboots the RipEX, its software will not terminate correctly resulting in logs, statistics and graphs not being saved properly. 4.2.7. GPS RipEX can be equipped with an internal GPS, see Section 4.5, “Model offerings”. The GPS module is used for time synchronisation of the NTP server inside RipEX. See Adv. Conf., Time for more. In this case the front panel contains a SMA female 50 ohm connector for connecting the GPS antenna. Fig. 4.12: GPS Connector SMA © RACOM s.r.o. – RipEX Radio modem & Router 43 Product 4.3. Indication LEDs Tab. 4.5: Key to LEDs Color Description Green The RipEX OS (Linux) is running succesfuly Dark Reset button has been pressed STATUS Green flashes slowly TX Green flashes quickly default access after 15-seconds pressing the Reset button Red Status alarm Red transmitting to radio channel Green receiver is synchronised to a packet Yellow there is a signal stronger than −80 dBm on Radio channel Green data receiving Yellow data transmitting Green data receiving Yellow data transmitting Yellow ON 100 Mb/s speed Yellow OFF 10 Mb/s speed Green ON connected Green flashes ethernet data Green powered succesfuly RX COM2 COM1 ETH Fig. 4.13: Indication LEDs PWR Blinks with a period of 1 sec Save mode Flashes once per 3 sec 44 reset after five-seconds pressing the Reset button Sleep mode RipEX Radio modem & Router – © RACOM s.r.o. 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. 10 W 6.25 kHz 20.83 – 15.63 – 10.42 kbps 5.21 – 2.60 kbps max. 2 W max. 10 W 25 kHz 69.44 – 52.08 – 34.72 kbps 20.83 kbps max. 2 W max. 10 W 12.5 kHz 34.72 – 26.04 – 17.36 kbps 10.42 kbps max. 2 W max. 10 W 6.25 kHz 17.36 – 13.02 – 8.68 kbps 5.21 kbps max. 2 W max. 10 W RF Data rate – CE Detail RF Data rate – FCC Detail FEC (Forward Error Correction) On/Off, ¾ Trellis code with Viterbi soft-decoder Transmitter RF Output power (Both Carrier and Modulated) Linear: 0.5 - 1.0 - 2.0 W Exponencial(FM): 0.1 - 0.2 - 0.5 - 1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 10**W Duty cycle Continuous Rx to Tx Time < 1.5 ms Intermodulation Attenuation > 40 dB Spurious Emissions (Conducted) < −36 dBm Radiated Spurious Emissions < −36 dBm Adjacent channel power < −60 dBc Transient adjacent channel power < −60 dBc Receiver Sensitivity Detail Anti-aliasing Selectivity 50 kHz @ −3 dB BW Tx to Rx Time < 1.5 ms Maximum Receiver Input Power 20 dBm (100 mW) Rx Spurious Emissions (Conducted) < −57 dBm Radiated Spurious Emissions < −57 dBm Blocking or desensitization © RACOM s.r.o. – RipEX Radio modem & Router Detail 45 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.1 W Save mode 2W Interfaces Ethernet COM 1 COM 2 10/100 Base-T Auto MDI/MDIX RJ45 RS232 DB9F 300–115 200 bps RS232/RS485 SW configurable DB9F 300–115 200 bps USB USB 1.1 Host A Antenna 50 Ω TNC female LED panel 7× tri-color status LEDs Power, ETH, COM1, COM2, Rx, Tx, Status Enviromental IP Code (Ingress Protection) IP40 MTBF (Mean Time Between Failure) > 100 000 hours Operating temperature −40 to +70 °C (−40 to +158 °F) Operating humidity 5 to 95 % non-condensing Storage −40 to +85 °C (−40 to +185 °F) / 5 to 95 % non-condensing Mechanical Casing Rugged die-cast aluminium Dimensions 50 H × 150 W × 118 mm D (1.97× 5.9 × 4.65 in) Weight 1.1 kg (2.4 lbs) Mounting DIN rail, L-bracket, Flat-bracket, 19" Rack shelf SW 46 RipEX Radio modem & Router – © RACOM s.r.o. 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 32 Encryption AES256 Optimization up to 3× higher throughput Diagnostic and Management Radio link testing Yes (ping with RSS, Data Quality, Homogenity) Device – Ucc, Temp, PWR, VSWR, *HW Alarm Input. Watched values (Can be broadcast Radio channel – *RSScom, *DQcom, TXLost[%] to neighbouring units. Received info User interfaces – ETH[Rx/Tx], COM1[Rx/Tx], COM2[Rx/Tx] displayed in Neighbours table) * not broadcast Statistics For Rx/Tx Packets on User interfaces (ETH, COM1, COM2) and for User data and Radio protocol (Repeates, Lost, ACK etc.) on Radio channel Graphs For Watched values and Statistics History Graphs) (Statistics, Neighbours, 20 periods (configurable, e.g. days) SNMP SNMPv1, SNMPv2 Trap alarms generation for Watched values Monitoring Real time/Save to file analysis of all physical interfaces (RADIO, ETH, COM1, COM2) and some internal interfaces between software modules (e.g. Terminal servers, Modus TCP server etc.) Standards CE, FCC, RoHS Spectrum (art 3.2) ETSI EN 300 113-2 V1.5.1 FCC Part 90 EMC (electromagnetic compatibility) ETSI EN 301 489-1 V1.9.2 (art 3.1.b) ETSI EN 301 489-5 V1.3.1 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 © RACOM s.r.o. – RipEX Radio modem & Router 47 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. Today’s wireless communication arena tends to be overcrowded and a modern radio modem, which is demanded to compete with others in that environment, should have good dynamic range that is defined by the parameters listed above. Receiver of a radio modem, which is designed purely for optimum sensitivity, will not be able to give proper performance. However, the main receiver parameters determining its dynamic range go against each other and a clear trade-off between the sensitivity and the blocking is therefore an essential assumption. Then, from the viewpoint of a logical comparison, the consequence of better receiver sensitivity can be easily seen – a lower power level of the blocking and degradation parameters generally. Blocking or desensitization values were determined according to the standards EN 300 113-2 V1.5.1, resp. EN 300 113-1 V1.7.1 (channels 25 and 12.5 kHz) and ETSI 301 166-1 V1.3.2 (channel 6.25 kHz) respectively. Tab. 4.8: CE 25 kHz CE 25 kHz Classification kbps FEC Modulation Blocking or desensitization [dBm] Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 ±1 MHz ±5 MHz ±10 MHz 7.81 0.75 2CPFSK 13K8F1DCN -118 -115 -111 -8 -6 -5 10.42 1.00 2CPFSK 13K8F1DBN -117 -114 -110 -10 -8 -7 15.63 0.75 4CPFSK 14K2F1DDN -115 -112 -107 -9 -9 -7 20.83 1.00 4CPFSK 14K2F1DDN -113 -110 -104 -11 -11 -9 15.62 0.75 DPSK 24K0G1DCN -114 -112 -107 -6 -6 -5 20.83 1.00 DPSK 24K0G1DBN -113 -111 -106 -8 -8 -7 31.25 0.75 π/4-DQPSK 24K0G1DDN -113 -110 -106 -4 -4 -3 41.66 1.00 π/4-DQPSK 24K0G1DDN -111 -108 -104 -6 -6 -5 46.87 0.75 D8PSK 24K0G1DEN -106 -103 -98 -8 -8 -8 62.49 1.00 D8PSK 24K0G1DEN -104 -101 -95 -10 -10 -9.5 62.49 0.75 16DEQAM 24K0D1DEN -104 -101 -95 -6 -6 -5 83.32 1.00 16DEQAM 24K0D1DEN -102 -99 -93 -8 -8 -7 © RACOM s.r.o. – RipEX Radio modem & Router 49 Product Tab. 4.9: CE 12.5 kHz CE 12.5 kHz Classification kbps FEC Modulation Blocking or desensitization [dBm] Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 ±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.00 DPSK 11K9G1DBN -115 -113 -109 -6 -6 -5 15.62 0.75 π/4-DQPSK 11K9G1DDN -115 -113 -109 -3.5 -3 -2 20.83 1.00 π/4-DQPSK 11K9G1DDN -114 -111 -106 -4 -4 -3 23.44 0.75 D8PSK 11K9G1DEN -109 -106 -101 -6 -6 -5 31.25 1.00 D8PSK 11K9G1DEN -107 -104 -98 -8 -8 -7 31.25 0.75 16DEQAM 11K9D1DEN -107 -104 -99 -3 -3 -2 41.67 1.00 16DEQAM 11K9D1DEN -105 -102 -96 -5 -5 -4 Tab. 4.10: CE 6.25 kHz CE 6.25 kHz Classification kbps FEC Modulation Blocking or desensitization [dBm] Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 ±1 MHz ±5 MHz ±10 MHz 1.96 0.75 2CPFSK 3K00F1DCN -122 -120 -114 -0.5 +1.0 +5.5 2.61 1.00 2CPFSK 3K00F1DBN -121 -119 -113 -2.5 -1.0 +4.0 3.91 0.75 4CPFSK 3K00F1DDN -119 -116 -111 -1.5 -0.0 +5.0 5.21 1.00 4CPFSK 3K00F1DDN -117 -114 -108 -3.5 -1.5 +3.0 3.91 0.75 DPSK 6K0G1D -121 -118 -113 0.0 1.5 7.0 5.21 1.00 DPSK 6K0G1D -119 -117 -112 -2.0 -0.5 5.0 7.82 0.75 π/4-DQPSK 6K0G1D -117 -115 -112 +1.0 3.0 6.0 10.42 1.00 π/4-DQPSK 6K0G1D -116 -113 -110 -0.5 1.0 4.0 11.72 0.75 D8PSK 6K0G1D -111 -109 -104 -1.0 1.0 4.0 15.63 1.00 D8PSK 6K0G1D -111 -109 -104 -3.0 -1.0 2.0 15.63 0.75 16DEQAM 6K0D1D -110 -107 -103 -7.5 -2.0 1.5 20.83 1.00 16DEQAM 6K0D1D -107 -104 -99 -5.5 -3.5 0.0 50 RipEX Radio modem & Router – © RACOM s.r.o. Product Tab. 4.11: FCC 25 kHz FCC 25 kHz Classification kbps FEC Modulation Blocking or desensitization [dBm] Sensitivity [dBm] Emission -2 BER 10 -3 BER 10 -6 BER 10 ±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.75 D8PSK 19K8G1DEN -108 -105 -99 -9.0 -7.0 -5.5 52.08 1.00 D8PSK 19K8G1DEN -106 -103 -96 -11 -9.0 -7.5 52.08 0.75 16DEQAM 19K8D1DEN -106 -103 -96 -12 -9.0 -8.0 69.44 1.00 16DEQAM 19K8D1DEN -104 -101 -94 -14 -12 -10 Tab. 4.12: FCC 12.5 kHz FCC 12.5 kHz Classification Blocking or desensitization [dBm] Sensitivity [dBm] -2 BER 10 -3 BER 10 -6 kbps FEC Modulation Emission BER 10 ±1 MHz ±5 MHz ±10 MHz 7.81 0.75 4CPFSK 8K90F1D -117 -114 -108 -5 -5 -4 10.42 1.00 4CPFSK 8K90F1D -115 -112 -105 -7 -7 -6 13.02 0.75 π/4-DQPSK 10K0G1D -115 -113 -109 -2 -2 -2 17.36 1.00 π/4-DQPSK 10K0G1D -114 -111 -106 -4 -4 -3 19.53 0.75 D8PSK 10K0G1D -109 -106 -101 -6 -6 -5 26.04 1.00 D8PSK 10K0G1D -107 -104 -98 -8 -8 -7 26.04 0.75 16DEQAM 10K0D1D -107 -104 -99 -3 -3 -2 34.72 1.00 16DEQAM 10K0D1D -105 -102 -96 -5 -5 -4 Tab. 4.13: FCC 6.25 kHz FCC 6.25 kHz Classification Blocking or desensitization [dBm] Sensitivity [dBm] -2 BER 10 -3 Emission 3.91 0.75 4CPFSK 4K35F1D -120 -117 -112 -2 -2 -2 5.21 1.00 4CPFSK 4K35F1D -118 -115 -109 -4 -4 -3 6.51 0.75 π/4-DQPSK 5K00G1D -118 -116 -113 -3 -3 -2 8.68 1.00 π/4-DQPSK 5K00G1D -117 -114 -111 -5 -5 -4 9.77 0.75 D8PSK 5K00G1D -112 -110 -105 -2 -2 -2 13.02 1.00 D8PSK 5K00G1D -110 -107 -102 -4 -4 -3 13.02 0.75 16DEQAM 5K00D1D -110 -107 -103 -3 -3 -2 17.36 1.00 16DEQAM 5K00D1D -108 -105 -100 -5 -5 -4 © RACOM s.r.o. – RipEX Radio modem & Router BER 10 -6 kbps FEC Modulation BER 10 ±1 MHz ±5 MHz ±10 MHz 51 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. Ordering code (Part No’s) Trade name: RipEX Type (according to bands): RipEX-160, RipEX-300, RipEX-400, RipEX-900. Code (according to the tuned frequency and specific HW models): e.g. RipEX-368, RipEX-432DG etc. RipEX – XXXyyy XXX – base frequency 135 135–154 MHz 154 154–174 MHz 300 300–320 MHz 320 320–340 MHz 340 340–360 MHz 368 368–400 MHz 400 400–432 MHz 432 432–470 MHz yyy – HW models empty – basic model D – separate connectors for RX and TX antennas (Part No. RipEX-HW-DUAL) G – internal GPS module (Part No. RipEX-HW-GPS) Code examples: RipEX-368 = RipEX for frequencies from 368 to 400 MHz RipEX-400G = RipEX for frequencies from 400 to 432 MHz, with GPS module RipEX-432DG = RipEX for frequencies from 432 to 470 MHz, with separate Rx and Tx antenna connectors, with GPS module SW feature keys ROUTER – enables Operating mode Router. If not activated, only Bridge mode is available (Part No. RipEX-SW-ROUTER) 83 – enables two highest Data rates (Part No. RipEX-SW-83) COM2 – enables the second serial interface configurable as RS232 or RS485 (Part No. RipEXSW-COM2) 10W – enables RF output power 10 W for CPSK modulation (Part No. RipEX-SW-10W) MASTER – enables all functionalities of all possible SW feature keys (Part No. RipEX-SW-MASTER) Software keys are always tied to a specific RipEX Serial number (S/N). When SW key is ordered later and not together with RipEX unit, this S/N must be given. © RACOM s.r.o. – RipEX Radio modem & Router 53 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.2 Ah (for RipEX-HSB) Holders RipEX_F_BRACKET – Flat-bracket, for flat mounting RipEX_L_BRACKET – L-bracket, for vertical mounting 19‘ rack mounting RipEX_D_RACK_230 – 19" rack shelf double, incl. 2× PS 100–256 VAC / 24 VDC RipEX_D_RACK_48 – 19" rack shelf double, incl. 2× PS 48 VDC / 24 VDC RipEX_S_RACK_MS – 19" rack shelf single, incl. MS2000/12 + AKU 7.2 Ah RipEX_S_RACK_230 – 19" rack shelf single, incl. PS 100–256 VAC / 24 VDC RipEX_S_RACK_48 – 19" rack shelf single, incl. PS 48 VDC / 24 VDC Others RipEX_X5 – X5–ETH/USB adapter RipEX_DEMO_CASE – Demo case (without radio modems) RipEX_DUMMYLOAD – Dummy load antenna RipEX_FAN_KIT – Fan kit, for external cooling RipEX_C_NM_50 – Feedline cable, RG58, 50 cm, TNC Male – N Male OTH-HX090F/F – Coaxial overvoltage protection 0–1.5 GHz, N female/N female RipEX-HS – 19" Hot standby chassis, RipEX units excl., pow.supplies incl. (has got its own ordering codes, see RipEX-HS User manual) RipEX-HSB – 19" Battery pack chassis for RipEX-HS, batteries excl. 54 RipEX Radio modem & Router – © RACOM s.r.o. 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 For more information see RipEX-HS datasheet or User manual on www.racom.eu . 2. X5 – ETH/USB adapter ETH/USB adapter for service access to the web interface via USB connector. Includes a built-in DHCP server. To access the RipEX always use the fixed IP 10.9.8.7. For details on use see Section 5.3, “Connecting RipEX to a programming PC”. 3. Demo case A rugged plastic case for carrying up to three RipEX's and Fig. 4.15: X5 adapter ETH/USB 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 demostration of both radiomodems and the 3G router. During a field test, units can be powered from the backup battery and external antenna can be connected to one of the RipEX units through „N“ connector on the case. http://www.racom.eu © RACOM s.r.o. – RipEX Radio modem & Router 55 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. Fiamm 12FGH23 • 1× Power cable (European Schuko CEE 7/7 to IEC 320 C13) • 1× Ethernet patch cable (3 m, UTP CAT 5E, 2× RJ-45) • Quick start guide RipEX accessories: • 3× Dummy load antennas • 1× L-bracket, 1x Flat-bracket samples • 1× Fan kit • 1× X5 – ETH/USB adapter M!DGE accessories: • Whip antenna (900–2100 MHz, 2.2 dBi, vertical) • Outside dimensions: 455 × 365 × 185 mm • Weight approx. 4 kg (excluding the RipEx’s and M!DGE) 4. Fan kit External Fan kit for additional cooling in extreme temperatures. For connection see chapter Connectors. 56 RipEX Radio modem & Router – © RACOM s.r.o. 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.5 kg (without power supply and RipEX) • Can be assembled with power supply ○ 100 – 256 V AC / 24 V DC ○ 230 V AC / 24 V DC ○ 48 V DC / 24 V DC ○ MS2000/12 + back up battery 7.2 Ah © RACOM s.r.o. – RipEX Radio modem & Router 57 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. Feedline cable 58 RipEX Radio modem & Router – © RACOM s.r.o. 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. – RipEX Radio modem & Router 59 Bench test 5. Bench test 5.1. Connecting the hardware Before installing a RipEX network in the field, a bench-test should be performed in the lab. The RipEX Demo case is great for this as it contains everything necessary: 3 RipEX’s, Power supply, dummy load antennas, etc. If you use your own installation for lab tests, don’t forget: • A dummy load or an actual antenna with 50 ohm impedance should be connected to the RipEX • The minimum RF output must be set to avoid overloading the dummy antenna and to keep the received signal at reasonable level, between -40 and -80 dBm. • The power supplies must meet the requirements given in the specifications, Table 4.6, “Technical parameters”. Make sure the power supplies do not generate interference in the radio channel and that they can handle very fast changes in the load when RipEX switches from reception to transmission and back. 24 VDC Center 24 VDC RTU 24 VDC config. PC RTU Fig. 5.1: Bench test 5.2. Powering up your RipEX Switch on your power supply. LED PWR flashes quickly and after 8 seconds it switches to a green light. After approximately 30 seconds your RipEX will have booted and will be ready; the STATUS LED shines. You’ll find the description of the individual LED states in Section 4.3, “Indication LEDs”. 5.3. Connecting RipEX to a programming PC To configure a RipEX you can connect it to your PC in two ways: 60 RipEX Radio modem & Router – © RACOM s.r.o. 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. The RipEX’s IP address for access over the ETH/USB adapter is fixed: 10.9.8.7. Go to 3. Login to RipEX 2. PC connected directly to ETH port Set a static IP address in PC, example for Windows XP: Start > Settings > Network Connections > Local Area Connections Right Click > Properties > General select Internet Protocol (TCP/IP) > Properties > General IP address 192.168.169.250 - for RipEX in the default state Subnet mask 255.255.255.0 Default gateway leave empty OK (Internet Protocol Properties window) OK (Local Area Properties window) Some Operating systems may require you to reboot your PC. © RACOM s.r.o. – RipEX Radio modem & Router 61 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.7 – when connected via "X5" - external ETH/USB adapter to USB. IP address 10.9.8.7 is fixed and cannot be changed; it is independent of the IP address of the RipEX’s ethernet interface.) • 192.168.169.169 – when connected directly to ETH Note https - For security reasons the communication between the PC and RipEX is conducted using the protocol https with ssl encryption. The https protocol requires a security certificate. You must install this certificate into your web browser (Mozilla Firefox, Internet Explorer). The first time you connect to the RipEX, your computer will ask you for authorisation to import the certificate into your computer. The certificate is signed by the certification authority Racom s.r.o. It meets all security regulations and you need not be concerned about importing it into your computer. Confirm the import with all warnings and exceptions that your browser may display during installation. The login screen appears: 62 RipEX Radio modem & Router – © RACOM s.r.o. 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. IP address unknown If you don’t have the adapter or you have forgotten the password, you can reset the access parameters to defaults, see Section 4.2.6, “Reset button”. © RACOM s.r.o. – RipEX Radio modem & Router 63 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.3, “Configuration examples” as your models, or the RipEX-App. notes, Address planing . 5.5. Functional test To test radio communication between the RipEX’s you can use the Ping test, under Diagnostic/Ping menu. Setting up and the output of this test are described in chapter Adv. Conf., Tools. If the radio communication between RipEX’s is functional, you can proceed with a test of communication between the connected devices. You can monitor the status of configuration using the diodes on the LED panel, see Section 4.3, “Indication LEDs”. http://www.racom.eu/eng/products/m/ripex/app/routing.html 64 RipEX Radio modem & Router – © RACOM s.r.o. 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. Configure RipEX (Chapter 7, Advanced Configuration). 9. Test radio link quality (Section 5.5, “Functional test”). 10. Check routing by the ping tool (the section called “Ping”) to verify accessibility of all IP addresses with which the unit will communicate. 11. Connect the SCADA equipment. 12. Test your application. 6.1. Mounting 6.1.1. DIN rail mounting Radio modem RipEX is directly mounted using clips to the DIN rail. The mounting can be done lengthwise (recommended) or widthwise, in both cases with the RipEX lying flat. The choice is made by mounting the clips, one M4 screw per each. RipEX is delivered with two clips, two screws and four threaded holes. Fig. 6.1: Flat lengthwise mounting to DIN rail – recommended Fig. 6.2: Flat widthwise mounting to DIN rail For vertical mounting to DIN rail, L-bracket (optional accessory) is used. © RACOM s.r.o. – RipEX Radio modem & Router 65 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. 66 RipEX Radio modem & Router – © RACOM s.r.o. 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.2, “Power and Control” ), which is triggered when the temperature inside RipEX exceeds a set temperature (recommended) or it can run permanently (it should be connected in parallel to the RipEX’s power supply). Configuration of the Alarm Output is described in chapter Advanced Configuration, Device. Dimensions are given in the Product chapter. © RACOM s.r.o. – RipEX Radio modem & Router 67 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. Proper network planning, including field signal measurements, should decide antenna types in the whole network. The plan will also determine what type of mast or pole should be used, where it should be located and where the antenna should be directed to. The antenna pole or mast should be chosen with respect to antenna dimensions and weight, to ensure adequate stability. Follow the antenna manufacturer’s instructions during installation. The antenna should never be installed close to potential sources of interference, especially electronic devices like computers or switching power supplies. A typical example of totally wrong placement is mount a whip antenna directly on top of the box containing all the industrial equipment which is supposed to communicate via RipEX, including all power supplies. Additional safety recommendations Only qualified personnel with authorisation to work at heights are entitled to install antennas on masts, roofs and walls of buildings. Do not install the antenna in the vicinity of electrical lines. The antenna and brackets should not come into contact with electrical wiring at any time. The antenna and cables are electrical conductors. During installation electrostatic charges may build up which may lead to injury. During installation or repair work all open metal parts must be temporarily grounded. The antenna and antenna feed line must be grounded at all times. Do not mount the antenna in windy or rainy conditions or during a storm, or if the area is covered with snow or ice. Do not touch the antenna, antenna brackets or conductors during a storm. 6.3. Antenna feed line The antenna feed line should be chosen so that its attenuation does not exceed 3 to 6 dB as a rule of thumb, see Chapter 3, Network planning. Use 50 Ω impedance cables only. 68 RipEX Radio modem & Router – © RACOM s.r.o. 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. Always follow the installation recommendations provided by the cable manufacturer (bend radius, etc.). Use suitable connectors and install them diligently. Poorly attached connectors increase interference and can cause link instability. 6.4. Grounding To minimise the odds of the transceiver and the connected equipment receiving any damage, a safety ground (NEC Class 2 compliant) should be used, which bonds the antenna system, transceiver, power supply, and connected data equipment to a single-point ground, keeping the ground leads short. The RipEX radio modem is generally considered adequately grounded if the supplied flat mounting brackets are used to mount the radio modem to a properly grounded metal surface. If the radio modem is not mounted to a grounded surface, you should attach a safety ground wire to one of the mounting brackets or a screw on the radio modem’s casing. A lightning protector should be used where the antenna cable enters the building. Connect the protector to the building grounding, if possible. All grounds and cabling must comply with the applicable codes and regulations. 6.5. Connectors RipEX uses standard connectors. Use only standard counterparts to these connectors. You will find the connectors’ pin-outs in chapter Section 4.2, “Connectors”. 6.6. Power supply We do not recommend switching on the RipEX’s power supply before connecting the antenna and other devices. Connecting the RTU and other devices to RipEX while powered increases the likelihood of damage due to the discharge of difference in electric potentials. RipEX may be powered from any well-filtered 10 to 30 VDC power source. The supply must be capable of providing the required input for the projected RF output. The power supply must be sufficiently stable so that voltage doesn’t drop when switching from receiving to transmission, which takes less than 1.5 ms. To avoid radio channel interference, the power supply must meet all relevant EMC standards. Never install a power supply close to the antenna. Maximal supply cable length is 3 m. 10 – 30VDC +10 to +30 V Fig. 6.10: 10–30 VDC Supplying © RACOM s.r.o. – RipEX Radio modem & Router 69 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. However it is not recommended to manage an over-the-air connected RipEX in this way, because high amounts of data would have to be transferred over the Radio channel, resulting in quite long response times. When you need to manage an over-the-air connected RipEX, log-in to a RipEX, which your computer is connected to using either a cable (via LAN) or a high speed WAN (e.g. Internet). The RipEX which you are logged-in to in this way is called Local. Then you can manage any remote RipEX in the network over-the-air in a throughput-saving way: all the static data (e.g. Web page graphic objects) is downloaded from the Local RipEX and only information specific to the remote unit is transferred over the Radio channel. RipEX connected in this way is called Remote. When in Router mode, the IP address of either the Radio or Ethernet interface in the remote unit can be used for such remote management. IP routing between source (IP of ETH interface in Local RipEX) and destination IP (either Radio or ETH interface in Remote RipEX) has to exist. When in Bridge mode, IP addresses of Ethernet interfaces are used for both the Local and Remote units. Be careful, each RipEX MUST have its unique IP address and all these IP addresses have to be within the same IP network (defined by the IP Mask) when remote management is required in Bridge mode. Fig. 7.1: Menu Header Values from The Unit name (Settings/Device/Unit name) of the RipEX from which data is currently displayed and which is currently managed. Remote IP address of the remotely connected RipEX. After filling-in the Connect button shall be pressed. 70 RipEX Radio modem & Router – © RACOM s.r.o. 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. Device, Radio, ETH&COM's This part of Status page displays basic information about the RipEX (e.g. Serial No., MAC addreses, HW versions etc.) and overview of its most important settings. Configurable items are underlined and one click can take you to the respective Settings menu. 7.2.2. Diagnostic The current state of Watched values is displayed in the Diagnostic part of the Status page. Watched values are values of parameters, which are continuously monitored by RipEX itself. On-line help for each individual item is provided by balloon tips (when cursor is placed over an item name). When an item goes red, it means that the item is monitored for alarm and its value is in the alarm range (see Settings/Device/Alarm management) © RACOM s.r.o. – RipEX Radio modem & Router 71 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 convenience, no DNS (Domain Name Server) is used in the RipEX network. Operating Mode List box: Bridge, Router Default = Bridge 72 RipEX Radio modem & Router – © RACOM s.r.o. 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. once a message is delivered, it is 100% error free. All the messages received from user interfaces (ETH&COM's) are immediately transmitted to Radio channel, without any checking or processing. ETH: The whole network of RipEX units behaves like a standard Ethernet network bridge, so the Ethernet interface IP address itself is not significant. Each ETH interface automatically learns which devices (MAC addresses) lie in the local LAN and which devices are accessible via the Radio channel. Consequently only the Ethernet frames addressed to remote devices are physically transmitted on the Radio channel. This arrangement saves the precious RF spectrum from extra load which would otherwise be generated by local traffic in the LAN (the LAN to which the respective ETH interface is connected). COM1,COM2: all frames received from COM1(2) are broadcast over Radio channel and transmitted to all COM's (COM1 as well as COM2) on all units within the network, the other COM on the source RipEX excluding. • • Frame closing (COM1,2) List box: Idle, Stream Default = Idle Idle Received frames on COM1 (COM2) are closed when gap between bytes is longer than the Idle value set in COM1,2 settings and transmitted to Radio channel afterwards. ○ 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 the Radio channel is transmitted to the respective user interface (ETH,COM1,2) and to the Radio channel again. The Bridge functionality is not affected, i.e. only frames whose recipients belong to the local LAN are transmitted from the ETH interface. It is possible to use more than one Repeater within a network. To eliminate the risk of creating a loop, the "Number of repeaters" has to be set in all units in the network, including the Repeater units themselves. ○ Number of repeaters [0-7] Default = 0 If there is a repeater (or more of them) in the network, the total number of repeaters within the network MUST be set in all units in the network, including the Repeater units themselves. 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. Furthemore, a copy of every frame transmitted to or received from the Radio channel is stored (for a period). Whenever a duplicate of a stored frame is received, it is discarded to avoid possible looping. These measures are not taken when the parameter "Number of repeaters" is zero, i.e. in a network without repeaters. ○ TX delay [ms] [0-5000] © RACOM s.r.o. – RipEX Radio modem & Router 73 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. In order to prevent such a collision, TX delay should be set individually in each slave RipEX. The length of responding frame, the length of Radio protocol overhead, Modulation rate have to be taken into account. Stream In this mode, the incoming bytes from a COM are immediately broadcast over the Radio channel. COM port driver does not wait for the end of a frame. When the first byte is coming from a COM, the transmission in the Radio channel starts with the necessary frame header. If the next byte arrives before the end of transmission of the previous one, it is glued to it and the transmission on the Radio channel continues. If there is a gap between incoming bytes, the byte after the gap is treated as the first byte and the process starts again from the beginning. Padding is never transmitted between blocks of bytes. The receiving RipEX transmits incoming bytes (block of bytes) from the Radio channel to both COM ports immediately as they come. When the ETH interface is used simultaneously (e.g. for remote configuration), it works as the standard bridge described above. ETH frames have higher priority, i.e. the stream from COM is interrupted by a frame from Ethernet. Stream mode is recommended to be used for time-critical application only, when the first byte has to be delivered as soon as possible. However there is not any data integrity control. If the Baud rate of COM is significantly lower than the Modulation rate on the Radio channel, frames are transmitted byte by byte. If it is higher, blocks of bytes are transmitted as frames over the Radio channel. Note: Stream mode can not be used when there is a Repeater in the network. Router Router mode is suitable for Multipoint networks, where Multi-master applications with any combination of polling and/or spontaneous data protocols can be used. The proprietary link-layer protocol on the Radio channel is very sophisticated, it can transmit both unicast and broadcast frames, it has collision avoidance capability, it uses frame acknowledgement and retransmissions and a CRC check to guarantee data delivery and integrity even under harsh interference conditions on the Radio channel. RipEX works as a standard IP router with 2 independent interfaces: Radio and ETH. Each interface has got its own MAC address, IP address and Mask. IP packets are processed according the Routing table. There is also possibility to set a router Default gateway (apply to both interfaces) in 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 port numbers. Destination IP address of COM port is either the IP of ETH or the IP of Radio interfaces. The source IP address of outgoing packets from COM ports is always the IP of ETH interface. • 74 ACK List box: Off, On. RipEX Radio modem & Router – © RACOM s.r.o. 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. • • • Note: The acknowledgement/retransmission scheme is an embedded part of the Radio protocol and works independently of any retries at higher protocol levels (e.g. TCP or user application protocol) ○ Off There is no requirement to receive ACK from the receiving RipEX. i.e. the packet is transmitted only once and it is not repeated. Retries [No] [0-15] Default = 3 When an acknowledge from the receiving RipEX is not received, the frame is retransmitted. The number of possible retries is specified. RSS threshold [-dBm] [50-150] 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. Repeat COM Broadcast List box: On, Off Default = Off If On, a broadcast originated on COM port (Protocol/Broadcast = On) in any remote unit and received by this unit on Radio channel is repeated to Radio channel. Hot Standby When RipEX unit is used in RipEX-HS and Hot Standy is „On“ there are some limitations with it. Specifically, CD pin on COM1 and HW alarm Input and Output are used internally and not available to the user. Neither Save nor Sleep modes can be activated. Please refer RipEX-HS User manual. All settings below are valid only for RipEX units in RipEX-HS equipment, where two units in Hot Standby mode are running. Both units MUST have the same settings! Only Unit names should be different as this parameter is used in SNMP to recognize the sender of SNMP traps. In order to ensure that the settings of both units are identical, it is recommended to set unit “A”, thereafter save its settings into a file (Maintenance/Configuration/Save to file) and use these settings for unit “B”. (Maintenance/Configuration/Restore/File path/Upload) Finally, a unique Unit name should be assigned to Unit B. List box: Off, On Default = Off When “On”, HW switching from RipEX unit “A” to RipEX unit “B” is performed based on the HW Alarm Output settings in Settings/Alarm management. RipEX “A” is the primary unit, , Unit “B” is activated if there is HW alarm on unit “A” or unit “A” power source is down or when Auto Toggle Period expired. When mentioned events passed, RipEX “A” goes to be active again. • MAC Both units in RipEX-HS are using the same MAC addresses (MAC cloning). Whichever unit is active (either “A or B”), RipEX Ethernet interface will use this MAC address. This MAC address has to be unconditionally set to the same value in both units used in RipEX-HS. Otherwise, the switching between units will not function properly. © RACOM s.r.o. – RipEX Radio modem & Router 75 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. ○ Start Date [YYYY-MM-DD] Fill in the Date in the required format when Auto Toggle mode starts. ○ Start Time [HH:MM:SS] Fill in the Time in the required format when Auto Toggle mode starts on ”Start Date“ day. ○ Period [min.] Minimum value 60 min. Within this period units “A” and “B” will change their activities over. Unit “A” starts to operate at “Start Date and Time”. When “Period” minus “Unit B” time expires, controller switches to unit “B”. ○ Unit B [min.] Minimum value 5 min. Time when unit “B” will be active within “Period”. It has to be shorter than Period by 5 min. Time List box: Manual, NTP Default = Manual Internal calendar time of RipEX can be set manually or synchronized via NTP (Network Time Protocol). • Manual • RipEX internally uses the Unix epoch time (or Unix time or POSIX time) - the number of seconds that have elapsed since January 1, 1970. When RipEX calendar time is set, the Unix epoch time is calculated based on filled in values (Date, Time) and the time zone, which is set in operating system (computer), where the browser runs. ○ Current Date&Time Information about the actual date and time in the RipEX ○ Date [YYYY-MM-DD] Fill in Local Date in required format ○ Time [HH:MM:SS] Fill in Local Time in required format ○ RipEX Time zone Select RIPEX Time zone from list box. Default = (GMT +1:00) Central Europe This time zone is used for conversion of internal Unix epoch time to "human readable date&time" in RipEX logs. ○ Daylight saving List box: On, Off Default = On If On, Daylight saving is activated according the respective rules for selected RipEX Time zone. NTP 76 RipEX Radio modem & Router – © RACOM s.r.o. 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). ■ Internal GPS – The source of time is the internal GPS. In this case only RipEX Time zone and Daylight saving parameters below are active. ○ Source IP Default = empty IP address of the NTP server, which provides Time source. Date and Time will be requested by RipEX from there. More NTP servers can be configured, the more servers, the better time accuracy. If the Time source is a RipEX over Radio channel, only one source server is recommended, since the Radio channel could be overloaded. ○ Minimum polling interval List box: 1min to 2h 17min RipEX polls the source server in order to synchronize itself in the set period or later. ○ RipEX Time zone Select RipEX Time zone from list box. Default = (GMT +1:00) Central Europe This time zone is used for conversion of internal Unix epoch time to "human readable date&time" in RipEX logs.. ○ Daylight saving List box: On, Off Default = On If On, Daylight saving is activated according the respective rules for selected RipEX Time zone. RipEX NTP server Information about the status of internal NTP server in the RipEX ○ State ■ not synced - not synchronized ■ synced to GPS - synchronized to internal GPS ■ synced to NTP - synchronized to NTP server ○ Stratum 1 to 16 (1=the best, 16=the worst, 8=when internal time in RipEX is set manually) The stratum represents the quality and accuracy of time, which the NTP server provides. ○ Delay [ms] This is the delay of packet (1/2 round trip time), which RipEX received from the NTP server while asked for synchronization. This delay is compensated in the RipEX NTP server. ○ Jitter [ms] The Jitter of received times when RipEX asked for time synchronization from NTP server(s). Firewall List box: Off, On Default = Off There is a standard Linux firewall implemente. • Port – a range of port numbers can be entered. E.g. 2000-2120. © RACOM s.r.o. – RipEX Radio modem & Router 77 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. Related – a connection related to the “Established” one. e.g. FTP typically uses 2 TCP connections – control and data - where data connection is created automatically using dynamic ports. Note1: Port 443 and 8889 are used internally for service access. Exercise caution when making rules which may affect datagrams to/from this port in Firewall settings. Connection between your PC and RipEX may be lost. When this happens, use the Reset button on the bottom side of RipEX (keep it pressed for 15 sec.) in order to set Default access, which restores the default IP, default password and clears the Firewall. Note2: Firewall settings do not impact packets received and redirected from/to Radio channel. Alarm management The average values of parameters listed in the table (Watched values) are continuously monitored. When any of them exceeds the respective threshold, the selected action(s) is(are) invoked. Fig. 7.4: Menu Alarm management Note: At least 10 values have to be included on average before it is checked for the possible alarm. Since different values are sampled over different periods, different times are required to obtain correct values: Ucc, Temp – approx. 10 sec. after booting PWR, VSWR - approx. 10 sec. after booting and after the first transmission Others – approx. 200 sec. of respective communication • 78 Threshold RipEX Radio modem & Router – © RACOM s.r.o. 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. HW Alarm Output List box: Off, N.O. (Normally Open), N.C. (Normally Closed) Default = Off If "N.O." or "N.C.", the HW Alarm Output is active and its normal status (no alarm) is open or closed, respectively. The HW Alarm Output is a pin (open n-p-n collector) on the screw terminal at the Power and Control connector on the front panel. Detail Graph start Just for information. It can be set in Settings/Graph/Detail Graph start, not here. Alarm starts Detail Graph only when this value is set to "Alarm" HW Alarm Input List box: Off, N.O. (Normally Open), N.C. (Normally Closed) Default = Off If "N.O." or "N.C.", the HW Alarm Input is active and its normal status (no alarm) is open or closed, respectively. Alarm event is triggered when the HW Alarm Input changes its status from “Normal” to “Alarm”. Note that to “Close” the HW Alarm Input means connecting the respective screw terminal at the Power and Control connector on the front panel to the Ground terminal of the same connector. When Statistic and Neighbours logs are cleared, RSScom, DQcom, ETH, COM1, COM2 alarms are cleared as well. When Hot Standby is “On”, Alarm thresholds and HW alarm input are used internally for switching between units “A” and “B”. The “HW alarm input” parameter is changed to “Hot Standby active”. However, SNMP Alarm and Detailed Graphs tick boxes can be used for information about switching between units “A” and “B”. Power management • • • Power supply mode List box: Always On, Save Mode, Sleep Mode Default = Always On Always On RipEX is always on, no special power saving modes are active. Save Mode RipEX is listening on Radio channel in the Save mode while consuming 2.0 W. Router mode: When the RipEX receives a packet for its IP address, it wakes up. However data from this first received packet is lost. Bridge mode: Any packet received on Radio channel wakes the unit up. ○ Timeout List box: On, Off Default = On © RACOM s.r.o. – RipEX Radio modem & Router 79 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. When the respective pin is grounded, RipEX goes to sleep and consumes only 0.1 W at 13.8 V (see Section 4.4, “Technical specification”). The time needed for complete wake-up is approx. 25 seconds (booting time). ○ Timeout from sleep request [sec.] Default = 300 [0 - 64 800] RipEX remains on for the set time from the moment when the sleep input pin has been grounded. Neighbours&Statistics • Parameters List box: Default, Manual, Default = Default Default – Default (recommended) values are set and can not be edited. Manual – Values can be set manually. There are 2 tables with diagnostic information in the main menu - Diagnostic/Neighbours, Diagnostic/Statistic. 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. ○ Watched values broadcasting period [min] Default = 10 min, [0 = Off] RipEX periodically broadcasts its Watched values to neighbouring units. The Watched values can be displayed in Graphs and Neighbours menu. Note: When Bridge mode is used, watched values broadcasting creates collisions for user traffic. Be careful in using this feature. ○ Neighbours&Statistic log save period [min] Default = 1440 min (1 day) [10 - 7200 min] This is the period, in which Neighbours and Statistics logs are saved in the archive and cleared and new logs start from the beginning. Note: The history files are organized in a ring buffer. Whenever a new file is opened, the numbers of files are shifted, i.e. 0->1, 1->2, etc. There is a history of 20 log files available Graphs • 80 Parameters List box: Default, Manual, Default = Default Default – Default (recommended) values are set and can't be edited. Manual – Values can be set manually. Graphs displays history of Watched values and history of some of the items from the Statistic table. Displayed values are stored in each RipEX including data from selected five neighbouring units. Neighbour = RipEX, which can be accessed directly over the Radio channel (not over Ethernet), RipEX Radio modem & Router – © RACOM s.r.o. 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.0 Up to 5 IP addresses of neighbouring units can be set. (Neighbour = RipEX, which can be accessed 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. ○ Overview graph sampling period List box: 1, 2, 4, 12 hours Default = 12 hours The 60 samples per graph file result in (depending on the sampling period) 60, 120, 240 or 720 hours in each file. There are 6 files available, so total history of saved values is 15, 30, 60 or 180 days. The Overwiev graph files are organized in a ring buffer. Whenever a new file is opened, the oldest one is replaced. ○ Detail Graph sampling period List box: 1, 5, 10, 20 mins Default = 1 min The 60 samples per graph file result in 60, 300, 600, 1200 minutes in each file. There are 20 files available. They are organized in a ring buffer. When a new file is opened, the one with oldest data is replaced. The Detail graph files may not cover a continuous segment of history. See Detail graph start for details. ○ Detail Graph start List box: No, Alarm, Single, Continual Default = No Detail graph data sampling is started based on selected event from list box: No – Detail graph does not start. Alarm – if a tickbox in Detail graph column (Settings/Alarm management) is checked, then the Detail graph file is stored in case of that alarm. Twenty samples prior the alarm event and forty samples after the alarm event are recorded. When another alarm occurs while a Detail graph file is opened, the sampling continues normally and no other file is opened. Single – a single Detail graph file can be manually started. After Apply here, go to Diagnostic/Graph where a Start/Stop button is available Continual – Detail graph files are periodically saved in the same way as Overview graph files are. © RACOM s.r.o. – RipEX Radio modem & Router 81 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). The value entered must be within the frequency tuning range of the product as follows: RIPEX-135: 135–154 MHz RIPEX-154: 154–174 MHz RIPEX-300: 300–320 MHz RIPEX-320: 320–340 MHz RIPEX-340: 340–360 MHz RIPEX-368: 368–400 MHz RIPEX-400: 400–432 MHz RIPEX-432: 432–470 MHz RX frequency** Receiving frequency, the same format and rules apply. Note: By default, the TX and RX frequencies are locked together and change in one field is mirrored in the other. If clicked, the lock is removed and different TX and RX frequencies can be entered. 82 RipEX Radio modem & Router – © RACOM s.r.o. 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. Modulation rate [kbps] • • Approval List box: possible values ○ CE Radio parameters meet the requirements of ETSI EN 300 113 ○ FCC Radio parameters meet the requirements of FCC part 90 CPFSK modulations have approx. 20% higher frequency deviation compared to CE, so the receiver sensitivity for the same modulation (data rate) is approx. 1-2 dB better. ○ Others There are no official Radio test reports for CE 6,25 kHz and FCC 25 kHz channel spacings as yet. However “Others” enables setting of Modulation rates for these options. Modulation rate [kbps] List box: possible values Default = 16DEQAM Possible values in list box are dependent on the Approval set. The two highest rates are available only when the corresponding SW feature key is active. Higher Modulation rates provide higher data speeds but they also result in poorer receiver sensitivity, i.e. reduced coverage range. Reliability of communication over a radio channel is always higher with lower Modulation rates. FEC List box: possible values Default = Off FEC (Forward Error Correction) is a very effective method to minimize radio channel impairments. Basically the sender inserts some redundant data into its messages. This redundancy allows the receiver to detect and correct errors (to some extent). The improvement comes at the expense of the user data rate. The lower the FEC ratio, the better the capability of error correction and the lower the user data rate. The User data rate = Modulation rate x FEC ratio. Optimization* List box: On, Off Default = Off © RACOM s.r.o. – RipEX Radio modem & Router 83 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. FTP download) it splits the continuous stream of packets and creates a window for the other links. To minimize the actual load, Zlib compression (with LZ77 decimation and Huffman coding) and other sophisticated methods are used. In addition a special TCP optimiser is used for TCP/IP connections. It supervises every TCP session and eliminates redundant packets. It also compresses TCP headers in a very efficient way. The overall effect of the Optimization depends on many factors (data content, packet lengths, network layout etc.), the total increase of network throughput can be anything from 0 to 200%, or even more in special cases. Note: Apart from this Optimization, there is an independent compression on the Radio channel, which works in both Operating modes, Bridge and Router. This compression is always On. Encryption AES 256 (Advanced Encryption Standard) can be used to protect your data from an intrusion on Radio channel. When AES 256 is On, control block of 16 Bytes length is attached to each frame on Radio channel. AES requires an encryption key. The length of key is 256 bits (32 Bytes, 64 hexa chars). The same key must be stored in all units within the network. List box: Off, AES 256 Default = Off When AES 256 Key mode List box: Pass Phrase, Manual Default = Pass Phrase • • Pass phrase It is not necessary to fill in 32 Bytes of hexa chars in order to set the encryption key. The key can be automatically generated based on a Pass phrase. Fill in your Pass phrase (any printable ASCII character, min. 1 char., max. 128 char.). The same Pass phrase must be set in all units within the network Manual The key can be configured manually (fill in 32 Bytes of 64 hexa chars) or it can be randomly generated using Generate button. The same key must be in all units within the network, i.e. it has to be generated only in one unit and copied to the others. MTU [bytes]* Default = 1500 Bytes [70 - 1500] (max. packet size) 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. The reassembly of the fragments into the original packet normally takes place in the unit at the end of the path. Reducing the maximum length of a frame on a Radio link may improve its performance under unfavourable conditions (interference, multi-path propagation effects). However the recommended place to determine the packet size is the actual user interface, e.g. a COM port. Note that the IP fragmenting is possible in the Router mode only. 84 RipEX Radio modem & Router – © RACOM s.r.o. 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. DHCP* List box: Off, Server Default = Off Server DHCP (Dynamic Host Configuration Protocol) Server in RipEX sets network configuration (IP address, 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. Important! Never activate the DHCP Server when ETH interface of RipEX is connected to LAN, where another DHCP server is operating. • Start IP Default = IP address of ETH interface + 1 DHCP Server assigns addresses to connected clients starting from this address. © RACOM s.r.o. – RipEX Radio modem & Router 85 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. 10 days) A DHCP Client has to ask DHCP Server for refresh of the received configuration within this timeout, otherwise the Lease expires and the same settings can be assigned to another device (MAC). Assigned IP's Table shows MAC addresses of Clients and IP addresses assigned to them by the Server. Expiration is the remaining time till the respective Lease expires. If the assigned IP addresses are required to be deleted, set DHCP Server to Off, then action Apply and set DHCP server to On (+Apply) again. Preferred IP's It is possible to define which IP should be assigned by the Server to a specific MAC. The requested IP has to be within the Start IP – End IP range. • • • • Shaping* List box: On, Off Default = Off Ethernet interface could easily overload the Radio channel. Because of that, it is possible to shape traffic received from the ETH interface. If On, specified volume of Data [Bytes] in specified Period [sec] 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. Further over-limit packets are discarded. Speed List box: Auto, 100baseTX/Full, 100baseTX/Half, 10baseT/Full, 10baseT/Half Default = Auto Communication speed on the Ethernet interface. Modbus TCP* Use this setttings only for Modbus TCP Master when it communicates with both types of Modbus slaves using either Modbus RTU or Modbus TCP protocols. Or when TCP/IP communication should run locally between Modbus Master and RipEX in Modbus TCP network. Read Help and Application note Modbus in RipEX. For more information refer to the manual Application note / Modbus TCP . ** - denotes items to be used only when either all or some RTUs (Remote Telemetry Unit) on remote sites are connected via RS232 or RS485 interface to RipEX, using the Modus RTU protocol. Then automatic conversion between Modbus TCP and Modbus RTU protocols takes place for such units. List box: On, Off Default = Off http://www.racom.eu/eng/products/m/ripex/app/modbus.html 86 RipEX Radio modem & Router – © RACOM s.r.o. 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. RipEX (Protocol utility) converts such message to an IP broadcast and broadcasts it to all RipEX units resp. to all SCADA units within the network. If On, the address for broadcast packets in SCADA protocol has to be defined: Broadcast address format - List box Hex, Dec - format in which broadcast address is defined. Broadcast address - address in the defined format (Hex, Dec) Address translation List box: Table, Mask Default = Mask In a SCADA protocol, each SCADA unit has a unique address, a "Protocol address". In RipEX Radio network, each SCADA unit is represented by an IP address (typically that of ETH interface) and a UDP port (that of the protocol daemon or the COM port server to which the SCADA device is connected via serial interface). A translation between "Protocol address" and the IP address & UDP port pair has to be done. It can be done either via Table or via Mask. Each SCADA message received from serial interface is encapsulated into a UDP/IP datagram, where destination IP address and destination UDP port are defined according the settings of Address translation. ○ Mask Translation using Mask is simpler to set, however it has some limitations: − all IP addresses used have to be within the same network, which is defined by this Mask − the same UDP port is used for all the SCADA units, which results in the following limitations: − SCADA devices on all sites have to be connected to the same interface (COM1 or COM2) − 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 the 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.0 A part of Base IP address defined by this Mask is replaced by 'Protocol address'. The SCADA protocol address is typically 1 Byte, so Mask 255.255.255.0 is most frequently used. ■ UDP port (Interface) List box: COM1, COM2, TS1-TS5, TCPM1, Manual. Default = COM1 This UDP port is used as the destination UDP port in the UDP datagram in which serial SCADA packet received from COM1(2) is encapsulated. Default UDP ports for COM1, COM2 or Terminal servers 1-5 (TS1-TS5) or Modbus TCP (TCPM1) 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 © RACOM s.r.o. – RipEX Radio modem & Router 87 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.g.: 56 −−> 192.168.20.20) − Interval of "Protocol addresses" to one "IP address" (e.g.: 56-62 −−> 192.168.20.20) − Interval of "Protocol addresses" to interval of "IP addresses" (e.g.: 56-62 −−> 192.168.20.2026). It is possible to write only the start IP and dash, the system will add the end address itself. ■ Protocol address This is the address which is used by SCADA protocol. It may be set either in Hexadecimal or Decimal format according the List box value. Protocol address length can be 1 Byte, only for DNP3 and UNI protocols 2 Bytes. ■ IP IP address to which Protocol address will be translated. This IP address is used as destination IP address in UDP datagram in which serial SCADA packet received from COM1(2) is encapsulated. ■ UDP port (Interface) This is the UDP port number which is used as destination UDP port in UDP datagram in which the serial SCADA message, received from COM1(2), is encapsulated. ■ Note You may add a note to each address up to 16 characters long for your convenience. (E.g. “Remote unit #1" etc.). ■ Active You may tick/untick each translation line in order to make it active/not active. ■ Modify Edit Delete Add buttons allow to edit or to add or to delete a line. The lines can be sorted using up and down arrows. 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. Examples of the use: A SCADA application in the centre should be connected to the Radio network via a serial interface, however for some reason that serial interface is not used. The operating system (e.g. Windows) can provide a virtual serial interface to such application and converts the serial data to TCP (UDP) datagrams, which are then received by the Terminal server in RipEX. This type of interconnection between RipEX and application is especially advantageous when: • • there is not any physical serial interface on the computer the serial cable between the RipEX and computer would be too long (e.g. the RipEX is installed very close to the antenna to improve radio coverage). the LAN between the computer and the place of RipEX installation already exists Modbus TCP is used with local TCP sessions on slave sites or when combination of Modbus RTU and Modbus TCP is used. For more information refer to Application note Modbus TCP/RTU This applies also to other SCADA protocol TCP versions, e.g. DNP3 TCP. • • http://www.racom.eu/eng/products/m/ripex/app/modbus.html 88 RipEX Radio modem & Router – © RACOM s.r.o. 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. When data reaches the destination RipEX, it can be transferred to the RTU either via a serial interface or via TCP (UDP), using the Terminal server again. • Terminal server List box: On, Off Default = Off If On, up to 5 independent Terminal servers can be set up. Each one can be either of TCP or UDP Type, Keepalive is the timeout in sec for which the TCP socket in RipEX is kept active after the last data reception or transmission, My IP address of a Terminal server has to be always the same as the IP address of the RipEX ETH interface, My Port can be set as required. Destination IP and Destination port values belong to the locally connected application (e.g. a virtual serial interface). In some cases, applications dynamically change the IP port with each datagram. In such a case set Destination port=0. RipEX will then send replies to the port from which the last response was received. This feature allows to extend the number of simultaneously opened TCP connections between a RipEX and locally connected application to any value up to 10 on each Terminal server. Protocol follows the same principles as a protocol on COM interface. You may tick/untick each individual Terminal server in order to make it active/inactive. 7.3.4. COM's * 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. The source IP address of outgoing packets from COM ports is equal to IP address of the interface (either Radio or Ethernet) through which the packet has been sent. Outgoing interface is determined in Routing table according to the destination IP. The default UDP port numbers are COM1 = 8881, COM2 = 8882. If necessary they may be changed using CLI, nevertheless it is recommended to stick to the default values because of dependencies between different settings (e.g. Protocols) in the network. Note: UDP port settings is valid only in Router mode. In Bridge mode all packets received by COM port are broadcasted to all COM ports on all RipEXes within the network. © RACOM s.r.o. – RipEX Radio modem & Router 89 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. Serial ports use two-level (binary) signaling, so the data rate in bits per second is equal to the symbol rate in bauds Data bits List box: 8, 7 Default = 8 The number of data bits in each character. Parity List box: None, Odd, Even Default = None Wikipedia: Parity is a method of detecting errors in transmission. When parity is used with a serial port, an extra data bit is sent with each data character, arranged so that the number of 1-bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check. Stop bits List box: possible values Default = 1 90 RipEX Radio modem & Router – © RACOM s.r.o. 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. MRU [bytes] Default = 1600 [1 - 1600] MRU (Maximum Reception Unit) — an incoming frame is closed at this size even if the stream of bytes continues. Consequently, a permanent data stream coming to a COM results in a sequence of MRUsized frames sent over the network. Note 1: very long frames (>800 bytes) require good signal conditions on the Radio channel and the probability of a collision increases rapidly with the length of the frames. Hence if your application can work with smaller MTU, it is recommended to use values in 200 – 400 bytes range. Note 2: this MRU and the MTU in Radio settings are independent. However MTU should be greater or equal to MRU. Flow control List box: None, RTS/CTS Default = None 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. Note: RTS/CTS Flow control requires a 5-wire connection to the COM port. Protocol* List box: possible values Default = None Each SCADA protocol used on serial interface is more or less unique. The COM port daemon performs conversion to standard UDP datagrams used in RipEX Radio network. Each protocol has its individual configuration parameters, which are described in separate Help page (accessible from configuration light box Protocol - click on Protocol, then on Help). Protocol “None” simply discards any data received by the COM port or from the network, which means that the respective COM port is virtually disconnected from the RipEX. © RACOM s.r.o. – RipEX Radio modem & Router 91 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.) for data integrity control, so RipEX calculates this code and check it with the received one. RipEX radio network works in IP enviroment, so the basic task for Protocol interface utility is to convert SCADA serial packets to UDP datagrams. The Address translation settings are used to define the destination IP address and UDP port. Then these UDP datagrams are sent to RipEX router, processed there and they are typically forwarded as unicasts to Radio channel to their destination. When the gateway defined in the Routing table belongs to the Ethernet LAN, UDP datagrams are rather forwarded to the Ethernet interface. After reaching the gateway (typically a RipEX router again), the datagram is forwarded according to the Routing table. Note: Even if UDP datagrams, they can be acknowledged on the Radio channel (ACK parameter of 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). The UDP port can also be that of a Terminal server or any other special protocol daemon on Ethernet like Modbus TCP etc. The datagram is then processed accordingly to the respective settings. RipEX uses a unique, sophisticated protocol on Radio channel. This protocol ensures high probability of data delivery. It also guarantees data integrity even under heavy interference or weak signal conditions due to the 32 bit CRC used, minimises the probability of collision and retransmits frame when a collision happens, etc., etc. These features allow for the most efficient SCADA application arrangements to be 92 RipEX Radio modem & Router – © RACOM s.r.o. 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. Mode of Connected device List box: Master, Slave Default = Master Typical SCADA application follows Master-Slave scheme, where the structure of the message is different for Master and Slave SCADA units. Because of that it is necessary to set which type of SCADA unit is connected to the RipEX. Note: For SCADA Master set Master, for SCADA Slave set Slave. • Master SCADA Master always sends addressed messages to Slaves. The way of addressing is different from SCADA protocol to SCADA protocol, so this is one of the main reasons why an individual Protocol utility in RipEX for each SCADA protocol has to be used. ○ Broadcast List box: On, Off Default = Off 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 an IP broadcast and broadcasts it to all RipEX units resp. to all SCADA units within the network. If On, the address for broadcast packets in SCADA protocol has to be defined: ■ Broadcast address format - List box Hex, Dec - format in which broadcast address is defined. ■ Broadcast address - address in the defined format (Hex, Dec) ○ Address translation List box: Table, Mask Default = Mask In a SCADA protocol, each SCADA unit has a unique address, a "Protocol address". In RipEX Radio network, each SCADA unit is represented by an IP address (typically that of ETH interface) and a UDP port (that of the protocol daemon or the COM port server to which the SCADA device is connected via serial interface). A translation between "Protocol address" and the IP address & UDP port pair has to be done. It can be done either via Table or via Mask. So SCADA message received from serial interface is encapsulated into a UDP/IP datagram, where destination IP address and destination UDP port are defined according the settings of Address translation. ■ Mask Translation using Mask is simpler to set, however it has some limitations: − all IP addresses used have to be within the same network, which is defined by this Mask − the same UDP port is used for all the SCADA units, which results in the following limitations: − SCADA devices on all sites have to be connected to the same interface (COM1 or COM2) © RACOM s.r.o. – RipEX Radio modem & Router 93 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.0 A part of Base IP address defined by this Mask is replaced by 'Protocol address'. The SCADA protocol address is typically 1 Byte, so Mask 255.255.255.0 is most frequently used. • UDP port (Interface) List box: COM1,COM2, TS1-TS5, TCPM1, Manual. This UDP port is used as the destination UDP port in UDP datagram in which serial SCADA packet received from COM1(2) is encapsulated. Default UDP ports for COM1, COM2 or Terminal servers 1-5 (TS1-TS5) or Modbus TCP (TCPM1) 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. ■ Table The Address translation is defined in a table. There are no limitations such as when the Mask translation is used. If there are more SCADA units on RS485 interface, their “Protocol addresses” should be translated to the same IP address and UDP port pair, where the multiple SCADA units are connected. There are 3 possibilities how to fill in the line in the table: − One "Protocol address" to one "IP address" (e.g.: 56 −−> 192.168.20.20) − Interval of "Protocol addresses" to one "IP address" (e.g.: 56-62 −−> 192.168.20.20) − Interval of "Protocol addresses" to interval of "IP addresses" (e.g.: 56-62 −−> 192.168.20.2026). It is possible to write only the start IP and dash, the system will add the end address itself. • Protocol address This is the address which is used by SCADA protocol. It may be set either in Hexadecimal or Decimal format according the List box value. Protocol address length can be only 1 Byte. • IP IP address to which Protocol address will be translated. This IP address is used as destination IP address in UDP datagram in which serial SCADA packet received from COM1(2) is encapsulated. • UDP port (Interface) This is UDP port number which is used as destination UDP port in UDP datagram in which the serial SCADA message, received from COM1(2), is encapsulated. • Note You may add a note to each address up to 16 characters long for your convenience. (E.g. “Remote unit #1 etc.). • Active You may tick/un-tick each translation line in order to make it active/not active. • Modify Edit Delete Add buttons allow to edit or to add or to delete a line. The lines can be sorted using up and down arrows. Slave SCADA Slave typically only responds to Master requests, however in some SCADA protocols it can communicate spontaneously. RipEX Radio modem & Router – © RACOM s.r.o. 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. Async link Async link creates asynchronous link between two COM ports on different RipEX units. Received frames from COM1(2) are sent without any processing transparently to Radio channel to set IP destination and UDP port. Received frames from Radio channel are sent to COM1 or COM2 according UDP port settings. • Parameters ○ Destination IP This is IP address of destination RipEX, either ETH or Radio interface. ○ UDP port (Interface) This is UDP port number which is used as destination UDP port in UDP datagram in which packet received from COM1(2) is encapsulated. C24 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. Underlined parameters are described in Common parameters. Mode of Connected device Master Address translation Table Mask Slave • Protocol frames List box: 1C,2C,3C,4C Default = 1C One of the possible C24 Protocol frames can be selected. • Frames format © RACOM s.r.o. – RipEX Radio modem & Router 95 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. • Local ACK List box: Off, On Default = Off Available for Protocol frame 1C only. When On, ACK on COM1(2) is send locally from this unit, not over the Radio channel. Cactus 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. Underlined parameters are described in Common parameters. Mode of Connected device Master Broadcast Note: There is not the possibility to set Broadcast address, since Cactus broadcast messages always have the address 0x00. Hence when the Broadcast is On, packets with this destination are handled as broadcasts. Address translation Table Mask Slave Broadcast accept • Max gap timeout [ms] Default = 30 The longest time gap for which a frame can be interrupted and still received successfully as one frame. It should not be set below 10ms, while 15–40 ms should be OK for a typical Cactus protocol device. Comli Comli is a serial polling-type communication protocol used by Master-Slave application. When RipEX radio network run in Router mode, more Comli Masters can be used within one Radio network and one Slave can be polled by more Masters. Broadcasts packets are not used, so the configuration is using only some parameters described Common parameters. Mode of Connected device 96 RipEX Radio modem & Router – © RACOM s.r.o. 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. Broadcast According to the DF1 specification, packets for the destination address 0xFF are considered broadcasts. Hence when Broadcast is On, packets with this destination are handled as broadcasts. Address translation Table Mask • Advanced parameters ○ ACK Locally List box: Off, On Default = On If "On", ACK frames (0x1006)are not transferred over-the-air. When the RipEX receives a data frame from the connected device, it generates the ACK frame (0x1006) locally. When the RipEX receives the data frame from the Radio channel, it sends the frame to the connected device and waits for the ACK. If the ACK is not received within 1 sec. timeout, RipEX sends ENQ (0x1005). ENQ and ACK are not generated for broadcast packets. DNP3 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. • Broadcast - Note: There is not the option to set the Broadcast address, since DNP3 broadcast messages always have addresses in the range 0xFFFD - 0xFFFF. Hence when Broadcast is On, packets with these destinations are handled as broadcasts. Address translation Table Mask © RACOM s.r.o. – RipEX Radio modem & Router 97 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. Protocol broadcast address is not configurable, it is defined by Address mode in Advance parameter (default 0xFF) Address translation Table Mask Slave Broadcast accept • Advanced parameters ○ Address mode Even if IEC 870-5-101 is the standard, there are some users which customized this standard according their needs. When addressed byte has been moved, RipEX has to read it on the correct location. ■ IEC101 Address byte location according to IEC 870-5-101 standard. Broadcast from Master station is generated when address byte is 0xFF. ■ 2B ADDR Two byte address (IEC 870-5-101 standard is 1 Byte). The frame is 1 Byte longer than standard one. There is Intel sequence of bytes: low byte, high byte. Mask Address translation has to be used, because Table one is limited just to one byte address length. Broadcast from Master station is generated when low address byte is 0xFF and high address byte is 0x00. ■ TELEGYR The Control byte in standard IEC packet is omitted. The frame is 1 Byte shorter than standard one. This is typically used in Telegyr 805/809 protocol. Broadcast from Master station is generated when address byte is 0x00. ■ SINAUT The sequence of Address byte and Control byte in the frame is changed-over. Broadcast from Master station is generated when address byte is 0x00. ITT Flygt ITT Flygt is a serial polling-type communication protocol used in Master-Slave applications. ITT Flygt protocol configuration uses all parameters described in Common parameters. Mode of Connected device Master Broadcast 98 RipEX Radio modem & Router – © RACOM s.r.o. 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. 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. Address translation Table Mask Slave Broadcast accept • Wait timeout [ms] Default = 5000 An ITT Flygt Slave sometimes sends the WAIT COMMAND (0x13) to its Master. The RipEX does not accept the next WAIT COMMAND (discards it), till the Wait timeout does not expire. The Recommended value is in the 1-10 seconds range. Modbus Modbus RTU is a serial polling-type communication protocol used by Master-Slave application. When RipEX radio network run in Router mode, more Modbus Masters can be used within one Radio network and one Slave can be polled by more Masters. Modbus protocol configuration uses all parameters described in Common parameters. Mode of Connected device Master Broadcast Address translation Table Mask Slave Broadcast accept Profibus RipEX supports Profibus DP (Process Field Bus, Decentralized Periphery) the widest-spread version of Profibus. The Profibus protocol configuration uses all parameters described in Common parameters. © RACOM s.r.o. – RipEX Radio modem & Router 99 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. Mode device of Connected Master • Local simulation RB List box: Off, On Default = Off The RP570 protocol Master very often transmits the RB packets (hold packets) solely to check whether slaves are connected. In order to minimize the Radio channel load, the RipEX can be configured to respond to these packets locally and not to transmit them to the slaves over the Radio channel. If On, the RipEX responds to RB packets received from the RP 570 master locally over the COM interface. However from time to time (RB period) the RB packets are transferred over the network in order to check whether the respective slave is still on. When the RB response from the slave to this RB packet is not received over the Radio channel within the set RB timeout, i.e. the respective slave is out of order, the central RipEX stops local answering to RB packets from the master for the respective slave. • RB Net period [s] Default = 10 The RipEX responds to the RB packets locally and in the set RB period the RB packets are transferred over the network. • RB Net timeout [s] Default = 10 (maximum=8190) Whenever an RB packet is sent over the network, the set RB Net timeout starts. When the RB response from the remote unit (slave) is not received within the timeout, i.e. the respective slave is out of order, the central RipEX stops the local answering to RB packets from the master for the respective slave. Address translation 100 RipEX Radio modem & Router – © RACOM s.r.o. 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. If On, the RipEX generates RB packets locally and transmits them over the COM interface in the RB Request period and expects the RB response for each RB packet from the RP570 Slave within the RB Response timeout. When the RipEX does not receive the response(s) from the RP570 slave, the RipEX does not respond to the RB packet from the Master which it receives over the Radio channel. • RB Request period [ms] Default = 200 (maximum=8190) RipEX sends locally RB packets to the connected RTU in the set period. • 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. • RTU address (Hex) Default = 01 Active only when the Local simulation RB is On. The connected RTU’s address is supposed to be filled in. This address (0x00-0xFF) is used in the RB packets generated locally in the RipEX and transmitted over the COM. UNI UNI is the "Universal" protocol utility designed by RACOM. It is supposed to be used when the application 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 Master application device always contain the respective Slave address and that address (or its relevant part) position, relative to the beginning of the message (packet, frame), is always the same (Address position). Generally two communication modes are typical for UNI protocol: In the first one, communication has to be always initiated by the Master and only one response to a request is supported; in the second mode, Master-Master communication or combination of UNI protocol with ASYNC LINK protocol and spontaneous packets generation on remote sites are possible. The UNI protocol is fully transparent, i.e. all messages are transported and delivered in full, without any modifications. Underlined parameters are described in Common parameters. © RACOM s.r.o. – RipEX Radio modem & Router 101 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. Address position Specify the sequence number of the byte, where the Protocol address starts. Note that the first byte in the packet has the sequence number 1, not 0. Address mask (Hex) When the Address mode is Binary 2 Bytes, a 16-bit value is read from the SCADA protocol message according to the Address mode setting (either the MSB or the LSB first), The resulting value is then bit-masked by the Address mask and used as the input value for SCADA to IP address translation (e.g. by a table). The default value of the Address mask is FFFF, hence the full 16-bit value is used by default. Example: The Address mode is set to Binary (2B LSB first), the Address mask is set to 7FF0 and the Address position is set to 2. The SCADA message starts with bytes (in hex) 02 DA 92 C3 .. The 2-Byte address is read as 0x92DA (note the LSB came first in the message), Then 0x7FF0 mask is applied and the resulting value 0x12D0 (0x92DA & 0x7FF0) is used as the input for the translation. Poll response control List box: On, Off Default = On On – The Master accepts only one response per a request and it must come from the the specific remote to which the request has been sent. All other packets are discarded. This applies to the Master - Slave communication scheme. Note: It may happen, that a response from a slave (No.1) is delivered after the respective timeout expired and the Master generates the request for the next slave (No.2) in the meantime. In such case the delayed response from No.1 would have been considered as the response from No.2. When Poll response control is On, the delayed response from the slave No.1 is discarded and the Master stays ready for the response from No.2. Off – The Master does not check packets incoming from the RF channel - all packets are passed to the application, including broadcasts . That allows E.g. spontaneous packets to be generated at remote sites. This mode is suitable for Master-Master communication scheme or a combination of the UNI and ASYNC LINK protocols. 102 RipEX Radio modem & Router – © RACOM s.r.o. Advanced Configuration Broadcast Address translation Table Mask Slave Broadcast accept © RACOM s.r.o. – RipEX Radio modem & Router 103 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. Destination IP address of COM port is either IP of ETH or IP of Radio interfaces. The source IP address of outgoing packets from COM ports is equal to IP address of interface (either Radio or Ethernet) through packet has been sent. Outgoing interface is determined in Routing table according the destination IP. The IP addressing scheme can be chosen arbitrarily, only 127.0.0.0/8 and 192.0.2.233/30 restriction applies. 7.4.1. Menu Routing Fig. 7.9: Menu Routing Interfaces Radio IP address and Mask define the IP network (Radio LAN) within RipEX can communicate directly over the Radio channel, however the radio repeater (defined as the gateway in the route) can be used. All units which are supposed to communicate directly have to be within the same Radio LAN. ETH IP address and Mask define the IP network (LAN) in which RipEX can communicate directly over the Ethernet. All devices which should be accessible directly have to be within the same LAN. Routes Destination, Mask, Gateway Each IP packet, received by RipEX through any interface (Radio, ETH, COM1 or COM2), has got a destination IP address. RipEX (router) forwards the received packet either directly to the destination IP address or to the respective Gateway, according to the Routing table. Any Gateway has to be within 104 RipEX Radio modem & Router – © RACOM s.r.o. 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. The network (Destination and Mask) can by specified in both formats. Either 10.11.12.13/24 in Destination or 10.11.12.13 in Destination and 255.255.255.0. in Mask columns. RipEX displays and converts both formats. There is also a balloon tip while the cursor is in the specific line on the Mask. It shows which IP addresses are included in the network which is routed to the respective Gateway. Interface It may happen that networks defined by IP and Mask of router interfaces overlap. In such a case it is necessary to define to which interface (Radio, ETH) the packet should be forwarded. When Auto is selected, the packet is forwarded automatically to the correct interface. Note You may add a note to each route with your comments up to 16 characters (only ASCII is supported) for your convenience. (E.g. “Central station” etc.). Following characters are not allowed: " (Double quote) ` (Grave accent) \ (Backslash) $ (Dollar symbol) ; (Semicolon) Active You may tick/un-tick each route in order to make it active/not active. This feature is advantageous e.g. when one needs to redirect some route temporarily. Modify Edit Delete Add buttons allow to edit or add or delete a line. One may order the lines using up and down arrows. Buttons • • • • Apply - applies and saves the changes. Cancel - restores original values. Find - finds (highlights the respective line in the table) the route for a specific IP address if exists. Check routing - highlights duplicate routes for specific IP if they exist. © RACOM s.r.o. – RipEX Radio modem & Router 105 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). The files are organized in a ring buffer. Whenever a new file is opened or the Operating mode is changed, the numbers of files are shifted, i.e. 0->1, 1->2, etc. Then both the Neighbours and the Statistic log values are accumulated and weight-averaged over the whole Log save period (one day by default). Hence a fresh change in a traffic pattern is not completely averaged out when the recent log is e.g. 23 hours long. When a fresh and shorter sample of the log values is needed, there is a Difference log available. It uses an independent buffer for data and can be cleared and displayed anytime. Buttons All buttons are common for both logs, Neighbours and Statistic: • • Save button – the log is manually saved, stored in the history file and cleared. This equals to situation when the Log save period expires. When the Operating mode (Bridge / Router) is changed, the log is also Saved. Note: Remember that both the Neighbours and Statistic logs are saved. Difference Clear button – when pressed, the Difference log is cleared. The standard Neighbour and Statistic logs are not touched. Similarly, when the Log save period expires and the Neighbour and Statistic logs are cleared, the values in Difference log are not touched. Note: Remember that both Neighbours and Statistic logs are cleared. Display button – displays values of the Difference log, i.e. the values accumulated from time when the Set button has been pressed. 106 RipEX Radio modem & Router – © RACOM s.r.o. 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. It can be set in Settings/Device/Time menu. Log start Date and time when the log has been cleared and started. The log is cleared and started when Log save period expires or when Save buton is pressed or when power is switched On. Last update Date and time when log has been displayed. For actual values click the Refresh button. Log uptime The difference between Log start and Last update. Log Save period It redirects to Settings/Device/Neighbours&Statistics where Statistic&Neighbours log save period can be set. Also the Watched values broadcasting period can be set there. This is a period in which RipEX periodically broadcasts its Watched values to neighbouring units, where they are saved and can be displayed in the Neighbours table. Neighbours Neighbours log provides information about neighbouring units (Neighbour = RipEX, which can be accessed directly over the radio channel, i.e. without a repeater). Protocol on Radio channel uses MAC addresses. A unit can learn the IP address of its neighbour only when it receives its broadcast of Watched values (it contains both MAC and IP addresses). Thus when Watched values broadcasting is Off in a Neighbour (Settings/Device/Neighbours&Statistics), there is MAC address on the respective line in the Neighbours table. When a known IP adress of a Neighbour changes, the unit cumulates data to the old IP address till it receives the next Watched values broadcast. Maximum number of Neighbours listed in the table is 100. If this number is exceeded, the least significant Neighbour is omitted. The first criterion is whether this RipEX communicates with the Neighbour and the second criterion is the RSS level. Neighbours Table Generally: • • • • • there are balloon tips with on line help for column names the table can be sorted (descending/ascending) by any column, by clicking the column name two values are displayed for each item: Last and Average. Last is the last value received, the Average is a running average over all values received since the start of the log. The values received more recently weigh up to 50% more in the average than the earlier ones. if a value in the table is underlined, it is a link to Graphs green background indicates, that the item is monitored for alarm and its average value is within the “normal” range (Settings/Device/Alarm management) © RACOM s.r.o. – RipEX Radio modem & Router 107 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. The other values in both, Neighbours and Statistics tables are refreshed every 20s IP addresses: ○ Bridge mode Due to broadcast pattern of traffic in Radio channel, all frames generated by user application(s) cumulate in one line in the Neighbour table. When diagnostic or service frames (e.g. Watched values) are transmitted in the network, they are listed in separate lines, distinguished by IP address of their respective Ethernet interfaces. ○ Router mode 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. The first three columns are logged by the receiving RipEX itself. ○ Received headers [Count] Total number of frame headers received from the respective RipEX. ○ RSS [dBm] Received Signal Strength. ○ DQ Data Quality of received frames. The DQ value is about proportional to BER (bit error ratio) and about independent of the data rate and modulation used. Consequently when data rate is lowered, the DQ value increases and the other way round. Judging the DQ values requires experience, rule-of-thumb figures are as followsvalues: DQ below 100 means the link is unusable, aroundt 125 short packets starthould getting through, about 160 and above can be considered “good” values. The remaining columns contain values broadcasted by neighbouring units in their Watched values broadcasting periods(Settings/Device/Neighbours&Statistics). ○ TxLost [%] The probability of a transmitted frame being lost (100 * Lost frames / All transmitted frames). This value is broadcasted only when Router mode is used and ACK is On. ○ Ucc [V] Power voltage measured on power input. ○ Temp [°C] Temperature inside of the RipEX. ○ PWR [W] The actual value of Radio output power measured by RipEX itself. ○ VSWR Voltage Standing Wave Ratio (1.0=best, 1.0–1.8=acceptable, >2.5=indicates a serious problem in antenna or feeder) ○ Packets [Rx/Tx] The total number of packets received from / transmitted to ETH, COM1, COM2 interfaces. Can be used for interface activity diagnostic. 108 RipEX Radio modem & Router – © RACOM s.r.o. 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. Values in DATA part of the table are calculated for this source IP (origin), values in RADIO PROTOCOL part are for the last radio hop. Tx - for transmitted (Tx) packets, the IP destination address from UDP header is displayed. Values in DATA part of the table are calculated for this destination IP (final destination), values in RADIO PROTOCOL part are for the next radio hop. Note: Remember that the IP source and IP destination addresses of user IP packets are not the IP addresses of RipEXes who transport them. 7.5.2. Graphs Graphs functions as well as meanings of Overview, Detail, Sampling period are described in the help Settings/Device. © RACOM s.r.o. – RipEX Radio modem & Router 109 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. 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 corresponds with the start of the file. 1st IP List box: possible values Default = This unit List of IP addresses of RipEX units from which the graph values are available. The list of recorded units can be set in Settings/Device/Graphs. More in help Settings/Device. 1st line List box: possible values Default = TxLost 110 RipEX Radio modem & Router – © RACOM s.r.o. 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). When graph file is opened and threshold values are changed, new values are displayed in the next graph file. Present graph works till the end of its range threshold values set when started. Alarm When displayed value is out of threshold, a red line on the bottom of the graph is shown with its date and time displayed in a balloon tip. History There is a possibility to change displayed file(s) using standard buttons (Previous 10…6 5 4 .. Next). They are placed below the graph. Buttons Refresh - complete refresh of the screen, i.e. also files in list boxes are updated Display - displays/refresh ONLY data in graph according to current settings above Start/Stop - only for Detail graph. Active (displayed on the screen) when Detail Graph start (to be set in Settings/Graphs) is set to Single. Start button activates the sampling. Stop button can close the file before 60 samples are saved. © RACOM s.r.o. – RipEX Radio modem & Router 111 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. The source IP address of Ping in RipEX is always the IP address of Radio interface (Settings/ETH/IP) While using Ping, be sure that correct routing between source and destination IP addresses exists. Also pinged device has to have ICMP echo response enabled. RipEX has the ICMP echo response always enabled. Note: Ping utility generates on-line report each 2 seconds while you are connected to Local unit and each 10 sec. while it is generated from Remote unit and it is transffered over Radio channel. • Ping Type List box: ICMP, RSS Default = RSS ○ ICMP 112 RipEX Radio modem & Router – © RACOM s.r.o. 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.) for radio hop with the lowest RSS in both directions ■ Histogram of rtt of pings divided to 5 intervals ■ Load and Throughput ■ PER (Packet Error Rate) ■ BER (Bit Error Rate) Destination Default = 127.0.0.1 Destination IP address Length [bytes] Default = 80 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. Count Default = 5 Number of pings to be transmitted. The allowed range is from 1 to 1024. Period [ms] Default = 1000 When this Period expires, the next Ping is transmitted. The range is from 1000 (1 sec.) to 3600000 (1 hour). Timeout [ms] Default = 10000 Timeout from 1000 (1 sec.) to 3600000 (1 hour). When ping (the response) is not received within this timeout, it is counted as lost. Report A short report is generated in run-time for each individual ping packet. When the Ping utility is stopped, an overall statistic report is displayed. ○ ICMP Standard Linux ping reports are provided: ■ Run-time report: "88 bytes from 192.168.131.243: icmp_req=1 ttl=63 time=360 ms" 88 bytes = total packet lenght 192.168.131.243 = destination IP icmp_req = ping sequence number ttl = time to live, max. number of hops (passing through router) of the packet in the network time = rtt (round trip time), the time from transmission of ICMP echo request to reception of ICMP echo response ■ Statistic report: "5 packets transmitted, 5 received, 0% packet loss, time 4002ms" "rtt min/avg/max/mdev = 327.229/377.519/462.590/45.516 ms" time = total time of ping utility (From Start to Stop buttons) rtt min/avg/max/mdev = round trip time, minimal/average/maximal/standard deviation ○ RSS ■ Run-time report: © RACOM s.r.o. – RipEX Radio modem & Router 113 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.243 = destination IP seq = ping sequence number rtt = round trip time, the time from transmission to reception ■ Statistic report: "5 packet(s) transmitted, 5 received, 0.00% packet loss (0 corrupted), time 4.48 sec" "rtt: min/avg/max/mdev = 0.371/0.483/0.805/0.166 sec." corrupted = number of packets which have been received (UDP header is OK) nevertheless their data have been corrupted (CRC over data is not OK) time = the total time of ping utility (From Start to Stop buttons) rtt min/avg/max/mdev = round trip time, minimal/average/maximal/standard deviation "Load: 1098 bps" "Throughput: 1098 bps" Load = the load generated by Ping utility Throughput = the througput provided by Radio network "PER: 0.00% round trip, 0.00% one-way" "BER: 0.00% round trip, 0.00% one-way" PER - Packet Error Rate, i.e. the probability of a packet being lost. It is calculated for both the whole round trip and a one-way trip. BER - Bit Error Rate, the probability of one bit received with incorrect value. Only packets, no bits can be lost in packet radio network. When a single bit is received wrong, the whole packet is lost. The BER is calculated from the PER based on this assumption. "Radio hop with lowest RSS – direction to Destination" "RSS: 56.0/56.8/58.0/0.7 min/avg/max/mdev" "DQ : 208.0/219.0/232.0/9.4 min/avg/max/mdev" "Radio hop with lowest RSS – direction from Destination" "RSS: 56.0/56.4/57.0/0.5 min/avg/max/mdev" "DQ : 208.0/216.2/223.0/5.3 min/avg/max/mdev" There is RSS (Received Signal Strenght) and DQ (Data Quality) information from the radio hop with lowest RSS, separately for both directions (To and From the destination RipEX). The mdev values for both the RSS and DQ are provided, giving idea on signal homogeneity. The lower values are recorded, the more reliable the link should be. The “Homogenity” shows the jitter of RSS values from individual pings. "rtt histogram (time interval in sec.: %, count)" " 0.000 - 2.500: 100.00% 5" XXXXXXXXXX " 2.500 - 5.000: 0.00% 0" " 5.000 - 7.500: 0.00% 0" " 7.500 - 10.000: 0.00% 0" "10.000 - inf: 0.00% 0" 114 RipEX Radio modem & Router – © RACOM s.r.o. 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.14: Menu Monitoring Monitoring is an advanced on-line diagnostic tool, which enables a detailed analysis of communication over any of the interfaces of a RipEX router. In addition to all the physical interfaces (RADIO, ETH, COM1, COM2), some internal interfaces between software modules 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. Description of internal interfaces can be found below. • Interfaces Tick boxes: © RACOM s.r.o. – RipEX Radio modem & Router 115 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. When ticked, packets (frames, messages) coming in the respective direction are monitored. A packet is considered a Tx one when it comes out from the respective software module (e.g. 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. Please note the separate monitoring of Rx or Tx frames is not possible at the ETH interface. ○ Display List box: HEX, HEX+ASCII, ASCII Default = HEX The format of monitoring output. ○ Offset [bytes] Default = 0 Number of bytes from the beginning of packet/frame, which will not be displayed. The Length of bytes will be displayed starting from the immediately next byte. This feature is not available at the ETH interface. ○ Length [bytes] Default = 100 Number of bytes, which will be displayed from each packet/frame. rd • • th Example: Offset=2, Length=4 means, that bytes from the 3 byte to the 6 (inclusive) will be displayed: Data (HEX): 01AB3798A28593CD6B96 Monitoring output: 3798A285 Filter parameters for IP/ARP packets (available for RADIO, ETH and Internal RADIO (router), COMn(router), TSn(router), Modbus TCP(router)): ○ IP src IP source address range in the following format: aaa.bbb.ccc.ddd/mask ○ IP dst IP destination address range in the following format: aaa.bbb.ccc.ddd/mask ○ Port src TCP/UDP source port (range) in the following format: aaaa(-bbbb) ○ Port dst TCP/UDP destination port (range) in the following format: aaaa(-bbbb) ○ Protocol type (available for RADIO, ETH and Internal RADIO (router)) Tick boxes for displaying specific protocols only. "Other" means displaying everything except the four listed protocols (even non-IP frames in case of the RADIO interface). Interface specific parameters - RADIO ○ Radio IP src 116 RipEX Radio modem & Router – © RACOM s.r.o. 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. ■ Data Coding – Data Coding Header is displayed. It contains information on data part compression, fragmentation and encryption. ■ Both – Both the above mentioned headers are displayed. • Note that it may be quite difficult to locate the original payload in the data part of a Radio Link Protocol frame. Depending on the operation mode (Bridge vs. Router) and the interface used by the application (ETH, COM, Terminal Server...), different protocol headers (ETH, IP, UDP...) may be present and the whole data part may be compressed and encrypted. ○ Promiscuous mode: List box: On, Off Default = Off ■ Off – only frames which are normally received by this unit, i.e. frames whose Radio IP destination equals to Radio IP address of this RipEX unit and broadcast frames are processed further by monitoring filters. ■ On – all frames detected on the Radio channel are passed to monitoring filters ○ Link Control Frames List box: On, Off Default = Off ■ Off – Radio Link Control Frames (e.g. ACK frames) are never displayed. ■ On – Radio Link Control Frames which pass the other monitoring filters are displayed ○ Bridge mode ○ Router mode Tick boxes. When RADIO interface is in the Promiscuous mode, the unit is capable to monitor (receive) the frames which are transmitted in different operation modes (Bridge x Router) from the one set in this unit. Although such frames cannot be fully analysed by the monitoring engine, their content is displayed when the corresponding mode tick box is ticked. Note that only the applicable tick box is visible, i.e. when Operating mode is Router, than Bridge mode tick box and vice versa. ○ Rx stream Tick box. When ticked, received stream mode frames are included in the monitoring output. Applies to Bridge mode with Stream mode frame closing only. Warning : Stream mode traffic typically consists of large number of short frames, hence excessive amount of monitoring data may be generated. Note that TX frames in stream mode are not monitored. Interface specific parameters - ETH ○ ETH Headers List box: On, Off Default = Off When On, the ETH header is included in the monitoring output. Otherwise only the IP packet is displayed. ○ Management traffic List box: On, Off © RACOM s.r.o. – RipEX Radio modem & Router 117 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. The rule is then added after the rules generated from the filters set for the ETH interface on this web page. Internal - RADIO (router): ■ Headers: List box: None, Packet (IP), Frame (ETH) Default: None ■ None – Only the payload data is displayed, e.g. the data part of a UDP datagram. ■ Packet (IP) – Headers up to Packet layer are included, i.e. the full IP packet is displayed. ■ Frame (ETH) – The full Ethernet frame is displayed, i.e. including the ETH header Monitoring output control ■ Show time diff. Tick box. Default = Unticked When ticked, the time difference between subsequent packets is displayed in the monitoring output. ■ File period List box: 1 min, 2 min, 5 min, 10 min, 20 min, 30 min, 1 hour, 3 hours, 24 hours, Off Default = 5 min ■ File size List box: 1 KB, 10 KB, 50 KB, 100 KB, 500 KB, 1 MB, max (~2 MB) Default = 100 KB Upon clicking the File start button, the file is cleared and the monitoring output is copied into it. When the selected File period expires or the File size has been reached, whichever event occurs first, the file is closed and left waiting to be downloaded later. The start and stop of monitoring to file is independent of the on-line monitoring, i.e. the monitoring output is recorded even when the on-line monitoring is stopped. Buttons Buttons located at the bottom of the monitoring screen come in two groups: left: Start, Stop, Clear buttons, which control the on-line monitoring, and right: File Start, File Stop, File Status, Download buttons, which control the recording into the file. The two processes can be started/stopped by the respective buttons independently any time. Only one of the Start/Stop (File Start/File Stop) button pair is accessible at a time, depending on the status of the respective monitoring process (the other button is gray). The Clear button clears the screen with on-line monitoring output, even when the monitoring is running at the moment. 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. The Download button invokes the Download File dialog. Whenever the Start or File Start button is activated, the current settings of the monitoring from your web page are applied. When you change any setting on the page, both Start and File Start buttons indicate that a change has been made. They turn red when the respective monitoring process is idle and they change into Apply button when the monitoring is running, i.e. when the respective 118 RipEX Radio modem & Router – © RACOM s.r.o. 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. 1 below: RipEX Rx Rx Rx COM1 Tx COM PORTS MODULE Rx COM2 Tx Tx Tx ROUTER BRIDGE MODULE Rx RADIO CHANNEL MODULE RADIO Tx Rx ETH Tx Tx Rx virtual com eth TERMINAL & MODBUS TCP SERVERS Fig. 7.15: Monitoring The central router and bridge module acts as a standard IP router or bridge, i.e. decides to which interface an IP packet goes next. The COM ports module does the conversion from messages received over the serial ports to UDP datagrams and vice-versa. The Radio channel module wraps (unwraps) IP packets into radio channel frames and handles all sorts of service frames. Terminal servers process messages from/to virtual COM ports, transforming them into/from the same UDP datagrams as the COM port module does. The Modbus TCP server similarly processes packets of Modbus TCP(RTU) protocol - see the relevant application note (Modbus TCP/RTU) for details. Since it is possible to monitor the messages from virtual COM and the resulting UDP datagrams independently, the TSn and the Modbus TCP have two internal interfaces – distinguished as (com) and (router). © RACOM s.r.o. – RipEX Radio modem & Router 119 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). Time of activity of a key is counted only when the unit is switched on. Time limited key can be put on hold, i.e. temporarily deactivated. Press the corresponding Hold button (possibly several Hold buttons for several selected keys) and then press the Apply button to put the selected key(s) on hold. On hold (timeout dd:hh:mm:ss) – the key is On hold, i.e. temporarily not active. To re-activatete such a key, press the Activate and then Apply buttons. Master – when Master key (unlocks all keys) is active. Master (On hold) – The time-limited key for a specific feature is On hold, however the feature is active because of the Master key. Fill in the key you have received from RACOM or your distributor. • • Upload – when pressed, the selected SW key is uploaded into the RipEX, however it is not yet active. You can subsequently upload more keys. Apply – when pressed, all the uploaded keys are activated and/or status values of Time limited keys are changed following their respective buttons Activate or Hold have been pressed. Afterwards the unit automatically reboots itself. 120 RipEX Radio modem & Router – © RACOM s.r.o. 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. The following items are NOT cleared when the Factorry settings are applied: 1. Technical support package 2. Firmware archive 3. Configuration backup 4. Folder /home/… in Linux When you need to reset the device access parameters (the login, password and ethernet IP) to defaults, press the RESET button on the bottom-side of RipEX enclosure for 15 sec. More in Section 4.2.6, “Reset button”. • FILE ○ Save to file – saves the active configuration into a file. Configuration can be uploaded from a file. Fill in the file path, or browse your disk in order to find the file. When a file is selected, it can be uploaded. ○ Upload – uploads configuration from the selected file and activates it. The unit reboots itself afterwards. 7.6.3. Firmware Fig. 7.18: Menu Maintenance Firmware The firmware in the unit consists of several parts, however they come in one firmware package (file_name.cpio). Individual part names and their versions can be seen. There can be two versions of firmware packages stored within the unit – “Active” and “Archive”. Unit is always using the Active version. The Archive version is there just for convenience and safety of firmware manipulations. It can also be uploaded to a remote unit over the Radio channel. • Upload to Archive – Fill in the file path, or browse your disk in order to find the file. When a file is selected and the “Upload to Archive” button pressed, it is uploaded and becomes the Archive firmware. © RACOM s.r.o. – RipEX Radio modem & Router 121 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. Fill in the IP address of the desired unit and press the button. Note If possible, copy FW only over one Radio hop where radio link is quality sufficiently high. Otherwise it can be very time consuming. When Router mode is used, don’t forget to set correct Routing tables settings. 7.6.4. Password Fig. 7.19: Menu Maintenance Password It is highly recommended to change default password (admin) even if the user name remains always the same (admin). When the Apply button is pressed, the unit reboots. 7.6.5. Miscellaneous • Reboot – when pressed, the unit correctly shuts down and starts again (performs the cold start which equals to a power cycle). The reboot time is approx. 25 sec. 7.6.6. Technical support package Fig. 7.20: Menu Maintenance Configuration 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. • Log depth List box: possible values Default = 500 This is the number of rows downloaded. The greater the number of rows, the longer the history to be found in the file. However more lines means greater file size as well. When downloaded from a remote unit over Radio channel in poor signal conditions, a lower Log depth should be selected. 122 RipEX Radio modem & Router – © RACOM s.r.o. 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. Connecting with a putty client. Type the following command into the window Host Name (or IP address): admin@192.168.169.169 Press Open. Then enter the password admin. Thu Mar 31 10:56:47 CEST 2011 Welcome to RipEX Command Line Interface (CLI) on station: RipEX 50 For help try: cli_help CLI(admin):~$ The cli_help command shows a list of all available functions. The commands can be completed using the Tab key. If you select the command with the left mouse button, you can copy it to the clipboard and then use the right mouse button to insert it into the location of the cursor. You can use the -t parameter to send commands to remote RipEX’s. Every command gives a comprehensive help when invoked with -h or –help parameter. An example of a parameter request for the COM1 port of the RipEX with IP 192.168.1.1: CLI(admin):~$ cli_cnf_show_com 1 -t 192.168.1.1 COM UDP port setting: Default (d) COM UDP port (manual): 50001 COM link type: RS232 (RS232) COM bitrate: 19200 (19200) COM data bits: 8 (8) COM parity: None (n) COM stop bits: 1 (1) COM idle size: 5 chars COM MTU: 1600 bytes COM handshake: None (n) COM break length: 1000 chars COM protocol: None (n) 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. © RACOM s.r.o. – RipEX Radio modem & Router 123 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. Note that, in addition to resseting access parameters to defaults, your firewall rules will be cleared as well. My PC is unable to connect to the RipEX. • In PC settings, Network protocol (TCP/IP)/Properties, the following configuration is sometimes used: General tab - Automatically receive address from a DHCP server Alternate configuration tab - User defined configuration, e.g. 192.168.169.250 Use this configuration instead: General tab - Use the following IP, e.g. 192.168.169.250 • Verify your PC’s IP address from the command line: Start/Run/command ipconfig Send a ping to the RipEX: ping 192.168.169.169 3. If the ping runs successfully, look for a problem with the browser configuration. Sometimes the browser may need minutes to make new connection. I’m configuring the RipEX in its default state but it’s not working. 4. • There is another RipEX with the default configuration in close vicinity. Switch it off. I have configured one RipEX in its default state. But I cannot connect to another. • Your PC keeps a table of IP addresses and their associated MAC addresses. You can view it from the command line: Start/Run/command arp -a IP address 192.168.169.169 physical address type 00-02-a9-00-fe-2c dynamic All RipEX’s share the default IP address but their MAC addresses are different, meaning this record interferes with your purpose. The timeout for automatic cache clearing may be longer so you can delete the entry manually by typing: 124 RipEX Radio modem & Router – © RACOM s.r.o. 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. Use higher output, a unidirectional antenna, better direct the antenna, use a better feed line, taller pole. If nothing helps, lower the speed. The RSS Ping test reports good RSS but low DQ. • 9. When the DQ value is much lower then it should be at the given RSS, typicaly it is a case of multi-path propagation. It can cause serious problems to data communication, especially when high data rates are used. Since the interfering signals come from different directions, changing the direction of the antenna may solve the problem. A unidirectional antenna should be used in the first place. Metallic objects in close vicinity of the antenna may cause harmful reflections, relocating the antenna by few meters may help. Change of polarization at both ends of the link could be the solution as well. The RSS Ping test shows bad homogeneity. • Quite often the bad homogeneity comes together with a low DQ. In that case follow the advice given in the previous paragraph. If the DQ does correspond to the RSS level, you should look for unstable elements along the signal route – a poorly installed antenna or cable, moving obstacles (e.g. cars in front of the antenna), shifting reflective areas etc. If you cannot remove the cause of disturbances, you will need to ensure signal is strong enough to cope with it. © RACOM s.r.o. – RipEX Radio modem & Router 125 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. These frequencies are used for distress beacons and are incessantly monitored by the ground and satellite Cospas-Sarsat system. Other use of these frequencies is forbidden. 10.2. Safety distance Safety distances with respect to the US health limits of the electromagnetic field intensity are in Minimum Safety Distance tables below, calculated for different antennas and RipEX power levels. The distances were calculated according to (doplnit normu) and apply to 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. For output power 0.2 W or lower the safety limit is not exceeded at any distance and any of the antennas. The minimal safe distance is typically ensured by the antenna position on a mast. When special installation is required, the conditions of the standard EN 50385: 2002 have to be met. The distance between the persons and antenna shown in the table bellow comply with all applicable standards for human exposure of general public to RF electromagnetic fields. Tab. 10.1: Minimum Safety Distance 160 MHz 160 MHz/2 m band – 10 W RF power Dist. where the FCC limits are met for Antenna code Antenna description Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] OV160.1 single dipole 4.6 2.9 190 90 OV160.2 stacked double dipole 7.6 5.8 270 120 SA160.3 5 element directional Yagi 8.0 6.3 280 130 SA160.5 9 element directional Yagi 12.5 17.8 460 210 160 MHz/2 m band – 5 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV160.1 single dipole 4.6 2.9 140 60 OV160.2 stacked double dipole 7.6 5.8 190 90 126 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] RipEX Radio modem & Router – © RACOM s.r.o. 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.8 290 130 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] 160 MHz/2 m band – 3 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] Antenna code Antenna description OV160.1 single dipole 4.6 2.9 110 45 OV160.2 stacked double dipole 7.6 5.8 150 70 SA160.3 5 element directional Yagi 8.0 6.3 150 70 SA160.5 9 element directional Yagi 12.5 17.8 260 120 160 MHz/2 m band – 2 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] Antenna code Antenna description OV160.1 single dipole 4.6 2.9 90 40 OV160.2 stacked double dipole 7.6 5.8 120 60 SA160.3 5 element directional Yagi 8.0 6.3 130 60 SA160.5 9 element directional Yagi 12.5 17.8 210 100 160 MHz/2 m band – 1 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] Antenna code Antenna description OV160.1 single dipole 4.6 2.9 60 30 OV160.2 stacked double dipole 7.6 5.8 90 40 SA160.3 5 element directional Yagi 8.0 6.3 90 40 SA160.5 9 element directional Yagi 12.5 17.8 150 70 © RACOM s.r.o. – RipEX Radio modem & Router 127 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.2: Minimum Safety Distance 300–400 MHz 300–400 MHz/70 cm band – 10 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV380.1 single dipole 4.6 2.9 130 60 OV380.2 stacked double dipole 7.6 5.8 180 80 SA380.3 3 element directional Yagi 7.6 5.8 180 80 SA380.5 5 element directional Yagi 8.7 7.4 200 90 SA380.9 9 element directional Yagi 12.5 17.8 310 140 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] 300–400 MHz/70 cm band – 5 W RF power Dist. where the FCC limits are met for Antenna code Antenna description Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] OV380.1 single dipole 4.6 2.9 90 40 OV380.2 stacked double dipole 7.6 5.8 130 60 SA380.3 3 element directional Yagi 7.6 5.8 130 60 SA380.5 5 element directional Yagi 8.7 7.4 140 70 SA380.9 9 element directional Yagi 12.5 17.8 220 100 300–400 MHz/70 cm band – 4 W RF power Dist. where the FCC limits are met for Antenna code Antenna description OV380.1 single dipole 4.6 2.9 80 35 OV380.2 stacked double dipole 7.6 5.8 110 50 SA380.3 3 element directional Yagi 7.6 5.8 110 50 SA380.5 5 element directional Yagi 8.7 7.4 130 60 128 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposure [cm] posure [cm] RipEX Radio modem & Router – © RACOM s.r.o. 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.8 170 80 Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] 300–400 MHz/70 cm band – 2 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] Antenna code Antenna description OV380.1 single dipole 4.6 2.9 60 25 OV380.2 stacked double dipole 7.6 5.8 80 35 SA380.3 3 element directional Yagi 7.6 5.8 80 35 SA380.5 5 element directional Yagi 8.7 7.4 90 40 SA380.9 9 element directional Yagi 12.5 17.8 140 70 300–400 MHz/70 cm band – 1 W RF power Dist. where the FCC limits are met for Antenna code Antenna description Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] OV380.1 single dipole 4.6 2.9 40 20 OV380.2 stacked double dipole 7.6 5.8 60 25 SA380.3 3 element directional Yagi 7.6 5.8 60 25 SA380.5 5 element directional Yagi 8.7 7.4 70 30 SA380.9 9 element directional Yagi 12.5 17.8 100 50 300–400 MHz/70 cm band – 0.5 W RF power Dist. where the FCC limits are met for Antenna code Antenna description Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposposure [cm] ure [cm] OV380.1 single dipole 4.6 2.9 30 15 OV380.2 stacked double dipole 7.6 5.8 40 20 © RACOM s.r.o. – RipEX Radio modem & Router 129 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. RoHS and WEEE compliance The RipEX is fully compliant with the European Commission‟s RoHS (Restriction of Certain Hazardous Substances in Electrical and Electronic Equipment) and WEEE (Waste Electrical and Electronic Equipment) environmental directives. Restriction of hazardous substances (RoHS) The RoHS Directive prohibits the sale in the European Union of electronic equipment containing these hazardous substances: lead, cadmium, mercury, hexavalent chromium, polybrominated biphenyls (PBBs), and polybrominated diphenyl ethers (PBDEs). End-of-life recycling programme (WEEE) The WEEE Directive concerns the recovery, reuse, and recycling of electronic and electrical equipment. Under the Directive, used equipment must be marked, collected separately, and disposed of properly. Racom has instigated a programme to manage the reuse, recycling, and recovery of waste in an environmentally safe manner using processes that comply with the WEEE Directive (EU Waste Electrical and Electronic Equipment 2002/96/EC). The WEEE Directive concerns the recovery, reuse, and recycling of electronic and electrical equipment. Under the Directive, used equipment must be marked, collected separately, and disposed of properly. Racom has instigated a programme to manage the reuse, recycling, and recovery of waste in an environmentally safe manner using processes that comply with the WEEE Directive (EU Waste Electrical and Electronic Equipment 2002/96/EC). Battery Disposal—This product may contain a battery. Batteries must be disposed of properly, and may not be disposed of as unsorted municipal waste in the European Union. See the product documentation for specific battery information. Batteries are marked with a symbol, which may include lettering to indicate cadmium (Cd), lead (Pb), or mercury (Hg). For proper recycling return the battery to your supplier or to a designated collection point. For more information see: www.weeerohsinfo.com 10.5. Conditions of Liability for Defects and Instructions for Safe Operation of Equipment Please read these safety instructions carefully before using the product: 130 RipEX Radio modem & Router – © RACOM s.r.o. 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. The radio equipment can only be operated on frequencies stipulated by the body authorised by the radio operation administration in the respective country and cannot exceed the maximum permitted output power. RACOM is not responsible for products used in an unauthorised way. Equipment mentioned in this operator manual may only be used in accordance with instructions contained in this manual. Error-free and safe operation of this equipment is only guaranteed if this equipment is transported, stored, operated and controlled in the proper manner. The same applies to equipment maintenance. In order to prevent damage to the radio modem and other terminal equipment the supply must always be disconnected upon connecting or disconnecting the cable to the radio modem data interface. It is necessary to ensure that connected equipment has been grounded to the same potential. Only undermentioned manufacturer is entitled to repair any devices. 10.6. 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 reproduced 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. RACOM reserves the right to make changes in the technical specification or in this product function or to terminate production of this product or to terminate its service support without previous written notification of customers. Conditions of use of this product software abide by the license mentioned below. The program spread by this license has been freed with the purpose to be useful, but without any specific guarantee. The author or another company or person is not responsible for secondary, accidental or related damages resulting from application of this product under any circumstances. The maker does not provide the user with any kind of guarantee containing assurance of suitability and usability for his application. Products are not developed, designed nor tested for utilization in devices directly affecting health and life functions of persons and animals, nor as a part of another important device, and no guarantees apply if the company product has been used in these aforementioned devices. RACOM Open Software License Version 1.0, November 2009 Copyright (c) 2001, RACOM s.r.o., Mírová 1283, Nové Město na Moravě, 592 31 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 licences, declarations of responsibility exclusion and notifications. Exact terms of GPL, LGPL and some further licences is mentioned in source code packets (typically the files COPYING or LICENSE). You can obtain applicable machine-readable copies of source code of this software under GPL or LGPL li- © RACOM s.r.o. – RipEX Radio modem & Router 131 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. Product Conformity RACOM declares that the RipEX radio modem & router is in conformity with the essential requirements and other relevant requirements of the Directive of the European Parliament and of the Council 1999/5/EC on radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity. The RipEX radio modem & router has been type accepted for operation by the Federal Communications Commission in accordance with Title 47 Part90 of the FCC rules. See the label on the unit for the specific FCC ID and any other certification designations. 132 RipEX Radio modem & Router – © RACOM s.r.o. OID mappings Appendix A. OID mappings "MIB tables", and whole file "OID mappings" can be downloaded from: http://www.racom.eu/eng/products/radio-modem-ripex.html#download http://hnilux.racom.cz:3004/eng/products/radio-modem-ripex.html#download © RACOM s.r.o. – RipEX Radio modem & Router 133 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.3 column COM interface MTU in bytes. comProtocol 1.3.6.1.4.1.33555.2.2.5.2.1.4 column COM interface protocol. device 1.3.6.1.4.1.33555.2.1.1 node deviceCode 1.3.6.1.4.1.33555.2.1.1.3 scalar Device type. deviceMode 1.3.6.1.4.1.33555.2.1.1.5 scalar Station working mode. deviceType 1.3.6.1.4.1.33555.2.1.1.2 scalar Device type. eBCastMCast 1.3.6.1.4.1.33555.2.2.2.4 scalar Ethernet interface broadcast and multicast status. eDhcp 1.3.6.1.4.1.33555.2.2.2.2 scalar Ethernet interface DHCP mode. eGateway 1.3.6.1.4.1.33555.2.2.2.1 scalar Ethernet interface gateway address. eShaping 1.3.6.1.4.1.33555.2.2.2.3 scalar Ethernet interface shaping status. eSpeed 1.3.6.1.4.1.33555.2.2.2.5 scalar Ethernet bit rate and duplex settings. hwVerModem 1.3.6.1.4.1.33555.2.1.1.6.1 scalar HW version of the modem. hwVerRadio 1.3.6.1.4.1.33555.2.1.1.6.2 scalar HW version of the radio. hwVersions 1.3.6.1.4.1.33555.2.1.1.6 node ifCom 1.3.6.1.4.1.33555.2.2.5 node ifComEntry 1.3.6.1.4.1.33555.2.2.5.2.1 row ifComNumber 1.3.6.1.4.1.33555.2.2.5.1 scalar The number of COM interfaces. ifComTable 1.3.6.1.4.1.33555.2.2.5.2 table A list of COM interface entries. A COM interface entry. ifEth 1.3.6.1.4.1.33555.2.2.2 node ifRadio 1.3.6.1.4.1.33555.2.2.1 node ifTcpMod 1.3.6.1.4.1.33555.2.2.3 node ifTermServ 1.3.6.1.4.1.33555.2.2.4 node ifTmATM 1.3.6.1.4.1.33555.2.2.3.5 scalar Tcp Modbus COM protocol address translation mode. ifTmBCast 1.3.6.1.4.1.33555.2.2.3.4 scalar Tcp Modbus COM protocol broadcast accept. ifTmEnable 1.3.6.1.4.1.33555.2.2.3.1 scalar Tcp Modbus status. ifTmPort 1.3.6.1.4.1.33555.2.2.3.2 scalar Tcp Modbus port. ifTmTimeout 1.3.6.1.4.1.33555.2.2.3.3 scalar Tcp Modbus socket timeout in seconds. ifTsEnable 1.3.6.1.4.1.33555.2.2.4.1 scalar Terminal server status. ifTsEntry 1.3.6.1.4.1.33555.2.2.4.3.1 row A Terminal server interface entry. ifTsNumber 1.3.6.1.4.1.33555.2.2.4.2 scalar The number of Terminal server interfaces. ifTsTable 1.3.6.1.4.1.33555.2.2.4.3 table A list of Terminal server interface entries. interface 1.3.6.1.4.1.33555.2.2 node rEncryption 1.3.6.1.4.1.33555.2.2.1.4 scalar rFEC 1.3.6.1.4.1.33555.2.2.1.5 scalar Radio interface FEC. rRfPwr 1.3.6.1.4.1.33555.2.2.1.3 scalar Radio interface RF Power. rRxFrequency 1.3.6.1.4.1.33555.2.2.1.1 scalar Radio interface RX frequency in Hz. rTxFrequency 1.3.6.1.4.1.33555.2.2.1.2 scalar Radio interface TX frequency in Hz. ripex 1.3.6.1.4.1.33555.2 node Radio interface encryption method. ripextraps 1.3.6.1.4.1.33555.2.10 node serialNumber 1.3.6.1.4.1.33555.2.1.1.4 scalar stCom 1.3.6.1.4.1.33555.2.3.4 node stComBytesRX 1.3.6.1.4.1.33555.2.3.4.2.1.4 column stComBytesTX 1.3.6.1.4.1.33555.2.3.4.2.1.5 column COM TX bytes counter. stComEntry 1.3.6.1.4.1.33555.2.3.4.2.1 row A COM port entry. stComIndex 1.3.6.1.4.1.33555.2.3.4.2.1.1 column The COM port index. stComNumber 1.3.6.1.4.1.33555.2.3.4.1 scalar The number of COM ports. stComPacketsRX 1.3.6.1.4.1.33555.2.3.4.2.1.2 column COM RX packets counter. stComPacketsTX 1.3.6.1.4.1.33555.2.3.4.2.1.3 column COM TX packets counter. Manufactoring serial number of the product. COM RX bytes counter. Page 1 134 RipEX Radio modem & Router – © RACOM s.r.o. 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.4.1.33555.2.3.1.1.11 scalar Remote station total TX bytes counter. stRadioTotCtlPacketsRX 1.3.6.1.4.1.33555.2.3.1.1.4 scalar Total RX radio control packets counter. stRadioTotCtlPacketsTX 1.3.6.1.4.1.33555.2.3.1.1.5 scalar Total TX radio control packets counter. stRadioTotDataErr 1.3.6.1.4.1.33555.2.3.1.1.6 scalar Total radio data error packets counter. stRadioTotDuplicates 1.3.6.1.4.1.33555.2.3.1.1.1 scalar Total radio duplicate packets counter. stRadioTotFalseSync 1.3.6.1.4.1.33555.2.3.1.1.15 scalar Total radio false sync counter. stRadioTotHeadErr 1.3.6.1.4.1.33555.2.3.1.1.14 scalar Total radio header error packets counter. stRadioTotIpErr 1.3.6.1.4.1.33555.2.3.1.1.12 scalar Total radio IP error packets counter. stRadioTotLost 1.3.6.1.4.1.33555.2.3.1.1.3 scalar Total radio lost packets counter. stRadioTotPacketsRX 1.3.6.1.4.1.33555.2.3.1.1.8 scalar Remote station total RX packets counter. stRadioTotPacketsTX 1.3.6.1.4.1.33555.2.3.1.1.9 scalar Remote station total TX packets counter. stRadioTotRejected 1.3.6.1.4.1.33555.2.3.1.1.7 scalar Total radio rejected packets counter. stRadioTotRepeats 1.3.6.1.4.1.33555.2.3.1.1.2 scalar Total radio repeated packets counter. stRadioTotSubHeadErr 1.3.6.1.4.1.33555.2.3.1.1.13 scalar Total radio subheader error packets counter. stRadioTotal 1.3.6.1.4.1.33555.2.3.1.1 node stRemBytesRX 1.3.6.1.4.1.33555.2.3.1.3.1.5 column Remote station RX bytes counter. stRemBytesTX 1.3.6.1.4.1.33555.2.3.1.3.1.6 column Remote station TX bytes counter. stRemCtlPacketsRX 1.3.6.1.4.1.33555.2.3.1.3.1.10 column Remote station RX radio control packets counter. stRemCtlPacketsTX 1.3.6.1.4.1.33555.2.3.1.3.1.11 column Remote staion TX radio control packets counter. stRemDataErr 1.3.6.1.4.1.33555.2.3.1.3.1.12 column Remote station data error packets counter. stRemDuplicates 1.3.6.1.4.1.33555.2.3.1.3.1.7 column Remote station duplicate packets counter. stRemIndex 1.3.6.1.4.1.33555.2.3.1.3.1.1 column Remote station index. stRemIpAddr 1.3.6.1.4.1.33555.2.3.1.3.1.2 column Remote station IP address. stRemLost 1.3.6.1.4.1.33555.2.3.1.3.1.9 column Remote station lost packets counter. stRemPacketsRX 1.3.6.1.4.1.33555.2.3.1.3.1.3 column Remote station RX packets counter. stRemPacketsTX 1.3.6.1.4.1.33555.2.3.1.3.1.4 column Remote station TX packets counter. stRemRejected 1.3.6.1.4.1.33555.2.3.1.3.1.13 column Remote station rejected packets counter. stRemRepeats 1.3.6.1.4.1.33555.2.3.1.3.1.8 column Remote station repeated packets counter. stRemTotalBytesRX 1.3.6.1.4.1.33555.2.3.1.3.1.16 column Remote station total RX bytes counter. stRemTotalBytesTX 1.3.6.1.4.1.33555.2.3.1.3.1.17 column Remote station total TX bytes counter. stRemTotalPacketsRX 1.3.6.1.4.1.33555.2.3.1.3.1.14 column Remote station total RX packets counter. stRemTotalPacketsTX 1.3.6.1.4.1.33555.2.3.1.3.1.15 column Remote station total TX packets counter. stTcpMod 1.3.6.1.4.1.33555.2.3.2 node stTcpModBytesRX 1.3.6.1.4.1.33555.2.3.2.2.1.4 column TCP Modbus RX bytes counter. stTcpModBytesTX 1.3.6.1.4.1.33555.2.3.2.2.1.5 column TCP Modbus TX bytes counter. stTcpModEntry 1.3.6.1.4.1.33555.2.3.2.2.1 row A TCP Modbus port entry. stTcpModIndex 1.3.6.1.4.1.33555.2.3.2.2.1.1 column The TCP Modbus port index. stTcpModNumber 1.3.6.1.4.1.33555.2.3.2.1 scalar The number of TCP Modbus ports. stTcpModPacketsRX 1.3.6.1.4.1.33555.2.3.2.2.1.2 column TCP Modbus RX packets counter. stTcpModPacketsTX 1.3.6.1.4.1.33555.2.3.2.2.1.3 column TCP Modbus TX packets counter. stTcpModTable 1.3.6.1.4.1.33555.2.3.2.2 table A list of TCP Modbus port entries. stTermServ 1.3.6.1.4.1.33555.2.3.3 node stTermServBytesRX 1.3.6.1.4.1.33555.2.3.3.2.1.4 column Terminal Server RX bytes counter. stTermServBytesTX 1.3.6.1.4.1.33555.2.3.3.2.1.5 column Terminal Server TX bytes counter. stTermServEntry 1.3.6.1.4.1.33555.2.3.3.2.1 row A Terminal Server port entry. stTermServIndex 1.3.6.1.4.1.33555.2.3.3.2.1.1 column The Terminal Server port index. stTermServNumber 1.3.6.1.4.1.33555.2.3.3.1 scalar The number of Terminal Server ports. stTermServPacketsRX 1.3.6.1.4.1.33555.2.3.3.2.1.2 column Terminal Server RX packets counter. stTermServPacketsTX 1.3.6.1.4.1.33555.2.3.3.2.1.3 column Terminal Server TX packets counter. stTermServTable 1.3.6.1.4.1.33555.2.3.3.2 table A list of Terminal Server port entries. station 1.3.6.1.4.1.33555.2.1 node stationName 1.3.6.1.4.1.33555.2.1.1.1 scalar statistics 1.3.6.1.4.1.33555.2.3 node swVerBootloader 1.3.6.1.4.1.33555.2.1.1.7.4 scalar Name of the station. Bootloader version. Page 2 © RACOM s.r.o. – RipEX Radio modem & Router 135 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. tsEthProtDestIP 1.3.6.1.4.1.33555.2.2.4.3.1.6 column Terminal server partner's IP address. tsEthProtDestPort 1.3.6.1.4.1.33555.2.2.4.3.1.7 column Terminal server partner's destination TCP/UDP port. tsEthProtMyPort 1.3.6.1.4.1.33555.2.2.4.3.1.5 column Terminal server ethernet protocol socket TCP/UDP port. tsEthProtTimeout 1.3.6.1.4.1.33555.2.2.4.3.1.4 column Terminal server ethernet protocol socket timeout in seconds. tsEthProtType 1.3.6.1.4.1.33555.2.2.4.3.1.3 column Terminal server ethernet protocol type. tsIndex 1.3.6.1.4.1.33555.2.2.4.3.1.1 column A unique index for each interface. useCpu1 1.3.6.1.4.1.33555.2.1.2.1 scalar Average number of processes during last 1 minute. useCpu15 1.3.6.1.4.1.33555.2.1.2.3 scalar Average number of processes during last 15 minutes. useCpu5 1.3.6.1.4.1.33555.2.1.2.2 scalar Average number of processes during last 5 minutes. useLogStorage 1.3.6.1.4.1.33555.2.1.2.5 scalar Use storage for log in %. useMemory 1.3.6.1.4.1.33555.2.1.2.4 scalar System use memory in %. watchedValues 1.3.6.1.4.1.33555.2.4 node wvLoadAvg 1.3.6.1.4.1.33555.2.4.1.4 scalar Local station - average load value in hundredths of %. wvLoadLast 1.3.6.1.4.1.33555.2.4.1.3 scalar Local station - last load value in %. wvLocal 1.3.6.1.4.1.33555.2.4.1 node wvNoiseAvg 1.3.6.1.4.1.33555.2.4.1.2 scalar wvNoiseLast 1.3.6.1.4.1.33555.2.4.1.1 scalar Local station - last noise value in dBm. wvRemDqAvg 1.3.6.1.4.1.33555.2.4.3.1.7 column Remote station - average dq value hundredths. Local station - average noise value in hundredths of dBm. wvRemDqLast 1.3.6.1.4.1.33555.2.4.3.1.6 column Remote station - last dq value. wvRemHearings 1.3.6.1.4.1.33555.2.4.3.1.3 column Total heared packets from remote station. wvRemIndex 1.3.6.1.4.1.33555.2.4.3.1.1 column A unique index for each remote station. wvRemIpAddr 1.3.6.1.4.1.33555.2.4.3.1.2 column IP address of remote station. wvRemLoadAvg 1.3.6.1.4.1.33555.2.4.3.1.11 column Remote station - average load value in hundredths of %. wvRemLoadLast 1.3.6.1.4.1.33555.2.4.3.1.10 column Remote station - last load value in %. wvRemNoiseAvg 1.3.6.1.4.1.33555.2.4.3.1.9 column Remote station - average noise value in hundredths of dBm. wvRemNoiseLast 1.3.6.1.4.1.33555.2.4.3.1.8 column Remote station - last noise value in dBm. wvRemRfpwrAvg 1.3.6.1.4.1.33555.2.4.3.1.19 column Remote station - average RF power value in thousandths of W. wvRemRfpwrLast 1.3.6.1.4.1.33555.2.4.3.1.18 column Remote station - last RF power value in tenths of W. wvRemRssAvg 1.3.6.1.4.1.33555.2.4.3.1.5 column Remote station - average rss value in hundredths of dBm. wvRemRssLast 1.3.6.1.4.1.33555.2.4.3.1.4 column Remote station - last rss value in dBm. wvRemTempAvg 1.3.6.1.4.1.33555.2.4.3.1.17 column Remote station - average modem temperature value in thousandths of C. wvRemTempLast 1.3.6.1.4.1.33555.2.4.3.1.16 column Remote station - last modem temperature value in tenths of C. wvRemTxlostAvg 1.3.6.1.4.1.33555.2.4.3.1.13 column Remote station - average Tx Lost value in hundredths of %. wvRemTxlostLast 1.3.6.1.4.1.33555.2.4.3.1.12 column Remote station - last Tx Lost value in %. wvRemUccAvg 1.3.6.1.4.1.33555.2.4.3.1.15 column Remote station - average Ucc value in thousandths of Volt. wvRemUccLast 1.3.6.1.4.1.33555.2.4.3.1.14 column Remote station - last Ucc value in tenths of Volt. wvRemVswrAvg 1.3.6.1.4.1.33555.2.4.3.1.21 column Remote station - average VSWR value from interval <3, 25> in thousandths. wvRemVswrLast 1.3.6.1.4.1.33555.2.4.3.1.20 column Remote station - last VSWR value from interval <3, 25> in tenths. wvRemoteEntry 1.3.6.1.4.1.33555.2.4.3.1 row A remote station watched values entry. wvRemoteNumber 1.3.6.1.4.1.33555.2.4.2 scalar The number of remote stations. wvRemoteTable 1.3.6.1.4.1.33555.2.4.3 table A list of remote stations. wvRfpwrAvg 1.3.6.1.4.1.33555.2.4.1.12 scalar Local station - average RF power value in thousandths of W. wvRfpwrLast 1.3.6.1.4.1.33555.2.4.1.11 scalar Local station - last RF power value in tenths of W. wvTempAvg 1.3.6.1.4.1.33555.2.4.1.10 scalar Local station - average modem temperature value in thousandths of C. wvTempLast 1.3.6.1.4.1.33555.2.4.1.9 scalar Local station - last modem temperature value in tenths of C. wvTxlostAvg 1.3.6.1.4.1.33555.2.4.1.6 scalar Local station - average Tx Lost value in hundredths of %. wvTxlostLast 1.3.6.1.4.1.33555.2.4.1.5 scalar Local station - last Tx Lost value in %. wvUccAvg 1.3.6.1.4.1.33555.2.4.1.8 scalar Local station - average Ucc value in thousandths of Volt. wvUccLast 1.3.6.1.4.1.33555.2.4.1.7 scalar Local station - last Ucc value in tenths of Volt. wvVswrAvg 1.3.6.1.4.1.33555.2.4.1.14 scalar Local station - average VSWR value from interval <3, 25> in thousandths. wvVswrLast 1.3.6.1.4.1.33555.2.4.1.13 scalar Local station - last VSWR value from interval <3, 25> in tenths. TRAPS: Page 3 136 RipEX Radio modem & Router – © RACOM s.r.o. 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.10 notification Ethernet Rx/Tx packet ratio out of range. trpLoad 1.3.6.1.4.1.33555.2.10.4 notification Load value out of range. trpNoise 1.3.6.1.4.1.33555.2.10.3 notification Noise value out of range. trpRfpwr 1.3.6.1.4.1.33555.2.10.8 notification RF power value out of range trpRss 1.3.6.1.4.1.33555.2.10.1 notification RSS of remote station is out of range. trpTemp 1.3.6.1.4.1.33555.2.10.7 notification Modem temperature value out of range. trpTxlost 1.3.6.1.4.1.33555.2.10.5 notification Tx Lost value out of range. trpUcc 1.3.6.1.4.1.33555.2.10.6 notification Ucc value out of range. trpVswr 1.3.6.1.4.1.33555.2.10.9 notification VSWR value out of range. Page 4 © RACOM s.r.o. – RipEX Radio modem & Router 137 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., the IP address) corresponding to the media-dependent `physical' Address. atIfIndex atNetAddress 1.3.6.1.2.1.3.1.1.1 1.3.6.1.2.1.3.1.1.3 The media-dependent `physical' address. atPhysAddress 1.3.6.1.2.1.3.1.1.2 column Setting this object to a null string (one of zero length) has the effect of invaliding the corresponding entry in the atTable object. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atPhysAddress object. table The Address Translation tables contain the NetworkAddress to `physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. atTable 1.3.6.1.2.1.3.1 egp 1.3.6.1.2.1.8 node egpAs 1.3.6.1.2.1.8.6 scalar The autonomous system number of this EGP entity. egpInErrors 1.3.6.1.2.1.8.2 scalar The number of EGP messages received that proved to be in error. egpInMsgs 1.3.6.1.2.1.8.1 scalar The number of EGP messages received without Error. egpNeighAddr 1.3.6.1.2.1.8.5.1.2 column The IP address of this entry's EGP neighbor. egpNeighAs 1.3.6.1.2.1.8.5.1.3 column The autonomous system of this EGP peer. Zero should be specified if the autonomous system number of the neighbor is not yet known. egpNeighEntry 1.3.6.1.2.1.8.5.1 row Information about this entity's relationship with a particular EGP neighbor. A control variable used to trigger operatorinitiated Start and Stop events. When read, this variable always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set since the last initialization of the network management subsystem on the node, it returns a value of `stop'. egpNeighEventTrigger 1.3.6.1.2.1.8.5.1.15 column When set, this variable causes a Start or Stop event on the specified neighbor, as specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to the Idle state until a Start event occurs, either via egpNeighEventTrigger or Otherwise. Page 5 138 RipEX Radio modem & Router – © RACOM s.r.o. 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.12 column The interval between EGP Hello command retransmissions (in hundredths of a second). This represents the t1 timer as defined in RFC 904. egpNeighIntervalPoll 1.3.6.1.2.1.8.5.1.13 column The interval between EGP poll command retransmissions (in hundredths of a second). This represents the t3 timer as defined in RFC 904. egpNeighMode 1.3.6.1.2.1.8.5.1.14 column The polling mode of this EGP entity, either passive or active. egpNeighOutErrMsgs 1.3.6.1.2.1.8.5.1.9 column The number of EGP-defined error messages sent to this EGP peer. egpNeighOutErrs 1.3.6.1.2.1.8.5.1.7 column The number of locally generated EGP messages not sent to this EGP peer due to resource limitations within an EGP entity. egpNeighOutMsgs 1.3.6.1.2.1.8.5.1.6 column The number of locally generated EGP messages to this EGP peer. egpNeighState 1.3.6.1.2.1.8.5.1.1 column The EGP state of the local system with respect to this entry's EGP neighbor. Each EGP state is represented by a value that is one greater than the numerical value associated with said state in RFC 904. egpNeighStateDowns 1.3.6.1.2.1.8.5.1.11 column The number of EGP state transitions from the UP state to any other state with this EGP peer. egpNeighStateUps 1.3.6.1.2.1.8.5.1.10 column The number of EGP state transitions to the UP state with this EGP peer. egpNeighTable 1.3.6.1.2.1.8.5 table The EGP neighbor table. scalar The number of locally generated EGP messages not sent due to resource limitations within an EGP Entity. egpOutErrors 1.3.6.1.2.1.8.4 The total number of locally generated EGP messages. egpOutMsgs 1.3.6.1.2.1.8.3 scalar icmp 1.3.6.1.2.1.5 node icmpInAddrMaskReps 1.3.6.1.2.1.5.13 scalar The number of ICMP Address Mask Reply messages Received. icmpInAddrMasks 1.3.6.1.2.1.5.12 scalar The number of ICMP Address Mask Request messages Received. icmpInDestUnreachs 1.3.6.1.2.1.5.3 scalar The number of ICMP Destination Unreachable messages received. icmpInEchoReps 1.3.6.1.2.1.5.9 scalar The number of ICMP Echo Reply messages received. icmpInEchos 1.3.6.1.2.1.5.8 scalar The number of ICMP Echo (request) messages Received. icmpInErrors 1.3.6.1.2.1.5.2 scalar The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.). icmpInMsgs 1.3.6.1.2.1.5.1 scalar The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors. icmpInParmProbs 1.3.6.1.2.1.5.5 scalar The number of ICMP Parameter Problem messages Received. icmpInRedirects 1.3.6.1.2.1.5.7 scalar The number of ICMP Redirect messages received. icmpInSrcQuenchs 1.3.6.1.2.1.5.6 scalar The number of ICMP Source Quench messages Received. icmpInTimeExcds 1.3.6.1.2.1.5.4 scalar The number of ICMP Time Exceeded messages Received. icmpInTimestampReps 1.3.6.1.2.1.5.11 scalar The number of ICMP Timestamp Reply messages Received. icmpInTimestamps 1.3.6.1.2.1.5.10 scalar The number of ICMP Timestamp (request) messages Received. icmpOutAddrMaskReps 1.3.6.1.2.1.5.26 scalar The number of ICMP Address Mask Reply messages Sent. Page 6 © RACOM s.r.o. – RipEX Radio modem & Router 139 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.15 scalar The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's Value. icmpOutMsgs 1.3.6.1.2.1.5.14 scalar The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors. icmpOutParmProbs 1.3.6.1.2.1.5.18 scalar The number of ICMP Parameter Problem messages sent. icmpOutRedirects 1.3.6.1.2.1.5.20 scalar The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects. icmpOutSrcQuenchs 1.3.6.1.2.1.5.19 scalar The number of ICMP Source Quench messages sent. icmpOutTimeExcds 1.3.6.1.2.1.5.17 scalar The number of ICMP Time Exceeded messages sent. icmpOutTimestampReps 1.3.6.1.2.1.5.24 scalar The number of ICMP Timestamp Reply messages sent. icmpOutTimestamps 1.3.6.1.2.1.5.23 scalar The number of ICMP Timestamp (request) messages sent. column The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. column A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the hardware interface. row An interface entry containing objects at the subnetwork layer and below for a particular Interface. column The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. ifAdminStatus ifDescr ifEntry ifInDiscards 1.3.6.1.2.1.2.2.1.7 1.3.6.1.2.1.2.2.1.2 1.3.6.1.2.1.2.2.1 1.3.6.1.2.1.2.2.1.13 ifInErrors 1.3.6.1.2.1.2.2.1.14 column The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. ifInNUcastPkts 1.3.6.1.2.1.2.2.1.12 column The number of non-unicast (i.e., subnetworkbroadcast or subnetwork-multicast) packets delivered to a higher-layer protocol. ifInOctets 1.3.6.1.2.1.2.2.1.10 column The total number of octets received on the interface, including framing characters. The number of subnetwork-unicast packets delivered to a higher-layer protocol. ifInUcastPkts 1.3.6.1.2.1.2.2.1.11 column ifInUnknownProtos 1.3.6.1.2.1.2.2.1.15 column The number of packets received via the interface which were discarded because of an unknown or unsupported protocol. column A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface must remain constant at least from one re-initialization of the entity's network management system to the next reInitialization. ifIndex 1.3.6.1.2.1.2.2.1.1 Page 7 140 RipEX Radio modem & Router – © RACOM s.r.o. 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. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface. ifNumber 1.3.6.1.2.1.2.1 scalar The number of network interfaces (regardless of their current state) present on this system. ifOperStatus 1.3.6.1.2.1.2.2.1.8 column The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. ifOutDiscards 1.3.6.1.2.1.2.2.1.19 column The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. ifOutErrors 1.3.6.1.2.1.2.2.1.20 column The number of outbound packets that could not be transmitted because of errors. ifOutNUcastPkts 1.3.6.1.2.1.2.2.1.18 column The total number of packets that higher-level protocols requested be transmitted to a nonunicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent. ifOutOctets 1.3.6.1.2.1.2.2.1.16 column The total number of octets transmitted out of the interface, including framing characters. ifOutQLen 1.3.6.1.2.1.2.2.1.21 column The length of the output packet queue (in Packets). column The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent. column The interface's address at the protocol layer immediately `below' the network layer in the protocol stack. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length. column A reference to MIB definitions specific to the particular media being used to realize the interface. For example, if the interface is realized by an ethernet, then the value of this object refers to a document defining objects specific to ethernet. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value. ifOutUcastPkts ifPhysAddress ifSpecific 1.3.6.1.2.1.2.2.1.17 1.3.6.1.2.1.2.2.1.6 1.3.6.1.2.1.2.2.1.22 ifSpeed 1.3.6.1.2.1.2.2.1.5 column An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. ifTable 1.3.6.1.2.1.2.2 table A list of interface entries. The number of entries is given by the value of ifNumber. The type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack. ifType 1.3.6.1.2.1.2.2.1.3 column interfaces 1.3.6.1.2.1.2 node ip 1.3.6.1.2.1.4 node ipAdEntAddr 1.3.6.1.2.1.4.20.1.1 column The IP address to which this entry's addressing information pertains. Page 8 © RACOM s.r.o. – RipEX Radio modem & Router 141 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. column The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex. ipAdEntNetMask 1.3.6.1.2.1.4.20.1.3 column The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0. ipAdEntReasmMaxSize 1.3.6.1.2.1.4.20.1.5 column The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface. ipAddrEntry 1.3.6.1.2.1.4.20.1 row The addressing information for one of this entity's IP addresses. ipAddrTable 1.3.6.1.2.1.4.20 table The table of addressing information relevant to this entity's IP addresses. scalar The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol. scalar The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the SourceRoute option processing was successful. ipDefaultTTL ipForwDatagrams 1.3.6.1.2.1.4.2 1.3.6.1.2.1.4.6 The indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). ipForwarding 1.3.6.1.2.1.4.1 scalar Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value. ipFragCreates 1.3.6.1.2.1.4.19 scalar The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. ipFragFails 1.3.6.1.2.1.4.18 scalar The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set. ipFragOKs 1.3.6.1.2.1.4.17 scalar The number of IP datagrams that have been successfully fragmented at this entity. ipInAddrErrors 1.3.6.1.2.1.4.5 scalar The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. ipInDelivers 1.3.6.1.2.1.4.9 scalar The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). Page 9 142 RipEX Radio modem & Router – © RACOM s.r.o. 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.4 scalar The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc. ipInReceives 1.3.6.1.2.1.4.3 scalar The total number of input datagrams received from interfaces, including those received in error. ipInUnknownProtos 1.3.6.1.2.1.4.7 scalar The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol. ipNetToMediaEntry 1.3.6.1.2.1.4.22.1 row Each entry contains one IpAddress to `physical' address equivalence. ipNetToMediaIfIndex 1.3.6.1.2.1.4.22.1.1 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. ipNetToMediaNetAddress 1.3.6.1.2.1.4.22.1.3 column The IpAddress corresponding to the mediadependent `physical' address. ipNetToMediaPhysAddress 1.3.6.1.2.1.4.22.1.2 column The media-dependent `physical' address. ipNetToMediaTable 1.3.6.1.2.1.4.22 table The IP Address Translation table used for mapping from IP addresses to physical addresses. The type of mapping. ipNetToMediaType ipOutDiscards ipOutNoRoutes ipOutRequests 1.3.6.1.2.1.4.22.1.4 1.3.6.1.2.1.4.11 1.3.6.1.2.1.4.12 1.3.6.1.2.1.4.10 column Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToMediaType object. scalar The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. scalar The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down. scalar The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in IpForwDatagrams. ipReasmFails 1.3.6.1.2.1.4.16 scalar The number of failures detected by the IP reassembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. ipReasmOKs 1.3.6.1.2.1.4.15 scalar The number of IP datagrams successfully reAssembled. Page 10 © RACOM s.r.o. – RipEX Radio modem & Router 143 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. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned. ipRouteAge 1.3.6.1.2.1.4.21.1.10 ipRouteDest 1.3.6.1.2.1.4.21.1.1 column The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the tableaccess mechanisms defined by the network management protocol in use. ipRouteEntry 1.3.6.1.2.1.4.21.1 row A route to a particular destination. column The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of IfIndex. column A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value. ipRouteIfIndex ipRouteInfo 1.3.6.1.2.1.4.21.1.2 1.3.6.1.2.1.4.21.1.13 Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of: ipRouteMask ipRouteMetric1 ipRouteMetric2 ipRouteMetric3 ipRouteMetric4 1.3.6.1.2.1.4.21.1.11 1.3.6.1.2.1.4.21.1.3 1.3.6.1.2.1.4.21.1.4 1.3.6.1.2.1.4.21.1.5 1.3.6.1.2.1.4.21.1.6 column mask network 255.0.0.0 class-A 255.255.0.0 class-B 255.255.255.0 class-C If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism. column The primary 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 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 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 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. Page 11 144 RipEX Radio modem & Router – © RACOM s.r.o. 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. (In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that Interface.) ipRouteProto 1.3.6.1.2.1.4.21.1.9 column The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols. ipRouteTable 1.3.6.1.2.1.4.21 table This entity's IP Routing table. The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP architecture. ipRouteType 1.3.6.1.2.1.4.21.1.8 column Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipRouteType object. scalar The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing Entries. ipRoutingDiscards 1.3.6.1.2.1.4.23 mib-2 1.3.6.1.2.1 node snmp 1.3.6.1.2.1.11 node Indicates whether the SNMP agent process is permitted to generate authentication-failure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authentication-failure traps may be disabled. snmpEnableAuthenTraps 1.3.6.1.2.1.11.30 scalar Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant between re-initializations of the network management system. snmpInASNParseErrs 1.3.6.1.2.1.11.6 scalar The total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages. snmpInBadCommunityNames 1.3.6.1.2.1.11.4 scalar The total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity. scalar The total number of SNMP Messages delivered to the SNMP protocol entity which represented an SNMP operation which was not allowed by the SNMP community named in the Message. snmpInBadCommunityUses 1.3.6.1.2.1.11.5 snmpInBadValues 1.3.6.1.2.1.11.10 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 `badValue'. snmpInBadVersions 1.3.6.1.2.1.11.3 scalar The total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version. Page 12 © RACOM s.r.o. – RipEX Radio modem & Router 145 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. scalar The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity. snmpInGetRequests snmpInGetResponses 1.3.6.1.2.1.11.15 1.3.6.1.2.1.11.18 snmpInNoSuchNames 1.3.6.1.2.1.11.9 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 `noSuchName'. snmpInPkts 1.3.6.1.2.1.11.1 scalar The total number of Messages delivered to the SNMP entity from the transport service. scalar The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP. scalar The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity. 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 `tooBig'. scalar The total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs. scalar The total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs. scalar The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol Entity. 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 `badValue'. snmpInReadOnlys snmpInSetRequests snmpInTooBigs snmpInTotalReqVars snmpInTotalSetVars snmpInTraps snmpOutBadValues 1.3.6.1.2.1.11.11 1.3.6.1.2.1.11.17 1.3.6.1.2.1.11.8 1.3.6.1.2.1.11.13 1.3.6.1.2.1.11.14 1.3.6.1.2.1.11.19 1.3.6.1.2.1.11.22 snmpOutGenErrs 1.3.6.1.2.1.11.24 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 `genErr'. snmpOutGetNexts 1.3.6.1.2.1.11.26 scalar The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity. snmpOutGetRequests 1.3.6.1.2.1.11.25 scalar The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity. snmpOutGetResponses 1.3.6.1.2.1.11.28 scalar The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity. snmpOutNoSuchNames 1.3.6.1.2.1.11.21 scalar The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'. snmpOutPkts 1.3.6.1.2.1.11.2 scalar The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service. snmpOutSetRequests 1.3.6.1.2.1.11.27 scalar The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity. Page 13 146 RipEX Radio modem & Router – © RACOM s.r.o. 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.4 sysDescr 1.3.6.1.2.1.1.1 scalar A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software. It is mandatory that this only contain printable ASCII characters. sysLocation 1.3.6.1.2.1.1.6 scalar The physical location of this node (e.g., `telephone closet, 3rd floor'). scalar An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. scalar The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'. sysName sysObjectID 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.2 A value which indicates the set of services that this entity primarily offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs primarily routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., IP gateways) 4 end-to-end (e.g., IP hosts) 7 applications (e.g., mail relays) sysServices 1.3.6.1.2.1.1.7 scalar For systems including OSI protocols, layers 5 and 6 may also be counted. sysUpTime 1.3.6.1.2.1.1.3 scalar The time (in hundredths of a second) since the network management portion of the system was last Re-initialized. system 1.3.6.1.2.1.1 node tcp 1.3.6.1.2.1.6 node tcpActiveOpens 1.3.6.1.2.1.6.5 scalar The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. scalar The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD State. tcpAttemptFails 1.3.6.1.2.1.6.7 Page 14 © RACOM s.r.o. – RipEX Radio modem & Router 147 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.1.6.13.1.2 tcpConnLocalPort 1.3.6.1.2.1.6.13.1.3 column The local port number for this TCP connection. tcpConnRemAddress 1.3.6.1.2.1.6.13.1.4 column The remote IP address for this TCP connection. tcpConnRemPort 1.3.6.1.2.1.6.13.1.5 column The remote port number for this TCP connection. The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. tcpConnState 1.3.6.1.2.1.6.13.1.1 column As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably). tcpConnTable 1.3.6.1.2.1.6.13 table A table containing TCP connection-specific Information. scalar The number of TCP connections for which the current state is either ESTABLISHED or CLOSEWAIT. tcpCurrEstab 1.3.6.1.2.1.6.9 tcpEstabResets 1.3.6.1.2.1.6.8 scalar The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state. tcpInErrs 1.3.6.1.2.1.6.14 scalar The total number of segments received in error (e.g., bad TCP checksums). scalar The total number of segments received, including those received in error. This count includes segments received on currently established Connections. tcpInSegs 1.3.6.1.2.1.6.10 tcpMaxConn 1.3.6.1.2.1.6.4 scalar The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1. tcpOutRsts 1.3.6.1.2.1.6.15 scalar The number of TCP segments sent containing the RST flag. tcpOutSegs 1.3.6.1.2.1.6.11 scalar The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. tcpPassiveOpens 1.3.6.1.2.1.6.6 scalar The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. tcpRetransSegs 1.3.6.1.2.1.6.12 scalar The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted Octets. tcpRtoAlgorithm 1.3.6.1.2.1.6.1 scalar The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. Page 15 148 RipEX Radio modem & Router – © RACOM s.r.o. 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. The minimum 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 LBOUND quantity described in RFC 793. tcpRtoMin 1.3.6.1.2.1.6.2 scalar transmission 1.3.6.1.2.1.10 node udp 1.3.6.1.2.1.7 node udpEntry 1.3.6.1.2.1.7.5.1 row Information about a particular current UDP Listener. The total number of UDP datagrams delivered to UDP users. udpInDatagrams udpInErrors 1.3.6.1.2.1.7.1 1.3.6.1.2.1.7.3 scalar scalar The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port. udpLocalAddress 1.3.6.1.2.1.7.5.1.1 column The local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used. udpLocalPort 1.3.6.1.2.1.7.5.1.2 column The local port number for this UDP listener. udpNoPorts 1.3.6.1.2.1.7.2 scalar The total number of received UDP datagrams for which there was no application at the destination Port. udpOutDatagrams 1.3.6.1.2.1.7.4 scalar The total number of UDP datagrams sent from this Entity. udpTable 1.3.6.1.2.1.7.5 table A table containing UDP listener information. Page 16 © RACOM s.r.o. – RipEX Radio modem & Router 149 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.5 column When rs232PortAutoBaud is 'enabled', a port may autobaud to values different from the set values for speed, parity, and character size. As a result a network management system may temporarily observe values different from what was previously set. rs232AsyncPortBits 1.3.6.1.2.1.10.33.3.1.2 column The port's number of bits in a character. rs232AsyncPortEntry 1.3.6.1.2.1.10.33.3.1 row Status and parameter values for an asynchronous Port. rs232AsyncPortFramingErrs 1.3.6.1.2.1.10.33.3.1.7 column Total number of characters with a framing error, input from the port since system re-initialization and while the port state was 'up' or 'test'. rs232AsyncPortIndex 1.3.6.1.2.1.10.33.3.1.1 column A unique value for each port. Its value is the same as rs232PortIndex for the port. rs232AsyncPortOverrunErrs 1.3.6.1.2.1.10.33.3.1.8 column Total number of characters with an overrun error, input from the port since system re-initialization and while the port state was 'up' or 'test'. rs232AsyncPortParity 1.3.6.1.2.1.10.33.3.1.4 column The port's sense of a character parity bit. rs232AsyncPortParityErrs 1.3.6.1.2.1.10.33.3.1.6 column Total number of characters with a parity error, input from the port since system re-initialization and while the port state was 'up' or 'test'. rs232AsyncPortStopBits 1.3.6.1.2.1.10.33.3.1.3 column The port's number of stop bits. rs232AsyncPortTable 1.3.6.1.2.1.10.33.3 table A list of asynchronous port entries. Entries need not exist for synchronous ports. rs232Compliances 1.3.6.1.2.1.10.33.7.2 node rs232Conformance 1.3.6.1.2.1.10.33.7 node rs232Groups 1.3.6.1.2.1.10.33.7.1 node rs232InSigChanges 1.3.6.1.2.1.10.33.5.1.4 column The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'. rs232InSigEntry 1.3.6.1.2.1.10.33.5.1 row Input control signal status for a hardware port. Identification of a hardware signal, as follows: rs232InSigName 1.3.6.1.2.1.10.33.5.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 rs232InSigPortIndex 1.3.6.1.2.1.10.33.5.1.1 column The value of rs232PortIndex for the port to which this entry belongs. rs232InSigState 1.3.6.1.2.1.10.33.5.1.3 column The current signal state. rs232InSigTable 1.3.6.1.2.1.10.33.5 table A list of port input control signal entries implemented and visible to the software on the port, and useful to monitor. rs232Number 1.3.6.1.2.1.10.33.1 scalar The number of ports (regardless of their current state) in the RS-232-like general port table. rs232OutSigChanges 1.3.6.1.2.1.10.33.6.1.4 column The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'. rs232OutSigEntry 1.3.6.1.2.1.10.33.6.1 row Output control signal status for a hardware port. Page 17 150 RipEX Radio modem & Router – © RACOM s.r.o. 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.1 column The value of rs232PortIndex for the port to which this entry belongs. rs232OutSigState 1.3.6.1.2.1.10.33.6.1.3 column The current signal state. rs232OutSigTable 1.3.6.1.2.1.10.33.6 table A list of port output control signal entries implemented and visible to the software on the port, and useful to monitor. rs232PortEntry 1.3.6.1.2.1.10.33.2.1 row Status and parameter values for a port. column The port's type of input flow control. 'none' indicates no flow control at this level. 'ctsRts' and 'dsrDtr' indicate use of the indicated hardware signals. rs232PortInFlowType 1.3.6.1.2.1.10.33.2.1.7 rs232PortInSigNumber 1.3.6.1.2.1.10.33.2.1.3 column The number of input signals for the port in the input signal table (rs232PortInSigTable). The table contains entries only for those signals the software can detect and that are useful to observe. rs232PortInSpeed 1.3.6.1.2.1.10.33.2.1.5 column The port's input speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on most implementations. column The value of ifIndex for the port. By convention and if possible, hardware port numbers map directly to external connectors. The value for each port must remain constant at least from one re-initialization of the network management agent to the next. column The port's type of output flow control. 'none' indicates no flow control at this level. 'ctsRts' and 'dsrDtr' indicate use of the indicated hardware signals. column The number of output signals for the port in the output signal table (rs232PortOutSigTable). The table contains entries only for those signals the software can assert and that are useful to observe. rs232PortIndex rs232PortOutFlowType rs232PortOutSigNumber 1.3.6.1.2.1.10.33.2.1.1 1.3.6.1.2.1.10.33.2.1.8 1.3.6.1.2.1.10.33.2.1.4 rs232PortOutSpeed 1.3.6.1.2.1.10.33.2.1.6 column The port's output speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on most implementations. rs232PortTable 1.3.6.1.2.1.10.33.2 table A list of port entries. The number of entries is given by the value of rs232Number. rs232PortType 1.3.6.1.2.1.10.33.2.1.2 column The port's hardware type. column Number of frames aborted on the port due to receiving an abort sequence since system re-initialization and while the port state was 'up' or 'test'. column Source of the port's bit rate clock. 'split' means the tranmit clock is internal and the receive clock is external. rs232SyncPortAbortedFrames rs232SyncPortClockSource 1.3.6.1.2.1.10.33.4.1.7 1.3.6.1.2.1.10.33.4.1.2 rs232SyncPortEncoding 1.3.6.1.2.1.10.33.4.1.9 column The bit stream encoding technique that is in effect for this port. nrz for Non-Return to Zero encoding nrzi for Non-Return to Zero Inverted encoding. rs232SyncPortEntry 1.3.6.1.2.1.10.33.4.1 row Status and parameter values for a synchronous Port. rs232SyncPortFrameCheckErrs 1.3.6.1.2.1.10.33.4.1.3 column Total number of frames with an invalid frame check sequence, input from the port since system re-initialization and while the port state was 'up' or 'test'. rs232SyncPortIdlePattern 1.3.6.1.2.1.10.33.4.1.13 column The bit pattern used to indicate an idle line. rs232SyncPortIndex 1.3.6.1.2.1.10.33.4.1.1 column A unique value for each port. Its value is the same as rs232PortIndex for the port. Page 18 © RACOM s.r.o. – RipEX Radio modem & Router 151 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. The mode of operation of the port with respect to the direction and simultaneity of data transfer. fdx when frames on the data link can be transmitted and received at the same Time hdx when frames can either be received from the data link or transmitted onto the data link but not at the same time. simplex-receive when frames can only be received on this data link. rs232SyncPortMode rs232SyncPortRTSCTSDelay 1.3.6.1.2.1.10.33.4.1.12 1.3.6.1.2.1.10.33.4.1.11 column column simplex-send when frames can only be sent on this data link. The interval (in milliseconds) that the DCE must wait after it sees RTS asserted before asserting CTS. This object exists in support of older synchronous devices that cannot recognize CTS within a certain interval after it asserts RTS. The method used to control the Request To Send (RTS) signal. controlled when the DTE is asserts RTS each time data needs to be transmitted and drops RTS at some point after data transmission begins. If rs232SyncPortRole is 'dte', the RTS is an output signal. The device will issue a RTS and wait for a CTS from the DCE before starting to transmit. If rs232SyncPortRole is 'dce', the RTS is an input signal. The device will issue a CTS only after having received RTS and waiting the rs232SyncPortRTSCTSDelay interval. rs232SyncPortRTSControl rs232SyncPortReceiveOverrunErrs 1.3.6.1.2.1.10.33.4.1.10 1.3.6.1.2.1.10.33.4.1.5 column constant when the DTE constantly asserts RTS. column Total number of frames that failed to be received on the port since system re-initialization and while the port state was 'up' or 'test' because the receiver did not accept the data in time. rs232SyncPortRole 1.3.6.1.2.1.10.33.4.1.8 column The role the device is playing that is using this port. dte means the device is performing the role of data terminal equipment dce means the device is performing the role of data circuit-terminating equipment. rs232SyncPortTable 1.3.6.1.2.1.10.33.4 table A list of asynchronous port entries. Entries need not exist for synchronous ports. column Total number of frames that failed to be transmitted on the port since system re-initialization and while the port state was 'up' or 'test' because data was not available to the transmitter in time. rs232SyncPortTransmitUnderrunErrs 1.3.6.1.2.1.10.33.4.1.4 Page 19 152 RipEX Radio modem & Router – © RACOM s.r.o. 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. Normally Open CRC Cyclic Redundancy Check NTP Network Time Protocol CTS Clear To Send MRU Maximum Reception Unit dBc decibel relative to the carrier MTU Maximum Transmission Unit dBi decibel relative to the isotropic OS Operation System dBm decibel relative to the milliwat PC Personal Computer DCE Data Communication Equipment PER Packet Error Rate DHCP Dynamic Host Configuration Protocol POS Point of sale DNS Domain Name Server PWR Power DQ Data Quality RF Radio Frequency DTE Data Terminal Equipment RipEX Radio IP Exchanger EMC Electro-Magnetic Compatibility RoHS Restriction of the use of Hazardeous Substances FCC Federal Communications Commission RPT Repeater FEC Forward Error Correction RSS Received Signal Strength FEP Front End Processor RTS Request To Send GPL General Public License RTU Remote Terminal Unit https Hypertext Transfer Protocol Secure RX Receiver IP Internet Protocol kbps kilobit per second LAN Local Area Network LOS Line-of-sight MAC Media Access Control SCADA Supervisory control and data acquisition © RACOM s.r.o. – RipEX Radio modem & Router SDR Software Defined Radio SNMP Simple Network Management Protocol 153 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 accessories, 55 addressing bridge, 15 router, 19 alarm in/out, 41 management, 78 antenna, 39 dummy load, 58, 60 mounting, 68 separated, 53 basic setup, 64 bench test, 60 brc COM, 93 diagnostic, 80 TCP, 86 bridge, 12, 72 ETH param., 85 factory settings, 121 features, 9 firewall, 77 firmware, 121 firmware update, 25 GNU licence, 131 GPS, 43, 53 graphs, 80, 109 grounding, 69 helps on web, 70 Hot Standby, 75 important notifications, 131 input hw, 41 installation, 65 IP/serial, 23 keys sw, 26, 120 COM parameters, 89 protocols, 92 config. file, 121 configuration CLI, 123 web, 70 connect PC, 60 connecting HW, 60 connectors, 39 cooling fan, 56, 67 default parameters, 7, 61 setting, 43, 121 demo case, 55 diagnostic, 23 dimensions, 38 environment, 126 © RACOM s.r.o. – RipEX Radio modem & Router LED, 44 licensing, 126 menu diagnostic, 106 header, 70 maintenance, 120 routing, 104 settings, 72 status, 71 MIB tables, 133 Modbus TCP, 86 model offerings, 53 monitoring menu, 115 mounting bracket, 57, 65 DIN rail, 65 rack, 57, 66 multipath propagation, 31 155 Index neighbours, 80, 107 network example, 21 layout, 33 planning, 27 networkt management, 23 consumption, 46, 79 SW feature keys, 120 technical parameters, 45 technical support, 122 Terminal server, 89 time, 76 troubleshooting, 124 ordering code, 53 output hw, 41 part number, 53 password, 122 ping menu, 112 pooling, 12 power management, 79 product code, 53 Conformity, 132 protocols COM, 92 WEEE compliance, 130 USB adapter, 55 radio parameters, 49, 82 router, 9 repeater bridge, 15, 73 router, 17, 19 report-by-exception, 12 reset, 43, 122 RipEX, 9 RipEX Hot Stanby, 55 RoHS and WEEE, 130 router, 17, 74, 104 routing table, 104 safety, 126 distance, 126 SCADA, 22 sensitivity, 48 sleep, 41, 46 standards, 10 start, 7 statistics, 80, 109 stream, 74 supply connection, 40, 42, 69 156 RipEX Radio modem & Router – © RACOM s.r.o. 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.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 2012-07-11 Added information about RipEX-HS, Hot Standby unit. Upgraded chapters: Technical specification, Model offerings, Accessories, Safety distance, Advanced Configuration © RACOM s.r.o. – RipEX Radio modem & Router 157
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.7 Linearized : Yes Author : RACOM s.r.o. Create Date : 2012:10:26 07:30:15Z Keywords : communication, network, radio, packet, modem, control, system, data, ethernet, lottery, wireless, PLC, security, mobile, transport, assembly, RipEX, RIPEX, Ripex, ripex Modify Date : 2012:11:30 12:43:25+01:00 XMP Toolkit : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26 Format : application/pdf Title : RipEX Radio modem & Router Creator : RACOM s.r.o. Producer : XEP 4.16 build 20090723 Trapped : False Creator Tool : Unknown Metadata Date : 2012:11:30 12:43:25+01:00 Document ID : uuid:9d9f2ba6-d62e-4513-afb9-ffb70b82b3af Instance ID : uuid:d54ca7d7-5047-43e6-8a25-b0e9728f012a Page Mode : UseOutlines Page Count : 157EXIF Metadata provided by EXIF.tools