Before, I started the calibration one second after pressing a button, but I changed it so it would calibrate one second after I released it to make sure I wasn't disturbing it. I don't know if this made any difference, but it was the pragmatic approach.
When the program took ten readings to assess the resting value of the gyroscope, I waited two milliseconds between each. 2mS seemed to lend a reasonable amount of accuracy, but I knew that wasn't close to the program's scan time. I replaced the hard-coded time with a variable that checked the last scan time and used that, which tended to be between ten and fifteen milliseconds. The drifting numbers during resting periods went way down, and I could watch the device sit at zero for a bit, whereas before it would promptly skew negatively. I also tested accuracy by spinning the IMU and watching the display climb from 0 to 360.
To further improve accuracy, I may use scan times recorded during rotation, where the delay is greater. I may adjust the correction factor based on a table with scan times from ten to thirty milliseconds.
The rest of the posts for this project have been arranged by date.
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
When the program took ten readings to assess the resting value of the gyroscope, I waited two milliseconds between each. 2mS seemed to lend a reasonable amount of accuracy, but I knew that wasn't close to the program's scan time. I replaced the hard-coded time with a variable that checked the last scan time and used that, which tended to be between ten and fifteen milliseconds. The drifting numbers during resting periods went way down, and I could watch the device sit at zero for a bit, whereas before it would promptly skew negatively. I also tested accuracy by spinning the IMU and watching the display climb from 0 to 360.
To further improve accuracy, I may use scan times recorded during rotation, where the delay is greater. I may adjust the correction factor based on a table with scan times from ten to thirty milliseconds.
Spinning Cardinal on a Lazy Susan
The rest of the posts for this project have been arranged by date.
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2020-06-28
2020-06-28
Comments
Post a Comment