Avionics/Documentation

PC/104

Last updated Nov 10, 2026Avionics

PC/104

PC/104 is a board interconnect standard for small, stackable embedded boards. Instead of plucking cards into a backplane like a desktop computer, boards connect to each other directly into the board below. This is highly space efficient, allowing avionics to compact into a smaller, box-like form. It also exposes more edges, allowing for more inter-avionics connections to be made. The result is a self-supporting stack held together by standoffs at four corners.

The name PC/104 is self-explanatory. PC as it began as the IBM PC/AT ISA bus, and “104” referring to the 104 pins of the original bus connectors. For less complex systems with less transmitted data, we refer to as PC/104 styled. The same interconnecting technology is used, but less pins are utilized. This offers the same spatial and structural benefits as PC/104, at a fraction of the complexity.

Mechanical Standards

  • Four-sided PCB of mostly square shape (No long rectangles)
    • Side length ratio: near 1:1
  • Connectors in between boards providing a vertical connection
    • Header are simplest, however there are designs meant specifically for PC/104. See Figure 1.
  • Mounting holes
    • 4 corner holes, M3
  • Board to board pitch (distance between boards)
    • Generally 15.24mm. We allow slightly larger or smaller packing to fit fans, tall components, etc. in order to maximize spatial efficiency
  • Top/Bottom components
    • Both top and bottom assembled components may be used, but keep in mind that PC/104 styled interconnects are directional.
    • Component heights are generally pretty restrictive (<11mm top, <2.5mm bottom), but in our case we have leeway. Aim for <15mm both top and bottom, prioritizing ease of assembly by JLCPCB/other PCB providers.
  • PCB thickness
    • Generally 1.6mm. A range of 1mm-1.8mm should be safe for our purposes.

Figure 1: Headers being used as interconnects between two layers.

PC104 Standard Products

PC/104 itself is a rather rigid standard. There are significant benefits to follow it (namely requirement simplicity) in creating larger systems. For LRI avionics, we aim to dumb it down to a structure we can customize per mission, and reap the spatial and structural benefits. We use the form factor, not the bus. Normally, a regular avionics board can take up over 10cm of airframe length. Using a PC/104 form factor, avionics can separate boards and save around 8cm of airframe length, and create vertical connection points for screw-in components such as pryo wires and differential connections to servo actuation boards and radio boards. An example of integration is shown below in Figure 2.

Figure 2: Washington University (SARP)’s liquid rocket avionics board, using a PC/104 style stack-up.

The flight computer is the brain of SARP's liquid rocket. It is composed of  3 custom PCBs designed to control solenoids and actuators, read pressure  and temperature sensors, store data, communicate wi

Standard integration of PC/104 may use lower-speed communication protocols such as I2C and UART. SPI is a method that is preferred for its speed, but is highly dependent on microcontroller capability and trace lengths. As PC/104’s form factor inherently increases trace length and introduces a mode of data interference, designing a board correctly such that impedance and current interference sources are within the tolerable levels for desired communication speed is paramount. Engineers may use online impedance and trace width calculators in addition to deploying common practices in handling such weaknesses to counteract instability. For more information on interference, see “Interference and Impedance”.

Systems Requirements:

Tier 1: Does it fit, and does it survive flight?

If any of these fail, nothing else matters.

1. Software complexity. Is this a testing board that can easily fit all its components, or a complex flight computer with attitude and fluid-systems control? This decides whether a stack is justified at all.

2. Form factor and board area. Factor in PC/104’s form factor. Consider the sizes of all components and determine a minimum surface area. Define the maximum surface area from the rocket housing requirements. Leave margins for wiring on the bottom and sides. Define board clearance from component heights and any cooling hardware.

3. Central threaded rod. Many rockets use a central threaded rod to hold components in. Can the stack-up be integrated on the sides? Could a hole be put through the stack-up to accommodate the rod? Is there a section of the rocket with no threaded rod in the center?

4. High-g loads. High-g acceleration dramatically increases the specific force on components. Derive the design load from the actual motor thrust curve and recovery deployment profile, then apply a safety factor, instead of assuming a fixed value such as 20 g. Recovery deployment shock can exceed boost acceleration.

5. Vibration and sensor aliasing. Vibration is a major problem in rocket flight. Keep sensor sampling rates and control-loop rates away from the vehicle’s structural vibration modes; otherwise vibration aliases into the IMU data and corrupts the dynamical model. Mitigate with anti-aliasing filtering and, where needed, vibration isolation of the IMU. Structural failure of the stack itself is far less likely, given the stiffness of PC/104 setups.

