Otto,
This looks like hypertrend's fault. The datamembers you speak of (max) don't
seem to send out any values when they change. The datamember should be write-only.
When you remote a pot to this datamember, the pot will always read back
the value from the hypertrend as 0, and thus be equal to zero. When you
change it, you are writing to the hypertrend, and changing the value, but
not getting the confirmation back, so the pot snaps back to 0 (its trying
to reflect the value of the remote source). If you make a connection such
that the max datamember is equal to the pot (set to local, not remote) you
can count on the pot displaying the value that max is actually set to. Because
max=pot, the pots display is max's value.
Brian
"otto" wrote
:
>>Hey everybody,>>found a strange behaviour in Lookout 4.0.1. If you connect
a pot to the max>of a hypertrend item via remote position, it will correctly
set the max but>after a few seconds the pot display will revert to zero,
allthough the max>is still correctly set. It is no problem to just link the
pot to the max>via connection browser, but then the pot display will not
be directly linked>tot tha actual value. Can somebody explain?>>Otto
