I have a block transaction group to retrieve recipes from DB to an OPC trigger based. I’ve set up the tags for the OPC and the array for the block (up to 24 tags per block) and to retrieve the recipes, I have a SQL view which gives the rows/data needed to be written in PLC.
Everything should work fine, and it in fact does. But when I change recipes after some time (don’t know exactly what makes the buffer from previous download go away) the transaction group write in the tags data from the previous recipe downloaded to PLC. In other words, I download a 8 step recipe to PLC, when I download the next one with only 5 steps, the steps #6 to #8 uses the data from the previous recipe.
I do reset all tags after a successful handshake and I confirm the tags are 0. When the group is triggered, I’m able to see the values being written, so it seems to me that the Ignition query against the view has some kind of cache/buffer, providing wrong information to the transaction group.
Have any of you any kind of similar issue? I’m running Ignition 7.9.9
There doesn’t seem to be a bug number in the post. You may want to contact support to see where this stands. (You will certainly have to upgrade Ignition for any fix, once available.) The workaround would be to replicate your transaction group functionality with a script.