I am supporting a client's Vision setup, but have encountered an issue beyond my knowledge. There is an auger speed displayed that is setable by the operator, but roughly once per hour the displayed value will hang and require restarting the application to update the displayed value. I have confirmed the tag in Ignition and the PLC are properly updating, but the display still showed the previous auger speed.
Tag value has updated to 31, but speed is still shown as 30%.
The PLC tag updated to 31.
What version of Ignition are you seeing this happen on?
Does the numeric text entry field still have focus when this happens? Is Reject Updates During Edit enabled on that numeric text entry field? Or is that just a display field (entry via separate field/buttons)?
Is there anything in the vision client logs around when the value freezes?
Show the binding on that field if possible.
Ignition version 8.1.44
The numeric text entry field does not have to have focus, the up and down buttons increment the speed value and I managed to create the same error.
Reject Updates During Edit is enabled.
There are no corresponding events in clients log.
It is just a Tag binding.
Could you explain this more, do you mean you are able to cause the same issue by incrementing the value via the buttons? And then the value in the PLC changes but the display on your screen doesn't? If that is the case can you show the script on the buttons?
Try slapping a label component onto the screen that is bound to the exact same tag, and see if that value display changes when the other becomes stuck. I suspect it may be a focus issue with the number field in the template.
1 Like
Yes, both through text entry and through the inc/dec buttons I have seen it reproduce the error behavior of the tag being set for the correct, new value but the displayed value still being the previous running one.
I will try putting just a display on there and see what happens.
Another thing to possibly try when the field value becomes stuck is to interact with the entry field like you are going to change the setpoint, and then cancel the edit (pressing ESC or similar) and see if the value then updates to the correct value.
If Commit on Focus Loss is enabled this won't work as it will try to write whatever value is there when you press ESC
1 Like
I think you are right that it has to do with focus. Making sure I never click into the field results in the inc/dec buttons changing the displayed value. Would disabling Commit on Focus Loss fix this by requiring enter by the operators to change?
Possibly, try it and see.
I would expect the arrow buttons to pull focus when they are interacted with but this appears to not be the case.
