2018-09-14 (F) Weekly Summary


We decided to revisit a topic had hadn't touched since episode 013, Why do We Augment. This is the episode I ask people to start with when they ask about the show. It is a chance for Tim and me to sit down and just chat about why we love biohacking. We had a lot of fun recording this episode like we did back then.

Here is our unedited video recording (26:28) and here is the show page for the edited podcast with episode 054.
Brian - Left _____ Tim - Right

The single-button design was going to be ideal for keyring attachment due to its size but it was going to be cumbersome to use. A dual-button design was created which would have two buttons in addition to the encoder and the button built into the encoder.

Layout for 2-button EmerKeyB

Boards arrived for the EmerKeyBs and a single-button version was assembled. The mounting tabs had to be removed so it would fit. This weakened the attachment of the encoder to the board, but if the encoder was mounted to an enclosure, it should not be a problem since the stress would all fall on the encoder.

Top of assembled 1-button EmerKeyB

A two-button encoder board was assembled with two Cherry black switches. Black switches do not have a tactile feel or the loud click. There was no encoder on hand to connect to the board.

Top of partially assembled 2-button EmerKeyB

Cape Town, South Africa is enduring a drought, so some bright marketers asked the nation's top musicians to make two-minute versions of their songs so people could sing along in the shower while timing themselves.


To protect privacy or make some events difficult to record, like illusionist performances, lighting is being tested which made photography with smart phones come out poorly. Changing the lights faster than the eye can see, but enough that phone cameras pick up on them meant that events could be hidden from those cameras.





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.

Comments