Lookout will write whatever is connected to its FieldPoint outputs. This is the expected behaviour -- at least from Lookout's point of view.
You can, however, prevent this from happening in couple of ways:
1. Create an "Initialization" process in Lookout. And set this as your startup process. In this dummy process, do not include any FieldPoint Object; but can include other initialization functions you may want. So, you would first launch this dummy process, and from this dummy process, whenever you/system is ready, launch the actual process (which has the FieldPoint Object). This way you control when exactly Lookout connects and writes to the FieldPoint.
2. Another option is to not let the FieldPoint Object poll until you are ready. This can be done by using a Pulse Timer object for the Poll datamember (instead of a constant time), and use a Switch (or something similar) in the Pulse Timer Object to decide when to start the pulses. BUT, I remember there was an issue way back where Lookout would Poll all the driver objects in a process at startup of the process -- regardless of whether or not it was set to poll immediately.
3. Finally, you could setup the outputs for the FieldPoint object to match your power-up settings. Not sure how exactly you would do this -- perhaps have switches tied to the outputs in th state you want, and then save the process file. This would generate the state file (LST) which would keep these states the next time the process is launched. But, if during the use you change these states and close the process. These final states will be saved in the state file.
I hope the above gives you some ideas.
Regards,
-Khalid
