This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:eval:user-guides:inertial-mems:imu:adis16000-adis16229-eval-adis [12 Aug 2013 22:06] – [Main Menu Overview] Deepak Kumar Anigulu Mohan | resources:eval:user-guides:inertial-mems:imu:adis16000-adis16229-eval-adis [17 Feb 2021 06:09] (current) – Added demo system info Juan Chong | ||
---|---|---|---|
Line 1: | Line 1: | ||
=====ADIS16000/ | =====ADIS16000/ | ||
====OVERVIEW==== | ====OVERVIEW==== | ||
- | The ADIS16000 and ADIS16229 enable creation of a simple | + | The [[adi>ADIS16000|ADIS16000]] |
wireless vibration-sensing network for a wide variety of | wireless vibration-sensing network for a wide variety of | ||
industrial-equipment applications. . The ADIS16000 provides | industrial-equipment applications. . The ADIS16000 provides | ||
the gateway function, which manages the network, while the | the gateway function, which manages the network, while the | ||
- | ADIS16229 provides the remote sensing function. The ADIS16000 SPI interface provides simple connectivity with | + | ADIS16229 provides the remote sensing function. The [[adi>ADIS16000|ADIS16000]] |
most embedded processor platforms and the SMA connector | most embedded processor platforms and the SMA connector | ||
interface enables the use of many different antennas. This | interface enables the use of many different antennas. This | ||
- | module supports up to six ADIS16229 devices at one time, | + | module supports up to six [[adi>ADIS16229|ADIS16229]] |
using a proprietary wireless protocol. Once it has appropriate power on the VDD pin, the ADIS16000 | using a proprietary wireless protocol. Once it has appropriate power on the VDD pin, the ADIS16000 | ||
will automatically begin a self-initialization process. Once this | will automatically begin a self-initialization process. Once this | ||
Line 18: | Line 18: | ||
indicates when to avoid SPI communication requests. | indicates when to avoid SPI communication requests. | ||
- | {{: | + | {{ : |
====REQUIRED MATERIALS==== | ====REQUIRED MATERIALS==== | ||
- | ADIS16000AMLZ | + | [[adi> |
ADIS16COM1/ | ADIS16COM1/ | ||
- | ADIS16229AMLZ | + | [[adi> |
[[adi> | [[adi> | ||
Line 35: | Line 35: | ||
* Net Framework 3.5 | * Net Framework 3.5 | ||
+ | ====DEMO SYSTEM==== | ||
+ | [[: | ||
+ | Click on the link above to visit a demo system developed around the ADIS16000/ | ||
====ADIS16000 INSTALLATION ON EVAL-ADIS==== | ====ADIS16000 INSTALLATION ON EVAL-ADIS==== | ||
- | For those who would prefer to perform PC-based evaluation of the ADIS16000/ | + | For those who would prefer to perform PC-based evaluation of the ADIS16000/ |
{{: | {{: | ||
Line 49: | Line 52: | ||
Use the 4 M2 x.4 x 6mm screws from the included bag and line up the ADIS16COM1/ | Use the 4 M2 x.4 x 6mm screws from the included bag and line up the ADIS16COM1/ | ||
- | {{: | + | {{: |
- | {{: | + | {{: |
<WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
**WARNING: | **WARNING: | ||
Make sure that the connector cable going from J1 on the [[adi> | Make sure that the connector cable going from J1 on the [[adi> | ||
- | {{: | + | {{: |
=== Step #2 === | === Step #2 === | ||
- | Carefully insert the ADIS16000AMLZ into the mating connector J2 of the previously installed ADIS16COM1/ | + | Carefully insert the [[adi> |
{{: | {{: | ||
- | {{: | + | {{: |
====ADIS16229 INSTALLATION==== | ====ADIS16229 INSTALLATION==== | ||
- | This section is a continuation and focuses on [[adi> | + | This section is a continuation and focuses on [[adi> |
{{: | {{: | ||
=== Step #1 === | === Step #1 === | ||
- | The [[adi> | + | The [[adi> |
{{: | {{: | ||
- | {{: | + | {{: |
- | <WRAP center round alert 60%> | + | <WRAP center round alert 80%> |
- | **WARNING: | + | **WARNING: |
=== Step #2 === | === Step #2 === | ||
Line 84: | Line 86: | ||
{{: | {{: | ||
- | <WRAP center round box 60%> | + | <WRAP center round box 90%> |
- | **NOTE:** The antenna used in this [[adi> | + | **NOTE:** The antenna used in this [[adi> |
</ | </ | ||
====VIBRATION SOFTWARE INSTALLATION==== | ====VIBRATION SOFTWARE INSTALLATION==== | ||
- | MARK: Think about title for best branding | ||
- | |||
- | Download location (MARK: upload to EVAL-ADIS " | ||
+ | The [[adi> | ||
====USB Driver Installation==== | ====USB Driver Installation==== | ||
- | The SDPDrivers.exe file contains USB drivers that are compatible with both 32-bit and 64-bit Windows systems. Double-click on the SDPDrivers.exe file and follow the prompts to install the USB driver files onto the PC. When the following window appears, click on **Next** and then click on **Install** to continue with the 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. |
- | {{: | + | |
- | The following pictures show the progress bar and the final confirmation window. Click on **Finish** to complete the installation. | + | {{: |
- | {{: | + | When the setup wizard opens, click on **Next** to start the installation process |
- | {{: | + | |
+ | {{: | ||
- | Software copy (executable file) to correct | + | Click on **Next** |
+ | |||
+ | {{: | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{: | ||
Line 115: | Line 127: | ||
When the application is opened, SPI communication is setup between ADIS16000 (Gateway Node) and the Evaluation board. Upon successful SPI communication with ADIS16000, a command to add a sensor node to the network is issued. | When the application is opened, SPI communication is setup between ADIS16000 (Gateway Node) and the Evaluation board. Upon successful SPI communication with ADIS16000, a command to add a sensor node to the network is issued. | ||
- | {{ : | + | {{ : |
When the user clicks on **ok** in the above message, the main window with an active tab ' | When the user clicks on **ok** in the above message, the main window with an active tab ' | ||
- | + | {{ : | |
- | {{ | + | |
<WRAP center round box 60%> | <WRAP center round box 60%> | ||
Line 129: | Line 139: | ||
When the user sees the following error message, Ensure that ADIS16000 is connected to the Eval Board. | When the user sees the following error message, Ensure that ADIS16000 is connected to the Eval Board. | ||
- | {{ : | + | {{ : |
When the user sees the following error message, Ensure that ADIS16000 is selected in **Devices** drop-down menu. | When the user sees the following error message, Ensure that ADIS16000 is selected in **Devices** drop-down menu. | ||
- | {{ : | + | {{ : |
User is notified of an unsuccessful addition of a sensor node to the network as shown below. | User is notified of an unsuccessful addition of a sensor node to the network as shown below. | ||
- | {{ : | + | {{ : |
Unsuccessful addition of the sensor node can occur under the following circumstances.. | Unsuccessful addition of the sensor node can occur under the following circumstances.. | ||
**Case 1:** A new sensor node had not been powered on during the initial start of the application. | **Case 1:** A new sensor node had not been powered on during the initial start of the application. | ||
- | If this is the case, User can turn on the sensor and follow connecting nodes section for adding the new sensor. | + | If this is the case, User can turn on the sensor and follow |
- | **Case 2:** ADIS16000 had been reset and the sensor node is already part of the network with a sensor identifier flashed in it. As a result, the sensor node does not respond to the command for adding a new sensor to Gateway. In order to check this case, follow Scan Network section for updating Gateway with already existing nodes. | + | **Case 2:** ADIS16000 had been reset and the sensor node is already part of the network with a sensor identifier flashed in it. As a result, the sensor node does not respond to the command for adding a new sensor to Gateway. In order to check this case, follow |
**Case 3:** ADIS16000 or ADIS16229 is in an unknown state. Power cycle both the parts and restart the application. | **Case 3:** ADIS16000 or ADIS16229 is in an unknown state. Power cycle both the parts and restart the application. | ||
Line 153: | Line 163: | ||
A sensor was successfully added to the network. User can start a FFT capture from sensor 1 by clicking on **Start** button. Any user initiated command is issued to the sensor node whose tab is currently active. For example, if Sensor 1 tab is held active by clicking on it and then a start command is issued, FFT capture is obtained from Sensor Node 1. | A sensor was successfully added to the network. User can start a FFT capture from sensor 1 by clicking on **Start** button. Any user initiated command is issued to the sensor node whose tab is currently active. For example, if Sensor 1 tab is held active by clicking on it and then a start command is issued, FFT capture is obtained from Sensor Node 1. | ||
- | {{ : | + | {{ : |
+ | ====Automatic/ | ||
+ | In order to change the mode from Manual to Periodic FFT, the drop down box needs to be clicked and appropriate mode can be selected as shown below. Automatic mode is started with a default update interval of 2 secs. The automatic or periodic mode can be stopped by double clicking **//<fc # | ||
- | ====Automatic/ | + | {{ : |
- | In order to change the mode from Manual to Periodic FFT, the drop down box needs to be clicked and appropriate mode can be selected as shown below. Automatic mode gets started with a default update interval of 2 secs. The automatic or periodic mode can be stopped by double clicking **//<fc # | ||
- | {{ : | ||
- | ==== Reconfiguring the Sensor Nodes ==== | + | ===Reconfiguring the Sensor Nodes ==== |
Line 174: | Line 184: | ||
Hold the respective sensor node active by clicking on its tab in the main wondow and then Click on Register access menu. | Hold the respective sensor node active by clicking on its tab in the main wondow and then Click on Register access menu. | ||
- | {{ : | + | {{ : |
**Step 2:** | **Step 2:** | ||
In the register access menu, Scroll down to the registers of the respective sensor page indicated by Page column of the Table as shown below. Click on the register that needs to be modified | In the register access menu, Scroll down to the registers of the respective sensor page indicated by Page column of the Table as shown below. Click on the register that needs to be modified | ||
- | {{ : | + | {{ : |
**Step 3:** | **Step 3:** | ||
Enter the new value in the box and hit Write. | Enter the new value in the box and hit Write. | ||
- | {{ : | + | {{ : |
**Step 4:** | **Step 4:** | ||
Scroll up to registers in Page 0 and then Select COMMAND_16K. Write the command 0x02 which is a command to update the sensor node. A wait of 400 ms will ensure that the sensor is updated with the new settings. | Scroll up to registers in Page 0 and then Select COMMAND_16K. Write the command 0x02 which is a command to update the sensor node. A wait of 400 ms will ensure that the sensor is updated with the new settings. | ||
+ | {{ : | ||
- | {{ : | ||
+ | <fc # | ||
+ | |||
+ | The user can alternately use Register access to set up the periodic mode. When a remote sensor is set up in periodic mode using Register access and data collection is started, the sensor can be stopped only by writing **0x800** to the <fc # | ||
+ | |||
+ | < | ||
+ | </ | ||
+ | |||
+ | < | ||
Line 214: | Line 229: | ||
- | {{ : | + | {{ : |
====Alarm Configuration==== | ====Alarm Configuration==== | ||
Line 236: | Line 250: | ||
The user can initiate a capture in Manual FFT mode to check for the Alarms. At the end of the capture, the Alarm status should refresh indicating the status of Alarms in the capture. | The user can initiate a capture in Manual FFT mode to check for the Alarms. At the end of the capture, the Alarm status should refresh indicating the status of Alarms in the capture. | ||
- | {{ : | + | {{ : |
When an alarm is triggered, the alarm status window indicates it with a yellow shade or a red shade on the corresponding band and axis in the table. The yellow shade indicates a lower threshold alarm has been | When an alarm is triggered, the alarm status window indicates it with a yellow shade or a red shade on the corresponding band and axis in the table. The yellow shade indicates a lower threshold alarm has been | ||
activated. The red shade indicates that the higher threshold has been activated in the corresponding band and axis. | activated. The red shade indicates that the higher threshold has been activated in the corresponding band and axis. | ||
- | {{ : | + | {{ : |
Line 253: | Line 265: | ||
**Step 2:** Click on **Scan Network** button. | **Step 2:** Click on **Scan Network** button. | ||
- | + | {{ : | |
- | {{ : | + | |
The Gateway node checks for every node in the network( Node 1 through 6) and updates its sensor map at the end of it. | The Gateway node checks for every node in the network( Node 1 through 6) and updates its sensor map at the end of it. | ||
Line 262: | Line 273: | ||
- | MARK: Think about title for best branding | + | MARC: Think about title for best branding |