This year we decided to go sleek and simple and our Electronics Team drafted up a plexiglass box, laser cut it and fit all of our electronics in it. The idea is to easily take all the electronics off the robot quickly if something breaks/shorts (we had a fair share of that last year).
All the external motors connect to the box via Anderson Connectors, and the smaller components via PWM connectors.
Looks really good. Just make sure that the field personnel can easily see the indicator lights on your D-link when it’s in your robot. Also, why did you decide to go with a wood bottom rather than plexiglass or Lexan?
Is that Plexiglas (acrylic) or polycarbonate (Lexan/Makrolon)? You do not want to use acrylic on your robot.
While that may be a COTS fan intended for using with a computing device, it’s not part of a COTS computing device you are using on the robot. However, having some type of high powered air circulation device for use in the pits might be a good idea, especially during the playoffs.
Nice work! I like the lighting.
Make sure your radio isn’t buried too far down in the robot.
I think the fan would be legal if it was not a light up computer fan, but instead the similar one from FIRST Choice: http://firstchoicebyandymark.com/fc15-117
Yes, the FIRST Choice fan would be legal.
I will swap out the fans. We have a TON of the FIRST Choice fans. Thanks for the tip!
The D-Link is easily seen, there won’t be anything blocking it from view on the robot. I used wood on the bottom because it’s easier for mounting, so it won’t warp or crack with all the electronics on it and so we could save some money.
It’s ¼" acrylic.
You might be fine this year because of the lack of intentional robot contact, but I’d highly recommend using polycarbonate in the future. Anywhere from .09-.125" is fine for FRC non-structural use. The stuff pretty much just doesn’t shatter, and takes a lot more abuse than acrylic can. Oh, and did I mention it won’t shatter into those nice expensive electronics? 
On another note, that’s a pretty cool design. If you heed the warnings about placing your radio somewhere where it’s easy to see, you seem to have a great design on your hands for an electronics board. Good luck at competition!
Am I missing something with all the electrical layouts I’ve seen this year (including from my own team)?
The PDB is designed as a “fishbone” pattern, with the mains power coming in at one end, specialty stuff at the other end, and power splitting out to either side.
Why haven’t I seen a design that has talons (or other motor controllers) on both sides of the PDB? This design also has CAN crossing from (in the one shot that shows the whole board) from lower right to upper left, and PWMs (and RSL) crossing from upper right to lower left.
I’m also encouraged by the low number of Analog In and DIO ports I’ve seen populated. We’re using all four Analogs on the R-RIO, and at least six of the DIO’s for sensors, with backup plans for a few more if the camera code doesn’t mature in time. I’m convinced that this game (up to the regional championship level, at least, possibly as far as entree into Einstein) goes to tams that gain speed through automation and smart use of sensors. Whether we get there remains to be seen (only one of our programmers has contributed notably to our code base in previous years), but as a programming mentor this year, I’m spending most of my time making sure that we have the sensors we will need to have a fighting chance; our other programming mentor (who has been working programming our whole time as a team) is doing most of the training. Of course, both of us are giving lots of advice.