Creative Commons images are CC BY-NC-SA 3.0

14.95

added to your
shopping cart

quantity
24 available 24 in stock
14.95 1+ units
13.46 10+ units
11.96 100+ units

Description: We've been using and selling Analog Devices' ADXL accelerometers for a good while now, and now we've found another great part in the series! The ADXL362 is a complete 3-axis MEMS acceleration measurement system that operates at extremely low power consumption levels. It measures both dynamic acceleration, resulting from motion or shock, and static acceleration, such as tilt. It's easy to communicate with the ADXL362 over SPI and built-in digital logic even enables autonomous operation for "wake-on-shake" operation.

We think this is a really cool device, so we spun up a breakout board! Now you can add low-power-consumption motion sensing to your next project!

Features:

  • 3-Axis: ±2, ±4, ±8
  • Ultralow Power
  • SPI Digital Interface
  • High Resolution: 1 mg/LSB
  • Low Noise Down to 175 μg/√Hz
  • Wide Voltage Range: 1.6 V to 3.5 V
  • Adjustable Threshold for Motion Activation
  • Measurement Ranges Selectable via SPI Command

Documents:

Comments 22 comments

  • An Arduino Library can be found here:

    http://annem.github.com/ADXL362

  • What is the measure unit of the sensor readings? G or mG? Thanks.

  • My readings show

    “XDATA = -1 YDATA = -1 ZDATA = -1 Temperature = -1”

    and do not change. Any idea as to what I’m doing wrong?

    • Most likely you’re completely failing to communicate with the chip.

      Check your connections and make sure everything’s set up right. If you’re still having issues you can contact tech support.

  • How i can read the data, and compare it? example:

    if(XValue>=0) {Serial.print(“Hello World”);}

    I only want compare the data output and I dont know which or how with this arduino library.

  • I’m using the ADXL362 library along with my Arduino Uno. All connections are sound and x,y,z readings are flowing. Can anyone guide me on how to convert these readings (accelerations) into angle/degrees?

    • Most universities should have a little page describing the calculations, but one example is here. It’s math intensive if you do it by hand-I’d recommend checking the Arduino forum for example code someone may have written to handle the computations for you.

      • Thanks Toni_K! Lemme be more clear though… what is the max and min value I could see on the Arduino digital pin? In other words if I knew x could only equal -64000 through 64000 I could do some basic division to get me the meaningful value I need. Guess it’s more of an Arduino/SPI question than calculation question. Thanks!

        • Ah, gotcha. Sorry for the misunderstanding. That would simply be a matter of reading the registers for each axis and again, translating that to a usable value of acceleration. The pertinent information for this is going to be in the datasheet for the sensor. Keep in mind though that acceleration is not the same as position/orientation. You’re still going to need to do some derivations to get the angles from the acceleration readings.

  • I would like to know if this purchase come with the breakout board and the ic ? And is that all are already assembled (welded) ?

  • Just received the ADXL362 and have it wired up to an Arduino 2560. Ran the Arduino library example linked above and have the following results:

    Soft Reset

    Setting Measeurement Mode - Reg 2D before = 0, Reg 2D after = 0

    Start Burst Read of all Control Regs - Library version 6-24-2012: Reg 20 = 0 Reg 21 = 0 Reg 22 = 0 Reg 23 = 0 Reg 24 = 0 Reg 25 = 0 Reg 26 = 0 Reg 27 = 0 Reg 28 = 0 Reg 29 = 0 Reg 2A = 0 Reg 2B = 0 Reg 2C = 0 Reg 2D = 0 Reg 2E = 0

    Obviously not correct. Any ideas what I did wrong? Or is the ADXL362 been hosed?

    • I had the same thing. I had Slave Select on pin 53, which I got from reading the SPI material on the arduino site. I read the ADXL362.cpp file and found that they had SS on pin 10. So I changed that to pin 53. I also had issues correctly changing the logic level from 5V to 3.3. But everything is working now. Hope that helps

      • So I switched over to my STK600 with an AtMega2560. Wired everything correctly according the docs, running the STK600 at 2.0V. Attempted to read the DEVID from the device with the following bytes sent in order: 0x0B 0x00 0x00. The result after the 3rd byte was 0xFF which is incorrect. Verified everything with a scope to make sure bytes sent and received. MOSI looks good going out, MISO shows all high during the 3rd clock sequence for the 3rd byte transfer. I also have a ADXL345 which I have successfully been able to wire up and run, no problems. Any help appreciated.

  • I’ve wired this up following the tutorial that comes with the library, but when I run the test sketch with the device resting on the table, it just spits out semi random sequences of numbers:

    XDATA = -32 YDATA = 792 ZDATA = 448 XDATA = -289 YDATA = 272 ZDATA = 688 XDATA = -799 YDATA = 524 ZDATA = 688 XDATA = -285 YDATA = 272 ZDATA = 1196 XDATA = -32 YDATA = 272 ZDATA = 1204 XDATA = 224 YDATA = 524 ZDATA = 1188 XDATA = -285 YDATA = 280 ZDATA = 1204 XDATA = -285 YDATA = 780 ZDATA = 448 XDATA = -32 YDATA = 512 ZDATA = 688 XDATA = -32 YDATA = 272 ZDATA = 700 XDATA = 224 YDATA = 272 ZDATA = 688 XDATA = 224 YDATA = 280 ZDATA = 700

    There’s sort of a pattern in the same numbers returning, but I would expect values around 0. When I move it, there is definetely a change in the sequence, so it is picking up some sort of acceleration. When I run it in 8-bit mode, it seems a bit more stable, but still unexpected reading, especially for X:

    XDATA = 254 YDATA = 0 ZDATA = 8 XDATA = 254 YDATA = 0 ZDATA = 8 XDATA = 254 YDATA = 0 ZDATA = 8 XDATA = 252 YDATA = 0 ZDATA = 8 XDATA = 252 YDATA = 0 ZDATA = 8 XDATA = 254 YDATA = 0 ZDATA = 16 XDATA = 254 YDATA = 0 ZDATA = 8 XDATA = 252 YDATA = 0 ZDATA = 16 XDATA = 254 YDATA = 0 ZDATA = 8 XDATA = 254 YDATA = 0 ZDATA = 8

    I’m running it at 3.3V from a Pro Mini 168, 8Mhz. Is it broken or did I zap it when soldering the pins on?

    • I had a similar display on mine. I also noticed the display showed “Reg 2D after = 0” not 2 as expected.. I found that the ground to the device was open due to a bad socket on the breadboard. once it had a good ground it work as shown in the HOW - TO

  • I bought one of these planning to use it with a TI MSP430 Launchpad board; turns out the board runs at 3.6V, and not 3.3V as I had thought. The ADXL362 datasheet lists a maximum operating voltage of 3.5V and an absolute maximum rating of 3.6V. Does anybody know if it’s likely to work without problems, or do I need to do some level translation? Would a diode on each supply and I/O line be enough to do the job?

    • Diodes would be a reasonable quick-and-dirty way to interface this board to the 3.6V Launchpad. Use them on the power supply and any I/O line going -to- the ADXL362 (the ones coming back won’t be a problem). That should bring all the voltages into spec. There’s a good chance that it would work fine at 3.6V, but personally I take datasheet numbers seriously. Good luck!

  • Will you have just the adxl362 available without the board?


Related Products