e, 10 mar 2022 a las 11:07, Otto Fowler ()
escribió:
+1, this is in my experience how these “drivers” used to be presented in
scada/hmi apps
From: Christofer Dutz
Reply: dev@plc4x.apache.org
Date: March 9, 2022 at 09:19:33
To: dev@plc4x.apache.org
Subject: [DISCUSS] Rename "modbus&
stofer Dutz
>
> Reply: dev@plc4x.apache.org
> Date: March 9, 2022 at 09:19:33
> To: dev@plc4x.apache.org
> Subject: [DISCUSS] Rename "modbus" to "modbus-tcp"?
>
> Hi all,
>
> I'm currently working on the modbus RTU stuff ... as in general the
> pro
+1, this is in my experience how these “drivers” used to be presented in
scada/hmi apps
From: Christofer Dutz
Reply: dev@plc4x.apache.org
Date: March 9, 2022 at 09:19:33
To: dev@plc4x.apache.org
Subject: [DISCUSS] Rename "modbus" to "modbus-tcp"?
Hi all,
I
Why not keeping modbus as protocol family, encoding as option with
transport as part of URI?
Full uri would look like modbus::.
Then defaults could be:
modbus:serial:/ => rtu, same as modbus:rtu:serial:/
modbus:ascii:serial:/ => ascii over serial
modbus:tcp:/ => tcp
modbus:rtu:tcp:/ => rtu
-0
Having an alias for modbus-tcp as modbus would probably be good practice,
but hey if no one complains then go for it.
Currently the modbus-tcp also supports udp, it would look funny as
modbus-tcp:udp
I haven't actually seen it over udp but apparently they're out there.
Modbus+ should
On 2022-03-09 17:07, Christofer Dutz wrote:
Hi Lukas,
I think that Modbus+ is a completely different thing. Seems to be
related to routing of Modbus traffic ... haven't looked too deep at
it.
I think it was an attempt to modernize Modbus for the 21st century, but
I have not seen any devices
tween the
> transport and the driver.
>
> Please correct me if I'm wrong,
>
> Chris
>
> -Original Message-
> From: Lukas Ott
> Sent: Mittwoch, 9. März 2022 16:48
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Rename "modbus" to "modbus-tcp&qu
-Original Message-
From: Lukas Ott
Sent: Mittwoch, 9. März 2022 16:48
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Rename "modbus" to "modbus-tcp"?
+1
I would follow the most common naming convention and call the drivers the
following:
- Modbus ASCII
- Su
+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
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
10 matches
Mail list logo
