2020-06-24 (W) InCompass

I created ten variables to store the history of the Z Gyro readings because I couldn't find anything named an array, and that's when I discovered Lists in Blockly. Lists are arrays by another name, at least in the way I am using them. Next, I made a function to scan the gyroscope, update the min and max variables, and record the history. After some errors, I found out that Blockly lists are 1-justified, which will take some getting used to.

When I had the scanning function defined, I constructed another to monitor the accelerometers. I had everything in place to expect spikes in the readings and use those periods of activity to update the headings, and the downtime would help calibrate and temper the gyroscope. After I looked at the values, I remembered that these accelerometers monitor the inclination, not acceleration. I will have to implement a calibration period where the errant gyroscope readings will be averaged out and subtracted from the running numbers.

Code screenshot

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

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-24