cRIO-9030 value change - old value incorrect

[LJHerskowitz]

I am working on a cRIO-9030. That is one of the cRIOs with Linux OS. I have a pecuilar problem. I created a cluster with 2 text rings. I created an event that monitors its value change. I watched the old value, and it was showing incorrect information. Instead of showing my values it would show <####>. It wouldn't show '#' but a bunch of numbers. I posted a video of it below and a picture of the block diagram. Does any one have an idea what the issue here may be?

EDIT: Apparently I can't post a video. So here is a still of the front panel. You can clearly see the nubmer on the OldVal cluster.

I tried running this exact code on the computer instead of the RT, and it worked fine.

[mikeporter]

The display you are seeing is what you get when you select a value in the ring that you haven't defined.

Mike...

[LJHerskowitz]

All the values are defined. It worked on the computer, and it doesn't show the same problem in the NewVal cluster. But either way here is a screen capture of the ring properties.

[mikeporter]

Yes, it's exactly like I said. As your screen shot shows you only have the values 0 through 2 defined. The text in the string doesn't matter. It could be "Tom", "**bleep**", and "Harry".

Mike...

[mikeporter]

Hmmm. Make that "Tom", "Richard", and "Harry". 😄

Mike...

[LJHerskowitz]

You are right the text doesn't matter. I am just cycling through the defined values {0, 1, 2}. The NewVal cluster shows the correct values {0, 1, 2}, but the OldVal shows incorrect values. I don't allow undefined values so I shouldn't be able to get a number that isn't defined.

Edited: Here is another front panel. This time I took out the text rings on the indicators and the OldVal is clearly incorrect.

[crossrulz]

What was the cluster's value before you had the Value Change event?  Do you have any parts of your code writing to the control?  You can write invalid values programatically and you will get a display like that.

[LJHerskowitz]

It was [0, 0]. I thought maybe it was the first change, but it happens a lot. Usually when I switch to the second choice, but it doesn't matter if I switch to it from the first or third. It doesn't matter if I switch the top or bottom ring, it will occur. Sometimes it will just say [0, 0] no matter what it should be. And I am running it right now and the OldVal says it is [9216, 0]. I am starting to think this is a bug that will require a CAR.

Sorry I didn't see your second question. The image of the block diagram above is all there is to this code. The other even case is just to stop the while loop. I kept this simple to probe this issue.