Hi!
Pretty straight forward, I have a MPU6050 sensor who needs to measure the angle of a wheel turning around.. wondering where to position it to get the best results, at the edge of the wheel or close to the hub? does it makes any difference? considering moving very fast.. (maybe metals and noises have more effect close or far..)
following this tutorial:
and I also have a discussion on the "bigger" picture project of this here:
after i finish implementing and having good visuals will post all results there
Thanks a lot in advance!
The MPU6050 datasheet indicates it has the "ability to precisely and accurately track user motions" which has two components: 1. direction 2. rate but an angle has one component 1. direction... so a stationary angle seems outside the MPU capability unless you keep track of its last movement.
Maybe you can use this to help establish wheel angle in the "digital level" section...
Very interesting will read now.
But I don’t understand why I succeeded if that is the case. Connecting the mpu and rotating it in a circular motion while the face of it is upwards gave me a good indication of angle (I used the mpu6050tockn library as in the example I am following)
I do calculate the current position using the function: calcGyroOffsets(true)
And also using (int) (mpu6050.getAccAngleX()+360)%360
To get the angle and it seems to be working.. so maybe what I see in serial is not the angle?
If so what is it?
Still the question of where to locate the sensor is relevant..
Edit:
Read the article and some similar but I still don’t understand what you meant , can you please explain?
In the article there was also no mentions of where the sensor is best located to track the movement.. in the middle of the object? Close to the centre of the mass? In the margins of the shape?
That involves motion. If the motion is constant, you have a scalar (a speed or a direction). If the motion increases or decreases you have a vector (a change of speed or a speed and direction or a change in direction).
Can you show the output, and describe what you intend to see versus what you see?
I will be by the computer and sensor tomorrow or maybe later today. But what I see is actually fine. I see the angle that the sensor is at, I move it like an orbit around a centre point when the face always up (will upload a video also).
My main concern is where to put the sensor to get the most consistent results.. close to the microcontroller (esp32) or far? Or it doesn’t matter?
In the serial output it looks about the same, I can’t tell the difference, and I can’t move it in the speeds a bike wheel can. Maybe the best approach will be to do the 3d printed parts and the wires modular so I could try both and then see what works best.
Will add a detailed post with the serial output and me rotating in two videos, one time “smaller” circle and the second with a bigger circle of motion.
Thanks for your help so far!
intersting, that is what i was looking for!
thank you!
now trying to understand what will more suit a bike POV display
I believe finer is the way to go, but will be happy to hear what you think
not quite sure I got the phrase, or did you mean literally?
anyway it will be mounted very carefully and steady and be used in a performance show for a minute or two on a trainer.. so lets hope for the best in regards to safety and so.. and I will do my best to make sure it is safe and mounted good..
I don't mean to put it on the bike permanently and there are a lot of products that have the same concept even Monkeylectric once manufactured this product..
But thanks for the last tip.. will try putting it close to the margins of the wheel..
Hello guys, about mpu6050 sensor I suggest this link where you can find more informations about mpu6050 ... And this video show how to manipulate directly mps6050 registers to use it like a shock sensor with Arduino (It is in Italian language, use english subtitle) ...