Read the End-User License Agreement (EULA). Select I Accept and click Next .
Ensure the FactorySoft Client has "Local Launch" and "Local Activation" permissions for the current user. 🚀 Step 4: Connecting to an OPC Server
Before beginning the installation, ensure the target computer meets these requirements:
: If you are connecting to a remote OPC DA server, you must configure Windows DCOM settings (via dcomcnfg ) on both the client and server machines to allow cross-network communication.
In the configuration settings, input the server address (e.g., opc.tcp://localhost:4840 ). factorysoft opc client install
Select your target server (e.g., Kepware.KEPServerEX.V6 , Matrikon.OPC.Simulation ) and click . Step 3: Create an OPC Group
Locate your OPC Server and adjust the to allow network access for the client user account. 3. Adding Tags and Verifying Data
: Check the "Quality" column. If it says "Good," your installation and connection are successful. Troubleshooting Tip: DCOM Errors
: The installer typically registers necessary DLL files automatically. If it fails, you may need to manually register them using regsvr32 . Post-Installation Configuration Read the End-User License Agreement (EULA)
Because FactorySoft OPC Client relies on Microsoft's Distributed Component Object Model (DCOM) architecture for OPC DA communication, you must configure network and security settings—especially if connecting to an OPC server hosted on a different computer. Step 1: Launch Component Services Press Win + R , type dcomcnfg , and press . Expand Component Services > Computers > My Computer . Step 2: Modify Default Properties Right-click My Computer and select Properties . Navigate to the Default Properties tab. Ensure Enable Distributed COM on this computer is checked. Set the Default Authentication Level to Connect . Set the Default Impersonation Level to Identify . Step 3: Configure COM Security Switch to the COM Security tab.
Windows versions ranging from Windows 2000/XP to modern Windows Server (2016–2025) and 64-bit client OS for testing. Frameworks: Many FactorySoft components require the .NET Framework
This guide covers the installation and configuration of a FactorySoft-style OPC client, typically used for commissioning OPC Classic (DA) OPC Unified Architecture (UA) connections. Factory IO Prerequisites
To ensure your installation is fully functional, perform a quick live data test: 🚀 Step 4: Connecting to an OPC Server
While many modern installers include these, having the OPC Foundation Core Components pre-installed can prevent registration issues. FactorySoft OPC Client Install: Step-by-Step
If the server is on the same machine, expand the tree to view registered OPC DA (Data Access) servers.
If prompted to restart your computer, do so immediately to ensure all DCOM registry changes take effect. Configuring the Client for First Use
If you absolutely must keep the FactorySoft Client running, do not try to force it onto Windows 10. Instead, use VMware Workstation or Hyper-V . Create a Windows XP Virtual Machine, install FactorySoft there, and network it to your control system. This preserves the software in the environment it was designed for, while running on modern hardware.