When redundancy is set to warm it is like it is active, with the exception of logging data or writing to devices, allowing for faster fail-over.
Does it run gateway and tag change scripts?
Scripts only run on the active node.
Is there any way to set warm on some devices and cold on others?
It looks like all of our modbus device connections fail to connect when its connected to another system.
For example, if the backup is a warm state actively tries to connect to the devices and does connect before the master, then that will prevent the master from connecting.
Any ideas on a work around for that?
No there’s no granularity in any of the system. Cold and Warm states are all or nothing wherever they are used.
Any suggestions on this problem?
I need to do a warm state because we have so many tags that the time it takes for devices to get connected (over cellular) and tag subscriptions to be created can take up towards 30 minutes. Redundancy doesn’t help us if the master goes down for 10 minutes because it takes longer for the backup to get started up and start reading tags.
I don’t see how you have a warm setting which actively connects to devices but no one has any problems with their modbus devices being connected from two different scada systems.
I think many people have a problem with how our "warm" works (it works how I would expect "hot" to work...), and they use "cold" instead.
Redundancy modes and behavior need a bit of an overhaul IMO, but that's definitely not a trivial undertaking and not something happening soon AFAIK.