Unable to attach AD4630 board

Hi Ron,

Thanks for getting in touch,

There's a couple of possible causes for this issue, but in order to help us debug, can you check if there was a log file generated for the app startup so that we can determine if there is an issue in your ACE installation.

It should be in the AppData folder on your machine, see path example below:

C:\Users\USERNAME\AppData\Local\Analog Devices\ACE\AppTrace.log

If you can send the file or even the error messages it would help see if there is something missing.

Aside from that, some things to check would be:

- Open the plugin manager in ACE and check if any updates are available, especially for the AD4630 plugin or Support.IIO, Hardware.IIOSupport or Board.GenericIIO plugins. If any updates are available, install, restart ACE and try to connect again

- Open Device Manager and check that the Zedboard is appearing as a device there when connected. This will help to rule out driver level and hardware issues.

-  Ensure that you are using the OTG MicroUSB port on the Zedboard. The Zedboard has 2 MicroUSB ports, OTG and UART. Connecting via UART will show a device is present in Device Manager but ACE uses only the OTG port to interact with the Zedboard so connection in ACE will not be successful with UART.

If you could try the above and let us know the results, that will help to narrow down the cause of your issue, especially the log file.

Thanks,

Eoin

Hi EoinM,

Thanks for your response, I have

• verified that no updates are available,
• re-installed the IIOplugin from inside of ACE
• restarted my computer
• verified that the board shows up as serial port in Device Manager w/o error
• Connected to the OTG port
• and the log file here: drive.google.com/.../view

Hopefully you can have a look and point out where the problem might be

Hi Ron,

Thanks for trying those out. 

Can you just run another little test for me please.

- Along with the ACE application, you should have a console application running - IIOWCFServerHelper.exe. If you do not have this console open, I'd suggest a clean reinstallation of ACE. I'll include the steps for a clean installation of ACE at the end here.

- Press the Refresh Attached Hardware button in ACE. This will trigger a search for attached hardware and you'll see some messages in the IIOWCFServerHelper console.

- Your console should ideally look like this image here if you have IIO compatible hardware connected.

- If you're only seeing the text "Process Connected" and nothing after that, this is a known issue and for the moment I would suggest this workaround.

- Download and install MS Visual C++ redistributable 2013 from this link https://www.microsoft.com/en-us/download/details.aspx?id=40784
- Restart ACE

Would you mind attaching the log file again after following these steps please? if the solution above doesn't work for you, the updated log file will help with identifying the issue. If this does work for you, it'll greatly help improve the user experience in the future.

Thanks,

Sid

To clean reinstall ACE:

- Run the ACE uninstaller either through Add or Remove Programs in Windows settings, or from C:\Program Files (x86)\Analog Devices\ACE\uninstall.exe.
- Make sure the Scrub Uninstall checkbox is checked.

- Run the latest ACE installer downloaded from this link https://analog.com/ace
- At the "Choose Components" step, select the LibIIO Wrapper.

- Once the ACE installation is complete, open ACE and install the Board.AD4630IIO plugin

- Restart ACE.

Hi,

Thank you for the response.

Yes, I do see the console and after installation of the Visual C++ Redistributable Packages for Visual Studio 2013, it does seem to recognize the board. Yay!

The updated log file:drive.google.com/.../view

I was able to read some data until it told me at some point that there was no hardware connected. I power cycled the Zenboard and restarted ACE but only getting this now and can't seem to analyse data of the ADC anymore:

The log file is here: drive.google.com/.../view

Oh and when I hit refresh now, I get:

 and need to restart ACE to be able to re-establish connectivity..

Along with the libusb error, I also see the following in ACE: