Re: THE HORROR! THE HORROR!
 

This actually sounds EXACTLY like the situation that much of the Einstein report pointed out, as well as several other teams noted during the season. The most well known of these probably being 118. They functioned "completely normally" until the elims in CT. They also functioned "completely normally" until Einstein. Again, I reference the Einstein report. I highly suggest you go and read pages 12-13 [and really the rest of it, but specifically those pages if you don't want to learn from the whole thing].

And I appreciate that different people have different senses of humor, and that your graphics should have indicated your tone of sarcasm... but as the saying goes "TOO SOON...TOO SOON".

Re: THE HORROR! THE HORROR!
 

We had problems also with all robots shutting down and having to play a rematch.

Not sure why frc still uses wifi, should move to independent channel RF.

Re: THE HORROR! THE HORROR!
 

What?!?!

Re: THE HORROR! THE HORROR!
 

Our spinning was due to a failed battery. We had 2 separate instances in elims where batteries showed 13 volts on the charger and dropped to 6 volts within seconds during autonomous.

To the best of my knowledge we had no problems with the FMS in Hub City.

Re: THE HORROR! THE HORROR!
 

I thought bandwidth caps were in place...?

Re: THE HORROR! THE HORROR!
 

Out of curiosity did you ever figure out why the batteries behaved in such a strange way?

Re: THE HORROR! THE HORROR!
 

I can only tell you what the FTA mentioned to me in passing. I'll note that he didn't say and I didn't say that the cameras were causing issues for teams other than the ones running the cameras.

Re: THE HORROR! THE HORROR!
 

This is almost always a failed cell in the battery - or many failed cells.

We use the West Mountain battery tester to test our batteries. We found several this year that had normal voltages initially, checked good on our battery beak, but fell off after 5-10 minutes of testing fairly sharply.

Re: THE HORROR! THE HORROR!
 

On the one hand I want one of these. On the other hand I don't want to spend the money. Maybe I'll spend some time this offseason working out some software to use a Black Jaguar and some power resistors as a poor man's version of this.

Re: THE HORROR! THE HORROR!
 

Buzz's dance was not due to FMS. Due to possible programming issue plus the fact that we had to keep safety pins in to keep the feeder up ans therefore within starting envelope. We did not have enough pressure in the system after the last match and refs would not let us power up to recharge.

Re: THE HORROR! THE HORROR!
 

Hmm. You've got me curious. Can you give a general idea of what you have in mind? Is the purpose of the Jag to allow you to record data (via CAN) and shut off automatically so you don't have to babysit it?

Re: THE HORROR! THE HORROR!
 

Team RUSH 27 ran into Smart Dashboard issues at Northern Lights that spammed our cRIO and ran our processing to over 100%. Blame was originally on 7Mbps but after further investigation, NI advisors suggested it may be an issue with the smart dashboard itself. This caused major issues that hindered our robot for 3 matches. Any other issues similar?

Re: THE HORROR! THE HORROR!
 

They were simply failing batteries/cells that managed to emerge at the worst possible time. You can be sure we are taking measures to ensure that does not happen again.

Re: THE HORROR! THE HORROR!
 

Black Jags are serial controllable and have current control modes plus built voltage and current feedback. So all you would need for a battery tester is a serial port (or USB-Serial adapter), a serial to Jaguar adapter, a Black Jaguar that most every FRC team has 1 of, and a power resistor you can get at Mouser or your local electronics surplus store. Battery on the input side, power resistor on the output side, tell the Jag to dump X amps into the resistor, then record and plot your feedback. Primary difficulty is making the program to control the Jaguar. Either I'd need to figure out how to generate the FRC heartbeat, or you'd have to flash the Jag with custom firmware.

Re: THE HORROR! THE HORROR!
 

I remember one work session where a robot decided to "spin out" as soon as it was enabled. It did not respond to any control inputs. The cause turned out to be a disconnected gamepad. Pressing F1 on the Driver Station brought things back to normal.