2021-04-29 (Th) Wearable Macro Keyboard BackOfTheHand BotH Soothing Inputs

I had trouble reading high and low presses because I got a lot of noise and false positives. The problem was similar to bouncing switches, where a single activation triggers a few times. I went back to printing percentages to get an idea of what the computer saw, and it looked like one of the inputs would hover around the value for a light tap. That erratic behavior would flip above and below the specific number and repeatedly activate the code. I added a stipulation that the keyboard wouldn't issue any new commands from a finger until the readings dropped below a low percentage. The erratic behavior stopped and was almost sluggish by requiring this settling, but responsive finger rods didn't have any trouble.
Reset threshold

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.