Strange behavior with digital control limit settings

[Henrik Skupin]

Hi,

inside a sub VI i have numerous controls which limits are setting
dynamically. Therfor i use property nodes with the entry DataRange. The
values of that controls i want's to initialize with numbers i have reading
from an inifile. When i assign this numbers to the controls the limit
settings are ignored and the number is not reduced to the selected
datarange. I also selected the item "force range".

But why manual input is always working?
How could i solve it?

regards
Henrik

[Gorka Larrea]

In LV 5 there's a option called "coerce" inside data range, that forces data to the set range, but property nodes don't include data range option. If you select coerce, it will work fine. Perhaps it's some kind of problem with LV 6? Have you updated to 6.02?
Hope this helps

[Henrik Skupin]

Yeah.. i forgot to say.. i reinstalled LV6 and updated to 6.02. My last work
on that vi is a long time ago, but i think to remember that all was fine
with LV6.
If i use sliders then outside values are changed into the data range.
I can also change the direction of setting the data (value <-> data range)
oder inside the property node of the digital control but nothing happens..

Henrik


Gorka Larrea schrieb in im Newsbeitrag:
506500000005000000202E0000-991728092000@quiq.com...
> In LV 5 there's a option called "coerce" inside data range, that
> forces data to the set range, but property nodes don't include data
> range option. If you select coerce, it will work fine. Perhaps it's
> some kind of problem with LV 6? Have you updated to 6.02?
> Ho
pe this helps

[Greg_McKaskle2]

> Yeah.. i forgot to say.. i reinstalled LV6 and updated to 6.02. My last work
> on that vi is a long time ago, but i think to remember that all was fine
> with LV6.
> If i use sliders then outside values are changed into the data range.
> I can also change the direction of setting the data (value <-> data range)
> oder inside the property node of the digital control but nothing happens..
>

Data range functionality was changed a bit in 6.0. The range settings
are now settable from the property node, but that would cause major
confusion if the settings on a control changed what a subVI would
and would not accept. The data range feature on numerics and Booleans
is now for interactive user limits, not programmatic ones. A local,
terminal, or value
property can write any value they like, as can the
input to a subVI. A conversion warning window will alert you to VIs
converting from previous versions that had coercion turned on, but it
will not try to fix up the diagrams for you.

If you need the coercion, the Data Range primitive on the diagram
has been enhanced to not only return the range status, but also
the coerced values. You can pretty easily take a subVI input,
compare against valid range values, then either produce an error
or coerce to valid values and continue the diagram.

I believe there is some more information in the upgrade notes.

Greg McKaskle

[Doug (CapeFl)]

In addition to Gorka's answer...could it be your 'sequence of events'...you are loading in your ini.file values, THEN you set the properties nodes for DataRanges after the data is already there?
Just be sure the parameters are set prior to loading data.
Good Luck, Doug