Control System Layout Infographic

so like this?

1 Like

I’d add the resistors in, though the switch isn’t necessary.

The switch should have signal and ground connected, not 5v and ground.

1 Like

The wire to the DIO looks grey [signal] to me. As I think on it, I would likely also want to bring the ground (0V) wires from the PDP and the DIO together so the signal isn’t entirely free-floating relative to the RIO.

Added: Looking at the limit switch - IIRC, the DIO signal wires are normally pulled high through a resistor, so you use ground rather than 5V to the other side of the switch. Yes, in figure 16 of the User Manual.

Yes, you would generally put Ground (0v) on the common (as it is in the image) and then your Digital Input Signal line on either the NO or NC pin of the switch (where the red wire is currently running), relying on the pull-up resistors to keep the input from floating.

Also, amazing work on this Graphic! A few more revisions to the above noted concerns and I will certainly be looking into getting one or two large posters made for 3468’s shop and/or programming room!


also here’s a version optimized for 24 x 30 posters or larger sizes with the same aspect ratio: FRC Control System 30 x 24.pdf - Google Drive


I love this graphic, and I may be borrowing this for my team haha

Ordered two 32x40" posters from PosterBurner of the layout graphic for team 3468 to put up in the Programming and Build Rooms. Thank you so much for designing this! No Bananas readily available, so Spatula for Scale.


This diagram is excellent. I’m also looking for any similar block diagram that shows example FRC code (preferably Java) and what each section of the code does?

1 Like

There are no code snippets, and I am not the best at diagrams, but I did make a sort-of “flowchart” of data for the Command-Based Model. You’re welcome to take a look:

1 Like

Is this for the old command based or the 2020 command based?

This is phenomenal.

1 Like

It would be the old one. Don’t know how much of this is changed by the re-write.

Thanks @stefenacepcion. That is great. I’ve sent a link to my team. We may borrow the idea from @ExploitSage and make a poster for the shop.

1 Like

At this level of abstraction, the differences are minor. It’s been a while since I looked at the new API, but the big real difference I see is that in the new command based paradigm, the commands, subsystems, and OI all interact with the scheduler, and not with each other (much cleaner, and enabled the much more flexible composition of commands than before). If drawing the diagram for 2020, I would probably separate the Robot and the scheduler.


This is excellent, thank you.

3161 has some amazing brand identity standards (“brandards”).

1 Like

imma shamelessly plugging our Brandards here


I don’t exactly know how this fits into the control system infographic discussion, but holy ■■■■ that’s nice. That’s nicest looking branding document I’ve ever seen in FRC.


This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.