G Force Calculation Optimisation with camera, equations & accelerometer (drop testing)

  • Context: Undergrad 
  • Thread starter Thread starter ao01
  • Start date Start date
Click For Summary

Discussion Overview

The discussion revolves around optimizing G-force calculations during drop testing of devices using an accelerometer and camera. Participants explore the accuracy of G-force measurements, the impact of drop height on results, and the potential for simulation to improve data analysis.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested
  • Experimental/applied

Main Points Raised

  • One participant notes inconsistencies in G-force values from the accelerometer, particularly at higher drop heights, suggesting potential issues with the device's accuracy.
  • Another participant recommends integrating acceleration over time to compare with expected velocity changes instead of dividing by collision time.
  • Questions are raised about the number of drops conducted from each height and the spread of values for fixed heights, indicating a need for more data to assess consistency.
  • Concerns are expressed regarding the temporal resolution of the accelerometer and whether it can accurately capture short-duration peaks during impacts.
  • One participant mentions using a specific program (pcc) for determining speed and acceleration, offering to share data files but expressing doubt about their comprehensibility.

Areas of Agreement / Disagreement

Participants do not reach a consensus on the accuracy of the accelerometer or the best method for calculating G-force. Multiple viewpoints regarding the reliability of measurements and the approach to data analysis remain unresolved.

Contextual Notes

Limitations include potential friction or binding in the testing setup, the need for more repeated trials to establish consistency, and uncertainties regarding the accelerometer's performance at high speeds.

Who May Find This Useful

This discussion may be of interest to those involved in experimental physics, engineering testing, and anyone seeking to improve data accuracy in impact testing scenarios.

ao01
Messages
4
Reaction score
0
TL;DR
G Force Calculation Optimisation with camera&equations&accelerometer
Hello, we do drop testing on devices and we have an accelerometer. Our accelerometer does not always give accurate G values, that is, as the altitude increases, the G force should increase, but there are moments when it decreases. We also place impact labels on the box we throw away, but they cannot always verify this situation.

I'm trying to get more accurate results on the computer with the help of a camera. Peak accelerations average 441 in all tests (427-528). I tried to find a better result by dividing these by the collision time, and indeed I got slightly better results, but I'm never sure.

Apart from this verification, I also want to reach this result by making calculations. I don't know how the G-Force value is calculated, it is calculated differently in many sources. Maybe I'm wrong because I examined the calculations according to the impact label table.

To give an example, we carry out the tests by raising the height by 10 centimeters:

385G in 30cm
40 542G
50 550G
60 552G
70 524??
80 425??

We reach the values and the impact label of the device turns red at 80 cm, but the G value is lower than other heights.

I also want to develop a simulation. With which application can I find an easier and faster result while developing this simulation? I'm waiting for your help.
 
Last edited by a moderator:
Physics news on Phys.org
Welcome to PF.

Can you upload some pictures of your test setup and sample preparation? (Use the "Attach files" link at the lower left of the Edit window.) It looks like you have some extra friction or binding in the higher drop tests...
 
Last edited:
  • Like
Likes   Reactions: Lnewqban
ao01 said:
I tried to find a better result by dividing these by the collision time,
You should rather intergrate the acceleration over time, and compare that to the expected velocity change.

ao01 said:
To give an example, we carry out the tests by raising the height by 10 centimeters:
Did you drop it from each height several times? What is the spread of values you get for a fixed height?

What is the temporal resolution of your accelerometer and data recording? Are you sure it can even capture short time peaks properly?
 
  • Like
Likes   Reactions: SammyS, Lnewqban and berkeman
berkeman said:
Welcome to PF.

Can you upload some pictures of your test setup and sample preparation? (Use the "Attach files" link at the lower left of the Edit window.) It looks like you have some extra friction or binding in the higher drop tests...
I'm sorry, I'm on leave for a while, but the system is like this. I am using pcc program with determine the speed and acceleration. If it might be useful to you, I can share the velocity and acceleration txt documents, but I don't think you can understand them alone.

1722252339286.png
1722237839007.png


A.T. said:
You should rather intergrate the acceleration over time, and compare that to the expected velocity change.


Did you drop it from each height several times? What is the spread of values you get for a fixed height?

What is the temporal resolution of your accelerometer and data recording? Are you sure it can even capture short time peaks properly?
We could only do it once because we did not have enough impact labels.
 
ao01 said:
We could only do it once because we did not have enough impact labels.
I'm asking about your accelerometer values. How consistent are they for the same drop height?
 
  • Like
Likes   Reactions: SammyS

Similar threads

  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 6 ·
Replies
6
Views
3K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 6 ·
Replies
6
Views
3K
  • · Replies 2 ·
Replies
2
Views
4K
  • · Replies 0 ·
Replies
0
Views
4K
  • · Replies 1 ·
Replies
1
Views
5K
  • · Replies 0 ·
Replies
0
Views
3K
  • · Replies 3 ·
Replies
3
Views
27K
  • · Replies 8 ·
Replies
8
Views
21K