2014-11-22 (Sa) Arduino Laser Tag

The tape was peeled from the painted plastic and came away cleanly. There was concern the paint would not from a clean edge since the paint was allowed to dry with the tape in place. The paint was still tacky to the touch but was not affected by light contact.

Clear window in the paint job

A second screen arrived by mail. The header pins were removed by clipping the plastic between each one then prying the pin out while applying heat from a soldering iron. Wires from an ethernet cable were salvaged for the first eight wires which were soldered in in place of the header pins. A spare wire took the place of the ninth connection.

 Headerless screen and salvaged wires

Wires soldered in place

Double-sided foam tape was applied to the screen PCB and trimmed. A second layer of tape was applied to build up the thickness beyond the height of the actual screen. The screen was stuck to the painted plastic so the screen was right-side-up and lined up with the clear window.

 Tape applied to screen PCB

Two layers of tape
Screen behind window

Glue was applied to the face of an RJ11 socket which was placed behind the 1/2" (13mm) hole so the port was accessible through the hole. The glue seemed to dissolve the paint which had not fully dried. The painted side had been placed on the inside of the clear plastic to keep it from being scratched away. The tagger will still be prone to this cosmetic damage but the clear plastic would expose the electronics while the rest of the device has color PVC underneath.

 RJ11 socket glued from back

Everything held neatly in place

Paint distorted by glue

To do:
  • Draft schematics
  • Break down tasks further
  • Build vests
  • Build another tagger
  • Make instructions for all parts
 Journal Page 1

Journal Page

The rest of the posts for this project have been arranged by date.

A list showing of all the final posts of COMPLETED projects.

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, are 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 claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.

2014-11-20 (Th)