R3 Bridge E User manual

Bridge E
User Manual UMEREB1000M20221031EU
EREB 1000M (EU Version)
EREB 1000M2 (EU Version)
r22.07
R3 Solutions GmbH · Kurfürstendamm 21 · 10719 Berlin · Germany · [email protected] www.r3.group

UMEREB1000M20221031EU
Table of Contents
1 General Terms of Use of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Please Observe the Following Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3 Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1.1 Versions of this Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1.2 Conformity/National Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2 Intended Use of the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.3 Equipment Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3.1 Requirements for the Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.4 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.5 LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1 Hardware Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1.1 DIN Rail Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1.2 Wall or Mast Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2.1 R3 Launcher Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2.2 Internet Connection Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2.3 Configuration Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2.4 Set Up and Access Web User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.5 Update Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Configuration and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5 Using the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2 Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3 Advanced Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.2 Traffic Filters and Queue Sizes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.3 Broadcast Repetition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.4 Backbone IP and Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.5 Static IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.4.1 Change Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.5 Save and Restore Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1 Device Not showing up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2 Different Regularity Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
ERCI Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
List of Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Product Change Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
www.r3.group

1 General Terms of Use of this Document
It is the user’s responsibility to check and ensure they have downloaded the latest version
of this manual regularly as R3 may edit, revise, or improve product documentation over
time.
The user must ensure the product is used correctly according to this document’s guidelines,
in particular observing all relevant standards and regulations.
This document, including all diagrams and images, is copyrightprotected. Any changes
whatsoever violate our Terms of Use.
www.r3.group Page 1 of 45 1. General Terms of Use of this Document

2 Please Observe the Following Notes
Please observe and obey the following note formats and instructions throughout the docu
ment:
TIP — Text in this format is information explaining the use of the product.
!ATTENTION — Text in this format must be observed to prevent malfunctions and/or even damage, or
safety risks.
iEXAMPLE/NOTE — Text in this format provides examples or notes.
2. Please Observe the Following Notes Page 2 of 45 www.r3.group

3 Product Information
3.1 General Information
3.1.1 Versions of this Product
• EREB 1000M / EREB 1000M2 (EU Version)
• EREB 1000M / EREB 1000M2 (US/CA Version) – NOT COVERED BY THIS DOCUMENT
3.1.2 Conformity/National Approvals
The device complies with these essential EU directives, which include any modifications:
• 2011/65/EU Restriction of the use of certain hazardous substances (RoHS)
• 2014/53/EU Radio equipment (RED).
Additional information (e.g. declaration of conformity, documents, data sheets, certificates,
etc.) can be found at www.r3.group.
3.2 Intended Use of the Product
The Bridge E (device) provides a reliable, timecritical wireless link between Ethernetbased
industrial protocol devices. It can be used to:
• Replace cablebased network infrastructure with a wireless connection in machinery,
vehicles and devices, providing simplified infrastructure and flexible operations.
• Replace network cables between moving structures or components in machinery, ve
hicles and devices to reduce weight, size and use of installation space, as well as wear
and tear on network infrastructure.
ATTENTION — Installation must only be performed by qualified specialist personnel. !
ATTENTION — This radio device is designed to transmit wireless data. It is also intended to be used
for low latency and/or high reliability data communications. When using the device, keep in mind the
general behavior and physics of the wireless channel. Abrupt or predictable changes in the operational
environment, such as movement of people or objects, and the presence of interfering devices, can result in
reduced wireless signal quality and failed data transmissions. As a result, intended operations cannot
rely solely on this device when used in critical applications, where the result of poor wireless
conditions can cause serious injury or economic damage. A comprehensive system solution, such as
an integrated wired failsafe in the case of poor wireless connectivity, must be installed and tested to the
level of intended application’s importance.
!
ATTENTION — The device emits Radio Frequency (RF) energy in the Industrial, Scientific, Medical (ISM)
band. Make sure that all medical devices used in proximity to this device meet appropriate susceptibility
specifications for this type of RF energy. !
ATTENTION — The antennas used for this transmitter must be installed to provide a separation distance
of at least 20cm from all persons and must not be colocated or operating in conjunction with any other
antenna or transmitter. !
ATTENTION — The device is recommended for use in industrial environments. It is mandatory to use a
functional ground connection to comply with safety requirements. !
www.r3.group Page 3 of 45 3. Product Information

