Thanks for the support. I called opto support, and was directed to this article (which I’ll try today)
Loss of communication from PAC Project software on Windows 8 computer to SNAP PAC controllers
Problem was discovered in version:
Loss of communication from PAC Project software on Windows 8 computer to SNAP PAC controllers. Viewed in any PAC Project configuration window, a configured controller that appears normally as, for example, PacController is displayed as \PacController\PacController after the problem occurs.
When you try to modify a controller, the network is locked into 255.255.255.255 and cannot be altered. An attempt to add a new controller results in the same corrupted name and network. No communication from an affected PC to a controller (including a SoftPAC local controller) will occur while this problem is experienced.
There are three possible workarounds.
1.Try running the Windows 8 compatibility troubleshooter on the PAC Project executable files Term.exe, Control.basic.exe and Control.pro.exe. Or manually configure these files to run in “Windows XP Spk3” compatibility mode.
2.After running the Compatibility troubleshooter or manually changing the compatibility mode to Windows XP Spk 3, manually recreate the controller definitions using either PAC Term or PAC Control.
Workaround #2: Disconnect your Windows 8 Microsoft cloud-based account and switch the machine to use a PC local account (Desktop Configuration Tool Icon > Change PC Configuration > Users > Your account).
1.Exit PAC Control.
2.Right-click the icon for PAC Control and choose the “run as admin” option.
3.Add the control engine again.
Opto 22 is investigating this issue.