[Michael Coleman]

Issue #1
The software templates are mandatory for FTC competitions. Robots that don't display the diagnostics may fail software inspection.

Issue #2
The Field Technical Advisor (FTA) at a competition is responsible for diagnosing problems when robots behave unexpectedly during competitions. Unexpected behavior can be caused by the robot or the Field Control System. The diagnostic information written to the NXT enables the FTA to quickly eliminate many of the common robot problems. Robots that don't display the diagnostics could be at a disadvantage when there is unexpected robot behavior during a match.

For example, a robot doesn't start Autonomous or doesn't move in the Tele-op portion of a match. The robot is still in the starting position near the field wall and the FTA can see the NXT display. [This is a very common situation.] If the robot is using the ROBOTC template the FTA can check for the following on the NXT display:

- Is the NXT enabled or disabled?
- Does the NXT's internal battery have sufficient voltage?
- Is the external battery pack powering the HiTechnic controllers turned on and have sufficient voltage?
- Is the NXT receiving Bluetooth packets?
- What is the name of the Tele-op program?

If the NXT doesn't display the expected diagnostic information, the door is open for the FTA to declare that the unexpected robot behavior is likely a robot failure since it isn't programmed using the mandatory template. Or worse, the robot should not be allowed to participate in a match since it shouldn't have passed software inspection.

Suggestion:
Teams could write their own information to the NXT display during software development and testing. Once the software is competition ready, it is in the team's best interest to use the mandatory template. The template minimizes the risk of failing software inspection and provides the FTA with valuable information when diagnosing unexpected robot behavior during a match.

Michael