I have moved from RSSQL to FactorySQL and the project size which is being shifted has around 5000 groups.
I have many groups in my project which have triggers configured for execution. these groups are for event monitoring and the triggers can sometimes be complex and involve Action Items. Now my problem is that, if I only rely on the trigger say on Change, during a downtime of FactorySQL or a switch over from Master to Backup or if the Database was down, the trigger can be lost and consequently that event is lost also.
I have to use Stored Procedure groups here and to make the group trigger on the actual event as well as every 30 seconds to see, if the trigger condition is true and the event has indeed been logged, I add an “or” condition into the Trigger Action item using the Date and Time functions. The result is that if the group did not execute due to the Tag change, the 30 second timer will execute it.
The under lying stored procedure checks if the event was supposed to be started or ended and has it indeed been started or ended. This does add come additional DB calls but is necessary.
Now what I am noticing is that the execution of the same group is not sequencial i.e. FactorySQL is not waiting for the Stored procedure execution to complete before calling it again…this happens when the Trigger value based on Timer was executed on 58th second and the trigger again came at 59th second. Again, its just my observation on it.
due to this, I am having problems like duplicate insertion of events and incorrect event starts and ends.
My problem is that I cannot simply rely on a PLC based trigger and have to monitor the groups in between also to ensure that data has been logged. The way I am doing it, when the 2 triggers come very close by, the stored procedure which is not a simple insert/update and takes some time, screws up.
What I want is to program the redundant part of my trigger such that, it pulsates every 30 seconds but if the PLC trigger has come, then skip one cycle. I would like if it can be done using FactorySQL functions instead of a timer in PLC. I am suing FactorySQL 4.2.12 in redundancy mode.
Also if there is anyway to ensure 1 by 1 execution of a stored procedure in Sql Server 2000 Enterprise edition, that should solve it also.
On another note, is there a section of the Inductive Automation Website, where I can get relase notes and version releases for the softwares, I am anxiously waiting for Ignition to have store and forward for Stored Procedure Groups, We have already purchased it with 1 yr support but cannot upgrade to it, till that feature comes in.