RAYPCB · ENGINEERING GUIDE
PCB Switch Footprint: Match Contacts, Actuation and Assembly Clearance
A PCB switch footprint must match both the electrical contact circuit and the physical part. Terminal count, body shape and nominal pitch do not fully describe it. A four-terminal tactile switch can have permanent internal connections that are easy to misunderstand, while an actuator that fits the board drawing may be inaccessible in the enclosure.
This page provides a contact-and-mechanical review worksheet. It records whether evidence has been reviewed for the actual part; it does not inspect a CAD footprint or simulate switching. For binary configuration settings and firmware bit order, use the separate DIP switch PCB guide.
Define the user action and electrical function
State what the switch does in the product: momentary input, maintained setting, reset, service action or switching a load. Define the expected resting state, actuation direction and what the application should recognize. A label such as push button leaves the circuit and behavior incomplete.
Identify the load or sensing circuit connected to the contacts. A low-level logic input and a power load can require different contact characteristics and ratings. Do not assume a mechanically suitable switch is electrically suitable for either task without reading the relevant specification.
Keep the mechanical action separate from the firmware interpretation. Pressed, contact closed, input low and command accepted are not always the same event. The controller's sampling and debounce behavior belongs in the design record alongside the physical switch.
Read the contact diagram before assigning pads
Obtain the exact part drawing and identify common terminals, throws and any terminals permanently connected internally. A package with four leads does not necessarily contain two independently controlled switches. Use a manufacturer circuit diagram rather than guessing from the body outline.
For the conceptual four-terminal example shown here, A 1 and A 2 are one permanently connected node, B1 and B2 are another, and actuation joins the two nodes. These labels illustrate a possible arrangement only; they are not a universal numbering scheme or a particular manufacturer's pinout.
Map the schematic symbol to the actual footprint pad numbers and verify the correspondence. If the library part was adapted from another variant, check the entire mapping again. A netlist can be internally consistent while still connecting the wrong physical terminals if the library definition is wrong.
| Review item | What to establish |
|---|---|
| Action | Momentary/maintained behavior, sensing or load task and resting state. |
| Circuit | Internal permanent connections and actual pad-to-symbol mapping. |
| Drawing | View direction, exact variant, land pattern and actuator geometry. |
| Process | Part-specific soldering, cleaning, support and installation sequence. |
| Evidence | Physical actuation, electrical response and application behavior tested separately. |
Switch footprint and contact review
Switch footprint and contact review
Use the current inputs and keep the assumptions
Load the example to learn the worksheet, then clear it before entering your project values. Blank fields are not silently converted to zero. Units and selected conventions belong to the result, so review them together with the numbers. Editing any input invalidates the previous result and disables its download until you calculate again. Edited example data remain labeled as an illustrative example.
This tool runs locally on the values you enter. It does not open a schematic, select approved components, measure signals or inspect a physical board. Keep the exact component documents and a record of measurements with the design. Downloading the text report does not send an enquiry or populate the Contact form. Attach it manually if it helps explain a specific engineering question; completing the worksheet is optional.
| Input | What to establish before using it |
|---|---|
| Review reference | Use a nonconfidential revision reference. |
| Contact circuit and permanent internal pin connections | Self-reported status; record evidence outside this worksheet. |
| Exact package drawing and recommended land pattern | Self-reported status; record evidence outside this worksheet. |
| Actuator direction, travel and enclosure tolerance | Self-reported status; record evidence outside this worksheet. |
| Soldering, washing and mechanical mounting conditions | Self-reported status; record evidence outside this worksheet. |
| Debounce, startup and load ratings reviewed | Self-reported status; record evidence outside this worksheet. |
Confirm the viewing direction and dimensions
Read whether the drawing shows a top, bottom or terminal view. Preserve the coordinate and orientation convention when building or checking the footprint. Mirroring a terminal arrangement can create a subtle error that is hard to see in a symmetrical-looking switch.
Use the actual recommended land pattern or hole arrangement for the selected part, including locating pegs and mechanical tabs where applicable. Do not treat body dimensions as pad dimensions. A family can contain several terminal, height or mounting variants with different requirements.
Check the actuator height and direction against the enclosure and surrounding components. Include tolerance and the available finger, tool or mechanism access. A switch that can be pressed on a bare board may have insufficient travel or excessive preload after assembly into the housing.
Use the review worksheet as an evidence register
For each row, select whether the item remains open, evidence has been recorded or it is not applicable with a reason. The tool summarizes those declared states. It does not turn a checked box into an inspected footprint or validate the reason for an exclusion.
Keep the actual drawing, schematic mapping, dimensional check and process information with the project revision. The worksheet is useful as a concise list of outstanding items, especially when engineering and assembly are reviewing different parts of the same switch implementation.
If a part changes, reopen the affected checks. Similar appearance or a shared family name is not enough to preserve terminal mapping, actuator force, height, contact behavior or process limits. An alternate needs an explicit review rather than inheriting the previous part's evidence automatically.
Plan for bounce, sampling and startup
Mechanical contact transitions can produce several electrical changes before reaching a stable state. Define how the application interprets those transitions and what latency is acceptable. There is no universal debounce delay appropriate to every switch, user action and circuit.
Review the electrical input circuit, thresholds and startup state. If the switch can be held during power-up or used for a service mode, define that behavior explicitly. A normal-operation event handler does not establish how reset or boot logic interprets the same connection.
Use the PCB controller state guide to connect switch input behavior to the product's actions. For configuration banks, return to the DIP-specific mapping page rather than adding bit-order logic to every general switch-footprint review.
Protect mechanical and process requirements during assembly
Read the selected part's soldering and cleaning restrictions and the conditions for any sealing claim. A switch described as sealed still has a defined specification and process scope. Do not assume every part in a visual family tolerates the same wash or reflow process.
Coordinate support and actuation forces with the board mounting. Repeated pressing can stress the PCB or solder joints if the surrounding mechanical design is inadequate. Define the intended support and operating action rather than expecting the footprint alone to carry every force.
If the switch is hand-installed or adjusted after other operations, include that sequence in the assembly instructions. Keep protective caps, films or temporary fixtures controlled so they do not become an undocumented step that changes product behavior.
Test the actual contact and product response
Use a suitable continuity or electrical check to establish the unactuated and actuated connection for the actual part. Then observe the intended application response. These checks answer different questions: correct contacts do not automatically mean correct firmware interpretation.
Check actuation in the final mechanical arrangement or a representative fixture. Record access, travel and unintended interference along with the electrical result. One successful press on an exposed PCB does not establish durability or enclosure compatibility.
For a failure, retain the part identity, board and firmware revision, physical action and observed signal. This makes it possible to distinguish a footprint error, process issue, mechanical obstruction or debounce problem without replacing components at random.
Release the switch as part of the complete product interface
Provide the exact switch part, footprint definition, schematic mapping, placement and mechanical requirements with the assembly package. Identify the operating and test scope, quantity and approved alternatives. Use the component reference guide to keep the switch identity consistent across files.
For RAYPCB review, highlight a concrete open question such as terminal mapping, actuator clearance or a part-specific process restriction. Include the appropriate drawing instead of only a photograph. The connector guide supports related mating-interface decisions elsewhere on the board.
A complete review connects the contact diagram, footprint, enclosure and application response. The worksheet helps keep those tasks visible, but actual inspection and testing remain tied to the chosen part and released product revision.
Make the setting reproducible for assembly and service
Give an installer-facing drawing and an engineering-facing mapping the same revision identity. The drawing should show the actual board orientation, position numbers and intended default state. The mapping should show contact closure, electrical input and software meaning. If a reserved combination changes product behavior, describe it explicitly in the appropriate service instructions.
Include a simple verification procedure in the assembly or functional-test scope. It should state which physical action is performed and which observable result is expected, without requiring the operator to infer bit order from source code. Keep mechanical access, process restrictions and electrical behavior as separate checks. A correctly decoded number does not establish that the switch can be operated in the enclosure or survives the selected soldering and cleaning process.
Standards, source context and limits
The referenced manufacturer documentation supports specific devices, interfaces or design methods. Apply the version and operating conditions appropriate to the actual part. A similar product name is not evidence that pin functions, voltage tolerance, startup behavior or package dimensions match. Worked examples illustrate reasoning and arithmetic; they are not released schematics or independent hardware test results.
For fabrication scope and the agreed construction requirements, see PCB manufacturing.
