ABB DSQC 351 3HNE 00006-1 DeviceNet/Interbus Gateway Module

Description

The ABB DSQC 351 3HNE 00006-1 is a specialized communication gateway module designed for industrial robot control systems, including the ABB IRC5 controller platform. It functions as a protocol translator interface between an internal DeviceNet network and an external Interbus fieldbus architecture. By enabling structured cyclic and acyclic data exchange between distinct fieldbus protocols, the module allows the main controller to integrate seamlessly into complex automated production lines and distributed process control environments.

Engineered to fit into designated option expansion slots inside the IRC5 Control Module, the ABB DSQC 351 connects to the internal DeviceNet master bus (such as the DSQC 603 master) and acts as an Interbus interface node. This setup enables real-time transmission of digital/analog operational signals, safety interlocks, status monitoring messages, and supervisory control commands between the robot controller and higher-level PLCs or distributed I/O systems across the plant floor.

Features

• Dual-Protocol Gateway Architecture: Enables seamless protocol conversion and signal mapping between DeviceNet and Interbus fieldbus networks.
• IRC5 Controller Compatibility: Designed for mounting on internal mounting rails within the ABB IRC5 Control Module customer expansion area.
• Standardized Terminal Interfaces: Utilizes front-facing Phoenix Combicon pluggable connectors to facilitate reliable field wiring and quick module swapping.
• Compact DIN Rail Mounting: Features a snap-on mechanical retention mechanism with a manual release lever for secure panel assembly.
• Real-Time Data Transmission: Supports rapid cyclic I/O signal exchange and parameter mapping for precise industrial automation synchronization.
• Centralized System Integration: Streamlines communication between the main robot controller, supervisory PLCs, and secondary automation equipment.

Applications

• Automotive & Robotic Assembly Lines: Connects IRC5 robot controllers to main Interbus-based factory control networks for coordinated cell operations.
• Distributed Material Handling: Integrates robot controllers with supervisory PLCs, transfer lines, and conveyor tracking systems across long distances.
• Packaging & Palletizing Cells: Facilitates multi-device communication between robot controllers, safety gateways, and external fieldbus networks.
• Industrial Robot System Retrofits: Upgrades existing IRC5 robot cells to interface with legacy or specialized Interbus automation infrastructure.

Technical Specifications

Connections / Interfaces

Installation Guidelines

1. Safety Verification: Switch off the main power switch on the IRC5 Control Module and ensure power to all connected external equipment is disconnected before opening the cabinet.
2. ESD Protection: Attach an ESD grounding wrist strap to the designated grounding post on the computer unit inside the control cabinet.
3. Mechanical Mounting: Locate an available slot on the customer plate mounting rail inside the IRC5 Control Module. Snap the DSQC 351 module onto the rail until securely latched. Pull the release lever if necessary to facilitate proper alignment.
4. Wiring Integration: Connect the internal DeviceNet communication harness and attach the external Interbus fieldbus cabling to the front Phoenix Combicon connectors. Ensure all pluggable terminal blocks are firmly seated and tightened.
5. Pre-Power Inspection: Verify signal polarity, ground connections, and fieldbus cabling integrity prior to re-energizing the controller cabinet.

Configuration Guidelines

1. System Definition: Configure the new gateway node within the IRC5 system software (RobotStudio / RobotWare System Builder) to match the physical hardware configuration.
2. Signal & Bus Mapping: Define I/O signal mappings, station addresses, and baud rates according to the application's fieldbus requirements as detailed in the relevant ABB application manual for the bus system.
3. Backup Settings: Perform a full system backup of the controller configuration parameters once communication between the DeviceNet and Interbus networks is verified.