RACOM PROFI MR400 Specifications

.RipEXApplication notes.version 1.21/31/2012fw 1.0.9.0www.racom.euRACOMs.r.o. •Mirova1283•59231NoveMestonaMorave•CzechRepublicTel.:+420565659511•Fax:+

MSSSSSSS10.10.1.6/24192.168.2.62/2410.10.1.3/24192.168.2.254/2410.10.1.8/24192.168.3.62/2410.10.1.5/24192.168.1.62/2410.10.1.2/24192.168.1.254/24EthEt

MSSSSSSS10.10.1.6/24192.168.2.62/2910.10.1.3/24192.168.2.254/2610.10.1.8/24192.168.3.62/2910.10.1.5/24192.168.1.62/2910.10.1.2/24192.168.1.254/26EthEt

2. SNMP for RACOM RipEX2.1. Simple Network Management ProtocolSNMP is a simple, widespread and useful standardised protocol used to read values from d

2.1.3. MIB database – Management Information BaseOID, which uniquely identifies every value in SNMP, is formed by a sequence of numbers divided bypoin

2.2.1. RipEX MIBName OIDripex 1.3.6.1.4.1.33555.2station 1.3.6.1.4.1.33555.2.1device 1.3.6.1.4.1.33555.2.1.1stationName 1.3.6.1.4.1.33555.2.1.1.1 Name

stRemBytesTX 1.3.6.1.4.1.33555.2.3.1.3.1.6 Remote station TX bytes counter.stRemDuplicates 1.3.6.1.4.1.33555.2.3.1.3.1.7 Remote station duplicate pack

RipEX SNMP TrapsSNMP Trapsripextraps 1.3.6.1.4.1.33555.2.10trpRss 1.3.6.1.4.1.33555.2.10.1 RSS of remote station is out of range.trpDq 1.3.6.1.4.1.335

2.2.4. Example of Zenoss settings for RipEXThese examples merely illustrate certain Zenoss settings. Refer to Zenoss manual for more information.If yo

Fig. 2.3: Setting SNMP Manager parameters in ZenossOther parameters, such as SNMP Performance Cycle Interval (secs) use the Edit command in Ad-vanced

Fig. 2.5: Template for RipEX in ZenossThe individual OIDs can be grouped in graphs which depict the changes of monitored values over time.Thresholds c

Fig. 2.7: Displaying graphs for a specific device in ZenossZenoss also allows you to display current, average and maximum values in graphs.RipEX Appli

3. Data speed and ModulationsOn efficient use of narrowband radio channelIntroductionThe industrial narrowband land mobile radio (LMR) devices, as con

to the extreme adjacent channel transmitted power (ACP) attenuation requirements, and inherent ro-bustness against channel nonlinearities. Relatively

In the systems, where the transmitter power efficiency is of high importance, the transmitter nonlinearityalso creates an important issue. Generally s

Fig. 3.3: Modulated signal spectrums. (left) π/4-DQPSK with R=17.3 kBaud, (right) 16-DEQAM withR=17.3 kBaud.As for the linear modulation techniques, t

Tab. 3.1: Measurement results of the transmitter parameters for selected modes of operation.SpectrumplotηTXPINOccupiedBandwidth@ 99.9%ACILower UpperPo

Assigning this value as S, one can also express what signal-to-noise ratio (SNR) can be expected inrelation to noise figure (NF) and transformed to th

Fig. 3.5: Maximum usable sensitivity measurement results. Channel separation 25 kHz.3.2.2. Efficient use of narrowband radio channelAs it has been wri

Tab. 3.2: Overall performance characteristics of the narrowband radio transceiver for selectedmodes of operation.SystemGainAvailableOutputPowerDataSen

• For applications where higher data throughputs are needed the additional increase in spectrum ef-ficiency can be gained by D8PSK and 16-DEQAM modula

Table of Contents1. Address planing ...

4. AutospeedNormally all radio modems in a network have to transmit with the same data rate on the same radiochannel. The Autospeed feature of RipEX e

to four times) of the whole network, quite probably making it unusable for the application. RipEX Auto-speed feature allows to change the transmission

5. Back-to-Back repeaterThis layout and settings may be used if you need to operate different parts of the radio network ondifferent frequencies. Conn

SSf1SBack2Backf2f2f1EthIP:192.168.10.254EthIP:192.168.10.1EthIP:192.168.10.3EthIP:192.168.10.2EthIP:192.168.10.4SEthIP:192.168.10.100Mask:

6. Combining MORSE and RipEX networksWhen expanding a MORSE network with RipEX radio modems, different arrangements are possible.In the following para

