Lookout 6.0.2 OPClient Object Loses Connection With OPC Server Primary Software: LookoutPrimary Software Version: 6.0.2 Primary Software Fixed Version: 6.0.2 Secondary Software: N/A
Problem: In my Lookout 6.0.2 process, I am using the OPCFieldpoint or OPClient driver objects to communicate with an OPC Server. Everything works fine for a while, but after a while I can no longer update values on the OPC Server from my Lookout process. Solution: The OPClient driver object (which is also used by the OPCFieldpoint driver object) handles the OPC communication between your Lookout process and the OPC Server. While nearly all processes will be unaffected, there are some rare cases where this communication could be disrupted when a particular set of circumstances allowed a race condition resulting in a loss of communication without triggering an alarm. You may be affected by this condition if your process is able to write values to an OPC server, but after a period of time the values written by the OPC Client don't appear on the server side and no alarms are triggered. This behavior has been seen when communicating using the OPCFieldpoint or OPCClient object to communicate with a Fieldpoint controller. The output values sent to the Fieldpoint controller are reflected correctly on the Fieldpoint bank for a time, but then cease to update. The Lookout development team has isolated the issue and released an update for it. To install the update, follow these steps:
Related Links: Drivers and Updates: Lookout Version 6.0 for Windows 2000/NT/XP -- Updates Attachments:
Report Date: 05/11/2006 Last Updated: 10/20/2006 Document ID: 3XA8JQPZ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
