Introduction
In the industrial automation sector, communication between devices and systems is crucial for efficient and reliable operations. FactorySoft OPC Client is a software application that enables communication between OPC (Open Platform Communications) servers and clients, facilitating data exchange and monitoring. This paper provides an overview of the FactorySoft OPC Client installation process, highlighting its key features, benefits, and best practices.
What is OPC?
OPC (Open Platform Communications) is a set of standards for industrial communication and interoperability. It enables devices and systems from different manufacturers to communicate with each other seamlessly, facilitating data exchange, monitoring, and control. OPC is widely used in various industries, including manufacturing, oil and gas, power generation, and chemical processing.
FactorySoft OPC Client Overview
FactorySoft OPC Client is a software application designed to connect to OPC servers, enabling users to monitor and control industrial processes. The client software provides a user-friendly interface to configure and manage OPC connections, browse OPC servers, and monitor data in real-time. FactorySoft OPC Client supports various OPC specifications, including OPC DA (Data Access), OPC AE (Alarm and Events), and OPC HDA (Historical Data Access).
Key Features of FactorySoft OPC Client
Installation Requirements
Before installing FactorySoft OPC Client, ensure that your system meets the following requirements:
Installation Steps
To install FactorySoft OPC Client, follow these steps:
Best Practices
To ensure a successful installation and optimal performance of FactorySoft OPC Client, follow these best practices:
Conclusion
FactorySoft OPC Client is a powerful software application that enables communication between OPC servers and clients, facilitating data exchange and monitoring. By following the installation requirements and steps outlined in this paper, users can successfully install and configure FactorySoft OPC Client. By adhering to best practices and leveraging the key features of the software, users can optimize their industrial automation processes and improve overall efficiency.
Installing the FactorySoft OPC Client (often referred to as the Simple OPC Client) is a straightforward process designed for testing and troubleshooting OPC DA (Data Access) connectivity. Installation Steps
Download the Installer: Ensure you have the latest version of the SimpleOPCClient.exe or the installation package from the official FactorySoft source or your authorized distributor.
Run as Administrator: Right-click the installer file and select Run as Administrator to ensure the software has the necessary permissions to register COM/DCOM components. Follow the Setup Wizard: Accept the license agreement.
Choose your destination folder (the default is usually C:\Program Files (x86)\FactorySoft). Complete the installation and click Finish.
DCOM Configuration: Since this is an OPC DA client, ensure that OpcEnum is running on the target server machine so the client can "browse" for available servers. Quick Start Guide
Once installed, follow these steps to verify your connection:
Connect to a Server: Launch the application, click on File > Connect, and select your OPC Server from the list. If the server is on a remote machine, enter the IP address or Hostname first.
Add a Group: You must create a group before adding tags. Click Group > Add and give it a name (e.g., "TestGroup").
Browse for Tags: Click Item > Add to open the address space browser. Select the tags you want to monitor and move them to the "Items to Add" list.
Monitor Data: The main window will now display the Value, Quality, and Timestamp for each tag in real-time. Troubleshooting Common Issues
"Server Not Found": This usually indicates a DCOM mismatch or a firewall blocking the connection. Ensure Port 135 is open on the server.
"Access Denied": Check that the user account running the FactorySoft client has permissions in the DCOM configuration of the OPC Server. factorysoft opc client install
Empty Server List: Ensure the OPC Core Components are installed on your machine; these are required for the client to communicate with the OpcEnum service.
Getting your FactorySoft OPC Client up and running is a straightforward process that bridges the gap between your Windows applications and industrial hardware. Whether you are testing a new PLC connection or building a custom HMI, this guide will walk you through the installation steps. 1. System Requirements & Preparation Before starting, ensure your environment is ready:
Operating System: Windows 7, 8, 10, or 11 (32-bit and 64-bit supported).
Framework: Most versions require the .NET Framework 4.0 or higher.
Permissions: Ensure you have Administrative Privileges on the machine to register COM components and DCOM settings. 2. Downloading the Installer
Head to the official FactorySoft website or your provided vendor link to download the latest setup package. It typically comes as a .zip or a standalone .exe installer. 3. The Installation Process
Extract the Files: If you downloaded a ZIP, extract it to a local folder. Avoid running the setup directly from the compressed folder.
Run Setup.exe: Right-click the installer and select "Run as Administrator."
Follow the Wizard: Click through the license agreement and choose your installation directory.
OPC Core Components: The installer may prompt you to install the OPC Core Components from the OPC Foundation. Accept this step, as these redistributables are essential for any OPC DA/HMI communication to work on Windows.
Finish: Once the progress bar completes, you may be asked to restart your computer to finalize DCOM registrations. 4. Initial Configuration
Once installed, launch the FactorySoft OPC Client. To verify the install:
Discovery: Click on "Connect" or "Server List" to see if it detects local OPC Servers (like Kepware, Matrikon, or RSLinx). Installation Steps To install FactorySoft OPC Client, follow
Add Tags: Select a server, browse the address space, and drag a few tags into your watch list.
Validate: Check the "Quality" column. If it says "Good," your installation and connection are successful. Troubleshooting Tip: DCOM Errors
If the client installs but cannot "see" servers on other machines, the issue is likely DCOM permissions. Ensure that both the client and server machines have matching user accounts or that the "Everyone" group is temporarily allowed for testing purposes.
If you deploy the client across 10+ workstations, use silent installation parameters:
msiexec /i "FactorySoft_OPC_Client_v5.2.8.msi" /quiet /qn /norestart
ADDLOCAL=ALL
REGISTER_COM_SERVER=0
ALLOW_DCOM_CONFIG=1
Then, push a PowerShell script to set DCOM permissions:
# PowerShell snippet for DCOM config (run as Admin)
$appID = "B2C5D6A3-8F1E-4B9A-9C2D-3E4F5A6B7C8D" # Replace with actual FactorySoft AppID
Grant-DCOMAccess -AppId $appID -Account "DOMAIN\OPCClientSvc" -Permissions Launch,Activation
Always test silently on a staging VM first.
Installing a FactorySoft OPC Client is a task rooted in legacy IT management. While the installation wizard itself is straightforward, the surrounding ecosystem—DCOM configuration, Administrative rights, and OS compatibility—presents the real challenge.
Checklist for Success:
If these steps fail on a modern OS, consider moving the software to a Virtual Machine to ensure stability for your industrial operations.
Here’s a complete review of the FactorySoft OPC Client installation process, covering prerequisites, step-by-step setup, common issues, and post-install validation.
Run these three tests to confirm a working factorysoft opc client install.
The FactorySoft OPC Client requires the OPC Foundation Core Components (Redistributable) . Install version 3.0 or higher before the FactorySoft client.
Warning: Windows 10/11 Anniversary Update and later disable DCOM by default. You must re-enable DCOM and configure firewall rules prior to install. and post-install validation.
| Problem | Likely Cause | Solution |
|---------|--------------|----------|
| “OPC Server not found” | OPC Core Components missing | Install from OPC Foundation |
| Access denied (E_ACCESSDENIED) | DCOM permissions | Run dcomcnfg → give Anonymous/Everyone launch & activation rights |
| Installer hangs | Antivirus blocking | Disable AV temporarily |
| Cannot browse remote server | Firewall blocking DCOM (port 135) | Allow port 135 TCP in Windows Firewall |
| “Class not registered” | 32‑vs‑64-bit mismatch | Use 32‑bit OPC Client for 32‑bit OPC servers |