User manual . RipEX2 Radio modem & Router . fw 2.0.3.0 2021-05-18 version 1.12 RACOM s.r.o. | Mirova 1283 | 592 31 Nove Mesto na Morave | Czech Republic Tel.: +420 722 937 522 | E-mail: racom@racom.eu www.racom.
Table of Contents Important Notice .................................................................................................................................. 7 1. Quick guide ..................................................................................................................................... 8 1.1. Bench testing ........................................................................................................................ 9 2. Product ........................................
RipEX2 Radio modem & Router 7.2. 7.3. 7.4. 7.5. 7.6. 4 7.1.3.3.1. None .................................................................................................. 72 7.1.3.3.2. Transparent protocol .......................................................................... 72 7.1.3.3.3. Async link ........................................................................................... 72 7.1.3.3.4. DNP3 .........................................................................................
RipEX2 Radio modem & Router 7.6.1.4.2. Hot standby LAN interface settings ................................................. 125 7.6.2. Configuration ......................................................................................................... 126 7.6.3. Events .................................................................................................................... 127 7.6.4. SNMP ..........................................................................................................
Important Notice Important Notice Copyright © 2021 RACOM. All rights reserved. Sole owner of all rights to this User manual is the company RACOM s. r. o. (in this manual referred to under the abbreviated name RACOM). 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. Products offered may contain software proprietary to RACOM.
Quick guide 1. Quick guide RipEX2 is a widely configurable compact radio modem, more precisely a radio IP router. All you have to do to put it into operation is to connect it to an antenna and a power supply and configure it using a PC (tablet, smartphone) and a web browser. Fig. 1.1: Connecting RipEX2 to a PC over WiFi, ETH/USB adapter, ETH interface Default password for "admin" account is "admin". Change the password before deploying unit to a network.
Quick guide • PC connected directly to an ETH port The default IP address for access via ETH ports is 192.168.169.169. Set a static IP address in PC to 192.168.169.0/24 (e.g.192.168.169.250, subnet mask 255.255.255.0). Important When you change the RipEX2 ETH address to a different IP address/mask, the IP address of your PC might be necessary to be updated to match the same subnet (mask).
Quick guide Fig. 1.2: RipEX2 bench testing 10 RipEX2 Radio modem & Router – © RACOM s.r.o.
Product 2. Product RipEX2 is a radio modem platform renowned for overall data throughput in any real-time environment. RipEX2 radio modems are native IP devices, Software Defined with Linux OS that have been designed with attention to detail, performance and quality. RipEX2 is built into a rugged die-cast aluminium casing that allows for multiple installation possibilities, see Section 4.1, “Mounting”. © RACOM s.r.o.
Product 60 7 67 2.1. Dimensions 185 143 67 92,5 42 M4 (4x) max. depth 6mm 125,5 134,7 93,7 62,7 31,7 60 Fig. 2.1: RipEX2 dimensions 12 RipEX2 Radio modem & Router – © RACOM s.r.o.
Product 31,7 62,7 93,7 125,5 4x) M4 ( 8 mm h p de t max. 42 92,5 143 185 Fig. 2.2: RipEX2 dimensions – bottom 134,7 68,3 60 68,3 185 DIN Rail Clip DIN 35 Rail 125,5 Fig. 2.3: RipEX2 with DIN rail © RACOM s.r.o.
7,7 22,1 31,6 42,7 153,8 166,4 142,4 154,1 167,1 Product 10,2 17,8 21 32,8 47,3 Fig. 2.4: RipEX2 dimensions with connectors For more information see Section 4.1.1, “DIN rail mounting” and Section 4.1.2, “Flat mounting”. 14 RipEX2 Radio modem & Router – © RACOM s.r.o.
Product 2.2. Connectors All connectors are located on the front panel. The upper side features a LED panel. The HW button is located on the front panel as well (close to the COM connector). Fig. 2.5: Connectors 2.2.1. Antenna An antenna can be connected to RipEX2 via TNC female 50Ω connector. RipEX2 is equipped with two connectors. The Tx/Rx connector will be used for common transmitting and receiving single antenna installation (even with different Rx and Tx frequencies). Fig. 2.
Product 2.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 RipEX2. It is Tyco 7 pin terminal block plug, part No. 1776192-7, contact pitch 3.81 mm. The connector is designed for 2 electric wires with a cross section of 0.5 to 1.5 mm . Strip the wire leads to 6 mm (1/4 inch).
Product HW ALARM INPUT Alarm Input HW ALARM INPUT is a digital input. If grounded (e.g. by connecting to pin 3), an external alarm is triggered. SI AI - Pin No.: HW ALARM OUTPUT HW ALARM OUTPUT is a digital output. + 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 4.
Product 2.2.3. ETH1 - ETH4 Standard RJ45 connectors for Ethernet connection. RipEX2 has 10/100/1000Base-T Auto MDI/MDIX interfaces so it can connect to 10 Mb/s, 100 Mb/s or 1000 Mb/s Ethernet network. The speed can be selected manually or recognized automatically by RipEX2. RipEX2 is provided with Auto MDI/MDIX function which allows it to connect over both standard and cross cables, adapting itself automatically. Pin assignment Tab. 2.
Product 2.2.5. COM RipEX2 provides serial interface COM terminated by DSUB9F connectors. It can be configured as RS232 or RS485. RS232 of RipEX2 is a hard-wired DCE (Data Communication Equipment) device. Equipment connected to the serial port of RipEX2 unit should be DTE (Data Terminal Equipment) and a straight-through cable should be used. If a DCE device is connected to the serial port of RipEX2, a null modem adapter or cross cable has to be used.
Product Pin Signal 7 RxD COM2 8 TxD COM2 This interface is not compatible with RipEX2-HS. If the RipEX2 unit is installed in the RipEX2-HS (Hot Standby chassis), the DI/DO interface is dedicated for the Hot Standby operation. 2.2.6. USB RipEX2 uses USB 3.0, Host A interface. USB interface is wired as standard: Tab. 2.
Product RipEX2 can be equipped with an internal GPS (Expansion board 'G'). The GPS module is used for time synchronization of the NTP server inside RipEX2. In this case the AUX connector serves for connecting the GPS antenna: • active antenna • 3.3 VDC supply see details 2.2.8. DI/DO Tab. 2.
Product 2.2.9. HW button Fig. 2.11: HW button HW button is placed on the right side of COM interface. Fig. 2.12: HW button scheme HW button operation • Press less than 2 seconds - Nothing happens • Press from 2 up to 7 seconds - Reboot is performed on button release • Press from 7 up to 20 seconds - Factory settings are performed on button release • Press more than 20 seconds - Nothing happens 2.3. Indication LEDs Fig. 2.13: Indication LEDs 22 RipEX2 Radio modem & Router – © RACOM s.r.o.
Product Tab. 2.7: Key to LEDs LED Colour Green Red Rx Tx COM Alarm Function Permanently lit System OK Flashing - period 500 ms Reset button pushed Three fast (50 ms) flashes - pause Reset button factory reset (500 ms) SYS AUX Style Permanently lit Alarm Flashing regularly - period 500 ms Serious system error Orange Permanently lit Unit is starting Green Permanently lit Activity of mPCIe connected equipent (like GPS fix, LTE connected, ...
Product 2.4. Ordering codes Trade name - trade and marketing name of the product. This name is used for all products within the same product family. Possible values: RipEX Gen. - generation of the product of specific Trade name. The very first generation does not have any number in this position. Possible values: none, 2 Band - frequency band and sub-band Possible values: 1A: 135-175 MHz 3A: 285-335 MHz 3B: 335-400 MHz 4A: 400-470 MHz 4B: 450-520 MHz Exp.
Product Note Only one option for mPCIe slot is possible. Var. – designation of product variant, if it is used. These variants can’t be ordered and included in the unit later on. Possible values: Processor type – X or N or E X*– Processor with HW encryption option N – Processor without HW encryption option. Encryption features will never be possible, neither HW nor SW encryption E – Processor without HW encryption option.
Product * The processor included in the unit uses an encryption module listed as 5A002 a.1 in the COUNCIL REGULATION (EC) No 428/2009, setting up a Community regime for the control of exports, transfer, brokering and transit of dual-use items. Units are subject to export control when exporting outside the European union, according to national, EU and US law (ECCN 5A002 a.1), see http://ec.europa.eu/trade/import-and-export-rules/export-from-eu/dual-use-controls/index_en.htm.
Accessories 3. Accessories 1 Whole accessory list is available on RACOM website. 1. L-bracket (see https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting Note L-bracket cannot be used if a cellular Expansion board (any of E/P/A) is installed. 2. Flat-bracket 2 (see https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting) 3. RipEX2 Hot Standby 3 (see https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting) 4. RipEX2-RD 4 (see https://www.
Installation 4. Installation Step-by-step checklist 1. Mount RipEX2 into cabinet (Section 4.1, “Mounting”). 2. Install antenna (Section 4.2, “Antenna installation”). 3. Install feed line (Section 4.3, “Antenna feed line”). 4. Ensure proper grounding (Section 4.4, “Grounding”). 5. Run cables and plug-in all connectors except from the SCADA equipment (Section 2.2, “Connectors”). 6. Apply power supply to RipEX2. 7. Connect configuration PC (Ripex2 "Connecting"). 8. Configure RipEX2. 9.
Installation 4.1. Mounting 4.1.1. DIN rail mounting The radio modem RipEX2 is directly mounted using clips to the DIN rail. The mounting can be done lengthwise (recommended) or widthwise; in both cases with the RipEX2 lying flat. The choice is made by mounting the clips, one M4 screw per clip. RipEX2 is delivered with two clips, two screws and four threaded holes. Use solely the M4×5 mm screws that are supplied. Fig. 4.1: Flat lengthwise mounting to DIN rail – recommended Fig. 4.
Installation When tightening the screw on the clip, leave a 0.5 mm gap between the clip and the washer. Fig. 4.3: Clip mounting For vertical mounting to DIN rail, L-bracket (optional accessory) is used. Use solely the M4×5 mm screws that are supplied. Fig. 4.4: Vertical widthwise mounting to DIN rail Fig. 4.5: Vertical lengthwise mounting to DIN rail 1 For more information see L-bracket . 1 https://www.racom.eu/eng/products/radio-modem-ripex.
Installation 4.1.2. Flat mounting For flat mounting directly to the support you must use the Flat bracket (an optional accessory). Use solely the M4×5 mm screws that are supplied. Fig. 4.6: Flat mounting using Flat bracket Fig. 4.7: Flat mounting using Flat bracket 2 For more information see Flat-bracket . 2 https://www.racom.eu/eng/products/radio-modem-ripex.html#HOL-RipEX-FLAT © RACOM s.r.o.
Installation 4.1.3. Full duplex mounting The standard mounting for full-duplex operation is possible for surrounding temperatures bellow + 60°C (see Table 9.1, “Technical parameters”), but it is recommended to use external passive cooler (e.g. installation in RipEX2-RS chassis) or keep the surrounding temperature bellow +35°C for increasing of a long term reliability .
Installation Fig. 4.9: IPx2 mounting 4.2. Antenna installation 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.
Installation 4.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. Use 50 Ω impedance cables only. The shorter the feed line, the better. If RipEX2 is installed close to antenna, the data cable can be replaced by an Ethernet cable for other protocols utilizing the serial port, see Section 7.1.4, “Terminal servers”.
Installation RipEX2 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.
RipEX2 in detail 5. RipEX2 in detail 5.1. Bridge mode Bridge mode enables transparent data transfer over the RipEX2 network. It is suitable for Point-toMultipoint networks, where Master-Slave applications with polling-type communication protocol are used. The Bridge mode is suitable also for Point-to-Point links (both half and full duplex). One of the advantages of the Bridge mode (together with Radio Transparent protocol) is its transparency.
RipEX2 in detail COM port The COM port needs to be Enabled and a Protocol needs to be selected to transfer any data. "Transparent" type of COM protocol is dedicated for Bridge mode purposes. This protocol transfers data between the COM port and the RipEX2 network transparently. Any other Protocol can be selected when needed.
RipEX2 in detail Step 3 RipEX2 C and RipEX2 A send the received packet to their COM ports. Packet is addressed to RTU C, so only RTU C responds. RipEX2 A is set as a repeater, so it retransmits the packet on Radio channel. Packet is received by all RipEX2 units. Step 4 RipEX2 B sends repeated packet to its COM. RTU B does not react, because the packet is addressed to RTU C.
RipEX2 in detail 5.1.2. Configuration examples You can see an example of IP addresses of the SCADA equipment and RipEX2 ETH interfaces in the picture below. In Bridge mode, the IP address of the ETH interface of RipEX2 is not relevant for user data communication. However it is strongly recommended to assign a unique IP address to each RipEX2 Network interface, since it allows for easy local as well as remote service access.
RipEX2 in detail 5.2. Router mode RipEX2 works as a standard IP router with multiple independent interfaces: Radio and Ethernets. Each interface has its own MAC address, IP address and mask. IP packets are processed according to routing table rules. You can also set the router’s default gateway (applies to both interfaces) in the routing table. The COM ports are treated as standard host devices, messages can be delivered to them as UDP datagrams to selected port numbers.
RipEX2 in detail 5.2.1.1. Router - Base driven, Functionality example A star topology with one repeater is used in the following example of a SCADA network using a polling and report by exception combination. The Repeater is also serving as a Remote radio. The packets’ acknowledgement on Radio channel is used in both directions in the example. Step 1 RipEX2 base station regularly checks the queue status of RipEX2 Remote stations for which it has no queueing information.
RipEX2 in detail Fig. 5.3: Router - Base driven, Addressing Important For those accustomed to using the Flexible Radio protocol: Settings for radios connected over a Repeater differ considerably in Base driven protocol. Note When only serial protocols are used, there is no need to use Routing tables. Instead of using Routing tables records, Address translation in COM protocol settings is used. Serial protocol address to IP address translation rules apply where the Radio IP addresses are used.
RipEX2 in detail Fig. 5.4: Router - Base driven, Addressing - Serial 5.2.2. Router - Flexible Router mode with Flexible protocol is suitable for Multipoint networks of all topologies with unlimited number of repeaters on the way, and all types of network traffic where Multi-master applications and any combination of simultaneous polling and/or report-by-exception protocols can be used.
RipEX2 in detail Step 1 FEP sends a request packet for RTU1 through COM to its connected RipEX2. Simultaneously PLC2 sends a packet for PLC1 to RipEX2 B through ETH4. Step 2 FEP’s RipEX2 transmits an addressed packet for RTU1 on Radio channel. RipEX2 1 receives this packet, checks data integrity and transmits the acknowledgement. At the same time packet is sent to RTU1 through COM. RipEX2 3 receives this packet too. It doesn’t react, because this packet is directed to RipEX2 1 only.
RipEX2 in detail 5.2.2.2. Configuration example As it was mentioned above, RipEX2 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 RipEX2 units required to communicate over the radio channel must share the same IP network.
RipEX2 in detail Example of a route from FEP (RipEX2 50) to RTU 2: • The destination address is 192.168.2.2 • The routing table of the RipEX2 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 RipEX2 50’s radio IP is 10.10.10.50/24, the router can tell that the IP 10.10.10.
RipEX2 in detail Fig. 5.6: Router - Flexible, Optimised addressing The default gateway is also a very powerful routing tool, however be very careful whenever the default route would go to the radio interface, i.e. to the radio channel. If a packet to non-existing IP destination came to the router, it would be transmitted over the radio channel. Such packets increase the load of the network at least, cause excessive collisions, may end-up looping etc.
RipEX2 in detail A SCADA application in the center 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 RipEX2.
Web interface 6. Web interface RipEX2 can be easily managed from your computer using a web browser. If there is an IP connection between the computer and the respective RipEX2, you can simply enter the IP address of any RipEX2 in the network directly in the browser address line and log in. However, it is not recommended to manage an over-the-air connected RipEX2 in this way, because high amounts of data would have to be transferred over the Radio channel, resulting in quite long response times.
Web interface The login page informs you about the Unit name and IP address of the RipEX2 unit you are trying to log in. The login page allows changing of the language of the whole web interface (English language is default). Web interface is designed for usage on all kinds of equipment - with different screen sizes and screen resolutions. Most of the pictures depicted in this User manual are taken on the desktop type of screen resolution.
Web interface 6.1. Supported web browsers Supported web browsers for desktop are current versions of: • Edge • Chrome • Firefox • Safari Supported Web browsers for mobile equipment are current versions of: • Safari for iOS • Chrome for android 6.2. Changes to commit All changes of configuration parameters are marked by different color. Multiple configuration changes in various menus can be prepared prior to final Commit. Changes to commit "basket" collects all the changes. You can: © RACOM s.r.o.
Web interface • Apply (Save to radio unit) all the changes using Send Changes or • Discard all changes via Reset All 6.3. Notifications With RipEX2 new way of showing important system events to the user is introduced. It is called Notification Centre and is used consistently throughout the interface. Notification Centre is located on the top right corner of the interface. It exists in two forms: active notification display and full Notification Center.
Web interface the system and are not shown in the Notification Centre, but on Diagnostics > Events page. In other words Notifications are caused by the user, Events are caused by changing status of the unit. Every new notification is displayed in the Notification Center drawer.
Web interface The content of the help is identical with the respective sub-chapter of the User manual. 6.6. Remote access RipEX2 unit management is designed to work smoothly even when the unit under configuration is connected via relatively slow radio channel. In case of locally connected unit - direct configuration of the unit (accessing the unit IP address directly from the web browser) works fine.
Web interface The IP address of the actually connected RipEX2 unit is displayed as part of the Remote access button. All the configuration settings are remotely available using standard web interface. Some of the Diagnostic features are available via local connection only. © RACOM s.r.o.
Settings 7. Settings Information provided in this chapter is identical with the content of Helps for individual menu. which will be gradually added on all screens. 7.1. Interfaces 7.1.1. Ethernet RipEX2 provides 5 physical Ethernet ports ETH1, ETH2, ETH3, ETH4 and ETH5. First 4 ETH ports are metallic, the 5th port is a SFP port. There is a possibility to define an Ethernet bridge - a logical Network interface - by bridging (joining) together multiple physical Ethernet interfaces.
Settings Single or multiple Ethernet subnets can be defined within one Network interface. Each subnet is identified by its IP address&mask. Use the optional field. Note to keep your network configuration in human readable manner. Enable / Disable: enables / disables specific Ethernet subnet IP address: IP address&mask of the specific Ethernet subnet (in CIDR notation). IP address represents the Network interface in the Layer 3 Ethernet network. Note Ethernet subnet description (optional).
Settings 7.1.2. Radio Radio interface behavior is heavily affected by a Radio protocol. There are several protocols available: • Transparent – This protocol is very simple; no channel access mechanism takes place. Suitable for star topology with maximum one repeater along the packet path. Available in Bridge mode. • Base driven – TCP/IP optimized protocol having deterministic channel access mechanism. Suitable for star topology with maximum one repeater along the packet path. Available in Router mode.
Settings 7.1.2.1. Radio channel parameters • TX frequency Transmitting frequency in Hz. Step 5 kHz (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: RipEX2-1A: 135-175 MHz RipEX2-3A: 285-335 MHz RipEX2-3B: 335-400 MHz RipEX2-4A: 400-470 MHz RipEX2-4B: 450–520 MHz • RX frequency Receiving frequency, the same format and rules apply as for TX frequency.
Settings • Occupied bandwidth limit [kHz] List box {possible values}, default = "25 kHz" Occupied bandwidth is limited by granted radio channel. The standards supported by using individual OBW limits are in Section 9.1, “ Detailed radio channel parameters” of this manual.
Settings • Mode List box {Passphrase; Key}, default = "Passphrase" ○ PassphraseThe key can be automatically generated based on a Passphrase. Fill in your Passphrase (any printable ASCII character, min. 1 char, max. 128 char). The same Passphrase must be set in all units within the network ○ Key [64 hex digits] The key can be configured manually (fill in 32 Bytes of 64 hexa chars). The same key must be in all units within the network. 7.1.2.2.
Settings 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.
Settings 7.1.2.3.1. Radio protocol - Base station • Station type List box {Base; Remote}, default = "Base" Note Only one Base station should be present within one radio coverage when Base driven protocol is used. 7.1.2.3.2. Base station - List of Remote stations • BDP address (from), BDP address (to) Protocol address [0 to 255] is the unique address assigned to each Remote and is only used by Base driven protocol. It is set in Remote unit in its Radio protocol settings.
Settings • Retries Number {0 – 15}, default = 3 Set value is used in one direction from Base to Remote (Remote to Base direction is configured in Remote unit in its Radio protocol settings). If the Remote station is behind Repeater, set value is used for both radio hops: Base station - Repeater and Repeater - Remote. • CTS Retries Number {0 – 15}, default = 3 Based on sophisticated internal algorithm, Base station sends a CTS (Clear To Send) packet which allows Remote station to transmit.
Settings • IP / Mask IP address of the radio interface and the mask of the radio network. • ACK List box {On; Off}, default = "On" Genetral setting of acknowledging of received packets. It can be set differently in individual link options. • Retries [No.] Number {0 .. 15}, default = 3 • Foreign packets RSS threshold [-dBm] Number {50..150}, default = 120 When the received foreign packet (the packet which is not addressed to the actual unit) has weaker signal (the listed number bigger, e.g.
Settings This parameter allows to set a maximal distance of a radio hop (in km). The same number shall be used for the whole network. We recommend to change the value only in case that the network uses radio hops longer than 100 km. 7.1.2.5.2. Queues • TX Buffers The Radio protocol transmission buffer handles data waiting to be transmitted. Its size is defined by both the number of records (Queue length) and total storage space (Queue size) requirement.
Settings 7.1.2.5.3. Flexible - advanced This settings allows to customize individual length and numbers of slots used for accessing of the radio channel or waiting with retransmissions of an undelivered packet. The length of the slots has to be same in all radio units within on radio network. It is highly recommended to consult changes of these parameters with our technical support. 7.1.3. COM Data incoming to the RipEX2 unit from the COM port are received by the Protocol module.
Settings • Type List box {possible values}, default = "RS232" COM port can be configured to either RS232 or RS485. • Baud rate [b/s] List box {standard series of rates from 600 to 1152000 b/s}, default = "19200" Select Baud rate from the list box: 600 to 1152000 b/s 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.
Settings • MRU [B] Number {1 – 2047}, default = 1500 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 MRU-sized frames sent over the network. Note 1. Very long frames (>800 B) require good signal conditions on the Radio channel and the probability of a collision increases rapidly with the length of the frames.
Settings • Broadcast List box {On; Off}, default = "On" Some Master SCADA units sends broadcast messages to all Slave units. SCADA application typically uses a specific address for such messages. RipEX2 (Protocol module) converts such message to a customized IP broadcast and broadcasts it to all RipEX2 units resp. to all SCADA units within the network. • Broadcast address Number {0 – 65535}, default = "255" The protocol address which is treated as broadcast address.
Settings 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 connected via the RS485 interface, their multiple "Protocol addresses" are translated to the same IP address and UDP port pair. Note You may add a note to each address with your comments (UTF8 is supported) for your convenience. © RACOM s.r.o.
Settings ○ Protocol address (from) This is the address which is used by SCADA protocol. The typical Protocol address length is 1 Byte. Some protocols, e.g. DNP3 are using 2 Bytes long addresses. ○ Protocol address (to) Several consecutive SCADA addresses shall be tranlated using one rule. ○ IP address (base) IP address to which Protocol address will be translated. This IP address is used as destination IP address in UDP datagram into which serial SCADA packet received from COM is encapsulated.
Settings • Destination IP This is IP address of destination RipEX2, either ETH or Radio interface. • Transmit as broadcasts List box {On; Off}, default = "Off" Allows sending of the packets incomming from COM port as broadcast. • Accept broadcasts List box {On; Off}, default = "Off" On: Broadcast packets from the radio channel will be send to the COM port. Off: Only unicast packets will be send to the COM port. 7.1.3.3.4.
Settings Note There is not an 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. 7.1.3.3.5. DF1 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 RipEX2 configuration.
Settings 7.1.3.3.6. IEC101 • ComProt_IECMode List box {Primary; Secondary; Combined}, default = "Primary" • ComProt_IECAddrMode List box {8bit; 16 bit; 8bit w/o ctrl bytem 8bit swpctrl byte; No addr}, default = "8bit" • Broadcast List box {On; Off}, default = "On" 7.1.3.3.7. Modbus RTU Modbus RTU is a serial polling-type communication protocol used by Master-Slave application.
Settings It is possible to set address, which will be handled as a broadcast address while Broadcast = "On". Default broadcast address of the Modbus RTU protocol is 0. • Mode of connected device: SLAVE ○ Response timeout Number { 0 – 8190}, default = 300 The Response timeout parameter controls how long the unit waits for an acknowledgement frame. The timeout is started when the original frame received from the Radio channel is transmitted to the connected device (over the serial channel).
Settings (Block Check Character). 3964(R) handles only the link layer (L2 in OSI model), hence RipEX uses a similar way to read “SCADA address” as in UNI protocol. There is a handshake STX(0x02) – DLE(Ox10) on the start of communication and DLE+ETX – DLE on the end. This handshake is performed by RipEX locally, it is not transferred over the RipEX network.
Settings Note 3964(R) protocol is using escape sequence (control sequence) for DLE(0x10). I.e. when 0x10 is in user data, 0x1010 is sent instead. When address position is calculated, the bytes added by escape sequence algorithm are not taken into account. Note The first byte in the packet has the sequence number 1, not 0. • Slave ○ DLE timeout [ms] Number {300 – 8190}, default = 1000 RipEX expects a response (DLE) from the connected device (RTU) within the set timeout.
Settings Note Obviously, two pieces of equipment which are communicating together must be set so that one has High priority and the other has Low. ○ BCC List box {On; Off}, default = "On" BCC (Block Check Character) is a control byte used for data integrity control, it makes the reliability higher. BCC is used by 3964R, 3964 does not use it. RipEX checks (calculates itself) this byte while receiving a packet on COM. RipEX transmits DLE (accepts the frame) only when the check result is OK.
Settings When "ACK" is enabled, RipEX is waiting "ACK timeout [ms]" after transmitting frame to receive acknowledgement. If the ACK frame isn't received, the frame is re-transmitted. Frame re-transmission happens up to "Repeats" number of times. • Repeats Number {0 – 31}, default = 3 Number of frame re-transmissions.
Settings • Mode of Connected device Listbox: {Master, Slave}, default = Master • Adress mode List box {Binary (1B); ASCII (2B); Binary (2B LSB first); Binary (2B MSB first)}, default = "Binary (1B)" Protocol address format and length (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 (the ASCII-2-Byte format function will be available in a future FW release).
Settings remote sites. This mode is suitable for Master-Master communication scheme or a combination of the UNI and ASYNC LINK protocols. • Mode of Connected device: SLAVE ○ Accept broadcasts List box {On; Off}, default = "On" "On" – Broadcast packets received at the radio channel are forwarded to the COM port. "Off" – Broadcast packets (received at the radio channel) are discarded. Unicast packets are forwarded to the COM port. 7.1.4.
Settings Up to 5 independent Terminal servers can be set up. Each one can be either TCP or UDP Type, TCP Inactivity is the timeout in seconds for which the TCP socket in RipEX2 is kept active after the last data reception or transmission. As source IP address of a Terminal server will be used the IP address of the RipEX2 ETH interface (Local preferred source address if exists see Section 7.2.1, “ Static”), Source (my) port can be set as required.
Settings • Enable / Disable: enables / disables the cellular WWAN connection. When disabled, the module power is off. • SIM List box {SIM1; SIM2}, default = "SIM1" Active SIM card selection. • Prefered service List box {2G (GSM) first; 2G (GSM) only; 3G (UMTS) first; 3G (UMTS) only; 2G/3G (GSM/UMTS) only; 4G (LTE) first; 4G (LTE) only; 3G/4G (UMTS/LTE) only}, default = "4G (LTE) first" Sets preferences and/or permission of the individual cellular network services.
Settings • Masquerade List box {On; Off}, default = "On" Enables / disables SNAT (MASQUERADE) for the packets outgoing to the WWAN interface. When on, the source address of packets outgoing via the cellular WWAN interface will be changed to the address assigned to this interface. Returning packets will be correctly routed to this interface. • Management enabled Enables / disables access into the unit’s management via the cellular WWAN interface.
Settings • Location area identity (LAI) String {00000 – 999999}, default = 00000 The Public Land Mobile Network (PLMN) identification number of the cellular network. • Access point name (APN) String {up to 99 char}, default = The APN for the access into the cellular network. • Authentication List box {None; PAP (legacy); CHAP}, default = "None" ○ None – no authentication is used for the APN access. ○ PAP (legacy) –PAP (Password Authentication Protocol) authentication.
Settings source address value - see description below. Outgoing interface is determined in Routing table according to the destination IP. The IP addressing scheme can be chosen arbitrarily, only 127.0.0.0/8 and 192.0.2.233/30 and 192.0.2.228/30 restriction applies. It may happen that also the subsequent addresses from the 192.0.2.0/24 subnet according to RFC5737 may be reserved for internal usage in the future.
Settings Local preferred source address: (Routing_LocalUseSrcAddr) Local IP address used as a source address for packets originating in the local RipEX2 unit being routed by this routing rule. It might be for example packets originating from the COM port or from the Terminal Server. If the address is set to 0.0.0.0 it is not considered active. The IP address has to belong to some of the following interfaces: Radio interface, Network interfaces. 7.2.2.
Settings ○ Broadcast – to be used in the network where all the participants always hear each other (Ethernet). Designated Router (DR) and Backup DR (BDR) are setup between the neighbors. They are responsible for the update propagation (broadcast). ○ NBMA (Non-Broadcast Multiple Access) – to be used in the network where only specific participants can communicate between each other; all the participants hear each other but multicast is not available. DR and BDR is setup.
Settings OSPF area identifier. The ID has a format of an IP address. This IP address does not have to be ‘real’. The ‘Router ID’ value is used typically. The default value of 0.0.0.0 is called ‘backbone’ and it has to be present somewhere in the OSPF network. • Stub area List box {On; Off}, default = "Off" Defines if the area is of a ‘stub’ type – which means, the traffic is not routed through such an area. Every traffic is originated or terminated in the ‘stub’ area.
Settings • Cost Number {1 – 65535}, default = 10 The cost of traffic over this interface. The higher the Cost, the worse the path. It is added to OSPF metric ‘Type 1’. • Hello interval Number {1 – 3600}, default = 10 Interval (in seconds) of sending Hello packets. The interval must be the same for the all participants of the given interface. • Poll interval Number {1 – 3600}, default = 20 Interval (in seconds) of sending Hello packets to inactive neighbors in the NMBA type of interface.
Settings • Active List box {On; Off}, default = "Off" Enables / disables the interface. • Interface List box {list of existing OSPF interfaces} OSPF interface the neighbor belongs to. The interface – Note value is used when defined. The interface – Interface value is used otherwise. • IP IP address of the neighbor. • Note Informational note 7.2.2.6. Network - Areas and interfaces - Networks The Networks table modifies networks announced out of the area.
Settings List box {On; Off}, default = "Off" Enables / disables the static routing rule. • Destination IP / Destination mask IP address, default = 0.0.0.0/0 IP address and mask defining the exported routing rule address range. • Metric type List box {Type 1; Type 2}, default = "Type 1" Metric type of the routing rule. Metric 1 is added to the path cost. Metric 2 stays apart and compared to metric 1 is always bigger. • Metric Number {1 – 65535}, default = 1000 Routing rule metric value.
Settings • Filter source List box {Off; Match; Not match}, default = "Off" Method of the OSPF routing rule source comparison.
Settings List box {Off; Match; Not match}, default = "Off" Selects a method of the routing rule destination range comparison. • Network IP / Network mask IP address, default = 0.0.0.0/0 IP address and mask defines the network prefix to be compared • Mask from Number {0 – 32}, default = 0 • Mask to Number {0 – 32}, default = 32 Definition of the enabled range of the mask length of the processed routing rule.
Settings Connections to another AS are called ‘external’ (eBGP): • It is possible to communicate from the router to the neighbor AS the MED (Multi-Exit Discriminator) metric designating which of the AS border routers will be used as an input point. When the routing rules are spread across the multiple AS, those AS are added into the accumulated path (BGP path). Path length is the primary criteria during the decision which of the routing rules will be used.
Settings Setting of MED (Multi-Exit Discriminator) on the routing rules being exported to other AS. MED makes it possible to advertise which of the routers in the local AS is the preferred input point to the AS. "Static" option sets the fixed value for all rules (Static MED). "OSPF metric 1" copies the OSPF metric to MED; for the rules which are not from the OSPF it enters the fixed value Static MED.
Settings Local IP address of the connection. Default value 0.0.0.0 provides automatic set up of this address – from the routing. • Neighbor connection List box {Direct; Multihop}, default = "Direct" Network connection type between the neighbors. "Direct" means direct – one hop – connection. This is typical for eBGP routers. "Multihop" means connection over the multiple routers. This is typical for iBGP routers.
Settings 32 Number {0 – 2 -1}, default = 10 The cost of connection to this neighbor. The higher the number the higher the cost. It enables to make decisions inside the router between multiple paths from the same neighbor. • Next hop self List box {Off; Always; Internal; External}, default = "Off" Defines it the exported routing rules should have ‘next hop’ addresses overwritten to the address of this router. "Internal" overwrites only the rules from the local AS.
Settings Number {0 – 32}, default = 32 Definition of the enabled range of the mask length of the processed routing rule. • Filter source List box {Off; Internal; External}, default = "Off" Selection based on the routing rule source. "Internal" selects rules received from the internal (iBGP) connection. "External" selects rules received from the other AS (eBGP).
Settings • Note Informational note • Filter network List box {Off; Match; Not match}, default = "Off" Selects a method of the routing rule destination range comparison. • Network IP / Network mask IP address, default = 0.0.0.0/0 IP address and mask defines the network prefix to be compared • Mask from Number {0 – 32}, default = 0 • Mask to Number {0 – 32}, default = 32 Definition of the enabled range of the mask length of the processed routing rule.
Settings Defines what action is taken on the routing rules which were not captured (i.e. fallback) in the Import OUT filter. • Filter limit Number {1 – 65535}, default = 1024 Limit of the accepted routing rules from the neighbor. The limit applies before this Import OUT filter. Excess rules are dropped. • Active List box {On; Off}, default = "On" Enables / disables the filter rule. • Note Informational note.
Settings 7.2.3.8. Export OUT filter Export OUT filter rules. The order of rules matters. Maximum number of filter rules is 256. • Filter policy List box {Accept; Reject}, default = "Accept" Defines what action is taken on the routing rules which were not captured (i.e. fallback) in the Export OUT filter. • Active List box {On; Off}, default = "On" Enables / disables the filter rule. • Note Informational note.
Settings Selects position of the specific AS (Path AS). "Any" – anywhere on the path. "Neighbor" – the path was received from this AS (last on the path). "Source" – routing rule was originated from this AS (first on the path). • Path AS 32 Number {0 – 2 -1}, default = 65000 The number of the AS searched for. • Action List box {Accept; Reject; Pass}, default = "Accept" Defines what action is taken on the routing rule. "Pass" continues in processing. 7.3. Firewall 7.3.1.
Settings 7.3.2. Firewall L3 Firewall L3 active switches L3 firewall Off, On; default is Off Each individual firewall rule is described by the following items: • Protocol List box {All; ICMP; UDP; TCP; GRE; ESP; Other}, default = "All" • Source IP / Mask source IP address and mask. The rule with narrower mask has higher priority. The rule’s order does not affect priority. • Source port (from) and (to) interval of source ports • Input interface List box {All; Radio; All ETH; ETH1..
Settings Relates 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 RipEX2 network to outside. • Connection state Established List box {Off; On}, default = "Off" - active only for TCP protocol Relates to an already existing TCP connection. Used e.g. for allowing to get replies for TCP connections created from RipEX2 network to outside.
Settings Although there are 2 modes of operation RipEX2 only offers Tunnel mode. In Tunnel mode, the entire IP packet is encrypted and authenticated. It is then encapsulated into a new IP packet (ESP – Encapsulating Security Payloads) with a new IP header. Symmetrical cryptography is used to encrypt the packets. The symmetric keys must be safely delivered to the peer. In order to maintain a secure connection, symmetric keys must be regularly exchanged.
Settings • Configuration Active {On, Off} IPsec system turning On/Off • Make-before-break {On, Off}, default Off This parameter is valid for all IKE SA using IKEv2 with re-authentication. A temporary connection breaks during IKE_SA re-authentication is suppressed by this parameter. This function may not operate correctly with some IPsec implementations (on peer side). • Peer Address Default = 0.0.0.0 IKE peer IP address.
Settings ○ Start state List box {Passive; On demand; Start}, default = "Passive" ○ MOBIKE List box {On; Off}, default = "On" Enables MOBIKE for IKEv2 supporting mobility or migration of the tunnels. Please note IKE is moved from port 500 to port 4500 when MOBIKE is enabled. The peer configuration must match. ○ Dead Peer Detection © RACOM s.r.o.
Settings List box {On; Off}, default = "On" Detection of lost connection with the peer. IKE test packets are sent periodically. When packets are not acknowledged after several attempts, the connection is closed (corresponding actions are initialized). In the case when Detection is not enabled, a connection loss is discovered when regular key exchange process is initiated. ○ Phase 1 IKE Parameters related to IKE SA (IKE Security Association) provide SA keys exchange with the peer.
Settings The higher the Diffie-Hellman group, the higher the security but also the higher the network and CPU load. ■ Reauthentication List box {On; Off}, default = "Off" This parameter is valid if IKEv2 is used. It determines the next action after IKE SA has expired. When enabled: the new IKE SA is negotiated including new peer authentication. When disabled: only the new keys are exchanged. ■ SA lifetime [s] Number {180 – 86400}, default = 14400 s (4 hours) Time of SA validity.
Settings The higher the Diffie-Hellman group, the higher the security but also the higher the network and CPU load. ■ Payload compression List box {On; Off}, default = "Off" This parameter enables payload compression. This takes place before encryption. Peer configuration must match ■ SA lifetime [s] Number {180 – 86400}, default = 3600 s (1 hour) Time of CHILD SA validity. The new key exchange or re-authentication is triggered immediately the key expires.
Settings • Active {On, Off}, default On Relevant CHILD SA can be enabled/disabled. 7.4.1.1. Advanced menu Several additional parameters are available in menu: ADVANCED / VPN / IPsec © RACOM s.r.o.
Settings • DPD check period [s] Number {5 - 28800}, default = 30 Dead Peer Detection check period • DPD action List box {Clear; Hold; Restart}, default = "Hold" One of three connection states automatically activated when connection loss is detected: ○ Clear – connection is closed and waiting ○ Hold – connection is closed. Connection is established when first packet transmission through tunnel is attempted. ○ Restart – connection is established immediately 7.4.2.
Settings • GRE L2 Enable – switches all L2 tunnels On or Off Individual L2 tunnels: • Enable – enables actual L2 tunnel • Note – Informational note • Peer address – IP address of the equipment with the second end of the tunnel. This address is the expected source address of incoming GRE packets from the peer.
Settings • GRE L3 Enable – switches all L3 tunnels On or Off Individual L3 tunnels: • Enable – enables actual L3 tunnel • Note – Informational note • Peer address – IP address of the equipment with the second end of the tunnel. This address is the expected source address of incoming GRE packets from the peer.
Settings Read only access for configuration parameters (except secured part of configuration). Diagnostics tools are available. • Technician (role_tech) All privileges of Guest role plus: write access for non-secured part of configuration. • Security technician (role_sectech) All privileges of Technician role plus: write access for secured part of configuration (except unit authentication related parts); unit firmware up/down-grade • Administrator (role_admin) No access level restrictions.
Settings Following user account parameters can be changed: password, user role. Any account (expect the last one of Administrator role) can be deleted. Export all users button provides backup of all Local user accounts into a file. Import all user button provides restoration of all Local user accounts from a backup file. Active session is logged out automatically after this command. + Add user account button invokes new user account creation dialog: • Username String {1..
Settings 7.5.2. Remote authentication Setings of the remote authentication using RADIUS is available in ADVANCED/Security/RADIUS menu. 7.6. Device 7.6.1. Unit 7.6.1.1. General The general settings affecting the whole unit. • Mode List box {Bridge; Router}, default = "Bridge" Selecting Bridge or Router mode affects many other parameters across the unit. See Section 5.1, “Bridge mode” and Section 5.2, “Router mode” for detailed description.
Settings only adapters listed in https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_ethusb can be used. The DHCP server is running on this service interface to enable easier connection of the management device (PC, tablet or smart phone). • Enable / Disable Each of the ETH or WiFi service can be enabled or disabled separately. When the WiFi is enabled, the units acts as a WiFi Access Point (AP). • IP / Mask IP address of the DHCP server.
Settings When automatic definition of SSID is enabled, the SSID contains unit Serial number. • SSID WiFi AP SSID. When entered manually, it must follow SSID naming conventions. • Mode List box {802.11g; 802.11g }, default = "802.11g " WiFi AP mode. • Channel Selected WiFi channel. • Security List box {Off; WPA2-PSK}, default = “Off” It is a good practice to use WPA2-PSK secured connection together with a strong password. It is highly recommended in case of permanent WiFi adapter installation. 7.6.1.3.
Settings • Status The Status field provides information about NTP synchronization status. Refresh button is used to update the Status information. • Change device time manually This field is used to setup unit time manually. • Update in device Sets the given time to the unit. • Use browser time checkbox Permanently updates the Change device time manually field to minimize the delay between the time input and the moment of time setup.
Settings • Time zone Time zone to represent unit internal time. All the unit timestamps are displayed using this time zone. Changing the time zone does not affect unit internal records – they are always recorded using UTC time zone. • NTP servers Multiple NTP servers can be configured to get more precise time synchronization or to have a backup solution in case of an individual NTP server unavailability. Maximum number of records in the list is 32.
Settings MAC address of shared LAN interface. It should be same for both individual RipEX2 units. This MAC address has to differ from other MAC addresses used in unit. It is possible to use e.g. VRRP type of addresses: 00:00:5E:00:01:XX. To prevent a collision with broadcast addresses (in case of Flexible protocol usage), the address must not be ended with :FF:FF:FF. • Virtual IP This address has to fit into range of addresses used for the relevant network interface (e.g.
Settings 7.6.1.4.2. Hot standby LAN interface settings It is necessary to set LAN interface used for HS functionality. The Range for virtual address parameter is in this menu available only when HS functionality in the menu SETTINGS/Device/Unit/Hot standby is enabled (see above). The parameter Range for virtual address has to be set to On for the LAN address interconnected with shared ETH interface (Range for virtual address set to On).
Settings 7.6.2. Configuration You can backup the actual unit configuration into a file or restore backed up configuration from the file. • Restore factory settings Restores all configuration parameters to default setup (including monitoring settings) Deletes user database (only default user "admin" with default password will remain). Logout from station will apply. • Total purge Deletes completely all diagnostic 126 RipEX2 Radio modem & Router – © RACOM s.r.o.
Settings 7.6.3. Events Settings of the severities of the individual events. Some events can generate SNMP notification and can change level of the HW alarm outputs (AO, DO1, DO2) see Section 2.2.2, “Power and Control”. 7.6.4. SNMP SNMP (Simple Network Management Protocol) implementation in RipEX provides three SNMP versions: v1, v2c and v3. © RACOM s.r.o.
Settings Note Following characters are prohibited in SNMP communication: " (Double quote) ` (Grave accent) \ (Backslash) $ (Dollar symbol) ; (Semicolon) • SNMP mode List box {Off; v1_v2c_v3; v3}, default = "Off" Enables the SNMP and defines which protocol versions are available. • Community name String {1..32 char}, default = Community name used by v1 and v2c When mode v1_v2c_v3 is used, this parameter is mandatory. Version 3 settings • Security user name String {1..
Settings The v3 protocol security level. Switches on/off Authentication (Auth) and the SNMP data encryption (Priv). • Authentication List box {MD5_legacy; SHA1_legacy; SHA224; SHA256; SHA384; SHA512}, default = "SHA256" Authentication algorithm. Legacy algorithms are not recommended to use, they are available for compatibility reasons only. • Authentication passphrase String {8..128 char}, default = Passphrase used for authentication with SNMP server.
Settings • Destination IP IP address {0.0.0.0}, default 0.0.0.0 IP address of SNMP server receiving notification packets. • Destination port Number {1 – 65535}, default = 162 Notification packets destination port. 7.6.5. SW keys Certain RipEX2 features needs to be activated by a SW key to be available. When the respective SW key is not present, the feature can not be configured.
Settings - SW keys are always installed as a file (there is not a clipboard option) - Single file can contain multiple SW keys - SW keys are not time limited 7.6.6. Firmware Unit firmware defines the unit functionality. There are several principles for managing the firmware in the running network: • Maintain the same version of firmware all around the network – preferred scenario.
Settings To upgrade the firmware: 1. Optional (recommended): Backup the current unit configuration (menu Settings – Device – Configuration – Back up and download) 1 2. Download the required firmware from the Racom web : Products – RipEX – Download – Firmware RipEX2 – ripex2-fw-x.x.x.0.fwp 3. Click the Choose File button (the button label may differ based on your web browser localization) to select the firmware file 4. Click the Upload firmware to archive button to transfer the firmware file into the unit.
Settings When you visit the page for the first time, you will see a search field and below a tree of configuration pages. Search field looks through all labels and the tree itself and is capable of showing all relevant configuration pages. It features so called “fuzzy” search capable of returning right answers even when there is a typo in search query. Try searching for “Ethernet” or “BGP” to see the feature in action. To use the whole tree again, simply delete search query.
Settings Please note, that RipEX 2 is a very powerful device and it really shows in the Advanced section. Be careful when adjusting settings in Advanced section and review the “Changes” page in detail before sending changes to the device. 134 RipEX2 Radio modem & Router – © RACOM s.r.o.
Diagnostics 8. Diagnostics 8.1. Overview The Overview windows shows the short view of the statistic over last 15 minutes (from the time of opening of the window or Refresh button pressed). 8.2. Events This menu shows all events which occurs within the unit history. For filtering of the events you can use the filtering tool. When no filter rules are used, the last 30 events will be displayed after Display button click.
Diagnostics It is possible to change severities of individual events in the menu SETTINGS/Device/Events. 8.3. Statistics RipEX2 unit permanently monitors various system 'channels'. There are several types of those channels: Physical interfaces (Ethernet ports, serial ports, radio interface, additional module interface (e.g. LTE module) when installed), virtual interfaces (e.g. VLAN interfaces) and HW sensors (CPU temperature, supply voltage, ...). Monitored values are stored in the internal database.
Diagnostics Fig. 8.1: Statistics data in the context of unit interfaces 8.3.1. Parameters Statistics data are always retrieved as aggregated for a certain time Interval. This Interval can be set by putting specific date and time into "From" and "To" fields, or using buttons “Last day”, “Last hour” or “More options” fast presets (from several minutes to several days). Button “Set Current Time” sets current time to both From and To fields to ease current unit status diagnostics.
Diagnostics “Display” button then shows chosen data below. “Download Selected Data” button generates CSV (UTF-8 encoded) file of all chosen systems’ data and downloads them as files without displaying them. Both "Display" and "Download ..." buttons send a request for the required set of statistics data to the unit. Retrieving and transferring of the data (over the radio channel) takes some time.
Diagnostics 8.3.3. Radio protocol statistics Radio protocol statistics provides set of data monitoring the radio channel access protocol frames and events. It corresponds to monitoring Radio - Interface. Frames which are not addressed to/from this unit are not handled (they do not affect any counter). Rx direction: from the 'air' radio interface to the Radio protocol module. Tx direction: from the Radio protocol module to the radio interface. Link address – Link address of the frame.
Diagnostics Packet rej (Tx) – Rejected packets count (rejected before handed over to the transmitter) – reason: buffer overflow, buffer timeout. Ctrl frames (Rx, Tx) – Received / transmitted control frames count. Total (Rx) – Received frames count and amount of data in Bytes. Amount of data - for both Rx and Tx - is summed over the whole Layer 2 Ethernet frame (i.e. all IP headers are counted). Total (Tx) – Transmitted frames count and amount of data in Bytes. Re-translated frames are included. 8.3.4.
Diagnostics avg / dev / min / max – average / standard deviation / minimum / maximum Phy header MSE [dB] – modulation Mean Squared Error - measured within the header reception Freq offset [Hz] – Averaged frequency offset between the transmitter and the receiver station, measured by the receiver station. Att1 [%] - First internal attenuator (15 dB) activated. Shown in percents of affected frames. Att2 [dB] – Value of the 2nd internal attenuation applied.
Diagnostics Interface – Interface name Correct (Rx, Tx) – Correctly received / transmitted packets count and amount of data in Bytes. Accepted by the COM port or Terminal server module - based on the selected Protocol processing. Amount of data - for both Correct and Drop counters - is affected by COM port data only (i.e. IP headers of the UDP frames created in the COM port module are NOT counted).
Diagnostics Fig. 8.2: Interfaces 8.4.1. Common parameters • Max. file size List box {1 kB; 10 kB; 50 kB; 100 kB; 500 kB; 1 MB; max (~2 MB)}, default = "100 kB" When the selected "Time period" expires or the "Max. file size" has been reached, whichever event occurs first, the file is closed. The file can be downloaded later. Monitoring to the file will be implemented in future FW versions.
Diagnostics Please, see Max. file size description above for more details. • Show time difference List box {On; Off}, default = "Off" When On, the time difference between subsequent packets is displayed in the monitoring output.
Diagnostics 8.4.2. Interfaces Common parameters for several interfaces: • Rx enabled, Tx enabled List box {On; Off}, default = "On" 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. Interface COM) is monitored, the Tx also means packets being transmitted from the RipEX2 over the respective interface (Rx means "received").
Diagnostics TCP/UDP destination port to be enabled/disabled in the monitoring output. Use "... (to)" parameter to specify range of ports . • Dropped frames List box {On; Off}, default = "Off" When On, monitoring shows packets which are dropped (e.g. CRC is not valid, buffer overflow, ...). ETH interfaces • Include management traffic List box {On; Off}, default = "Off" Enable/disable management packets monitoring output.
Diagnostics Monitoring output can also be limited to a specific address range - Source and Destination IP address and mask can be used to define the required range. Radio interface • Corrupted frames List box {On; Off}, default = "On" Corrupted ("header CRC error", "data CRC error", etc.) received frames monitoring output can be suppressed.
Diagnostics Menu DIAGNOSTICS/Monitoring/Advanced groups together all setting across all monitoring web pages, mentioned above, in one web page. 148 RipEX2 Radio modem & Router – © RACOM s.r.o.
Diagnostics 8.5. Tools Available are all paremeters used by standard ICMP ping. Start / Stop button starts / stops pinging. 8.6. Support Note Testing is only allowed without standard radio protocol. Please set "Radio protocol" to "None" in Radio Settings before using this feature. • Reboot button RipEX2 unit can be rebooted on request. • RF Transmission Test Pre-defined type of RF signal can be transmitted for a specific purpose. • Type © RACOM s.r.o.
Diagnostics List box {Random data; Carrier wave; Single tone}, default = "Random data" Type of transmitted signal during the test. In case of Single tone a frequency with an offset from the central frequency is transmitted. • Period [s] Number {1 – 120 s} Transmission test pre-set duration. • Start button Starts the transmission test • Stop button Allows to stop the test before the pre-set time. 8.7.
Technical parameters 9. Technical parameters Tab. 9.1: Technical parameters hazardous-locations Radio parameters Frequency bands 135 – 175 MHz; 285 – 335 MHz; 335 – 400 MHz; 400 – 470 MHz; 450 – 520 MHz Channel spacing 6.25; 12.5; 25; 50; 100; 150; 200; 250; 300 kHz Frequency stability ±0.5 ppm ±0.
Technical parameters Anti-aliasing Selectivity 56 kHz @ -3 dB BW applicable for 6.25; 12.5; 25 kHz 500 kHz @ -3 dB BW applicable for 50; 100; 150; 200; 250; 300 kHz Tx to Rx Time < 2 ms @ 6.25 kHz channel < 1.0 ms @ 12.5 kHz channel < 0.
Technical parameters not available when Expansion board 'C' (COM ports) is used Optional interfaces Active antenna 3.3 VDC SMA female (AUX on front panel) Expansion board 'G' GPS (GNSS) Expansion board 'C' COM ports Expansion board 'E', 'P', 'A' Cellular 72-channel u-blox M8 engine GPS/QZSS L1 C/A, GLONASS L10F, BeiDou B1I, Galileo E1B/C, SBAS L1 C/A: WAAS, EGNOS, MSAS, GAGAN COM2: RS232 - 5 pin (RxD, TxD, GND, RTS, CTS) 600 b/s to 2 Mb/s COM3: RS232 -3 pin (RxD, TxD, GND) 2.4 kb/s to 921.
Technical parameters Indication LEDs LED panel 5× tri-color status LEDs (SYS, AUX, RX, TX, COM) ETH 4× RJ45 (Link and Activity LEDs), 1× SFP (Status LED) Environmental IP Code (Ingress Protection) IP41, IP42, IP52 - see details MTBF (Mean Time Between Failure) > 900 000 hours (> 100 years) 4) 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 alum
Technical parameters Encryption AES256-CCM VPN IPsec, GRE VLAN IEEE 802.1Q (tagging), Q-in-Q for Transparent mode AAA protocol RADIUS Firewall Layer 2 - MAC, Layer 3 - IP, Layer 4 - TCP/UDP FW Digitally signed HW tamper Case opening evidence 4) When full-duplex with full power (40 dBm PEP) and the surrounding temperature above + 60°C 3 the external passive cooler should be used (e.g. RipEX2-RS 19" Rack chassis ).
Technical parameters Standards CE RED, RoHS, WEEE FCC, IC FCC Part 90, IC RSS-119 Spectrum ETSI EN 302 561 V2.1.1 ETSI EN 300 113 V2.2.1 EMC (electromagnetic compatibility) ETSI EN 301 489-1 V2.2.3 ETSI EN 301 489-5 V3.2.1 EN 61850-3:2014 Product Safety EN 62368-1:2014 + A11:2017 RF health safety EN 62311:2008 Electric power substations environment IEEE 1613:2009 IEEE 1613.
Technical parameters Tab. 9.
Technical parameters Tab. 9.
Technical parameters Frequency Division Duplex (FDD) DL Rx diversity 2G GSM/GPRS/EDGE 3GPP Release 8 Enhanced Data rate GSM Evolution (EDGE) GSM EGPRS Radio Access (GERA) Time Division Multiple Access (TDMA) DL Advanced Rx Performance Phase 1 Data rates up to 150 Mb/s downlink / 50 Mb/s uplink Tab. 9.6: Sensitivity Modulation 2CPFSK 4CPFSK DPSK π/4DQPSK D8PSK 16DEQAM 64QAM 256QAM -6 Sensitivity [dbm] @ BER 10 , FEC 3/4 (2/3 QAM64 and QAM256) Channel spacing 6.
Technical parameters 9.1. Detailed radio channel parameters Tab. 9.7: Channel spacing 6.25 kHz Channel spacing [kHz] 6.25 Occupied BW limit [kHz] 5 5 Modulation type FSK QAM RipEX 1 "Mode" FCC, CE FCC Baudrate [kBaud] 2.60 4.34 RipEX2 Compliance FCC, ISED FCC, ISED 6.25 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 2.60 kBaud 2.60 2CPFSK 3K60F1DBN 3.60 5 5.21 4CPFSK 3K60F1DBN 3.60 5 Baudrate 4.34 kBaud 160 4.34 DPSK 5K00G1DBN 5.
Technical parameters 6.25 kHz Sensitivity [dBm] Classification Modulation rate [kb/s] Bitrate [kb/s] FEC Modulation -2 BER 10 -3 -6 BER 10 BER 10 RX sensitivity, Baudrate 2.60 kBaud 2.60 1.95 3/4 2CPFSK -122.5 -121.0 -119.0 2.60 2.60 Off 2CPFSK -122.0 -120.0 -117.0 5.21 3.91 3/4 4CPFSK -121.0 -119.0 -116.0 5.21 5.21 Off 4CPFSK -120.0 -117.5 -114.0 RX sensitivity, Baudrate 4.34 kBaud 4.34 3.26 3/4 DPSK -122.0 -120.5 -116.0 4.34 4.34 Off DPSK -121.5 -119.
Technical parameters Tab. 9.8: Channel spacing 12.5 kHz Channel spacing [kHz] 12.5 Occupied BW limit [kHz] 11 Modulation type FSK RipEX 1 "Mode" FCC, CE FCC CE Baudrate [kBaud] 5.21 8.68 10.42 RED RED FCC, ISED FCC, ISED RipEX2 Compliance 11 12.5 QAM RED 12.5 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 5.21 kBaud 5.21 2CPFSK 7K50F1DBN 7.0 11.0 10.42 4CPFSK 7K50F1DDN 7.0 11.0 Baudrate 8.68 kBaud 8.68 DPSK 10K0G1DBN 10.0 11.
Technical parameters 12.5 kHz Modulationrate Bitrate [kb/s] [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] RX sensitivity, Baudrate 5.21 kBaud 5.21 3.91 3/4 2CPFSK -120 -119 -117 -7 5.21 5.21 Off 2CPFSK -120 -118 -115 -10 10.42 7.81 3/4 4CPFSK -119 -117 -114 -11 10.42 10.42 Off 4CPFSK -118 -115 -112 -6 RX sensitivity, Baudrate 10.42 kBaud 10.42 7.81 3/4 DPSK -119 -118 -114 -6.5 10.
Technical parameters Tab. 9.9: Channel spacing 25 kHz Channel spacing[kHz] 25 Occupied BW limit[kHz] 14 Modulation type 16 FSK RipEX 1 "Mode" Baudrate [kBaud] RipEX2 Compliance 16 20 25 QAM CE Narrow FCC CE 8.68 10.42 13.89 17.36 20.83 RED RED RED RED FCC, ISED FCC, ISED FCC, ISED FCC, ISED RED 25 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 8.68 kBaud 8.68 2CPFSK 13K5F1DBN 13.5 14 17.36 4CPFSK 12K2F1DDN 12.
Technical parameters 25 kHz Modulation rate [kb/s] Bitrate [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] Rx sensitivity Baudrate 10.42 10.42 7.81 3/4 2CPFSK -118 -117 -115 -6 10.42 10.42 Off 2CPFSK -118 -116 -113 -7 20.83 15.63 3/4 4CPFSK -117 -115 -112 -10 20.83 20.83 Off 4CPFSK -115 -113 -109 -6 Rx sensitivity Baudrate 20.83 20.83 15.62 3/4 DPSK -117 -116 -112 -6 20.83 20.
Technical parameters Tab. 9.10: Channel spacing 50 kHz Channel spacing [kHz] 50 Occupied BW limit [kHz] 40 Modulation type 50 QAM RipEX 1 "Mode" CE Unlimited Baudrate [kBaud] 34.72 41.67 RipEX2 Compliance RED RED 50 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 34.72 kBaud 34.72 DPSK 40K0G1DBN 40.0 40 69.44 π/4-DQPSK 40K0G1DDN 40.0 40 104.17 D8PSK 40K0G1DEN 40.0 40 138.89 16DEQAM 40K0G1DEN 40.0 40 208.33 64QAM 40K0G1DEN 40.
Technical parameters 50 kHz Modulation rate [kb/s] Bitrate [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] Baudrate 41.67 kBaud 41.67 31.25 3/4 DPSK -114 -113 -109 -7 41.67 41.67 Off DPSK -114 -112 -107 -7 83.33 62.50 3/4 π/4-DQPSK -113 -112 -108 -10 83.33 83.33 Off π/4-DQPSK -112 -110 -105 -11 125.00 93.75 3/4 D8PSK -110 -108 -103 -13 125.00 125.
Technical parameters Tab. 9.11: Channel spacing 100 kHz Channel spacing [kHz] 100 Occupied BW limit [kHz] 80 Modulation type 100 QAM Baudrate [kBaud] 69.44 RipEX2 Compliance RED 83.3 100 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 69.44 kBaud 168 69.44 DPSK 80K0G1DBN 80.0 80 138.89 π/4-DQPSK 80K0G1DDN 80.0 80 208.33 D8PSK 80K0G1DEN 80.0 80 277.78 16DEQAM 80K0G1DEN 80.0 80 416.66 64QAM 80K0G1DEN 80.0 80 555.
Technical parameters 100 kHz Modulation rate [kb/s] Bitrate [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] Baudrate 69.44 kBaud 69.44 52.08 3/4 DPSK -112 -110 -106 -7 69.44 69.44 Off DPSK -111 -109 -104 -7 138.89 104.17 3/4 π/4-DQPSK -111 -109 -105 -10 138.89 138.89 Off π/4-DQPSK -110 -108 -102 -11 208.33 156.25 3/4 D8PSK -108 -105 -100 -13 208.33 208.
Technical parameters Tab. 9.12: Channel spacing 150 kHz Channel spacing [kHz] 150 Occupied BW limit [kHz] 125 Modulation type 150 QAM Baudrate [kBaud] 115.74 RipEX2 Compliance RED 124.01 150 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 115.74 kBaud 170 115.74 DPSK 125KG1DBN 125.0 125 231.48 π/4-DQPSK 125KG1DDN 125.0 125 347.22 D8PSK 125KG1DEN 125.0 125 462.96 16DEQAM 125KG1DEN 125.0 125 694.45 64QAM 125KG1DEN 125.0 125 925.
Technical parameters 150 kHz Modulation rate [kb/s] Bitrate [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] Baudrate 115.74 kBaud 115.74 86.71 3/4 DPSK -110 -108 -104 -7 115.74 115.74 Off DPSK -109 -107 -102 -7 231.48 173.61 3/4 π/4-DQPSK -109 -107 -103 -10 231.48 231.48 Off π/4-DQPSK -108 -106 -100 -11 347.22 260.42 3/4 D8PSK -106 -103 -98 -13 347.22 347.
Technical parameters Tab. 9.13: Channel spacing 200 kHz Channel spacing [kHz] 200 Occupied BW limit [kHz] 175 Modulation type QAM Baudrate [kBaud] 138.89 RipEX2 Compliance RED 200 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 138.89 kBaud 172 138.89 DPSK 150KG1DBN 150.0 175 277.78 π/4-DQPSK 150KG1DDN 150.0 175 416.67 D8PSK 150KG1DEN 150.0 175 555.56 16DEQAM 150KG1DEN 150.0 175 833.33 64QAM 150KG1DEN 150.0 175 1111.
Technical parameters 200 kHz Modulation rate [kb/s] Bitrate [kb/s] FEC Co-Channel Rejection Ratio Sensitivity [dBm] Classification Modulation -2 BER 10 -3 BER 10 -6 BER 10 [dB] Baudrate 138.89 kBaud 138.89 104.17 3/4 DPSK -109 -107 -103 -7 138.89 138.89 Off DPSK -108 -106 -101 -7 277.78 208.33 3/4 π/4-DQPSK -108 -106 -102 -10 277.78 277.78 Off π/4-DQPSK -107 -105 -99 -11 416.67 312.50 3/4 D8PSK -105 -102 -97 -13 416.67 416.
Technical parameters Tab. 9.14: Channel spacing 250 kHz Channel spacing [kHz] 250 Occupied BW limit [kHz] 250 Modulation type QAM Baudrate [kBaud] 208.33 250 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 208.33 kBaud 208.33 DPSK 225KG1DBN 225.0 250 416.67 π/4-DQPSK 225KG1DDN 225.0 250 625.00 D8PSK 225KG1DEN 225.0 250 833.33 16DEQAM 225KG1DEN 225.0 250 1250.00 64QAM 225KG1DEN 225.0 250 1388.89 256QAM 225KG1DEN 225.
Technical parameters Tab. 9.15: Channel spacing 300 kHz Channel spacing [kHz] 300 Occupied BW limit [kHz] 300 Modulation type QAM Baudrate [kBaud] 260.42 300 kHz Modulation rate [kb/s] Modulation Emission code OBW [kHz] OBW limit [kHz] Baudrate 260.42 kBaud 260.42 DPSK 280KG1DBN 280.0 300 520.83 π/4-DQPSK 280KG1DDN 280.0 300 781.25 D8PSK 280KG1DEN 280.0 300 1041.67 16DEQAM 280KG1DEN 280.0 300 1562.50 64QAM 280KG1DEN 280.0 300 1736.11 256QAM 280KG1DEN 280.
Technical parameters 9.2. Recommended MSE thresholds Tab. 9.16: MSE Recommended MSE thresholds Modulation FEC Mean MSE [dB] 2CPFSK 3/4 -10 2CPFSK Off -11 4CPFSK 3/4 -12 4CPFSK Off -15 DPSK 3/4 -10 DPSK Off -11 π/4-DQPSK 3/4 -12 π/4-DQPSK Off -14 8DPSK 3/4 -17 8DPSK Off -20 16DEQAM 3/4 -19 16DEQAM Off -22 64QAM 3/4 -24 64QAM Off -27 256QAM 3/4 -30 256QAM Off -33 Fig. 9.1: MSE recommended tresholds 176 RipEX2 Radio modem & Router – © RACOM s.r.o.
Safety, regulations, warranty 10. Safety, regulations, warranty 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 parameters have to be set exactly as listed. Important Use of frequencies between 406.0 and 406.1 MHz is worldwide-allocated only for International Satellite Search and Rescue System.
Safety, regulations, warranty 300–470 MHz/70 cm band – 10 W RF power SA380.5 5 element directional Yagi 8.7 7.4 200 90 SA380.9 9 element directional Yagi 12.5 17.8 310 140 Tab. 10.2: Minimum Safety Distance 135–175 MHz 135 - 175 MHz / 2 m band – 10 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 OV138.1 single dipole 4.6 2.
Safety, regulations, warranty • The radio equipment can only be operated on frequencies stipulated by the body authorized 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 unauthorized way. • Equipment mentioned in this User manual may only be used in accordance with instructions contained in this manual.
Safety, regulations, warranty 10.7. EU Compliance 10.7.1. RoHS, WEEE and WFD Fig. 10.1: EU Declaration of Conformity RoHS, WEEE 180 RipEX2 Radio modem & Router – © RACOM s.r.o.
Safety, regulations, warranty Waste Framework Directive Statement According to the Directive 2008/98/EC on waste amended by Directive (EU) 2015/1127 and Directive (EU) 2018/851 (Waste Framework Directive) we hereby state that our products doesn’t contain substances of very high concern (SVHC) listed on European chemical agency (ECHA) SCIP database candidate list in concentrations above 0.1 % w/w. 10.7.2.
Safety, regulations, warranty 10.7.3. EU Declaration of Conformity RED Fig. 10.3: EU Declaration of Conformity RED 10.7.4. Simplified EU declaration of conformity BG С настоящото RACOM s.r.o. декларира, че този тип радиосъоръжение RipEX2 е в съответствие с Директива 2014/53/ЕС. ES Por la presente, RACOM s.r.o. declara que el tipo de equipo radioeléctrico RipEX2 es conforme con la Directiva 2014/53/UE. CS Tímto RACOM s.r.o. prohlašuje, že typ rádiového zařízení RipEX2 je v souladu se směrnicí 2014/53/EU.
Safety, regulations, warranty DE Hiermit erklärt RACOM s.r.o., dass der Funkanlagentyp RipEX2 der Richtlinie 2014/53/EU entspricht. ET Käesolevaga deklareerib RACOM s.r.o., et käesolev raadioseadme tüüp RipEX2 vastab direktiivi 2014/53/EL nõuetele. EL Με την παρούσα ο/η RACOM s.r.o., δηλώνει ότι ο ραδιοεξοπλισμός RipEX2 πληροί την οδηγία 2014/53/ΕΕ. EN Hereby, RACOM s.r.o. declares that the radio equipment type RipEX2 is in compliance with Directive 2014/53/EU. FR Le soussigné, RACOM s.r.o.
Safety, regulations, warranty SK RACOM s.r.o. týmto vyhlasuje, že rádiové zariadenie typu RipEX2 je v súlade so smernicou 2014/53/EÚ. SL RACOM s.r.o. potrjuje, da je tip radijske opreme RipEX2 skladen z Direktivo 2014/53/EU. FI RACOM s.r.o. vakuuttaa, että radiolaitetyyppi RipEX2 on direktiivin 2014/53/EU mukainen. SV Härmed försäkrar RACOM s.r.o. att denna typ av radioutrustning RipEX2 överensstämmer med direktiv 2014/53/EU. 10.8.
Safety, regulations, warranty Fig. 10.4: TCB authorization © RACOM s.r.o.
Safety, regulations, warranty Fig. 10.5: TCB authorization 186 RipEX2 Radio modem & Router – © RACOM s.r.o.
Safety, regulations, warranty FCB Technical Acceptance Certificate CB Number: US0156 ISSUED TO RACOM s.r.o. RACOM, Mirova 1283 Nove Mesto na Morave 592 31 Czech Republic CERTIFICATION No. 24993-RIPEX24A DESCRIPTION Wireless modem router TYPE OF EQUIPMENT Land-Mobile Transmitter and Receiver (27.41–960 MHz) HVIN(s) RipEX2-4 PMN(s) RipEX2-4 FVIN(s) N/A TYPE OF LISTING: New Single Certification ANTENNA INFORMATION External Antenna, 12.
Safety, regulations, warranty Radio Details Number: CB-19-0187 Issue 1 Frequency Min (MHz) Frequency Max (MHz) RF Power (W) Min Max Emission Designator Specification Issue 406.1 430.0 11.8 406.1 430.0 11.8 11.8 19K8G1D RSS-119 Issue 12 11.8 15K5F1D 406.1 430.0 RSS-119 Issue 12 11.8 11.8 10K0G1D 406.1 RSS-119 Issue 12 430.0 11.8 11.8 7K50F1D RSS-119 Issue 12 406.1 430.0 11.8 11.8 5K00G1D RSS-119 Issue 12 406.1 430.0 11.8 11.8 3K60F1D RSS-119 Issue 12 450.0 470.
Safety, regulations, warranty 10.9. Compliance ANATEL Brasil RipEX2-4A : RipEX2-4A : This equipment is approved by ANATEL under number 16763-20-08917. 10.10. Warranty RACOM-supplied parts or equipment ("equipment") is covered by warranty for inherently faulty parts and workmanship for a warranty period as stated in the delivery documentation from the date of dispatch to the customer. The warranty does not cover custom modifications to software.
Safety, regulations, warranty Action Period Note Draining hole on dipole must be downward pointing There should be no damaged elements on the antenna Angle of elevation of antenna Azimuth (angle of horizontal deviation) in accordance with design Visual check – Coaxial Cable: Mechanical damage Solar degradation Entire cable correctly mounted to surface Connectors tightened to function optimally Self-vulcanizing tape used for all connections requiring insulation PSV & RF measurements Annually Visual che
Abbreviations Appendix A. Abbreviations ACK Acknowledgement MDIX Medium dependent interface crossover AES Advanced Encryption Standard MIB Management Information Base BER Bit Error Rate NMS Network Management System CLI Command Line Interface N.C. Normally Closed CRC Cyclic Redundancy Check N.O.
Abbreviations TCP Transmission Control Protocol TS5 Terminal server 5 TX Transmitter UDP User Datagram Protocol VSWR Voltage Standing Wave Ratio WEEE Waste Electrical and Electronic Equipment 192 RipEX2 Radio modem & Router – © RACOM s.r.o.
Index P A product conformity EU, 182 accessories, 27 addressing bridge, 39 antenna, 15 mounting, 33 AUX, 20 Q quick guide, 8 R C radio parameters, 160 reset, 22 RoHS and WEEE, 180 router, 40 connectors, 15 Copyright, 7 S D safety, 177 distance, 177 B base driven protocol, 40 default parameters, 8 setting, 22 dimensions, 12 E T technical parameters, 151 W warranty, 177 environment, 177 F flexible protocol, 40 G grounding, 34 I installation, 28 IP/serial, 47 L LED, 22 M mode router, 40
Revision History 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 0.9 First issue 2018-11-11 Revision 1.0 2019-07-30 Chapter Technical parameters updated.
