INT Bits Not Resetting back to 0

[Pesos777]

I have an interesting problem here... In my program 'OperatorMessages' I use MOVE logic to receieve an integer, and display the visibility of the bit if its ON/OFF, this is stored on a datalamp which displays a color for whatever bit is triggered via HMI (help2.png). 

I have 2 tags here, HMI.MessageLT and HMI.FuncMSG, they are both under the same UDT and are both INTS.

You can see that when Machine.Mode.Auto is SET HMI.MessageLT holds the INT value.When Logic to the Left is RESET the INT value is placed back to 0.

So my HMI.MessageLT is working perfectly,

BUT the HMI.FuncMsg does not reset its bits. (images below)

So you can probably image that on my HMI Data lamps, the DataLamp which takes HMI.MessageLT as a variable dissapears and reappears accordingly with the triggered bits, but the DataLamp which takes HMI.FuncMSG is not dissapearing, so when RESET it still displays as if there is an error because the bit is not resetting. Headache.

[Str8jCkt]

@Pesos777

This would be a hard one for someone to debug given just those snippets of code.

Think anyone would need to sort thru the logic to find out what is actually going on 

[BE]

On 07/06/2024 at 9:32 AM, Str8jCkt said:

This would be a hard one for someone to debug given just those snippets of code.

Think anyone would need to sort thru the logic to find out what is actually going on

I second this.

 

If I had to take a stab at it, either there is a problem with the reset logic for HMI_FuncMsg or this same variable is being written from somewhere else.......

[Crossbow]

You must be writing the 0 to HMI.MessageLT... Integers do NOT go back to zero when the logic is false like bits do.  The MOVE is simply not happening anymore, and the value remains at what it was set to last...  So if you want to to be zero, YOU NEED TO WRITE ZERO TO IT.

You might also want to consider pulsing those MOVE instructions, is there really any reason to do it every program scan?

[Crossbow]

You must be writing the 0 to HMI.MessageLT... Integers do NOT go back to zero when the logic is false like bits do.  The MOVE is simply not happening anymore, and the value remains at what it was set to last...  So if you want to to be zero, YOU NEED TO WRITE ZERO TO IT.

You might also want to consider pulsing those MOVE instructions, is there really any reason to do it every program scan?