2020-08-13 (Th) InCompass

The device stopped working again, and I had to reload the code to resume. I was worried that this could lead to unreliable software, so it necessitates more testing. When I connected it to a computer, I tried to use it without the 5V supply, but the data lines may have pull-up resistors because it didn't work. I wanted to do this because power was coming from the USB and a battery.

I commented out the code that printed the battery voltage each iteration. The next step was changing the functions to only print the heading if there was a change. If nothing moved, the system didn't spend resources and clock cycles on data. It also saved on my computer's memory while connected and looked less frantic on the screen.

When the code started, there was a check to see if the IMU was functioning, and if it failed, the program would not execute. I suspected this might be a cause for the cease-function. Nothing worked after that because the check also initiated the sensor. I modified it so that it would start, but not hang on a failed sensor.
Responsive code

GitHub repo for Cardinal, aka InCompass

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.