2025-11-06 (Th) BonfireLaserTag New remote recording

 I wanted each tagger to have a unique name, but I never showed it on the screen. I added it to the welcome page and reloaded the screen whenever I changed the serial number through the USB port. For fun, I wrote a sequence that made the colored LEDs on the front show a rotating triangle that replaced the square or cross. This new function was a fun diversion, but it turned out to be practical, too. When I fired, all the LEDs illuminated in the team's color. Going from three to twelve was a more dramatic change, and fewer LEDs will be easier on the battery. I also thought the triangle looked cooler.

I recorded the button codes for the new 44-key remote and stored them in a spreadsheet. I colored the RGB button codes to keep things organized. I thought about the tricky coding required to recognize the color codes because they were not sequential, but then I figured there was no harm in programming the buttons out of order. I grouped everything by button layout, so now I can scan each key and assign the team based on where its button code is stored. Not all the colors will match perfectly, but I assigned them as closely as possible.

Remote codes and the order to import them

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
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.
2025-10-21