Wiki

This version is outdated by a newer approved version.DiffThis version (12 Dec 2019 11:51) was approved by Eoin Hanrahan.The Previously approved version (12 Dec 2019 11:03) is available.Diff

This is an old revision of the document!


Known Issues

ACEZIP File Installation Unsuccessful Due to Security Block

In some cases downloading an ACEZIP file from an e-mail or from a remote/networked location has caused the file to become blocked by a security feature in Windows. This is not made clear during the download process but when the user attempts to install the ACE plug-in it will not work correctly.

If this happens, follow these steps to verify the ACEZIP has not been blocked and resolve the issue if it has:

  1. Right click the file.
  2. Select properties in the context menu.
  3. Under the General tab, if a file has been blocked a new Security tag and Unblock button will have appeared.
  4. Click Unblock.
  5. Retry the plug-in installation by double clicking the ACEZIP.

High-Speed DAC Eval Boards are not discovered

The High-Speed DAC boards have a second on-board USB controller, make sure this is connected as well as the main FPGA controller board. To avoid potential confusion, ACE only reports boards on the second controller (where it is required).


As of version 1.14, ACE replaces the driver of the on-board controller to avoid any of the conflicts with VISA drivers listed below and installs the DPGDownloaderLite application to replace the High-Speed DAC Software Suite.

However, at this time, the High-Speed DAC Eval Boards listed below are not yet supported through ACE but through a dedicated SPI application that requires the NI VISA driver. The recommended action if you are actively using these High-Speed DAC Eval Boards with dedicated SPI applications is to not update to ACE version 1.14 or install version 1.13 available here.

Not yet supported through ACE Supported through ACE with DPGDownloaderLite
AD9783/81/80 AD9129/19
AD9717/16/15/14 AD9122/21/25
AD9117/16/15/14 AD9135
AD9707/06/05/04 AD9136
AD9736/35/34 AD9142A
AD9779A/78A/76A AD9144
AD9748/44/42/40 AD9162/1/3/4
AD9148 AD9172/1/3/4/5/6
AD9146 AD9739A/7A
AD9739/37 AD9747/6/5/3/1
AD9788/87/85
AD9789
AD9993
AD9963/61
AD9767/65/63/09


For ACE version 1.13 and earlier, there is a known driver conflict issue between the NI VISA driver and Keysight's VISA driver (used for automation of equipment). To work around this, try setting the Keysight VISA driver as the secondary VISA driver. This can be done with the Keysight installer. If this doesn't work, you may need to uninstall the Keysight Driver.

The same workaround may be necessary for Rhode-Schwarz VISA.


If you need to automate equipment and use ACE at the same time you might have to use two separate PCs. The ACE remote control/scripting interface can be used by networking the PCs and setting Firewall rules appropriately.


Another possible issue causing ACE to not detect Hsdac boards is an outdated version of the “Evaluation Board Service” library. This library is installed as part of DPGDownloader. The “BitFlipper” application installer overwrites the currently installed version of the library with an incompatible one. Reinstalling the latest version of High-Speed DAC Software Suite will restore the correct version of the library.

This is the ACE log entry indicating an incompatible version of the “Evaluation Board Service”

Could not initialise DPG Client System.Exception: Could not query DPG3 for connected evaluation boards --->
System.Exception: DeviceNotResponding at AnalogDevices.DPG.USB.CSA_USB.ControlIn(Int16 requestType, Int16 request, UInt16 wValue, UInt16 wIndex, Int16 length) at
AnalogDevices.DPG.EvaluationBoards.Communication.DPG3_CSA.Finder.AttachedBoards(String[] DevicePaths)

Register Debugger Does Not Update Software Values

While not a bug, the behavior of the register debugger can be confusing and lead users to think that ACE is not successful communicating to the hardware. The register debugger reads and writes directly to the hardware, and it does not update register values stored in the software. This allows the user to avoid any events that would be triggered in the plug-in based on the register change, but this will cause the register map to be out of sync between the hardware and the software. The registers that are out of sync will be indicated by bold lettering in the register map, as seen in the figure below. If the user clicks the “Apply Changes” or if the Apply Changes transaction is executed by any other sequence in the plug-in, then ACE will update the hardware to match the UI, overriding changes made in the register debugger.


