KB83358
Published: November 17, 2020
Revision: 2.0

Unable to Communicate from PAC Project Software on Windows 8, Windows 10, or Newer Computer to SNAP PAC Controllers


Applies To:

PACPROJECTBAS
PACPROJECTPRO

Versions Affected:

Problem was discovered in version: R9.3x

Resolved In Version:

Problem is fixed in version: R9.4000


Symptoms:

Loss of communication from PAC Project software on Windows 8, Windows 10, or newer 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.

Workaround:

There are three possible workarounds.

Workaround #1:

  1. Try running the Windows 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 Microsoft cloud-based account and switch the machine to use a PC local account (Desktop Configuration Tool Icon > Change PC Configuration > Users > Your account).

Workaround #3:
  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.

Resolution:

Opto 22 has resolved this issue.

Questions?

Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com


DISCLAIMER

This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.

OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.

Copyright © 2024 Opto 22. All rights reserved.