Features:
- DeviceNet slave role: Connects a compatible ABB drive to a DeviceNet master for cyclic and explicit data exchange.
- Supported messaging: Provides Explicit Messaging, Poll and Change of State/Cyclic services.
- Drive data exchange: Carries mapped commands, references, status, actual values, parameters and diagnostic information.
The adapter provides the fieldbus bridge between the ABB drive option slot and the DeviceNet trunk.
Onboard switches set the network node address and communication rate for the installed network.
A 34-pin drive-side connector and removable 5-pole DeviceNet terminal separate the two physical interfaces.
Apter Power supports ABB RDNA-01 DeviceNet Fieldbus Adapter quotation, technical documentation and configuration review.
ABB RDNA-01 DeviceNet Fieldbus Adapter Manuals,Datasheets,Link
Important Notice: Confirm the drive family, option slot, firmware, node address and DeviceNet communication rate before commissioning.
- Slave operation: The adapter occupies a DeviceNet slave node controlled by the network master.
- Explicit Messaging: Parameter and attribute access is available through non-cyclic requests.
- Poll service: Cyclic command and status exchange can be scheduled by the master.
- Change of State/Cyclic: Event-driven or timed I/O updates follow the configured DeviceNet connection.
- Listed drive families: ABB documents ACS550, ACH550, ACS800, ACQ800 and DCS800 support.
- Option-slot requirement: The drive must provide the correct slot and 34-pin interface for the adapter.
- Firmware boundary: Drive firmware and parameter groups determine the available mapping and control behavior.
- Network boundary: Node address, communication rate and trunk termination must agree with the installed DeviceNet design.
- Status indicators: Adapter LEDs provide the first view of module and network condition.
- Network power: Missing DeviceNet power prevents communication even when the drive is energized.
- Address and rate: A duplicate node or mismatched baud rate keeps the master from establishing the expected connection.
- Data mapping: A healthy network does not by itself prove that control words, references and status values are mapped correctly.
- Drive control networks: Integrates supported ABB drives into a DeviceNet command and reference path.
- Status supervision: Returns mapped drive status and actual values to the supervising master.
- Parameter access: Supports commissioning and service tasks that use Explicit Messaging.
- Event-based I/O: Supports Change of State/Cyclic updates where the DeviceNet system is configured for that service.