I started programming the taggers as standalone units. This method allows me to identify which functions will be necessary when we add vests. I will initially make all the changes via USB, but in the future, they will be made over Bluetooth from the Raspberry Pi in the vest. My short-term goal was to create a playable tagger that works without the vests. The guns will not have any speakers.
I added code to change the serial number and damage values and print them to the screen. After that, I wrote a Help Menu function that described what each letter would change, and it showed the current serial, team, and damage values. The last thing I did was write those values to non-volatile EEPROM memory and reload them at restart. I tested by pulling power and seeing the exact numbers on the screen.
The signal each tagger will transmit is a three-byte train with its serial number, team, and damage. There was a way to do this with bit shifting, but I programmed the unsigned long variable by multiplying it by hex numbers, such as 0x10000. I used a Flipper to record and retransmit the signal, allowing me to view it through the serial monitor.
I created a software filter to ignore all the noise coming from my television remote and camera's LiDAR. My protocol was so simple that I only needed a few bytes, and most signals were lengthy so that I could ignore the big ones. I parsed the simple incoming messages into team, serial number, and damage.
When I run laser tag sessions, I want to assign teams without connecting the taggers to a computer for changes, so I pulled a generic remote control from my stock and mapped the button locations. I printed a sticker that fit over the remote with new labels for the button functions, then I recorded each button's code into the Arduino sketch.
This week, we discussed The Color Out of Space, a Nicolas Cage film inspired by an H.P. Lovecraft story, along with Dan Henk, who introduced his book Down Highways in the Dark... by Demons Driven. Although the movie wasn't my favorite, I appreciated the visual effects, acting, and production quality.
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
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 on 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.
 |
| Changing colors by changing teams |
I added code to change the serial number and damage values and print them to the screen. After that, I wrote a Help Menu function that described what each letter would change, and it showed the current serial, team, and damage values. The last thing I did was write those values to non-volatile EEPROM memory and reload them at restart. I tested by pulling power and seeing the exact numbers on the screen.
 |
| Help menu and setting after rebooting |
The signal each tagger will transmit is a three-byte train with its serial number, team, and damage. There was a way to do this with bit shifting, but I programmed the unsigned long variable by multiplying it by hex numbers, such as 0x10000. I used a Flipper to record and retransmit the signal, allowing me to view it through the serial monitor.
 |
| Flipper reflects the tagger's signal |
I created a software filter to ignore all the noise coming from my television remote and camera's LiDAR. My protocol was so simple that I only needed a few bytes, and most signals were lengthy so that I could ignore the big ones. I parsed the simple incoming messages into team, serial number, and damage.
 |
| The microcontroller can recognize team, serial number, and damage |
When I run laser tag sessions, I want to assign teams without connecting the taggers to a computer for changes, so I pulled a generic remote control from my stock and mapped the button locations. I printed a sticker that fit over the remote with new labels for the button functions, then I recorded each button's code into the Arduino sketch.
 |
| Custom sticker on a cheap remote |
This week, we discussed The Color Out of Space, a Nicolas Cage film inspired by an H.P. Lovecraft story, along with Dan Henk, who introduced his book Down Highways in the Dark... by Demons Driven. Although the movie wasn't my favorite, I appreciated the visual effects, acting, and production quality.
Critical Affection:The Color Out of Space (1:06)
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
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 on 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
Post a Comment