Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
resources:eval:user-guides:inertial-mems:accelerometers:adxl362:eval-adxl362z-mlp [16 Jul 2012 22:51] – [Kit Contents] Nitzan Gadishresources:eval:user-guides:inertial-mems:accelerometers:adxl362:eval-adxl362z-mlp [03 Jan 2013 20:42] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== ADXL362 Real-Time Evaluation System ======
 +<WRAP important>This page is under construction.</WRAP>
 +
 +===== Resources =====
 +
 +==== Kit Contents ====
 +
 +1 x Low-Power Inertial Sensor Evaluation Board (LP-ISEB) (also referred to as Motherboard)\\
 +1 x ADXL362 Satellite Board\\
 +1 x ADXL362 Micropower MEMS Accelerometer\\
 +1 x Ribbon Cable (connects Motherboard to Satellite board)\\
 +1 x USB cable (connects Motherboard to computer)\\
 +8 x Standoffs + screws (stabilize the Motherboard and Satellite board on a flat surface)\\
 +
 +==== Design and Integration Files ====
 +^Schematics: |{{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:motherboard_schematic.pdf|Motherboard}}  |{{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:satellite_board_schematic.pdf|Satellite Board}}^
 +^Layouts:   |Motherboard   |Satellite Board^
 +
 +==== Installation Files ====
 +<WRAP center round download 60%>
 +// //
 +  * **Driver installer: {{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:adi_iseb_drivers.zip|.zip}}**
 +  * **LabView environment and GUI installer: [[ADI>static/imported-files/eval_boards/ADXL362_EVB_GUI_Installer.zip|.zip]]**
 +</WRAP>
 +
 +
 +
 +----
 +
 +===== Quick Start Guide =====
 +
 +==== For first-time installations ====
 +
 +
 +<WRAP center box 80%>
 +|  :!:**  If you've never used ANY of Analog Devices' Inertial Sensor Evaluation Kits before*, start here!  **:!: \\ //*This includes any of ''%%EVAL-ADXL###Z-M%%'', ''%%EVAL-ADXRS###Z-M%%'' and ''%%EVAL-ADXL###Z-MLP%%''.//  |
 +</WRAP>
 +
 +
 +  - **Begin by installing the drivers.**\\ Click on the link **[[#installation_files|above]]** to download the driver installer. Extract the entire contents of the folder and run the file **%%ADI_ISEB_USB_Drivers.exe%%**.\\ Follow the installer instructions to install the drivers. \\ \\
 +  - **Next, install the GUI.**\\ Download and run the ADI-provided **LabView environment and GUI installer**, also **[[#installation_files|above]]**. \\ Follow the installer instructions. \\ \\
 +==== For returning users ====
 +**Prior to starting the GUI, plug in the system:** \\
 +<wrap indent>Connect the motherboard to the satellite board via the ribbon cable. \\ </wrap>
 +<wrap indent>Then, connect the motherboard to the computer via the USB cable.</wrap> \\ \\
 +
 +The ADI installer places a shortcut to the GUI in the Start menu under ''All Programs'' -> ''Analog Devices - Inertial Sensor Eval'', as shown below. Click on this shortcut to start the evaluation system GUI.
 +
 +{{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:start_menu.png?200|Click for full-size image}}
 +
 +The GUI starts up grayed out with all functions disabled. Before testing any devices, you must associate the software GUI with the installed hardware by selecting the appropriate COM port from the menu in the lower left corner. **Follow [[resources:eval:user-guides:inertial-mems:evalsystem:findyourcomport|these instructions]] if you do not know which COM port to use.**\\
 +\\
 +Selecting the appropriate COM port and clicking Connect should enable all GUI functionality.
 +
 +{{ :resources:eval:user-guides:inertial-mems:accelerometers:adxl362:1.png?400 |Click for full-size image}}
 +
 +// //
 +To end the program, click the “Quit Program” button at the bottom right corner of the GUI screen, and then use the X at the top right to close the window.
 +
 +
 +----
 +
 +===== Debug Tips =====
 +In no particular order, here are a few tips for troubleshooting the system when things aren’t working:
 +  * If you see a yellow triangle next to the icon in the Device Manager, consult the Driver Troubleshooting section.
 +  * Verify the COM port in the Device Manager window. Ensure that you are connecting to this COM port when opening the GUI.
 +  * Reflash the firmware.
 +  * Make sure there is a part inside the socket: with the board unplugged (unpowered!), open the socket lid and look for a part. If you’re unsure, turn the (open) socket over into your hand and see if a part falls out. If it does, put it back in. If it does not, get another.
 +  * Try a new USB port; a new USB cable; and reconnect the ribbon cable, to isolate the possibility of a faulty connection.
 +  * Try restarting the connection. Follow these steps in this order:
 +      - Quit the GUI and close the GUI window.
 +      - Unplug the motherboard from the USB port.
 +      - Count to 10.
 +      - Plug the motherboard back in.
 +      - Start the GUI and try again.
 +
 +----
 +
 +===== The GUI =====
 +
 +The ADXL362 Evaluation System GUI includes 4 tabs for evaluation of various paramaters:
 +
 +| **[[#real-time_data|Real-time data]]**: |**View and save real-time acceleration measurements under user-input settings.** |
 +| ||
 +| **[[#power_consumption|Power consumption]]**: |**View real-time power consumption under user-input settings.** |
 +| ||
 +| **[[#temperature|Temperature]]**: |**View the effect of temperature on acceleration output.** |
 +| ||
 +| **[[#configuration|Configuration]]**: |**Write to and read from device registers.**  |
 +
 +----
 +==== Real-Time Data ====
 +{{ :resources:eval:user-guides:inertial-mems:accelerometers:adxl362:2.png?600 |Click for full-size image}}
 +
 +The Real Time Data tab configures the inertial sensor evaluation system and the ADXL362 for real-time acceleration monitoring. The tab contains an oscilloscope-like interface that you can use to view the output of the accelerometer and adjust the relevant parameters, such as output data rate, measurement range, output format, different work mode for power/noise tradeoff and Self Test (see figure above).
 +
 +**Configuration options:**
 +  * **<wrap em>Data Rate (Hz)</wrap>**: choose the desired output data rate from the pull-down list.
 +  * **<wrap em>Range (g)</wrap>**: choose the desired full-scale measurement range from the pull-down list.
 +  * **<wrap em>Output Format</wrap>**: choose between 8-bit and 12-bit (default) data.
 +  * **<wrap em>Low Noise Mode</wrap>**: choose between Normal Mode (lowest power consumption), Low Noise Mode, and Ultralow Noise Mode (lowest noise).
 +  * **<wrap em>Half BW</wrap>**: select whether the anti-aliasing filter bandwidth is set to 1/2 ODR (wider bandwidth for given ODR) or 1/4 ODR (less susceptibility to aliasing, therefore improved signal integrity).
 +  * **<wrap em>Self Test</wrap>**: engage self-test. You should see an offset appear on all 3 outputs when you chose this option.
 +
 +
 +**Functionality:**
 +  * **<wrap em>Begin real-time measurement</wrap>** by clicking the **''View Meas''** button. This causes many of the options and tabs to be grayed out or to disappear, to prevent software conflicts, until the Stop Meas button is clicked. The accelerometer output data then begins to flow across the screen. 
 +  * **<wrap em>Begin //and save// real-time measurement</wrap>** by clicking the **''View & Save Meas''** button.\\ <WRAP INDENT> When this button is clicked, the user is prompted to specify a file name and location for saving the data. Data is saved into a tab-delimited .txt file. The first row of the file always contains column labels denoting Date, Time, X, Y, and Z (for acceleration data in //g//).\\ The Save functionality is capable of saving unlimited data. To keep file size manageable, the data is split up into up to 11 separate .txt files. The first 10 files have a capacity of 64000 samples. The 11th file will contain all remaining data.\\ The name and location of the first .txt file are specified by the user upon clicking the ''**View & Save Meas**'' button. All 11 files are created as soon as the first file name and location are specified. Consecutive numeric suffixes are appended to the specified file name, and all 11 files are saved to the same location. For example, if the first file is named ''ADXL362Test.txt'' and saved to the desktop, then 11 files will be automatically created on the desktop: ''ADXL362Test.txt'', ''ADXL362Test_1.txt'', ..., ''ADXL362Test_10.txt''. Files will be filled in order as data becomes available. When measurement is stopped (via the GUI), empty files are automatically deleted. </WRAP>
 +  * **<wrap em>Stop real-time measurement</wrap>** by clicking the **''Stop Meas''** button.
 +
 +**Other readouts / indicators:**
 +  * **<wrap em>Output Graph</wrap>**
 +    * X-, y-, and z-axis acceleration values are plotted on the graph in white, red, and green respectively.
 +    * Data can be shown in LSBs or in //g//'s, as selected by the ''Output - LSB'' or ''Acceleration - g'' tab above the graph.
 +    * Use the controls in the top-right of the graph frame to recenter, zoom, and move the graph.
 +    * Double-click on any of the axes values and type in a new value to re-scale that axis.
 +    * Right-click in the graph area for additional options.
 +  * **<wrap em>Bias Values</wrap>**
 +    * **Current Vs [V]**: shows the measured supply voltage to the ADXL362.
 +    * **Current**: shows the current consumption of the ADXL362 in µA.
 +    * **Current VDD I/O [V]**: shows the measured supply voltage to the digital portion of the ADXL362 (digital logic and SPI communication).
 +    * **Temp [degC]**: shows the ambient temperature, as measured by a sensor on the satellite board.
 +  * **<wrap em>Output Values</wrap>** 
 +    * Shows x-, y-, and z-axis output values in LSBs and in //g//'s. The conversion to //g//'s assumes ideal scale factor.
 +
 +----
 +
 +
 +==== Power Consumption ====
 +
 +When used properly, the ADXL362 offers extremely low //system-level// power consumption in addition to its own device-level power savings. A deep FIFO, robust motion (and lack-of-motion) detection, and autonomous interrupt processing allow the accelerometer to operate as a motion sensor and a power manager without the intervention of a host processor. The Power Consumption tab is designed to highlight some of the ADXL362's system-level power savings features.
 +
 +{{ :resources:eval:user-guides:inertial-mems:accelerometers:adxl362:3.png?600 |Click for full-size image}}
 +
 +The following functionality is available to you within the Power Consumption tab: 
 +
 +==Modes of Operation==
 +
 +  * <wrap em>Measurement</wrap>: Configures the accelerometer for measurement mode, in which acceleration is sampled continuously at the specified data rate.
 +  * <wrap em>Standby</wrap>: Configures the accelerometer for Standby. The device is non-operational and consumes only 10 nA.
 +  * <wrap em>Auto Sleep</wrap>: Configures the accelerometer for autosleep. When inactivity is detected, the accelerometer enters a low-power, low-bandwidth mode; when activity is detected, the accelerometer enters measurement mode.
 +  * <wrap em>Wake Up</wrap>: Configures the accelerometer for wakeup mode. This is a low-power, low-bandwidth mode in which acceleration is sampled ~6 times per second, and the accelerometer sleeps to conserve power between samples.
 +
 +  * <wrap em>Meas Range</wrap>: select the desired full-scale measurement range.
 +  * <wrap em>Data Rate (Hz)</wrap>: choose the desired output data rate from the pull-down list.
 +  * <wrap em>Half BW</wrap>: select whether the anti-aliasing filter bandwidth is set to 1/2 ODR (wider bandwidth for given ODR) or 1/4 ODR (less susceptibility to aliasing, therefore improved signal integrity).
 +  * <wrap em>Low Noise Mode</wrap>: choose between Normal Mode (lowest power consumption), Low Noise Mode, and Ultralow Noise Mode (lowest noise).
 +
 +==Activity Configuration==
 +  * <wrap em>✔ Activity Interrupt</wrap>: when checked, enables activity detection.
 +  * <wrap em>THRESH_ACT [mg]</wrap>: specify the threshold, in m//g//, for activity detection.
 +  * <wrap em>Time_Act [num]</wrap>: specifies the number of consecutive samples that must be above the activity threshold (THRESH_ACT) for an activity event.
 +  * <wrap em>Coupling</wrap>: selects between AC (Referenced) and DC (Absolute) activity detection.
 +==== Temperature ====
 +{{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:4.png?600|Click for full-size image}}
 +==== Configuration ====
 +{{:resources:eval:user-guides:inertial-mems:accelerometers:adxl362:5.png?600|Click for full-size image}}
 +
 +
 +