Hello All,
I have a push button that does the following:
- if button enable property is set to true, pressing the button sets a bit to 1 that is binded to an indirect tag which is to send to the plc.
- if button is disabled, the button is greyed out and does not show that you can press it(by hovering over it, it does not show what it does for an enabled button), however for one scan cycle on the plc(20ms), I was able to trend a rising edge of the tag that I send to the plc when clicking it and is disabled on my end. Multiple presses in short bursts does not keep setting the rising edge I saw.
- the tag that sets the button to true is bidirectional.
- I tried replicating this with a test button and a latch on the plc, was not able to replicate this.
- my scan rate for the tags are set to 250ms...any faster causes overload.
Things to consider:
- The action is on mouse release of the button, it sets this custom property("{$.IndirectBool_PB}) I have on the button to a value of 1.
- The custom property I have called "IndirectBool_PB" is binded to the same indirect tag as the disabled button, which is a client tag called nCurrentCellNum to determine which cell number in which structure I want to send the number to.
- I can see the button is indeed disabled
- the plc is seeing the disabled bit
Has anyone experienced a bug like this with their buttons disabled and was able to use the button to set a bit to the plc?