This page should be a collection of which drivers use which combinations of transports and protocols.

It's part of an attempt to make multi-channel drivers easier to manage, as currently the common approach is, to have a main channel and to implement the supplementary channels manually. 

We'd like to change this and make it possible to have multi-channel drivers. Step 1 is to collect what we currently have.

DriverTransportProtocol Description
ab-ethrawab-eth
ads

tcp(48898)

udp(48899)

ads

ads-discovery

Main protocol

Discovery & Management of AMS Routes

bacnetipudp(47808)bacnetipConnections need to share a fixed local port
c-bustcp(10001)c-bus
cansocketcangenericcan
canopensocketcancanopen
eiptcp(44818)eip
firmataserialfirmata
knxnetipudp(3671)knxnetip
mock


modbus


  • modbus-ascii
serialmodbus
  • modbus-ascii (via tcp)
tcp(???)modbus
  • modbus-ascii (via udp)
udp(???)modbus
  • modbus-rtu
serialmodbus
  • modbus-rtu (via tcp)
tcp(???)modbus
  • modbus-rtu (via udp)
udp(???)modbus
  • modbus-tcp
tcp(502)modbus
opcuatcp(4840) (default port not defined in the driver)opcua
open-protocoltcp(4545)open-protocol
plc4xtcp(49837)plc4x
profinet

udp(34964)

udp(50000)

raw

raw

raw



lldp-discovery

pn-dcp-discovery


s7

tcp(102)

tcp(???) (Only for HA)

s7

s7


simulated


  • No labels