Hi,
The terminology does get a little confusing between Lookout's Server/Client processes and the OPC Server/Clients. But looks like you have configured it right -- the Lookout Server porcess is where the "driver objects" are normally created. Like the Modbus driver object. In your case, the "driver object" is the OPCClient object (as you're using OPC for communication with your device).
So, as you've done correctly, the OPCClient Object is created in the Lookout Server process. You can now create additional client process(es) in Lookout which would exchange data to and from the Lookout Server process.
This "Lookout Server/Client processes" architecture is a good development practice. Which you should implement. However, for testing and for th
e "checking out" stage, you can just have one single process in Lookout with everything in it. After creating and setting up the OPCClient object, you can go to Object Explorer (from the Object menu), navigate to your OPCClient object and expand it. You should now see the items for your device. Drag-and-drop the items onto a panel for testing.
Later on, you could move these expressions and switches/pushbuttons to other processes (clients) to separate it from the server process.
Hope this cleared some confusion.
Regards,
Khalid