[EricH]

Originally Posted by Nate Laverdure

See T22.E.i and ii

Just so we're all aware of the full relevant text of the referenced rule...

T22
The only equipment, provided it does not jam or interfere with the remote sensing capabilities of another Team, including vision systems, acoustic range finders, sonars, infrared proximity detectors, etc. (e.g. including imagery that, to a reasonably astute observer, mimics the VISION TARGET), that may be brought in to the ALLIANCE STATION are as follows:

A. the OPERATOR CONSOLE,
B. non-powered signaling devices,

E. devices used solely for the purpose of planning or tracking strategy provided they meet all of the following conditions:
i. do not connect or attach to the OPERATOR CONSOLE
ii. do not connect or attach to the FIELD or ARENA
iii. do not connect or attach to another ALLIANCE member
iv. do not communicate with anything or anyone outside of the ARENA.

Mr. Lavedure is using the April Tag as a device "used solely for the purpose of planning or tracking strategy". However, doing so completely misrepresents its real use: as a sensor target. It's not for tracking strategy at all!

As a sensor target, it should be classed as a non-powered signaling device (it is signaling a location, to any robot that happens to see it and be able to read it), and thus be subject to T22-B, rather than T22-E. T22-B passes it in as equipment that may be brought into the Driver's Station.

As it is attached to the Operator Console, and could theoretically be small enough to be the back pattern of the laptop, it could also theoretically be counted as part of the Operator Console... but that's unnecessary as it's already in.

This assumes that no April Tags exist in the field itself; should there be one or more, T22 takes over and kicks it out under mimicking part of the field.