Why Vibration Data Belongs in the PLC
The 3500 protects the machine with hard-wired relays. The PLC adds trends and alarms. First, you see orbit plots on the HMI. Second, you catch slow bearing wear early. Moreover, ControlLogix logs the data for the reliability team. However, the 3500 must keep its SIL role. Therefore, never route trips through the PLC. The relays stay the final line. Finally, treat the network link as information only, not protection.
Building the EtherNet/IP Link
The 3500/22M Transient Data Interface is the bridge. It speaks EtherNet/IP. First, set the gateway IP on the same subnet as the PLC. Second, add the 3500 EDS file to Studio 5000. Moreover, create a generic Ethernet module for the gateway. However, use explicit messaging, not I/O assembly. Therefore, you poll only the tags you need. Finally, set the RPI to 500 ms to limit traffic. A fast RPI floods a small network.
Step-by-Step Integration
- Step 1: Configure the 3500/22M IP and subnet mask in the frame setup.
- Step 2: Import the EDS into Studio 5000. Name the module "BN3500".
- Step 3: Build a MSG instruction. Pick "Get Attribute Single" for each tag.
- Step 4: Map 1X, 2X, and gap voltage to DINT tags in the controller.
- Step 5: Trend the tags in FactoryTalk. Confirm the values track the rack.
Exposing Data with OPC UA
The DCS often prefers OPC UA over native Rockwell tags. Use a server to bridge. First, enable the OPC UA server on the edge node. Second, browse the ControlLogix tags as nodes. Moreover, set a 1,000 ms publish rate for trends. However, lock the certificate to avoid rejected sessions. Therefore, export the server cert to the client store. Finally, test a cold subscribe after a power loss. A missing cert stops the link silently.
Diagnosing a Comms Drop
A frozen trend hides a real fault. Find the break with this plan:
- Step 1: Ping the 3500/22M from the PLC subnet. Check the reply.
- Step 2: Read the MSG .ER error code in Studio 5000.
- Step 3: Open the 3500 frame LCD. Confirm the gateway shows "Link OK".
- Step 4: Swap the cable. A kinked shield drops packets under load.
- Step 5: Review the OPC UA session log. Fix a rejected certificate.
Moreover, check the switch port for CRC errors. A noisy port breaks the poll. Therefore, move the link to a managed VLAN with storm control.
Conclusion & Action Advice
Allen-Bradley ControlLogix and Bently Nevada 3500 work well together. Keep the 3500 relays as the trip path. Pull vibration data over EtherNet/IP for insight. Expose it with OPC UA for the wide plant. Therefore, you gain early warning without risking the machine. Document the MSG tags in the P&ID notes. Finally, alarm on a comms loss so a dead link never hides a fault.