!ATTENTION — The device is certified with the enclosed antenna. Any other antenna can exceed the
maximum permitted transmission power.
!ATTENTION — The device must not be disassembled. Do not break the seal!
3.3 Equipment Required
Needed to
ID Item Deploy Operate Update
1Bridge E x x x
2Power Cable M12, 5pin, Acoded x* x* x*
3Ethernet Cable M12/RJ45 x x x
4Network Switch x x
5Ethernet Cable RJ45/RJ45 x x
* Item not needed if Power over Ethernet (PoE) is used.
3.3.1 Requirements for the Equipment
ID Item Requirements
3Ethernet Cable M12/RJ45 The signal cable for digital input must be routed in the
same cable as the power supply and functional ground if
the line length exceeds 3 meters.
4Switch Possibility to disable IGMP Snooping; at least as many
ports as Bridge E devices should be connected + 2
3. Product Information Page 4 of 45 www.r3.group

3.4 Connectors
Figure 3I: Connectors
TIP — The Ethernet connector is PoE (Power over Ethernet) and can also be used to supply power to the
device (48 VDC, PoE 802.3at Type 1).
Figure Pins Function
1 Power supply 24 VDC (+/ 10%)
2 Ground for digital input
3 Ground for power supply
4 Digital input + (9 – 30 VDC)
5 Functional ground
Table 3i: Power connector (M12 plug, A coded)
Figure Pins Function Color Mark (T568B)
1 Send Orange/white
2 Receive Green/white
3 Send Orange
4 Receive Green
Table 3ii: PoE/Ethernet connector (M12 plug)
3.5 LED Indicators
LED Color/pattern Meaning
Power •Off No power.
•Green Device is connected to power.
Ethernet •Green Ethernet physical layer was able to establish
a connection to another device.
Config •Off Device is in Deployment Mode.
•Green Device is in Configuration Mode and a
Configuration Server was found.
•Green blinking (slow) Device is updating its firmware.
www.r3.group Page 5 of 45 3. Product Information

LED Color/pattern Meaning
Status •Green Device is in active deployment and EchoRing
is reporting healthy state.
•Green blinking (slow) EchoRing offline.
•Red The main station manager task found an
unrecoverable error. Device is not working.
•Red blinking (slow) EchoRing not in healthy state.
•Red / •Green switching (fast) System initialization experienced a critical
failure. The system is most likely offline on
all interfaces.
•Red / •Green switching (medium) Failed to start or stop EchoRing and/or the
Bridge E or the initialization of the Bridge E
failed during bootup.
Config+
Status
•Green flashing Config and Status
(very slow)
System is initializing.
•Green flashing Config and Status
(very slow) with
•Orange Status for a short moment
at the beginning of a cycle
Waiting to receive a DHCP lease.
•Green flashing Config (slow)
alternating with
•Green blinking Status (fast)
Update successful.
•Green flashing Config (slow)
alternating with
•Red blinking Status (fast)
Update failed.
•Green flashing Config
•Green Status
The EchoRing network interface has been
started or, in the case of a Mobile Station in
Deployment Mode, the device is ready to be
controlled via ERCI (see Section 6.2).
•Green Config
•Red flashing Status
Failed to deploy the configuration to flash or
failed to verify the written configuration.
all •Off Inconclusive; a specific mode might have
been exited (depending on context).
Table 3iii: Explanation of LEDs
TIP — There are other LED labels on older versions of the Bridge E: PWR (Power), ETH (Ethernet), CFG
(Config), HLT (Status).
Flashing speeds
• Very Slow: 1.6s on  1.6s off
• Slow: 800ms on  800ms off
• Medium: 200ms on  400ms off
• Fast: 200ms on  200ms off
3. Product Information Page 6 of 45 www.r3.group

