The normal approach of having a propre state owner in Lookout (4.x ...) is to let the PLC own the values and have the pots, switches remote connected to the driver object.
If you consider to have Lookout own the value (valueable argument for setpoints), using direct connections to the driver object, Lookout saves those states once a while in the state file and once the Lookout process is restarting it reads the last saved value from the state file on startup.
Now this state is as precise as the lookout process saves it last time (default: every hour, 60 minutes) and it could defer from the current state.
Now, you could decrease this default value of 60 with the drawback that the save-state-file task will be performed more often and could cause some performance de
crease. But you minimize the risk to have a difference between saved state and current state (it all depends on how fast the state of the object would change - right :))
If you just need a startup value, I would as well consider a customized approach. Leave the save state file on a higher value (e.g.60) but for really critical values you might set up a customized setup with the object datamember (reset, resetvalue) by fireing the reset with a timer on startup.
There are maybe other ways.
Hope this helps
Roland