Tier 2: Mission and safety assurance

These determine whether a fault ends the mission.

6. No single fault disables the stack. If a board fails, it should not affect the other boards, leaving a backup processor to take over so flight operations continue after a single-point failure. The shared stack connector and bus are themselves a single point of failure: keep critical functions such as recovery deployment on hardware that is electrically independent of the bus.

7. Power budget. High-consumption boards matter, but actuation and high-gain radios can take up a large share of the budget. Allocate a set power budget per board, per flight phase, including the longest expected pad hold.

8. Power states and hung-board recovery. Define which boards are always on, how they are turned on and off, which are switchable, and how the main computer recovers from a hung board (power cycling, watchdog).

9. Sensor placement. Some sensors output data that depends on their physical location. An IMU placed far from the center cannot be treated as if it were at the center of rotation; computing attitude quaternions under that faulty assumption gives highly inaccurate results and can jeopardize the mission. Work closely with the software team so the dynamical model accounts for sensor offsets.

10. Misassembly-proof configuration. Board configuration across multiple boards is a common failure point. Design pins, connectors, and keying so that a reasonable engineer cannot misassemble the stack.

Tier 3: Interfaces and integrity

These define how the boards work together.

11. Board interconnections. Define and optimize the number of board-to-board connections. Power boards and high-speed links often need several power and ground pins, and fast digital lines such as high-frequency chip selects need adjacent ground pins. Frequency and robustness requirements drive the pin allocation.

12. EMI/EMC and grounding. Reduce the chance of failure from magnetic fields generated by high-current lines. Keep input power traces away from magnetometers and high-speed data lines, and consider whether an extra ground plane between boards is necessary.

13. Co-designed mounting interfaces. Design mounting interfaces alongside the board, relating dimensions, functionality, and interfaces so each board attaches to and works with its neighboring components.

Tier 4: Vehicle-level budgets and environment

These matter, but they are usually tradeable within margins.

14. Mass budget. Each extra board adds mass, and complex stack-ups add up quickly. Connectors, spacing rods, and standoffs also add significant weight.

15. Center of gravity. Keep the stack-up as centered as possible so its CG sits near the vehicle centerline wherever the stack is placed, and account for it in the vehicle’s stability margin.

16. Thermal management. The launch environment can heat the rocket past 50 °C, compromising sensitive components such as SD cards and high-power parts. Make conduction to the airframe (through standoffs, rods, or a thermal plate) the primary heat path, with heatsinks on hot parts. Fans do little in a sealed avionics bay, because they only recirculate hot air.

17. Humidity and contamination. Define a method to limit dust, rain, and other contaminants (for example conformal coating with masked connector contacts) so boards and connections accumulate less damage.

Tier 5: Operability and convenience

These affect turnaround and debugging, not flight success.

18. Side access. All inputs should ideally be on the side. Unscrewing boards to access panels is inefficient and complicated.

19. Cable routing out of the stack. Spread external cabling evenly along a short strip of the margins around the stack-up, leaving space for airflow and for other subsystems’ cables.

20. Debug access. The stack-up should be easy to debug, with its ports readily accessible while assembled.

Design and Integration General Procedures

  1. Consider the board requirements. Board requirements should be mostly complete before making lower-level considerations. If needed, add more low-level specific requirements based on boards’ needs.
  2. Create 4 holes as components within each board schematic. Use M3 holes, without grounding. Consider if fans need to be installed in-between boards, and allocate additional holes if necessary to screw a fan in.
  3. Design the board around PC/104, not PC/104 around the board. Start by first allocating holes and rough component placement, before defining the size of the board.
  4. Holes are part of component placement, place and roughly wire all components as in the schematic, ensuring that the holes are near the corners of the rectangular board. Allocate 2-3mm of clearance around each hole for spacing rods to occupy.
  5. Define the final shape of the PCB based on component placement. Double-check that hole placement is correct and follows PC/104 form factor standards, before fabrication.

Summary

In general, PC/104 wins when modular, parallel development is a priority. For large teams, working on a single board can lead to mass confusion and integration disputes. Splitting boards offers a clean and relatively simple way to distribute work and isolate failures. It also allows the computer to offload work and computation, increasing computational speed often by double or triple. In complex environments with many tasks, the PC/104 form factor is the design of choice to minimize confusion and speed up workflow.