The Fastest Radio Modems
RipEX
Key features
RipEX2 is the only fully CE & FCC certified 256 QAM radio modem on the market.
Network throughput is the only valid parameter for performance as seen by the user: how many packets/bytes of payload data were successfully delivered in a given time period.
Never rely solely on Gross data rate typically listed in data sheets.
Channel size | Gross data rate | Possible Network throughput | ||||
RipEX | RipEX2 | RipEX2e | RipEX | RipEX2 | RipEX2e | |
6.25 kHz | 21 kb/s | 35 kb/s | 26 kb/s | > 25 kb/s | > 42 kb/s | > 32 kb/s |
12.5 kHz | 42 kb/s | 83 kb/s | 63 kb/s | > 50 kb/s | > 100 kb/s | > 75 kb/s |
25 kHz | 83 kb/s | 167 kb/s | 125 kb/s | > 100 kb/s | > 200 kb/s | > 150 kb/s |
50 kHz | 167 kb/s | 333 kb/s | 250 kb/s | > 200 kb/s | > 400 kb/s | > 300 kb/s |
100 kHz | – | 555 kb/s | – | – | > 700 kb/s | – |
150 kHz | – | 925 kb/s | – | – | > 1.1 Mb/s | – |
200 kHz | – | 1.1 Mb/s | – | – | > 1.4 Mb/s | – |
250 kHz (*) | – | 1.3 Mb/s | – | – | > 1.7 Mb/s | – |
300 kHz (*) | – | 1.7 Mb/s | – | – | > 2.1 Mb/s | – |
(*) Available only in Bridge mode
Network throughput is achieved by:
- Gross data rate
- Min. Rx/Tx switching and synchronization times
- Optimum Radio protocol for given application
- Data compression
- Payload data are always compressed (Zlib, LZ77 decimation and Huffman coding) and compared with original packet size. The smaller packet is then transferred.
- Ethernet / IP / TCP / UDP header compression
- Terminal server, TCP proxy (RipEX)
- Eliminates TCP overhead transfer over-the-air
- Info sheet
- Single frequency or Dual frequency with different channels for Rx and Tx operation
- Half duplex (RipEX, RipEX2, RipEX2e)
- Full duplex (RipEX2)
- Different Modulation (Data speed), FEC and Retries are possible to set for individual radio links from each unit
- Receiver is automatically adjusted to the data rate of the incoming frame
Stream mode (RipEX)
- Transmitting starts immediately on the Radio channel, without waiting for the end of the received frame on COM => zero latency
Calculate RipEX network performance
Application note – Data speed
Network throughput is achieved by:
- Gross data rate
- Min. Rx/Tx switching and synchronization times
- Optimum Radio protocol for given application
- Data compression
- Payload data are always compressed (Zlib, LZ77 decimation and Huffman coding) and compared with original packet size. The smaller packet is then transferred.
- Ethernet / IP / TCP / UDP header compression
- Terminal server, TCP proxy (RipEX)
- Eliminates TCP overhead transfer over-the-air
- Info sheet
- Single frequency or Dual frequency with different channels for Rx and Tx operation
- Half duplex (RipEX, RipEX2, RipEX2e)
- Full duplex (RipEX2)
- Different Modulation (Data speed), FEC and Retries are possible to set for individual radio links from each unit
- Receiver is automatically adjusted to the data rate of the incoming frame
Stream mode (RipEX)
- Transmitting starts immediately on the Radio channel, without waiting for the end of the received frame on COM => zero latency
Calculate RipEX network performance
Application note – Data speed
Device
RipEX2, RipEX2e
- Open casing tamper detection, FIPS 140-2 security level 2
- HW alarm input – can be connected to cabinet door
- Digitally signed FW
- Data integrity – FW is encrypted with a symmetric cypher unique to each FW version
- Data authenticity – symmetric cypher is digitally signed by an asymmetric cypher whose Private key is in the RACOM vault and Public key is part of the FW
- Secured FW upgrade
- Secure boot
- Device fully boots only when either HW or FW are not tampered
- Physical port disable
- Each physical interface (ETH’s, COM’s, USB, SFP…) can be individually enabled / disabled
RipEX
- HW alarm input – can be connected to cabinet door
- Secured FW upgrade
- Secure boot
- Device fully boots only when FW is not tampered
- Physical port disable
- Each physical interface (ETH, COM’s, USB…) can be individually enabled / disabled
- HTTPS
- Web interface
- API interface (RipEX2, RipEX2e)
- SSL (X.509) certificate
- Own SSL certificate
- SSH
- Command Line Interface (SSH, RipEX)
- Fast remote access
- Logical port disable
- Each Logical port (HTTPS, SSH, SNMP…) or Virtual interface (Terminal server…) can be individually enabled / disabled
- SNMP v3
Access Control
RipEX2, RipEX2e
- Role-based access control (RBAC)
- 4 levels
- Guest – read only
- Tech – configuration excluding security
- Sectech – Tech + security
- Admin – full access
-
Maximum number of user accounts (all levels together) is one hundred
- 4 levels
- Password management
- Failed login alert
- Complexity (configurable)
- Timeout of inactivity (configurable)
- Lockout (after each failed attempt, the time for the next possible login is gradually extended up to 15 min.)
- RADIUS
- 802.1x
- Continuous improvement, no backdoor
RipEX
- Role-based access control (RBAC)
- 2 levels
- Guest – read only
- Admin – full access
- 2 users per level
- 2 levels
Data Security
- Radio channel
- AES256-CCM encryption
- Either own or randomly generated cryptographic key
RipEX2, RipEX2e
-
- Meets NIST SP 800-38C, RFC 6655
- Replay attack protection (25B control block: 13B nonce + 12B tag)
- Automated key management system
- IPsec
- Encrypted end-to-end tunnel
- Mutual network-level peer authentication
- Data-origin authentication
- Reply protection against tampering
- Data integrity control (e.g. MD5, SHA 1, 256, 384, 512)
- Data encryption (e.g. 3DES, AES128, 192, 256)
- Forward secrecy (PFS) Diffie-Hellman groups e.g.:
- Regular Groups – modp1024, modp1536, modp2048, modp3072
- NIST Elliptic Curve Groups ecp192, ecp224, ecp256, ecp384, ecp512
- Brainpool Elliptic Curve Groups ecp224bp, ecp256bp, ecp384bp, ecp512bp
- Elliptic Curves X25519, X448
- Periodic cryptographic keys exchange (IKEv1, IKEv2)
- Application note
- OpenVPN (RipEX2, RipEX2e)
- Encrypted end-to-end tunnel suitable for point-to-multipoint scenarios (i.e. one server and multiple clients)
- Each unit can serve as OpenVPN server(s) or OpenVPN client(s)
- One RipEX2 unit can interconnect up to 30 OpenVPN clients
- Authentication based on certificates and keys
- Data integrity control (e.g., SHA256, SHA512, RSA-SHA512, MD5…)
- Data encryption (e.g., AES-256-CBC, AES-128-GCM, ARIA, CAMELLIA, CHACHA20…)
- Data compression (LZO, LZ4, LZ4v2 – on/off, asymetric mode)
- Enhanced TLS protection (TLS Auth, TLS Crypt), MKA – Multiple Key Algorithms
- Supports either routed mode (TUN, Layer3) or bridged mode (TAP, Layer2)
- Failover peer selection
- Application note
Credentials (Keys and certificates)
- Independent from unit configuration
- Saved in separate file
- Independent update
- Can be generated directly in the unit using high-entropy random number generators
- Uploading a customer-supplied key
- Used by
-
- Radio channel encryption (AES256)
- IPsec tunnel
- Remote access authentication
- Web server authentication
- FW distribution authentication
- Fully featured standard stateful Linux firewall
- Layer 2 – MAC, Layer 3 – IP, Layer 4 – TCP/UDP
- All unwanted traffic is blocked at the network boundary
Device
- 3 years warranty standard, optionally longer
- Mean Time Between Failure (MTBF) > 100 years
- Approved for Hazardous locations
- Electrical power substation hardened
- Vibration and shock resistant
- Seismic qualification
-
Conformal coating of PCBs for Harsh environment
- Industrial hardened design
- Units tested in a climatic chamber(-40 / +70 °C ) and in real traffic
- Rugged die-cast aluminum case
- Heavy-duty industrial components
- Components sourced exclusively from manufactures / authorized dealers
- No adjustable components, No moving parts…
- RipEX-HS Master Station (RipEX2, RipEX)
- Hot standby, 1+1 redundant
- Fully monitored
- Automatic failover
- Hot swappable
- Suitable for Central sites, Repeaters or Important remotes where single point of failure is not accepted
- Private radio frequency
- Licensed => Predictability, Non-shared operation
- Guaranteed capacity and Quality of Service
- Fully under the user’s control
- FEC, Interleaving, Proprietary data compression
- CRC32 data integrity control
- Proprietary protocol with packet acknowledgement
- Backup routes
- Automatic failover to an alternative path
- Alternative path(s) can be on Radio channel or Cellular or any IP network
- Hybrid networks
- Radio and Cellular technologies (or any IP network) are interconnected within one network and utilize the best characteristics of each
- One technology can be used as back up for the other one
VIBRATION AND SHOCK TEST
RipEX is a native IP router, i.e. each individual interface like Radio, ETH‘s and Cellular have their own IP addresses and Masks, while COM ports are routed in the standard way – messages to them can be delivered to an IP address of any interface as UDP datagrams with the selected UDP port numbers.
- Transparent protocol on the Radio channel
- Packets received on any interface (ETH, COM) are broadcast to the respective interfaces on all units in the network. Packets received on COM are broadcast to all COM’s at all remote sites, allowing you to connect more RTU’s to each remote unit.
- Flexible or Base driven protocol on Radio channel
- Packets are addressed, routed and acknowledged
- Each interface (Radio, Cellular, Ethernet…) has its own IP/Mask
- All IP packets are processed according to the Routing table
- It is possible to set Metric for each route (RipEX2, RipEX2e)
- Standard IP routing even on Radio channel
- Mesh network over-the-air
- Direct peer-to-peer communication
- Routing tables are not needed at all
- RipEX2 and RipEX2e are the only radio modems on the market which offer IP based full-featured Dynamic routing optimized for narrowband Radio channel
- See details
- RipEX2 and RipEX2e Ethernet ports can be combined as one or more Switch(es) with routing capabilities among them
- Multiple Ethernet subnets (aliases) identified by its IP address & mask can be defined within each Ethernet interface
- 802.1Q
- ‘Unlimited‘ number of VLAN (1-4096)
- Any number of VLANs can be assigned to Subnets
- RipEX management can be done over separate VLAN
- Application note
- 5 independent sessions
- Encapsulates serial protocol to TCP (UDP) and vice versa
- Eliminates a transfer of TCP overhead over-the-air
- Suitable for IP and serial RTU’s combination within one network
- Non encrypted end-to-end tunnel
- Encapsulates any network layer protocol inside virtual point-to-point link
- Application note
- Both NTP server and NTP client
- NTP server may be synchronized from internal GPS
- Source and destination (IP/Mask/Port) translation supported
- Suitable for cases, when all RTU’s in network have got the same IP address
- Application note
TCP proxy (RipEX)
- Converts TCP into UDP and vice versa
- TCP run only locally between connected device and RipEX on LAN
- Only payload (user) data are transferred over-the-air, i.e. less traffic on Radio channel, no more problems with TCP timeouts
ARP proxy (RipEX)
- RipEX can mimic any IP address (typically RTU behind the Radio channel)
- Suitable in case when RTU’s in the network are without routing capabilities (the default gateway cannot be configured) and they are within the same subnet.
In the case of RipEX2 and RipEX2e, GRE tunnel can be used in this situation instead of an ARP proxy - Application note
- Prioritize critical traffic (SCADA) over lower priority applications (management)
- Packet prioritization on Radio interface
- 8 priority levels available
- Priority assignment based on protocol (TCP, UDP…) and source and destination (IP/Mask/Port)
- 802.1p and DiffServ (DSCP) supported
- Suitable for prioritization of different applications and/or management connected via any interface (COM’s, Ethernet)
- Guaranteed bandwidth for critical traffic, maximum application performance, adhere to Service Level Agreements (SLAs)
- Application note
Unique options
Radio protocols
Protocol on the Radio channel is the most critical part for Network throughput. It manages how radio modems access a Radio channel to transmit data, guarantees the packet deliveries and eliminates packet collisions.
Different applications have different requirements for
- Collision management
- Latency
- Response time and jitter
- Communication topology
Only one protocol on Radio channel is not enough!
RipEX provides three different protocols which are optimized for different applications, from legacy serial to modern TCP/IP such as IEC104, making the network reliable and stable, even with a high number of RTU’s.
Transparent | Flexible | Base driven | |
Topology | Any | Tree | Star |
Repeaters | 1-2 possible | Unlimited | One on each link |
Device mode | Bridge | Router | Router |
Application | Master-slave | Any | Any, TCP/IP optimized |
Base stations | Available | Available | Dedicated |
Collisions | Unmanaged | Managed | Impossible |
Packet acknowledgement | No | Yes | Yes |
The physical layer of radio protocols in RipEX2 and RipEX2e is fully compatible and the units can be combined in one network on the same frequency. RipEX is not compatible with them and must be operated on a separate frequency.
- Star topology, repeaters supported
- Fully transparent
- No collision avoidance capability (collisions are unmanaged)
- All messages received from user interfaces are immediately broadcast to the Radio channel, without any checking or processing => minimum latency
- Suitable for master-slave polling applications
TRANSPARENT
- Star topology, repeaters supported
- Up to 255 remotes under one Base station
- Standard IP routing, either Static or Dynamic
- All traffic is fully managed by Base station
- Non-collision protocol on Radio channel (never any collisions in the network)
- Radio channel access is granted by a proprietary deterministic algorithm
- High reliability – each packet can be transferred as an acknowledged unicast
- More than 90% of Radio channel capacity dedicated for user data
- Optimized for TCP/IP, especially for IEC104
- Stable response times with minimum jitter
- Fair distribution of channel capacity among all remotes
- Suitable also for collision networks when a remote is not be heard by other remotes and/or different Rx and Tx frequencies are used
- RipEX2e can be used only as Remote; RipEX2 and RipEX as both, Remote and Base station
- Info sheet
- Application note – Base driven protocol
- Application note – Address planning
BASE DRIVEN
- Unlimited Tree topology with many repeaters and branches
- Standard IP routing, either Static or Dynamic
- No extra base stations
- Any unit simultaneously a repeater
- Unlimited number of repeaters
- Unlimited peer-to-peer communication (Full Mesh Topology) – any unit can directly communicate with any other
- Anti-collision protocol – collisions are managed
- Sophisticated Radio channel access – proprietary combination of LBT, CSMA/CD and slotted ALOHA
- High reliability – each packet can be transferred as an acknowledged unicast
- Suitable for (multi) polling and report by exception concurrently applications
- Info sheet
- Application note – Address planning
- Application note – Radio channel access
FLEXIBLE
SCADA protocols
Serial
Special SW drivers map serial SCADA protocol addresses to RipEX IP addresses and reduce the data amount which are transferred over-the-air.
RipEX2, RipEX2e, RipEX
- Modbus, IEC101, DNP3, PR2000, Comli, DF1, Async Link, PPP, Siemens 3964(R), SAIA S-BUS, UNI, MARS-A, RDS, Transparent
- Application note – Modbus
- Application note – UNI
RipEX only
- C24, RP570, Slip, Cactus, Profibus
- Application note – Profibus
Ethernet
- TCP(UDP) protocols (e.g. IEC104, DNP3/TCP, etc.) can be handled transparently or using Terminal server or TCP proxy (RipEX)
- Embedded Modbus RTU / Modbus TCP converter
Dynamic routing
RipEX2, RipEX2e
- Routing tables are not needed at all
- On/Off for each individual interface (Radio, Cellular, ETH’s) and VLAN
- Each device distributes information to its neighbors to which networks it can route, and based on this, a next gateway is dynamically selected
- When more next gateways exist, the one with the best metric is selected
- The next packet to the same destination can be routed via different gateway than the previous one
- Three standard Dynamic IP routing protocols are implemented:
- BGP
- OSPF
- Babel
- OSPF based
- Different algorithms for wired and wireless interfaces
- Minimum overhead
- Optimized for narrowband Radio channel
- Application note
RipEX
- Automatic routing established between Nomadic Centre and Remotes
- Any existing static unit can be configured as Nomadic Base station
- Nomadic Remotes automatically connect to the best available Base station
- Network expansion – without changes in Routing tables
- Portability – Nomadic Remotes can be transferred from one Base to the other one
- Application note
Backup routes
Backup routes feature significantly increases network reliability by automatically switching to an alternative path in the case of a failure. Alternative paths can be fully or partially on Radio channel or Cellular or any IP network.
BACKUP ROUTES
RipEX2, RipEX2e
-
- Automatic switchover between main and backup link
- Several backup links with priorities
- Routing rules are static
- Widely configurable automatic contol of backup links functionality (Test period, Repeat period, Reply timeout, Passes, Retries…)
- Automatic switch back to the higher priority link once it is restored
- IPsec tunnels can be bound to particular links via Peer ID parameter so they are also swapped respectively
-
- Dynamic alternative routing paths between any two IP devices (RipEX, Cisco, …)
- Dynamic routing is used
- Application note
RipEX
- Alternative paths are static and always between two RipEX IP addresses, even behind a repeater(s) or IP network
- Automatic failover is based on packet losses or weak RSS
- Continuously tested, i.e. failover only to functioning backup
- Unlimited number
- Priority assignment
- Application note
Radio and Cellular technologies (or any IP network) interconnected within one network and utilize the best characteristics of each.
- RipEX Radio modems + M!DGE Cellular routers
- RipEX2 with mPCI extension Cellular module enables one box solution
- Critical data on Radio part, large data or not so important sites on Cellular part
- Takes advantage of the benefits of both technologies
- One technology can be used as backup for the other one
- Standard units used – No additional hardware required
- Same SW protocol drivers and logic on all interfaces of all devices
- One network interface for application – central RipEX manages the routing
- Common SNMP management
- High levels of Security and Flexibility
- Info sheet
Network characteristics | |
Radio | Cellular |
Private network – completely under user’s control | Public network – 3rd party dependency Make use of existing infrastructure |
Single user – guaranteed capacity and behaviour | Multi users can affect capacity and behaviour |
Licensed frequency – guaranteed quality of service | Public networks – quality of service not guaranteed |
Higher investment, guaranteed running fees paid to government | Lower investment, unpredictable running fees paid to private company |
Mission critical real-time applications | Non-mission critical applications |
HYBRID NETWORKS
Migration solution is used in case of legacy radio network modernization or when simultaneous use of two radio networks is required.
Customer benefits
- Standard RipEX units used – no expensive temporary migration HW required
- No network outage during migration
- No time limits for legacy and new RipEX networks co-existence
- Migration as part of regular maintenance
- Gradual one by one replacement
Technical features
- No changes to legacy network required
- The same frequency for legacy and the new RipEX radio network can be used
- The same antenna for legacy unit and the new RipEX radio can be used
- Automatic Antenna Switch automatically manages antenna switching
- HW contact for ‘Carrier On’ legacy base station transmissions supported
- RipEX routing table manages traffic for legacy and new network
- Reduced traffic load on legacy network offers improved performance
- SCADA central SW and RTU’s can also be migrated, gradually and independently of each other or simultaneously. The new SCADA can be used simultaneously with the legacy one on another RipEX interface e.g. Ethernet.
- Application note
MIGRATION SOLUTION
TUTORIAL VIDEO
- RipEX2 only
- Transparent L2 Bridge
- Up to 1.7 Mb/s / 300 kHz in both directions simultaneously
- Minimal latency
- Long distances (5-50 km) when Line of sight is not required
- Frequency pair to be used
- Either external or internal duplexer
- All RipEX2 features supported
- Typical use cases:
- Power distribution
- GOOSE messaging (IEC 61850)
- SEL Mirrored Bits (relay-to-relay)
- AMI/AMR concentrators backbone
- DMR base stations interconnection
- Mounting
- Common surrounding temperature
- Units can be mounted on DIN rail or on a shelf in a 19″ rack
- High surrounding temperature – it is recommended to use 19″ rack chassis
- RipEX2-RS
- 1x RipEX2
- 1x Power supply
- 1x Internal Duplexer (optional)
- RipEX2-HS
- Redundant solution
- 2x RipEX2
- 2x Power supply
- 1x Internal Duplexer (optional)
- Two N(f) antenna connectors (Tx and Rx) on the rear panel are available
When an internal duplexer is used, only one N(f) connector (Tx/Rx) is there
- RipEX2-RS
- Common surrounding temperature
- Ordering information
Other details
- Each radio hop is typically 5 – 50 km, right up to 100 km
- Line of sight not required
- Any unit can work simultaneously as a repeater
- Unlimited number of repeaters on the way
- RF Output power 0.1 – 10 W
- Exceptional receiver sensitivity
- High resistance to multipath propagation and interference
- Any IP network (e.g. Internet) can interconnect any RipEX units
- Management access
- Wifi
- Via USB using WiFi/USB adapter with DHCP
- WPA2-PSK security
- Wifi
-
- Cable
- Via USB using USB/ETH adapter with DHCP
- Directly via any ETH interface
- Cable
- Web interface
- Intuitive
- Responsive, optimized for mobile devices
- Integrated Helps
- Checking of set values
- API interface (RipEX2, RipEX2e)
- Application Programming Interface
- Unit can be managed by external application
- Full access to configuration and diagnostics
- Detail description on request
- Command Line Interface (RipEX)
- via SSH
- Fast remote access
- Only required data from remote unit are transferred over-the-air, html page is provided from the local unit
- USB Flash drive allows to do automatically (RipEX):
- Firmware upgrade (RipEX2, RipEX2e also)
- SW Keys upload
- Configuration backup / restore
- SSL certificate upload
- Technical support package download
- Firmware upgrade possible over-the-air
- Datasheets, User manuals, Info sheets, Application notes, Tutorial videos…
TUTORIAL VIDEOS
- Embedded tools for
- Network planning
- Testing
- Diagnostics
- Network management
- Radio link testing
- Ping with RSS, Data Quality (RipEX) or MSE (RipEX2, RipEX2e) and Homogeneity separately for each radio hop
- Application note
- Statistic
- Detailed statistics for each radio link and all user interfaces
- Rx/Tx packets, Rx/Tx bytes, Repeats, Lost, Rejected…
- History
- Saved Historical values
- Online adjustable Difference log
- Device monitoring
- Real time / Save-to-file analysis of all interfaces
- Network management
- Any SNMP based Network Management Software can be used
=> proprietary NMS is not required - Free, open-source Zabbix is recommended
- Test live demo Zabbix here (customer / RacomDemo1234)
- Alarms – either SNMP Traps or acknowledged SNMP Informs generated when preset thresholds of Watched values (RipEX) are exceeded or when specific Event (RipEX2, RipEX2e) is triggered
- Application note
- Any SNMP based Network Management Software can be used
- Event log (RipEX2, RipEX2e)
- Settings of the severities of the individual events
- Some events can generate SNMP notification and can change level of the HW alarm outputs (AO, DO1, DO2)
- Information (RipEX2, RipEX2e)
- Quick overview about unit settings, FW versions, Serial numbers etc.
- Watched values (RipEX)
- Their broadcasting incl. Alarms
- TXLost, Ucc, Temp, PWR, VSWR, ETH [Rx/Tx], COM1,2 [Rx/Tx]
- Neighbours (RipEX)
- Count, RSS, DQ + Watched values from neighbouring units
- Graphs (RipEX)
- Real-time sampling means 10 samples saved even before Alarm
- HW Alarm input, HW Alarm output
- Malfunctioning antenna detection
HW models
- The same HW for Base, Repeater or Remote stations => minimizing spares, enabling easy network reconfiguration
- FSK and QAM modulation within one box
- Different models
- 19″ rack chassis
RipEX2
- Always two antenna connectors SW configurable: 1x Rx/Tx or 1x Rx + 1x Tx
- mPCIe slot for extension modules: Cellular, 2x RS232, GPS …
Extension modules features are continuously improved, for details see User manual
RipEX2e
- Always one antenna connector Rx/Tx
- mPCIe slot is not available
SW keys
- SW authorization keys allow to use advance features only when and where needed
- Future investment protection – gradual upgrade
RipEX
- Router, Speed, COM2, 10W, Backup routes, Master
- Time limited keys
- Allow to test features prior to the order
- Master key trial
- All coded functions for free for 30 days in each unit
- Solar ready
- Sleep mode
- Wake up triggered by Sleep digital input or by internal RTC (RipEX2, RipEX2e)
- Save mode (RipEX)
- Wake up by a received packet from Radio channel or by Sleep digital input
Specifications
RipEX2 | RipEX2e | RipEX | |
Max. Speed | 1.7 Mb/s @ 256QAM |
250 kb/s @ 64QAM |
166 kb/s @ 16DEQAM |
Speed @ 25 kHz | 167 kb/s | 125 kb/s | 83 kb/s |
Channel size | 6.25 – 300 kHz | 6.25 – 50 kHz | 6.25 – 50 kHz |
Interfaces | 4×ETH, 1×SFP, 1×COM, 1×USB | 2×ETH,2×COM, 1×USB | 1×ETH,2×COM, 1×USB |
mPCIe | Yes | No | No |
Full duplex | Yes | No | No |
Fully Redundant Hot Standby Master Station | Yes | No | Yes |
Management Access | 4 levels | 4 levels | 2 levels |
IPsec | Yes | Yes | Yes |
RADIUS | Yes | Yes | No |
Radio parameters | RipEX2 | RipEX2e | ||||
Frequency bands | 135 – 175 MHz
285 – 335; 335 – 400 MHz 400 – 470; 450 – 520 MHz 803 – 897; 860 – 960 MHz |
|||||
Channel spacing | 6.25; 12.5; 25; 50; 100; 150; 200; 250; 300 kHz | 6.25; 12.5; 25; 50 kHz | ||||
Frequency stability | ±0.5 ppm ±0.01 ppm with internal (optional) GNSS (GPS) or external time synchronisation, see details |
±0.5 ppm | ||||
Modulation | QAM: 256QAM; 64QAM; 16DEQAM; D8PSK; π/4DQPSK;
DPSK FSK: 4CPFSK; 2CPFSK, see details |
QAM: 64QAM; 16DEQAM; D8PSK; π/4DQPSK;
DPSK FSK: 4CPFSK; 2CPFSK, see details |
||||
FEC (Forward Error Correction) | 2/3; 3/4; 5/6; Off
Trellis code with Viterbi soft-decoder |
|||||
Gross data rate (data speed) 1) | Channel spacing
[kHz] |
Gross data rate
(modulation rate)
[kb/s] |
Channel spacing
[kHz] |
Gross data rate
(modulation rate)
[kb/s] |
||
6.25 | 35 | 6.25 | 26 | |||
12.5 | 83 | 12.5 | 63 | |||
25 | 167 | 25 | 125 | |||
50 | 333 | 50 | 250 | |||
100 | 555 | |||||
150 | 925 | |||||
200 | 1111 | |||||
250 2) | 1389 | |||||
300 2) | 1736 | |||||
Transmitter | ||||||
RF Output power | QAM: 0.1 – 5.0 W (20 – 37
dBm) RMS in 1dB step 3)
FSK: 0.1 – 10 W (20 – 40 dBm) in 1dB step see details |
|||||
Duty cycle | Continuous | |||||
Rx to Tx Time | < 2 ms @ 6.25 kHz
channel < 1.0 ms @ 12.5 kHz channel < 0.7 ms @ 25 kHz channel |
|||||
Spurious Emissions (Conducted) | < -36 dBm | |||||
Radiated Spurious Emissions | < -36 dBm | |||||
Adjacent channel power | < -60 dBc | |||||
Transient adjacent channel power | < -60 dBc | |||||
Receiver | ||||||
Anti-aliasing Selectivity | 56 kHz
@ -3 dB
BW applicable for 6.25; 12.5; 25 kHz
500 kHz @ -3 dB BW applicable for 50; 100; 150; 200; 250; 300 kHz |
56 kHz
@ -3 dB
BW applicable for 6.25; 12.5; 25 kHz
500 kHz @ -3 dB BW applicable for 50 kHz |
||||
Tx to Rx Time | < 2 ms @ 6.25 kHz
channel < 1.0 ms @ 12.5 kHz channel < 0.7 ms @ 25 kHz channel |
|||||
Maximum Receiver Input Power | 20 dBm (100 mW) | |||||
Rx Spurious Emissions (Conducted) | < -57 dBm | |||||
Radiated Spurious Emissions | < -57 dBm | |||||
Blocking or desensitization | > -23 dBm
@ 1 MHz
> -19 dBm @ 2 MHz > -15 dBm @ 5 MHz > -13 dBm @ 10 MHz |
|||||
Spurious response rejection | > 70 dB | |||||
Technical parameters are subject to change without prior notification. | ||||||
1) | Network throughput varies and depends heavily on the data structure, optimization effectivity, protocol on Radio channel, network topology, signal budgets and many other parameters of the network. Practical tests are recommended. | |||||
2) | Available only in Bridge mode. | |||||
3) | Max peak envelope power (PEP) 10 W (40 dBm) . |
Electrical | RipEX2 | RipEX2e | |||
Primary power | 10 to 30 VDC, negative GND | ||||
Rx | 8 W / 13.8 V, see details | ||||
Tx | 12 – 55 W, see details | ||||
Sleep mode | 0.01 W | ||||
Interfaces | |||||
Ethernet | 10/100/1000Base-T Auto MDI/MDIX | 4× RJ45 | 10/100/1000Base-T Auto MDI/MDIX | 2× RJ45 | |
SFP | 10/100/1000Base-T or 1000Base-SX or 1000Base-LX user exchangeable SFP with max. power consumption 1.25 W |
1× SFP | No SFP | ||
COM | RS232 / RS485 SW configurable | DB9F | |||
600 b/s – 2 Mb/s | |||||
COM2 | Extension module 'C' 2 × RS232 RJ45 | RS232 DB9F (COM1,COM2) | |||
COM2: 600 b/s – 2 Mb/s; COM3: 2.4 kb/s – 921.6 kb/s |
600 b/s – 2 Mb/s | ||||
USB | USB 3.0 | Host A | |||
Antenna | 50 Ω SW configurable 1× Tx / Rx or 1× Rx + 1× Tx |
2× TNC female | 50 Ω 1× Tx / Rx |
1× TNC female | |
Inputs/Outputs | 1× HW alarm input
1× HW alarm output 1× Sleep input |
Power connector |
|||
2× DI, 2× DO, 1× diffDI
not available when Extension module 'C' (COM ports) is used |
RJ45 | Not available | |||
Indication LEDs | |||
LED panel | 5× tri-color status LEDs (SYS, EXT, RX, TX, COM) | ||
ETH | 4× RJ45 (Link and Activity LEDs), 1× SFP (Status LED) | ||
Environmental | |||
IP Code (Ingress Protection) | IP41, IP42, IP52 - see details | ||
MTBF (Mean Time Between Failure) | > 900 000 hours (> 100 years) | ||
Operating temperature | −40 to +70 °C ( −40 to +158 °F) 4) | ||
Operating humidity | 5 to 95 % non-condensing | ||
Storage | −40 to +85 °C ( −40 to +185 °F) / 5 to 95 % non-condensing | ||
Mechanical | |||
Casing | Rugged die-cast aluminium | ||
Dimensions |
H×W×D: 60×185×125.5 mm (2.34×7.2×4.94 in) |
||
Weight |
1.55 kg (3.4 lbs) |
||
Mounting | DIN rail, L-bracket,
Flat-bracket, 19" Rack chassis
see details |
||
SW | |||
Operating modes | Bridge / Router | ||
Radio channel protocols | Transparent @
Bridge Base driven, Flexible @ Router see details |
||
User protocols on COM | DNP3, DF1, IEC101, Modbus RTU, PR2000, RDS, Siemens 3964(R), COMLI, SAIA S-bus, Mars-A, PPP, UNI, Async Link | ||
User protocols on Ethernet | Modbus TCP, IEC104, DNP3 TCP, Comli TCP, Terminal server… | ||
Serial to IP convertors | DNP3 / DNP3 TCP, Modbus RTU / Modbus TCP | ||
Protocol on Radio channel | |||
Multi master applications | Yes | ||
Report by exception | Yes | ||
Collision Avoidance Capability | Yes | ||
Remote to Remote communication | Yes | ||
Addressed and acknowledged serial SCADA protocols |
Yes | ||
Data integrity control | CRC 32 | ||
Optimization | Intelligent payload data and header (Eth / IP / TCP / UDP) compression | ||
Security | |||
Management | HTTPS (Web Interface or Application Programming Interface) | ||
Role-based access control (RBAC) | 4 levels (Guest, Tech, SecTech, Admin) | ||
WiFi management access (optional) | WPA2-PSK secured | ||
Encryption | AES256-CCM | ||
VPN | IPsec, OpenVPN, GRE | ||
VLAN | IEEE 802.1Q (tagging), Q-in-Q for Transparent mode | ||
AAA protocol | RADIUS | ||
Firewall | Layer 2 - MAC, Layer 3 - IP, Layer 4 - TCP/UDP | ||
FW | Digitally signed | ||
HW tamper | Case opening evidence | ||
4) | When full-duplex with full power (40 dBm PEP) and the surrounding temperature above + 60°C the external passive cooler should be used (e.g. RipEX2-RS 19" Rack chassis). |
Diagnostic and Management | |
Link testing | ICMP ping, RSS ping |
Status information | User interfaces |
Statistics |
Historical and differential statistics for Rx / Tx Packets on all user
interfaces (ETH 1-5, COM 1-3, TS 1-5) and Radio interface - for individual
connections. |
Statistics history | Several weeks |
Event log | Events filtered by time, severity, user, remote IP address and type of event |
SNMP | SNMPv1, SNMPv2c, SNMPv3 Trap / Inform alarms generation as per settings |
NTP | Client / Server |
Monitoring | Real time analysis of all interfaces (RADIO, ETH 1-5 , COM 1-3, TS 1-5) and internal interfaces between software modules, see details |
Standards | |
CE | RED; RoHS; WEEE |
FCC, IC | FCC Part 90, IC RSS-119 |
Spectrum | ETSI EN 302 561 V2.1.1 ETSI EN 300 113 V2.2.1 |
EMC (electromagnetic compatibility) |
ETSI EN 301 489-1 V2.2.3 ETSI EN 301 489-5 V3.2.1 EN 61850-3:2014 |
Product safety | EN 62368-1:2014 + A11:2017 |
RF health safety | EN 62311:2008 |
Electric power substations environment |
IEEE 1613:2009 IEEE 1613.1:2013 EN 61850-3:2014 |
Hazardous locations | EN 60079-0:2012 EN 60079-11:2012 |
Environmental | EN 61850-3: 2014 |
Vibration & shock |
EN 60068-2-6:2008 |
Seismic qualification | EN 60068-2-27:2010 |
IP rating | EN 60529:1993 + A1:2001 + A2:2014 |
Optional interfaces (not applicable for RipEX2e) | ||
Extension module 'G' |
Active antenna 3.3 VDC SMA female (EXT on front panel) | |
72-channel u-blox M8 engine GPS/QZSS L1 C/A, GLONASS L10F, BeiDou B1I, Galileo E1B/C, SBAS L1 C/A: WAAS, EGNOS, MSAS, GAGAN | ||
Extension module 'C' |
COM2: RS232 - 5 pin (RxD, TxD, GND, RTS, CTS) 600 b/s to 2 Mb/s COM3: RS232 - 3 pin (RxD, TxD, GND) 2.4 kb/s to 921.6 kb/s RJ45 (DI/DO on front panel) |
|
Extension module 'W', 'M', 'O'
|
see details |
Radio parameters | ||||||||||||||
Frequency bands | 135 – 154; 154 – 174 MHz 215 – 240 MHz 300 – 320; 320 – 340; 340 – 360 MHz 368 – 400; 400 – 432; 432 – 470 MHz 470 – 512 MHz 928 – 960 MHz see details |
|||||||||||||
Channel spacing | 6.25; 12.5; 25; 50 kHz 1) | |||||||||||||
Frequency stability | ±1.0 ppm | |||||||||||||
Modulation | QAM (linear): 16DEQAM; D8PSK; π/4DQPSK; DPSK | |||||||||||||
FSK (exponential): 4CPFSK; 2CPFSK | see details | |||||||||||||
FEC (Forward Error Correction) | On/Off, ¾ Trellis code with Viterbi soft-decoder | |||||||||||||
Gross data rate (data speed) 2) |
|
|||||||||||||
Transmitter | ||||||||||||||
RF Output power | QAM: 0.5 – 2 W
3) FSK: 0.1 – 10 W 4) see details |
|||||||||||||
Duty cycle | Continuous | |||||||||||||
Rx to Tx Time | < 1.5 ms | |||||||||||||
Intermodulation Attenuation | > 40 dB | |||||||||||||
Spurious Emissions (Conducted) | < -36 dBm | |||||||||||||
Radiated Spurious Emissions | < -36 dBm | |||||||||||||
Adjacent channel power | < -60 dBc | |||||||||||||
Transient adjacent channel power | < -60 dBc | |||||||||||||
Receiver | ||||||||||||||
Sensitivity | -113 dBm (12.5 kHz, 2CPFSK, BER 10-6, 3/4 FEC, see details | |||||||||||||
Anti-aliasing Selectivity | 50 kHz @ -3 dB BW | |||||||||||||
Tx to Rx Time | < 1.5 ms | |||||||||||||
Maximum Receiver Input Power | 20 dBm (100 mW) | |||||||||||||
Rx Spurious Emissions (Conducted) | < -57 dBm | |||||||||||||
Radiated Spurious Emissions | < -57 dBm | |||||||||||||
Blocking or desensitization | see details | |||||||||||||
Spurious response rejection | > 70 dB | |||||||||||||
1) | 50 kHz channel spacing is HW dependent, versions before 2014 didn´t support it. 6.25 kHz channel spacing is not available for RipEX-928. | |||||||||||||
2) | Network throughput varies and depends heavily on the data structure, optimization effectivity, protocol on Radio channel, network topology, signal budgets and many other parameters of the network. Practical tests are recommended. | |||||||||||||
3) | Max peak envelope power (PEP) 7.0 W | |||||||||||||
4) | For output power 10 W it is recommended to use input power above 11 VDC. | |||||||||||||
RipEX-470, RipEX-928 - max. RF Output power 8 W. |
Electrical | ||||
Primary power | 10 to 30 VDC, negative GND | |||
Rx | 5 W / 13.8 V; 4.8 W / 24 V; (Radio part < 2 W) | |||
Tx | 13 – 40 W, see details | |||
Sleep mode | 0.1 W | |||
Save mode | 2 W | |||
Interfaces | ||||
Ethernet | 10/100 Base-T Auto MDI/MDIX | RJ45 | ||
COM1 | RS232 | DB9F | ||
300 – 115 200 b/s | ||||
COM2 | RS232/RS485 SW configurable | DB9F | ||
300 – 115 200 b/s | ||||
USB | USB 1.1 | Host A | ||
Antenna | 50 Ω | TNC female | ||
Inputs/Outputs | 1x HW alarm input 1x HW alarm output 1x Sleep input |
Power connector |
Indication LEDs | |||
LED panel | 7× tri-color status LEDs (Power, ETH, COM1, COM2, Rx, Tx, Status) |
||
Environmental | |||
IP Code (Ingress Protection) | IP40, (IP51 - see details) | ||
MTBF (Mean Time Between Failure) | > 900 000 hours (> 100 years) | ||
Hazardous lodations | Ex II 3G Ex ic IIC T4 Gc | ||
Operating temperature | −40 to +70 °C (−40 to +158 °F) | ||
Operating humidity | 5 to 95 % non-condensing | ||
Storage | −40 to +85 °C (−40 to +185 °F) / 5 to 95 % non-condensing | ||
Mechanical | |||
Casing | Rugged die-cast aluminium | ||
Dimensions | H × W × D: 50 × 150 × 118 mm (1.97 × 5.9 × 4.65 in) | ||
Weight | 1.1 kg (2.4 lbs) | ||
Mounting | DIN rail, L-bracket, Flat-bracket, 19" Rack shelf | ||
SW | |||
Operating modes | Bridge / Router | ||
Radio channel protocols | Transparent @ Bridge Base driven, Flexible @ Router see details |
||
User protocols on COM |
Modbus, IEC101, DNP3, PR2000, UNI, Comli, DF1, RP570, Profibus, … |
||
User protocols on Ethernet | Modbus TCP, IEC104, DNP3 TCP, Comli TCP,
Terminal server… |
||
Serial to IP convertors | Modbus RTU / Modbus TCP, DNP3 / DNP3 TCP | ||
Protocol on Radio channel | |||
Multi master applications | Yes | ||
Report by exception | Yes | ||
Collision Avoidance Capability | Yes | ||
Remote to Remote communication | Yes | ||
Addressed & acknowledged serial SCADA protocols |
Yes | ||
Data integrity control | CRC 32 | ||
Optimization | Payload data and Ethernet / IP / TCP / UDP header compression, Packet flow on Radio channel optimization | ||
Security | |||
Management | HTTP, HTTPS (own certificate), SSH | ||
Access accounts | 2 levels (Guest, Admin) | ||
Encryption | AES256-CCM | ||
VPN | IPsec, GRE | ||
VLAN | IEEE 802.1Q (tagging), Q-in-Q for Transparent mode | ||
Firewall | Layer 2 - MAC, Layer 3 - IP, Layer 4 - TCP/UDP |
Diagnostic and Management | |||
Radio link testing | Yes (ping with RSS, Data Quality, Homogeneity) | ||
Watched values (Can be broadcast to neighbouring units. Received info displayed in Neighbours table) | Device - Ucc, Temp, PWR, VSWR, *HW Alarm
Input. Radio channel - *RSScom, *DQcom, TXLost [%] User interfaces - ETH (Rx/Tx), COM1 (Rx/Tx), COM2 (Rx/Tx) * not broadcast |
||
Statistics | For Rx/Tx Packets on User interfaces (ETH, COM1, COM2) and for User data and Radio protocol (Repeats, Lost, ACK etc.) on Radio channel | ||
Graphs | For Watched values and Statistics | ||
History (Statistics, Neighbours, Graphs) |
20 periods (configurable, e.g. days) | ||
SNMP | SNMPv1, SNMPv2c, SNMPv3 SNMP Traps or SNMP Informs generation for Watched values |
||
NTP | Client, Server (synchronized from internal GPS) | ||
Monitoring | Real time/Save to file analysis of all physical interfaces (RADIO, ETH, COM1, COM2) and some internal interfaces between software modules (e.g. Terminal servers, Modbus TCP server etc.) |
Standards | |
CE | RED, RoHS, WEEE |
FCC, IC | FCC Part 90, Pending: IC RSS-119 |
Spectrum | ETSI EN 302 561 V2.1.1:2017 ETSI EN 300 113 V2.2.1:2017 |
EMC (electromagnetic compatibility) | ETSI EN 301 489-1 V2.1.1:2017 ETSI EN 301 489-5 V2.1.1:2017 IEC 1613:2009 Class 1 |
Safety | EN 60950-1:2006, A11:2009, A1:2010, A1:2010, A12:2011, A2:2013 |
SAR | EN 50385:2002 EN 50383ed.2:2011 |
Vibration & shock | EN 61373:1999 EN 60068-2-6:2008 |
Seismic qualification | IEC 980:1989 (seismic category 1a) |
Hazardous locations | EN 60079-0:2012 EN 60079-11:2012 |
IP rating | EN 60529:1993 + A1:2001 + A2:2014 |
Accessories
RACOM is a primary producer and therefore does not provide delivery of all available accessories for its products. This list contains tested accessories which RACOM is able to deliver together with RipEX units. Components are only held in limited quantities and the delivery date may therefore be affected by the need for subcontracting. If you require other accessories, please contact us or your supplier.
DC power supply, DIN rail
- Input 90-264 VAC, 127-370 VDC
- Output 12 VDC
- 75 W
- -20°C to +70°C
- Overload, Over voltage, Over temperature protections
- Direct DIN rail mounting
- Datasheet, Part No.: PWS-AC,DC/12VDC/75W2
- Manufactured by MeanWell
- Replacement of PWS-AC,DC/12VDC/76W from VIII/2021
DC power supply, Battery charger
- Input 90 – 264 VAC, 127 – 370 VDC
- Output 13.8 VDC
- 97 W
- -30°C to +70°C
- Overload, Over voltage, Battery low protections
- Back-up battery charger
- Direct DIN rail mounting
- Datasheet, Part No.: PWS-AC,DC/13.8VDC/97W
- Manufactured by MeanWell
- Replacement of PWS-AC-DC_13.8VDC_152W from VIII/2020
DIN rail clips
- Standard accessory
- Shipped with every RipEX, RipEX2 and RipEX2e unit
- Part No.: HOL-RipEX-DINSET
Flat bracket
- For flat surface mounting
- Datasheet, Part No.: HOL-RipEX-FLAT, HOL-RipEX2-FLAT
- Manufactured by RACOM
L bracket
- For vertical mounting
- To DIN rail or directly to a mounting surface
- Datasheet, Part No.: HOL-RipEX-L, HOL-RipEX2-L
- Can not be used when mPCI Extension cellular module is installed in RipEX2
- Manufactured by RACOM
S bracket
- For side mounting
- To DIN rail or directly to a mounting surface
- Datasheet, Part No.: HOL-RipEX2-S
- Manufactured by RACOM
19″ rack chassis
RipEX
- 1.6U (70mm) height
- Ready for assembly with either one (S-single) or two (D-double) RipEX units
- Power options:
- 100 – 230 VAC / 24 VDC, Part No’s.: RipEX-RS-230, RipEX-RD-230
- 48 VDC / 24 VDC, Part No’s.: RipEX-RS-48, RipEX-RD-48
- Dataheet
- Manufactured by RACOM
RipEX2
- 2U height
- Power options
- Built-in duplexer possible
- Chassis also serve as a passive cooler for the unit(s)
- RipEX2-RS
- 1x RipEX2 or RipEX2e
- 1x Power supply
- 1x Built-in duplexer (optional)
- RipEX2-RD
- 2x RipEX2 or RipEX2e
- 2x Power supply
- 2x Built-in duplexer (optional)
- Redundancy
- Redundant antenna system (independent antenna(s) for each unit) and redundant connection of connected technology to “A” and “B” units are required
- Ordering information
- Datasheet
- Manufactured by RACOM
Ingress Protection IP52
- For RipEX2 and RipEX2e only
- RipEX2 and RipEX2e standard Ingress Protection is IP41
- Increase of Protection against Solid objects to IP5x
- Dust covers for all unused connectors
- 5x RJ45, 1x USB, 1x SFP, 2x TNC, 1x SMA, (DSUB9 cover is not needed)
- Datasheet, Part No.: SET-RipEX2-IP5x
- Increase of Protection against Water to IPx2
- Unit installed just with connectors facing downward
- Datasheet
- For service and management access to the web interface via USB connector
- Any RipEX provides built-in DHCP server (up to 5 leases)
- Direct easy access from connected device to RipEX management without any reconfiguration
- To access the RipEX always use the fixed IP 10.9.8.7
- To avoid FW compatibility issues it is necessary to order these adapters from RACOM
Wifi adapter
- For RipEX only
- Part No.: OTH-USB/WIFI-W1
- Manufactured by Edimax
Wifi adapter 2
- For RipEX2 and RipEX2e only
- Datasheet, Part No.: OTH-USB/WIFI-W2
- Manufactured by Ogemray
USB/ETH adapter
- For RipEX, RipEX2 and RipEX2e
- FW 1.7.1.0 or higher is required
- Datasheet, Part No.: OTH-USB/ETH-U2
- Manufactured by i-tec
USB/ETH adapter 2
- For RipEX2 and RipEX2e only
- FW 1.4.3.0 or higher is required
- Datasheet, Part No.: OTH-USB/ETH-XR
- Manufactured by Axagon
All common types of SFP modules are supported. There are two basic tested modules which RACOM can deliver together with RipEX2 units. If you require anything else, please contact us or your supplier.
SFP module Fibre
- Two fibres
- Single mode
- LC connector
- 20 km
- -45°C to +85°C
- Datasheet, Part No.: SFP-2F-1G-EDGE
- Manufactured by EDGE Technologies
SFP module Ethernet
- Metallic 1 Gb Ethernet
- IEEE 802.3
- RJ45 connector
- -45°C to +85°C
- Datasheet, Part No.: SFP-RJ45-1G-EDGE
- Manufactured by EDGE Technologies
- Coaxial, N(f) / N(f) connectors
- 100 – 512 MHz
- Up to 750 watts
- PLZ0A(B) – LPZ1 zones
- Also suitable for the PLZ0A zone, serving as a lightning conductor
- Low VSWR
- Continuous RF performance after surge (no fuse, automatic reset)
- Flexible bulkhead and bracket mounting capabilities
- IP67
- Datasheet, Part No.: SURGE-COAXIAL
- Manufactured by Polyphaser
Coaxial Patch cord
- 0.5 m (19.7 in)
- RG58
- TNC(m) / N(m)
- For antenna feedline extension inside of the cabinet, e.g. between RipEX and Coaxial surge protection
- Part No.: CAB-RG58-0.5m
- Manufactured by RACOM
Coaxial connectors
RG58
- N male
- Crimp
- -55 to +155°C
- Datasheet, Part No.: CON-Nm-RG58
- Manufactured by Rosenberger
RG213
- N male
- Crimp
- -55 to +155°C
- Datasheet, Part No.: CON-Nm-RG213
- Manufactured by Rosenberger
H1000
- N male
- Screwing
- -40 to +85°C
- Datasheet, Part No.: CON-Nm-H1000
- Manufactured by PPC
Power connector
- Part of Accessory kit shipped with every unit
- 7 pin clamping screw plug (14 – 30 AWG)
- Datasheet, Part No.: CON-RipEX-PWR
- Manufactured by Tyco
Antennas
It is recommended to source antennas locally, however RACOM is also capable to deliver them. If you would need any help or consultation, don’t hesitate to contact us.
Dummy load antenna
- For laboratory testing
- 50 ohms
- TNC male connector
- Up to 1 W RF output power
- Part No.: ANT-RipEX-DUMMYLOAD
- Manufactured by RACOM
Duplexers
- 140-175 MHz, 300-360 MHz, 400-470 MHz
- Symmetrical, 6 cavities
- Isolation and Inserted loss are dependent on frequency
- Maximum input power 25W
- Impedance 50 ohms
- N female connectors
- Rx and TX frequencies must be specified while ordering
- Datasheet, Part No.: OTH-DUPLEXER
- May be used internally in RipEX2-RS and RipEX2-HS, Part No’s.: RipEX2-HS-HW-DUP
- Manufactured by RCD
Migration solution
These accessories are recommended when Migration solution is implemented.
Migration Serial cable
- RS232 cable between RipEX and legacy base station
- 2m (80 in) long
- Crossing cable (null-modem), Rx->Tx, Tx->Rx, GND
- ‘Carrier On’ contact for legacy base station keying (Relay Dry Contact), managed by CTS envelope from RipEX
- DSUB9M – DSUB9M, ‘open wires’ for ‘Carrier On’ contact for legacy base station
- Part No.: OTH-MIG-CAB
- Manufactured by RACOM
Automatic Antenna Switch
- Automatically manages antenna switching: when one base station transmits, the other one is disconnected from the common antenna
- Attenuation between antenna connectors > 50 dB
- Insertion loss max. 4.5 dB in full frequency range
- RF output power of connected second radio modem up to 25 watts (duty cycle 50%)
- Different models for different frequency bands: 135-174, 300-340, 360-400, 400-470 MHz
- Includes 3 cables RG58 each 50 cm (20 in) long: 1x SMA(f)-TNC(m), 2x SMA(f)-N(f)
- Panel or DIN rail mounting
- Datasheet, Part No.: OTH-MIG-AAS
- Manufactured by RACOM
- For 3 pcs of RipEX or RipEX2 or RipEX2e and 1 pc of M!DGE
- Suitable for functional demonstration
- Ready for complete application bench-test
- Rugged and sturdy, Ultra High-Impact ABS Plastic
- Dustproof, airtight, watertight
- Outside dimension: 455 x 365 x 185 mm
- Weight approx. 4 kg (excluding the RipEX’s and M!DGE)
- Part No.: RipEX2-DEMO-CASE
- Manufactured by RACOM
- Redundant hot standby chassis (fully monitored, hot swappable, 1+1 redundant)
- Two booted-up standard RipEX units inside
- Automatic switchover capability on detection of failure
- Suitable for Central sites, Repeaters or Important remote sites where no single point of failure is required
- Details
- Part No‘s.: RipEX-HS, RipEX2-HS
Accessory kit shipped with every RipEX, RipEX2 or RipEX2e unit
- DIN set – set of two DIN rail clips + two screws, Part No.: HOL-RipEX-DINSET, 1 pc
- Power connector plug, Part No.: CON-RipEX-PWR, 1 pc
- Removable plate with sticker for your notes
Calculations
Calculations
RipEX settings
|
Use our calculations for a simplistic overview of RipEX network performance. RipEX settings are common for both independent parts – Payload bitrate and Netwok performance. Payload bitrate gives you a quick and easy idea of the possible bitrate in the RipEX network. Network performance is the more robust and detailed option. See the details in respective helps. | ||||||||||||||||
Payload bitrateBased on this calculation, one can see the effect packet length has on the resulting bitrate. Since the RipEX radio protocol overhead per packet is fixed, the longer the user data are, the higher the payload bitrate.
|
Network performanceNetwork performance calculation is intended to give you a quick performance overview based on several basic parameters. |
Download
Product overview | ripex-product-overview.pdf | 2 118 kB | 01.08.2019 |
Datasheet RipEX - A4 - ver.4.0 - English | ripex-dsA4-en.pdf | 2 622 kB | 15.03.2024 |
Datasheet RipEX - A4 - ver.4.0 - En español | ripex-dsA4-es.pdf | 2 845 kB | 15.03.2024 |
Брошюра RipEX - A4 - ver.4.0 - По-русски | ripex-dsA4-ru.pdf | 2 717 kB | 15.03.2024 |
Datasheet RipEX - A4 - ver.4.0 - Francais | ripex-dsA4-fr.pdf | 2 642 kB | 15.03.2024 |
Datasheet RipEX - A4 - ver.4.0 - Em português | ripex-dsA4-po.pdf | 2 826 kB | 15.03.2024 |
RipEX – Radio modem & Router - DEMO handbook | ripex-case-man-en.pdf | 3 640 kB | 14.10.2021 |
User manual RipEX2, RipEX2e | ripex2-man-en.pdf | 27 013 kB | 14.03.2024 |
User manual RipEX | ripex-man-en.pdf | 12 141 kB | 10.03.2022 |
Base Driven protocol | ripex-base-driven-protocol-is.pdf | 2 427 kB | 07.01.2020 |
Data speed | ripex-data-speed-is.pdf | 1 796 kB | 07.01.2020 |
Flexible protocol | ripex-flexible-protocol-is.pdf | 508 kB | 07.01.2020 |
Hybrid networks | ripex-hybrid-networks-is.pdf | 1 924 kB | 07.01.2020 |
Migration solution | ripex-migration-solution-is.pdf | 898 kB | 07.01.2020 |
Power distribution - CFE, Mexico | ripex-cs-cfe-en.pdf | 2 902 kB | 25.02.2016 |
Water management - WSC, Malta | ripex-cs-wsc-en.pdf | 1 281 kB | 24.09.2015 |
WSC Malta whitepaper | wsc-psaila-wp-en.pdf | 443 kB | 24.09.2015 |
RipEX Firmware package 1.9.7.0 | ra1-RACOM-1.9.7.0.cpio | 11 873 kB | 23.07.2021 |
Firmware Release notes | ripex-fw-rn-en.pdf | 368 kB | 11.05.2022 |
MIB table | ripex-mib.zip | 26 kB | 16.09.2019 |
Zabbix ver. 6 templates | ripex-zabbix-v6.0.zip | 4 480 kB | 23.06.2022 |
Firmware | ripex2-fw-2.1.6.0.fwp | 34 789 kB | 13.03.2024 |
Firmware | ripex2-fw-2.1.6.0-patch-2.1.2.0.fwp | 4 496 kB | 13.03.2024 |
Firmware Release notes | ripex2-fw-rn-en.pdf | 571 kB | 13.03.2024 |
MIB table 2.1.6.0 | ra2-mib-2.1.6.0.zip | 24 kB | 13.03.2024 |
Zabbix ver. 6 templates 2.1.6.0 | ripex2-zabbix-6.0-2.1.6.0.zip | 5 023 kB | 12.03.2024 |
USB adapters | |||
Adapter USB/ETH (RipEX2, M!DGE2, RAy3), Axagon | OTH-USB_ETH-XR.pdf | 110 kB | 18.08.2020 |
Adapter USB/ETH (RipEX, RipEX2, M!DGE2, RAy2, RAy3), i-tec | OTH-USB_ETH-U2.pdf | 398 kB | 16.04.2021 |
Adapter USB/Wifi (RipEX2, RAy2, RAy3), Ogemray | OTH-USB_WIFI-W2.pdf | 219 kB | 10.12.2018 |
SFP modules | |||
SFP module, 1 Gb Ethernet, RJ45, EDGE | SFP-RJ45-1G-EDGE.pdf | 291 kB | 16.01.2021 |
SFP module, 2 fibres, SM, LC, 20 km, EDGE | SFP-2F-1G-EDGE.pdf | 477 kB | 08.11.2019 |
Power supplies | |||
Power supply 90-264VAC/12VDC/75W, DIN, MeanWell | PWS-AC,DC_12VDC_75W2.pdf | 654 kB | 23.08.2021 |
Power supply with back-up 90-260VAC/13.8VDC/97W | PWS-AC,DC_13.8VDC_97W.pdf | 1 113 kB | 05.08.2020 |
Mounting | |||
19" rack chassis for RipEX | RipEX-Rx.pdf | 721 kB | 11.12.2019 |
19" rack chassis for RipEX2 | RipEX2-Rx.pdf | 2 011 kB | 03.02.2021 |
Bracket for flat surface mounting | HOL-RipEX1-2-FLAT.pdf | 971 kB | 10.12.2019 |
Bracket for side mounting | HOL-RipEX2-S.pdf | 834 kB | 06.02.2023 |
Bracket for vertical mounting | HOL-RipEX1-2-L.pdf | 1 643 kB | 03.02.2021 |
Set of connector dust covers for RipEX2 | SET-RipEX2-IP5x.pdf | 1 837 kB | 03.02.2021 |
Surge protection | |||
Surge protection coaxial, N(f)/N(f), PLZ0A(B)-LPZ1, Polyphaser | SURGE-COAXIAL.pdf | 414 kB | 12.05.2017 |
Cables & Connectors | |||
Coaxial cable H1000, atten. 8.4dB/100m/400MHz, Belden | CAB-H1000.pdf | 217 kB | 14.03.2019 |
Coaxial cable RG213, atten. 13.8 dB/100m/400MHz, Draka | CAB-RG213.pdf | 49 kB | 14.03.2019 |
Coaxial cable RG58, atten. 29.7dB/100m/400MHz, Draka | CAB-RG58.pdf | 78 kB | 14.03.2019 |
Connector N male, for H1000, screwing, PPC | CON-Nm-H1000.pdf | 134 kB | 14.03.2019 |
Connector N male, for RG213, crimp, Rosenberger | CON-Nm-RG213.pdf | 65 kB | 14.03.2019 |
Connector N male, for RG58, crimp, Rosenberger | CON-Nm-RG58.pdf | 84 kB | 14.03.2019 |
Connector, RipEX, Power plug with terminals | CON-RipEX-PWR.pdf | 238 kB | 14.03.2019 |
Migration solution | |||
Automatic Antenna Switch, cables included | OTH-MIG-AAS.pdf | 198 kB | 21.07.2022 |
Duplexers | |||
Duplexer, 6 cavities, RCD | OTH-DUPLEXER.pdf | 219 kB | 13.09.2020 |
DEMO case | |||
User manual - Demo case | ripex-case-man-en.pdf | 3 640 kB | 10.04.2019 |