Tips for Communicating with DeviceNet Modules: A Guide to Updating Outdated Technology

The initial image showcases a vampire clamp used for connecting to a flat DeviceNet cable.

• 17-01-2025
• alan_505

In a comment, alan_505 mentioned using a vampire clamp to attach a flat DeviceNet cable in the first photo. This specialized connector is designed for flat cables, making it compatible with various devices.

• 17-01-2025
• jjwitty

Ah, the old 160 drives - I recall their tendency to explode. The later series is said to have addressed this issue, resulting in fewer incidents but not eliminating them entirely. While not directly related to your query, I recommend considering a system upgrade to incorporate more modern technology. The Flex rack remains a dependable option when paired with an AENT, as everything else displayed is outdated. It may be time to update and enhance your system for improved performance and reliability.

• 17-01-2025
• 5618

More than a decade ago, I faced the challenge of migrating a panel filled with 160 series drives on DeviceNet. After researching, I discovered that ABB ACS355 with FDNA-01 adapters could be a suitable replacement with a similar size. Despite encountering some issues with rerouting power and configuring RSNetworx with ABB eds files, I successfully upgraded two out of many drives before leaving the company. The 160 series drives were appreciated for their time, especially for their convenient top power input. It's nostalgic to think back on the days when VFDs had fewer than a thousand parameters.

• 17-01-2025
• OkiePC

The cabinets and equipment shown have undergone some basic maintenance over the years, which has kept them operational. However, it is crucial for the system owner to have a migration and disaster-recovery plan in place. Without the necessary software and hardware tools, options include hiring assistance or investing in these tools and learning how to use them effectively. In a scenario with budget constraints, one can request a trial version of RSNetworx from a distributor and purchase a serial 1770-KFD in the secondary market. This allows for uploading the 1747-SDN configuration, identifying Node 00, and plugging in a pre-configured 160-DN2 into each drive to capture configurations. This process provides essential disaster-recovery information for drive configurations and facilitates easy replacement when needed. With a budget for RSNetworx, the approach remains similar but involves less manual effort and a more streamlined network configuration process. This is essential for efficient maintenance and management of the drives in the system.

• 17-01-2025
• Ken Roach

I once encountered a customer facing severe issues with Bulletin 160 drives connected to their conveyors, resulting in a company-wide restriction on DeviceNet installations. The root of the problem was not the network itself, but rather the lack of grounding in their conveyors, causing them to act as massive static generators like Van De Graff machines. This led to discharge through the drive control modules once the potential exceeded the isolation capability of the DNet adapters. Maintenance workers would often receive painful shocks while servicing the machines, mistakenly attributing the issue to the network when the drives went into red-light mode due to static discharge. Years later, I hired a former controls engineer from the same company who validated the challenges faced with those systems. He candidly questioned, "Why couldn't they resolve the DeviceNet issue?"

• 17-01-2025
• Ken Roach

A decade ago, I faced the challenge of migrating from a panel of 160 series drives on DeviceNet. My solution was to switch to ABB ACS355 drives with FDNA-01 adapters, which had a similar footprint and worked well on DeviceNet. Despite some difficulties with rerouting power and RSNetworx compatibility, I successfully completed a few conversions before moving on. I appreciated the practicality of the 160 series drives, especially their top power input. Those were the days when VFDs had fewer parameters to manage. Now, I feel confident in my ability to integrate Powerflex and ENET Flex IO systems. By reusing existing wiring supplying both DeviceNet and VFDs, this approach seems very feasible.

• 17-01-2025
• jjwitty

Ken Roach mentioned that the cabinets and equipment shown have undergone some makeshift maintenance over time, highlighting the importance of implementing a migration and disaster-recovery plan. Without the necessary software and hardware tools, the system owner must consider either hiring help or investing in the tools and learning how to use them. In a tight budget scenario, seeking a trial version of RSNetworx and purchasing a serial 1770-KFD from the aftermarket could be a viable solution. This would involve uploading the 1747-SDN configuration and saving the configurations for disaster-recovery purposes. Identifying DeviceNet network addresses and mapping data in the PLC program would be crucial steps in this process. As the lone controls specialist in an oil bottling plant, the urgency of upgrading the outdated technology is clear. Even though cleaning is not a daily priority, the implications of equipment failure should not be underestimated. Recommending the migration to PF 525 and Flex systems is a proactive step towards ensuring operational efficiency and minimizing potential downtime. With proper planning and implementation, the management can avert a crisis before it occurs.

• 17-01-2025
• jjwitty