2017-04-16 (Su) Pi0 Laser Tag PiTagErrUs

Python code which could talk to the serial port was started. This was supposed to be a simple task and it took very little time to get communication established. Communication wasn’t the problem, syntax and formatting were the issues. As advertised, it was simple to establish communication, so simple that rudimentary automation was possible with the first attempt. Since all the functions are controlled by a simple numeric string it was as easy to transmit bytes over IR as it was to blink some LEDs.

Getting two-way communication between Python and the Arduino firmware

Revisions were made to the firmware again since formatting had to be overhauled. In some places, it was better to use print() statements and in another place, it showed up better in Python if a write() statement was used. This type of formatting will take at least another day to correct. Once all the functions have been tested, it should be possible to rev the firmware from 0.0.X to 0.1.0. When a game of laser tag is successfully played it will be rev’d to 1.0.0.

Transmitting a signal by pressing the trigger button

Ideally, it would be possible to use the program on any machine running Python 3. The program is currently being written on a Raspberry Pi 0. If that program can be run on an Android device or a Windows device, with small modifications, future programmers may have a simple task when creating new games. Multiple device compatibilities has been on the scope of this project for awhile but the idea of using the exact same program hadn’t seemed possible.

Flashing lights by pressing the reload button


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-04-13 (Th)