As of ACE 1.13, there is an option to change the behavior of the register debugger using the “Update Software Registers” option. Selecting this will cause both the GUI and the hardware to update when registers are read or written through the register debugger.


To preserve the changes made in the register debugger, click the “Read All” toolbar button after completing register debugger writes and before performing any additional operations in ACE.

Board & Chip Diagrams Distorted (Regional Formatting Bug)

This issue is addressed in ACE versions 1.7+

There is a known issue with some regional formats that causes bad loading and rendering of board and chip views. When the problem occurs, you may see some shapes appear with missing content and exaggerated size. The problem is particular to formats that use a comma (',') or any character besides '.' as the decimal separator.

To use the workaround, you need to temporarily change the format settings in Windows to a format that uses '.' as the decimal separator such as English (United States). For example, in Windows 7, you can access the setting through Control Panel → Change display language, click the Formats tab, and select “English (United States)” in the “Format” drop-down.

 Region and Language : Formats

ACE or SDP Driver Install Fails or Warns me the driver/exe is unsigned

Warnings may be safely ignored and dismissed, but they do highlight likely issues with your PC. The SDPDrivers and ACE package uses the latest signing technology and your PC may be out of date and unable to recognise the signing key.

  1. Make sure the PC is connected to the Internet and can get root certificate updates, normally this happens automatically.
  2. Check group policies to automatically update these run gpedit.msc
    1. Make sure the setting below is either Not Configured or Disabled UpdateRoot.png
  3. Check for and install all the latest Windows updates
  4. Check your group policy settings, these may be controlled by IT or a System Administrator
  5. Ideally select Warn as the safer option in case you later encounter malicious software
  6. Run gpedit.msc and navigate to the setting below CodeSigning.png

ACE Plug-ins Fail to Load When a Different User Logs in

This issue may affect ACE versions 1.14 and earlier.

When a machine is shared between users, the file access permissions may not be set correctly on all the installed plug-ins. The effect of this is that the plug-in cannot be accessed and fails to load. To fix this issue you will need Administrator privileges (or contact your Admin) in order to wipe out existing file permissions and reset appropriately.

  1. Using Windows File Explorer navigate to the ACE plug-ins folder (%ProgramData%\Analog Devices\ACE\Plugins)
  2. Right Click on the “Plugins” folder and select “Properties”
  3. Select the “Security” tab and click “Advanced”
  4. Choose “Change Permissions”
  5. If you see “Everyone” or “Users” click “Edit” otherwise click “Add”
  6. Grant “Full Control” or at minimum read/write/execute, click OK to dismiss the dialog
  7. Check the box “Replace all child object…”
  8. Click Apply

ACE Crashes on Startup after Update

This issues has been fixed with the latest release of ACE, v1.15.2818.1254

When updating from an older version of ACE there is an issue that can cause ACE to crash on startup. ACE can crash with one of the two following errors present in the exception.txt or AppTrace.log application log files:

 System.NullReferenceException: 
 Object reference not set to an instance of an object.
 at AnalogDevices.Csa.UI.Themes.ThemeSelector.ApplyPreferredTheme()
 at AnalogDevices.Csa.App.Wpf.CsaApplication..ctor()
 at AnalogDevices.Csa.App.Wpf.Program.Main()
 System.Exception: Cannot find resource named 'WindowBackgroundBrush'. Resource names are case sensitive.

This occurs because of a missing user setting when moving from older versions of ACE. This should not occur if you perform a scrub uninstall prior to updating the software, if you are updating from a version of ACE higher than v1.12 or if you are installing ACE for the first time.

The issue will not occur with the latest update of ACE, however if you are already experiencing this and need to resolve it in order for ACE to start, follow the steps below:

  1. Ensure ACE is not running
  2. Open the AnalogDevices folder in LocalAppData (C:\Users\username\AppData\Local\Analog Devices)
  3. Open the ACE folder
  4. Open the UserSettings folder
  5. Delete the Configuration.Settings.xml file
  6. Restart ACE

This will fix the startup issue and allow ACE to generate a new complete user settings file.

This issues has been fixed with the latest release of ACE, v1.15.2818.1254
resources/tools-software/ace/knownissues.1576147912.txt.gz · Last modified: 12 Dec 2019 11:51 by Eoin Hanrahan