gnicholl

TOPIC: LABVIEW 7.0 data sockets and connection to a remote OPC server through Dcom (Dynamic Communications Object Model) 1) Automated Solutions OPC Server was installed on a Windows 2000 Machine. 2) Automated Solutions Clients on Win XP/Win 98 can read from this OPC Server. 3) LabVIEW 6.1 Data Socket Client on Win XP can Access OPC Server. 4) LabVIEW 7.0 Data Socket Client on Win XP/Win 98 CANNOT Access OPC Server. On this server system we have enabled the DCOM connection for system access by client machines running 98/200/XP. On the upgrade to LABVIEW 7.0 the same OPC data socket example program is now not able to resolve the Automated solutions OPC server on the remote machine. We have examined the connection through the ServerExplorer and it is not able to resolve the connection to the server. We continually get the error message below attachment. We have also examined the Data socket Server (& manager) and set up permissions to

We are in the process of writing a dedicated labview connection driver to interface to a Acromag 966en 6006 temperature logger that utilizes the ethernet modubus standard. we are trying to advoid using third party opc servers as a intermediate stepping stone to this application as they are expensive and we need to limit costs. We have received some guidance from the Info LABVIEW group with some partial libaries. However these libraries they connect to the device, but the data returned dosent make sense. we are getting 65535 for all values in the registers instead of a temperature reading say like 229 which is 22.9. Has any one had exposure to Ethernet Modubus ( PLC programming) with labview and shed some light on the matter. If you have written a connection driver suitable for use with LABVIEW 7.0 i'd like to here from you!