Factorysoft Opc Client Install < WORKING - 2024 >

FactorySoft OPC Client Install — Step-by-step guide

This article walks through installing and configuring the FactorySoft OPC Client so you can connect to OPC servers, read/write tags, and troubleshoot common issues. Assumes Windows environment (FactorySoft products are typically Windows-based).

Connecting to an OPC server

1. In the FactorySoft OPC Client, open the “Server Browser” or “Connect” dialog.
2. Select the target OPC server from the list (local servers often appear automatically; remote servers may require manual entry of hostname/IP).
3. Click Connect. If connection fails:
   • Verify server is running.
   • Check firewall (Windows Firewall: allow DCOM/OPC traffic or temporarily disable for testing).
   • Confirm DCOM settings and user permissions as above.
4. Once connected, browse the server namespace and locate items/tags.

1.1 System Requirements (Windows 10/11 & Server)

• Operating System: Windows 10 Pro/Enterprise (21H2+), Windows Server 2019/2022.
• Architecture: The FactorySoft OPC Client is typically a 32-bit COM component. It runs on 64-bit systems via WOW64 (Windows-on-Windows 64-bit).
• Memory: 4 GB RAM (8 GB recommended for high-tag-count environments).
• Dependencies: Microsoft Visual C++ Redistributables (2015-2022).

Part 2: Step-by-Step FactorySoft OPC Client Install

Follow these steps meticulously. Screenshot references are included for key dialogs. factorysoft opc client install

Step 2: Choose Installation Type

• Typical Install (Recommended): Installs the OPC client engine, the OPC Browser utility, and sample configurations.
• Custom Install: Use only if you need to exclude documentation or change the install path. Keep the default path C:\Program Files (x86)\FactorySoft\OPC Client to avoid pathing issues with legacy OPC servers.

Common installation & runtime issues

• Connection refused / server not listed:
  • DCOM permissions, Windows Firewall blocking, incorrect server name/IP.
• Access denied on connect:
  • Mismatched user accounts, missing Launch/Activation permissions in DCOM config.
• Intermittent data updates:
  • Network latency, sampling rate too high/low, server load.
• 32-bit vs 64-bit mismatch:
  • OPC Classic is often 32-bit; ensure the client and server bitness are compatible or use surrogate/COM+ bridging if needed.
• Missing OPC Core Components:
  • Install Microsoft OPC Core Components Redistributable.

Test 2: Tag Browsing and Quality

Connect to an OPC server → Expand a tag group → Select a single tag → Click "Read Value" . FactorySoft OPC Client Install — Step-by-step guide This

• Pass: Returns a value with Quality = "Good".
• Fail: Quality = "Bad" or "Uncertain" → Check data type mismatch or server configuration.

FactorySoft OPC Client Installation Guide

7. Silent Installation (for automation)

FactorySoftOPCClient_Setup.exe /quiet /norestart /log install.log INSTALL_TYPE=Complete ADD_FIREWALL_RULES=1

| Parameter | Description | |-----------|-------------| | /quiet | No UI | | /norestart | Prevent automatic reboot | | /log | Saves install log | | INSTALL_TYPE=Complete | Full installation | | ADD_FIREWALL_RULES=1 | Auto‑configure Windows Firewall | In the FactorySoft OPC Client, open the “Server

---