Generally speaking, they should be configured as follows: the driver’s computer must grant both local and remote access from IOServer.
My OPC scout is version 10 and looks completely diferent than the provided screenshots. NOTE: To connect this driver to a remote server, you will need to set up the DCOM permissions (dcomcnfg) both in the computer running the driver and in the computer running the OPC server. The OPC Scout tutorial steps also seem quite outdated (looking at the ). Could it be because the previous step is incomplete? In Station Configuration Editor the Import station step fails - OPC Server_1 claims not be installed. Therefore the User Account of the OPC Client must exist in the Active Directory (located on the Domain Controller) of the OPC Server PC. First, the OPC Server PC must recognize the User Account of the OPC Client PC. The next step is to go to Simatic Net Configuration Console which I think is replaced now by something else (configuration console does not exist after installing Simatic Net V14 SP1). The trick to getting communication working is Windows Authentication on both the OPC Client and Server PCs. You can export your NI OPC Server configuration by going to File. All is compiled and plc setup loaded into the HW. Creating three-dimensional (3D) representations of the world from.
I got to a point where I have my PC station (containing the OPC server) connected to my PLC in a TIA project and. ) but they are neither suited for a single pc aproach nor up to date with the current frameworks (I'm getting asked to use older tools they were replaced in my version by something else.). _single_ PC station to run both server and client on
I'm struggling setting up the OPC server using S7-300 PLC. Configuring LabVIEW 2009 to Communicate with Acromag BusWorks and EtherStax Modbus I/O Modules via an OPC Server.