| Mode | Decoded signal |
|---|---|
| ITS, Blue team, Sentry mode | 00000111000000000000111100001000 |
| ITS, Red team, Sentry mode | 00000100000000000000111100001000 |
| ITS, Yellow team, Sentry mode | 00000101000000000000111100001000 |
| ITS, Green team, Sentry mode | 00000110000000000000111100001000 |
Not much interesting going on in Sentry mode.
| Mode | Decoded signal |
|---|---|
| ITS, Blue team, Bomb mode | 00000111000000010000111000011000 |
| 00000111000000100000111000011000 | |
| ITS, Red team, Bomb mode | 00000100000000110000111000011000 |
| ITS, Blue team, Bomb mode | 00000111000001000000111000011000 |
| 00000111000001010000111000011000 | |
| 00000111000001100000111000011000 | |
| 00000111000010000000111000011000 | |
| 00000111000010010000111000011000 | |
| 00000111000010100000111000011000 | |
| 00000111000010110000111000011000 | |
| 00000111000011000000111000011000 | |
| 00000111000011010000111000011000 | |
| 00000111000011100000111000011000 | |
| 00000111000011110000111000011000 | |
| 00000111000100000000111000011000 |
There's something interesting going on with Bomb mode that I don't understand.
Look closely. It's counting how many times it's been activated.
There's no way to see this on the tagger. It's a previously unused section of the shot signal. It doesn't reset when a different team activates it. What were they planning with this? I can't come up with anything...
| Mode | Decoded signal |
|---|---|
| ITS, Blue team, Medic mode | 000001110000000000000110000000100<SYNC>00001000000000000000100000000111 |
| 000001110000000000000110000000100<SYNC>00001000000000000000100000000111 | |
| ITS, Red team, Medic mode | 000001000000000000000110000000100<SYNC>00001000000000000000100000000100 |
Here's another interesting one. The part before the <SYNC> is the shot that activates the medic. The part after is the medic's response.
Look closely at it. Here, I'll even copy it around for you so you can see it easier...
| Red team, Laser Strike | 000001000000000000000110000000100 |
| ITS, Red team, Medic mode | 00001000000000000000100000000100 |
That's right. The medic's response is one bit shorter. I captured it a couple times to make sure.
I can tell that the last part of the medic response is the team that it's healing. The rest of it's a mystery, as it doesn't match the rest of the stuff I've seen.
I'm curious to poke around with some of those unused high-end bits, now. If setting the bit that the medic uses up there can let the tagger recognize a shorter packet, I wonder what else is hidden up there...
One idea I'd like to try with the I.T.S. is to create an Arduino translator board... so that the original board continues to function, but the translator receives LTTO signals and then sends the matching Light Strike code to the original board. This seems relatively straightforward, I'm just waiting for the prices in Seattle to come down so I don't have to pay $25 for one of these.
ReplyDeleteYou're going to be better off replacing the board in the ITS completely, really. It's actually what I'm planning on doing, before too long. Already have a good chunk of the parts picked out. The only part that's really going to be missed is the sounds.
DeleteAre you saying that there's signs of future expansion/new stuff that the Light Strike system planned for? Or is it just unused space that they didn't need for the current lineup?
ReplyDeleteIt looks to me like the protocol was capable of a lot that didn't get used. That high byte of the signal looks to be a combination team/type field. With the medic mode changing it so completely, and the bomb mode being the only thing to touch that second byte, there's either a lot of stuff that was planned and not used, or they didn't plan their protocol very well and just changed things as they came up, leading to a lot of "special case" programming. Either is possible, really. Without more stuff to capture signals from or the specs of the protocol, there's no way to tell.
Delete