I added a feature to the calibration routine that let me cancel it with a serial command. I also refined the speed calibration calculations, which I'd been repeating in the calibration function instead of leaning on the dedication routine.
I continued coding the calibration routine, but the first run accelerated a few times and then ran continuously at one speed without advancing. I ran the motor for 1,900 cycles to get a thorough picture. My min and max were typically off by 10,000 microseconds. I told the program to allow these tolerances, then ran the calibration thirteen times and recorded the results. The acceleration between speeds was smooth, but everything over 90% was useless.
Calibration tables
I added a delay between speeds, so I couldn't accidentally accept a trial where ten rotations occurred during the early acceleration phase. The routine took noticeably longer, and the changes in motor sounds were audible as steps rather than a single smooth ramp. Over 90% was still unusable, but that is a failure of the sensing equipment. I ran a dozen more tests, and the results looked similar but should be more reliable.
After adding a delay
The rest of the posts for this project have been arranged by date.
First time here?
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
Completed projects from year 8
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.
2022-11-18
I continued coding the calibration routine, but the first run accelerated a few times and then ran continuously at one speed without advancing. I ran the motor for 1,900 cycles to get a thorough picture. My min and max were typically off by 10,000 microseconds. I told the program to allow these tolerances, then ran the calibration thirteen times and recorded the results. The acceleration between speeds was smooth, but everything over 90% was useless.
I added a delay between speeds, so I couldn't accidentally accept a trial where ten rotations occurred during the early acceleration phase. The routine took noticeably longer, and the changes in motor sounds were audible as steps rather than a single smooth ramp. Over 90% was still unusable, but that is a failure of the sensing equipment. I ran a dozen more tests, and the results looked similar but should be more reliable.
The rest of the posts for this project have been arranged by date.
First time here?
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
Completed projects from year 8
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.
2022-11-18
Comments
Post a Comment