element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
NanoRama
  • Challenges & Projects
  • Project14
  • NanoRama
  • More
  • Cancel
NanoRama
Blog Nano Rocket #3 : Making Sense of the Acceleration Data
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join NanoRama to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: dubbie
  • Date Created: 12 May 2020 2:44 PM Date Created
  • Views 3277 views
  • Likes 8 likes
  • Comments 15 comments
  • nano
  • acceleration
  • nano rocket
Related
Recommended

Nano Rocket #3 : Making Sense of the Acceleration Data

dubbie
dubbie
12 May 2020

Since I made my Nano Sense 33 BLE based data logger for a water powered rocket, and subsequent amendment to hand thrown 'rocket' I have been trying to get my head around what the data from the on-board accelerometers (x, y, z) is actually showing (Nano Rocket #1 : Hand Thrown with TTL Serial Communications  and Nano Rocket #2 : An Accelerating Truck ). There have been many helpful comments from members and I will be following some of the advice given (sorry, I forget who advised what, but thanks to you all) and I have gradually come to realise that I have been confusing acceleration with velocity, as well as trying to understand other 'real world' acceleration effects such as vibration from wheels and so on.

 

So I decided to try some calibration experiments instead and I have started with straight forward static acceleration on a table, see the video below:

 

You don't have permission to edit metadata of this video.
Edit media
x
image
Upload Preview
image

 

Then, as before, I connected the rocket to a USB - serial converter module and downloaded the data into Putty, and then cut-and-pasted it into Google sheets and obtained the following graphs, showing highlighted X, Y and Z traces.

 

X Trace Highlighted

 

image

 

Y Trace Highlighted

 

image

 

Z Trace Highlighted

 

image

 

Apart from a little bit of noise which could be vibration from the laptop fan, or other external sources, the only acceleration being applied is that due to gravity, in the downward direction. The output from the accelerometers is 1 g = 1.0 and this can be seen in all three traces. In the X trace the value is zero until the middle third (when the rocket was turned on end) and has a value of -1.0. This would have been +1.0 if I had stood the rocket on the other end but that is rounded and much more difficult to maintain in an upright position. The Y trace also shows a -1.0 in the final third of the graph which is when the rocket was held on it's side. If the other side had been used it would have been +1.0. These first two traces show a simple transition from one orientation to another, but the Z trace shows a much more interesting output. The Z trace in the first third shows a +1.0 value, as gravity is accelerating downwards. At the second reorientation two thirds of the way along there is peak as the rocket is rotated and illustrates an acceleration followed by a deacceleration.

 

Armed with this calibration data I decided to throw the rocket straight upwards so that only the Y value should show any acceleration and X and Z should be constant at 0.0. Let's see if this is correct and that I am able to throw the rocket directly upwards. So, time for some tea and a sit outside in the sunshine, then some throwing!

 

A few technical issues intervened in the sitting in the sun, drinking tea, collecting data scenario: it was nearly lunch time so I went without the tea, plus the sun went in so there was no sitting. Also, perhaps more importantly, because I was throwing the rocket directly upwards, or mostly directly upwards, it meant it came almost directly down and as I have mowed the lawn, there was very little buffering and the rocket hit quite hard, causing a power reset. After some additional packaging and repeated attempts I managed to obtain the following data.

 

image

 

It still looks confusing but I started the rocket pointing directly upwards in order to obtain the -1.0 (approximately) on the X trace, as seen in the previous calibration traces. I then threw the rocket as directly upwards as I could manage, indicate by the spikes at sample number 325 (approx.). At this point there is no force acting on the rocket so all traces show 0. At sample number 625 (approx.) the rocket hits the ground and there is a considerable deacceleration period, possibly due to the casing flexing as it absorbs the force of impact, followed by some further rapid accel/de-accel periods as the rocket bounced into the flower bed. There is then  a long static period and then some further variations as I picked up the rocket.

 

As it is rather confusing having all three traces plotted together, I have just plotted the X trace on it's own and the process outlined above becomes much clearer.

 

image

 

I am not quite convinced that I fully understand what is happening as I would expect to see acceleration due to gravity in the period between launch and hitting the ground, but perhaps that is due to a flaw in my understanding of how gravity works or the sensor does not detect gravity when in free flight.

 

It would have been more intersting to have fitted this system to a real water rocket as this would have provided a much better 'upwards' acceleration effect, but overall, the results are good.

 

Dubbie

  • Sign in to reply

Top Comments

  • dougw
    dougw over 5 years ago in reply to dubbie +4
    Your confusion is normal because, despite their name, accelerometers don't measure the motion of acceleration. Usually, they measure the force required to prevent a known mass from moving in its housing…
  • DAB
    DAB over 5 years ago in reply to dubbie +4
    Yes, there are other forces involved that affect what the accelerometer records verses why you think it records. Think of it more as an impact sensor, not a relative sensor. Your brain is telling you that…
  • beacon_dave
    beacon_dave over 5 years ago +3
    "... or the sensor does not detect gravity when in free flight..." Or rather in free fall there is no measured displacement of the mass within the sensor itself ? I think some of the confusion might arise…
Parents
  • DAB
    DAB over 5 years ago

    You have keep the relationships in mind when dealing with acceleration.

    You have distance in each dimension, x,y,z.

    You have velocity in each dimension, Vx, Vy, Vz

    You have acceleration in each dimension Ax, Ay, Az.

     

    Acceleration is the rate at which the velocity changes. So if Ax = 0, that just means you are moving at a constant velocity.

    Velocity is the rate of change in distance. So if x1 = x2, then Vx = 0.

     

    When you go from X0 to X1 in a given time interval t, then you get Vx= X2-X1/t. When V goes from 0 to Vx, then Ax = Vx-0/t.

     

    DAB

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • dubbie
    dubbie over 5 years ago in reply to DAB

    DAB,

     

    I did physics at school and am OK with the concepts of acceleration, just about, but I'm still struggling to understand why the sensor doesn't show any deacceleration or acceleration when in flight. There is acceleration when I throw the rocket upwards but then the sensor doesn't shown anything until it hits the ground, but the rocket must be slowing down (deaccelerating until it reaches it peak (zero velocity) and then speeds up (accelerating due to gravity) as it starts to fall down. Is it the sensor or my brain that is not registering?

     

    Dubbie

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • beacon_dave
    beacon_dave over 5 years ago in reply to dubbie

    ...Is it the sensor or my brain that is not registering?...

     

    Think of how the sensor actually works. Basically a mass suspended inside the sensor housing by a spring type arrangement. In order to get a reading, the mass needs to be displaced in relation to the housing.

     

    In freefall however gravity is acting on the mass and the housing equally so there is no displacement taking place so a zero reading.

     

    The velocity of the mass and the velocity of the housing is the same until another force acts on the  housing. The sensor housing is attached to the rocket, so when the rocket hits the ground, the velocity of the housing almost instantly decreases to zero but the mass inside keeps going and you end up with a displacement which is measured. A change in velocity over time is what gives you the acceleration.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 5 years ago in reply to dubbie

    Yes, there are other forces involved that affect what the accelerometer records verses why you think it records.

    Think of it more as an impact sensor, not a relative sensor. Your brain is telling you that you should see readings of it going up and going down. If it was a powered vehicle, you might see some of that, but as a toss up and come down vehicle, all you should see is the initial push up and then the impact as it comes down.

     

    You have to look at the whole event through the view of the sensor. It is not an IMU, where it keeps track of position, velocity and acceleration. It is looking for specific events where the sensor is shaken or moved. While the vehicle is in motion, there are no sensor events. As the vehicle drifts upwards from your initial impulse, the sensor sees a very benign environment, which is why you data does not show much. The next big event the sensor sees is when you catch it or it hits the ground.

     

    I hope my little discussion here helps you better understand what you should expect to see.

     

    DAB

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • dubbie
    dubbie over 5 years ago in reply to dougw

    Douglas,

     

    This makes sense. I will have to update my brain in this area.

     

    Dubbie

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • dubbie
    dubbie over 5 years ago in reply to DAB

    DAB,

     

    This is very helpful. So I should probably have used the IMU data rather than the accelerometer data. I might have a go at this, sometime. At the moment my brain still hurts. Electronics seems so much easier than mechanical stuff.

     

    Dubbie

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 5 years ago in reply to dubbie

    Yes, when you look at things from a systems engineering point of view, you have to put everything into context and sometimes that means doing the math.

     

    Don't be discouraged, a lot of people overestimate what they will get from just an accelerometer.

    They are not as simple to use as some suggest.

     

    DAB

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
Comment
  • DAB
    DAB over 5 years ago in reply to dubbie

    Yes, when you look at things from a systems engineering point of view, you have to put everything into context and sometimes that means doing the math.

     

    Don't be discouraged, a lot of people overestimate what they will get from just an accelerometer.

    They are not as simple to use as some suggest.

     

    DAB

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
Children
  • dubbie
    dubbie over 5 years ago in reply to DAB

    Dab,

     

    I have come to the same conclusion, accelerometers might appear simple but they're not, nor do they always measure acceleration. Now I know. I wonder if I'll remember this? If I start warbling on about accelerometers again some time in the future then we'll all know I didn't remember!

     

    It might be interesting to put an accelerometer into a mobile robot - I haven't done that before.

     

    Dubbie

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube