2017-04-01 (Sa) Pi0 Laser Tag PiTagErrUs

Transmitting data over infrared has proven to be the hardest part of this project. Fortunately, it has been done before with more conventional means before.

It was speculated before that it may be necessary to offload some, or all, of the components to an Arduino. Arduinos are better at handling I/O but it would have been elegant to keep everything on the Raspberry Pi.

And Arduino Micro (Leonardo) will be used due to the ease of serial communication on this board. This change in hardware opens up the possibility to connect other devices besides the Raspberry Pi. It would be possible to write an Android-compatible program and run the tagger from a mobile phone. In fact, this ability would make a touch-screen easy to implement.

The premise of the Arduino programming with be that a serial interface over USB will do nothing more than accept incoming data and appropriately manipulate the I/O. So, someone with a Raspberry Pi could receive data from the Arduino that the trigger has been pulled then it would send the serial signal to
shoot with a particular user ID
activate the laser for a quarter of a second
activate the report emulator for a quarter of a second
and keep the flashlight off
Anyone with an Android could send those same signals. Or a Windows tablet and maybe iOS devices.

While this costs a little more it does add to the versatility and Ken Shirriff has written a very good library for combining Arduino and infrared. It’s what I used when I wrote a laser tag game for Arduino years ago.

Inputs and outputs were decided for the Arduino and two were given header pins and affixed to breadboards. The hardware was attached to the breadboard. A string of eight NeoPixels was added but those will not be implemented anytime soon.

Arduinos on breadboards and pin layout


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

First time here?

Completed projects from year 1 
Completed projects from year 2
Completed projects from year 3

Disclaimer for http://24hourengineer.blogspot.com/ and 24hourengineer.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, 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 property or assets based on a post.
This blog, including pictures and text, is copyright to Brian McEvoy.

2017-03-30 (Th)