You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2026/04/16 16:19:41 UTC
[SPI3] Extensive testing of the new Modbus driver
Hi all,
I just wanted to point out that today I’ve added an Integration Test that starts a python Modbus server and then runs our driver against that and tests:
*
Modbus TCP
*
TCP
*
UDP
*
TLS
*
Modbus RTU
*
TCP
*
UDP
*
Mobbus ASCII
*
TCP
*
UDP
Technically it would have been possible to also map a serial port, but I tried that in my ToddySoft Firmata driver and it was a stability nightmare.
So … just if you’re interested.
Chris
AW: [SPI3] Extensive testing of the new Modbus driver
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi all,
Also one thing to point out, which I really think is awesome for tracking down issues.
I added an „audit log“ component, that you can enable via connection string.
First however you need to make sure the
toddysoft-connect-java-utils-audit-log-impl
is added to the module. Without that you can enable audit log, but it will default to a no-ops logging that simply logs to slf4j the fact that that library is missing.
As soon as that’s on the classpath, you can add the following argument to the connection string:
log.audit-log-file=audit.log
And when running, the driver will log all information to the file with the name you gave it.
This sill be super helpful as this way we don’t have to have our users configure Wireshark and explain to them how to use it. Simply tell them to add the dependency and configure the connection and send us the results.
As it sends what the driver is sending to the transport, this way we will also be able to diagnose issues with encrypted transports.
Just wanted to leave that here.
Chris
Von: ott.lukas.murena.io via dev <de...@plc4x.apache.org>
Datum: Donnerstag, 16. April 2026 um 20:03
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Cc: ott.lukas@murena.io <ot...@murena.io>
Betreff: Re: [SPI3] Extensive testing of the new Modbus driver
I know, but Python code finally got some usw even so it is external...😉
Am 16. April 2026 19:03:23 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>Hi Lukasz,
>
>unfortunately I’m not „eating our own dogfood“. I’m using pymodbus, which is an external project.
>
>Chris
>
>Von: ott.lukas.murena.io via dev <de...@plc4x.apache.org>
>Datum: Donnerstag, 16. April 2026 um 18:25
>An: dev@plc4x.apache.org <de...@plc4x.apache.org>
>Cc: ott.lukas@murena.io <ot...@murena.io>
>Betreff: Re: [SPI3] Extensive testing of the new Modbus driver
>
>Nice finally some Python stuff is actually used in our project. Besides Ben s effort a few years back 🙂
>
>Cheers
>Lukas
>
>Am 16. April 2026 18:19:41 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>>Hi all,
>>
>>I just wanted to point out that today I’ve added an Integration Test that starts a python Modbus server and then runs our driver against that and tests:
>>
>>
>> *
>>Modbus TCP
>> *
>>TCP
>> *
>>UDP
>> *
>>TLS
>> *
>>Modbus RTU
>> *
>>TCP
>> *
>>UDP
>> *
>>Mobbus ASCII
>> *
>>TCP
>> *
>>UDP
>>
>>Technically it would have been possible to also map a serial port, but I tried that in my ToddySoft Firmata driver and it was a stability nightmare.
>>
>>So … just if you’re interested.
>>
>>Chris
Re: [SPI3] Extensive testing of the new Modbus driver
Posted by "ott.lukas.murena.io via dev" <de...@plc4x.apache.org>.
I know, but Python code finally got some usw even so it is external...😉
Am 16. April 2026 19:03:23 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>Hi Lukasz,
>
>unfortunately I’m not „eating our own dogfood“. I’m using pymodbus, which is an external project.
>
>Chris
>
>Von: ott.lukas.murena.io via dev <de...@plc4x.apache.org>
>Datum: Donnerstag, 16. April 2026 um 18:25
>An: dev@plc4x.apache.org <de...@plc4x.apache.org>
>Cc: ott.lukas@murena.io <ot...@murena.io>
>Betreff: Re: [SPI3] Extensive testing of the new Modbus driver
>
>Nice finally some Python stuff is actually used in our project. Besides Ben s effort a few years back 🙂
>
>Cheers
>Lukas
>
>Am 16. April 2026 18:19:41 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>>Hi all,
>>
>>I just wanted to point out that today I’ve added an Integration Test that starts a python Modbus server and then runs our driver against that and tests:
>>
>>
>> *
>>Modbus TCP
>> *
>>TCP
>> *
>>UDP
>> *
>>TLS
>> *
>>Modbus RTU
>> *
>>TCP
>> *
>>UDP
>> *
>>Mobbus ASCII
>> *
>>TCP
>> *
>>UDP
>>
>>Technically it would have been possible to also map a serial port, but I tried that in my ToddySoft Firmata driver and it was a stability nightmare.
>>
>>So … just if you’re interested.
>>
>>Chris
AW: [SPI3] Extensive testing of the new Modbus driver
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Lukasz,
unfortunately I’m not „eating our own dogfood“. I’m using pymodbus, which is an external project.
Chris
Von: ott.lukas.murena.io via dev <de...@plc4x.apache.org>
Datum: Donnerstag, 16. April 2026 um 18:25
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Cc: ott.lukas@murena.io <ot...@murena.io>
Betreff: Re: [SPI3] Extensive testing of the new Modbus driver
Nice finally some Python stuff is actually used in our project. Besides Ben s effort a few years back 🙂
Cheers
Lukas
Am 16. April 2026 18:19:41 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>Hi all,
>
>I just wanted to point out that today I’ve added an Integration Test that starts a python Modbus server and then runs our driver against that and tests:
>
>
> *
>Modbus TCP
> *
>TCP
> *
>UDP
> *
>TLS
> *
>Modbus RTU
> *
>TCP
> *
>UDP
> *
>Mobbus ASCII
> *
>TCP
> *
>UDP
>
>Technically it would have been possible to also map a serial port, but I tried that in my ToddySoft Firmata driver and it was a stability nightmare.
>
>So … just if you’re interested.
>
>Chris
Re: [SPI3] Extensive testing of the new Modbus driver
Posted by "ott.lukas.murena.io via dev" <de...@plc4x.apache.org>.
Nice finally some Python stuff is actually used in our project. Besides Ben s effort a few years back 🙂
Cheers
Lukas
Am 16. April 2026 18:19:41 MESZ schrieb Christofer Dutz <ch...@c-ware.de>:
>Hi all,
>
>I just wanted to point out that today I’ve added an Integration Test that starts a python Modbus server and then runs our driver against that and tests:
>
>
> *
>Modbus TCP
> *
>TCP
> *
>UDP
> *
>TLS
> *
>Modbus RTU
> *
>TCP
> *
>UDP
> *
>Mobbus ASCII
> *
>TCP
> *
>UDP
>
>Technically it would have been possible to also map a serial port, but I tried that in my ToddySoft Firmata driver and it was a stability nightmare.
>
>So … just if you’re interested.
>
>Chris