*Pssst!*
While waiting for Kevin to get permission to include this in some future v8.3.x, you can use my Modbus driver in Edge (cheap!).
/shameless plug
*Pssst!*
While waiting for Kevin to get permission to include this in some future v8.3.x, you can use my Modbus driver in Edge (cheap!).
/shameless plug
Oh my god I didn't know that!
Thanks to mention. Our clients need this functionality for long time for connecting to DCS system which always are modbus master.
Note that if you buy either of my driver modules for Edge, I take the opportunity to also inject a whitelist for my Integration Toolkit. So you can use that in Edge, also. ![]()
Hi Kevin. Thank you for this valuable module. But the artifacts are expired (V8.1: https://github.com/kevinherron/modbus-server-driver/actions/runs/16881175375). Would you be able to generate a fresh .modl file? Or to update the releases for both versions 8.1 & 8.3? Thank you.
The releases page should have downloads for 8.1 and 8.3: Releases · kevinherron/modbus-server-driver · GitHub
yes, but it seems your last changes in ModbusServerModuleHook.java file is not applied on them. I downloaded the .modl and source code .zip file of V8.1 and checked them. there are no lines of
[at]Override public boolean isFreeModule() {return true;}
in the source code. and the .modl file is still trial. Thanks
Ok, try this: Release v2.0.0 · kevinherron/modbus-server-driver · GitHub (for Ignition 8.3)
Thanks Kevin. Would you please do it for V8.1 too?
Very interesting module !
What is the expected synthax for ranges ?
I tried 0.10 or 0,10 but devices has no data, I probably missed something obvious.
Do hyphens work to specify the range?
No
It's supposed to be a hyphen but it probably broke without me realizing it. I'll take a look.
Hi, Kevin,can it be used as a modbus slave?(modbus rtu)
It is a Modbus slave (aka server), but it's Modbus TCP only. No serial support.
My alternate Modbus driver has slave RTU support, directly and via ethernet-to-serial devices.
Maybe some day I'll add it... I have serial/RTU support in my Modbus library and the CLI... just seemed unlikely here.
Thanks, the modbus tcp server can set Slave ID?
Client specifies slave ID. This server driver implementation ignores it - there is a single shared process image for all slave ids.
My alternate driver does not ignore slave ID, can emulate multiple different devices on the same RTU chain, and can coexist with other, perhaps real, devices on an RTU chain.