Nobody's done a decent tutorial on how to use DIN terminal blocks.
https://www.phoenixcontact.com/onli...cks_P-15/4784f273-1e2b-4a34-8da7-709d3af232aa
But, that's the standard for doing control panels. The DIN blocks are essentially an electrical/electronic erector set. You can get terminals and "jumpers" that don't take up positions. You can get fuseholders etc.
General rules, help the process along. A few are:
1. NEMA enclosure with a 1/4" aluminum sub-panel in the bottom.
2. ALWAYS have a set of blocks for inputs/outputs.
3. Wiring duct tidies up the whole thing.
4. I've used 7/? (7 strand that made up 18 AWG) for wiring and was really happy. The wire will stay put.
It does add considerable expense to a design and probably not warranted for you.
So, for a major panel I designed, all the I/O came in on one large piece of conduit. It had to go though a firewall, so they were individually strain relieved there and then became class II PTFE wiring. Low level detectors had their own conduit,
This was a building install, but yea real world things mean something. The difficulty repairing a system became apparent when the powers that be failed to follow my advice. It never became manageable.
You can imagine when you have a whole bunch of inputs that are basically from building infrastructure and someone wants to out the control system is a rack including powering of an air velocity alarm. Eventually, I managed to get the velocity detector powered from a control cabinet on the wall which helped a lot. But why connect 10 or 12 building infrastructure devices via a big cable?
You couldn't even disconnect both controllers from each other to troubleshoot and they were on slides. Terminal strips made the interconnections. A real mess.
I digress, sorry.