[techhelpbb]

Originally Posted by Al Skierkiewicz

You can continue to look at your own robot and spend your time chasing a power issue that you believe is the only problem that exists.

Again with the straw man arguments. I *never said it was the only problem* and everyone can go back and read my posts to prove it.

Your argument is the equivalent of you have it handled and there's nothing to see here. I think a national broadcast of that was something to see there.

No disrespect to you intended you are in point of fact overwhelmed. It was clearly apparent on the faces of each and every senior person on that field.

It was the direct result of doing everything that could be done to sandbox any argument that differs from your own. In point of fact you continue to do exactly that. It is literally unbelievable. From your own post:

We have a good and cost effective competition system that works. There are occasional issues that are as yet unexplained but the FIRST staff is working hard on solutions. They are as committed as I am to insure everyone has the ability to run when they are scheduled to play. Again, there is no indication these issues had anything related to power on the robot radio.

Except on the robots where it was a problem. Now clearly it's unlikely these were the robots during Einstein but your argument ignores your own points about the issues you know exist with the D-Link (namely that power connector). Worse it was you who argued about large relay contacts making noise and having variable resistance in the topic about reverse voltage protecting the Jaguars. The power connector on the D-Link is the functional equivalent of a giant normally closed spring tension relay contact.

I am convinced (more now that I observed from the scorer's table thousands of matches) that radio power is not the panacea that you believe it is. While I do not wish to stifle teams who are trying to expand our understanding I am firmly committed to preventing misleading lines of thought so that teams will keep their minds open to other possible failure modes.

Every troubleshooting process for TCP/IP (in fact most things) starts at the bottom. At the electronics and therefore power level. Each and every time you fail to start at the bottom and work your way up you undermine your troubleshooting process.

Again, even if a small number of teams are impacted by power quality issues who is anyone to claim a fair and level playing field when you deny them the opportunity to find their problems quickly?