Expand the table below to find the breakout board for your specific IMU.
The EVAL-ADIS-FX3 includes a laundry list of hardware and software features designed to enable in-depth test and characterization of iSensor IMUs. To get started, we suggest you first download the latest Evaluation GUI and FX3 device drivers from our GitHub page.
Once downloaded, double click on
FX3DriverSetup.exe and follow the install prompts. Once complete, the signed Analog Devices driver should be installed on your PC.
Every FX3 Evaluation GUI release is packaged inside of a .zip archive. We recommend extracting the archive somewhere convenient on your PC (like your desktop), where it can easily be accessed.
Once extracted, double click on
iSensorFX3Eval.exe to launch the GUI. Before the main GUI launches, the software will ask you to select a device configuration to load.
Select the product ID/model number of the sensor you're connecting to and click on “Apply Device Settings.”
Once you've selected the correct FX3 board, the main screen should like the image below.
Once at the main window, click on “Connect to FX3” to enable all GUI features. If the connection to the EVAL-ADIS-FX3 was successful, all of the Evaluation GUI utilities would activate. The iSensor FX3 Eval software assesses IMU Status by writing a randomly-generated number to the sensor module and reading it back.
Congratulations! If the Eval GUI looks similar to the image shown above, then you're ready to interact with the IMU and stream sensor data. Click HERE to go to the Eval GUI user guide!
If the Eval GUI shows a connection error, the section below should help debug many common connection issues.
The FX3 Evaluation GUI attempts to read and write a random number to a scratch register upon startup or when the user clicks on “Check DUT Connection.” This read and write operation does not commit any changes to the sensor's onboard flash memory and will not overwrite the register's contents. The FX3 Evaluation software will display an error if the verification operation fails. We've listed many common debugging steps to try if you encounter any errors while using our software or hardware.
These errors occur when the FX3 Evaluation GUI cannot detect or somehow loses connection with an active EVAL-ADIS-FX3 board.
The EVAL-ADIS-FX3 must be plugged into a USB Type-A port capable of at least USB 2.0 speeds. USB hubs should be avoided since the USB protocol imposes artificial power limits when connecting through one.
Many USB cables that ship with mobile phones are not capable of transferring USB data and are designed for high-speed charging. We suggest using a high-quality USB C cable (like the one included with the EVAL-ADIS-FX3) to ensure reliable, robust communication.
The Analog Devices FX3 bootloader is flashed to the onboard EEPROM as part of the EVAL-ADIS-FX3 manufacturing process. It can be verified by looking for a USB device named “Analog Devices FX3 Bootloader” in the Windows Device Manager.
If you’re unable to find the device, try resetting the FX3 by either unplugging the USB cable or pressing the reset button on the EVAL-ADIS-FX3. If this still doesn’t solve the issue, try pressing and holding the “RECOVERY” button while plugging the board into your PC. This will force the board to connect in recovery mode.
The EVAL-ADIS-FX3 includes short-circuit protection on the sensor supply pins when using the onboard (USB) supply. Even so, it is still possible to exceed the USB current limits and force the EVAL-ADIS-FX3 to brownout. A connection issue like this can be harmful to both the EVAL-ADIS-FX3 and the host PC and may permanently damage either if not corrected immediately.
The EVAL-ADIS-FX3 was designed for bench evaluation, data capture, and characterization. Even though most iSensor portfolio devices are designed and validated to operate in extreme environments, the EVAL-ADIS-FX3 was not. Exposing the EVAL-ADIS-FX3 to environments outside of typical lab use may cause it to behave unreliably.
Certain FX3 API functions can take a very long time to execute and may look like the FX3 has “locked up.” The Eval GUI has timeouts implemented during many of these function calls to prevent this behavior, but developers may occasionally run into these issues when writing their own applications.
If the board becomes unresponsive, pressing the reset button on the FX3 or unplugging/plugging the USB cable should return the FX3 to its default bootloader state.
This error occurs when the register read-back operation fails to return the number that should've been written to the first scratch register listed in the selected register map.
The EVAL-ADIS-FX3 can either supply power to the sensor using an onboard linear regulator or bypass the onboard regulator and use an external power source. The jumper must be set to “USB” when using the onboard regulator, as shown below.
It's common to invert (flip) the ribbon cable orientation when connecting the EVAL-ADIS-FX3 to a sensor coupon or breakout board. The correct cable orientation is shown below.
It's possible to shift the sensor or ribbon cable connection by one position or row. An example of a shifted connection is shown below.
The name of the active profile and register map can always be found on the main form, as shown below.
If the incorrect profile was accidentally loaded, a new one could be selected by connecting to the FX3 and clicking on the “Select DUT Type” button on the main window.
It's possible to change the EVAL-ADIS-FX3 configuration such that it exceeds the SPI specifications listed on the sensor's datasheet. Reloading the device configuration by clicking “Select DUT Type” in the main window will always restore the SPI settings to a known-good configuration.
Some logic analyzers and in-circuit debuggers will hold GPIO lines at specific states such that either the EVAL-ADIS-FX3 or the sensor cannot source/sink enough current to force a transition.
The EVAL-ADIS-FX3 was not designed to drive long cable lengths without adding additional driver circuitry. As cable length increases, the SPI signal integrity will quickly deteriorate. Variables such as SPI SCLK rate and stall time will also influence the overall cable length. A long cable will usually result in zeros intermittently inserted in random registers and incomplete register writes.
The EVAL-ADIS-FX3 firmware includes an error logging feature that stores any exceptions generated during operation into the onboard EEPROM. When reporting an issue, it’s helpful to provide this file since it will help us recreate and diagnose the issue's root cause. The firmware log is unique to each EVAL-ADIS-FX3 and is only transmitted to the PC when requested by the user.
To extract the firmware log, connector to the EVAL-ADIS-FX3 in question, navigate to the “Advanced” tab and click on the “Check FX3 Error Log” button.
This window will list the number of errors logged in the EVAL-ADIS-FX3 EEPROM and allow you to extract a log file. This file contains firmware metadata and the exact line in the FX3 firmware where the error was generated. Providing this information greatly speeds up the debug process and plays a crucial role in determining the error's root cause.
If the Eval GUI ever encounters an exception, an error log will be generated and stored in:
C:\ProgramData\Analog Devices\FX3ExampleGUI\ERROR_LOG.csv When reporting an issue on GitHub, please be sure to attach this error log to help us further understand the root cause of the exception.