You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this sounds ridiculous, but there are instances where the slave is Modbus-TCP but only allows one connection, when new master tries to poll, there might be an option to either drop existing connection or refuse the new one.
It would be beneficial to have the slave side of mbusd as modbus TCP to over come this issue and allow multiple masters to poll the slave.
The text was updated successfully, but these errors were encountered:
No doubt this feature will be useful in some cases, but it's still not clear to me how to fit it into mbusd concept. At least we need to find the way to switch between RTU and TCP master modes using command line and/or the configuration file in a compatible way with existing setups (including systemd part).
I know this sounds ridiculous, but there are instances where the slave is Modbus-TCP but only allows one connection, when new master tries to poll, there might be an option to either drop existing connection or refuse the new one.
It would be beneficial to have the slave side of mbusd as modbus TCP to over come this issue and allow multiple masters to poll the slave.
The text was updated successfully, but these errors were encountered: