Converter Modbus TCP Server / KNX - HD67815-KNX-B2
Converter Modbus TCP Server / KNX - HD67815-KNX-B2
The ADFweb HD67815-KNX-B2 exposes KNX TP bus values to a Modbus TCP Client system. It operates as a Modbus TCP Server on the Modbus side and responds to requests from the supervisory device. More
Code: HD67815-KNX-B2
The ADFweb HD67815-KNX-B2 exposes KNX TP bus values to a Modbus TCP Client system. It operates as a Modbus TCP Server on the Modbus side and responds to requests from the supervisory device. More
Code: HD67815-KNX-B2
ADFweb HD67815-KNX-B2
Modbus TCP Server / KNX
The ADFweb HD67815-KNX-B2 exposes KNX TP bus values to a Modbus TCP Client system. It operates as a Modbus TCP Server on the Modbus side and responds to requests from the supervisory device.
We will check your selection and prepare a quotation
Send us the device models, required connection and quantity.
Converter applications
Use it to connect an existing PLC or supervisory application to KNX values. It provides bidirectional mapping of up to 1,440 bytes for reading and 1,440 bytes for writing.
Technical specifications HD67815-KNX-B2
| Order code | HD67815-KNX-B2 |
|---|---|
| Protocol connection | Modbus TCP Server / KNX |
| Roles and version | Modbus TCP Server; KNX TP |
| Interfaces and ports | KNX TP; Ethernet RJ45 |
| KNX TP data rate | 9 600 bit/s |
| Data capacity | 1440 bytes in each direction |
| Converter power supply | 8-24 V AC / 12-35 V DC |
| Consumption at 24 V DC | 3.5 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 | SW67815 |
For an older device, check the hardware version and connections against its label.
Communication and configuration
In SW67815, configure Modbus TCP network parameters, the KNX device address and telegram reception and transmission. Map Modbus registers to KNX group addresses and define the meaning of the transferred data.
An external Modbus TCP Client must send read and write requests. This model does not independently poll other Modbus Servers or Slave units; check the communication roles of both sides when selecting it. The converter uses a TP bus on the KNX side. Prepare group addresses, data types and the required transfer direction; check the power supply for both the KNX bus and the converter.
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. An external Modbus TCP Client must send read and write requests. This model does not independently poll other Modbus Servers or Slave units; check the communication roles of both sides when selecting it. The converter uses a TP bus on the KNX side. Prepare group addresses, data types and the required transfer direction; check the power supply for both the KNX bus and the converter.
How is this converter configured?
In SW67815, configure Modbus TCP network parameters, the KNX device address and telegram reception and transmission. Map Modbus registers to KNX group addresses and define the meaning of the transferred data.
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.
An external Modbus TCP Client must send read and write requests. This model does not independently poll other Modbus Servers or Slave units; check the communication roles of both sides when selecting it. The converter uses a TP bus on the KNX side. Prepare group addresses, data types and the required transfer direction; check the power supply for both the KNX bus and the converter.
Converter enquiry HD67815-KNX-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 HD67815-KNX-B2
| Order code | HD67815-KNX-B2 |
|---|---|
| Protocol connection | Modbus TCP Server / KNX |
| Roles and version | Modbus TCP Server; KNX TP |
| Interfaces and ports | KNX TP; Ethernet RJ45 |
| KNX TP data rate | 9 600 bit/s |
| Data capacity | 1440 bytes in each direction |
| Converter power supply | 8-24 V AC / 12-35 V DC |
| Consumption at 24 V DC | 3.5 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 | SW67815 |
For an older device, check the hardware version and connections against its label.