In the world of industrial automation, few terms evoke nostalgia and simultaneous IT headaches quite like "FactorySoft." For a significant period in the late 1990s and early 2000s, FactorySoft was a premier provider of OPC (OLE for Process Control) tools. Their client software allowed operators to connect HMIs, spreadsheets, and custom applications to PLCs and DCS systems with ease.
FactorySoft (now often associated with eMation) offers specialized toolkits for developers rather than just standalone client software. The installation typically follows a standard Windows developer setup, but because these are development toolkits, there are a few specific nuances to ensure your environment is ready. 💿 Pre-Installation Requirements factorysoft opc client install
# 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
Operating System: Windows 7, 8, 10, or Windows Server (32-bit or 64-bit). Operating System: Windows 7, 8, 10, or Windows
Register Components: The toolkit may require manual registration of certain DLL files using regsvr32 if not handled automatically by the installer. Easy Configuration : FactorySoft OPC Client provides a
However, a seemingly straightforward installation can become a troubleshooting nightmare due to DCOM permissions, Windows security updates, and 32-bit vs. 64-bit architecture conflicts. This guide walks you through every phase of the installation—from pre-flight checks to post-install validation—ensuring your OPC client communicates flawlessly.
%SystemRoot%\System32\svchost.exe (for RPCSS service).