4 Installation
4.1 Hardware Installation
Figure 4I: Dimensions are in millimeters (mm)
Screw the antenna(s) to the device’s SMA connector(s). Note: antenna is not included in
the diagram.
ATTENTION — Antennas should only be tightened by hand or with a torque wrench of maximum 0.3 Nm. !
4.1.1 DIN Rail Mounting
Figure 4II: DIN rail mounting
Applies to both versions of the Bridge E.
1. Use the selftapping screws provided
to attach the device to DIN rail. Place
the screws through the small DIN rail
adapter plates and screw into device
in their designated position.
2. Place the device now attached to the
adapter on the top edge of DIN rail.
3. Push the device downwards so that it
snaps into place.
TIP — To release device from DIN rail, push the device downwards while pulling outwards.
4.1.2 Wall or Mast Mounting
TIP — Attaching wall mounts to a device is irreversible.
1. Place the wall mounts in their desired
positions on the device. They can be
placed horizontally or vertically.
2. Use adequate force to drive the
mount bolt in the device notch. If
using a hammer, please ensure you
do not accidentally hit and damage
the device casing.
3. Repeat with the other mounts.
Figure 4III: Wall or mast mounting
Applies to both versions of the Bridge E.
www.r3.group Page 7 of 45 4. Installation

4.2 Software Installation
4.2.1 R3 Launcher Application
The R3 Launcher is an application provided as a single installer.
The application allows you to enable Internet Connection Sharing (ICS) and launch the
Configuration Server that can be accessed using your browser.
• To install, doubleclick the R3 Launcher application setup file.
• It will prompt confirmation to make changes to your system. Click on ”Yes”.
• When the screen below appears, select if you want to create a desktop shortcut and
click on ”Next”.
4. Installation Page 8 of 45 www.r3.group

• Click on ”Install”. This will run the setup file and begin installing the R3 Launcher
application on your computer.
• Wait for R3 Launcher to finish installing. The installation will be completed in a few
seconds.
• Click on ”Finish” to complete the installation process. The R3 Launcher application is
now successfully installed on the system and ready to use.
www.r3.group Page 9 of 45 4. Installation

4.2.2 Internet Connection Sharing
An internet connection is required to update the Bridge E. When you operate the Bridge E in
a separated network without internet connection, you can use ICS to share the connection
from a second network interface (e.g. WiFi). To enable ICS in the application, first select the
network interface that the Brige E is connected to (”EchoRing interface”) and the interface
providing the internet connection (”Internet interface”). Then you can enable ICS using the
toggle switch.
i
NOTE — Due to a problem with Windows 10, enabling Internet Connection Sharing can interrupt the ability
to access the web on the computer sharing the connection.
Suggested courses of action:
• Try connecting to the Internet over Ethernet.
• Try using a WiFi dongle as the problem might be related to certain brands of WiFi cards.
• Install update KB5014669.
• Factory reset the computer.
4.2.3 Configuration Server
The Bridge E is updated using the Configuration Server. To start the Configuration Server,
select the network interface it should be running on (”EchoRing interface”).
!ATTENTION — Do not setup multiple instances of the Configuration Server on the same physical Ethernet
interface.
4. Installation Page 10 of 45 www.r3.group

This interface needs an assigned IP address to run the Configuration Server. Start the
server by clicking the button ”Enable pyRTMF”.
NOTE — PyRTMF is part of the webbased user interface’s front end. i
If no IP address is assigned, the following error prompt will appear:
www.r3.group Page 11 of 45 4. Installation

