Home

RipEX - racom.eu

Contents

1. eem remet T4 8 5 Master Modbus TCP slaves Modbus RTU or Modbus TCP eeeeeeeeeenee 75 8 6 Multiple Modbus TCP or Modbus RTU Masters and Slaves eem 15 MEE Reo 01 ole Reem tan I T NU MI Tf 9 1 MASTER SLAV E COMMUNIGATON x ioi ttecet hm te te ten da Ra i a P aa e E cdi Ere a us 77 9 2 MASTER SLAVE with several Masters cccccccseccseece cece eeeeeeteseeeeeteeeeeeeseeeseeeneesseenes 79 9 2 MASE Re MIPS TEER auis erp ED eiue unten tva EN a atte h Cus denis Riu dur Meneses 79 9 4 MASTEROUONIE S ASYNG IINI SLAVES iitirivmei tutte EU E D Eu Ure E RCM pube 79 10 CHANING ACCESS nune ronenptd i ation Rebate ioR Ebo eh vr ula tu dnce to sorde aoi a pe per Du n et ida 81 TOT CON I ON Sx cda tanc sedated caa I dmi an erc ut A Ec UTR Rc DU 81 10 2 BIG GS Manolo men 82 10 3 Bila dge riedearna COM Streami dedii Erit picta te caved venient a Uaaeynet aa heeeass 85 1024 ROUE r MOGOGG soia uia aeta RR ERE a a ua Ra at de Metu d cues ate aaa nmin a Ext S ta ede Gana eu Ns 86 ui odd ORY re WINING rU eT UH ET 88 VA Ws LIV ERO GUI GUOM ED D omms 88 11 2 Franson EAN CARP PIOXY dgetecsad cceielacteces cle a eu ee dicenaaacate 88 11 93 Transparent VLAN d mia dut ecu ph d td eec e etas Vltun Eon tli a e e a d tcl o tc Sait 89 TA Gontguratlon EXalmples oh Seen diced Ede ath eene cud De deseri a N 90 UE Nee URSI IA EE E E Dom 103 P24 2 6 40 6 TOU S eee I ee ene eee ee
2. 1E 01 4 e 2CPFSK 10 42 kBaud a ACPFSK 10 42 kBaud x pi4 DQPSK 17 36 kBaud 1 E 02 AX x DSPSK 17 36 kBaud E L 16 DEQAM 17 36 kBaud Y 1 E 03 2 LL X S wF E 1E 04 X i 1 E 05 H 120 118 116 114 112 110 108 106 104 102 100 98 96 94 92 90 Signal Level dBm Fig 3 5 Maximum usable sensitivity measurement results Channel separation 25 kHz 3 2 2 Efficient use of narrowband radio channel As it has been written in the Section 1 the radio transceiver in exponential modulation mode can make use of higher transmitter power In order to take this fact into account the system gain SG or the maximum allowed path loss 2 2 SG dB Pur S 2 2 is usually calculated for the wireless communication systems Here the P is the available transmitter power expressed in dBm and S is the measured value of radio receiver sensitivity also in dBm It ex presses the referential value of the link budget assuming 0 dBi of antennas gain and together with the spectrum efficiency given by 2 3 it expresses how effectively the radio device uses its assigned bandwidth Rp n bit s Hz 2 3 B In 2 3 the R is the raw bit rate given in bits s and B is the frequency bandwidth assigned to the radio system 25 kHz in particular All these performance characteristics are collectively given in Table 3 2 It can be seen that even with the lower available transmitter
3. VLAN IP VLAN IP 192 168 2 251 24 192 168 2 252 24 VLAN tagged VLAN tagged Data VLAN tagged Mais VLAN tagged A agge ata N ata SOS SS VLAN 2 IP a VLAN 2 IP pi 192 168 2 1 24 VLAN 4 IP 192 168 2 2 24 VLAN 3 IP 10240021 jj PC 192 168 4204 PC 2 Fig 11 17 15 Management VLAN diagram Note o VLAN 2 is on the same subnet 192 168 2 0 24 VLAN 3 is on the subnet 192 168 3 0 24 and VLAN 4 is on the 192 168 4 0 24 subnet 11 5 Summary We have described just a few basic examples of VLAN amp ARP proxy usage Feel free to download the RipEX User manual from http www racom eu download hw ripex free eng ripex m en pdf or the Ap plication notes from http www racom eu download hw ripex free eng ripex app en pdf to conduct further tests Do not hesitate to contact us if you have any questions RACOM technical support team E mail lt support racom eu gt Tel 420 565 659 511 RACOM s r o RipEX 103 Backup routes 12 Backup routes 12 1 Introduction RipEX provides Backup routes functionality to increase reachability in networks through redundant paths See the following example where we have three possible paths between RipEX A and RipEX B The direct radio link is set as the primary path because it is direct The path over RipEX C is the first backup option two hops and if this path also fails GPRS backup path is ready in case of radio failure In cellular networks data transfer i
4. we will use VLAN ID 2 with the IP address 192 168 2 252 VLAN amp Subnets VLAN amp Subnets On Interface VLAN ID IP MASK Priority Unit Manag ARP proxy Note Active Modify ETHO 192 168 4 252 24 wf Default interface Add Subnet 0 Add Subnet Delete Add VLAN OK Fig 11 15 RipEX B VLAN configuration The VLAN ID is the same as used on RipEX A but we can set any ID when needed Note You can try to enable VLAN on the default interface after you complete this example The RipEX B routing table consists of three rules e Destination 192 168 2 251 32 Mask 255 255 255 255 Gateway 10 10 10 2 e Destination 192 168 2 1 32 Mask 255 255 255 255 Gateway 10 10 10 2 e Destination 192 168 3 0 24 Mask 255 255 255 0 Gateway 10 10 10 2 RACOM s r o RipEX 101 ARP Proxy amp VLAN Radio modem amp Router 2 i OM AS Ripex Status Values from RipEX B Sue ag 10 10 10 4 Wizards Settings Interfaces Routing Radio MAC 00 02 AS BAT3 GB IP 10 10 10 4 Mask 255 255 255 0 i ETH MAC 00 02 AS BACGF B3 IP 1892 168 4 252 Mask 255 255 255 0 VLAN amp Subnets Diagnostic SSS Neighbours Routes Tum Destination Mask Gateway Backup Note Active Modify 192 168 27 251 32 255 255 255 255 10 10 10 2 Off RipEX A VLAN d 7 Delete Add Graphs 182 168 2 1 32 z55 255 255 255 10 10 10 2 Off Pt 1 P Delete Add m 192 168 3 0 24 255 255 255 0 10 10 10 2 Off RipEx A ETH v Delete Add ng D
5. Alternative paths Name Peer IP Hysteresis SMMP Trap Gateway Policy Active Note Modify Backup 1 192 168 17 1 20 Delete Add 10 10 10 16 Default v Indirect link T Add 10 10 10 17 Default w Direct link Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 15 ipEX A Routing menu RipEX B switched off As soon as the Backup routes system evaluates the situation correctly the ping packets are successful again Also notice the ping packets RTT value is lower than with the primary indirect path being used ping recvmsg No ping recvmsg No From 192 From 192 88 bytes 88 bytes 88 bytes 168 15 1 168 15 1 from 192 from 192 from 192 route to host route to host icmp seq 558 Destination Host Unreachable icmp seq 559 Destination Host Unreaghable 168 17 1 icmp req 563 ttl 64 time i74 ms 168 17 1 icmp req 564 ttl 64 time 157 ms 168 17 1 icmp req 565 ttl 64 time 174 ms Fig 12 16 RipEX A Ping packets backup direct path Now you can turn RipEX B back on again Because RipEX checks the primary indirect path with Hello packets periodically it will switch back to the primary path This change will not cause any loss in ping packets 12 3 3 Ethernet Radio In this test the primary route is via the Ethernet link and it is backed up by the radio link See the following example RACOM s r o RipEX 115 Backup routes PATH 2 10 10 10 2 10 10 10 1 192 168
6. 192 168 20 outing SUE A DRM n f4 t2 GW 192 168 1 254 a N I S Eth IP 192 168 30 3 Eth IP 192 168 30 3 IP hex C0 A8 1E 03 Default GW 192 168 10 253 IP hex C0 A8 02 02 Mask 255 255 255 0 Mask 255 255 255 0 Routing Routing GW 192 168 30 254 GW 192 168 30 254 Fig 6 3 RIpEX MR400 in Router mode RACOM s r o RipEX 63 Combining MORSE and RipEX networks 6 2 2 Terminal devices connected to COM A MORSE network can only be expanded with RipEX modems if the application protocol is supported both by MORSE and RipEX or if RipEX s UNI protocol can be used instead If you want to use protocols which are not implemented in RipEX by default please consult RACOM s technical support The COM port of the border RipEX and the RS232 of the border MRxxx are connected with crosslink serial cable see Fig 6 2 Crosslink serial cable If the Master is located in the MORSE part of the network the border MRxxx should use Multiaddressing for addresses of all Slaves in the RipEX network Protocol settings should reflect that The border RipEX then should be set up as connected to the Master using the appropriate protocol address translation using a mask or table routing rules If the Master unit is located on the RipEX side of the network rules for address translation should direct all the packets sent to Slave units of the MORSE network to the COM port connected to the border MRxxx This COM port should then use an appro
7. Oe kOe wie Oe Oded LOS DOSTIOSU6 era 051010217 10 10 10 19 via 10 10 10 17 this record is only necessary if you require communication between end devices 19 and 18 For 10 10 10 19 Ore es EO I5 via d Vb bs T4 USUS diosa AED SOS sO TU 10 10 10 18 via 10 10 10 17 this record is only necessary if you require communication between end devices 19 and 18 To display the full routing table type ip route show table normal in CLI interface e For 10 10 10 19 10SID T0 T5 via 10 10 10 04T7 dev radio Proto Static broadcast L0 10 10 0 dev radio proto static scope link sre 10 10 10 19 broadeast 10 10 10 255 dev radio proto statac scope Tink sre 10 10 10 19 Lele LO elo vibe Os Os LO dey radio Proto Stale LO eA sO he Via DOIO ITUSDTPOdev radio proto Star re 10 10 10 0 24 dev radio proto static scope link 192 168 141 0 24 dev ethO proto static scope link default via 192 168 141 254 dev eth0 proto static An example of a routing table on page Routing for 10 10 10 19 6 RipEX RACOM s r o Address planning 3 gt gt lt Radio modem amp Router Co PRACOM Status Values from RipEX 24 Fastremote access Wizards Settings OK Update finished successfully Routing laanostii Operating mode Router Note Routing is active only when Operating mode is set to Router Diagnostic Heighbours Interfaces 7 Statistic Radio MAC 00 02 A5 A0 DF C1 IP 10 10 10 18 Mask 255 255 255 0 Graph ETH MAC 00 02 A9 A0 DB D9
8. Terminal server Ethernet protocol socket TCP UDP port 33555 2 2 4 3 1 6 X tsEthProtDestlP Terminal server partner s IP address 33555 2 2 4 3 1 7 X tsEthProtDestPort read only current Terminal server partner s destination TCP UDP port 33555 2 2 4 3 1 8 X tsComProtType undi nnd d server COM user protocol type 33555 2 2 5 1 ifComNumber Number of COM interfaces 33555 2 2 5 2 ifComTable not access current List of COM interface entries ible 33555 2 2 5 2 1 ifComEntry COM interface entry ible 33555 2 3 1 1 1 stRadioTotDuplic read only current Total radio duplicate packets counter ates 33555 2 3 1 1 2 stRadioTotRe Total radio repeated packets counter peats 33555 2 3 1 1 3 stRadioTotLost Total radio lost packets counter 33555 2 3 1 1 4 s t R a d i jread only current Total Rx radio control packets counter oTotCtlPacketsRx 33555 2 3 1 1 5 Js t R ad i jread only current Total Tx radio control packets counter oTotCtlPackets Tx RACOM s r o RipEX 39 SNMP 33555 2 3 1 1 6 jstRadioTot read only current Total radio data error packets counter DataErr 33555 2 3 1 1 7 stRadioTotRejec read only current Total radio rejected packets counter ted 33555 2 3 1 1 8 stRadioTotPacket read only current Remote station total Rx packets counter SRx 33555 2 3 1 1 9 stRadioTotPacket read only current Remote station total Tx packets counter sTx 33555 2 3 1 1 10 stRadioTotBytes Remote sta
9. The COM port protocol at the border MRxxx must be the same as protocol used by the other MORSE devices in the network In some special cases the ASYNC LINK protocol can be used for the border interconnection 62 RipEX RACOM s r o Combining MORSE and RipEX networks If the Master is located on the side of the MRxxx the border MRxxx should be set to Slave Depending on the SCC interface used the MRxxx should use Multiaddressing with addresses of all the Slave units on the RipEX network If the Master is located on the side of the RipEX the border MRxxx is set like it was connected to the Master and the Node of the connected SCC interface has to correspond to the Master s address Fig 6 2 Crosslink serial cable 6 2 RIpEX in Router mode There are two basic scenarios e Terminal devices are connected over Ethernet e Terminal devices are connected over COM interface 6 2 1 Terminal devices connected over Ethernet In this scenario the border RipEX and MRxxx should be interconnected with an Ethernet cable Routing in both parts of the network should be set up so that communication between them is channeled over the border modems It is recommended that terminal devices in the two parts of the network are located on separate LAN s The picture shows MORSE network settings Eth IP 192 168 20 2 IP hex C0 A8 14 02 000 Ses IP 192 168 1 1 Mask 255 255 255 0 IP hex C0 A8 01 01 Routing Hay 255 255 255 0
10. 12 2 1 Protocol Procedure RipEX A sends out Hello packets UDP via all possible paths to RipEX B RipEX B receives these packets and records them according to the received path RipEX B sends the list of received Hello packets within its own Hello packet back to RipEX A RipEX A receives this packet and evaluates the conditions of individual paths Due 9 Individual alternative paths can obtain the following states Up the path is functional and can be used Down the path is not functional and cannot be used Unknown the path s state cannot be evaluated due to lack of information This state is active imme diately after the RipEX power up or its state is not being evaluated because a higher priority path is being used Note See the respective help for detailed parameter descriptions in RipEX web interface 12 3 Configuration Examples In this chapter we will go through several examples in order to explain Backup routes in practice Please follow the examples one by one to fully understand the configuration differences and benefits of various solutions Note The examples are configured similarly to the examples used in the RipEX Application note Chapter 1 Address planning 12 3 1 Radio Radio End Devices Connected via Serial Interface In the first example there are five RipEX units in a network All end devices are connected to the RipEX units via a serial interface It is helpful to use o
11. 3 gt C Radio modem amp Router Co PIANC CORA Status Values from RipEX A Wizards Settings Device Routing Unit name Time Manual Alarm management X Default Neighbours amp Statistics Default Di ti Operating mode Router SNMP Off Power management Always On Graphs Default lagnostic g Hot Standby Off Firewall Off Neighbours LI Statistic Radio T ETH COM s COM 1 COM 2 Graphs IP IP 192 168 2 251 ina RS232 Rs232 Ping Mask Mask 255 255 255 0 Baud rate bps 19200 19200 z Tx 430 52 000 Default GW 0 0 0 0 Monitoring TX frequency Data bits 8 8 RX frequency El 436 525 000 DHCP Of Parity None None Maintenance Gund aracng Baz ae Shaping ee 1 NH 1 Modulation rate kbps 41 67 m 4DQPS Speed nm idie bytes 5 5 oF RF power W 05 7 mdi s MRU bytes 1600 1600 Terminal servers Off FEC Off hi Flow control None None hd E TCP proxy Off Onlimizali i one one sina VLAN amp Subnets Of MED Encryption Off 2 MTU bytes 1900 Fig 11 4 RipEX A settings Do not forget to set the same TX RX frequencies Channel spacing Modulation rate and other para meters on both RipEX units Do not enable ARP proxy or VLAN The next step is to set Routing see the Routing menu Configure RipEX A with these routing rules Destination 192 168 2 252 32 Mask 255 255 255 255 Gateway 10 10 10 4 Destination 192 168 2 2 32 Mask 255 255 255 255 Gateway 10 10 10 4 RipEX B will have ver
12. FM ON Destination Mask Gateway Backup Note Active Modify at 10 10 10 18 32 255 255 255 255 10 10 10 17 Off RipEX D v Y Delete Add Graphs 10 10 10 19 32 255 255 255 255 10 10 10 17 Off RipEX E Delete Add Ping Add Monitoring Backup Alternative paths Maintenance Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Mote Modify Add Legend Up Down Unknown Currently used Route for IP Fig 12 4 RipEX B Routing menu example 1 Note RipEX B is not the end point Peer IP of the Backup routes system and so there is no backup route defined RACOM s r o RipEX 107 Backup routes Radio modem amp Router m PRACOM A Ripex Status Values from RipEX C aiu dad 10 10 10 17 Wizards Settings Interfaces Routing Radio MAC 00 02 A3 BA 73 6B IP 10 10 10 17 Mask 255 255 255 0 4 ETH MAC OU 02 AS BA GF 83 IP 192 168 17 1 Mask 255 255 255 0 Diagnostic Neighbours Routes SEE Destination Mask Gateway Backup Note Active Modify i 10 10 10 15 32 255 255 255 255 Backup 1 Backup RipEX A v Delete Add Graphs Add Ping Backup Monitoring Alternative paths A Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Maintenance RS up 1 10 10 10 15 20 Delete Add 10 10 10 15 Default Direct link hd Add 10 10 10 16 Default v Indirect link E Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 5 RipEX C Routing menu example 3 Note See the configuration of RipEX D a
13. RS232 rs232PortType Items 6 gt x21 ICMP ping Accessibility Items 0 ICMP ping fails ICMP ping Accessibility 1 ICMP ping successful Note Two value mappings should already be included in the Zabbix itself see SNMP interface status ifAdminStatus and SNMP interface status ifOperStatus in the Value mapping menu Four Items from the RFC1213 template use these mappings How can I Edit an Item to Link with a Value Map Go to Configuration Templates and choose one of the imported template Open the item configur ation window and click on the chosen item to view and edit its settings Choose the appropriate value map in the Menu Show value and save the changes Example RipEX eDhpc RACOM s r o RipEX 2f SNMP Host RipEX Template Name Ethemet interface DHCP mode Type SNMPy2 agent Key eDhcp SNMP OID 1 5 6 1 4 1 33555 2 2 2 2 SNMP community public Port Type of information Numeric unsigned Data type Decimal gt Units Use custom multiplier Update interval in sec 1600 Flexible intervals New flexible interval Interval in sec 50 Period 1 7 00 00 24 00 Add Keep history in days 90 Keep trends in days 365 Store value As is Show value RipEX eDhcp show value mappings Fig 2 9 Linking a value map to an item 2 4 How do Know that Something Has Happened to the RipEX Station There are two ways to check the RipEX stations You can actively query the station in
14. 0 Enabled j Information Backu th state has changed within last 5 minutes 1RipEX SNMP Trapper Template trpBpath nedata 300 0 Enabled RipEX SNMP Trapper Template troCom1Pr str OFF 0 Enabled RipEX SNMP Trapper Template trpoCom2Pr str OFF 0 Enabled Average ipEX station Etherne t rati RipEX SNMP Trapper Template trpEthPr str OFF 0 Enabled Average RipEX station HW input in the alarm state RipEX SNMP Ti r Template trpHwin str OFF 0 Enabled Information RipEX station Modem becomes active in a Hot Standby mode within the last 5 minutes RipEX SNMP Trapper Template trpHotStby nodata 300 7 0 Enabled RipEX station Modem temperature value out of ra 1RipEX SNMP Trapper Template trpTemp str OFF 0 Enabled DgX Y Z W str OFF 0 Disabled RipEX SNMP Trapper Template trpRssX Y Z W str OFF 0 Disabled ais RipEX SNMP Trapper Template trpRfpwr str OFF 0 Enabled ae 1 1RipEX SNMP Trapper Template trpUnitReady str OFF 0 amp Information RipEX station The unit Ready signal is UP 1 i Enabled RipEX SNMP Trapper Template trpUnitReady noadata 300 0 iam Average RipEX station TX Lost value out of range RipEX SNMP Trapper Template trpTxLost str OFF 0 Enabled som Average RipEX station UCC value out of range RipEX SNMP Trapper Template troUicc str OFF 0 Enabled Average RipEX station VSWR value out of range RipE
15. 86 U 10 10 2 LN 1 A y R Ox0020 0202 cOa 0201 0000 470d 4a17 0006 286e Ox0030 4c51 3a43 0100 0000 1011 Ox0040 1213 1415 1617 1819 lalb 1cl1d lelf 2021 PS bad Fig 11 13 Monitoring ping packets with VLAN tags VLAN on Both Ends We can also configure VLANs on both RipEX units so the VLAN tagged data will be transmitted via the Ethernet link between PC 2 and RipEX B too However traffic is always untagged on the radio channel oee the following diagram 100 RipEX RACOM s r o ARP Proxy amp VLAN Radio link Router mode Aut hy fi Radio IP 10 10 10 2 24 Untagged Data 1051040 434 RipEX A RipEX B ETH IP ETH IP 192 168 3 251 24 VEAN 192 168 4 251 24 VLAN VLAN IP VLAN IP 192 168 2 251 24 192 168 2 252 24 VLAN tagged J VLAN tagged Untagged Data Untagged Data Data i Data RU O VLAN IP o VLAN IP ETH IP pcg 192168 2 1 24 ETH IP pc yo 192 168 2 2 24 192 168 3 1 24 122 168 121 Fig 11 14 VLAN configuration diagram 2 RipEX Configuration RipEX A has the same configuration as in the previous example If you want to test the connectivity of RipEX ETH interfaces you need to add this routing rule e Destination 192 168 4 0 24 Mask 255 255 255 0 Gateway 10 10 10 4 RipEX B needs several changes Change the Ethernet IP address to 192 168 4 252 with the mask 255 255 255 0 Now go to the VLAN amp Subnets menu enable the feature and add a new VLAN
16. 88 bytes from 182 168 17 icmp req 10 ttl 63 time 480 ms icmp req 11 ttl 63 time 378 ms icmp req 12 ttl 63 time 343 ms icmp req 13 ttl 63 time 378 ms 1 1 1 1 1 1 B8 bytes from 192 168 17 1 icmp req 8 ttl 63 time 309 ms 1 1 1 1 1 1 icmp req 14 ttl 63 time 412 ms Fig 12 14 Successful ping packets primary indirect path You can also turn on the radio interface monitoring Go to the Diagnostic Monitoring menu and check the radio interface Leave other parameters at their defaults and click on the Start button You can see all the packets in the radio network ping packets Hello packets ARP Now turn RipEX B off and see the differences You can see that there are no replies to ping packets in Ping and Monitoring menu Check the Routing menu by pressing the Backup status button to see when the active path is switched to the backup direct path 114 RipEX RACOM s r o Status Wizards settings Routing Diagnostic Neighbours Statistic Graphs Ping Monitoring Maintenance Values from RipEx A Radio modem amp Router Backup routes C RACOM Interfaces Radio MAC FBBE OF AB IP 10 10 10 15 Mask 255 255 255 0 ETH MAC HF BBE DB C3 IP 192 168 15 1 Mask 255 255 205 0 Routes Destination Mask Gateway Backup Note Active Modify 182 168 16 0 24 2520 255 225 0 10 10 10 16 Of RipEX B v Delete Add 192 168 17 0 24 255 255 255 0 Backup 1 RipEX C v Delete Add Add Backup
17. BES 132 46 002 0440 Assign asset ID RELANCE GENE Product Support Information Ctrl F E Hs Solia TS REENNNDI ye Displays properties of Ehe selected object Far editing Chg DP slave properties window opens Click on the PROFIBUS button DP slave properties x General Operating Parameters Option handling Identification Module Order Number BES 151 14404 0460 Family ET 2005 DP Slave Type ET 2005 Designation M151 Standard Addresses Made Master system Diagnostic Address 1 Ue IDP master system 1 STML FHEEZE Capabilities fF Iw watchdog Comment OF Cancel Help Properties PROFIBUS window opens Select the Transmission Rate 19 2 Kbps or 9 6 Kbps under the Network Settings tab The recommended value is 19 2 Kbps Under Profile select User Defined and click Bus Parameters RACOM s r o RipEX 67 Profibus Properties PROFIBUS xi PROFIBUS x General Network Settings Name PROFIBUS_DA Highest PROFIBUS Options 57 subnet ID 0101 0004 Aitor jh l Change Project path RacomTestyDPAPROFIBUS DP Storage location of the project D Projekty R acom R acomT es Transmission Rate Author Date created 12 27 2010 11 07 35 4M Last modified 03 22 2011 11 35 25 4M DP Standard Universal DP FMS User Defined Cancel Help Cancel Help OK PROFIBUS DP is the most important settings window fill
18. IP 192 168 141 183 Mask 255 255 255 0 Ping Routes Maintenance Destination Mask Gateway Interface Note Active Modify 10 10 10 15 32 255 255 255 255 10 10 10 17 Auto P Edit Delete 10 10 10 16 32 255 255 255 255 10 10 10 17 Auto w Edit Delete Add 10 10 10 18 32 255 255 255 255 10 10 10 17 Auto v EgitDelete Apply Route for IP Check routing amp RACOM Mirova 1283 592 31 Move Mesto na Morave Czech Republic Tel 420 565 659 511 E mail racom racom eu www racom eu If SCADA device addresses can be chosen arbitrarily routing can be significantly simplified when radio IP addresses can be grouped to subnets according to radio network layout One example of simplification is shown with repeaters connecting to separate subnets The routing table can then contain a single record for all devices on the subnet In this example the first repeater connects to subnet 10 10 10 0 29 i e devices may have addresses from 10 10 10 1 to 10 10 10 6 10 10 10 0 is reserved for the subnet address 10 10 10 7 for broadcast ing See e g http www subnet calculator com subnet php net_class A all subnets masks are 255 255 255 248 29 gn 10 10 10 18 10 10 10 19 10 10 10 254 f 10 10 10 17 10 10 10 20 4 1 10 10 10 2 10 10 10 9 i 10 10 10 12 4 10 10 10 3 gn TOS 10 10 10 10 gn ie 10 10 10 11 et Fig 1 2 Network with subnets For 10 10 10 254 RACOM s r o RipEX
19. If you want to have RipEX A management ETH IP subnet reachable from RipEX B you can add this routing rule 192 168 3 0 24 via 10 10 10 2 But this is not necessary for the end station con nectivity Computer Configuration PC 2 IP configuration is the same e IP address 192 168 2 2 RACOM s r o RipEX 97 ARP Proxy amp VLAN e Subnet Mask 255 255 255 0 e Default Gateway 192 168 2 252 Setting of PC 1 is not so straightforward Please set the following parameters e IP address 192 168 3 1 e Subnet Mask 255 255 255 0 e Default Gateway 192 168 3 251 As you can see we are connected to RipEX A within the 192 168 3 0 24 management IP subnet But we still need to configure the VLAN interface This step depends very much on the Operating system OS you use We will describe the necessary steps in Ubuntu 12 04 and will give you a short Windows 7 example too Ubuntu 12 04 In the command prompt run the following commands e modprobe 8021q e vconfig add ethO 2 iplink set eth0 2 up iplink set mtu 1496 dev eth0 2 ipaddr add 192 168 2 1 24 dev eth0 2 The most important command is vconfig which creates the VLAN interface called eth0 2 We enabled the interface decreased the MTU because 4 additional bytes are added to each frame due to the VLAN tag and of course we assigned the IP address to the interface The last two commands create routes so any packet destined to the 192 168 2 2 or 192 168 2 252 is routed v
20. RACOM s r o Profibus Router mode should only be used where network topology does not allow for Bridge mode to be used see page YY of Operating mode the manual If you choose to use Router mode we recom operatingmode Router mend switching off acknowledgement on the radio channel This speeds up packet transmission on the radio channel RSs treshold dB m 120 Repetition of undelivered packets is ensured through the application layer of the DP Master 7 3 2 COM2 desee Fig 7 2 ACK Off Profibus DP utilises RS485 interface This interface can only be set to COM2 in RipEX COM2 functionality is conditioned by using the appropriate software key see chapter Maintenance of the manual COM2 settings must correspond to PLC device settings We recommend setting port speed to 9600 for complex networks or 19200 bps for networks without re translation the timing is derived from the length of a single bit Idle state can be reduced to as little as 1 In Router mode set Protocol to Profibus For explanation of the individual parameters refer to on line help in the web interface or chapter Settings of the manual Note If Profibus IP s do not correspond to RipEX IP s e g several PLC Slaves are connected to a RipEX over a single bus addresses must be translated using a table 7 4 Advanced settings 7 4 1 Calculation of minimum slot time Setting the appropriate minimum Tslot_Init value for a given netw
21. See the following diagram 90 RipEX RACOM s r o ARP Proxy amp VLAN Radio link Router mode Radio IP 9 gt Radio IP 10 10 10 2 24 Untagged Data 10 10 10 4 24 RipEX A RipEX B ETH IP ETH IP 192 168 2 251 24 192 168 2 252 24 Untagged Untagged Data Data PC 1 PC 2 192 168 2 1 24 192 168 2 2 24 GW 192 168 2 251 GW 192 168 2 252 Fig 11 3 Basic configuration diagram This example does not reflect the common configuration because the computers share the same IP subnet but behind different RipEX units in the Router mode Usually the RipEX units would connect different IP subnets This can easily be done with ARP proxy but in this example we can configure it with special routing rules Note o Do not connect the PCs via X5 converter but use the Ethernet interface You can use the X5 converter just for configuration steps not the connectivity tests RipEX Configuration To access the first RipEX unit go to the Settings and name it RipEX A Set the following IP addresses e Radio IP address 10 10 10 2 mask 255 255 255 0 e Ethernet IP address 192 168 2 251 mask 255 255 255 0 On the second unit set the name to RipEX B and configure it with the appropriate IP addresses e Radio IP address 10 10 10 4 mask 255 255 255 0 e Ethernet IP address 192 168 2 252 mask 255 255 255 0 See the RipEX A settings on the following screen shot RACOM s r o RipEX 91 ARP Proxy amp VLAN
22. T Address planning Destination via Gateway LOL LO shee cea TOTOE 10 10 10 98 29 via 10 10 10 9 19 102T0 6 29 war 10101017 e For 10 10 10 2 WiglOelO 67 29 uq DOs LU SI 105 10 10216729 TO DOS LOST e For 10 10 10 3 and 10 10 10 4 and 10 10 10 5 10 10 10 249 29 via 10 10 1072 lO eye gs 20 00 1022 LO LO LO5T6 29 wie VOI 0052 e For 10 10 10 9 10s CO DOC 129 vo ot D sO rd Or IOXTUSJTO 029 opa 0 LU 10 9 e For 10 10 10 10 and 10 10 10 11 and 10 10 10 12 10 t0 10 249 29 wie 10 10 10 9 LO pO LOE OOo i09 LO AO el hopy7o Aus TUTO DO For 10 10 10 17 LUTBO T0 1 29 word TOLO s102 LO T0510 16729 Sra 10 50 10 17 e For 10 10 10 18 and 10 10 10 19 and 10 10 10 20 10 10 10 249729 Via 10 10 T0717 TOO lye Whe SaNaT LOSU TU0 29 wie 20 210 10 17 1 2 End devices connected over Ethernet Both radio modem s network interfaces must be used for routing Radio modem routing works the same as standard IP routing for more information refer to http www comptechdoc org independent net working guide netguide pdf chapter Network Routing Limitations A f you can set the IP address network mask gateway and routing table in the IP device connected to RipEX 8 RipEX RACOM s r o Address planning There are no limitations to setting up routing in this case The only rule is that the range of radio and Ethernet IP addresses must not overlap B If you can only set the IP address network mask and gateway not th
23. Triggers trpDqX Y Z W 7 Zabbix trapper TRAPS Disabled CN RipEX SNMP Trapper Template Remote station X Y Z W RSS value out of ra Triggers 1 trpRssX Y Z W 7 Zabbix trapper TRAPS Disabled Fig 2 12 Default DQ trap item Click on the item and then click on the Clone button Now you can edit the item Replace the X Y Z W string in the item Name with the remote RipEX IP address e g 192 168 131 55 Do the same in the Key field and select the Enabled option in the Status field See the following example RACOM s r o RipEX 31 SNMP Keep history in days Allowed hosts New application Statistics COM ports Statistics Radio Statistics TCP Modbus Statistics Terminal Servers A Populates host inventory field Description 4 notification to indicate that DQ value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateDg DQ alarm state wyRemDgAvg Remote station Average DX value in hundredths Status Disabled x Fig 2 13 Edited DQ trap item Save the changes and open the host Triggers list Repeat the above steps for the DQ trigger and save the changes You should see the trigger with the enabled status 32 RipEX RACOM s r o SNMP z ZAB B X Help Get support Print Profile Logout Configuration Host groups Templates Maintenance Web Actions Scre
24. alarmStateRxTxEth Alarm state of ETH Rx to Tx packets ratio value wvRx TxEth Local station ETH Rx to Tx packets ratio value from interval lt 1 10000 gt in hundredths 33555 2 10 11 troCom1Pr current A notification to indicate that average COM1 interface Rx to Tx packets ratio value has exceeded threshold limits This notification sends additional inform ation about the event by including the following objects in its varbinding list alarmStateRxTxCom1 Alarm state of COM1 Rx to Tx packets ratio value wvRxTxCom1 Local station COM1 Rx to Tx packets ratio value from interval lt 1 10000 gt in hundredths 33555 2 10 12 troCom2Pr current A notification to indicate that average COM2 interface Rx to Tx packets ratio value has exceeded threshold limits This notification sends additional inform ation about the event by including the following objects in its varbinding list alarmStateRxTxCom2 Alarm state of COM2 Rx to Tx packets ratio value wvRxTxComz2 Local station COM2 Rx to Tx packets ratio value from interval 1 10000 in hundredths 33555 2 10 13 troHwin current A notification to indicate that HW alarm input state has changed This notifica tion sends additional information about the event by including the following ob jects in its varbinding list ifHwAlInput State HW alarm input contact state ifHwAlnputType HW alarm input contact type 33555 2 10 14 troHotStby current A notification to ind
25. been shown in later sections a reasonable use of the exponential modulation can be still be neficial for these systems Based on the results presented the most important concluding notes can be seen in the following When the long distance coverage as well as the overall power efficiency are of the primary applic ation concern the use of exponential modulation techniques 2CPFSK and 4CPFSK at relatively low symbol rates e g 10 4 kBaud can be the recommended option In this case the nonlinear modulation techniques can make use of higher frequency deviation and increase the system gain by outstanding values of receiver sensitivities At the 10 W of output power the system gain of 157 dB and 153 dB for 2CPFSK and 4CPFSK modulation techniques respectively can be expected e When higher symbol rates are selected the exponential modulation techniques lose their power efficiency and their main advantage significantly Further increase of the exponential modulation spectrum efficiency from the values currently being used by the narrowband systems up to 1 bit s Hz can be therefore considered inefficient e From all the modulation formats studied the rr 4 DQPSK can provide the narrowband LMR system with communication efficiency closest to the optimal communication systems The proposed solution based on this modulation technique can reach the spectrum efficiency of up to 1 5 bit s Hz The data sensitivity limit required by 1 can also by fulfilled w
26. community public or PUBLIC to be parsed and the third line will force the snmptrapd to use our script If you don t know what community names you will receive add the following line to accept all community names disableAuthorization yes Don t forget to restart the snmptrapd Use n to force snmptrapd not to translate SNMP OID numbers Otherwise the script will NOT function correctly snmptrapd n Note RipEX default Community string name is public however it can be changed since firmware release 1 3 All RipEX stations within the network must have the same Community string Otherwise disableAuthorization has to be set to yes or set authCommunity variables for all allowed Community string names Note On Ubuntu releases you can define default snmptrapd parameters at e etc default snmpd o TRAPDRUN yes RACOM s r o RipEX 33 SNMP o TRAPDOPTS n p var run snmptrapd pid e etc init d snmpd o TRAPDRUN yes o TRAPDOPTS n p var run snmptrapd pid Basic Trap Functionality Tests Now Zabbix is ready to receive SNMP traps from all RipEX stations and enter them into the database properly In order to test it force the trap to be sent from any RipEX and see whether it appears in the Zabbix front end If not check that the respective UDP port 162 is enabled at your firewall and check the settings again On the RipEX side you can monitor the interfaces to check whether the trap was sent Mon
27. connected to the PLC Master over RS485 while others connect over the radio network This is because in Bridge mode RipEX would broadcasts to radio channel each packet received on RS485 This could cause slower communication in some situations and even collisions when a repeater is used In Router mode only the packets destined for remote PLC Slaves are broadcast over the radio channel while packets sent to the PLC Slaves connected directly over RS485 are ignored i af RS495 i ey RS495 Fig 7 1 RS485 and Radio network http www racom eu eng products m ripex ripex detail html RACOM s r o RipEX 65 Profibus 7 2 Profibus settings We will only be looking at the basic communication parameters of the protocol other parameters correspond to the standard Profibus DPVO Profibus protocol is very sensitive to DP Slave response times Delays are common in radio networks this should be taken into account when setting up Profibus communication parameters Recommended default Profibus settings for data transfer using RipEX radio modems Tslot_Init 16 383 t_bit Max Tsdr 50 t_bit Min Tsdr 11 t_bit Tset 1 t_bit Tqui Ot bit Explanation of acronyms Tslot init Slot time This indicates how long a DP Master should wait for a response from a DP Slave before it repeats a packet or sends another The maximum value is 16 383 Max Tsdr Maximum Station Delay of Responders Sets the maximum DP Slave respo
28. current template will be automatically updated Each Item has its Description SNMP OID number community string UDP port 161 key update in terval and other parameters One of the key parameter is the update interval because it defines how often Zabbix will request various replies from the RipEX stations This interval is predefined to 30 minutes but you should consider changing it to suit your radio network infrastructure 18 RipEX RACOM s r o SNMP The individual items can be in an active or disabled state By default only some items are active based on their importance see the next chapter for more information If you wish to monitor more values activate the desired ones But as already mentioned preferably use the RipEX Ethernet interface for SNMP communication to free up the radio channel If this is not possible consider carefully whether monitoring other values is necessary Always monitor only the values which you really need and with reasonable update times The items are divided into the usage groups called Applications in Zabbix These applications serve for better clarification of the defined items If you wish to be notified whenever any monitored value is out of its threshold range you can define a Trigger for it These notifications are viewable on the Zabbix dashboard item history or you can have e mail jabber sms notifications enabled Each notification can have one of six predefined severity levels
29. designed by RACOM It is not a new SCADA protocol it can actually process different protocols of different vendors It supports both the standard MASTER SLAVE and the MULTI MASTER types of communication At least one Master is required in the network The SCADA protocol to be handled by the UNI has to meet solely the following condition There has to be an 8 or 16 bit protocol address in every message generated by a Master station and the address position in all messages has to be the same The position of address in the reply from an RTU is not relevant because the reply is always send back to the address where the request originated Note Some SCADA protocols use two byte ASCII address which is an ASCII representation of an 8 bit address in the hexadecimal format e g 8C means 8 bit value Ox8C in hex 140 in decimal notation Address bytes for some protocols PR2000 3rd Byte RDS 2nd Byte Mars A 8th Byte without local ACK Hirsch 2nd Byte 9 1 MASTER SLAVE communication Master reads the address byte defined by configuration and generates the destination IP address using the mask or the translation table The message is then delivered to that IP address and the respective UDP port e g the port No 8882 which is assigned to the COM2 interface Protocol Protocol Mode of Connected device Address made Binary 1E Address position Poll response control On bul Broadcast Broadcast addr format Broadcast address
30. enables different speeds to be used simultaneously in a radio modem network The following picture gives an example of a network layout Let us assume that all signals are strong enough to ensure almost perfect operation i j amp Fig 4 1 Autospeed initial situation After some time situation changes and path loss on one of these links significantly increases rendering the communication unreliable j l ay s Bua d m Fig 4 2 Autospeed problem What can we do e Change antennas on one or both sides of the link Use higher masts on one or both sides of the link Build additional repeater s Lower the data rate significantly to increase the system gain The first three possibilities require time and money i e additional investment The fourth possibility when applied to whole network as it normally is the case would slow down the response time two 58 RipEX RACOM s r o Autospeed to four times of the whole network quite probably making it unusable for the application RipEX Auto speed feature allows to change the transmission data rate at the affected radios only the rest of the network may continue in full soeed Consequently the overall performance of network is maintained practically at the same level while no additional investment is required More over the whole fix can be done in minutes from behind a web browser screen while sitting in your offi
31. ere an creak routing Backup stus T Route for IP Fig 12 8 RipEX A Backup path is Up Note For proper functioning do not forget to repeat these steps on the partner RipEX C unit If not set on both units RipEX A can communicate with RipEX C via the primary path in one direction and via the backup path in the other direction asymmetric routing To revert to using the primary path again disable RSS checks or improve the RSS signal between the RipEX units 12 3 2 Radio Radio End Devices Connected via Ethernet Interface In the second example we use the same configuration except that the RTU devices are connected via the Ethernet interface See the following diagram Radio 10 10 10 18 18 Radio 10 10 10 17 192 168 18 2 24 PATH 2 E Radio 10 10 10 15 gw 192 168 18 1 PATH 1 A A c 00017 192 168 17 2 24 gw 192 168 17 1 RipEX A ETH Radio 10 10 10 16 192 168 15 2 24 gw 192 168 15 1 RipEX B lle ETH 192 168 16 2 24 gw 192 168 16 1 Fig 12 9 Network topology 2 110 Radio 10 10 10 19 192 168 19 2 24 gw 192 168 19 1 RipEX RACOM s r o Backup routes Note In this example we switched the priorities for the alternative paths RTU units are now connected via the Ethernet ports which means we need to add the correct IP ad dresses and routing into the appropriate RipEX units If not already set change the Ethernet IP addresses according to
32. hum and noise of the transmitter Adjacent channel power is usually ref erenced to the unmodulated carrier power 1 For a channel separation of 25 kHz the adjacent channel power shall not exceed a value of 60 dB below the transmitter power without the need to be below 37 dBm It is interesting to note that until 07 2007 the standard strictly demanded the adjacent channel power ratio of 70 dB The ACP parameter is particularly important in LMR systems since it influences the density of the radio channels that can be used in a given area Its value originated in the use of the traditional analog fre quency modulated FM radio systems Ironically it was one of the main limitations for why those systems were for many years not able to utilize spectrally more efficient modulation schemes The problem in this case is that all the advanced multi level modulation techniques such as M PSK M QAM OFDM CDMA or FBMCM have one negative property and that is a non constant modulation envelope RBW 100 Hz RBW 100 Hz VBW 30 Hz SWT 34 s PUR d ahil ald sss Wiad ta Center 420 0125 MHz 10 kHz Span 100 kHz Center 420 0125 MHz 10 kHz Span 100 kHz Tx Channel Tx Channel Bandwidth 25 kHz Power 10 06 dBm Bandwidth 25 KHZ Power 10 21 dBm Adjacent Channel Adjacent Channel Bandwidth 16 kHz Lower 62 02 dB Bandwidth 16 kHz Low
33. i e RipEX s retransmissions are always more effective than the application ones since the radio modem can use more information from the channel when calculating the retransmission time out Moreover when repeaters are involved re 86 RipEX RACOM s r o Channel access transmitting over a single hop is always faster and has a greater chance to succeed than retransmitting over the whole path Consequently a reasonable approach is to set application time out to maximum value possible and use an adequate number of Retries in RipEX s in the network Though the application engineers may find it difficult to understand such setting will make the application run faster There are few exceptions and hitches though There are applications which rather send a fresh data instead of simply retransmitting the original message In such case depending on the frequency of fresh data from the application the Retries should be setto 1 or ACK switched off completely Sometimes the application is hard wired and the retransmission time out cannot be changed then it is better to minimize or switch off RipEX s retransmissions again The trickiest case is when the application centre generates messages to non existent or switched off remotes for any reason When a remote site is without power including the RipEX and the centre continues sending requests to that remote the last repeater will keep retransmitting these requests for full number of Retries se
34. of Celsius C 33555 2 5 1 15 alarmThrRfP read only current Alarm threshold minimum RF power wrMin value in tenths of Watt W 33555 2 5 1 16 alarmThrRfP read only current Alarm threshold maximum RF power wrMax value in tenths of Watt W 33555 2 5 1 17 alarmThrVswrMin read only current Alarm threshold minimum VSWR value from interval 3 25 in tenths 33555 2 5 1 18 alarmThrVswrMax read only current Alarm threshold maximum VSWR value from interval 3 25 in tenths 99999 2 9 1 31 alarmThrRx jread only current Alarm threshold minimum ETH inter TxEthMin face Rx to Tx packets ratio value in hundredths 33555 2 5 1 32 alarmThrRxTxEth read only current Alarm threshold maximum ETH inter Max face Rx to Tx packets ratio value in hundredths 33555 2 5 1 33 alarmThrRxTx read only current Alarm threshold minimum COM in Com1Min terface Rx to Tx packets ratio value in hundredths 33555 2 5 1 34 alarmThrRxTx read only current Alarm threshold maximum COM1 in Com1Max terface Rx to Tx packets ratio value in hundredths 33555 2 5 1 35 alarmThrRxTx read only current Alarm threshold minimum COM2 in Com2Min terface Rx to Tx packets ratio value in hundredths 33555 2 5 1 36 alarmThrRxTx read only current Alarm threshold maximum COM in Com2Max terface Rx to Tx packets ratio value in hundredths 33555 2 5 2 1 alarmStateRss Alarm state RSS 33555 2 5 2 2 alar
35. of remote stations ber 33555 2 4 3 wvRemoteTable not access current List of remote stations ible 33555 2 4 3 1 wvRemoteEntry Remote station watched values entry ible 33555 2 4 3 1 1 X Remote station Unique index 33555 2 4 3 1 2 X wvRemlpAddr Remote station IP address 33555 2 4 3 1 3 X wvRemHearings read only current Remote station Total heard packets from the remote station 33555 2 4 3 1 4 X wvRemRssLast read only current Remote station Last RSS value in dBm 33555 2 4 3 1 5 X wvRemRssAvg read only current Remote station Average RSS value in hundredths of dBm 33555 2 4 3 1 6 X wvRemDqLast Remote station Last DQ value 33555 2 4 3 1 7 X wvRemDqAvg read only current Remote station Average DQ value in hundredths 33555 2 4 3 1 12 X wvRemTxLostLast Remote station Last Tx lost value in 33555 2 4 3 1 13 X wvRemTxLostAvg read only current Remote station Average Tx lost value in hundredths of 96 33555 2 4 3 1 14 X wvRemUccLast read only current Remote year Last UCC value in tenths of Volt V 33555 2 4 3 1 15 X wvRemUccAvg read only current Remote station Au UCC value in thousandths of Volt V 33555 2 4 3 1 16 X wvRemTempLast read only current Remote station Last us rid ure value in tenths of Celsius C 33555 2 4 3 1 17 X wvRemTempAvg read only current Remote station Average s tem perature value in thousandths of Celsius C 33555 2 4 3 1 18 X wvRemRfPwrLast read meni c
36. over Ethernet and COM ports or if you require remote access to a network which uses COM ports border RipEX s must be interconnected both via Ethernet see 1 1 and COM see 1 2 5 2 Back to Back in Router mode In Router mode border RipEX s are interconnected by Ethernet cable Routing in both parts of the network must be set up so that communication passes through the Ethernet interface of the border RipEX s We recommend splitting both radio networks to two separate LAN networks 60 RipEX RACOM s r o COT O00 S et IP 192 168 10 100 Mask 255 255 255 0 ae fi O00 Shea IP 192 168 10 200 Mask 255 255 255 0 Fig 5 2 Back2Back in bridge mode IP 192 168 20 2 ask 255 255 255 0 Routing GW 192 168 20 254 got a 000 S IP 192 168 30 3 Mask 255 255 255 0 Routing GW 192 168 30 254 Fig 5 3 Back2Back in router mode RACOM s r o RipEX Back2Back lsh _Back2Back m Back to Back repeater O00 S IP 192 168 10 300 Mask 255 255 255 0 f2 9 000 S e IP 192 168 10 400 Mask 255 255 255 0 IP 192 168 40 4 Mask 255 255 255 0 Routing GW 192 168 40 254 f2 O00 S E re 192 168 50 5 Mask 255 255 255 0 Routing GW 192 168 50 254 61 Combining MORSE and RipEX networks 6 Combining MORSE and RipEX networks When expanding a MORSE network with RipEX radio modems different arrangements are possible
37. power the radio transceiver can reach wider system gain at higher spectrum efficiencies while running in linear as oppose to the exponential modulation mode On the other hand if the long distance coverage is of the primary application concern even the 2CPFSK modulation having spectrum efficiency of 0 4 bit s Hz but the system gain of impressive 157 dB can be a reasonable option RACOM s r o RipEX 99 Data speed and Modulations Tab 3 2 Overall performance characteristics of the narrowband radio transceiver for selected modes of operation Available Modulation Modul Symbol Raw Bit Spectrum Sensitivity Output System Format Param Rate Rate Efficiency BER 107 Power Gain EH H kBaud kbits s bit s Hz dBm dBm dB h 0 6 2CPFSK h 0 2 0 0 28 17 36 17 36 107 40 147 h 0 3 4CPFSK h 0 1 0 0 28 1736 34 72 1 39 102 40 142 Measurement uncertainty 2 dB 3 3 Conclusion As it was shown in this paper the strict limits of the referenced standard as well as the state of the technology hindered increasing the communication efficiency with which the narrowband systems have been using the occupied frequency bandwidth The key limiting factor that has been identified was the limit of adjacent channel power attenuation Lessening the requirement from 70 dBc to 60 dBc in 2007 has opened up the closed door for implementation of linear digital modulation techniques However as it has
38. site there is an installation documentation Follow the steps described Simple guide for version 2 0 x comments start with a double slash sign Szabbix frontend path to Zabbix frontend in Ubuntu var www zabbix your src directory with SNMP builder tar gz file Sdistname name of the SNMP builder ditribution 1 cd zabbix frontend 2 tar xvzf Syour src Sdistname snmpbuilder 2 0 imgs tar gz 36 RipEX RACOM s r o SNMP 3 patch p1 lt your src distname snmpbuilder 2 0 patch 4 cp r your src distname zabbix 5 Restart the Apache service service apache2 restart OR etc init d apache2 restart If you have been successful the SNMP Builder folder is added in the Zabbix front end Configuration Administration General DM Authentication Users Media types Scripts Audit Queue Notifications Locales Installation SEARCH History Latest data Zabbix Latest data Host groups Zabbix SNMP Template RipEX Gomplele 7j me Host 19216613123 SNMP version Community pubic Builder OID Tree OID Data Force view as table m APEX s Oid Name Type Value 3 p RIPEX stationName STRING RipexTP ae B amp internet SNMP OID Description Type of information Data type Units Custom multiplier Delta directory E H C mgmt experimental 1 amp private Interval 60 History 90 Trends 365 rien 3 racom i Create Graph Name Width Hei
39. to broadcast in Modbus set the re quired parameters For more information refer to on line help or chapter Protocols Slave of the manual 8 1 1 Modbus RTU with multiple Masters reuse Cu S i Modbus RTU O00 S us 0S Modbus RTU ME lt es US Mua Modbus RTU Uis Modbus RTU RS232 Modbus RTU a RS232 Modbus RTU Fig 8 2 Modbus RTU with multiple Masters RipEX allows for several Masters to operate at the same time and to communicate with the same Slaves Router mode is presumed in this design RipEX settings remain the same as above Each Slave responds directly to the Master unit which queries it i e if Master A issues a query to a Slave the response is sent exclusively to Master A If a single Slave is queried by two Masters at once queries are resolved one by one Query from the second Master is queued inside RipEX until it receives a response from Slave RTU on its serial interface or until 500 ms timeout has passed 8 2 Modbus TCP A standard simple network with a single Master and several Slaves running Modbus TCP A TCP IP connection is established and maintained between Master PLC and Slave RTU across the entire radio network In Bridge mode no special setup is required RipEX operates as an intelligent Bridge For more inform ation refer to on line help or chapter ETH Modbus TCP of the manual In Router mode routing must be set up in the radio network Communication between the IP addre
40. trpRss current A notification to indicate that average RSS value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateRss RSS alarm state wwRemRssAvg Remote station Av erage RSS value in hundredths of dBm wvRemlpAddr Remote station IP ad dress 33555 2 10 2 trpDq current A notification to indicate that average DQ value has exceeded threshold limits This notification sends additional inform ation about the event by including the RACOM s r o RipEX 45 SNMP following objects in its varbinding list alarmStateDq DQ alarm state wvRemDqAvg Remote station Aver age DQ value in hundredths wvRemlpAddr Remote station IP ad dress 33555 2 10 5 troTxLost current A notification to indicate that average Tx lost value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateTxLost Tx lost alarm state wvTxLostAvg Local station Average Tx lost value in hundredths of Jo 33555 2 10 6 troUcc current A notification to indicate that average UCC value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateUcc UCC alarm state wvUccAvg Local station Average UCC value in tho
41. you choose another one you will need to alter at least the trap handling bash script provided Windows Installation If you need to use Windows platform as the host operating system for Zabbix you can install VMware Vir tualBox software and install Zabbix Appliance The Zabbix Appliance can be downloaded from ht tp www zabbix com download php Please remember that Zabbix Appliance is not intended for serious production use at this time VMware download https www vmware com support VirtualBox download https www virtualbox org wiki Downloads See the respective documentation on how to install and use virtualisation software 2 3 2 Templates After successful installation you can import any of the predefined templates Each template is the collection of Zabbix Items corresponding to a set of OIDs triggers graphs and applications The template can be easily linked to any monitored host RipEX and you can have access to the desired values very quickly What Templates do we Provide The Templates list Name RipEX Template o Consists of all specific OIDs provided by RACOM o mplements one neighbouring RipEX monitoring o 17 Applications 237 Items 4 Triggers 5 Graphs e Name RipEX RFC1213 Template o Consists of supported RFC1213 OIDs o 1 Application 56 Items e Name RipEX RS232 Template o Consists of supported RS232 OIDs o 1 Application 21 Items e Name RipEX SNMP Trapper Template o Consists of SNMP trapper
42. you need to clone the item within the host configuration tem list To enable the settings to change you need to click on the Clone button first the software will then allow you to change the settings Total bandwidth used requests replies if monitoring only the values defined above e Approx 3 kB 1 RipEX station 1 hour 2 3 3 How to Import Monitored RipEX Stations Now you have a working template but you need to define hosts RipEX stations Each RipEX station has its own IP address The following steps will guide you through the Host Configuration To create a host go to Configuration Hosts and click on the Create Host button Define the Host name and its IP address Host name 192 168 1 10 Visible name RipEX1 Groups In groups RipEX Fig 2 5 Defining the Host name and its IP address You can optionally define a Group for the hosts Creating a Group is straightforward You can create a new one while creating a host or you can do so by going to the Configuration Groups tab and clicking on the Create Group button Linking a template to the host s can be achieved under the same tab or you can open Template settings and link any desired host to it You have to set the IP address and port number for the SNMP interface port 161 Otherwise you won t be able to use any SNMP item 20 RipEX RACOM s r o DEEP nah SKE ee bie A CRO UN SMU A T I ORES SECS AE CaNeSSES CRT MEMS bENS LLL eces Rhee DIL IL
43. 10 10 16 Off RipEX D wv Delete Add PI 10 10 10 159 32 209 200 200 200 10 10 10 16 OF RipEX E v Delete Add nd Delete Add Add Monitoring Backu Maintenance P Alternative paths Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Backup 1 10 10 10 17 20 Delete Add 10 10 10 17 Default wf Direct link T Add 10 10 10 16 Default v Indirect link Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 3 RipEX A Routing menu example 1 106 RipEX RACOM s r o Backup routes In RipEX A we have one route which uses the backup configuration and two simple routes to other RipEX units The backup route is named Backup 1 and it checks its health against the RipEX C radio IP address The highest priority is set to the direct link and the second possibility is to use RipEX B as a repeater Both paths are now checked by default and both are Up Note Only the remote RipEX radio or the main Ethernet interface IP addresses can be used no subnet IP addresses on RipEX Ethernet or IP of connected device behind RipEX See the respective configurations from RipEX B and C 2 4 Radio modem amp Router 3 4 NCCCONAA sd Status Values from RipEX B ATTI 10 10 10 16 Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BAco4 2B IP 10 10 10 16 Mask 255 255 255 0 1 ETH MAC 00 02 A9 BA 50c43 IP 192 168 16 1 Mask 255 255 255 0 Diagnostic Neighbours Routes
44. 100 2 am 192 168 100 1 192 168 2 1 a RipEX A RipEX B PATH 1 Fig 12 17 Network topology 3 Note This example will not be explained in as such detail as the previous ones and we will use different IP addresses pP gt f C Radio modem amp Router Co PRACOM Status Values from RipEX A Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BB 0F AB IP 10 10 10 1 Mask 255 255 255 0 re ETH MAC 02 AS BR OB C3 IP 192 168 100 1 Mask 255 255 255 0 Diagnostic Neighbours Routes f c Destination Mask Gateway Backup Note Active Modify Hu 192 168 2 0 24 200 250 255 0 Backup 1 wf 7 Delete Add Graphs 192 168 100 2 32 299 255 205 255 i Backup 1 v Delete Add Ping ul Add Monitoring Backup i Alternative paths Maintenance Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Backup 1 192 168 100 2 20 Delete Add 492 168 100 2 v M Add 10 10 10 2 Default wv m Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 18 RipEX A Routing menu example 3 The primary Ethernet link provides a high bandwidth capacity It is appropriate to send Hello packets every second This will lead to a rapid switch over to the backup radio link in case of the Ethernet link failure ping recvmsg No route to host ping recvmsg No route to host From 197 168 15 1 icmp seq 558 Destination Host Unreachable From 192 168 15 1 icmp seq 559 Destination Host Unreachable 88 bytes from 192 168
45. 17 1 icmp req 563 ttl 64 time i74 ms 88 bytes from 192 168 17 1 icmp req 564 ttl 64 time 157 ms 88 bytes from 192 168 17 1 icmp req 565 ttl 64 time 174 ms Fig 12 19 Hello packet period set to one second 116 RipEX RACOM s r o Backup routes RipEX B is configured with 192 168 100 2 24 IP address which is used only for communication between RipEX units The additional subnet 192 168 2 0 24 is used for the rest of the Ethernet communication See the details in ARP Proxy amp VLAN Application note The Hello packet period for the Ethernet link is also set to one second on RipEX B C RACOM m 3 f 2 X Radio modem amp Router Status Values from RipEX B Remote IP Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BA 73 6B IP 10 10 10 2 Mask 255 255 255 0 E ETH MAC 00 02 A9 BA6F 83 IP 192 168 100 2 Mask 259 255 255 0 VLAN amp Subnets Diagnostic Neighbours Routes maru Destination Mask Gateway Backup Note Active Modify 192 168 100 1 32 255 255 255 255 Backup 1 v Delete Add Graphs Add ome Backup Monitoring Alternative paths m Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Maintenance Backup 1 192 168 100 1 20 Delete Add 192 168 100 1 v T gums 10 10 10 1 Default v a Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 20 RipEX B Routing menu example 3 When you disconnect the primary Ethernet path the system will automatically s
46. 2 1 or ping 192 168 2 251 if you are executing the ping from the PC 1 and check the results You can also try the other direction just switch IP addresses See the following example Ge C Windows system32 cmd exe E Microsoft Windows RIT ERE USE Copyright c 2009F Microsoft Corporation All rights reserved CoNUsers it gt ping 192 168 2 1 Pinging 192 168 2 1 with 32 bytes of data Reply from 192 168 2 1 bytes 32 time 56ms TTL 62 Reply from 192 168 2 1 bhytes 32 time b6ms TTL 62 Reply from 192 168 2 1 bytes 32 time 75ms TTL 62 Reply from 192 168 2 1 bytes 32 time 57ms TTL 62 Ping statistics for 172 168 2 1 Packets Sent 4 Received 4 Lost B z loss gt Approximate round trip times in milli seconds Minimum 56ms Maximum 75ms Average 63ms Fig 11 7 Ping results Basic configuration 94 RipEX RACOM s r o ARP Proxy amp VLAN Note If the ping is not successful try to turn the Windows firewall off It can block the ping packets 11 4 2 ARP Proxy If we would not have computers as the end stations but only simple RTUs it may happen that routes and default gateways cannot be configured In this case we need to reach the connectivity via the ARP proxy feature See the diagram Radio link Router mode Radio IP hi pi Radio IP 10 10 10 2 24 Untagged Data 10 10 10 4 24 RipEX A RipEX B with ARP proxy with ARP proxy ETH IP ETH IP 192 168 2 251 24 192 168 2 252 24
47. 2 168 2 1 gt 192 168 2 2 ICMP ecto remues id 18967 seq 6 length 64 Ox0000 0002 a9bb Obc3 0023 aez 5ee 8100 0002 Graphs x 010 O800 4500 0054 0000 4000 4001 b555 c a8 Ping Ox0020 0201 c a8 0202 0800 3f0d 4a17 0006 286e 0x0030 4c51 0000 0000 3a43 0100 0000 0000 1011 Monitoring Ox0040 1213 1415 1617 1819 lalb 1cld lelf 2021 Ox0050 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 Ox0060 3233 3435 3637 14 42 59 674102 RF phy Tx 96 RLhead 4ea0 Olba 736b bb f ab TU TU TU 2 T0 10 10 4 LN 5 A y R DChead 00 F C E Ox0000 0800 4500 0054 0000 4000 3f01 b655 clas 0x0010 0201 cOa8 0202 0800 3f0d 4a17 0006 286e 0x0020 4c51 0000 0000 3a43 0100 0000 0000 1011 0x0030 1213 1415 1617 1819 lalb 1cld lelf 2021 Ox0040 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 x0050 3233 3435 3637 14 42 59 736328 RF phy Rx 2e IP RLhead 4e34 Olbb Ofab ba73 6b DChead 00 F C E Ox0000 0800 4500 0054 Od3d 4000 7f01 6918 c aB8 0x0010 0202 cOa8 0201 0000 470d 4a17 0006 286e 0x0020 4c51 0000 0000 3a43 0100 0000 0000 1011 0x0030 1213 1415 1617 1819 lalb 1cld lelf 2021 Ox0040 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 Ox0050 3233 3435 3637 14 42 59 738444 ETH IP 192 168 2 2 gt 192 168 2 LL LLCME echten id 18967 seq 6 length 64 Ox0000 0023 ae02 Seed 0002 a9bb Obc3 8100 0002 8 CUa Ox0010 O800 4500 0054 Od3d 4000 7e01 bale Maintenance 92 168 2 2 gt 192 168 2 1 AFP echo reply length
48. 255 Address translation Mask Base IP 10 0 0 1 Mask 255 255 255 UDF part interface An example of Master configuration is in the picture above The address translation then proceeds as follows RACOM s r o RipEX 77 UNI protocol The 5th byte from the incoming message from SCADA centre is used to replace the last byte of the Base IP and the resulting IP address is used as the destination of the UDP datagram which contains the original SCADA message Let assume that the content of 5th byte is 0x65 then the IP destination address will be 10 0 0 101 and the UDP port 8882 The translation by a table is more versatile however it requires an extra line of configuration for every remote in the network The table has to be used when addresses of RipEX radiomodems and SCADA RTUs do not match or different ports interfaces at different remotes have to be configured Protocol Protocol Mode of Connected device Address mode Binary 1E Address position Poll response control on em Broadcast Address translation Hex UHI adr IP Interface UDP port Hote Active Modify 10 0 0 101 COM 8882 v T Edit Delete Add 10 0 0 32 COM 8882 w Edit Delete Add 10 0 0 32 COM 8882 Edit Delete Add 10 0 0 32 COM2 8882 v Edit Delete Add The example of table in the picture above demonstrates a situation when there are three SCADA devices connected to the COM2 of a single RipEX unit over a RS485 bus The configura
49. 4 Eth Cay MA l 10 10 1 4 24 192 168 3 254 24 Eth qe 192 168 1 0 2 4 via 10 10 1 2 0 10 1 4 10 10 1 1 24 192 168 255 2 24 192 168 2 253 24 gw 192 168 2 254 192 168 255 1 24 gw 192 168 255 2 Eth 192 168 3 253 24 gw 192 168 3 254 Fig 1 3 Network with standard masks 192 168 1 0 29 via 10 10 1 9 192 168 1 8 29 via 10 10 1 10 192 168 255 0 24 via 10 10 Eth T 192 168 255 0 24 via 10 10 1 5 l Eth 10 10 1 5 24 192 168 1 62 24 ge 10 10 1 9 24 192 168 1 6 24 0 10 1 192 168 1 5 24 000 S gw 192 168 1 6 e 10 10 1 10 24 192 168 1 14 24 Eth e 192 168 1 13 24 I S aw 192 168 1 14 e 10 10 1 11 24 192 168 2 70 24 Eth e 192 168 2 69 24 gri 000 S ow 192 168 2 70 10 10 1 12 24 192 168 2 78 24 Eth 192 168 2 77 24 Ns gw 192 168 2 78 10 10 1 13 24 192 168 3 6 24 Eth e 192 168 3 5 24 II S ow 192 168 3 6 10 10 1 14 24 192 168 3 14 24 Eth 192 168 1 61 24 gw 192 168 1 62 10 10 1 6 24 192 168 2 62 24 OS 192 168 2 61 24 gw 192 168 2 62 l 10 10 1 7 24 192 168 2 126 24 192 168 2 125 24 000 S ow 192 168 2 126 l 10 10 1 8 24 192 168 3 62 24 E 192 168 3 61 24 I S ow 192 168 3 62 f Eth 192 168 3 13 24 DOOS gw 192 168 3 14 Virtual network narrowing may also be used while in reality narrower masks will be only used for routing purposes This would allow you to use even the addr
50. 4 1 7 wvUccLast read only current Local station Last UCC value in tenths of Volt V 33555 2 4 1 8 wvUccAvg read only current Local station Average UCC value in thousandths of Volt V 33555 2 4 1 9 wvTempLast read only current Local station Last device temperature value in tenths of Celsius C 33555 2 4 1 10 wv TempAvg read only current Local station Average device temper ature value in thousandths of Celsius C 33555 2 4 1 11 wvRfPwrLast read only current Local station Last RF power value in tenths of Watt W 33555 2 4 1 12 wvRfPwrAvg read only current Local station Average RF power value in thousandths of Watt W 33555 2 4 1 13 wvVswrLast read only current Local station Last VSWR value from interval 3 25 in tenths 33555 2 4 1 14 wvVswrAvg read only current Local station Average VSWR value from interval lt 300 2500 gt in thou sandths wvRxTxEth read only current Local station ETH interface Rx to Tx packets ratio value from interval 1 10000 in hundredths WVRXxTxCom 1 read only current Local station COM 1 interface Rx to Tx packets ratio value from interval lt 1 10000 gt in hundredths 33555 2 4 1 41 33555 2 4 1 42 42 RipEX RACOM s r o SNMP 33555 2 4 1 43 wvRxTxCom2 read only current Local station COM2 interface Rx to Tx packets ratio value from interval lt 1 10000 gt in hundredths 33555 2 4 2 wvRemoteNum read only current Number
51. 5 eon 26 gt ethernet 3Mbit RACOM s r o RipEX 25 SNMP RFC1213 ifType 2 nsip 28 slip 29 ultra 30 gt ds3 31 gt sip 32 gt frame relay RFC1213 ipForwarding 1 gt forwarding 2 gt not forwarding RFC1213 snmpEnableAuthenTraps 1 2 enabled 2 gt disabled RS232 rs232AsyncPortParity 1 none 2 odd 3 gt even 4 mark 5 gt space RS232 rs232AsyncPortStopBits 1 gt one 2 two 3 oneAndHalf 4 dynamic RS232 rs232PortlnFlowType 1 none 2 gt ctsRts 3 gt dsrDtr RS232 rs232PortType 1 other 2 gt rs232 3 gt rs422 4 rs423 5 gt v35 26 Items Items RFC1213 The indication of whether this entity is acting as an IP gateway Items RFC1213 SNMP Indicates whether the SNMP agent process is permitted to generate authentication failure traps Items RS232 port 1 The port s sense of a character parity bit RS232 port 2 The port s sense of a character parity bit Items RS232 port 1 The port s number of stop bits RS232 port 2 The port s number of stop bits Items RS232 port 1 The port s type of input flow control RS232 port 2 The port s type of input flow control RS232 port 1 The port s type of output flow control RS232 port 2 The port s type of output flow control Items RS232 port 1 The port s hardware type RS232 port 2 The port s hardware type RipEX RACOM s r o SNMP
52. 92 168 2 70 192 168 2 77 29 gw 192 168 2 78 10 10 1 13 24 192 168 3 6 29 Ul S ey wsi 10 10 1 14 24 192 168 3 14 29 192 168 3 5 29 gw 192 168 3 6 192 169 3 13 29 gw 192 168 3 14 11 SNMP 2 SNMP 2 1 Simple Network Management Protocol SNMP is a simple widely used and useful standardised protocol typically used by Network Management Software NMS to read values from devices Values can be obtained at regular intervals or on requests saved to a database and then displayed as graphs or tables SNMP also enables devices to generate trigger the alarms by themselves and notify the NMS explicitly SNMP traps 2 1 1 How does SNMP work SNMP requires two parties for communication 1 SNMP manager software installed at your computer e You can use commercial software or free software such as Zabbix Zenoss Nagios Cacti etc If you want to read values manually you can use tools such as snmpwalk snmpget or Mib browser software 2 SNMP agent a part of firmware in remote devices such as RipEX e The agent receives SNMP requests to query information and responds to the manager Several managers may read values at once and they can send their requests at any time Alternatively the agent sends SNMP traps whenever the monitored values watched values in RipEX e g temperature are outside the threshold range RipEX is capable of sending SNMP traps to up to two SNMP managers since the firm
53. EP RACOM RADIO DATA NETWORKS Application notes CENTER version 1 5 4 11 2014 fw 1 3 x x RACOM s r o Mirova 1283 592 31 Nove Mesto na Morave Czech Republic Tel 420 565 659 511 LEM mt E 10 565 659 512 E mail racom racom eu Table of Contents As PACING SS AN MUNG ots Mn 5 1 1 End devices connected via serial interface ccccccceccceseeeeeeeeeeeteeeeeeeeeeeteeeseeeteeteeeteeens 5 1 2 End devices connected over Ethernet srinniennae aa 8 gas E Inerhelddaressillbl Deemer ieee em ee ee enero re eer cee ee eee 9 LII ur UrR T 12 2 1 Simple Network Management Protocol seeesssessssssseseeeeenene nnne nnne 12 2 2 SSINIVIEEIBETSIDEUN aaea ade trees eI I Cr SIM D ISDEM PM DEI ILI DID LM D EU DIUI 13 2 3 Network Management System ZABBIX ssessssssseesssessseeeesee nennen nennen nnn nnn nnns 16 2 4 How do Know that Something Has Happened to the RipEX Station 28 2 What Else does ZabbbCOlTIGl e sesocsau tien bu a Pp UD ET OR Rd Mm Rn dr uae scene e eens 35 220 RDEX MB Ta Dle ar uh n diese uet mse ne amt ene Neer eee Ne ene eee E 38 3 Data speed and ModulatlORnis iue espe e hx ia Ee air e x o aa aso cde dr Ea Me o beca o NO Cow as 49 3 1 Narrowband radio transrmiltter i uaa tuer rero a Eee ev bre ERE EU Ford pex e
54. ILIITRCD T SEN T EE EE E ROEN EE AE A E tin resGioegae tines inisesmeeheus IIICLEB Cabos tab III I LLLI Agent interfaces IP address DNS name Connect to Port Default SNMP interfaces 192 168 131 239 Oooo ar J e Add Fig 2 6 Defining the SNMP interface Where can I See the RipEX Monitored Values To check monitored values go to the Monitoring Latest data tab and choose the desired host from the Menu ITEMS Group Host Ripex TP z Filter Desciotion s lache Laat value Change History COM ports 18 Items Ethernet 5 Items Local Station 11 Items Station working mode 10 Sep 2012 10 46 34 router 2 poer Graph Radio HW version 10 Sep 2012 10 46 42 1 1 50 7 History Fig 2 7 RipEX latest data For each item you can see a graph or a history table If a trigger is configured for the item the graph shows a line with a threshold value g T Ripex TP Local station average modem temperature value in C e e e e oco e i last min avg max E Local station average modem temperature value in C all 33 18 C 31 8 C 36 89 C 40 43 C Fig 2 8 RipEX graph RACOM s r o RipEX 21 SNMP 2 3 4 Value Mappings Responses of Several OID objects are unsigned integers but these values have a special meaning Example 2 1 deviceMode e 1 stands for bridge mode e 2 stands for router mode Unfortunately by default you can see only the numeric values at the Zabbi
55. In the following paragraphs we assume that the whole network is divided into two parts the MORSE part and the RipEX part The two parts are interconnected through two radio modems one MRxxx and one RipEX hereafter referred to as border radio modems As RipEX and MRxxx radio channel protocols are not compatible we strongly recommend you use different frequencies for either part of the network 6 1 RipEX part in Bridge mode There are two basic scenarios e Terminal devices are connected to Ethernet interface Terminal devices are connected to COM port 6 1 1 Terminal devices connected over Ethernet If terminal devices are connected over Ethernet the border RipEX and MRxxx should also be intercon nected by an Ethernet cable The IP addresses of all devices in the network should belong to a single LAN The picture shows MORSE network settings note the use of Proxy ARP in IP M IP mode 000 Sh lt lt IP 192 168 10 160 IP hex C0 A8 0A A0 Mask 255 255 255 0 000 S c IP 192 168 10 1 IP hex C0 A8 0A 01 Mask 255 255 255 0 Eth cable O00 Ses IP 192 168 10 2 Eth IP 192 168 10 161 IP hex C0 A8 0A 02 IP hex C0 A8 0A A1 ws Mask 255 255 255 0 Mask 255 255 255 0 Fig 6 1 RipEX MR400 in Bridge mode 6 1 2 Terminal devices connected to COM The COM port of the border RipEX and the RS232 of the border MRxxx are connected with a crosslink serial cable see Fig 6 2 Crosslink serial cable
56. Neighbours menu The value needs to be higher than the current value e g in the example the current RSS value is 56 dBm The condition for switching to the backup indirect path is set to 50 dBm Policy Parameters Hello packet sec RSS dBm Hello packet success rate 25 87 5 g Lower priority paths checking On cw r Fig 12 7 RipEX A Alternative path RSS change Apply the changes and click on the Backup status button to see the changes The policy is set to Manual and the backup indirect path is being used RACOM s r o RipEX 109 Backup routes RIDE Radio modem amp Router Status Values from RipEX A Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BB 0F AB IP 10 10 10 15 Mask 255 255 255 0 3 ETH MAC 00 02 AS BB OB C3 IP 192 168 15 1 Mask 255 255 255 0 Diagnostic Neighbours Routes mens Destination Mask Gateway Backup Note Active Modify S 10 10 10 17 32 255 255 255 255 Backup 1 Backup RipEX C v Delete Add Graphs 10 10 10 18 32 255 255 255 255 10 10 10 16 Off RipEX D Delete Add LE 10 10 10 19 32 255 255 255 255 10 10 10 16 Off RipEX E vl Delete Add Tri pa a Add Monitoring d Backu Maintenance P Alternative paths Mame Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Backup 1 10 10 10 17 20 Delete Add 10 10 10 17 v Direct link M Add 10 10 10 16 Default v Indirect link Add Add Legend Up Down Unknown Currently used ec
57. RipEX RFC1213 Template o Allitems are disabled by default e RipEX RS232 Template o Allitems are disabled by default RipEX SNMP Trapper Template o All SNMP trap items and triggers are enabled by default except DQ and RSS These triggers need to be cloned for individual hosts because we cannot predefine remote hosts IP addresses See Chapter 2 4 2 for more information e PING Template RACOM s r o RipEX 19 SNMP o Pre activated Items 1 o Default Update Time 30 minutes o The only active item checks the host reachability and triggers an alarm if the host is not reachable Note If you need to monitor more than one remote RipEX station you need to clone existing items for the remote station watched values Configuration example of the second remote station Data Quality item e Go to the Template list window and click on the items of RipEX template e Find the item called Remote station 1 wv Average DQ value and click on it e Find the item called Remote station 1 wv Average DQ value and click on it e Change the Key parameter to have 2 in the brackets wvRemDqAvg 2 e Change the last digit of the SNMP OID to be 2 instead of 1 i e 1 3 6 1 4 1 33555 2 4 3 1 7 2 e Click on the Clone button e Click on the Save button Now every station using this template will monitor two remote stations for their DQ value e f you want to define that item for individual RipEX stations only
58. Temperature C RF Power W e VSWR Voltage Standing Wave Ratio 1 0 the best ratio 1 0 1 8 acceptable ratio gt 2 5 in dicates a serious problem in antenna or feeder e Ethernet RX TX Packets ratio Ratio between received and sent packets over Ethernet e COM1 2 RX TX Packets ratio Ratio between received and sent packets over COM ports e HW Alarm input e Hot Standby SNMP trap containing active station identity sent by the active station e Backup paths system Backup path state and Alternative path state changes e Unit ready the hardware alarm output or the SNMP trap indicates that the RipEX radio is ready to operate 2 3 Network Management System ZABBIX To access our SNMP values any Network Management System NMS can be used However we recommend using the ZABBIX open source monitoring system It can be downloaded at http www zab bix com download php Zabbix website provides the following short description Zabbix is the ultimate open source availability and performance monitoring solution Zabbix offers ad vanced monitoring alerting and visualization features today which are missing in other monitoring systems even some of the best commercial ones If you have chosen the Zabbix software please read the following pages where we offer a basic Starting Guide to RipEX and Zabbix co working The sections may in any case be helpful for some generally applicable hints and tips Note The
59. Untagged Untagged Data Data PC 1 PC 2 192 168 2 1 24 192 168 2 2 24 no gateway no gateway Fig 11 8 ARP proxy configuration diagram RipEX Configuration On both RipEX units we have almost everything already configured Just go to the Settings menu and click on the VLAN amp Subnets button Turn the feature on and check the ARP proxy option on both units Confirm and apply the changes VLAN amp Subnets VLAN amp Subnets Interface VLAN ID IP MASK Priority Unit Manag ARP proxy Note Active Modify ETHO 182 168 2 251 24 a Default interface Add Subnet Add WLAN Fig 11 9 Enabling the ARP proxy You do not need to change the routing rules Just remember that the ARP proxy feature works for all destination IP addresses in the RipEX routing table RipEX will not mimic ARP proxy replies to any other IP address RACOM s r o RipEX 95 ARP Proxy amp VLAN Add routing rules to enable ARP proxy on other IP addresses e g if wanting to use the ARP proxy for IP addresses 192 168 2 8 15 add the IP subnet 192 168 2 8 29 into the routing rules Computer Configuration Both computers have the same IP addresses as in the basic configuration example Just remove the default gateway e PC 1 IP address 192 168 2 1 Mask 255 255 255 0 e PC 2 IP address 192 168 2 2 Mask 255 255 255 0 You need to delete the routing rules we added previously just go the the Command prompt again and type in the following comma
60. W 17 mL 200W 18 gt mL 500mW 19 mL 1W 20 mL 2W RipEX SettingState 0 off 1 on 24 Items TCP Modbus COM protocol address translation mode Items HW alarm input contact state Items HW alarm input contact type Items Radio interface encryption method Items Radio interface RF power Items Ethernet interface broadcast and multicast status Ethernet interface shaping status Terminal server status TCP Modbus COM protocol broadcast accept Radio interface FEC TS 1 on off TS 2 on off RipEX RACOM s r o RipEX SettingState Items TS 3 on off TS 4 on off TS 5 on off RipEX tsEthProtType Items 0 gt tcp TS 1 Ethernet protocol type 1 udp TS 2 Ethernet protocol type TS 3 Ethernet protocol type TS 4 Ethernet protocol type TS 5 Ethernet protocol type SNMP RFC1213 ifType Items 1 other RFC1213 Interface 1 The type of interface physical link protocol 2 gt regular1822 RFC1213 Interface 2 The type of interface physical link protocol 3 hdh1822 4 ddn x25 5 gt r c877 x25 6 gt ethernet csmacd 7 gt is088023 csmacd 8 gt iso88024 tokenBus 9 gt iso88025 tokenRing 10 iso88026 man 11 2 starLan 12 proteon 10Mbit 13 gt proteon 80Mbit 14 hyperchannel 15 fddi 16 gt lapb 17 gt sdic 18 gt ds1 19 2 e1 20 gt basicIlSDN 21 gt primarylSDN 22 propPointToPointSerial 23 ppp 24 softwareLoopback 2
61. With its modification as well as with the new emerging specifications ETSI EN 302 561 2 ETSI EN 301 166 3 it is now possible for the up to date architectures of narrowband LMR devices to make the utilization of more efficient modes of system operation practically applicable The main objective of this paper is to describe the favorable properties of operational modes based on advanced nonlinear and linear digital modulation techniques in order to easy the decision on their usage and thus to help system integrators to increase the efficiency of the narrowband radio channel utilization allocated to the new generation of industrial LMR devices 3 1 Narrowband radio transmitter From the very advent of the radio transmission it was evident that a radio device should not only use its occupied channel bandwidth effectively but in addition should also avoid any unnecessary interfer ence with other systems Since then the frequency spectrum had been proving its importance and has become a scarce resource nowadays The narrowband radio devices under consideration are specified mostly by the European standard ETSI EN 300 113 1 Such radio equipments have to face challenging environmental and radio conditions all over the world The dynamic range in the vicinity of 100 dB very strict adjacent channel transmitted power attenuation requirements high data sensitivity adjacent channel selectivity high level of radio blocking or desensitization and h
62. X SNMP Trapper Template trpVswr str OFF 0 Enabled Fig 2 11 Definition of RipEX traps RipEX sends a trap whenever the watched value is out of range or other condition configured is met e g changes in Backup paths When the watched value returns to its configured interval RipEX sends a trap again to notify Zabbix or any other NMS All triggers stay active until this notification is received RSS and DQ trap items are disabled in the template by default The reason is that we need to define remote RipEX IP addresses first See the following example for enabling a DQ trap Go to the Zabbix web front end and select a RipEX host for which you want to process DQ traps Click on the Items button and find an item with the following key trpDqX Y Z W ZA B B X Help Get support Print Profile Logout Configuration Host groups Templates Maintenance Web Actions Screens Slide shows Maps Discovery IT services SNMP Builder P Search History Configuration of items Latest data Configuration of hosts Configuration of items Latest data CONFIGURATION OF ITEMS Items Displaying 1 to 2 of 2 found Filter Host list Host RipEX Mrazek Monitored E ERI ET 1 Applications 20 Items 326 Triggers 21 Graphs 5 Discovery rules 0 Wizard Name Triggers Key t Interval History Trends Type Applications Status Error a RipEX SNMP Trapper Template Remote station X Y Z W DO value out of range
63. X comProtocol 0 none 3 AsyncLink 4 Modbus 5 EC101 6 DNP3 7 gt UNI 8 gt Comli 9 gt DF1 10 Profibus 12 C24 13 RP570 14 Cactus 15 ITT Flygt 16 2 SLIP 16 Siemens 3964 R RipEX deviceMode 1 bridge 2 router RipEX eDhcp 0 off 1 server 2 client RipEX eSpeed 0 auto 1 2 s 100baseTX Full 2 gt s 100baseTX Half 3 gt s 10baseT Full 4 s 10baseT Half RACOM s r o RipEX SNMP Items Backup Paths 1 Alternative Paths Currently passive paths State Backup Paths 2 Alternative Paths Currently passive paths State Backup Paths 1 Alternative Paths Currently used path otate Backup Paths 2 Alternative Paths Currently used path otate Items COM Protocol COM2 Protocol TS 1 COM user protocol type TS 2 COM user protocol type TS 3 COM user protocol type TS 4 COM user protocol type TS 5 COM user protocol type Items Station working mode Items Ethernet interface DHCP mode Items Ethernet interface bit rate and duplex settings 23 SNMP RipEX ifTmATM 0 gt mask 1 table RipEX lOState 1 unknown 0 off 1 on RipEX RelayContactType 0 gt off 1 normally closed 2 gt normally open RipEX rEncryption 0 off 1 gt aes256 RipEX rRfPwr 0 gt mE 100mW 1 mEr 200mW 2 mE 500mW 3 gt mE 1W 4 mE 2W 5 gt mE 3W 6 gt mE 4W 7 mE 5W 8 mE 10W 9 mE 8
64. apter port belongs to pem messem Fig 11 12 Adding VLANs in Windows 7 On the example we added a VLAN 2 interface See the respective network card manuals for more details If you were successful in adding a new VLAN interface You should see this interface among other physical network interfaces Set the IP address mask and gateway as usual P address 192 168 2 1 e Subnet Mask 255 255 255 0 e Default Gateway 192 168 2 251 Now you just need to add routes to the 192 168 2 2 and 192 168 2 252 IP addresses Run the Command prompt and type e route add 192 168 2 252 mask 255 255 255 255 192 168 2 251 e route add 192 168 2 2 mask 255 255 255 255 192 168 2 251 Note You need Admin privileges to add a route in Windows 7 Test the Connectivity The test is exactly the same as described in prvious chapters You can run the Monitoring feature in RipEX to capture packets on the radio Ethernet interfaces and see Ethernet VLAN tags and other valuable information See the following example RACOM s r o RipEX 99 ARP Proxy amp VLAN 3 2 X Radio modem amp Router co 2 ACCCOAA Status Values from RipEX A Wizards Settings Monitoring Routing RADIO v COM1 COM2 ETH y Internal show params Diagnostic Show time diff File period 5 min File size 100 kB rum 0x0060 3233 3435 3637 Statistic 14 42 59 642847 ETH IP 19
65. arming features of collisions The first is a systematic repeated collision No application generates a totally random traffic pattern So it may happen and it does happen that a certain sequence of packets in a certain network layout generates a collision and it generates this collision repeatedly in fact always The result is that certain specific packets are never delivered regardless of number of retries set at the application level Imagine a SCADA system never capable of performing one specific task while all communication tests report that links are in perfect shape It would be very tempting to blame the SCADA while the true problem is a systematic collision i e wrong network design Ways to avoid such collisions are described further in this document The second dangerous feature of collisions is just a direct consequence of probability laws The most effective communication scheme for many applications is the report by exception mode which can vastly reduce the amount of mainly useless traffic generated by polling type systems Report by excep tion means though that collisions can never be ruled out completely hence a collision solving system must be an integral part of the protocol in the radio channel RipEX in router mode provides such protocol of course Solving a collision means retransmission typically a delayed retransmission Consequently the probability of another packet being generated by the application in the meantime in
66. at Unit ready signal has changed This notification sends additional information about the event by including the following objects in its varbinding list alarm StateUnitReady alarm input state 48 RipEX RACOM s r o Data speed and Modulations 3 Data speed and Modulations On efficient use of narrowband radio channel Introduction The industrial narrowband and mobile radio LMR devices as considered in this paper have been the subject to European standard ETSI EN 300 113 1 The system operates on frequencies between 30 MHz and 1 GHz with channel separations of up to 25 kHz and is intended for private fixed or mobile radio packet switching networks Data telemetry SCADA maritime and police radio services traffic monitoring gas water and electricity producing factories are the typical system applications Long distance coverage high power efficiency and efficient channel access techniques in half duplex operation are the primary advantages the system relays on Very low level of adjacent channel power emissions and robust radio receiver architectures with high dynamic range enable for a system s co existence with various communication standards without the additional guard band frequency intervals On the other hand the strict limitations of the referenced standard as well as the state of the technology has hindered the increase in spectrum efficiency with which the system has used its occupied bandwidth
67. ate you have all OID objects already transformed into the Zabbix items Note RipEX supports several OID objects from the RS232 MIB and the RFC1213 MIB tables These are contained in the http www racom eu download hw ripex free eng 3_ fw RACOM RipEX MIB zip file 2 6 RipEX MIB Table 2 6 1 RipEX OD Name ws Stato Descinon 33555 2 2 2 4 eBCastMCast read only current Ethernet interface broadcast and multic ast state 33555 2 2 2 5 Ethernet interface bit rate and duplex settings 33555 2 2 3 1 ifTmEnable TCP Modbus state 38 RipEX RACOM s r o SNMP 33555 2 2 3 3 TCP Modbus socket timeout in seconds 33555 2 2 3 4 ifTmBCast a wid TCP Modbus COM protocol broadcast accept 33555 2 2 3 5 ifTmATM read only current TCP Modbus COM protocol address translation mode 33555 2 2 4 1 iffsEnable Terminal server state 33555 2 2 4 2 Number of Terminal server interfaces 33555 2 2 4 3 ifTsTable not access current List of Terminal server interface entries ible 33555 2 2 4 3 1 ifTSEntry Terminal server interface entry ible 33555 2 2 4 3 1 1 X Unique index for each interface 33555 2 2 4 3 1 2 X tsEnable read only current Terminal server interface state 33555 2 2 4 3 1 3 X tsEthProtType Terminal server Ethernet protocol type 33555 2 2 4 3 1 4 X tsEthProtTimeout read only current Terminal server Ethernet protocol socket timeout in seconds 33555 2 2 4 3 1 5 X tsEthProtMyPort read only current
68. ation begins on port 502 from where it is redirected to other RipEX ports corresponding to the individual RTU s based on negotiation with the Modbus TCP Master To set up RipEX connected to Modbus TCP Master RACOM s r o RipEX 73 Modbus TCP RTU e Set Modbus TCP RTU to On Type the port number on which the connected Modbus TCP Master initiates communication by default 502 into My TCP Port field e Select how you want to translate Modbus addresses to RipEX IP addresses using mask or table Set the UDP interface to Terminal server TS1 TS5 Set the same TS for remote RipEX s too Note The maximum number of concurrent TCP IP connections between a Modbus TCP device and RipEX is set to 10 due to limited computing capacity Note The number of concurrently open TCP IP connections can be increased using CLI if necessary Modbus TCP Master must be set to not open more than 10 TCP IP connections at any given time To set up RipEX connected to Modbus TCP Slave e Modbus TCP RTU Off e Terminal Servers On e Setthe Terminal Server see RipEX Master settings to TCP and set My Port to 502 Use the address of the connected Modbus Slave as the destination IP and fill in the destination port number which the connected Modbus Slave device scans for incoming communication e Set Protocol to UNI and Mode of Connected device to Slave 8 4 Master Modbus TCP slaves Modbus RTU Note Only works in Router mode Ma
69. cation or multiple master polling type one loads the network collisions can not be avoided completely despite the sophisticated channel access method used Then a collision solving algorithm becomes equally important The standard protocol feature of sending an Acknowledgement ACK to every data packet and retrans mitting it when no ACK comes takes care of all possible reasons for packet non delivery collisions in cluded However retransmitting a packet increases the network load and so increases the collision probability Moreover it is possible to create a systematic collision by e g a regular retransmissions after the initial random collision Thus the calculation of the retransmission time out requires a sophist icated approach again RipEX uses its settings packet parameters sequence number of the retrans mission and the necessary random element to calculate the time out Retransmission feature is enabled by selecting On in the ACK listbox By deciding on number of Retries you define the very important compromise between the longest possible delivery time and the probab lity of a packet being lost Note that this setting does not normally affect the typical most probable delivery time in the network since a typical packet is delivered without retransmissions Most applications require their data to be delivered completely and error free hence there are message retransmissions at the application level Note that the RF protocol
70. ce Of course a similar scenario can be used right from the moment of planning a new network The invest ment cost can be reduced by purposefully configuring the few difficult radio links to a lower data rate The above scenarios are made possible by the unique capability of RipEX to automatically adjust its receiver to the data rate of the incoming frame Note that when an ACK frame is sent by the receiving RipEX it always uses the same data rate as the frame it acknowledges The only limitation of this feature is that all the frames have to have the same symbol rate and the same principle of modulation i e CPFSK or linear Modulation types which can be combined within one approval type FCC or CE 2CPFSK amp 4CPFSK with or without FEC Or D2PSK amp Pi ADQPSK amp D8PSK amp 16DEQAM with or without FEC The improvement in system gain value using this technique may be more than 15 dB Increasing gain of antenna system by that value would be impractical often impossible the difficult hops are designed to use high gain directional antennas from the beginning Hence the Autospeed may make a radio modem network the optimum choice in situations where it could not be economically feasible before Pi 16DEQAM i 16DEQAM ae F amp A a Mod 16DEQAM y ej am 4 e Fig 4 3 Autospeed solution je s d TJ4DQPSK 16DEQAM RACOM s r o RipEX 59 Back to Back repeater 5 Back to Back repea
71. cket acknowledgement on the radio channel you can shorten the repetition timeout if ACK is turned off Set up using CLI cli cnf set device mode ack n Turns on ACK retries 2 Number of retries 2 rto prog f Turns off progressive retries rto fix 10 Shortens the retry timeout to the minimum value of 10 Bytes rto var 10 Shortens the variable retry timeout to the minimum value of 10 Bytes Slots rx 0 Will receive immediately after request random channel access is not used slots tx 0 Will transmit immediately after request random channel access is not used Same settings should be used for all devices To find out more about CLI see RipEX manual chapter CLI Configuration Set the following in Profibus parameters Tslot_Init 16383 Note This setting is only appropriate for certain types of networks changes should only be made by experienced users Connecting RS 485 Connector layout of RipEX COM 2 for RS 485 and the corresponding PIN s on Siemens Simatic S7 SIEMENS RIPEX Fig 7 3 RS485 connection j http www racom eu eng products m ripex cli conf html 70 RipEX RACOM s r o Modbus TCP RTU 8 Modbus TCP RTU Use of Modbus in RipEX RipEX supports Modbus RTU Modbus TCP as well as their combinations Tab 8 1 Centre Remotes Radio network behaviour Available with protocol protocol Operating mode NL MEE ANM 00 NEN Modbus RTU overRadiochannel RTU over Radio channel Bridge Router Rout
72. creases by the delay and it increases at both parties involved in the collision That results in an increased probability of next collision to happen and so on This principle makes report by exception networks very sensitive to bursty loads Whenever the load increases over certain limit we may say normal network capacity number of collisions grows exponentially reducing the instant network capacity well below normal situation Series of lost packets and very long delivery times are the result from the application point of view While the network for report by exception application has to be designed to provide maximum capacity possible it is recommended to take measures to avoid burst load generation at the application level Limiting the possible load generated by a single device can help to avoid the whole network col lapse just because one remote unit goes suddenly crazy e g generates hundreds of exceptions per second RACOM s r o RipEX 81 Channel access 10 2 Bridge mode In Bridge mode a packet is transmitted to the radio channel immediately without any checking whether the radio channel is occupied or not If other radio was transmitting simultaneously a collision would occur and both packets would be lost Consequently Bridge mode can be used only for applications which never generate more than a single message at a time e g master slave polling applications Still appropriate measures have to be tak
73. dd Graphs 192 168 16 0 24 255 255 255 0 10 10 10 16 Off RipEX B V Delete Add Ping Add Monitoring Backup Alternative paths Maintenance Hame Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Backup 1 192 168 15 1 20 Delete Add 10 10 10 16 Default vi Indirect link T Add 10 10 10 15 Default v Direct link Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 12 RipEX C Routing menu example 2 In RipEX C we have a very similar configuration to RipEX A just in the opposite direction 112 RipEX RACOM s r o Backup routes Practical Test In this example we will use a different method to switch between the primary and backup paths We have set the highest priority for the indirect link our backup path in the previous example Whenever RipEX B is switched off the Backup routes system will use the direct path instead The RipEX failure detection time is based on the Policy settings Note If you set the Hello packet period to a low value e g 10 seconds and Hello packet success rate to 100 the procedure will be very fast But with these settings you are wasting the radio bandwidth with quite a lot of traffic and whenever a single Hello packet is lost the active path is labeled as Down In the example we will not alter the default values Alternative path Parameters Default Hello packet period sec Hello packet success rate 20 87 5 RSS dBm Off Lowe
74. di Pub RO PA ETIN UNE E 49 3 2 Narrowband radio TECCIVER 5 exc d ase Ph Sup Fra PECIS NEM a En VE seca NOR rV VENUE o3 OEC Grelpie DETo PR NT T DOT UTE 56 A AUTOS PECO MONTE EE m 58 sMisiz e conse dictu e Eres 60 9 1 Back to Back in Bridge Mode 5 eut Eu eot leet a ute eE eden oee c La ON URS 60 5 2 BACK O BACK In ROUter TOO seno pisi a dicm Reto lc bor bib sor Ei 60 6 Combining MORSE and RipEX networks eesssssssessssssssesesseeeeen nennen nnns nna nnns 62 Oo LSIDEX part in BridgedodO uu mss sr oos a o deb eub esa tbv ddtueol Ta uet pte dime tc two S Ga Ne 62 6 2 RIDE In ROULET MOUE uas sudes err EUR DIR EVFE RUN CU demi etai a a is Pro kv rap v eC pala t dus 63 TAE PONDUS m Dp MP 65 1 1 Bridge and Router MOO CS aos ortae oen adea E RE e Rak sta des onu F oue Cauda a adu 65 TAS ON die ob eect UNOS aa DR PD EE TRES 66 ESA RIDE AS CTU OS 9 eie eroe teme tor dug ad MV uo sepe adds p M MEM dU EU 68 1 uvae O acy lt 1 0G 6 ogee ieee a a dcc i ades ut a equ 69 9 Modbus TOP IS TU ss ceeetecteus da ac tns e cua Mie vado tuu ua out ca cube tein Dos Deed aaa idan tede 71 S Mi WOOL REO scettr tod seen e a MIS EMI MM ILI D M wana edited ata I eM DEDE ELSE 71 9 2 MOGDUS TOP osiuavi ccn oem ici ob EO eU od dtp vox a dead a neva alam Ka E SUA E EU dens 72 8 3 Modbus TCP local TCP IP connection uoc ooi buec oit de epo Debe Eo BU Dad e dun oq Ep Eon MEER ev Ped Eder T3 8 4 Master Modbus TCP slaves Modbus RTU
75. e ARP proxy functionality local RipEX can mimic any IP address and reply to ARP requests In our case the RTU Master would consider the RipEX MAC address as the Slave MAC address And with the appropriate routing rules in RipEX units we can achieve the needed interconnectivity We do not need to set anything on the connected RTUs no gateway no routing rules Important AN Be very careful when using this feature ARP proxy can disable all the traffic on the LAN Note Q e You can combine the ARP proxy feature with a TCP proxy and Terminal Servers See the respective help in the RipEX web interface for details e RipEX does not transmit broadcast packets via the radio link with the ARP proxy feature 11 3 Transparent VLAN The VLAN tag 802 1Q protocol is a 4B field in the Ethernet frame It is inserted between the MAC address and EtherType Length fields of the original frame The VLAN packet is defined by two main parameters VLAN tag VLAN Identifier VID is also called VLAN number It is 12 bits long so we can have up to 4096 VLANs 0x0000 and OxFFF values are reserved Priority Code Point PCP a 3bit field which refers to the IEEE 802 1p priority It indicates the frame priority level Possible values are from O best effort to 7 highest priority 1 represents the lowest priority These values can be used to prioritize different traffic classes voice data See the following example RACOM s r
76. e eee ee mee en eee ene eee er eer eer ree 104 RACOM s r o RipEX 3 RipEX AZ 1 onigoro iP euo pens PE 104 12 2 Backup Routing Management Protocol cece cece cece cece eeece seca eeseeeseeeeeeeeeeeseeeeeeeseeess 104 12 3 GConidgutralion Exarmples uoi oc eoe Ec E DUE Ure aces demir ad Sau ves ctis a e Dub tum dae 105 12 4 CENA to Cete E ETE idee tuum uode tisse do metr Voca TA TAE en ated Mua EMT M dE 117 As REVISION MISION ARC ereaiatele 118 4 RipEX RACOM s r o Address planning 1 Address planning In Router mode standard IP routing is used between individual RipEX radio modems and their interfaces The only non standard feature is that even if you assign all RipEX s radio interface IP addresses to a single network the RipEX s may not hear each other over the radio channel therefore routing tables should include even routes within the same network over repeaters This Application Note draws attention to certain situations in which routing tables can be simplified significantly 1 1 End devices connected via serial interface Every RipEX radio modem has two network interfaces and hence two IP addresses First is the Ethernet interface second the radio interface Serial interfaces are defined by their UDP port and are shared for the entire RipEX modem as a result both RipEX IP addresses can be used to access them both IP addresses work equally well The destination IP addres
77. e routing table in the IP device connected to RipEX In this case destination addresses must not be on the same network i e the destination address must always be outside of the network mask A destination address is the IP address of one of the devices connected to RipEX s which mutually communicate over the radio channel C Ifthe connected device allows neither network mask nor gateway to be set up Router mode cannot be used at all use Bridge mode instead 1 3 Ethernet addressing If you can set up IP addresses of the end devices connected over Ethernet you can simplify routing by hierarchic division into subnets either complete or for routing purposes only An example of such network layout follows The centre and main repeater form distinct networks with mask 255 255 255 0 24 the sub networks narrow down towards the end devices 255 255 255 192 26 and then 255 255 255 248 29 Routing tables are only given for a single branch of the network for clarity They will be similar for other RipEX s Only Master Slave type applications are presumed without any direct communication between Slave devices RACOM s r o RipEX 9 Address planning T T 192 168 1 0 26 via 10 10 1 5 192 168 255 0 24 via 10 10 1 1 192 168 2 0 24 via 10 10 1 1 192 168 3 0 24 via 10 10 1 1 wu l 10 10 1 2 24 192 168 1 254 24 192 168 1 253 24 Ill S gw 192 168 1 254 l 10 10 1 3 24 192 168 2 254 2
78. en to avoid collisions in special situations 10 2 1 Bridge mode with Repeaters Repeaters can be used in the Bridge mode in order to extend the radio coverage Considering the re peated packets it is necessary to schedule the access to the radio channel to avoid systematic collisions In a polling type network there is a request packet from centre to remote to which the remote responds immediately When a remote receives the request directly from the centre its immediate response would collide with the repeated request so it would be never received by the centre a perfect example of a systematic collision Packet header contains information about the number of Repeaters on the route i e how many times the packet can be possibly repeated This number is decremented when passing through each Repeater The remote radio modem which receives the packet must delay its own transmission for a period This delay is calculated from the number of the remaining repetitions the packet length and the modulation rate in the radio channel Repeaters always transmit immediately without any delay Example There are 4 radios in the network operated in the Bridge mode Everyone can receive each other except Radio 4 which is not able to receive Radio 1 and vice versa Therefore in the Radio 3 the Repeater function is turned on and it mediates the connection between 1 and 4 0 4 P 3 REP 82 RipEX RACOM s r o Channel acces
79. ens Slide shows Maps Discovery IT services SNMP Builder History Latest data Configuration of triggers Latest data Configuration of triggers Latest data CONFIGURATION OF TRIGGERS Search Group RipEX Host RipEX Office Triggers Displaying 1 to 22 of 22 found Hide disabled triggers Host list Host RipEX Office Monitored ERI E Applications 20 Items 327 Graphs 5 Discovery rules 0 3 Expression io 192 168 131 55 DO value out of range 192 168 131 231 trpDdj92 168 131 55 E amp tr OFF 3 0 Enabled L T T EX SNMP Trapper Template RipEX station VSWR value out of range 192 168 131 231 trpVswr str OFF 0 Enabled Trapper Template RipEX station UCC value out of ra 1192 168 131 231 trpUcc str OFF 0 Enabled Fig 2 14 Enabled DQ trap trigger Follow the same procedure DQ and RSS for other remote RipEX units as needed You can define Zabbix to send you an e mail whenever any trap is triggered See the Zabbix Document ation for e mail configuration Now we just link the snmptrapd to use our script Please find the file snmptrapd conf usually it s in the etc snmp directory Edit or create the file as root with the following lines authCommunity execute public authCommunity execute PUBLIC traphandle default bin bash home zabbix bin snmptrap sh The first two lines will allow all received traps with
80. ent standards organizations while lower level OIDs are allocated by associated organizations e g RACOM OID example RIPEX serialNumber serialNumber OBJECT TYPE e EROM Rule HX SYNTAX Unsigned32 MAX ACCESS read only STATUS current DESCRIPTION Product serial number 7 1so 1 org 3 dod 6 internet 1 private 4 enterprises 1 racom 33555 ripex 2 kb station 1 device 1 4 As you can see numbers 1 3 6 1 4 1 33555 are the higher level OIDs The lower level OIDs are 2 1 1 4 which are allocated by RACOM 2 2 SNMP in RipEX In RipEX SNMP protocol can be used to e Read configuration parameters from MIB Read operation statistics on the radio channel and e Sends traps when set thresholds for monitored values are exceeded TxLost vo UCC Temp PWR RACOM s r o RipEX 13 SNMP For detailed description of individual values refer to section RipEX MIB bellow RipEX utilises SNMP versions SNMPv1 and SNMPv2c it uses community string for authentication which is by default public but can be changed SNMP uses UDP protocol for communication delivery checks are implemented from version 2 Note The RipEX MIB module complies with a validity check for severity level 3 By default RipEX uses UDP port 161 SNMP for queries Manager which sends the query dynamically chooses a port from which it sends its query to RipEX port 161 RipEX replies from port 161 to the dy namically
81. er Multiple Mas RTU Modbus RTU over Radio channel m ters RTU 2 TCP TCP TCP IP protocol over Radio channel Bridge Router 3 TCP TCP TCP IP protocol locally between Modbus device Router and RipEX TCP IP overhead is not transferred over Radio channel TCP Conversion of Modbus TCP to Modbus RTU on Router the remote units Combination Using 3 and 4 Router of TCP and Router slaves RTU Master only communicates with RTU RTU masters RTU slaves utilising 1 1 and 5 8 1 Modbus RTU A standard simple network design with a single Master and several Slaves running Modbus RTU rouse 0S Modbus RTU ME AAE l Modbus RTU 000s wm rows su S Pare Modbus RTU ti S Modbus RTU RS232 Modbus RTU Fig 8 1 Modbus RTU In Bridge mode set the type of communication interface RS232 or RS485 for the COM port as well as the parameters of the serial interface both for the Master and Slave RACOM s r o RipEX 71 Modbus TCP RTU In Router mode set the COM port of your Master RipEX to Modbus Mode of Connected device To translate Modbus addresses to RipEX format and vice versa either use a mask if RipEX addresses mirror the Modbus ones or table A table must be used if there are several Modbus slaves behind a single RipEX RS485 or both COM1 and COM2 For more information refer to on line help or chapter Protocols Common parameters of the manual In addition set Modbus to Slave on all remote units If you intend
82. er 62 12 dB Spacing 25 kHz Upper 61 20 dB Spacing 25 kHz Upper l GB Fig 3 1 Modulated signal spectrums left 2CPFSK with R 10 4 kBaud modulation index h 0 6 right 2CPFSK with R 17 3 kBaud modulation index h 0 2 30 dB attenuator used in series 50 RipEX RACOM s r o Data speed and Modulations In the systems where the transmitter power efficiency is of high importance the transmitter nonlinearity also creates an important issue Generally speaking the higher the transmitter nonlinearity the higher the transmitter efficiency can be reached Unfortunately the device with a nonlinear transfer function also tends to distort the spectrum of the transmitted signal especially if the modulated signal exhibits the non constant modulation envelope In contrast it is also true that only the non constant envelope modulation can withstand a strict band limitation by means of modulation filtering characterized by the roll off parameter a in the following text In other words if the signal has a constant modulation envelope it has an unlimited spectrum and if it has a band limited spectrum it experiences the amp litude variations which after passing through the nonlinear power amplifier would be suppressed but would also regenerate the side lobes of the modulated signal spectrum The phenomenon is known as the spectral re growth and it depends mainly on the three transmitter characteristics Those are peak to average power rati
83. er of repeaters solves the collision between a repeated packet and a possible response When more than one repeater is used in a Bridge mode network collisions between repeated packets from different repeaters may occur These cannot be solved by simple delays rather a sophisticated anti collision protocol is required The RipEX Router mode is recommended to be used in more complex networks with multiple repeaters Nevertheless if certain conditions on signal coverage sometimes non coverage among repeaters centre and remotes are met the Bridge mode for a polling type application can be used See the chapter Bridge mode in RipEX Manual i http www racom eu eng products m ripex ripex detail html RACOM s r o RipEX 83 Channel access 10 2 2 Time division of responses in Bridge mode There is also the Tx delay setting in the menu It shall be used in Bridge mode if multiple RTUs connected to slave stations reply to a broadcast query from the centre It is necessary to spread out their replies to the radio channel in terms of time otherwise a massive collision occurs It can be achieved by setting the TX delay parameter to an adequate sequence of TX delays e g 0 100 200 ms as in the example below in individual remote RipEXes The slave RipEXes will enter the radio channel successively and no collisions will occur Note The TX delay applies to every packet that is sent out to the radio channel Example The Centre broadcasts
84. esses reserved for network and broadcast ing though we do not recommend doing so 10 RipEX RACOM s r o T 192 168 255 0 24 via 10 10 1 5 T 192 168 1 0 29 via 10 10 1 9 192 168 1 8 29 via 10 10 1 10 192 168 255 0 24 via 10 10 1 T 192 168 1 0 26 via 10 10 1 5 192 168 255 0 24 via 10 10 1 1 192 168 2 0 24 via 10 10 1 1 192 168 3 0 24 via 10 10 1 1 192 168 1 62 29 10 10 1 2 24 192 168 1 254 26 Eth 192 168 1 61 29 IIl S gw 192 168 1 62 192 168 1 253 26 gr II S gw 192 168 1 254 10 10 1 6 24 192 168 2 62 29 Eth 192 168 2 61 29 00 S gw 192 168 2 62 10 10 1 3 24 192 168 2 254 26 10 10 1 7 24 192 168 2 126 29 am Eth 10 10 1 1 24 192 168 255 2 24 192 168 2 253 26 Il S gw 192 168 2 254 Eth Eth 192 169 2 125 29 gw 192 168 2 126 192 168 255 1 24 gw 192 168 255 2 10 10 1 4 24 192 168 3 254 26 10 10 1 8 24 Eth 192 168 3 62 29 192 168 3 253 26 II S gw 192 168 3 254 Eth 192 168 3 61 29 I S Jow 192 168 3 62 Eth Fig 1 4 Network with narrowed masks RACOM s r o RipEX Eth 10 10 1 5 24 Eth Address planning 10 10 1 9 24 192 168 1 6 29 192 168 1 5 29 gw 192 168 1 6 10 10 1 10 24 192 168 1 14 29 Eth 192 168 1 13 29 I S qw 192 168 1 14 10 10 1 11 24 192 168 2 70 29 py ms 10 10 1 12 24 192 168 2 78 29 192 168 2 69 29 gw 1
85. ete Ada Add Monitoring E Backup paths f Maintenance P P Alternative paths Mame Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Add Legend Good Failure Unknown Currently used Route for IP Fig 11 16 RipEX B Routing table Computer Configuration We do not need to change anything on PC 1 PC 2 needs the following changes e IP address 192 168 4 2 mask 255 255 255 0 gateway 192 168 4 252 Now we need to add the VLAN interface with an ID 2 See the procedure in the previous example When you have added the VLAN interface add the following routing rules e route add 192 168 2 251 mask 255 255 255 255 192 168 2 252 e route add 192 168 2 1 mask 255 255 255 255 192 168 2 252 Note You need the admin privileges to add a route in Windows 7 Test the Connectivity Follow the steps described in any of previous chapters called Test the Connectivity You should be able to ping any VLAN or Ethernet IP address from any unit Management VLAN Now you should be experienced enough for the next test Set another VLAN ID on both computers Use the same VLAN ID on ETH O interface for the RipEX management You will have a VLAN only network See one of the possible examples 102 RipEX RACOM s r o ARP Proxy amp VLAN Radio link Router mode Radio IP ha gr Radio IP 10 10 10 2 24 Untagged Data 10 10 10 4 24 RipEX A RipEX B ETH IP VLAN ETH IP VLAN 192 168 3 251 24 192 168 4 251 24
86. following guide was tested with Zabbix release 2 2 0 It should work on any 2 0 x release or any newer 2 2 x release If you use any of the 1 8 x releases some tasks may need a different approach Take the opportunity to remotely access and test a live Zabbix demo Contact us for access details 2 3 1 Installation and Documentation Due to security requirements and mission critical nature of monitoring server UNIX is the only operating system that can consistently deliver the necessary performance fault tolerance and resilience Zabbix is tested on the following platforms e Linux IBM AIX FreeBSD NetBSD http www racom eu eng products m ripex demo zabbix html http www racom eu eng products remote access html load product zabbix 16 RipEX RACOM s r o SNMP OpenBSD e HP UX e MacOSX e Solaris e Windows 2000 Server 2003 XP Vista Server 2008 7 Zabbix agent only For further details visit Zabbix Documentation at http www zabbix com documentation php It contains a large body of information about installation steps configuration performance etc If you are unsure how to proceed with any task refer to the Zabbix documentation first You can find an installation guide there too This Guide does not present all Zabbix settings but should help you incorporate the RipEX SNMP functionality into the Zabbix software Note The following guide requires using MySQL database used in Zabbix If
87. ght Graph type Sj ripex Dane Function Draw style Y axis side 8 Gi deve LL stationName iL deviceType fL deviceCode eL serialNumber Fig 2 19 SNMP Builder overview Note The step three patch can end with an error message in such a case edit the j sLoad er php file manually Follow the instructions in the jsLoader php rej file probably adding lines with a plus sign on the beginning How to Work with the SNMP Builder and the RipEX MIB To be able to see the RipEX MIB table you need to import it to the Zabbix server default MIB directory usually usr share snmp mibs The directory is shown at the SNMP Builder front end in the second menu MIB Front end settings e Template choose the RipEX template e MIB choose the RipEX MIB If you cannot see any MIB you probably have a wrong path to the MIB directory change variables mibs dir and MIBS ALL PATH accordingly in the zab bix frontend snmp builder php file e Host Fill in the RipEX IP address e SNMP Version 2c e Community public RACOM s r o RipEX 37 SNMP On the left side of the Zabbix front end you can see the OID Tree You can navigate in there as you wish If you click on any OID object it should print a returned value on the right By selecting these values you can easily create various items with basic settings Not all options are implemented in the SNMP Builder If you have imported the RipEX templ
88. hanged e rpUnitReady Unit ready signal has changed If you want to clear the trap alarm just repeat the same zabbix sender command but change the message to contain the word OFF E g ALARM OFF 34 RipEX RACOM s r o SNMP System status Host group Disaster High Average Warning Information Rine 00 885 000 Zabbix sewers 0 0 o 00 Updated 16 35 33 Host status Host group Without problems Total a Updated 16 35 33 Last 20 issues Host Issue Last change 4 Age Info Ack Actions RipEX TP 26 Sep 2012 16 33 52 1m 41s No 1 of 1 issue is shown Fig 2 15 Zabbix dashboard Status of units You can also see Trap s output in Monitoring Latest Data TRAPS of your RipEX station History The displayed information differs based on the trap received See the detailed description in the respective Zabbix item 2 5 What Else does Zabbix Offer There are many features provided by the Zabbix software They are described in the Zabbix Document ation Below are just a few of them You can create Screens A Screen is a set of various graphs on one page for better overview of your network temperature UCC RF power You can create Maps If you administer many stations in many locations a Map can be a good choice You can define the background picture e g real maps various station pictures station status various statistics etc You can import any icon or background pict
89. has decreased to 14 and 10 Despite this negative trend the achieved values of output power exceeding 3 W and 2 W respectively are considered practically applicable for next generation of narrowband LMR devices and as it will be shown in the next section they enable the system to use its occupied bandwidth with even higher communic ation efficiency 3 2 Narrowband radio receiver The most important parameters which describe the quality of narrowband radio receiver are maximum usable data sensitivity co channel rejection adjacent channel selectivity desensitization and inter modulation response rejection Besides the maximum usable sensitivity all other receiver parameters can be classified as the measures of the receiver degradation parameters used to analyze the degrad ation of its performance due to the presence of unwanted interfering signals Although there is a strong relation between all of these parameters in this paper the attention is given only to the first of them to the maximum usable sensitivity in particular According to 1 the maximum usable data sensitivity is the minimum level of the signal emf at the receiver input produced by a carrier at the nominal frequency of the receiver modulated with a normal test signal which will without interference produce after demodulation a data signal with a specified bit error ratio BER of 10 ora specified successful message ratio SMR of 80 The maximum usable sens
90. ia 192 168 2 251 gateway RipEX VLAN interface Windows 7 There is no tool like vconfig in Windows 7 The VLAN features depend on the network adapter and driver installed Please see the respective download sites of your network card to obtain the correct VLAN enabled driver Note There is also the possibility that your network card will not support VLANs at all To see what network card and driver you have go to START Control Panel System and Security Device manager Network Adapters menu Here you should see your network card Right click on it and select the Properties option 98 RipEX RACOM s r o ARP Proxy amp VLAN Marvell Yukon 88E8040 PCI E Fast Ethernet Controller vlastnosti x I 4M Situs 4 Virtual Cable Tester Oviadab Rizeni udi AN eam Existing VLANs VLAN 2 Marvell Yukon 88E8040 PCI E Fast Ethemet Controller mermawe Remove All A Virtual LAN VLAN is a logical group of network devices that are able to communicate as if they were part ofthe same LAN regardless of their physical network structure VLANs provide benefits such as increased flexibility scalability and security The Existing VLANs list displays all VLANs this network ad
91. icate that device in Hot Standby mode has been activated This notification sends additional inform ation about the event by including the following objects in its varbinding list serialNumber Product serial number stationName Station name RACOM s r o RipEX 47 SNMP 33555 2 10 15 troBpath current A notification to indicate a change in Backup paths system backup path state has changed This notification sends additional information about the event by including the following objects in its varbinding list bpathsPeerlp Backup path peer IP address bpaths Name Backup path symbolic name bpathsAltUsedPrio Currently used al ternative path priority number bpath sAltUsedGw Currently used alternative path gateway IP address bpath sAltUsedState Currently used alternat ive path state 33555 2 10 16 troBpathAlt current A notification to indicate a change in Backup paths system alternative path state has changed This notification sends additional information about the event by including the following objects in its varbinding list bpathsPeerlp Backup path peer IP address bpaths Name Backup path symbolic name bpathsAltUsedPrio Currently used al ternative path priority number bpath sAltUsedGw Currently used alternative path gateway IP address bpath sAltUsedState Currently used alternat ive path state 33555 2 10 17 troUnitReady current A notification to indicate th
92. igh co channel rejection 1 are its most important radio characteristics to mention It is no wonder that for such high dynamic range demands super heterodyne transceiver architectures with a majority of analog components are still widely used But yet the radio transceiver has to be small in dimensions consumes low power and maintains all its parameters over the wide industrial temperature range and over extensive period of time for reasonable price At the same time it should provide enough flexibility to accommodate different channel bandwidths digital modulation formats data rates and techniques to combat negative effects of radio channel From this point of view the software defined radio SDR concept is indisputably a prospective alternative and has not been widely used by these systems The rapid expansion of the digital signal processing together with the advancements in signal analog to digital converters technology have in recent years made such projects economically feasible Today s LMR systems being subject to 1 use mostly exponential constant envelope modulations GMSK 2 CPFSK and 4 CPFSK The application of the continuous phase modulations is mainly due RACOM s r o RipEX 49 Data speed and Modulations to the extreme adjacent channel transmitted power ACP attenuation requirements and inherent ro bustness against channel nonlinearities Relatively simple implementation of non coherent demodulators and synchr
93. iled description 11 2 Transparent LAN ARP Proxy Even though RipEX works as a standard IP router RipEX can interconnect equal IP subnets behind different RipEX units without defining default gateways It can be done with the ARP proxy feature Note Q See the RipEX manual Chapter 2 3 Router mode for configuration examples without ARP proxy usage RipEX can reply to any ARP request to mimic it has this particular IP address RipEX can reply to more ARP requests This feature is typically used when RTU s IP addresses behind different RipEX units are within the same IP subnet and the RTUs do not provide routing capabilities Radio link Router mode Radio IP ha fi Radio IP 10 10 10 2 10 10 10 4 ETH IP ETH IP 192 168 1 251 24 192 168 1 252 24 l RTU l RTU RTU Master RTU Slave IP 19 168 1 1 24 IP 19 168 1 2 24 no gateway no gateway Fig 11 1 Basic ARP proxy usage In this diagram RTUs do not have routing capabilities i e RTU expects its counterpart is within the same physical Ethernet LAN If the RTU Master starts to communicate with RTU Slave it requests the RTU Slave s MAC address The RTU Slave is a member of the same physical LAN so the RTU Slave does not reply However when RipEX radio IP 10 10 10 2 has ARP proxy enabled it replies to this ARP request i http www racom eu eng products m ripex ripex detail html router_mode 88 RipEX RACOM s r o ARP Proxy amp VLAN So with th
94. in settings as shown below click Recalculate and confirm by clicking OK Confirm the values in all open windows and click the icon Download to Module Tslot_Init is a value which fundamentally influences operation of the entire device 16 383 t_bit is the maximum value which helps test radio transmission We recommend setting as described in chapter Advanced Settings Calculation of minimum slot time PROFIBUS DP Fed PROFIBUS_DP x Bus Parameters Bus Parameters pa Talot_Init Talot 16383 t bit Talot_Init 16383 t bit T alat 15383 t hit Max T adr Tidz FO t bit Max T adr A 4 t bit Tide Fl t bit Min T adr Try 11 t bit Min T adr 11 EX t bit Trdy 11 t bit T set Tid 3f t hit T set 1 t hit Tidi a7 t bit Tgui Ttr 669186 t bit Tgui 0 4 t bit Ttr BB3185 t bit 34853 4 ms 34853 4 ms Gap Factor Thr typically bba8 t bit Gap Factor 10 4 Ttr typically ESADE t bit 3479 6 ms 3479 6 ms Retry lirnit Retry limit 1524 Watchdog watchdog 1759054 t bit 1759054 t bit 91617 4 ms 91617 4 ms Recalculate Recalculate 7 3 RipEX settings 7 3 1 Operating mode See chapter Advanced configuration of the manual If there is no more than a single repeater on your network we recommend using Bridge mode Profibus DP is always a master slave type network in which there is no danger of radio channel collisions http www racom eu eng products m ripex h menu html 68 RipEX
95. interface IP addresses can be used no subnet IP addresses on RipEX Ethernet or IP of connected device behind RipEX RACOM s r o RipEX 111 Backup routes a 3 i 2 X Radio modem amp Router 3 T 2 NCCCOAA Aa Status Values from RipEX B Se 10 10 10 16 Wizards Settings Interfaces i Routing Radio MAC 00 02 A9 BA 54 2B IP 10 10 10 16 Mask 255 255 255 0 ETH MAC 00 02 A9 BA 50 43 IP 192 168 16 1 Mask 255 255 255 0 Diagnostic Neighbours Routes f EEP Destination Mask Gateway Backup Note Active Modify TE 192 168 15 0 24 255 255 255 0 10 10 10 15 Off RipEX A v Y Delete Add Graphs 192 168 17 0 24 255 255 255 0 10 10 10 17 Off RipEX C Delete Add Ping Add Monitoring Backup j Alternative paths Maintenance Name Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Add Legend Up Down Unknown Currently used Route for IP Fig 12 11 RipEX B Routing menu example 2 We also added paths in RipEX B for the Ethernet networks located behind other RipEX units Ripex Radio modem amp Router Co RANCO M P Status Values from RipEX C SETUP d 10 10 10 17 Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BACT3 6B IP 10 10 10 17 Mask 255 255 255 0 I 1 ETH MAC 00 02 AS BACGF 83 IP 1827 168 17 1 Mask 255 255 255 0 Diagnostic Neighbours Routes f CAE Destination Mask Gateway Backup Note Active Modify 192 168 15 0 24 255 255 205 0 0 16 Backup 1 RipEX A v 7 Delete A
96. ions which would not work when the normal store and forward regime is used because of the inevitable delays involved The Stream mode is configured in the Settings Device Operating Mode menu RACOM s r o RipEX 85 Channel access Operating mode Operating moide Frame closing COM s 10 4 Router Mode 10 4 1 Channel access in Router mode The protocol in the radio channel in the Router mode of RipEX uses sophisticated method to prevent and solve collisions When a data packet with RSS above the configurable threshold or a data packet destined for the RipEX itself are received it leads to the busy channel state as well as the RipEx s own transmission When RipEX evaluates the channel as free it calculates the Access period time for which it has to continue monitoring the channel before starting a transmission Only when the channel stays free for the Access period or more RipEX starts transmitting whenever a packet destined to radio channel ar rives If channel gets busy the arriving packets have to wait in a queue and whole process starts from the beginning The Access period calculation follows quite complex algorithm which takes into account RipEX settings properties of the last packet sent or received and there is very important random element The result is an optimum performance of RipEX s in a report by exception network 10 4 2 Solving collisions in Router mode When report by exception appli
97. ipEX RACOM s r o SNMP 33555 2 3 1 3 1 14 X stRem lotalPacket read only j current Remote station total Rx packets counter SRx 33555 2 3 1 3 1 15 X stRemTotalPacket read only current Remote station total Tx packets counter sTx 33555 2 3 1 3 1 16 X stRem TotalBytes Remote station total Rx bytes counter Rx 335552 3 1 3 1 17 X st Rem Total Remote station total Tx bytes counter BytesTx 33555 2 3 2 1 stTcpModNumber Number of TCP Modbus ports 33555 2 3 2 2 stTcpModTable List of TCP Modbus port entries ible 39555 2 3 2 2 stIcpModEntry TCP Modbus port entry ible 33555 2 3 2 2 1 1 X stTcpModIndex TCP Modbus port index 33555 2 3 2 2 1 2 X stTcpModPackets TCP Modbus Rx packets counter Rx 33555 2 3 2 2 1 3 X stTcpModPacket TCP Modbus Tx packets counter STX 33555 2 3 2 2 1 4 X stTcpModBytesRx TCP Modbus Rx bytes counter 33555 2 3 2 2 1 5 X stTcpModBytesTx TCP Modbus Tx bytes counter 39555 2 3 3 stfermServNum read only current Number of Terminal Server ports ber 39955 2 9 9 2 stTermServ Table ae List of Terminal Server port entries ible 33595 2 3 3 2 1 stTermServEntry Terminal Server port entry ble 33555 2 3 3 2 1 1 X stTermServIndex read only current Terminal Server Terminal Server port index index ee tell read only ual Terminal Leia NM Rx packets counter etsRx 33555 2 3 3 2 1 3 X stTermServPack read only current Terminal Server Tx packets counter ets Tx 33555 2 3 3 2 1 4 X
98. items which are triggered by 15 kinds of traps RACOM s r o RipEX 17 SNMP o 1 Application 15 Items 15 Triggers e Name PING Template o Pings a defined host and triggers whenever the host is unreachable o 1 Application 2 Items 1 Trigger All templates can be downloaded from the RipEX Download site at http www racom eu down load hw ripex free eng 3 fw RipEX Zabbix templ zip How do I Import the RipEX Templates In order to import the template click on the Configuration Templates button at the top of the Zabbix web page At top right corner you will see the Import Template button click on it Create Template Import Template Group Templates Fig 2 3 Importing Template button Important AN Before importing the template file see Chapter 2 3 4 Value Mappings Since the Zabbix release 2 2 1 it is mandatory to define the value mappings before importing the required templates Select the RipEX template file and Import that file Repeat this step for each template Import EJ Import file ne Element Update Existing Add Missing Template v v Template linkage w Rules Item v v Trigger v v Graph v v Fig 2 4 Importing Template options Now you can see all RipEX templates at the Template list window among all other templates which are in Zabbix by default Note If you already imported the template and you need to update it just import the newer version with the same name and the
99. ith margin of 2 3 dB resulting in the system gain of 147 dB o6 RipEX RACOM s r o Data speed and Modulations e For applications where higher data throughputs are needed the additional increase in spectrum ef ficiency can be gained by D8PSK and 16 DEQAM modulation formats However compared to 11 4 DQPSK an increase in overall communication efficiency cannot be expected while there is the in evitable penalty in power efficiency characteristic References 1 ETSI EN 300 113 1 V1 6 2 2009 11 Electromagnetic compatibility and Radio spectrum Mat ters ERM Part 1 Technical characteristics and methods of measurement European Standard ETSI 11 2009 2 ETSI EN 302 561 V1 2 1 2009 12 Electromagnetic compatibility and Radio spectrum Mat ters ERM Land Mobile Service Radio Equipment using constant or non constant envelope modulation operating in a channel bandwidth of 25 kHz 50 kHz 100 kHz or 150 kHz Harmonized EN covering essential requirements of article 3 2 of the R amp TTE Directive European Standard ETSI 12 2009 3 ETSI EN 301 166 1 V1 3 2 2009 11 Electromagnetic compatibility and Radio spectrum Mat ters ERM Part 1 Technical characteristics and methods of measurement European Standard ETSI 11 2009 RACOM s r o RipEX of Autospeed 4 Autospeed Normally all radio modems in a network have to transmit with the same data rate on the same radio channel The Autospeed feature of RipEX
100. itivity shall not exceed an electromotive force of 3 0 dBuV under normal test conditions RACOM s r o RipEX o3 Data speed and Modulations Assigning this value as S one can also express what signal to noise ratio SNR can be expected in relation to noise figure NF and transformed to the receiver input SNR S 10 log kT 10 log By NF dB 2 1 In 2 1 k is the Boltzmann s constant T is the absolute temperature in Kelvin and By is the receiver noise bandwidth of e g 25 kHz 3 2 1 Maximum usable data sensitivity In this section the results of maximum usable data sensitivity measurement Figure 3 4 for the complete narrowband radio transceiver are presented All the results are given for 25 KHz channel separation Firstly let us focus on operational modes with exponential modulations Figure 3 4 It can be seen that the emf sensitivity limit of 3 dBuV 110 dBm 50 Q is fulfilled with margin for both modulations 2CPFSK 4CPFSK when running at the symbol rate of 10 4 kBaud When higher symbol rates are selected these modulations loss their power efficiency rapidly and for the selected symbol rate of 17 3 kBaud the sensitivities lower down to the values of 107 dBm BER 10 and 102 dBm BER 10 for 2CPFSK and 4CPFSK respectively This discrepancy is caused mainly due to the fact that there is a significantly lower frequency deviation used at the higher symbol rates The decrease in power efficiency with increasi
101. itoring or by executing Tcpdump or Wireshark at the selected interface of your Zabbix server or somewhere along the intended packet path Another basic test can be run using the following command zabbix sender z localhost p 10051 s 192 168 10 1 k trpTemp o ALARM ON The IP address of your RipEX station is 192 168 10 1 key is trpTemp and the message for the Zabbix server is TEST The command should trigger the host s Temperature alarm Note that you need to have a host configured with this IP address otherwise the trap will not be shown It is important to set the KEY value correctly otherwise the trap would not match the trigger See more KEY values with their description below e trpRsslPAdaress Remote station RSS value out of range Replace the IPAddress with a real remote RipEX IP address e trpDglPAdaress Remote station DQ value out of range Replace the IPAddress with a real remote RipEX IP address e ttroTxLost TX Lost value out of range e trpUcc UCC value out of range e trplemp Modem temperature value out of range e trphfpwr RF power value out of range e trpLanPr Ethernet RX TX packet ratio out of range e trpCom1Pr COM1 RX TX packet ratio out of range e trpCom2Pr COM2 RX TX packet ratio out of range e trpHwln HW input in the alarm state e trpHotStby Modem becomes active in a Hot Standby mode e rpBpath Backup path state has changed e troBpathAlt Alternative path state has c
102. le polling type application which never generates more than a single packet at a time collisions may occur when repeaters are used The goal of channel access is either to eliminate collisions completely or to reduce their probability while ensuring that systematic repeated collisions never happen RipEX provides different channel access methods in different modes and optimum configuration can be found for every communication scheme and network layout 10 1 Collisions What is so special about collisions that they deserve that much attention Well they are a special case of interference friendly fire a military reporter would say which may very seriously harm network performance A collision happens when two or more transmissions in the network overlap in time Radio modem A transmits a packet for B C transmits for D In well designed network the respective signal levels i e A received at B C received at D do ensure error less reception For the period of time when these two transmissions overlap signal from C at receiver input B and signal A at D act as interference signals reducing the SNR Signal to Noise Ratio If B and D are in the same area the difference in signal strength is small and so is the resulting SNR at both receivers Consequently the BER Bit Error Rate at both receivers jumps to unacceptable level and none of the packets is successfully received That is the basic principle of a collision There are two very h
103. mStateDq Alarm state DQ AR Rin EX RACOM s r o SNMP 33555 2 5 2 16 alarmStateRx read only current Alarm state ETH interface Rx to Tx TxEth packets ratio 33555 2 5 2 17 alarmStateRxTx read only current Alarm state COM1 interface Rx to Tx Com packets ratio 33555 2 5 2 18 alarmStateRxTx read only current Alarm state COM2 interface Rx to Tx Com2 packets ratio 33555 2 5 2 31 alarmStateHwlin read only current Alarm state HW Input put 33555 2 5 2 32 a a r m read only current Alarm state Unit ready StateUnitReady 33555 2 6 1 bpathsNumber Number of Backup Paths 33555 2 6 2 bpaths Table not access current List of Backup Paths entries ible 33555 2 6 2 1 bpathsEntry Backup Paths entry ible 33555 2 6 2 1 1 X bpathsIndex Backup Paths index 33555 2 6 2 1 2 X bpathsPeerlp Backup Paths Peer IP address 33555 2 6 2 1 3 X bpathsName Backup Paths Symbolic Name 33555 2 6 2 1 4 X b p a t h jread only current Backup Paths Alternative Paths Cur sAltUsedPrio rently used path priority 33555 2 6 2 1 5 X bpathsAltUsedGw read only current Backup Paths Alternative Paths Cur rently used path Gateway IP address 33555 2 6 2 1 6 X bpathsAltUsed read only current Backup Paths Alternative Paths Cur otate rently used path State 33555 2 6 2 1 7 X bpathsAltPass read only current Backup Paths Alternative Paths Cur iveState rently passive paths State 33555 2 10 1
104. nd E in the Application Note Section 1 1 End devices connected via serial interface Practical Test In this scenario we will switch to the backup path due to a low RSS value We must change the policy for the primary path to enable RSS checks Click on the respective Default button in the Policy column Note You can check the connectivity with a Ping feature Diagnostic Ping 108 RipEX RACOM s r o Status Wizards settings Routing Diagnostic Neighbours Statistic Graphs Ping Monitoring Maintenance Radio modem amp Router Values from RipEX A Interfaces Radio MAC 00 02 AS BE OF AB ETH MAC 00 02 AS BR OB C3 Routes Destination Mask 10 10 10 17 32 255 255 255 255 10 10 10 18 32 255 255 255 255 10 10 10 19 32 255 255 255 255 Backup Name Peer IP Backup 1 10 10 10 17 20 Legend Up Down Apply Cancel Fig 12 6 RipEX A Policy button Hysteresis Backup routes EP RACOM IP 10 10 10 15 Mask 255 255 255 0 IP 192 168 15 1 Mask 255 255 255 0 Gateway Backup Note Active Backup 1 Backup RipEX C v 10 10 10 16 of RipEX D v 10 10 10 16 Of RipEX E v Alternative paths SNMP Trap Gateway Policy Active Note 40 10 10 47 v Direct link 10 10 10 16 Default v Indirect link Unknown Currently used Route for IP sJ EEER The new pop up window appears Change the Parameters to Manual and fill in the RSS dBm value according to the current RSS value see the
105. nds e PC 1 o route delete 192 168 2 252 mask 255 255 255 255 192 168 2 251 o route delete 192 168 2 2 mask 255 255 255 255 192 168 2 251 e PC 2 o route delete 192 168 2 251 mask 255 255 255 255 192 168 2 252 o route delete 192 168 2 1 mask 255 255 255 255 192 168 2 252 Test the Connectivity The test is exactly the same as described in Chapter the section called Test the Connectivity The most important thing to remember with the ARP proxy example is that we did not need to configure any default gateway or routing rules on the computers RTUs Thanks to this we can even add simple RTUs to our network and we can have the same IP subnets behind different RipEX units Tip Give careful thought to the network design because a good design can dramatically reduce the number of necessary routing rules in the RipEX routing table Example 11 1 Routing rules You have four end stations with IP addresses 192 168 2 1 2 2 2 5 and 2 6 and you need two of them behind RipEX A and two of them behind RipEX B With 192 168 2 1 and 2 2 behind RipEX A you will need to add only one rule in the RipEX B 192 168 2 4 30 via RipEX A Otherwise you will need to add two rules e g with 2 1 and 2 5 IP addresses 11 4 3 VLAN We will explain two similar examples to show the VLAN functionality VLAN on One End In this example we will have a VLAN ID 2 used between RipEX A and PC 1 RipEX management traffic on the same Ethernet
106. ng spectrum efficiency is not linear as for the typical linear modulations Although possible this example documents that the increase in spectrum efficiency of exponential modulation techniques cannot be considered for efficient use of assigned bandwidth 1 E 01 2CPFSK 10 42 kBaud e 2CPFSK 17 36 kBaud s 4CPFSK 10 42 kBaud amp 4ACPFSK 17 36 kBaud 1 E 02 A 1 E 03 im 1 E 04 1 E 05 120 118 116 114 112 110 108 106 104 102 100 98 96 94 92 90 signal Level dBm Fig 3 4 Maximum usable sensitivity measurement results for different settings of exponential modulations The second set of measurement results presented in Figure 3 5 documents the power efficiency analysis of operational modes based on the linear modulation techniques It can be seen that when using the linear 1 4 DQPSK the radio receiver can still reach the data sensitivity limit even for 17 3 kBaud with a 2 dB margin Even from this comparison it is evident that the 1r 4 DQPSK mode of operation outperforms the 4 CPFSK at higher spectrum efficiencies Further increase in spectrum effi ciency can be reached by higher order constellations such as D8PSK and 16DEQAM and the radio receiver can still maintain practically applicable sensitivities of 107 dBm BER 10 and 105 dBm BER 10 respectively o4 RipEX RACOM s r o Data speed and Modulations
107. nly the radio IP addresses for translation and data routing Ethernet IP addresses may be assigned randomly you can keep their defaults however we recommend setting Ethernet addresses similar to radio IP addresses to keep things organized RACOM s r o RipEX 105 Backup routes Radio 10 10 10 18 iin A PATH 1 N y RS232 18 Radio 10 10 10 17 Radio 10 10 10 15 1D PATH 2 RipEX C Radio 10 10 10 19 RS232 00017 Radio 10 10 10 16 ge RS232 RipEX A RS232 19 RipEX B 0016 RS232 Fig 12 2 Network topology 1 The device connected to RipEX A 10 10 10 15 is the Master station others are slaves Note We will not configure RS232 devices in this Application note The Backup routes system can be used between RipEX A 15 and RipEX C 17 packets can be transmitted via e the primary direct radio link between RipEX A and RipEX C or e the backup indirect radio link over RipEX B See the following RipEX A routing configuration 2 i 2 x lt Radio modem amp Router Status Values from RipEX A Wizards Settings Interfaces Ro uting Radio MAC O0D 02 AS BR OF AB IP 10 10 10 15 Mask 255 255 255 0 s ETH MAC 00 02 A3 BB OB C3 IP 192 168 15 1 Mask 255 255 255 0 Diagnostic Neighbours Routes f Statistic ae Gateway Backup Note Active Modify 10 10 10 17 32 255 255 255 255 Backup 1 Backup RipEX C v Delete Add Graphs 10 10 10 18 32 209 200 222 222 10
108. nse time This value is the same for all DP Slaves and is distributed from the DP Master at the beginning of their communication This value must be lower than Tslot init Slot time Min Tsdr Sets the minimum DP Slave response time 11 to 255 bit values are permitted This value is the same for all DP Slaves and is distributed from the DP Master at the beginning of their communic ation This value must be lower than Max Tsdr Tset Sets delay This is used to postpone broadcasting of the next packet This parameter enables you to create space for other communication on RipEX network Tqui Quit time Sets the switching time between reception and broadcasting This must be lower than Min Tsdr Note All times are given in bits 1t bit 1 Baud rate seconds A single bit time Baud rate data transfer speed 104 2 us 9600 bps 52 1 us 19200 bps Example of Profibus DP settings in STEP 7 Under network layout click the right mouse button to open Object Properties 66 RipEX RACOM s r o Profibus E3 HW Config SIMATIC 316 2 Configuration RacomTestyDP in Station Edit Insert PLC View Options Window Help T x D gx Gy Sl Eu a m ux Lcx kh 0 UR CPU 315 2 DP Ctrl C IMT51 Delete Del Move eo a Pack Addresses k 0 To Order number Object Properties Alt Return P PM E DC24V BES 138 4CAUT DAAL 4DI DC24V ST BES 1317 46001 O440 I 4D0 DC24V 0 54 ST
109. nt thus it is suitable for SCADA protocols containing the destination address in all packets Protocol 4 Protocol UMI Mode of Connected device Address mode Binary 1E Address position Poll response control Broadcast Broadcast addr format Broadcast address 255 Address translation Mask Base IP 10 0 0 1 Mask 255 255 255 0 UDF port interface The Poll Response Control has to be set to OFF for the MASTER MASTER type of communication 9 4 MASTER UNI ASYNC LINK SLAVES The combination of the UNI and the ASYNC LINK protocols is useful for networks where one application master communicates with many slaves and the slaves are allowed to spontaneously send messages to the master The UNI Master RipEXSs address is configured as the ASYNC LINK protocol destination address at all the slaves This arrangement makes the syntax of application protocol messages generated by slave completely arbitrary All slave messages are transparently delivered to the application master RACOM s r o RipEX 19 UNI protocol Protocol Protocol Asyne Link Destination IP 132 158 0 0 UDP port interface COM 8881 Note that similarly to the MASTER MASTER mode the Poll Response Control at the Master RipEX has to be set to Off 80 RipEX RACOM s r o Channel access 10 Channel access Method of accessing the radio channel may significantly affect the overall reliability of packet transmis sion Even in a simp
110. o RipEX 89 ARP Proxy amp VLAN Radio IP hy Radio link fi Radio IP 10 10 10 2 ACEN 10 10 10 3 24 Router mode i02 155425024 e Untagged Data Tagged Data FZ Untagged Ws IP 192 168 1 2 24 192 168 4 1 24 Gateway defined er Radio IP 10 10 10 4 v IP 192 168 2 2 24 ETH IP 192 168 4 1 24 Gateway defined Untagged Data Rru 2 Untagged Data Management Aplication IP 192 168 3 251 24 Tagged Data Tagged Data FEP 1 FEP 2 IP 192 168 1 1 24 IP 192 168 2 1 24 Gateway defined Gateway defined Fig 11 2 VLAN diagram As you can see in Fig 11 1 Basic ARP proxy usage we have individual VLANs for Management and two distinct technologies each with its own IP subnet Note You can combine the VLAN feature with a TCP proxy and Terminal Servers See the re spective help in the RipEX web interface for details 11 4 Configuration Examples In this chapter we will go through several examples in order to explain ARP proxy and VLAN features in practice All examples will have the same hardware configuration and we will alter the software settings only ARP proxy VLAN tagging routing Regular PCs will be used instead of RTUs Please follow the examples one by one to fully understand the configuration differences and benefits of various solutions 11 4 1 No ARP Proxy and No VLAN We will begin with a basic configuration example without using ARP proxy or VLANs
111. o PAPR of the digital modulation scheme in use transmitter nonlinearity and the efficiency of the power amplifier linearization or pre distortion technique and all have to be considered when selecting the digital modulation technique for the system where both power and spectrum are the key issues In light of these facts one can arrive at the conclusion that setting up the limit at 60 dB rather than 70 dB was a reasonable step while the initial limit has been left to be beyond the state of the present linearization technology for equipments production which in turn hindered the use of spectrally more efficient modulation techniques VBW 30 Hz VBW 30 Hz Ref 10 dBm Att 30 dB SWT 34 s Ref 10 dBm Att 30 dB SWT 34 s mom mn Center 420 0125 MHz 10 kHz Span 100 kHz Center 420 0125 MHz 10 kHz Span 100 kHz Tx Channel Tx Channel Bandwidth 25 KHZ Power 9 n 9 4 dBm Bandwidth 25 kHz Power 9 6 4 dBm Adjacent Channel Adjacent Channel Bandwidth 16 kHz Lower 60 92 dB Bandwidth 16 kHz Lower p0 19 daB Spacing 25 KEZ Upper 60 11 dB Spacing 25 KHz Upper 60 11 dB Fig 3 2 Modulated signal spectrums left 4CPFSK with R 10 4 kBaud modulation index h 0 3 right 4CPFSK with R 17 3 kBaud modulation index h 0 1 3 1 3 Transmitter power efficiency In this section the measurement results concerning the overall narrowband transmitter p
112. o configure traps only one of them will be explained in this guide Note Another approach could be using SNMPTT functionality You have to install an snmptrapd a daemon which receives SNMP traps and pass them into the Zabbix front end You can use the script snmptrap sh which is included in the RipEX Zabbix templ zip file downloadable from http www racom eu eng products radio modem ripex htmlZzdownload website Copy the script file into home zabbix bin directory and change the file privileges and make it executable mkdir p home zabbix bin chown zabbix home zabbix cp misc snmptrap snmptrapd sh home zabbix bin chmod x home zabbix bin snmptrapd sh After that you need to edit the file By executing which zabbix sender you will find the full path to this executable binary file Change the path in the file e g ZABBIX SENDER usr bin zabbix sender Make sure you have set other parameters correctly e g ZABBIX SERVER localhost ZABBIX PORT 1 UNS KEY snmptraps HOST snmptraps SERVER and PORT could be different as per your configuration KEY and HOST has default values they will be changed depending on type of trap received RACOM s r o RipEX 29 SNMP After that the script parses the output of each received SNMP trap looks to the MySQL database to select appropriate host and declares an associative array containing trap descriptions Eventually it sends the whole message to y
113. odbus TCP Master e Set the translation from Modbus to RipEX IP addresses to table based as described in chapter 3 e For devices connected over Modbus RTU set the UDP interface to COM1 or COM as in chapter 4 e For devices connected over Modbus TCP set the UDP interface to TS1 TS5 as described in chapter 3 e You can define address ranges in the table for greater ease of use To set up RipEX connected to Modbus RTU Slave e See chapters 4 and 1 respectively To set up RipEX connected to Modbus TCP Slave e See chapter 3 8 6 Multiple Modbus TCP or Modbus RTU Masters and Slaves Any combination of network designs described in chapters 1 5 is possible The only limitation is that a Master with Modbus RTU cannot communicate with a Slave using Modbus TCP RACOM s r o RipEX 15 Modbus TCP RTU A Slave with Modbus RTU protocol may simultaneously communicate with masters using Modbus TCP and Modbus RTU The network will deliver responses only to the Master which issued the queries using the appropriate protocol The individual settings are described in chapters 1 5 9 ge Modbus TCP RS232 Local TCP Modbus RTU connection connection RS232 000 S ETH RS232 Bia Modbus TCP Modbus RTU Local TCP N Modbus TCP Modbus RTU Local TCP connection Fig 8 7 Modbus TCP Slave RTU or TCP 76 RipEX RACOM s r o UNI protocol 9 UNI protocol UNI is the Universal protocol utility
114. onization algorithms also significantly contributes to the efficient channel usage especially in packet based switching networks The systems thus maintain good power efficiency while the spectral efficiency reaches compromising values not exceeding 1 bit s Hz 3 1 1 Digital modulation for narrowband channel The prime classification of the digital modulation techniques into a nonlinear or exponential and linear modulation class is based on the way how the modulated signal has been generated The complex modulation envelope of the linearly modulated signal such as M PSK M QAM etc can be described by a linear superposition of the properly filtered modulation impulses weighted by the information symbols In case of the nonlinear modulation techniques this general rule is valid only for the modulation signal which modulates the phase of the fundamental carrier signal Thus the modulation process itself is nonlinear exponential The M CPFSK in this case is recognized as a general class of nonlinear or exponential digital modulation with a continuous phase change 3 1 2 Adjacent channel power and spectrum efficiency The adjacent channel power or adjacent channel interference ACI is that part of the total output power of a transmitter under defined conditions of modulation which falls within a specified pass band centred on the nominal frequency of either of the adjacent channels This power is the sum of the mean power produced by the modulation
115. ork may significantly shorten the total DP Slave polling cycle If one of the DP Slaves is out of order or if its response is lost the DP Master will only wait for a set minimum time before sending another query The value should be set to maximum to prevent problems The calculator on http www racom eu eng products radio modem ripex html calculation enables you to calculate the RTT round trip time Set the PLC Master to Ethernet interface in the calculator Profibus protocol timing is based on the last sent byte time on Master s RS485 does not figure in this calculation RTT for Bridge mode can be used directly for Router mode the resulting average RTT needs to be multiplied by constant 1 25 to receive the maximum achieved RTT Calculate the recommended Tslot Init as follows Tslot Init RTT Port speed in bps 1000 i http www racom eu eng products m ripex h menu html a http www racom eu eng products m ripex h menu html RACOM s r o RipEX 69 Profibus 7 4 2 Router mode timing Router mode web based settings may cause time problems in more complex networks CLI lets you adjust radio channel access parameters and set up repetition taking into account the number of re translations in your radio network If you only use the Profibus protocol with RipEX and no other broadcast interferes with your network you can configure certain parameters to shorten the access time to channel using CLI If you want to use pa
116. our Zabbix server The script logs trap information into the tmp trap messages log file Note If you have MySQL database protected by a password you need to change this line ZABBIXHOST S echo select host from zabbix hosts where host SsourcelIp order by hostid P limit 1 mysql N 2 dev null to ZABBIXHOST S echo select host from zabbix hosts where host SsourcelIp order by hostid P limit 1 mysql N u lt USER gt p PASSWORD 2 dev null Replace the USER and PASSWORD to correspond to your settings OK now we have our script prepared let s configure the Zabbix front end If you have not yet done so import the template file zbx templates trapper xml This template includes Zabbix trapper and should be linked to each monitored RipEX station It will cause all received traps for known hosts to be mapped to the appropriate host Note If Zabbix receives a trap for an unknown host it will not be displayed The host MUST to be configured using the IP address as the Host name e g Host name 192 168 10 1 Visible name RipEX1 SNMP interface 192 168 10 1 port 161 IP Along with this template 15 new items and triggers appear at each used host That is exactly the number of SNMP traps defined at the RipEX Each trap should be recognized and the Zabbix should display the correct information message at the dashboard 30 RipEX RACOM s r o SNMP Status las It nodata 300
117. ower efficiency are presented It is no ambition however to provide exact power efficiency analysis of the particular high power amplifiecwith the selected linearization circuit proceeded It is rather to give the example of the practically achievable overall transmitter power efficiencies and to show the differences related to selected digital modulation formats of each of the linear nonlinear class The standard 2 specifying the conformity testing for TETRA like devices allows 55 dBc in normal or 50 dBc in extreme temperature conditions assuming channel separation of 25 kHz RACOM s r o RipEX 51 Data speed and Modulations RBW 100 Hz RBW 100 Hz VBW 30 Hz VBW 30 Hz Ref 10 dBm Att 30 dB SWT 34 s Ref 10 dBm Att 30 dB SWT 34 s Tx Channel Tx Channel Bandwidth 25 KHZ Power 3 99 dBm Bandwidth 25 JR Powe r 1 7 5 dBm jJacen anne Adjacent hannel elc pep duae 16 kHz Lower 60 78 dB ane 16 kHz Lower 60 35 dB Spacing 25 kHz Upper 61 80 dB Spacing 25 kHz Upper bU SU dB Fig 3 3 Modulated signal spectrums left 1 4 DQPSK with R 17 3 kBaud right 16 DEQAM with R 17 3 kBaud As for the linear modulation techniques the differentially encoded formats mrr 4 DQPSK D8PSK and 16 DEQAM have been selected and tested mainly due to their low modulation envelope variations and inherent robustnes
118. port would be untagged Traffic on the radio channel is always untagged Traffic between RipEX B and PC 2 will be also untagged 96 RipEX RACOM s r o ARP Proxy amp VLAN see the following diagram Radio link Router mode Radio IP hy a Radio IP 10 10 10 2 24 Untagged Data 10 10 10 4 24 RipEX A VLAN RipEX B no VLAN ETH IP 192 168 3 251 24 ETH IP VLAN IP 192 168 2 251 24 192 168 2 252 24 VLAN tagged Data Untagged Data Untagged Data ay x Sey SES SSGOXA ETH IP VLAN IP 192 168 2 1 24 192 168 3 1 24 PC 1 PC 2 l 192 168 2 2 24 GW 192 168 3 251 GW 192 168 2 252 Fig 11 10 VLAN configuration diagram RipEX Configuration The configuration on RipEX A will be a little more complicated There will be two subnets one for VLAN and one for other traffic Go to the Settings menu and change the Ethernet IP address to 192 168 3 251 Then click on the VLAN amp Subnets button and add a new VLAN we will use VLAN ID 2 with an IP address 192 168 2 251 VLAN amp Subnets VLAN amp Subnets On Interface VLAN ID IP MASK Priority Unit Manag ARP proxy Note Active Madify ETHO 192 168 3 251 24 v Default interface Add Subnet 0 v Add Subnet Delete Add VLAN OK Fig 11 11 RipEX A VLAN configuration On RipEX B turn the VLAN amp Subnets option off The routing rules can stay exactly the same as in the previous ARP proxy example on both RipEX units
119. pproximate results 3ms When more accurate calculation is necessary please check the calculation tool on Racom web pages http www racom eu eng products radio modem ripex html calculation TX delay is configured in the Settings Device Operating Mode menu for Radio 1 left and Radio 2 right Operating mode Operating mode Operating mode Operating mode Frame closing COM s dle T Frame closing COM s Idle Repeater Ott hi Repeater Of 2 Mo of repeaters j a Mo of repeaters TX delay ms fo TX delay ms 10 3 Bridge mode and COM stream The COM port in Bridge mode can be switched into the Stream mode In any other mode a packet frame coming to RipEX over any interface has to be received completely before any further processing In Stream mode the incoming bytes are transmitted to radio channel with minimum possible delay byte by byte Consequently nor checks neither processing of the data can be done All the bytes are simply broadcast to the radio channel and every radio modem which can receive them forwards them imme diately to its COM port s Obviously there can not be any repeaters in the Stream mode and no measures against possible colli sions can be taken The responsibility for collision free communication remains solely with the application Consequently only simple master slave polling type applications which never respond to broadcasts can use the Stream mode This mode should be used solely in applicat
120. priate protocol in Slave mode In the border RipEX the timeout for response from technology should be extended from 500 ms to several seconds the response time will depend on the size of the MORSE network this parameter can only be set in CLI On the MORSE side the protocol should be set to Master 64 RipEX RACOM s r o Profibus 7 Profibus Radio modem RipEX supports the most widely spread Profibus Process Field Bus type designated Profibus DP Decentralized Periphery type O see http www profibus com technology profibus Profibus DP is designed for fast master slave communication The central master unit communicates with the remote slaves using RS485 bus They are typically connected by twisted pair cabling The cable length between two RS485 repeaters is limited from 100 to 1200 m depending on the bit rate used The RipEX Profibus DP implementation allows for RS485 to be replaced by radio network either partially or entirely This significantly increases the potential distance between the individual nodes or even enables you to get rid of cable links altogether 7 1 Bridge and Router modes RipEX operates in two basic modes Bridge and Router Network topology determines which one is the more suitable for your specific application see chapter RipEX in detail of the manual Apart from network layouts designed in this manual we also recommend using Router mode if alongside the central RipEX some PLC Slaves are also
121. proximately 48 kilobytes Based on the limitations and the MIB size we recommend to query only carefully selected OIDs over the radio channel and not all possible data Set SNMP query time intervals in your NMS as long as possible The shortest recommended interval ranges from several minutes to tens of minutes Wherever possible use the RipEX Ethernet interface for SNMP communication to free up the radio channel Note There are many Network Management Systems available on the market Whichever you choose keep in mind the described limitations E g never use NMS which can download only the entire remote device MIB and not single OIDs i http www racom eu eng products m ripex h menu html 14 RipEX RACOM s r o SNMP Bandwidth Efficiency Tip If you wish to monitor many watched values VSWR Temperature UCC from remote stations connected over the radio channel and you have a star topology network you can improve bandwidth efficiency by reading OID values only from the Master Repeater RipEX station The advantage of the above is that the watched values from remote stations are broadcast in regular intervals and saved in the Master Repeater RipEX These values from neighbouring stations have their own OID s and can be downloaded from the Master Repeater RipEX In the picture below Master RipEX station periodically reads watched values from its neighbouring Slave stations Whenever the NMS requests any val
122. r priority paths checking On Fig 12 13 Default Policy values Note Hello packet success rate evaluation is based on last 8 Hello packets To see the whole procedure you can start with issuing ping packets Go to the RipEX A Diagnostic Ping menu and fill in the destination IP address 192 168 17 1 At this stage ping packets will be successful and will be transmitted via the primary indirect path e g check the RipEX RX TX led diodes RACOM s r o RipEX 113 Backup routes 3 2 X Radio modem amp Router Co RACONA Status Values from RipEX A Wizards settings Ping Routing Ping Type icmp Length bytes a Period ms E Destination K 192 168 17 1 7 Count Mo P oea ms 10000 Diagnostic m Neighbours PING 192 168 17 1 192 168 17 1 80 108 bytes of data Statistic 88 bytes from 192 168 17 1 icmp req 1 ttl 63Cfime 412 m33 88 bytes from 192 168 17 1 icmp req 2 ttl 63 time 446 ms Gr 68 bytes from 192 168 17 1 icmp req 3 ttl 63 time 360 ms gt Ping 88 bytes from 192 168 17 1 icmp_reg 4 ttl 63 time 360 ms 88 bytes from 192 168 17 1 icmp req 5 ttl 63 time 395 ms Monitoring 88 bytes from 192 168 17 1 icmp req 6 ttl 63 time 343 ms B8 bytes from 192 168 17 1 icmp req 7 ttl 63 time 412 ms Maintenance x uus 88 bytes from 192 168 17 1 icmp req 9 ttl 63 time 412 ms 88 bytes from 192 168 17 1 88 bytes from 192 168 17 88 bytes from 192 168 17 B8 bytes from 192 168 17
123. request and the RTUs 1 2 and 3 generate the response and send it out to their respective RipEX Request Response RTU 1 Radio 1 RTU 1 Radio 1 CHO CHFO A NS N RTU 2 Radio 2 Radio Centre RTU 2 Radio 2 Radio Centre C O O41 CEREO O B RTU 3 Radio 3 4 RTU 3 Radio 3 p 1 Radios 1 2 and 3 have the TX delay parameter set to 0 100 and 200 ms respectively Therefore Radio 1 starts transmitting just after reception of the frame from COM port Upon 100 ms later when Radio 1 has completed transmission Radio2 starts transmitting Finally 200 ms after the reception of the packet from RTU Radio 3 starts its transmission All three responses are thus sequentially sent to the Centre and no collision happens COM Radio Transmission Radio1 E LE RE delay E 0 B Radio 2 B LO T dellay 2 C Radio 3 M Q Tx dell 3 time 0 NE MEL Radio pud COM Centre A marcas Ores The TX delay parameter coresponds to multiples of maximum packet length expected and shall be set in miliseconds The packet transmission time through radio channel can be calculated as follows t n 12 8 b fec where 84 RipEX RACOM s r o Channel access t ms time needed for the packet transmission n number of bytes transmitted consider the longest possible reply from RTU b kbps Modulation rate fec Forward Error Correction tec 1 00 1t FEC Off tec S 0 75 1L FEC On This calculation gives a
124. ripex bench test html connect PC In the common configuration with two different IP subnets behind our RipEX units we would not need any further action to get the end point connectivity In this example we must add two routes on both computers To add routing rules in Windows you need to execute Windows Command Processor cmd Click on the Start button and then type Command Prompt or cmd in the Start Search field Select the Command Prompt icon After the Command Prompt window appears type the following commands on PC 1 CXO ute ada I92 169 2 292 MASK 2992299929999 1976166224251 FOULS add 197 160 7252 MaSK 2992299 29954209 1922166 2 2501 You also need to add similar routing rules on PC 2 Toute 300 L92410952 291 Week LOAA A LoL Ged FOULS 20d 192 100 2241 MASK 2002094299429 19e LIOA RACOM s r o RipEX 93 ARP Proxy amp VLAN Note You need Admin privileges to add a route in Windows 7 Programs 1 Files 4 File description Windows Command Processor Company Microsoft Corporation File version 6 1 7601 17514 1 Date created 1 7 2013 10 59 AM Size 295 KB 2 Slovensky Slovenian Serbian M Russian 4 d Romanian See more results p cmd x Shwst down k Fig 11 6 Command Prompt Test the Connectivity Check the connectivity by executing a ping command which is also executed from the Command prompt Type ping 192 168
125. s First packet A is broadcast from Radio 1 Radio 2 receives Packet A and sends it to its COM In the instant when it starts the reception of Packet A Radio 2 calculates from information in the received packet header and from number of repeaters in its own setting the time delay which is needed for the delivery of Packet A through the repeater repeaters When the response from the connected device arrives via COM Packet B the Radio 2 postpones its transmission for the delay COM RadioTx Rx header data A Radio 1 header A B Radio 2 dE la no Tx Radio 3 REP A A B B O Ted ed COM In the meantime Radio 3 Repeater receives Packet A and repeats it to the radio channel immediately Radio 4 receives the Packet A and then Packet B and sends them both to the COM Packet B is also received by Radio 3 and immediately repeated Whenever a radio receives a copy of the same packet during the calculated delay it discards it as a repeated packet Note that the picture does not show all the packets at all the radios Repeater is configured in the Settings Device Operating Mode menu for Radio 3 left and Radio 1 2 4 right Operating mode Operating mode Operating mode Bridge hil Operating mode Frame closing COM s Idle Frame closing COM s Idle bi Repeater On E Repeater Off a Mao of repeaters 2 Mo of repeaters 1 TX delay ms TX delay ms j The delay period based on numb
126. s against negative effects of signal propagation through the narrowband radio channel The 2CPFSK and 4CPFSK have been selected from the nonlinear modulation class There is one particular parameter of high importance essentially influencing the characteristics of these modulation formats and that is a modulation index It expresses the relation between the modulation rate and the maximum frequency deviation according to simple rule 1 1 2Af h 1 1 R M 1 where R is the modulation rate M is the number of modulation states and Af is the maximum frequency deviation representing the outermost symbol frequency position The selection of the modulation index in most practical applications of narrowband LMR has been driven by compromising requirements between the modulation rate receiver sensitivity and adjacent channel power level Its value usually converges to 1 M with a well known example of MSK particularly GMSK where M 2 thus h 0 5 as the lowest value needed to maintain an orthogonal signaling In order to compare the modulation formats at the same spectrum efficiency we also measured the properties of 2CPFSK and 4CPFSK modulations with very low modulation index resulting in use of high symbol rate of 17 3 kBaud The examples of transmitted signal spectrums can be seen in Figure 3 1 to Figure 3 3 It is interesting to note the degradation of the signal spectrum with increased symbol rate in case of 2CPFSK and 4CPFSK that implicitly poin
127. s charged and so it is used as the last option here Path priorities can be changed according to our requirements The path with the highest priority is always the primary one the direct radio link in our example and the path with the lowest priority is the last option GPRS in our example Thanks to the Backup routes functionality RipEX can handle various network problems without inter rupting the desired network communication RipEX C Se Backup path 1 9 RipEX A R e Primary path gt RipEX B GPRS network am T Backup path 2 T Fig 12 1 Backup routes functionality example Note The Backup routes functionality can be used in the Router mode only The Backup routes functionality is supported by the SNMP see Chapter 2 SNMP for further details 12 2 Backup Routing Management Protocol BRMP is the proprietary protocol developed by RACOM It handles the Backup routing functionality in RipEX networks with respect to radio network requirements The protocol e does not overload the radio network e enables more than one backup path e deals with a random packet loss and 104 RipEX RACOM s r o Backup routes e enables very fast path switching in cases of network failure The protocol always works between two particular RipEX units Each RipEX network can contain various backup routes and each backup route consists of several alternative paths We can even configure nested backup paths
128. s of a packet received via the serial interface is determined inside the radio modem from the SCADA address depending on the protocol used either using a mask or table see RipEX manual Adv config Protocols The source IP is generated similarly If all devices are connected to RipEX s via serial interface it is helpful to only use the radio IP addresses for translation and routing of data Ethernet IP addresses may be assigned randomly you could keep their defaults however we recommend setting Ethernet addresses similar to radio IP addresses to keep things organised Remote service access over the radio channel is also possible via the IP ad dresses of the radio interface i Rs232 Ul 18 Radio 10 10 10 17 los E Radio 10 10 10 15 4 RS232 00017 RS232 Radio 10 10 10 16 RS232 RS232 Fig 1 1 Network 1 The following paragraph shows routing tables for individual radio modems which enable mutual com munication between all devices All destinations share the mask 255 255 255 255 i e 10 10 10 xx 32 interface Auto or Radio e For 10 10 10 15 Destination via Gateway 101041017 via 10 10 10 06 http www racom eu eng products m ripex h menu html protocols RACOM s r o RipEX O Address planning POs Oe a 9 eee Os OI AG LOO Ol I wis 0 oO eG For 10 10 10 16 DLL bbs pacer PUIID D LOO LO ad Arar OL OV TOV e For 10 10 10 17 I9 T0 us cl Dig to TOLE e For 10 10 10 18
129. selected port of the manager RipEX launches SNMP agent automatically on start up if enabled RipEX also sends alarm states traps to manager from port 162 SNMPTRAP Users can change this port number in RipEX Traps behaviour can be influenced see Alarm management settings RipEX manual Adv config When using SNMP over radio channel we recommend setting RipEX to router mode From the point of radio network SNMP is typically a standalone application sharing the radio channel with others Thus it causes collisions which are automatically resolved by the radio channel protocol in router mode The radio channel uses no protocol in bridge mode meaning two competing applications can only be run at a great risk of collisions and with the knowledge that packets from both applications may be irre trievably lost 2 2 1 Limitations SNMP is primarily designed for Ethernet networks where generally bandwidth capacity is not an issue By contrast radio bandwidth capacity is very limited and RipEX mostly works over the radio channel For this reason special care is recommended while configuring NMS If badly configured NMS can take a significant portion of the network capacity or can even overload the network completely Bandwidth Consumption It is important to realise that the average size of a single request and response to a specific OID is approximately 184 Bytes each The entire MIB for a single RipEX with one neighbouring RipEX is ap
130. ss of the Modbus Master and IP addresses of all Modbus Slaves is necessary Remember to set Modbus TCP RTU and Terminal Servers under Settings Ethernet to Off http www racom eu eng products m ripex h menu html com par http www racom eu eng products m ripex h menu html slave http www racom eu eng products m ripex h menu html modbus 72 RipEX RACOM s r o Modbus TCP RTU ej i Modbus TCP i x F ETH a ETH Modbus TCP Modbus TCP b A Modbus TCP Modbus TCP Fig 8 3 Modbus TCP 8 3 Modbus TCP local TCP IP connection Note Only works in Router mode TCP connection is established only locally between Modbus devices and the connected RipEX units TCP protocol overhead is not transmitted over the Radio channel Secured TCP IP transfer is not ne cessary because in Router mode every packet in the Radio channel is acknowledged on every radio hop A packet is therefore repeated directly in the part of the network where it is lost not across the entire radio network as in TCP IP This improves latency and increases network throughput il 9 Modbus TCP Local TCP connection ETH Modbus TCP E Modbus TCP Local TCP connection Local TCP connection DO S Ec Modbus TCP Local TCP connection Modbus TCP Local TCP connection Fig 8 4 Modbus TCP local Set your Modbus TCP Master to use a single IP to communicate with Modbus TCP Slaves RipEX ethernet IP and set TCP port to 502 Communic
131. stTermServBytes Terminal Server Rx bytes counter Rx 33555 2 3 3 2 1 5 X Terminal Server Tx bytes counter BytesTx 33555 2 3 4 1 stComNumber Number of COM ports 33555 2 3 4 2 stComTable not access current List of COM port entries ible 33555 2 3 4 2 1 stComEntry COM port entry ible 33555 2 3 4 2 1 1 X stComIndex read only current COM COM port index index seee A MU 2 X uL ME E ue ad a Rx packets counter 33555 2 3 4 2 1 3 X stComPackets Tx COM Tx packets counter 33555 2 3 4 2 1 4 X stComBytesRx COM Rx bytes counter RACOM s r o RipEX 41 SNMP 33555 2 3 4 2 1 5 X stComBytes Tx COM Tx bytes counter 33555 2 3 5 1 stTcpProxyNum read only current Number of TCP proxy ports ber 33555 2 3 5 2 stTcpProxy Table current List of TCP proxy port entries ible 33555 2 3 5 2 1 stTcpProxyEntry TCP proxy port entry ible 33555 2 3 5 2 1 1 X stTcpProxyIndex TCP proxy port index 33555 2 3 5 2 1 2 X stTcpProxyPacket read only current TCP proxy Rx packets counter SRx 33555 2 3 5 2 1 3 X stTcpProxyPacket read only current TCP proxy Tx packets counter sTx 33555 2 3 5 2 1 4 X stTcpProxyBytes TCP proxy Rx bytes counter Rx 33555 2 3 5 2 1 5 X st Tcp Proxy jread only current TCP proxy Tx bytes counter BytesTx 33555 2 4 1 5 wvTxLostLast Local station Last Tx lost value in 96 33555 2 4 1 6 wvTxLostAvg read only current Local station Average Tx lost value in hundredths of 96 33555 2
132. ster establishes a local TCP connection to RipEX using Modbus TCP protocol as described in chap 3 A packet is securely sent over the Radio network to RipEX to which the destination Slave is connected by COM port The RipEX translates the packet to Modbus RTU format and sends it to the connected Slave using Modbus RTU protocol ess Cu S hs Modbus RTU ws reuse S ETH Modbus RTU 0I S Modbus TCP Local TCP connection us rows OS o Modbus RTU lii S Modbus RTU Fig 8 5 Modbus TCP RTU To set up RipEX connected to Modbus TCP Master e Select the type of translation from Modbus to RipEX IP address mask or table as described in chapter 3 TA Rip EX RACOM s r o Modbus TCP RTU e Set the UDP interface to COM1 or COM2 depending on the port that the remote RipEX uses to connect to the Slave device To set up RipEX connected to Modbus RTU Slave e As described in chapter 1 set the appropriate COM to Modbus and the Mode of Connected to Slave 8 5 Master Modbus TCP slaves Modbus RTU or Modbus TCP RipEX radio modems enable full featured cooperation between the Master using Modbus TCP and slave devices using Modbus RTU or Modbus TCP within a single network il ay Modbus TCP Local TCP connection us Cu S ETH Modbus RTU tf S Modbus TCP Local TCP connection mis ETH Modbus TCP Modbus RTU Local TCP connection Fig 8 6 Modbus TCP Slave RTU or TCP To set up RipEX connected to M
133. t More importantly a long retransmission time out at the application level is not desirable any more since it keeps the centre from continuing the polling cycle Nevertheless in any case it is beneficial to keep the number of applic ation retransmissions at the lowest setting available i e zero if possible and leave the RipEX network to use the time available for the possible retransmitting To calculate the typical and maximum possible delivery time for different settings please use the cal culator on Racom web pages hitp www racom eu eng products ripex html calculation The parameters discussed above are configured in the Router operating mode menu Kindly see the Help pages for further information Operating mode f Operating mode Router ACK on Retriez Ma 3 RSS threshold dBim 120 Repeat COM Broadcast Off RACOM s r o RipEX 87 ARP Proxy amp VLAN 11 ARP Proxy amp VLAN 11 1 Introduction ARP proxy can be used when RTU s IP addresses behind different RipEX units are for any reason within the same IP subnet typically they do not have routing capabilities VLAN feature is typically used when you need to split the network into several logical parts E g to distinguish between management and payload user data traffic or among different applications traffic e g various RTU technologies Both features can be combined to provide the necessary functionality See the following chapters for a deta
134. ter This layout and settings may be used if you need to operate different parts of the radio network on different frequencies Connection between these two parts is realised by Back2Back connection between two RipEX s hereafter referred to as border RipEX s each of which operates on different frequency 5 1 Back to Back in Bridge mode Ethernet If end devices are connected to RipEX s over Ethernet border RipEX s can be connected with an Ethernet cable IP addresses of all RipEX s as well as connected devices must be within the same LAN Ethernet interfaces must be interconnected for proper function of remote service access COM If end devices are connected to RipEX s over COM interface one any of the two COM port of a border RipEX must be connected to a COM port of the other border RipEX using RS232 crossover cable or null modem Communication parameters of both connected ports must be set to the same values we recommend using the highest available speed Important A Border RipEX s should be interconnected via one COM port only connecting both COM ports would create a loop Limitation If a device is connected to the free COM port of a border RipEX it only sends data to its part of the radio network Data from all other COM ports of other RipEX s throughout the entire network will be delivered to both COM ports of all other RipEX s Fig 5 1 Crosslink serial cable Ethernet COM If end devices are connect to RipEX s both
135. the defined time intervals or you can just wait for the trap to be received 2 4 1 Active Querying This option is the one already mentioned You have a defined item which is updated e g every 10 minutes It means that every 10 minutes Zabbix requests a reply to the SNMP GET message for the specific OID object and it stores these values in the database A trigger can be configured for each item For instance temperature threshold alarm is set to 50 C Whenever Zabbix receives an SNMP RESPONSE message from any monitored host with temperature higher than 50 C an alarm is triggered If the alarm is triggered it is displayed at the Zabbix Dashboard The Alarm will be visible in the Last 20 issues table and you will see which host is having an issue in the Host status table When the temperature falls back into the allowed range the issue will be deleted from the Zabbix dashboard 28 RipEX RACOM s r o SNMP Host Issue Last change Age Info Ack Actions or range 27 Sep 2012 13 20 58 23s No 1 of 1 issue is shown Fig 2 10 Displaying of RipEX trap 2 4 2 SNMP Traps The key aspect of the SNMP are the TRAPS These OID objects are not actively monitored by the Zabbix manager but by the RipEX itself This behaviour is described in the on line help on RipEX web oettings page or in the User manual Chapter 7 3 How to Configure Traps in Zabbix That unfortunately is rather tricky There are several ways how t
136. this topology e RipbEX A 192 168 15 1 24 e RipEX B 192 168 16 1 24 e RipEX C 192 168 17 1 24 Now we need to add the correct routing To make the example simple we will ignore RipEX D and RipEX E in our configuration See the following RipEX A routing settings 3 i gt X Radio modem amp Router Co PIANC COLA Status Values from RIpEX A Wizards Settings Interfaces Routing Radio MAG 00 02 A9 BB 0F AB IP 10 10 10 15 Mask 255 255 255 0 ETH MAC 00 02 A3 BB OB C3 IP 192 168 15 1 Mask 255 205 205 0 Diagnostic Neighbours Routes E Destination Mask Gateway Backup Note Active Modify 192 168 16 0 24 255 255 255 0 10 10 10 16 Off RipEX B v Delete Add Graphs 192 168 17 0 24 209 205 255 0 Backup 1 RipEX C vi Delte Add Ping Add Monitoring Backup LE Alternative paths Maintenance E Mame Seer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Backup 1 192 168 17 1 20 Delete Add E 10 10 10 16 Default wl Indirect link M Add 10 10 10 17 Default Y Direct link Add Add Legend Up Down Unknown Currently used Route for IP Fig 12 10 RipEX A Routing menu example 2 Notice that we are using the Backup routes system for the devices on the 192 168 17 0 24 network Also notice that we filled the Peer IP with the remote RipEX Ethernet IP address The path used currently is the primary indirect one but both paths are Up Note Only the remote RipEX radio or the main Ethernet
137. tion of a Slave radiomodem is very simple as demonstrated in the picture below When a UNI Slave receives the UDP datagram from RF channel it takes the original SCADA message and transmits it over the respective interface the COM2 in our example Protocol Protocol UMI Mode of Connected device Broadcast accept on If the SCADA device connected responds to the message within a timeout of 500 ms the source IP address of the received UDP datagram is used as the destination for the response Note only one packet is accepted as a response When the timeout expires all messages received by the serial in terface are discarded 7 Co RipEX RACOM s r o UNI protocol 9 2 MASTER SLAVE with several Masters The behaviour of Master and Slave is exactly the same as in the previous scenario i e a Slave always responds to the address from which the request was sent If by chance two simultaneous requests from different Masters are received by a slave radiomodem the RipEX radio modem waits for the first reply from the connected SCADA device before transmitting the request which arrived second The 500 ms timeout applies again i e when there is no reply for the first request the second one is trans mitted after the timeout expires 9 3 MASTER MASTER The Master Master communication is possible The translation of addresses is proceeded with every packet incoming to the RipEX radio modem from connected SCADA equipme
138. tion total Rx bytes counter Rx 33555 2 3 1 1 11 stRadio Tot Remote station total Tx bytes counter BytesTx 33555 2 3 1 1 12 stRadioTotlpErr Total radio IP error packets counter 33555 2 3 1 1 13 stRadioTotSub read only current Total radio subheader error packets HeadErr counter 33555 2 3 1 1 14 stRadioTotHead read only current Total radio header error packets Err counter 33555 2 3 1 1 15 stRadioTotFalse read only current Total radio false sync counter Sync 33555 2 3 1 2 stRadioRemNum read only current Number of remote stations ber 33999 2 3 1 3 stRadioRemTable not access current List of remote station entries ible 33555 2 3 1 3 1 stRadioRemEntry Radio remote station entry ible 33555 2 3 1 3 1 6 X stRemBytesTx read read only current Remote station Tx bytes counter t id stRemDuplicates E Remote station duplicate packets counter 33555 2 3 1 3 1 8 X stRemRepeats read only current Remote station repeated packets counter 33555 2 3 1 3 1 9 X stRemLost read read only Remote station lost packets counter 33555 2 3 1 3 1 10 X stRemCtlPackets read current Remote station Rx radio control packets Rx counter 33555 2 3 1 3 1 11 X stHemCtlPacket read only current Remote station Tx radio control packets sTx counter 33555 2 3 1 3 1 12 X stRemDataErr read only current Remote station data error packets counter 33555 2 3 1 3 1 13 X stRemRejected Remote station rejected packets counter 40 R
139. ts out that the assigned bandwidth is not used effectively It can be seen that the significant amount of the signal power is concentrated within the close vicinity of the carrier frequency and thus it results in poor ratio between the occupied signal bandwidth and the noise band width of radio receiver Table 3 1 52 RipEX RACOM s r o Data speed and Modulations Tab 3 1 Measurement results of the transmitter parameters for selected modes of operation Occupied Modulation Symbol Modul ACI Bandwidth Spectrum m m Rate Parameter Lower Upper 99 9 Tx plot H idm Bc d amp c kia IW P EH sp xS tae o easurement DE 2 dB eaa m a afas DEDE IED The measurement values of achievable output power Pous amount of adjacent channel interference ACI and overall transmitter power efficiency nry are collectively given for all the modulation formats in Table 3 1 It can be seen that the ACI limit 60 dBc is maintained for all of these settings however there are two penalties in case of linear modulation schemes that typically have to be paid for higher spectrum efficiency Firstly it is the lower output power level achievable For this specific transmitter architecture it is in particular 35 dBm rr 4 DQPSK D8PSK and 33 dBm 16 DEQAM Secondly itis the lower value of the overall transmitter power efficiency reached Comparing to exponential modes of system operation the efficiency of linear operational modes
140. ue mentioned the reply is sent only from the Master station over Ethernet saving radio bandwidth SNMP uses radio link only for sending SNMP Traps from any Slave to the NMS a SNMP Trap Management za luba isto RIpEX System NMS Station SNMP Reply Radio ETHERNET sea LINK Fig 2 2 NMS communication with Slave stations Note In such a case watched values from neighbouring stations are displayed as part of the Master Repeater station 2 2 2 RipEX SNMP Settings SNMP agent is switched off by default To enable it go to the settings menu and click on the SNMP button You can set the Community turn on SNMP traps and define two trap destination IP addresses and ports Important AN Thresholds for all SNMP traps can be configured in the RipEX web interface Settings Alarm management Since detailed description of RipEX SNMP traps settings can vary based on the current firmware please kindly refer to the online Help accessible through the RipEX web interface or see the User manual Chapter Settings http www ra com eu eng products m ripex h menu htmlZsettings 2 2 3 RipEX Traps Description The trap is sent whenever any of the following watched values are beyond their threshold ranges RACOM s r o RipEX 15 SNMP e RSS Received Signal Strength e DQ Data Quality e TX Lost The probability of a transmitted frame being lost e UCC Power voltage V e
141. ure you want to use T We CAS x of RipexAI m TRipEX B a Temp 32 8 C ee i Temp 31 5 cr ORSS 38 dBm f i RSS 43 dBm S300 207 Ti DQ 223 23 Fig 2 16 Basic map with two RipEX stations A short example of RipEX station configuration in Maps RACOM s r o RipEX 35 Type Host HOSTNAME Temp HOSTNAME wvTempAwvg last 0 Label RSS HOSTNAME wvRemRssAvg 1 last 0 DQ HOSTNAME wvRemDgqAvg 1 last 0 7 Label location Left v Host Ripex A Select Fig 2 17 Definition of RipEX station in maps Each map can be divided into several sub maps It can be useful for various levels of detail You can configure E mail notifications if anything goes wrong with the monitored stations Just go to Administration Media Types and define your SMTP server settings for outgoing messages After that go to Administration Users to define who will be notified Media Description Type SMIP server smtpserver racom eu SMTP helo zabbix racom eu SMTP email zabbix i racom eu Fig 2 18 E mail configuration example 2 5 1 SNMP Builder SNMP Builder is an add on for Zabbix to help users to use SNMP OIDs as items or to browse the entire MIB tree hierarchy Note The SNMP Builder is not supported in Zabbix 2 2 x releases Installation Download the SNMP builder tar gz e Zabbix version 2 0 x https github com atimonin snmpbuilder Within this
142. urrent Remote station i RF power value in tenths of Watt W 33555 2 4 3 1 19 X wvRemRfPwrAvg mdi only current Remote station Mus RF power value in thousandths of Watt W 33555 2 4 3 1 20 X wvRemVswrLast read only current Remote station Last VSWR value from interval 3 25 in tenths 33555 2 4 3 1 21 X wvRemVswrAvg read only current Remote station Average VSWR value from interval 300 2500 in thou sandths 33555 2 5 1 1 alarmThrRssMin Alarm threshold minimum RSS value in dBm RACOM s r o RipEX 43 SNMP 99999 29 1 2 alarmThrRssMax Alarm threshold maximum RSS value in dBm 33555 2 5 1 3 alarmThrDaMin Alarm threshold minimum DQ value 33555 2 5 1 4 alarmThrDqMax Alarm threshold maximum DQ value 33555 2 5 1 9 alarmThrTxLost read only current Alarm threshold minimum Tx lost Min value in 9o 33555 2 5 1 10 alarmThrTxLost read only current Alarm threshold maximum Tx lost Max value in 9o 33555 2 5 1 11 alarmThrUccMin read only current Alarm threshold minimum UCC value in tenths of Volt V V 99000 2 0 1612 alarmThrUccMax read only current Alarm threshold maximum UCC value in tenths of Volt V 99999 2 9 1213 alarmThrTempMin read only j current Alarm threshold minimum device temperature value in tenths of Celsius C 33555 2 5 1 14 alarmThrTemp read only current Alarm threshold maximum device Max temperature value in tenths
143. usandths of Volt V 33555 2 10 7 trpTemp current A notification to indicate that average device temperature value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateTemp Device temperature alarm state wvTempAvg Local station Average device temperature value in thousandths of Celsius C 33555 2 10 8 troRfPwr current A notification to indicate that average RF power value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateRfPwr RF power alarm state wvRfPwrAvg Local station Average RF power value in thousandths of Watt W 33555 2 10 9 troVswr current A notification to indicate that average VSWR value has exceeded threshold limits This notification sends additional information about the event by including the following objects in its varbinding list alarmStateVswr VSWR alarm state wvVswrAvg Local station Aver 46 RipEX RACOM s r o SNMP age VSWR value from interval lt 300 2500 gt in thousandths 33555 2 10 10 troEthPr current A notification to indicate that average ETH interface Rx to Tx packets ratio value has exceeded threshold limits This notification sends additional inform ation about the event by including the following objects in its varbinding list
144. ware release 1 3 2 1 2 SNMP communication In SNMP each value is uniquely identified using Object Identifier OID Standard communication starts by sending a request and then the response is returned Alternatively an agent can send an SNMP trap Peer SNMP GET Request ee SNMP Response 4 amp SNMP TRAP Fig 2 1 SNMP Communication 12 RipEX RACOM s r o SNMP A request is sent the manager sets message type to GET includes OID for the required value and sets this value to NULL A response is returned the agent sets message type to RESPONSE and sends the requested value along with its OID back to the manager A trap is sent to the manager without its request Basic Message Types GetRequest returns a single value GetNextRequest returns the next value using the next OID GetBulkRequest returns several values in a single packet for example temperature voltage number of transmitted messages or bytes per second etc Trap sent from the agent to the manager whenever any monitored value is beyond its thresholds SetRequest used to set various parameters unsupported by RipEX 2 1 3 MIB database Management Information Base The MIB is a virtual database used for managing the entities in a communications network The MIB hierarchy can be depicted as a tree with a nameless root the levels of which are assigned by different organizations Higher level MIB OIDs belong to differ
145. warning critical We also provide several triggers within the templates Triggers defined in templates cannot be edited within individual hosts which means you cannot define various threshold ranges for hosts and each host would have the same threshold range Please define your own triggers within each individual host Note Oo You can use a Clone option to create a copy of any template item or trigger for an individual host In this case you can edit its predefined values to meet your requirements for each host separately Graphs are automatically created for each monitored numeric value but you can also create special graphs with several values on a single graph We provide 5 predefined graphs containing some basic watched values like temperature UCC etc For more information see the Zabbix documentation You can delete add or edit any template com ponent The predefined state serves as a quick start but you do not have to use them at all and you can create your own set of monitored values items Which Values Items Should Monitor The templates themselves are fully scalable and consist of many items However monitoring all of them is not required in a routine situation Pre activated items in RipEX default templates are e RipEX Template o Pre activated Items 7 o Default Update Time 30 minutes m Local Station e Modem temperature C RF power W TX lost 9o UCC V VSWR m Remote Station e DQ RSS dBm e
146. witch to its backup radio path You can check this functionality using the same tools as in the previous examples 12 4 Summary We have described just a few basic examples of Backup routes usage Feel free to download the RipEX User manual from http www racom eu download hw ripex free eng ripex m en pdf or the Application notes from http www racom eu download hw ripex free eng ripex app en pdf to conduct further tests Do not hesitate to contact us if you have any questions RACOM technical support team E mail lt support racom eu gt Tel 420 565 659 511 RACOM s r o RipEX 117 Revision History Appendix A Revision History Revision 1 1 2011 09 02 First issue Revision 1 2 2012 01 31 New chapter UNI protocol Revision 1 3 2012 11 13 Modified and extended chapter Chapter 2 SNMP Revision 1 4 2013 04 20 New chapter Chapter 11 ARP Proxy amp VLAN Revision 1 5 2013 04 30 New chapter Chapter 12 Backup routes 118 RipEX RACOM s r o
147. x front end You need to create the value mappings for all OID objects of this kind manually The value mapping is not exported within the RipEX template Create the value mappings before importing the RipEX template Otherwise you will need to link all value mappings with the appropriate items manually Remember that since Zabbix version 2 2 1 itis mandatory to create the value mappings before importing the templates Note This syntax feature is used throughout all MIB tables not only the RipEX MIB table To add new value mappings go to Administration General Value Mapping Click on the Create value map button and insert the values which are mentioned on the following lines There is an Item list which uses these value mappings either link them manually or automatically by importing the template Note There are also several value mappings used at RFC1213 and RS232 Value Mappings List RipEX AlmState Items 1 unknown Alarm state COM1 interface Rx to Tx packets ratio 0 gt inactive Alarm state COM2 interface Rx to Tx packets ratio 1 active Alarm state Device temperature Alarm state DQ Alarm state ETH interface Rx to Tx packets ratio Alarm state HW Input Alarm state RF Power Alarm state RSS Alarm state Tx lost Alarm state UCC Alarm state Unit ready Alarm state VSWR 22 RipEX RACOM s r o RipEX BackupPathsState 0 unknown 1 up 2 down RipE
148. y similar routes Destination 192 168 2 251 32 Mask 255 255 255 255 Gateway 10 10 10 2 Destination 192 168 2 1 32 Mask 255 255 255 255 Gateway 10 10 10 2 Do not forget to activate both routes You can also add a note to each route See the RipEX A Routing example 92 RipEX RACOM s r o ARP Proxy amp VLAN 3 i gt XxX Radio modem amp Router Co 2 NCCOONA Status Wizards Settings Interfaces Routing Radio MAC 00 02 A9 BB 0F AB IP 10 10 10 2 Mask 255 255 255 0 3 ETH MAC 00 02 AS BB O0B C3 IP 182 168 2251 Mask 255 255 255 0 Diagnostic Neighbours Routes T e Destination Mask Gateway Backup Note Active Modify Ist 192 168 2 252 32 255 255 255 255 10 10 10 4 Off RipEX C ETH v Y Delete Add Graphs 192 168 2 2 32 255 255 255 255 10 10 10 4 Off PC42 Delete Add Ping Add Monitoring Backup paths E Alternative paths Maintenance Hame Peer IP Hysteresis SNMP Trap Gateway Policy Active Note Modify Add Legend Good Failure Unknown Currently used Route for IP Fig 11 5 RipEX A Routing Computer Configuration When we have successfully configured both RipEX units we can proceed with computers settings PC 1 IP address 192 168 2 1 Mask 255 255 255 0 Default Gateway 192 168 2 251 PC 2 IP address 192 168 2 2 Mask 255 255 255 0 Default Gateway 192 168 2 252 Note If you do not know how to configure these computers see the RipEX manual http www ra com eu eng products m

Download Pdf Manuals

Related Search

Related Contents

ES MANUAL DE INSTRUCCIONES  SmartLCD™ Technical Manual      Coragen en serre pour lutter contre la fausse arpenteuse du chou  3 - Panasonic Canada  Samsung GT-I9000 User Manual  User Manual  Guida per l`utente  Ford Power Stroke Diesel No-start Diagnosis  

Copyright © All rights reserved. Failed to retrieve file