There were technical difficulties with this show. They were all on my side. Firstly, the microphone I was using was meant for phone calls, not high-fidelity recording and it kept rubbing against my hoodie. Second, the microphone which was supposed to be doing the actual recording was connected to a computer which shut off partway through the show, so I was left with poor audio ripped from the YouTube broadcast. Less than ideal. Here is our unedited video recording of episode 47 and here is the show page for the edited podcast with episode 047.
Brian - Left _____ Tim - Right
Titles are not my forté, so one of the Hackday editors gets credit for this title which is fitting and appropriate for the article. I found it as a month-old tip, but it was gold. I don't know a lot about CNC mills, but I saw the value in this immediately.
It was time to start on a new technical project, so I picked one which was just dying to get out. I have been infatuated with my mechanical keyboard, and I keep fantasizing about the expensive improvements and upgrades, but I want my desire to benefit other people. All the designs and ideas I had in mind were similar so it made sense to break them into modules so people could customize them to their own needs without having to buy parts they didn't want.
Hand sketches of ModuKey plans
The whole project was going to be built around the Teensy-LC because it could use the accessible Arduino IDE and it was easy to add a socket where it could be replaced in case of a failure or damage.
Each module of the project would communicate with the I2C protocol to allow for a lot of inputs, up to 128 switches. The base module would only include a socket for the Teensy and a clever arrangement of header pins along the sides which would facilitate communication.
Each module of the project would communicate with the I2C protocol to allow for a lot of inputs, up to 128 switches. The base module would only include a socket for the Teensy and a clever arrangement of header pins along the sides which would facilitate communication.
In the layout of the first board and the controller board, the pins along the side show a different pattern on each side. Only four connections are necessary between each board, but sixty-four are present so that the boards can be placed adjacent, but they don't have to be exactly aligned. The boards can be offset up to 1.6" (40.96mm) in either direction, and there will always be enough connections next to one another that long jumpers won't be necessary. This will require a video explanation in the future.
While writing for Hackaday I see stuff I wouldn't otherwise come across, and I get to share that. This tip was an old video with Terry Gilliam from Monty Python's Flying Circus fame, and he was talking about how he did the animations for the show. They were distinctive, and it turns out, relatively simple. They might have even been partially responsible for the animation in South Park.
The rest of the weekly summaries 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 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in 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.
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in 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.
Comments
Post a Comment