4.2.4 Set Up and Access Web User Interface
The webbased configuration interface is used for configuring, deploying and updating
devices.
1. Set up and connect a PC running the R3 Configuration Server and the Bridge E devices
1, intended to be in the same network or subnetwork, to the switch 4, according to
Figure 4IV:
1 1 1
2 2 2
3 3 3
4
5
Figure 4IV: Configuration setup
2. Turn on the network switch.
3. Start the R3 Launcher application and start the Configuration Server. The Configuration
Server needs an IP address on the EchoRing interface (either from ICS, a DHCP server,
or assigned manually).
4. Open a web browser and enter the URL http://localhost:8080.
TIP — The webbased user interface is designed for the web browsers Firefox (version 100 or newer)
and Chrome (version 100 or newer). Other browsers may not support full functions.
5. Turn on the Bridge E devices.
4. Installation Page 12 of 45 www.r3.group

4.2.5 Update Devices
TIP — New devices require a software update before use. You must register first to have access to an
update that you can perform. Please visit www.r3.group and download registration form found on the
”Downloads” page.
New devices are already initialized but require an update before use. They require an
internet connection and a Dynamic Host Configuration Protocol (DHCP) and Network Time
Protocol (NTP) server in the network to perform an update. If you are using ICS, the DHCP
and NTP servers are provided by ICS.
Devices will never search or update on their own. This is to assure solution stability.
Updates are assigned on a customer basis. Ask your sales representative about new
versions.
1. Switch power on and pair the devices as described in Section 4.2.4.
2. Click the IP address to update all devices or click the devices that should be updated
individually.
3. Click ”Update Devices”.
4. Click ”Run Update” to install the listed update on each device on the screen.
5. Downloading started and the update will be installed right afterwards.
www.r3.group Page 13 of 45 4. Installation

6. The update is complete. Click ”Mode” to go back to the main page.
4. Installation Page 14 of 45 www.r3.group

4.3 Configuration and Deployment
There are two modes a device can operate in depending on whether the device needs to be
configured or go into deployment.
A device can be configured and updated in Configuration Mode. The device loads the
deployed configuration in Deployment Mode.
New devices will be in Configuration Mode. Once a configuration is successfully deployed,
the device will go into Deployment Mode after the next reboot.
Devices can be reset to Configuration Mode using the Configuration Server:
Once that command is sent to the device, it will return to Configuration Mode after the next
reboot.
The device will go into Fallback Mode if an error occurs during deployment or bootup. In
Fallback Mode, the device can be returned to Configuration Mode using the Configuration
Server as described above.
www.r3.group Page 15 of 45 4. Installation

5 Using the Device
5.1 Basic Concepts
Subnetwork A subnetwork is a network of multiple Bridge E devices where all
participants can communicate directly with each other. Each subnetwork
has its own channel assignment.
Network A network consists of one or more subnetworks. All subnetworks within
a network form a handover domain. If handover is enabled, stations
can roam between subnetworks seamlessly.
Handover The roaming of Mobile Stations between different subnetworks within
one network is called Handover. Mobile Stations do not lose their
connection during the Handover process.
Reconfiguration Mobile Stations can switch between networks (where each network has
its own configuration). The Mobile Station is not able to communicate
during reconfiguration.
Static Station A Static Station is a stationary node in a subnetwork that can be
connected to one or more client devices.
Anchor Station An Anchor Station is a Static Station acting as the central station of a
subnetwork for Mobile Stations using Handover. It requires a connection
to a shared backbone network between all Anchor Stations of other
subnetworks within the same network to support seamless handovers.
Relay Station A Relay Station is not not connected to a network or client device. It is
introduced into a subnetwork to increase reliability without consuming
any additional resources in the subnetwork. Currently only one Relay
Station per subnetwork is supported.
Mobile Station A Mobile Station can seemlessly roam between subnetworks within one
network. Roaming to a new subnetwork needs to be triggered externally.
Mobile Stations can be reconfigured to switch to another network.
5.1.1 Introduction
The Bridge E devices can be used in multiple application scenarios, for example, in storage,
logistics, production or tools.
Let’s take lifting platforms as an example in production. Nowadays large workpieces in
production lines, such as car chassis, are often carried between workstations by lifting
platforms. Complex cable layouts ensure power and realtime data connectivity. Despite
their speed and reliability, cables are constantly subject to wear and tear and are frequently
prone to failure, resulting in expensive downtimes for diagnosis and repairs.
EchoRing revolutionizes M2M communications, combining speed and reliability with the
flexibility of wireless networks. Fewer physical points of failure ensure durable, mobile
setups with far fewer maintenance cycles.
But how does this work?
Let’s stay with the example of the lifting platforms that are used on a shopfloor.
Lifting platforms are stationary conveyor systems embedded in the floor. They are com
monly used for final assembly of vehicles. In this context, lifting platforms are contiguous,
similar to a chain, and move forwards in tandem at low speeds.
5. Using the Device Page 16 of 45 www.r3.group