If the Master is located on the side of the MRxxx, the border MRxxx should be set to Slave. Dependingon the SCC interface used the MRxxx should use Mu

6.2.2. Terminal devices connected to COMA MORSE network can only be expanded with RipEX modems if the application protocol is supportedboth by MORSE a

7. ProfibusRadio modem RipEX supports the most widely spread Profibus (Process Field Bus) type designatedProfibus DP (Decentralized Periphery) type 0

7.2. Profibus settingsWe will only be looking at the basic communication parameters of the protocol – other parameterscorrespond to the standard Profi

DP slave properties window opens. Click on the PROFIBUS button:Properties – PROFIBUS window opens. Select the Transmission Rate (19.2 Kbps or 9.6 Kbps

4

PROFIBUS_DP is the most important settings window; fill in settings as shown below, click Recalculateand confirm by clicking OK. Confirm the values in

Fig. 7.2: ACK OffRouter mode should only be used where network topologydoes not allow for Bridge mode to be used (see page YY ofthe manual). If you ch

7.4.2. Router mode - timingRouter mode web based settings may cause time problems in more complex networks. CLI lets youadjust radio channel access pa

8. Modbus TCP/RTUUse of Modbus in RipEX.RipEX supports Modbus RTU, Modbus TCP as well as their combinations:Tab. 8.1:Available withOperating modeRadio

In Router mode, set the COM port of your Master RipEX to Modbus (Mode of Connected device). Totranslate Modbus addresses to RipEX format and vice vers

ETHModbusTCPMETHModbusTCPSETHModbusTCPSETHModbusTCPSETHModbusTCPSFig. 8.3: Modbus TCP8.3. Modbus TCP, local TCP/IP connectionNote - Only works in

• Set Modbus TCP/RTU to On. Type the port number on which the connected Modbus TCP Masterinitiates communication, by default 504, into “My TCP Port” f

• Select the type of translation from Modbus to RipEX IP address (mask or table), as described inchapter 3.• Set the UDP interface to COM1 or COM2 dep

A Slave with Modbus RTU protocol may simultaneously communicate with masters using Modbus TCPand Modbus RTU. The network will deliver responses only t

9. UNI protocolUNI is the "Universal" protocol utility designed by RACOM. It is not a new SCADA protocol, it can actuallyprocess different p

1. Address planingIn Router mode standard IP routing is used between individual RipEX radio modems and their interfaces.The only non-standard feature

The 5th byte from the incoming message from SCADA centre is used to replace the last byte of theBase IP and the resulting IP address is used as the de

9.2. MASTER – SLAVE with several MastersThe behaviour of Master and Slave is exactly the same as in the previous scenario, i.e. a Slave alwaysresponds

Note that, similarly to the MASTER-MASTER mode, the Poll Response Control at the Master RipEXhas to be set to Off.RipEX Application notes – © RACOM s.

10. Channel accessMethod of accessing the radio channel may significantly affect the overall reliability of packet transmis-sion. Even in a simple pol

10.2. Bridge modeIn Bridge mode, a packet is transmitted to the radio channel immediately, without any checkingwhether the radio channel is occupied o

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 PacketA, R

10.2.2. Time division of responses in Bridge modeThere is also the Tx delay setting in the menu. It shall be used in Bridge mode if multiple RTUs conn

- time needed for the packet transmissiont [ms]- number of bytes transmitted (consider the longest possiblereply from RTU)n [ - ]- Modulation rateb [k

10.4. Router Mode10.4.1. Channel access in Router modeThe protocol in the radio channel in the Router mode of RipEX uses several methods to prevent an

generates messages to non-existent or switched-off remotes (for any reason). When a remote site iswithout power (including the RipEX) and the centre c

10.10.10.18 via 10.10.10.1610.10.10.19 via 10.10.10.16• For 10.10.10.1610.10.10.18 via 10.10.10.1710.10.10.19 via 10.10.10.17• For 10.10.10.1710.10.10

Appendix A. Revision History2011-09-02Revision 1.1First issue2012-01-31Revision 1.2New chapter – UNI protocolRipEX Application notes – © RACOM s.r.o.6

If SCADA device addresses can be chosen arbitrarily, routing can be significantly simplified when radioIP addresses can be grouped to subnets accordin

Destination via Gateway10.10.10.1/29 via 10.10.10.210.10.10.8/29 via 10.10.10.910.10.10.16/29 via 10.10.10.17• For 10.10.10.210.10.10.8/29 via 10.10.1

There are no limitations to setting up routing in this case. The only rule is that the range of radioand Ethernet IP addresses must not overlap.B. If