Key Functions

• DeviceNet ↔ CANopen Bidirectional Protocol Conversion:
  Supports real-time, high-reliability data translation between two industry-standard fieldbuses, adhering to their respective protocols:

• DeviceNet: Compliant with ODVA DeviceNet v2.0, supporting master/slave modes, explicit messaging (for configuration/diagnostics) and implicit messaging (for cyclic I/O data), with baud rate compatibility (125 kbps, 250 kbps, 500 kbps).

• CANopen: Compliant with EN 50325-4, supporting NMT (network management), LSS (layer setting services), PDO (process data objects for real-time cyclic data) and SDO (service data objects for acyclic configuration), with baud rate compatibility (10 kbps to 1 Mbps).
  Transmission latency is <15ms, meeting the responsiveness requirements of time-sensitive tasks (e.g., CANopen servo drives triggering DeviceNet actuators based on position feedback).

• Dual Fieldbus Interface Capabilities:
  Each fieldbus interface is designed for industrial robustness and flexibility:

• DeviceNet Interface: Terminal block connection (compliant with ISO 11898) with 2.5kVrms optical isolation—protects against electrical noise, ground loops, and voltage spikes. Supports operation as a DeviceNet master (connecting up to 63 slave devices) or slave (integrating with external DeviceNet masters), adapting to existing network architectures.

• CANopen Interface: 9-pin D-Sub connector (industry-standard for CANopen) with 2.5kVrms optical isolation—ensures stable communication in harsh industrial environments. Supports operation as a CANopen master (managing up to 127 slave devices) or slave (connecting to external CANopen masters), compatible with motion control devices (e.g., Bosch Rexroth drives, Beckhoff I/O).

• Flexible Data Mapping & Configuration:

• SYCON.net Software Support: Configured via Hilscher’s industry-proven SYCON.net platform, allowing users to:

• LSS Configuration for CANopen: Built-in LSS support for CANopen—enables remote setting of CANopen node IDs and baud rates without physical dip switches, simplifying on-site adjustments.

1. Define custom data mapping between DeviceNet I/O points and CANopen PDO/SDO objects (e.g., map DeviceNet sensor values to CANopen PDOs for servo drive control).

2. Import EDS (Electronic Data Sheet) files for DeviceNet devices and CANopen devices—ensuring plug-and-play compatibility with third-party equipment.

3. Save/load configuration templates for batch deployment across multiple gateways, reducing setup time in large-scale systems.

• Request Custom Quote:

• 
  

• 📧 SoulPowerjun@outlook.com

• 
  

• 📱 +86 13306931203