Product 4.4. Technical specification Tab. 4.6: Technical parameters Radio parameters Frequency bands 135–175*; 300–330*; 928–960* MHz Channel spacing 6.25 / 12.5 / 25 kHz Frequency stability ±1.0 ppm Modulation 16DEQAM, D8PSK, π/4DQPSK, DPSKΩ 4CPFSK, 2CPFSK Detail 25 kHz 83.33 – 62.50 – 41.67 kbps 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.
Product Electrical Primary power 10 to 30 VDC, negative GND Rx 5 W (360 mA/13.8 V; 200 mA/24 V) Tx 4CPFSK, 2CPFSK Tx 16DEQAM, D8PSK, π/4DQPSK 0.1 W 1.0 A/13.8 V; 0.55 A/24V; 14 W 1W 1.1 A/13.8 V; 0.6 A/24 V; 15 W 5W 2.4 A/13.8 V; 1.3 A/24 V; 33 W 10 W 3.0 A/13.8 V; 1.6 A/24 V; 42 W 0.1 W 2.2 A/13.8 V; 1.25 A/24 V; 30 W 1W 2.2 A/13.8 V; 1.25 A/24 V; 30 W 2W 2.2 A/13.8 V; 1.25 A/24 V; 30 W Sleep mode 7 mA/13.8 V, 0.1 W; 6 mA/24 V; 0.15 W Save mode 170 mA/13.8 V; 95 mA/24 V; 2.
Product Collision Avoidance Capability Yes Remote to Remote communication Yes Addressed & acknowledged serial Yes SCADA protocols 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) Watched values in each radiomodem Rx/Tx packets for ETH, COM1, COM2 (broadcast to other radiomodems) Rx/Tx packets on User interfaces and for User data Statistics Rx/Tx Packets on User inte
Product 4.4.1. Emission code Tab. 4.7: Channel spacing 25 kHz, exponential modulation, CE Channel spacing 25 kHz Exponential modulation | Symbol rate 10,42 kBaud || CE Classification Modulation FEC Raw Code Rate Bit Rate Blocking or desensitization Sensitivity BER -2 10 Emission dsg.
Product 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 ETSI 300 113-1 V1.7.1 (channels 25 and 12.5 kHz) and ETSI 301 166-1 V1.3.2 (channel 6.
Product Tab. 4.11: Channel spacing 25 kHz, exponential modulation, FCC Channel spacing 25 kHz Exponential modulation | Symbol rate 10,42 kBaud || FCC Classification Modulation FEC Code Raw Rate Bit Rate Blocking or desensitization Sensitivity BER -2 10 Emission dsg.
Product Tab. 4.13: Channel spacing 12,5 kHz, exponential modulation, FCC Channel spacing 12,5 kHz Exponential modulation | Symbol rate 5,21 kBaud || FCC Classification Modulation FEC Code Raw Rate Bit Rate Blocking or desensitization Sensitivity Emission dsg.
Product Tab. 4.15: Channel spacing 6,25 kHz, exponential modulation, FCC Channel spacing 6,25 kHz Exponential modulation | Symbol rate 2,60 kBaud || FCC Classification Modulation FEC Code Raw Rate Bit Rate Blocking or desensitization Sensitivity BER -2 10 Emission dsg.
Product 4.5. Model offerings Software feature keys Certain advanced RipEX features are activated with software keys. Among such code protected features are the Router mode, High speed (83 kbps), COM2, 10 W and others. A Master key, which activates all coded features, is also available. 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.
Product 4.6. Accessories 1. RipEX Fan kit External Fan kit for additional cooling in extreme temperatures. For connection see chapter Connectors. 142 55 79 88 150 Fig. 4.15: Assembly dimensions with fan 2. RipEX – 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.16: Dummy load 3. RipEX – L-bracket Installation L bracket for vertical mounting.
Product 4. RipEX – Flat-bracket Installation bracket for flat mounting. For details on use see chapter Mounting and chapter Dimensions. 5. RipEX – 19" rack shelf – single Fig. 4.18: Flat bracket For installation of a single RipEX into the standard 19” rack. 6. RipEX – 19" rack shelf – double For installation of 2 RipEX’s into the standard 19” rack. Fig. 4.19: 19" Rack shelf 7. X5 – ETH/USB adapter ETH/USB adapter for service access to the web interface via USB connector.
Product Contains a MS2000/24 power supply connected via a switch to the 230 VAC socket. Three RipEX’s connected to 24 VDC power supply and complete with dummy loads are ready for testing. ETH/USB adapter can be used for service access. During a field test, RipEX's can be powered from the backup battery and external antenna can be connected to one of them through a connector on the case. Fig. 4.
Bench test 5. Bench test 5.1. Connecting the hardware Before installing a RipEX network in the field, a bench-test should be performed in the lab. The RipEX Demo case is great for this as it contains everything necessary: 3 RipEX’s, Power supply, dummy load antennas, etc.
Bench test 1. Using the "X5" - external ETH/USB adapter 2. Directly over the ethernet interface https://10.9.8.7 PC DHCP https://192.168.169.169 PC 192.168.169.250 Fig. 5.2: Connecting to a PC over ETH and over ETH/USB adapter 1. PC connected via ETH/USB adapter We recommend using the "X5" - external ETH/USB adapter (an optional accessory of the RipEX). The ETH/USB contains a built-in DHCP server, so if you have a DHCP client in your PC as most users, you don’t need to set anything up.
Bench test Fig. 5.3: PC address setting Note: When you change the RipEX ETH address from the default value later on and the new IP network does not include the default one, you will have to change your PC's static IP again to be able to continue configuring the RipEX. 3. Login to RipEX Start a web browser (Mozilla Firefox, Internet Explorer - JavaScript enabled) on your PC and type the RipEX’s default IP in the address line default IP of RipEXfield: • 10.9.8.
Bench test Fig. 5.4: Authentication The default entries for a new RipEX are: User name: admin Password: admin Click OK. Initial screen should appear then: Fig. 5.5: Status Menu Warning: Before you start any configuration, make sure only one unit is powered ON. Otherwise, a different radio modem could reply to your requests! (All units share the same IP address and are in Bridge mode when in factory settings.) 4.
Bench test 5.4. Basic setup For the first functionality test we recommend that you use the setup wizard. The wizard will guide you through basic functionality setup. Simply select Wizard in the web interface and proceed according to the information on the screen. Repeat for all RipEX’s in the test network. If you want to test applications which require a more complex setup, see Chapter 7, Advanced Configuration. To setup the IP addresses you can use the examples in Section 2.3.
Installation 6. Installation Step-by-step checklist 1. 2. 3. 4. 5. Mount RipEX into cabinet (Section 6.1, “Mounting”). Install antenna (Section 6.2, “Antenna mounting”). Install feed line (Section 6.3, “Antenna feed line”). Ensure proper grounding (Section 6.4, “Grounding”). Run cables and plug-in all connectors except from the SCADA equipment (Section 4.2, “Connectors”). 6. Apply power supply to RipEX 7. Connect configuration PC (Section 5.3, “Connecting RipEX to a programming PC”). 8.
Installation Fig. 6.3: Vertical widthwise mounting to DIN rail Fig. 6.4: Vertical lengthwise mounting to DIN rail 6.1.2. Flat mounting For flat mounting directly to the support you must use the Flat bracket (an optional accessory). Fig. 6.5: Flat mounting using Flat bracket 6.1.3. 19" rack mounting For installation into the 19" rack you can use the 19" rack shelf – single or 19" rack shelf- double for one or two RipEXes. 19" rack shelf is an optional accessory delivered with/without a power supply.
Installation Fig. 6.6: Rack shelf 6.1.4. Fan kit In extreme temperatures you can install an external fan kit for additional cooling. The fan kit installs using three screws driven into the openings on the bottom side of the RipEX. Use M4×8 screws. Fig. 6.7: Fan kit mounting The fan kit may be controlled using the Alarm Output (Control and Power connector, Section 4.2.
Installation Fan Kit Fan Kit SI AI - Pin No.: black black red SI AI - + A0 + 10–30VDC 1 2 3 4 5 6 7 Fig. 6.8: Fan kit using Alarm Output, recommended Pin No.: red + A0 + 10–30VDC 1 2 3 4 5 6 7 Fig. 6.9: Fan kit, always on 6.2. Antenna mounting The type of antenna best suited for the individual sites of your network depends on the layout of the network and your requirements for signal level at each site.
Installation The shorter the feed line, the better. RipEX can be installed right next to the antenna and an ethernet cable can be used to connect it to the rest of the installation and to power the RipEX . An ethernet cable can also be used for other protocols utilising the serial port, see Advanced Configuration, Terminal server. This arrangement is recommended especially when the feed line would be very long otherwise (more than 15 meters) or the link is expected to operate with low fading margin.
Advanced Configuration 7. Advanced Configuration This chapter is identical with the content of Helps for individual menu. 7.1. Menu header 7.1.1. Generally RipEX can be easily managed from your computer using any web browser (Mozilla Firefox, Microsoft Internet Explorer, etc.). If there is an IP connection between the computer and the respective RipEX, you can simply enter the IP address of any RipEX in the network directly in the browser address line and log in.
Advanced Configuration Connect Action button to connect to the remote RipEX, which is specified by the IP address in the Remote box. The Unit name in "Values from" box is changed accordingly afterwards. Disconnect When a Remote RipEX is sucessfully connected, the Disconnect button shows up. When the Disconnect process is executed, the Local RipEX (IP address in the Local box) can be managed and the Unit name in the "Values from" box changes accordingly. 7.2. Status Fig. 7.2: Menu Status 7.2.1.
Advanced Configuration Refresh - complete refresh of displayed values is performed. 7.3. Settings Fig. 7.3: Menu Settings 7.3.1. Device Unit name Default = NoName Each Unit may have its unique name - string up to 16 characters. Note: The Unit name is just for your convenience, there no DNS (Domain Name Server) is used in RipEX network.
Advanced Configuration 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.
Advanced Configuration • 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.
Advanced Configuration • • • 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.
Advanced Configuration • Information about the actual date and time in the 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 has to be connected via the Ethernet interface. ■ 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.
Advanced Configuration • • Established – relates to already existing TCP connection. Used e.g. for allowing to get replies for TCP connections created from RipEX network to the outside. Related – a connection related to the “Established” one. E.g. FTP typically uses 2 TCP connections – control and data – where the data connection is created automatically using dynamic ports. Note: Port 44 is used for the service access.
Advanced Configuration 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.
Advanced Configuration 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).
Advanced Configuration 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.
Advanced Configuration TX frequency** Transmitting frequency. Format MHz.kHz.Hz. Step 5 or 6.25 kHz. The value entered must be within the frequency tuning range of the product as follows: RIPEX-330: 330–350 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.
Advanced Configuration 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.
Advanced Configuration 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.
Advanced Configuration 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.
Advanced Configuration run locally between Modbus Master and RipEX in Modbus TCP network. Read Help and Application note Modbus in RipEX. 1 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.
Advanced Configuration 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.
Advanced Configuration 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.
Advanced Configuration 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. 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.
Advanced Configuration Stop bits List box: possible values Default = 1 Wikipedia: Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Idle [bytes] Default = 5 [0 - 2000] This parameter defines the maximum gap (in bytes) in the received data stream. If the gap exceeds the value set, the link is considered idle, the received frame is closed and forwarded to the network.
Advanced Configuration 7.3.5. Protocols Fig. 7.8: Menu Protocols COM Generally Each SCADA protocol like Modbus, DNP3, IEC101, DF1 etc. has its unique message format, most importantly its unique way of addresing of remote units. The basic task for protocol utility is to check whether received frame is within protocol format and it is not corrupted. Most of the SCADA protocols are using some type of Error Detection Codes (Checksum, CRC, LRC, BCC, etc.
Advanced Configuration used, e.g. multi-master polling and/or spontaneous communication from remote units and/or parallel communication between remote units etc. Note: These Radio protocol features are available only in the Router mode. The Bridge mode is suitable for simple Master-Slave arrangement with a polling-type application protocol. Common parameters The parameters described in this section are typical for most protocols. There is only a link to them in description of the respective Protocol.
Advanced Configuration • 88 − only one SCADA device to one COM port can be connected, even if the RS485 interface is used • Base IP Default = IP address of ETH interface When the IP destination address of UDP datagram, in which serial SCADA message received from COM1(2) is encapsulated, is created, this Base IP is taken as the basis and only the part defined by Mask is replaced by 'Protocol address'. • Mask Default = 255.255.255.
Advanced Configuration Messages from serial interface are processed in similar way as at Master site, i.e. they are encapsulated in UDP datagrams, processed by router inside the RipEX and forwarded to the respective interface, typically to Radio channel. ○ Broadcast accept List box: On, Off Default = On If On, broadcast messages from the Master SCADA device to all Slave units are accepted and sent to connected Slave SCADA unit. Protocols implemented: None All received frames from COM port are discarded.
Advanced Configuration 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.
Advanced Configuration 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).
Advanced Configuration 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.
Advanced Configuration • 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.
Advanced Configuration Mask Slave • Protocol frames List box: 1C,2C,3C,4C Default = 1C One of the possible C24 Protocol frames can be selected. • Frames format 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.
Advanced Configuration 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.
Advanced Configuration 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.
Advanced Configuration 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. © RACOM s.r.o.
Advanced Configuration 7.4. Routing Routing table is active only when Router mode (Settings/Device/Operating mode) is set. In such a case RipEX works as a standard IP router with 2 independent interfaces: Radio and ETH. Each interface has its own MAC address, IP address and Mask. IP packets are then processed according the Routing table. The COM ports are treated in the standard way as router devices, messages can be delivered to them as UDP datagrams to selected UDP port numbers.
Advanced Configuration the network defined by IP and Mask of one of the interfaces (Radio, ETH), otherwise the packet is discarded. Each line in the routing table defines a Gateway (the route, the next hop) for the network (group of addresses) defined by Destination IP and Mask. When the Gateway for the respective destination IP address is not found in the Routing table, the packet is forwarded to the Default gateway. When Default gateway is not defined (0.0.0.0), the packet is discarded.
Advanced Configuration 7.5. Diagnostic 7.5.1. Neighbours and Statistic Fig. 7.10: Menu Neighbours Neighbours and Statistics follow the same pattern. Most importantly, they share a common time frame. One Log save period and one Difference log (pair of Clear and Display buttons) apply to both logs. For both logs there is a history of 20 log files available, so the total history of saved values is 20 days (assuming the default value of 1440 min. is used as Log save period).
Advanced Configuration • Notice, that the Log start, Last upd. and Log uptime labels at the top change to Diff. start, Diff. upd. and Diff. uptime when the Difference log is displayed. They show the respective values for Difference log. History There is a possibility to display history logs using standard buttons. They are placed on the left side of the button bar. The Refresh button displays the latest log values. Top bar • • • • • Date Information about the actual date and time in the RipEX.
Advanced Configuration • • red background indicates, that the item is monitored for alarm and its average value is in the alarm range (Settings/Device/Alarm management) 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.
Advanced Configuration Statistic Fig. 7.11: Menu Statistic Statistic log provides information about communication on all interfaces: Radio, ETH, COM1, COM2. Balloon tips provide on line help for all column names. These tips explain the meanings and the way of calculation of individual values. Meaning of IP addresses listed: Rx - for received (Rx) packets, the IP source address from UDP header is displayed.
Advanced Configuration Fig. 7.12: Menu Graphs • • • • File period File period corresponds with 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.
Advanced Configuration • • • • • 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). Alarm When displayed value is out of threshold, a red line on the bottom of the graph is shown. Date and time is displayed in balloon tip then. History There is a possibility to change displayed file(s) using standard buttons (Previous 10…6 5 4 ..
Advanced Configuration Ping (Packet InterNet Groper) is a utility used to test the reachability of a particular host on an IP network. It operates by sending echo request packets to the target host and waiting for an echo response. In the process it measures the rtt (round trip time - the time from transmission to reception) and records any packet loss.
Advanced Configuration "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.
Advanced Configuration 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.
Advanced Configuration 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.
Advanced Configuration ○ 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"}.
Advanced Configuration ■ 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.
Advanced Configuration • • 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.
Advanced Configuration 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.
Advanced Configuration • • • • • 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 respective Hold button (possibly several Hold buttons for several selected keys) and then press the Apply button to put the selected key(s) on hold.
Advanced Configuration 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 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.
Advanced Configuration 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.
CLI Configuration 8. CLI Configuration CLI interface (Command Line Interface) is an alternative to HTTPS. You can work with the CLI interface in text mode using an appropriate client, either ssh (putty) or telnet. 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.
Troubleshooting 9. Troubleshooting 1. 2. I don’t know what my RipEX’s IP is – how do I connect? • Use the "X5" – external ETH/USB adapter and a PC as a DHCP client. Type 10.9.8.7 into your browser’s location field. • Alternatively, you can reset your RipEX to default access by pressing the Reset button for a long time, see Section 4.2.6, “Reset button” . Afterwards, you can use the IP 192.168.169.169/24 to connect to the RipEX.
Troubleshooting arp -d 192.168.169.169 or delete the entire table by typing: arp -d * 5. Then you can ping the newly connected RipEX again. I have assigned the RipEX a new IP address and my PC lost connection to it. 6. • Change the PC’s IP address so that it is on the same subnet as the RipEX. I entered the Router mode and lost connection to the other RipEX’s. 7. • Enter correct data into the routing tables in all RipEX’s. The RSS Ping test shows low RSS for the required speed. • 8.
Safety, environment, licensing 10. Safety, environment, licensing 10.1. Frequency The radio modem must be operated only in accordance with the valid frequency license issued by national frequency authority and all radio parametres have to be set exactly as listed. Important Use of frequencies between 406.0 and 406.1 MHz is worldwide-allocated only for International Satellite Search and Rescue System.
Safety, environment, licensing 160 MHz/2 m band – 4 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposure [cm] posure [cm] Antenna code Antenna description OV160.1 single dipole 4.6 2.9 117 52 OV160.2 stacked double dipole 7.6 5.8 165 74 SA160.3 5 element directional Yagi 8.0 6.3 173 77 SA160.5 9 element directional Yagi 12.5 17.8 290 130 160 MHz/2 m band – 3 W RF power Dist.
Safety, environment, licensing 160 MHz/2 m band – 0.5 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposure [cm] posure [cm] Antenna code Antenna description OV160.1 single dipole 4.6 2.9 41 19 OV160.2 stacked double dipole 7.6 5.8 58 26 SA160.3 5 element directional Yagi 8.0 6.3 61 27 SA160.5 9 element directional Yagi 12.5 17.8 103 46 160 MHz/2 m band – 0.2 W RF power Dist.
Safety, environment, licensing 300–400 MHz/70 cm band – 5 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposure [cm] posure [cm] Antenna code Antenna description OV380.1 single dipole 4.6 2.9 86 39 OV380.2 stacked double dipole 7.6 5.8 122 54 SA380.3 3 element directional Yagi 7.6 5.8 122 54 SA380.5 5 element directional Yagi 8.7 7.4 138 62 SA380.9 9 element directional Yagi 12.
Safety, environment, licensing 300–400 MHz/70 cm band – 2 W RF power SA380.9 9 element directional Yagi 12.5 17.8 135 61 300–400 MHz/70 cm 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 Exposure [cm] posure [cm] Antenna code Antenna description OV380.1 single dipole 4.6 2.9 39 17 OV380.2 stacked double dipole 7.6 5.8 54 24 SA380.3 3 element directional Yagi 7.6 5.
Safety, environment, licensing 300–400 MHz/70 cm band – 0.1 W RF power Dist. where the FCC limits are met for Gain G Gain G General Population General Population [dBi] [–] / Uncontrolled Ex- / Controlled Exposure [cm] posure [cm] Antenna code Antenna description OV380.1 single dipole 4.6 2.9 12 5 OV380.2 stacked double dipole 7.6 5.8 17 8 SA380.3 3 element directional Yagi 7.6 5.8 17 8 SA380.5 5 element directional Yagi 8.7 7.4 20 9 SA380.9 9 element directional Yagi 12.5 17.
Safety, environment, licensing tering 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.
Safety, environment, licensing 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.
Safety, environment, licensing Declaration of Conformity – RipEX ! in accordance with 1999/5/EC Directive of the European Parliament and of the Council of 9t h of March 1999 on radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity.
Abbreviations Appendix A. Abbreviations ACK Acknowledgement MDIX Medium dependent interface crossover AES Advanced Encryption Standard MIB Management Information Base ATM Automated teller machine NMS Network Management System BER Bit Error Rate N.C. Normally Closed CLI Command Line Interface N.O.
Abbreviations TCP Transmission Control Protocol TS5 Terminal server 5 TX Transmitter UDP User Datagram Protocol VSWR Voltage Standing Wave Ratio WEEE Waste Electrical and Electronic Equipment 130 RipEX Radio modem & Router – © RACOM s.r.o.
Index G A GNU licence, 126 GPS, 42, 52 graphs, 75, 103 addressing bridge, 15 router, 19 alarm in/out, 40 management, 73 antenna dummy load, 53, 56 mounting, 64 separated, 38, 52 B bench test, 56 brc COM, 87 diagnostic, 75 TCP, 81 bridge, 12, 68 C COM parameters, 83 protocols, 86 config.
Index power management, 74 product code, 52 protocols COM, 86 R radio param.
Revision History Appendix B. 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.
