Converter OPC UA Client / CANopen - HD67B13-B2
Converter OPC UA Client / CANopen - HD67B13-B2
The ADFweb HD67B13-B2 connects a CANopen network to OPC UA Server data. It accesses OPC UA variables as a Client and exchanges their values through configured CANopen communication. More
Code: HD67B13-B2
The ADFweb HD67B13-B2 connects a CANopen network to OPC UA Server data. It accesses OPC UA variables as a Client and exchanges their values through configured CANopen communication. More
Code: HD67B13-B2
ADFweb HD67B13-B2
OPC UA Client / CANopen
The ADFweb HD67B13-B2 connects a CANopen network to OPC UA Server data. It accesses OPC UA variables as a Client and exchanges their values through configured CANopen communication.
We will check your selection and prepare a quotation
Send us the device models, required connection and quantity.
Converter applications
Use it in installations that need to transfer values between a CANopen device and an existing OPC UA Server. It supports up to 1,500 bytes for reading and 1,500 bytes for writing; addresses and data types must match the connected devices.
Technical specifications HD67B13-B2
| Order code | HD67B13-B2 |
|---|---|
| Protocol connection | OPC UA Client / CANopen |
| Converter roles | OPC UA Client; CANopen |
| Interfaces and ports | CANopen; Ethernet RJ45 |
| Data capacity | 1500 bytes in each direction |
| CANopen data rate | up to 1 Mbit/s |
| CANopen communication | PDO (RPDO/TPDO); SDO Client/Server |
| Power supply | Confirm against the label and hardware version before ordering |
| Consumption at 24 V DC | 4 W |
| Operating temperature | -40 °C to +85 °C |
| Mounting | 35 mm DIN rail |
| Dimensions of the version shown (D × W × H) | 60 × 35 × 95 mm |
| Device weight | approximately 200 g |
| Configuration software | SW67B13 |
We will confirm the supply range for this model against the specific hardware version. Always check the device label before connecting the power supply.
Communication and configuration
In SW67B13, configure the OPC UA Client, CANopen node identifier and data rate. Define OPC UA variables, PDO reception/transmission and SDO Client/Server access using object dictionary indices and subindices.
The OPC UA peer must operate as a Server. CANopen node identifiers, PDO mapping, SDO objects and network state must match. Check OPC UA security requirements against the specific firmware and peer system.
Supply and accessories
Please provide the complete order code. If you need a power supply, connection cables or help with configuration, include them in your enquiry. We will confirm the scope of supply and required accessories for your installation in the quotation.
Documentation and software
Diagrams and hardware version
The images help identify the hardware version. When replacing an older unit, compare its label, connectors and dimensions; we will confirm the version to be supplied in the quotation.
Frequently asked questions
Is knowing the two protocols enough?
The device roles, physical interfaces and data to be transferred must also be checked. The OPC UA peer must operate as a Server. CANopen node identifiers, PDO mapping, SDO objects and network state must match. Check OPC UA security requirements against the specific firmware and peer system.
How is this converter configured?
In SW67B13, configure the OPC UA Client, CANopen node identifier and data rate. Define OPC UA variables, PDO reception/transmission and SDO Client/Server access using object dictionary indices and subindices.
What information should I send to check the selection?
Send the exact device models at both ends, the protocols and communication roles, the number of devices and the required values. For a PLC, include the firmware and method of accessing its data.
FOXON support with selection and ordering
Selection based on your devices
We will review the specific connection, communication roles and required data.
Availability check
Before you place an order, we will confirm current availability and the possible delivery date.
Documentation for the exact order code
We select the documentation and configuration tool using the complete order code.
Accessories for your installation
We will include the requested accessories in the quotation to suit the connection arrangement.
Choosing the correct version
Two devices with the same protocols can have different functions. Check the gateway role on each side, the connectors and the complete order code.
The OPC UA peer must operate as a Server. CANopen node identifiers, PDO mapping, SDO objects and network state must match. Check OPC UA security requirements against the specific firmware and peer system.
Converter enquiry HD67B13-B2
Provide the order code, quantity and the devices you need to connect. We will check the suitable version and prepare a quotation.
Request the converterTechnical specifications HD67B13-B2
| Order code | HD67B13-B2 |
|---|---|
| Protocol connection | OPC UA Client / CANopen |
| Converter roles | OPC UA Client; CANopen |
| Interfaces and ports | CANopen; Ethernet RJ45 |
| Data capacity | 1500 bytes in each direction |
| CANopen data rate | up to 1 Mbit/s |
| CANopen communication | PDO (RPDO/TPDO); SDO Client/Server |
| Power supply | Confirm against the label and hardware version before ordering |
| Consumption at 24 V DC | 4 W |
| Operating temperature | -40 °C to +85 °C |
| Mounting | 35 mm DIN rail |
| Dimensions of the version shown (D × W × H) | 60 × 35 × 95 mm |
| Device weight | approximately 200 g |
| Configuration software | SW67B13 |
We will confirm the supply range for this model against the specific hardware version. Always check the device label before connecting the power supply.