Table of Contents
VIBRATION EVALUATION PROGRAM WIKI GUIDE
|IMU Evaluation/EVAL-ADIS Product Support List|
PC SYSTEM REQUIREMENTS
Windows XP, Vista, 7
.NET Framework 3.5
NOTE: Newer versions of the .NET framework do not currently support the Vibration Evaluation Program.
VIBRATION EVALUATION PROGRAM DOWNLOAD
Vibration Evaluation Software installation only requires two simple step:
1. Download, unzip and install the EVAL-ADIS USB Driver (click here to see the download link)
2. Download, unzip and copy the Vibration*.exe file to the desired location on the test PC (click here to see the download link)
USB DRIVER INSTALLATION
After downloading the EVAL-ADIS USB Driver file, extract the SDPDrivers.exe file from the zip file, into a convenient location and then double click on it to start the process.
When the setup wizard opens, click on Next to start the installation process
Click on Next to accept the default driver location.
The process will involve at least two progress bars that look like the following:
If you encounter this type of message during the process, click on Install to continue with the installation.
Once the installation has completed, click on Finish to complete the process.
Download to the Vibration Evaluation Program package from the EVAL-ADIS home page, under SOFTWARE AND TOOLS (Click here to access). Extract the *.exe file from the zip file and copy it to any directory on the PC.
Plug the EVAL-ADIS (with ADIS16xxx/PCBZ device installed) and wait for both LED1 and LED2 to illuminate on the EVAL-ADIS. After LED1 and LED2 illuminate, double click on the *.exe file to launch the Vibration Evaluation Program and access the Main Menu.
You might see the appearance of a Window that indicates a search for an SDP device (USB), but this will disappear quickly. If this error message appears, click OK to proceed to the Main Screen.
Click on Device, located on the left hand side of the Menu bar, at the top of the Main Screen, to select the appropriate DUT (Device Under Test). In this example, the ADIS16228 is in use. Note that some of the Menu bar options appear in a lighter gray color, to indicate that they are not associated with a particular device. For example, all of the Network options presently only apply to the ADIS16229 at this time, so they will appear in the lighter gray color when either ADIS16227 or ADIS16228 options are in use.
The Register Access option on the Menu Bar provides direct read and write access to all of the user-accessible registers in DUT.
Register Access Window Appearance
Here is an example of the Register Access window that illustrates the ADIS16228.
Reading Register Contents
Writing Data to Registers
Use the following two steps to write a value to the register. 1. Enter the hex code for the register.
2. Click on Write
NOTE: Clicking on Write causes the Vibration Evaluation Program to write to both upper and lower bytes
The vibration sensor products often come with registers that support “Global Commands.” While these commands are associated with specific bits, located in user-accessible registers, the right side of the Register Access Window provides access to them through a drop down menu that offers each related register and a series of Write buttons.
The Alarm > Alarm Settings option on the Menu Bar provides a more convenient method for configuring the Spectral Alarm functions. This provides a more convenient method for tuning this function, in comparison with the single-register access method associated with Register Access window.
Selecting Alarms > Alarm Settings will cause the following window to open:
Select boxes in the matrix and enter values that are associated with the magnitude of the output data and FFT bin numbers.
Click on Write to DUT to update all registers that are associated with these entries.
Close this window, then go back in. The values will not appear automatically. Click on Read from DUT to make sure the settings are still in place.
The Alarms > Alarm Status Form option provides a convenient monitor for the conditions. The dashes will change to green (no alarm), yellow (“warning” alarm, associated with Level 1) or red (“critical” alarm, associated with Level 2), depending on the conditions, after a data capture event completes.
The Data Capture window provides user inputs for file location, base file name and for resetting the file count.
When this function is active (See the Enable Data Capture checkbox, located in the Main Screen), each trigger will cause the creation of a new file that contains the FFT result and FFT Header information. Notice the increments in the file count, after three clicks on the Start button.
This counter is also in the Data Capture Window
The Tools option in the Menu Bar offers two options: USB and SPI.
Use the USB option to manually connect or disconnect to the USB port on the EVAL-ADIS.
Use the SPI option to adjust the timing in between the EVAL-ADIS and the DUT. this should not be required for normal operation but the “typical” settings are offered in the following picture:
Visit the ADIS16229 Vibration Demo Wiki Guide for more details on this function.
Data Collection Mode
The ADIS16227, ADIS16228 and ADIS16229 all have four basic modes of data collection: Manual FFT, Automatic FFT, Manual Time (Time Domain) and Real-Time. Inside of these products, these modes are typically related to the settings in the REC_CTRL1 register. The Main Screen offers a drop-down selection menu for these modes, along with a Start button to begin operation.
Enable Data Capture
Checking the box next to Enable Data Capture results in every capture of data being copied into a data file, according to the configuration settings in the Data Capture Window.
SOFTWARE REVISION HISTORY
|REVISION||RELEASE DATE||SUMMARY OF UPDATES|
|v1.3.0||2/17/2014||See the Reported Issues & Solutions Table for list of issues being addressed|
|v1.2.0||1/25/2014||See the Reported Issues & Solutions Table for list of issues being addressed|
|v1.1.9||12/22/2013||See the Reported Issues & Solutions Table for list of issues being addressed|
|v1.1.8||N/A||Internal test version, never published online|
|v1.1.7||12/10/2013||Added partial support for the ADIS16227 (Manual FFT mode only)|
|v1.1.6||11/1/2013||Extended the wait time to 4 seconds, for each sensor in the Network Scan|
|v1.1.5||N/A||This version corrects a sizing problem in the main waveforms, along with a couple of bugs in other windows.|
|v1.1.4||N/A||Updates for internal use only|
|v1.1.3||N/A||Added delays to Periodic Mode Exit routine register writes.|
|v1.1.2||N/A||Added a dialog box for a user to specify the Update Interval of the Network Periodic Mode.|
|v1.1.1||10/11/2013||Corrected the GUI to indicate “not busy” after a communication is canceled by the user.|
|Added exception handling routines to prevent a program crash and to show the Reconnect Dialog if the USB is disconnected.|
|Expanded the vertical axis range options on the FFT plots (Main Menu) to go down to 0.0001g|
|v1.1.0||N/A||Added “Scan All Channels” option to find nodes that are on different frequency channels|
|Expanded the vertical axis range options on the FFT plots (Main Menu) to go down to 0.001g|
|v1.0.3||9/10/2013||Set the plot scale to +-2g for the first switch to time domain data. This ensures that data is visible on the plot. Subsequent plot mode changes set the scale to the previous user selected value for a particular mode.|
|Set the Mode combo-box to ‘Periodic’ or ‘Manual’ when a demonstration mode is selected. This ensures that the plot mode is appropriate for the data displayed during a demonstration loop.|
|v1.0.2||8/21/2013||Add sensor node selection tabs to Register Access and Alarm menus|
|NOTE: First version posted online at www.analog.com/EVAL-ADIS|
|v1.0.1||8/15/2013||Updated register names to match the ADIS16229 datasheet|
|Increased period mode sleep cycle time to 10 seconds|
REPORTED ISSUES, UPGRADE REQUESTS & SOLUTIONS
|REVISION||#||DATE||STATUS||DEVICE||DESCRIPTION & RELATED NOTES||SOLUTION|
|v1.3.1||01||7/29/14||CONFIRMED||ADIS16228||Real-time mode does not work after executing an Auto-null command in the Register Access menu. Click here for more details||After executing an Auto-null command, select Manual FFT mode first, then Real-time mode.|
|v1.3.0||01||2/24/14||CONFIRMED||ADIS16228||Real-time only supports data collection at a rate of 1.26kSPS||v1.4.0 will address this. For now, use AVG_CNT settings that are > 4 (Sample rate = 1260 SPS)|
|v1.2.0||04||2/12/14||CLOSED||ADIS16000||Connection with ADIS16229 is hard to establish||SPI Timing violation, click here for more details|
|v1.2.0||03||1/27/14||CONFIRMED||ADIS16228||Time Domain mode in this package seems to translate into Manual Time Capture in the ADIS16228 datasheet. Can the software be consistent with the datasheet?||v1.3.0 (or later), Not released yet|
|v1.2.0||02||1/27/14||CONFIRMED||ADIS16228||The Data Capture function does not appear to work when using Time Domain mode||v1.3.0 (or later), Not released yet|
|v1.2.0||01||1/27/14||CONFIRMED||ADIS16228||When using the Data Capture function, when in Real-Time mode, can this produce one continuous file for the data samples?||v1.3.0 (or later), Not released yet|
|v1.1.9||01||1/9/14||CLOSED||ADIS16228||Add all of the FFT Header registers to the Data Capture file||v1.2.0 (or later)|
|v1.1.7||06||12/17/13||CLOSED||ADIS16228||There appear to be a few typos in the register names in Register Access menu, as they do not match the names given in the ADIS16228 datasheet||v1.1.9 (or later)|
|v1.1.7||05||12/17/13||CLOSED||ADIS16228||Exiting Periodic FFT mode causes the program to jump into the Main Screen > Tools > USB Menu. When closing that Window, it engages in a 10 second countdown while allowing no user input.||v1.1.9 (or later).|
|v1.1.7||04||12/17/13||CLOSED||ADIS16228||Changes in the Mode Selection drop-down menu, located in the Main Screen, do not seem to track the related register settings in the Register Access menu||v1.1.9 (or later).|
|v1.1.7||03||12/13/13||CLOSED||ADIS16228||Manual FFT only seems to support 20480 SPS sample rates. For more details, click on the following file: Problem Report Details||v1.1.9 (or later).|
|v1.1.7||02||12/10/13||CLOSED||ADIS16228||The Alarm Status Form does not correctly display alarm status. Click on this file for more details: Problem Report Details||No issue found. Open this file for more details: Problem Resolution Details|
|v1.1.7||01||12/10/13||CLOSED||ADIS16227||Periodic FFT appears to lock the software up and does not appear to produce FFT results||v1.2.0 (or later)|
|v1.1.6||06||12/9/13||CONFIRMED||ADIS16000||There appear to be a few typos in the register names in Register Access menu, as they do not match the names given in the ADIS16000 datasheet||v1.1.10, release date estimate = 1/10/2014|
|v1.1.6||05||12/9/13||CLOSED||ADIS16000||Not able to add ADIS16229 devices to pages 2-6 in the ADIS16000||No issue found, but this will be closely scrutinized in the next two versions: v1.1.10 and v1.2.0|
|ADI: This function was verified in earlier versions of the software. Re-test of this function is in the test queue.|
|v1.1.6||04||12/9/13||CONFIRMED||ADIS16000||There are a number of cases where the software becomes non-responsive, with particular sensitivity observed when using Periodic FFT.||v1.2.0, release date estimate = 1/24/2014. For present revision, use Manual FFT mode only.|
|ADI: Investigation has revealed that the present approach for simultaneous sensor monitoring and user input management is not stable. The solution to this will require substantial code changes, which are in progress.|
|v1.1.6||03||12/9/13||CLOSED||ADIS16000||Sample rate settings in the AVG_CNT register do not seem to cause updates on the horizontal axis, of the x-axis data.||Use version v1.1.9 or later.|
|v1.1.6||02||12/9/13||CONFIRMED||ADIS16000||Real-time data logging is not working||This was not part of the original plan for this package, but is under consideration for v1.4.0 or later.|
|v1.1.6||01||12/9/13||CLOSED||ADIS16000||Waveforms updates do not always respond to Start button presses, in any mode.||Use v1.2.0 or later|
|STATUS CODE DEFINITIONS|
|OPEN means that the issue observation has been received, but has not been independently confirmed by ADI|
|CONFIRMED means that the issue has been independently confirmed and ADI is working on a solution path.|
|CLOSED means that the issue has been resolved|