Modbus Relay Optimization: Using Poll on Command, Device Duplication, and Event-

[isabellacog]

Hello everyone,

I am currently monitoring a relay via Modbus, but it has a large number of variables, which makes the polling queue very long and impacts response time.

I have a few questions:

* Is it possible to duplicate the device within the system to separate polling tasks?
For example, one device for continuous reading of essential variables and another only for alert or detailed diagnostic variables.

* I am also considering a logic where, for example, if I receive a critical flag (such as breaker opened), this event could trigger a Poll on Command to request more detailed readings only at that moment. Is this a viable approach?

* Is this strategy generally recommended, or could it create communication conflicts, request collisions, or overload the relay?

* I have never used Poll on Command before. Could someone explain, in general terms, how it works in practice?

* After loading the device and creating the channels, how is the Poll on Command actually triggered?
Does it require manual activation, scripting, event logic, external commands, or is there native automation for this?

My goal is to optimize communication by keeping essential variables updated quickly while performing heavier or more detailed polling only when operational events or alarms occur.

I would appreciate any shared experiences, limitations, or best practices.

[Author]

Posts