Programming hardware requires some setup to define what each pin does and what to call it. This is true for Arduino and Pi and probably all the clones. Since it had been awhile since I last programmed hardware for a Raspberry Pi it took a bit of time and some helpful tutorials to remember what needed to happen. This was also a time to brainstorm a bunch of the variables which would be used in the games.
Pseudo code for the basic game functions were written with indentation to give myself an idea of how the tagger would operate. The core operations of the game were sketched, like what to do with received data and how to check that it's valid. Data package structure was also sketched and includes a timestamp on each transmission so cheating would be more difficult. Simple laser tag guns can have their signals copied by a learning remote, commonly used for home entertainment systems.
The hardware setup and initial code was tested by controlling on-screen text and LEDs with buttons. Each of the buttons represents one of the inputs from the actual tagger such as the trigger or the reload button. Even more tutorials were necessary to recall the vital parts of interfacing with physical hardware.
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.
This blog, including pictures and text, is copyright to Brian McEvoy.
Animated scroll of beginning of code
Pseudo code for the basic game functions were written with indentation to give myself an idea of how the tagger would operate. The core operations of the game were sketched, like what to do with received data and how to check that it's valid. Data package structure was also sketched and includes a timestamp on each transmission so cheating would be more difficult. Simple laser tag guns can have their signals copied by a learning remote, commonly used for home entertainment systems.
Scrolling pseudo code
The hardware setup and initial code was tested by controlling on-screen text and LEDs with buttons. Each of the buttons represents one of the inputs from the actual tagger such as the trigger or the reload button. Even more tutorials were necessary to recall the vital parts of interfacing with physical hardware.
Testing code with physical hardware
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/
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.
2017-03-01 (W)
Comments
Post a Comment