1. Manuals
  2. Brands
  3. R3 Manuals
  4. Network Hardware
  5. Bridge E
  6. User manual

R3 Bridge E User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this 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 · contact@r3.group
www.r3.group

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Bridge E and is the answer not in the manual?

Questions and answers

Summary of Contents for R3 Bridge E

  • Page 1 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 · contact@r3.group www.r3.group...

  • Page 2: Table Of Contents

    4.2.1 R3 Launcher Application........

  • Page 3: General Terms Of Use Of This Document

    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.

  • Page 4: Please Observe The Following Notes

    — 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. EXAMPLE/NOTE — Text in this format provides examples or notes. Page 2 of 45 2. Please Observe the Following Notes www.r3.group...

  • Page 5: Product Information

    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.

  • Page 6: Equipment Required

    3 meters. Switch Possibility to disable IGMP Snooping; at least as many ports as Bridge E devices should be connected + 2 Page 4 of 45 3. Product Information www.r3.group...

  • Page 7: Connectors

    • Config 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. Page 5 of 45 www.r3.group 3. Product Information...
  • Page 8 Inconclusive; a specific mode might have been exited (depending on context). Table 3­iii: Explanation of LEDs — 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 •...

  • Page 9: Installation

    Figure 4­II: DIN rail mounting 3. Push the device downwards so that it snaps into place. Applies to both versions of the Bridge E. — To release device from DIN rail, push the device downwards while pulling outwards. 4.1.2 Wall or Mast Mounting —...

  • Page 10: Software 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.
  • Page 11 • 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.

  • Page 12: Internet Connection Sharing

    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...
  • Page 13 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. If no IP address is assigned, the following error prompt will appear: www.r3.group Page 11 of 45 4. Installation...

  • Page 14: 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 , intended to be in the same network or subnetwork, to the switch , according to Figure 4­IV:...

  • Page 15: Update Devices

    4.2.5 Update Devices — 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.
  • Page 16 6. The update is complete. Click ”Mode” to go back to the main page. 4. Installation Page 14 of 45 www.r3.group...

  • Page 17: Configuration And Deployment

    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. Page 15 of 45 www.r3.group 4. Installation...

  • Page 18: Using The Device

    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.
  • Page 19 (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.

  • Page 20: Basic Configuration

    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).
  • Page 21 • Exact Config: In this setting, all input parameters are set as specified if the input parameters provide a valid configuration. Page 19 of 45 www.r3.group 5. Using the Device...
  • Page 22 • External Relay Stations increase the reliability. They do not consume or block (temporal) resources in the subnetwork, but support data exchange between other Bridge E devices. Currently only one Relay Station per subnetwork is supported. Page 20 of 45 5.
  • Page 23 Routes: The MAC address of one or more customer network components that are to be connected to the Bridge E. Enable DHCP Client: The device should obtain its IP from a DHCP server. Static IP: If DHCP is disabled, this static IP will be the device’s IP address.

  • Page 24: Advanced Configuration

    All traffic that does not match the filter is treated as ”Best Effort” and thus will be sent after all priority traffic. The latency drop rule is not applied to ”Best Effort” traffic. Page 22 of 45 5. Using the Device www.r3.group...
  • Page 25 To customize queue sizes, queue sizes need to be configured for all priorities that have been assigned in the Traffic Filter section. If possible, the available buffers will be assigned as specified, any additional buffers will be distributed equally among all queues. www.r3.group Page 23 of 45 5. Using the Device...

  • Page 26: Broadcast Repetition

    Backbone Port and a multicast IP equal to the Backbone IP appended with subnet ID. It enables Anchor Stations to communicate with each other using a multicast address formed by appending the Target subnet ID to Backbone IP. Page 24 of 45 5. Using the Device www.r3.group...

  • Page 27: Static Ip

    — The Bridge E goes into Fallback Mode if the config flag is not set (i.e. in Deployment Mode), but the config check fails. Since the configuration in the Bridge E is not usable and therefore no static IP settings either, DHCP will be used.

  • Page 28: Deployment

    4. The deployment process cannot be started while the configuration is unlocked, so finish modifying the configuration first. Then click on ”Lock” and redeploy all devices. Page 26 of 45 5. Using the Device www.r3.group...

  • Page 29: Change Configuration

    The database contains all adjustments made in the Plant Configuration. The current database can be downloaded using ”Export”. A previously saved database can be uploaded using ”Import”. ATTENTION — All previous settings will be overwritten when you import a database. Page 27 of 45 www.r3.group 5. Using the Device...

  • Page 30: Troubleshooting

    → MEA, update → UPD). Hover over the labels to see the full subprotocol name. The version numbers on the labels must be the same, so that the Configuration Server and the devices can communicate in the domain concerned. Page 28 of 45 6. Troubleshooting www.r3.group...

  • Page 31: Different Regularity Domains

    ”CON: 5” would appear with gray background. INFO — To configure an Bridge E, it needs to use the same configuration subprotocol (CON) version as the Configuration Server. To update an Bridge E, it needs to use the same update subprotocol (UPD) version as the Configuration Server.

  • Page 32: Erci Specification

    Initialization If the configuration of a Bridge E only consists of a single network with a single subnetwork, the configuration is auto deployed and the Medium Access Control (MAC) started for Static Stations. This is not the case for Mobile Stations.
  • Page 33 → Wrong format Ring ID and Wrong State Antenna ID to 0 → Not in RUNNING (=invalid) Generic Error → Error in processing request Command 1B Command ­ Result Result Code, NULL terminated result description Page 31 of 45 www.r3.group 6. Troubleshooting...
  • Page 34 → Error in processing request 12..127 Not used yet 128..255 Reserved Command Result Codes Value Result 0..64 [Reserved] Success 66..69 [Reserved] Generic Error Wrong State Invalid Message Received Invalid Data Received No Config Available Page 32 of 45 6. Troubleshooting www.r3.group...
  • Page 35 The device is in a unrecoverable fault state and needs to be reset. MAINTENANCE The device is busy with other activities (i.e. updating, Configuration Mode, ...). CONFIGURED The device has been configured and is ready to be started (or reconfigured). State Diagram Page 33 of 45 www.r3.group 6. Troubleshooting...

  • Page 36: List Of Acronyms

    Sub­Miniature Version A..............7 Internet Connection Sharing ............. 8 Network Time Protocol ..............13 DHCP Dynamic Host Configuration Protocol ..........13 ERCI External Runtime Control Interface ............ 18 Medium Access Control ..............30 User Datagram Protocol..............30 Page 34 of 45 Acronyms www.r3.group...

  • Page 37: Product Change Notifications

    Reliability Impact minor major none Reason for change: As the product portfolio of R3 Solutions grows, new product names are necessary to differentiate product families better. Implementation date: 18-AUG-2022 R3 Solutions GmbH · www.r3.group Kurfürstendamm 21 · 10719 Berlin · Germany · contact@r3.group...
  • Page 38 Product Change Notification Form Contact details: Thomas Menzel, Lead Application Engineer thomas.menzel@r3.group Jürgen Heyer, Account Executive juergen.heyer@r3.group Affected part number(s) ER-EB 1000M R3 Solutions GmbH · www.r3.group Kurfürstendamm 21 · 10719 Berlin · Germany · contact@r3.group...
  • Page 39 R3 Solutions GmbH Appendix for PCN# PCN-E-001 - PCN Name change EREB to Bridge E (1 ANT) – 18-AUG-2022 Exhibit 1 New Code Marking (Lable) Face Plate Print...
  • Page 40 R3 Solutions GmbH Appendix for PCN# PCN-E-001 - PCN Name change EREB to Bridge E (1 ANT) – 18-AUG-2022 Exhibit 2 Existing Code Marking 1...
  • Page 41 R3 Solutions GmbH Appendix for PCN# PCN-E-001 - PCN Name change EREB to Bridge E (1 ANT) – 18-AUG-2022 Existing Code Marking 2 Existing Code Marking 3...
  • Page 42 R3 Solutions GmbH Appendix for PCN# PCN-E-001 - PCN Name change EREB to Bridge E (1 ANT) – 18-AUG-2022 Existing Code Marking 4...
  • Page 43 R3 Solutions GmbH Appendix for PCN# PCN-E-001 - PCN Name change EREB to Bridge E (1 ANT) – 18-AUG-2022...
  • Page 44 The product package now includes one Bridge E device, one antenna, and one IP65- compatible lid to seal an antenna port if not in use.
  • Page 45 Product Change Notification Form Contact details: Thomas Menzel, Lead Application Engineer thomas.menzel@r3.group Jürgen Heyer, Account Executive juergen.heyer@r3.group Affected part number(s) ER-EB 1000M-2 (formerly ER-EB 1000M) R3 Solutions GmbH · www.r3.group Kurfürstendamm 21 · 10719 Berlin · Germany · contact@r3.group...
  • Page 46 R3 Solutions GmbH Appendix for PCN# PCN-E-002 – PCN 2ANT – 20-AUG-2022 Appendix New Code Marking (Lable) Face Plate Print...
  • Page 47 R3 Solutions GmbH Appendix for PCN# PCN-E-002 – PCN 2ANT – 20-AUG-2022...
  • Page 48 UM­ER­EB1000M­20221031­EU R3 Solutions GmbH · Kurfürstendamm 21 · 10719 Berlin · Germany · contact@r3.group www.r3.group...

This manual is also suitable for:

Er-eb 1000mEr-eb 1000m-2

Table of Contents