I have inherited a system that utilizes a Parker ACR9000 motion controller with the Ethernet PowerLink option to control five Parker Compax3 servo drives. Each device is equipped with a two-port Ethernet PowerLink option board, currently set up in a simple "daisy chain" configuration. The ACR9000 communicates with ACR-View 6 software and a custom Windows application via a separate Ethernet port connected to an unmanaged switch. While the Compax3 can communicate over Ethernet PowerLink and TCP/IP through the EPL port on TCP ports 44821 and 44822, as well as RS-232 and RS-485 on its serial port, I have limited experience with Ethernet PowerLink. It is known for being fast and easy, operating similar to CANOpen over Ethernet, and compatible with ordinary Ethernet switches. However, my concern lies in the potential impact on my network if I connect the Ethernet PowerLink daisy-chain to the unmanaged switch. Will this result in Ethernet PowerLink frames congesting the network for normal Ethernet TCP/IP devices and PLCs? Is a "gateway" necessary to separate the real-time traffic from the LAN? Would a switch with VLAN routing suffice, and does Ethernet PowerLink support VLAN tags?
I have previously utilized Hischler gateways with older Parker servos, although it has been quite some time. If you're in need of a gateway, Anybus offers a solution. The Anybus Ethernet Powerlink 2023 provides seamless integration with various fieldbus and Industrial Ethernet networks. This gateway also comes equipped with integrated Powerlink connectivity through Anybus CompactCom. For more information and to explore your options, visit www.anybus.com.
Based on my observations of B&R Powerlink, all Powerlink devices operate within the 192.168.100.xx network. The unit number on each device corresponds to the host number in the IP address. Since Powerlink uses a broadcast protocol, it is recommended to separate it from your main network. Setting up a NAT router and using 1:1 mappings can help isolate the broadcast traffic and enable TCP/IP access to the individual devices. Consider this approach to enhance network security and efficiency for your Powerlink devices.
Hey Ken, I wanted to share with you the specifications for Ethernet Powerlink. Here's a link for you to check out: Powerlink specification for Ethernet.
Hello everyone! When I read the specifications and white papers, it reminds me of the challenge of transitioning from DH+ and Modbus Plus to Ethernet. I am particularly concerned about having raw Ethernet frames on my switch, not only for its switching speed but also for the potential impact on the customer PC and my HMI. I wonder if your average PLC or HMI device can handle a PowerLink network. It seems like those writing specifications and whitepapers are hesitant to provide clear guidance on what can be connected to the EPL network. To address this challenge, I plan to install a Red Lion DA50D, which features two separate, isolated Ethernet ports. This setup will allow me to connect one port to the customer PC and ACR9000's programming port, while the other connects to the EPL network containing the Compax3's. For testing purposes, I will utilize a Red Lion DSPSX and my PC's NIC by connecting them to the daisy-chain of the EPL network. I am eager to see how they perform in this setup.
Confirmation has been received that an EPL network typically operates with TCP/IP on the 192.168.100.x subnet, with the host number representing the PowerLink node. This highlights the necessity for a router, bridge, or NAT device to facilitate communication between these networks. This is crucial as my enterprise connection utilizes the 192.168.10.x subnet, with addresses that are unfortunately hard-coded into compiled executables.
While Ethernet PowerLink is indeed renowned for its speed and ease, you're correct to be concerned about potential network congestion. Connecting PowerLink to an unmanaged switch can certainly result in your main network getting bogged down. However, a gateway isn't necessarily a must. An alternative solution could be to utilize managed switches with VLAN capabilities. This way, you can isolate your PowerLink traffic from your regular network traffic, preventing any unwarranted congestion. To my knowledge, Ethernet PowerLink does not inherently support VLAN tags but segregating the traffic at the switch level should provide an effective workaround. I'd recommend carrying out some small-scale tests first before deployment.
It's great that you're diving into the intricacies of Ethernet PowerLink! Your concern about potential network congestion is valid. When you connect your Ethernet PowerLink daisy-chain to an unmanaged switch, the real-time traffic from the motion controller might contend with regular TCP/IP traffic, which could lead to latency issues depending on your network's load. While Ethernet PowerLink does not inherently support VLAN tagging, using a managed switch with VLAN capabilities can help isolate real-time communication from standard network traffic, thus preventing congestion and ensuring that your servo drives operate smoothly. A gateway isn't strictly necessary, but implementing VLANs through a managed switch is definitely a step in the right direction for optimizing performance!
It's great that you're diving into Ethernet PowerLink; it can be a bit tricky but very rewarding once you've got it set up right. Your concern about network congestion is valid—since Ethernet PowerLink is real-time oriented, mixing it with regular TCP/IP traffic on the same unmanaged switch could lead to issues, especially if there's a lot of non-time-critical data being transmitted. A dedicated switch for your PowerLink devices would be ideal, but if you're considering using VLANs, ensure that your switch can handle them effectively. While Ethernet PowerLink does not inherently support VLAN tagging, a VLAN-capable switch can help prioritize the traffic, reducing the risk of delays. So, in short, while you can technically connect everything to one switch, separating real-time and non-real-time data with appropriate hardware is a best practice to maintain performance and reliability.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Integrating Ethernet PowerLink into your network may congest the network for normal Ethernet TCP/IP devices and PLCs. Consider separating real-time traffic from the LAN using a gateway or a switch with VLAN routing.
Answer: Answer: Using a gateway can help separate real-time Ethernet PowerLink traffic from the LAN, ensuring smoother communication and reducing congestion for other devices on the network.
Answer: Answer: Using a switch with VLAN routing capabilities can assist in managing Ethernet PowerLink integration by segregating traffic and ensuring efficient communication. Consider checking if Ethernet PowerLink supports VLAN tags for better network organization.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.