How to Calibrate MPU6050 Simple/Easy (Part 2) 

Thank you, much love to you as well !

I am happy I helped your master's thesis. Yeah, I looked into that for a bit but will be a while before I actually do a more advanced calibration video. You are the first person to ask.

@@mmshilleh Oh. Thats ok. But thank you again for these videos. I would be happy to reffer to the video and know more anytime you upload. It is quite difficult to find the documentation for that (for me atleast :/).

Yes you do just need to change the orientation!

thanks. to be clear, when we orient x in the opposite direction of gravity, we are looking to get a value of '1', correct? The reason I ask, is that my application is an autonomous car that will use the gyro and x for direction and position.@@mmshilleh

You are the man Alex.

Hello Sohail, that is a much more detailed problem I cannot elaborate on in a comment. I plan to make a video in the future! Stay tuned and sub to the channel.

And lets assume you have these Z values: 2, 2 for +1G (offset 1), -1, -1 for -1G (offset 0) and 0, 0 (offset 0) for 0G. What would be the m and b?

To answer your question, x_sum is just the some of points you are measuring so we just increment by one.

Let me put it this way. If you measure 2 points, the first point for Z +1G and you get an offset of 1 the second for Z -1G you get an offset of 0 m = 1 (I just calculate the slope) and the y-intercept would be 0 hence an equation y = x for the bias This is known as two-point calibration. Ideally, you would want more. Hope that answers it

@@mmshilleh I don't fully understand the math behind (I like to understand things), but I already found the bug in my code (I'm playing with Arduino and C++, you with python). My problem with that algorithm is that you are using normalized values -1 to +1. My Arduino gets the values from MPU6050 in a range from -4096 to +4096 (for my configuration, the range depends on the resolution). The easiest way is to normalize the values and use your algorithm directly. The other way is to leave the value as it is and replace some +1 and -1 with +4096 and -4096 in the algorithm (only the +1/-1 that correspond to the X value). Btw for my Arduino and +1G the Z offset was not such big as yours, it was arround 450/4096.

@@DanyWay This is a two-point calibration method. The math is just trying to find the equation of a line. In this calibration, you would subject the accelerometer to two different known forces or accelerations, and record the output readings from the sensor for each input. These two points can be used to create a linear equation that maps the input values to the output readings, allowing the sensor to be accurately calibrated across its entire range of operations. Two-point calibration can be useful for an accelerometer because it allows for a more accurate and precise calibration across the full range of the sensor's operation. By measuring the sensor's response at two points, it is possible to account for any nonlinearity or error in the sensor's output readings, resulting in more accurate and reliable measurements. Additionally, by using two points, the calibration can be performed quickly and easily without the need for complex equipment or procedures.