+1

I would follow the most common naming convention and call the drivers the
following:
- Modbus ASCII
      - Supported Devices: Any Device Supporting Modbus ASII, Any Modbus
ASCII Comliant PLC, Flow Computers
- Modbus TCP/ IP (What is Modbus TCP/IP ? | Modbus Tcp/ip vs Ethernet ip -
The Automization <https://theautomization.com/what-is-modbus-tcp-ip/>)
    - Supported Devices: Applicom: Generic Modbus, TSX Premium, TSX
Quantum, Fluenta FGM, Instromet, Mailbox, Modbus Ethernet, Roxar RFM
- Modbus Plus (Difference between Modbus & Modbus Plus | Instrumentation
and Control Engineering (automationforum.co)
<https://automationforum.co/difference-between-modbus-modbus-plus/> )
      - Supported Devices: AT-984 Programmable Controller Board, Hilscher
CIF Card, Modbus Plus ISA PC Adapter Card, Modbus Plus PCI PC Adapter Card,
Modbus Plus Type II PCMCIA Card, Modbus Plus Type III PCMCIA Card, Modbus
Plus Type III PnP PCMCIA Card, SA85 (-002 and -001) PC Interface Cards,
SA85-PCI
- Modbus Serial
    - Supported Devices: Daniel S500 Flow Computer, Dynamic Fluid Meter,
Elliot Flow Computer, Magnetek GPD 515 Drive, Modbus Compatible Devices,
Omni Flow Computer (Enron Modbus), TSXCUSBMBP USB Adapter
- Modbus RTU Server Serial
    - Any Modbus compatible devices

Modbus ASCII vs Modbus RTU vs Modbus TCP/IP - The Automization
<https://theautomization.com/modbus-ascii-vs-modbus-rtu-vs-modbus-tcpip/>

To sum up, basically following your suggestion: modbus-tcp, modbus-rtu and
modbus-ascii sounds like a good approach.

Cheers,
otluk



Am Mi., 9. März 2022 um 15:19 Uhr schrieb Christofer Dutz <
[email protected]>:

> Hi all,
>
> I'm currently working on the modbus RTU stuff ... as in general the
> protocols are referred to modbus-tcp, modbus-rtu und modbus-ascii, I would
> like to rename the "modbus" to "modbus-tcp" ... While modbus-tcp will not
> be many variants, will the modbus-rtu and ascii also be available as
> "modbus-rtu:tcp" if a tcp tunnel is used.
>
> What do you think?
>
> Chris
>

Reply via email to