Release – mod_openopc v3.1-4

Hot off the presses (well maybe not so hot – luke warm?) — April 12th we released mod_openopc version 3.1-4 PUBLIC.



It’s a conglomerate of the #50 and #51 builds… revision notes as follows:

1) max writes per second per mod_openopc WRITE_DAEMON subroutine instance.  This was rougly 1200, and has been increased to 6000 (ideal world – don’t plan on more than 1500 in practical application – if you need more, setup multiple WRITE_DAEMON presets for the same OPC Server [see user manual on how to setup presets]).  Latency intentionally added to WRITE_DAEMON subroutine, where directory scan now cycles with a 0.05 second interval delay.
2) MySQL keepalive count has been dropped from 100,000 cycles to 10,000 cycles across the board.  Typically, this should result in a keep-alive request sent anywhere from once every 15 minutes to once every 6 hours, depending on system load relative to system horsepower.
3) an infinite-loop-killer has been added to the WRITE and the WRITE_ONE_SHOT subroutines, where a failed write will only be reattempted twice, after which the routine will exit as if it had completed rather than continue to loop indefinately.  It will, of course, bark out an error.  ‘system_faults’ table will be populated with error indicating subroutine name, opc server, date/time, and the fault type “OPC_INFINITE_LOOP”.
4) GATEWAY or OPC_SERVER_COMM reconnects will push much more informative faults.  We will now know a) what failed [gateway or opc server comm] and b) when the situation resolved itself [when gateway and/or opc server come back into running state].
—— GW_DOWN        (on fail if cause)
—— OPC_SERVER_DOWN    (on fail if cause)
—— GW_RESTORED        (on restore if cause)
—— OPC_COMM_RSTRD    (on restore if cause)
5) OPC Server data update rate is now controlled by the ‘scan’ time of your mod_opneopc data logging / recycling (for bridges, spacebridges, and reads).
6) you may now select ‘cache’ or ‘hybrid’ for the opc group read type.  mod_openopc uses subscription refreshes (“pulled”) rather than sync or async reads for bridges / spacebridges / and reads. Formerly, ‘hybrid’ was used by default, which would defer to whatever the opc server software’s base value was.  We are now able to explicitly choose ‘cache’ if we wish.

Pick up the tarball here…

About The Admin

Thyne benevolent dictator.
This entry was posted in SC-Specific, Science and Technology. Bookmark the permalink.

Comments are closed.