Episode 034 covered the reactions Tim and I have experienced and what we've seen in the media about reactions to other biohackers. As a fringe group, we want to keep things looking optimistic but that isn't always the case as we discussed in episode 034.
Brian - Left _____ Tim - Right
Programming for the taggers was finally dragged out by finding the microSD card where the original code was written. This was plugged into a Raspberry Pi Zero alread mounted to a tagger. Some, but not all, of the the hardware functioned properly.
Functioning IR emitter LED
The card was tested in the second tagger and a different set of problems appeared. The taggers were not fully functional but the problems seem to be a matter of troubleshooting hardware rather than errors in the programming. For that reason, PiTagErrUs won't be shown on this blog until it is fully functional.
Parts from two taggers
A new project was started. OpenVectorKB is going to be a programmable off-hand keyboard designed for OpenSCAD. OpenSCAD uses vectors, three numbers in brackets, which require laborious typing. Sometimes, it is useful to tweak the numbers incrementally which involves replacing the number in question and refreshing the view. Instead, this functionality will be mapped to rotary encoders which can quickly increment or decrement any of the numbers in the vector.
Sketch of the device
A schematic and layout for the board were made. The schematic was a simple matter since a Teensy LC would act as the controller. Alternatively, the controller and supporting components could have been components on the board in order to save cost. Using the Teensy LC intact will take significant time off the development and since this was not intended to be a commercial product, the cost is less significant.
OpenVectorKB layout
An enclosure was crafted in OpenSCAD, of course. Round holes for the encoders and buttons were placed on the top while rectangular holes were placed on the sides for the controller and expansion port.
Rotating enclosure model
The rest of the weekly summaries have been arranged by date.
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