Generally we don’t mind people suggesting products that would be useful (and perhaps even advisable), but please at least read the original post carefully before advertising…
Now, to answer the last question about working OPC status into the redundancy state:
You’re correct that this is the job of the “OPC Quality Monitoring” option. To use it, you must enable it, and then add an item (or more) that will be used to judge the server state. The item will be local to the machine, so you’ll need to set this up independently on both machines. Here’s a tip for setting up the items: browse the opc server, and select an item. Right-click and select “copy”. Go into Redundancy Settings, and click on the item list box. Use “ctrl-v” to paste the path into the list.
I just did a quick test, and it worked well for me. Perhaps one of the following is happening:
- You did not add items to the list, thinking it would just use the overall quality.
- You added items to one, but not both, nodes. The settings are not shared between redundant nodes.
- The items you added to the list weren’t good, or the path was slightly incorrect, causing bad data from the start.
- You tested by closing the OPC server, and FactorySQL was able to re-connect before the quality went bad.
In regards to #3, it is useful to know that the opc quality just becomes another element taken into consideration for determining who is master. If the quality is equal on both nodes, the other conditions will be looked at (ie, node ranking, or age if ranking isn’t enabled).
To verify that the points are good, after enabling the feature with the opc server running, you should now see that the “opc_quality” column of the “fsql_responsibility” table is 100 (as in 100% good).
Please let us know if you still can’t get it to work.