UD51 Unidrive Classic UD51

SKU: UD51 Category: Drive

Description
Additional information

The Control Techniques Unidrive Classic UD51 is an optional plug-in Solutions Module designed for use with the Unidrive Classic series of AC variable speed drives. The UD51 is a DeviceNet communications interface module, enabling the Unidrive Classic drive to be integrated into DeviceNet industrial networks. It fits directly into the drive's option module slot, extending the drive's connectivity without requiring external hardware.

The UD51 module supports the DeviceNet protocol, allowing the host Unidrive Classic drive to exchange process data and parameter information with a DeviceNet master controller. The module supports both polled and change-of-state (COS) I/O messaging, as well as explicit messaging for parameter read/write access. Data rates of 125 kbps, 250 kbps, and 500 kbps are supported, with node address and baud rate configurable via onboard rotary switches. The module draws its power from the host drive's internal bus, requiring no separate power supply.

The UD51 is commonly used in manufacturing and process automation environments where DeviceNet fieldbus networks are the standard communication infrastructure, particularly in North American industrial installations. Typical applications include conveyor systems, pumps, fans, compressors, and general-purpose machine drives where centralized PLC-based control via DeviceNet is required. The module is suited to any application where the Unidrive Classic must be supervised and commanded by a DeviceNet master such as an Allen-Bradley ControlLogix or SLC 500 system.

Technical Specifications

Communication Protocol	DeviceNet
Supported Data Rates	125 kbps, 250 kbps, 500 kbps
I/O Messaging	Polled, Change-of-State (COS), Cyclic
Explicit Messaging	Supported (parameter read/write)
Node Address Configuration	Rotary switches (0–63)
Baud Rate Configuration	Rotary switches
Host Interface	Unidrive Classic option module slot
Power Supply	Powered from host drive internal bus
Module Format	Plug-in Solutions Module
Compatible Drive Series	Unidrive Classic
Operating Temperature	0 °C to 40 °C
Certifications	CE

Common Fault Codes

Net Fault: DeviceNet network communication loss detected by the UD51 module; the drive has lost communication with the DeviceNet master.
Check DeviceNet cabling, termination resistors at both ends of the network, and verify the master controller is online and scanning the node correctly.
Node Address Conflict: The node address set on the UD51 rotary switches conflicts with another device on the DeviceNet network.
Power down the drive, set a unique MAC ID on the UD51 rotary switches, and restart the network.
Bus Off: The UD51 module has detected excessive errors on the DeviceNet bus and has taken itself offline to prevent further disruption.
Inspect DeviceNet wiring for shorts, open circuits, or missing termination. Check for correct cable type (DeviceNet thick/thin cable) and verify power supply to the network.
Idle Fault: The DeviceNet master has placed the network in idle state, causing the drive to receive no valid control data.
Verify the master controller program is running and actively scanning the UD51 node. Check the master's I/O configuration for the node.
Trip: CL.bit: The Unidrive Classic has tripped due to a control word bit condition received via the UD51 DeviceNet module, indicating an invalid or unexpected command from the network master.
Review the control word being sent by the DeviceNet master. Ensure the command sequence follows the Unidrive Classic control state machine requirements.
Trip: SL.Er: Solutions Module error trip on the Unidrive Classic host drive, indicating a fault in communication between the drive and the UD51 module.
Re-seat the UD51 module firmly in the option slot. If the fault persists, check for physical damage to the module connector and replace the UD51 if necessary.

Frequently Asked Questions

Which drives is the UD51 compatible with?

The UD51 is designed exclusively for use with the Control Techniques Unidrive Classic series of AC drives. It is not compatible with later Unidrive SP or Unidrive M series drives, which use different option module formats.

What fieldbus protocol does the UD51 support?

The UD51 supports the DeviceNet protocol, which is a CAN-based industrial network standard commonly used in North American automation systems.

How is the node address set on the UD51?

The node address (MAC ID) and baud rate are configured using onboard rotary switches on the UD51 module, allowing addresses from 0 to 63 to be set without software tools.

Does the UD51 require a separate power supply?

No, the UD51 draws its operating power directly from the Unidrive Classic host drive's internal option module bus, so no external power supply connection is required for the module itself.

Can the UD51 be used for both speed control and parameter access?

Yes, the UD51 supports both cyclic I/O messaging for real-time speed and torque control, and explicit messaging for reading and writing drive parameters over the DeviceNet network.

Troubleshooting

Drive does not respond to DeviceNet commands after UD51 installation

Verify the UD51 module is fully seated in the option slot and that the drive recognizes the module. Check that the node address and baud rate switches are set correctly and match the master configuration.

Re-seat the UD51 module, confirm the MAC ID and baud rate match the DeviceNet master scanner configuration, and ensure the master's EDS file for the UD51 is correctly installed and the node is enabled in the scanner's I/O list.

UD51 module shows Bus Off condition or network errors

Inspect the DeviceNet cable connections at the UD51 and throughout the network segment. Measure network voltage (nominally 24 V DC on the network power conductors) and check for correct 121-ohm termination resistors at both physical ends of the trunk cable.

Replace any damaged cabling, install correct termination resistors at both ends of the DeviceNet trunk, and ensure the network power supply is within specification. Reduce cable length or switch to thick DeviceNet cable if signal integrity is poor.

Unidrive Classic trips with SL.Er fault after UD51 is installed

The SL.Er trip indicates a communication failure between the drive's internal processor and the UD51 Solutions Module. This is often caused by a poorly seated module or a damaged option slot connector.

Power down the drive, remove the UD51, inspect the module and slot connector for bent pins or contamination, and re-insert the module firmly. If the fault persists, test with a known-good UD51 module to determine whether the module or the drive option slot is faulty.

DeviceNet master reports the UD51 node as offline or not found

Check that the UD51 node address matches the address configured in the master scanner's I/O list. Verify DeviceNet network power is present and that the UD51 is powered (host drive must be powered on).

Correct any node address mismatch using the UD51 rotary switches, ensure the Unidrive Classic drive is powered and operational, and confirm the DeviceNet network supply voltage is within the 11–25 V DC range at the node connection point.

Condition	Repair, Used, Refurbished, New in box (sealed)