Let’s assume there are Bridge E devices on each workstation and on each platform. For each
safetycritical production section there is a separate Configuration Zone, which corresponds
to a network. A network can consist of several subnetworks.
The Anchor Station is the central station of a subnetwork. There must be one Anchor
Station per subnetwork. It is connected to a shared network with all Anchor Stations of
other subnetworks to allow signaling.
There can also be Relay Stations in a subnetwork. Relay Stations exist to increase reliability.
They do not take part directly in the network, meaning they do not consume or block any
(temporal) resources in the subnetwork but can be used as a ”relay”. Currently only one
Relay Station per subnetwork is supported.
If a platform runs through a production line, then the Bridge E on this platform is called a
Mobile Station. Mobile Stations which move through the production line can switch between
the subnetworks performing Handovers without interruption.
Each of the sections has its own configuration and its own channel assignments, which
are loaded during downtime between the safetycritical sections. As a result, there is a
(Re)configuration of the Bridge E at the beginning for each configuration zone.
Each network has a defined maximum number of Static and Mobile Stations and a defined
number of transmission slots. Aside from that the level of reliability, the maximum packet
length, the latency and more parameters can be configured.
For each subnetwork it can be chosen on which channel and with which power the Bridge E
devices should operate.
Per Bridge E a capacity factor can be picked (which is limited by the overall network capacity)
e.g. to configure asymmetric traffic. Furthermore each Bridge E can be used either as an
Anchor or as a Relay Station or neither. The MAC address of network components that
should be connected to the Bridge E can be defined as well as if the device should obtain
its IP from a DHCP server or use a static IP.
Further information about all parameters and how to configure them will follow in the next
sections.
www.r3.group Page 17 of 45 5. Using the Device

5.2 Basic Configuration
In order to configure a device, it must be set to Configuration Mode before it is booted.
i
NOTE — If the configuration on a device has exactly one network and one subnetwork (i.e. Static Stations)
then the node will start automatically. Otherwise they are Mobile Stations and need to be started using
External Runtime Control Interface (ERCI) commands (see Section 6.2). The command to enable the
Configuration Mode on future bootups of the Bridge E can be sent by the Configuration Server (see
Section 4.3).
1. To enter the Configuration, click on ”Configure Plant”.
2. Mobile Stations are listed on the left. To add more, click on the ”+”symbol.
3. The different networks with their associated subnetworks are displayed and can be
configured. The networks can be renamed.
You can choose for each subnetwork on which Channel and with which TxPower the
devices should operate. Static Stations can be added to a subnetwork by clicking on
the ”+”symbol.
iNOTE — The maximum number of networks (= configurations) is 20 with no more than 24
subnetworks per network. The maximum number of Channels is 3 for all subnetworks in a network.
5. Using the Device Page 18 of 45 www.r3.group