precision property error

[reza_sed]

I need to see the precison of a control from another control.  however i keep getting error 1435

can't seem to fix it....any advice

[Norbert_B]

You should take a close look into your VI. You have to numeric controls, one is double, the other is u8. Now you created a property node for the u8 numeric control, selected the property precision and wired the output of the u8 control to the input of the property node.

Error 1435 is a bit misleading here since it tells you that you can only pass values between 0 and 8 to the property.

What really happens is that you try to set a property from a control by using its own value.....

hope this helps,

Norbert

PS: Controls are not designed to show values, but to enter values....

[reza_sed]

Thanks for the input but the property is for the Numeric Cotrol not for the u8

This was a sample vi to show what i was talking about and I created the u8 control by right clicking on the "Precision" property node of the "Numeric" control and selected Create > Control.  I wanted to get a control that was to the exact specifications of the "Precision" Property node

If you look at the new vi, I created a separate property node for the u8 to show the difference

[Norbert_B]

Well, you are correct, i mixed up the controls... nevertheless you said, you want to see the precision but you actually try to write it.

On this other hand, this behaviour seems not to be correct. What version of LV are you using?

Norbert 

[Norbert_B]

Gna, i should keep reading and trying before posting....

The behaviour you are seeing is expected. The double control is configured to "automatic formatting", so changing properties will be difficult from time to time.

You have to switch to "floating point", then it works.

hope this helps,

Norbert 

[Powerdou]

I also got this happened many times.  the messages appeared like below.

what I did is , that go to find the controls or indicators, and change the data type from automatic format to floating point, and run the project again, the message disappeared, even you go back to change the data type back to automatic, the message did not happen again.

anyway, the issue can be fixed by this way, even I do not konw the reason.

just for your reference.

[AllisonSCJ]

Apparently the default behavior of the Format property is readonly. I ran into this issue after upgrading to Labview 2022; the solution is to create a second property node for Display Format: Format and wire 0 as your value. This makes the property writeable again. Place this before any Display Format property, such as Format or Precision.

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Xq2SAE&l=en-US