Automation Professionals' Advanced Modbus Driver

[pturmel]

Hi Andres,

No, I have not, and have no prospects to do so. I have no access to a specification for it.

BTW, I have now replied twice to your email inquiries. You should look for them in your mail system. (A few minutes ago, and back on May 3rd. My email server says your email server accepted the messages.)

Phil

[Andres_Rossi]

Thanks for the response Phil.
Unfortunately my email system is blocking your emails and I can't see them. Would you mind resending them to arossi.aci@gmail.com?

Thanks in advance.
Regards, Andres

[SHuidrom]

@pturmel , while testing this advanced modbus driver configured as an advanced client connected with redundant slave devices. The problem is when i disconnect both the redundant devices the driver status on the device connection shows "Connected" and the status remains "Connected" until figured out.

In the second test, If one link is up out of the redundant client devices, it shows "Connected Recovering", and if i disconnect the live single link, the status remains "Connected Recovering", which is not an ideal scenario.
Is there a fix for this one ? thanks.

[pturmel]

Thanks for the report. Will investigate.

[Kamil_Muza]

Does Automation Professional's Modbus driver allows for multiple Modbus TCP servers/slaves on different tcp ports simultaneously?

[pturmel]

Yes. Multiple server instances are supported. A single instance can also listen on multiple ports.

[pturmel]

Automation Professionals is pleased to announce that this Advanced Modbus driver is now available for purchase for Ignition Edge, with a steep discount. See Automation Professionals' updated Module Sales Policy here:

https://www.automation-pros.com/Module%20Sales-2024-11-05.pdf

[pturmel]

Automation Professionals is pleased to announce a new production release of the Advanced Modbus Module.

For Ignition v8.1.x: v1.1.7.242701819

This includes a bugfix for the driver status problem mentioned in comment #63 above.

This includes the constrained Transaction ID feature requested in this topic:

Modbus TCP - Moore / Siemens 353

I have a new installation with a Moore / Siemens 353 controller using Modbus TCP. It all works great for the first 15 or so minutes - then, it just times-out and cycles from connecting/disconnecting/etc. If I disable/enable, it starts to work again - for 15 minutes. Is there some obvious setting that I can change to correct this behavior?

[pturmel]

Automation Professionals is pleased to announce a new production release of the Advanced Modbus Module.

For Ignition v8.1.x: v1.1.8.242731956

This release fixes a client driver bug in holding register Masked Write operations, as reported by @woodsb02 over here, long ago:

Ignition OPC UA Server Redundancy (Modbus TCP)

Actually, I think I may have found a bug when used with bit-level addressing and Modbus mask-write. Not sure if its new with this redundant BETA version or pre-existing. My test setup (both the modbus server and client are using your advanced modbus driver): Modbus Server listening on 0.0.0.0 Modbus Advanced Client connecting to 127.0.0.1 and 127.0.0.2 Setup a boolean OPC tag which uses the Modbus advanced client device. Using this address works: ns=1;s=[client]1.C1 Using this address work…

I couldn't reproduce with the designer tag browser or with fire-and-forget writes, because the actual write worked. The breakthrough came when I scripted my testing with system.opc.writeValue(). Boom!

This bug goes all the way back to the beta. All users should upgrade.

Sigh.

[woodsb02]

Hi @pturmel, can I please ask how your driver behaves on the non-active backup server configured in warm mode?

In the manual it says “only the active server will open the given ports” - does this mean it ignores the “warm mode” setting?

Does this change when an alternate target/port is configured for modbus redundancy?

[pturmel]

@woodsb02

does this mean it ignores the “warm mode” setting?

Yes, this. My drivers are always cold.

[woodsb02]

Ok, thanks for confirming

[pturmel]

Automation Professionals is pleased to announce a new production release of this driver:

For Ignition v8.1+: v1.1.9.242811552

This provides a better fix for the device connection status information, and fixes a potential bug in the Modbus TCP transaction ID limit feature recently introduced.

[Andres_Rossi]

Hi Phil,
Sorry if someone already asked this,
Does the driver have any practical limitations regarding the maximum number of devices that can be connected? Or regarding the maximum number of TAGs between all devices? Or regarding the number of updates/sec that it can process?

In my case I have around +2500 Modbus TCP devices and +2000 Modbus RTU over TCP with an average of 200 TAGs each at a scan rate of 1min (only 20% of the TAGs change in each scan) and I want to have an idea of ​​the size or amount of I/O gateways I need.

Thanks!

[pturmel]

I don't have any users with such an extreme workload, but I would expect it to be possible with enough CPU cores and RAM. There's no hard-coded limits in the software.

[pturmel]

Automation Professionals is pleased to announce a BETA release of this Advanced Modbus driver module, with one bugfix and two features.

For Ignition v8.1+: v1.1.10.243132114

• Fixed a bug in diagnostics that breaks device diagnostics for all devices in the gateway--that page then looks like no devices are configured. Due to RateStats losing its Comparable<> interface somewhere along the way. (And me not noticing.)

• Added [Diagnostics] folder to OPC browsing--basically a port of the code from the EtherNet/IP driver's Driver implementation. While in that mess, added separate diagnostic booleans for ConnectedA and ConnectedB when using live redundant connections.

• Altered the OPC browse to fan out the tree of OPC Item Paths in smaller increments, to dramatically reduce the amount of scrolling needed to browse to specific points.

The bugfix has been cooking for a couple weeks, so that is solid, but the new diagnostics are only lightly tested, and the new OPC fanout is barely tested.