I finished the HexShaftMonitor with a few finishing touches, uploaded my code to GitHub, and shot a demonstration video. The last bug was a double-tap on the reed switch every time the magnet passed, but I fixed that by turning it ninety-degrees.
Now that I had a drill shaft monitor, I was ready to start winding magnet coils. I whipped up a spindle model that used the same hex-shaped hole calculation as the HexShaftMonitor and printed two different sizes.
On one coil, I placed 250 turns and, on another, 100 rotations. I wanted to get a first-hand understanding of what difference this would make. There were a few issues with the winding process. The most frustrating part was keeping the wire in place on the spool.
After playing with the first two coils, I learned a few things and used that experience to revise the spindle model. First, I enlarged the hole so I wouldn't destroy anything when I placed it on a shaft and added a couple of little holes near the center where I could thread the start of the wire and keep it from slipping.
My magnet winding plans derailed because I had trouble finding time for physical projects. I started a new haptic compass project, which is actually a continuation of my first project on this blog. So far, I still haven't made one that works, but I've picked up a few things since then.
In this iteration, I will embrace electronics instead of ignoring them, and start with something that should already have all the hardware for a wearable version. I can miniaturize if the wearable is a success.
The rest of the summary posts 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 email@example.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.