Background/Environment:
Currently I have a legacy hardware system utilizing older FieldPoint FP-1600 ethernet modules with a couple of Discrete Input & Output modules. I run a custom desktop Visual C++ application which connects to the FieldPoint array through Ethernet via OPC server through the FieldPointOPC2.exe driver. The application doesn't run LabView or any other auxillary NI software to perform its work. The desktop computer (HP Proliant DL380 G4) was originally running Windows 2000 and Field Point Explorer to handle configuration. The computer was replaced with a HP Proliant DL380 G7 server running Windows Server 2008 SP1. FieldPointExplorer was replaced with MAX 4.1, the application updated for Visual Studio 2008, and we currently still use the FieldPointOPC2.exe driver (version 4.0.1.15). I believe the driver may be configured to run in compatibility mode for Windows XP SP3 but not certain. I am not certain what firmware level is running on the FP-1600 but is not likely to be the latest. No NI additional services are running besides NI Configuration Manager.
Problem/Questions:
- The application seems to have brief periods where a loss of communication to the OPC server occurs. I suspect this because inputs will seemingly all change state creating warnings/alerts in our application, but very quickly will return to normal operation as if nothing was ever wrong. The issue occurs very rarely and randomly (maybe once/week) although the system runs almost 24x7 6-days per week. Network hardware all appears to be ok including cabling. Is 4.0.1.15 the latest driver version for FieldPointOPC2.exe? Other forum posts suggest a version 5 may be available but I've had no luck locating it in the online driver packages.
- Outside of the random loss of communication, I also experience an occasional application exception which I believe may also be tied to the FieldPointOPC2 driver:
Updating the hardware is not readily an option due to funding issues and I'm hesistant to update FP1600 firmware considering their age, availability, and non-supported status from NI. Any help is greatly appreciated.