>Which step is CSS-BOY carrying out that caput does not include?
caput roughly does this:
connect, caget (old value), caput (desired value), caget (new value), disconnect
A display tool like CS-Studio tends to do this:
connect, subscribe to changes (monitor).
When you write, it performs a caput over that standing connection.
No active 'caget', simply relying on the monitor to report the value change that was caused by the 'caput'.
disconnect when you close the display.
So if you experience a problem when calling the command-line caput, maybe it's related to caput calling caget right after writing?
-Kay