2017-09-01 (F) Weekly Summary

There was a short break laser tag to distract with some easy and fun projects. It was a nice little break to play around with something that had a clear beginning, middle, and end. An electronic business card was made on thin printed circuit board. The front featured a spiral trace of copper which acted as an antenna which fed an ordinary LED, red in this case. When placed in the presense of an NFC field, like and Android phone, the LED would light up when the phone's antenna was transmitting.

NFC business card

Back to laser tag. A day was spent getting the programs into the Arduinos. It turned out that the most difficult part was finding a USB cable with data lines. Most of the USB cables in my stock were only capable of charging. Since this, many of the cables have been labeled.

Downloading to an Arduino

Getting a suitable OS onto the Raspberry Pi Zeros took more time than I would have liked. A whole day was spent to download the OS installer, copy it to microSD cards, run the installation routine, and copy the Python program to the computer. Fortunately, this could be done with Raspberry Pi Zeros not connected to the taggers since identical hardware meant that any Raspberry Pi Zero could be used for the installation.

Setting up Raspberry Pi Zeros

Two one-day projects were demonstrated this week. They aboth cenetered around 3D printing. The first, was a replacement foot for a stool that was printed a year before the blog so after a year of testing was done, the project was finally shown as successful.

Replacement stool foot

A second one-day project was brought out which capitalized on 3D printing. It allowed the range of an inexpensive IR remote control to be extended by focusing the beam through a lens. In the context of laser tag, this is important because a bare LED will only transmit usable light a certain distance, while a focused LED can transmit much further.

gRemLen parts





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