User guide
Top view
Bottom view
Hardware guide
For detailed hardware documentation, refer to:
AD-FMCOMMS11-EBZ Hardware - Board overview, PCB layers and dimensions
AD-FMCOMMS11-EBZ Functional Overview - System block diagram and signal paths
AD-FMCOMMS11-EBZ Characteristics & Performance - Transmitter and receiver characterization
Design files (schematic, PCB layout, bill of materials) are available here.
Software guide
The FMCOMMS11 evaluation board is supported with the libiio library. This library is cross-platform (Windows, Linux, Mac) with language bindings for C, C#, Python, MATLAB, and others.
ADI IIO Oscilloscope
The IIO Oscilloscope is a cross-platform application for interfacing with IIO devices, enabling you to configure device parameters and visualize data.
Important
Make sure to download/update to the latest version of IIO Oscilloscope.
For Linux
Remote run on host
The IIO Oscilloscope application can be used to connect to another platform that has a connected device, to configure the device and read data from it. This application is not for performance testing, but rather showcasing the basic features.
Please see IIO Oscilloscope documentation for installation steps and more details.
Build and start osc on a network-enabled Linux host.
For Windows computers, open the application from the start menu.
Once the application is launched, go to Settings > Connect > URI and type “ip:” then the IP address of the target in the pop-up window. This IP can be found out with a command from the previous section of this documentation.
Plugin
This project also contains an IIO-Oscilloscope device-specific plugin that enables you to access the unique features and functions of the device.
See also
For more information about this plugin: FMCOMMS11 Plugin Description
Scopy
Scopy is a cross-platform software toolbox for interfacing with ADI devices, enabling you to configure device parameters, visualize data, and perform advanced signal analysis.
PyADI-IIO
PyADI-IIO is a Python abstraction module for ADI hardware with IIO drivers. An FMCOMMS11 example can be found here.