Coder Legion - Recent posts tagged pcb

A PCB Bring-Up Log Is a Design Artifact

Tue, 15 Sep 2026 05:41:53 +0000

The first powered board produces more than a pass or fail result. It produces evidence about the design assumptions: which rail starts first, what the connector actually does, how hot the regulator becomes, and what the firmware sees during a fault.

If those observations stay in a chat thread, the next revision has to rediscover them. A structured bring-up log turns them into design knowledge.

Start with a state-based test plan

List the states before touching the probe: unpowered, USB attached, battery attached, processor held in reset, radio transmitting, maximum load, and brownout recovery. For each state, record the expected voltage, current, status pins, and safe limits.

The power path should be reviewed with the power-management component families, while high-current or high-frequency routes should be checked against the intended stack-up and PCB manufacturing process.

Record observations, not conclusions

Write down the measurement point, instrument, probe connection, bandwidth limit, input voltage, load, firmware revision, and board identifier. “Rail noisy” is a conclusion. “180 mV peak-to-peak at the sensor supply pin during a 2.4 GHz transmit burst, 4.2 V input, board B03” is evidence.

Do the same for component temperature and current. If a resistor or protection device is close to its limit, use a derating check and attach the actual ambient and case-temperature assumptions. If a divider or sense network is involved, verify the expected value with the voltage-divider calculation.

Capture the first failure mode

The most useful test is often the one that makes the board fail safely. Disconnect a sensor, remove the cable, reduce the supply, and trigger the maximum load step. Record whether the firmware reports an error, resets, or continues with stale data.

For a component substitution or a second source, write the exact part number and package. A catalog entry such as the M24C04-WBN6 product record illustrates why the ordering code matters; a generic “I2C EEPROM” label is not enough to identify the built device.

Convert the log into the next revision

Every observation should end with one of three outcomes: accepted as expected, assigned for correction, or accepted with a documented limitation. Link the issue to a schematic net, layout area, firmware module, or BOM line. When a change is made, repeat the original measurement so the result is comparable.

For interface and digital timing issues, review the relevant logic controller and buffer families. For RF boards, also record the antenna state, enclosure, cable routing, and measurement reference plane; otherwise a later “fix” may only move the test setup.

A bring-up log is not paperwork after the engineering work. It is part of the engineering work. It preserves the assumptions that the next board, assembler, and service technician need in order to reproduce the result.

References

The Five-Minute Pre-Release Check for a New PCB

Mon, 31 Aug 2026 05:44:35 +0000

The final hour before releasing a PCB is rarely the right time to discover that a connector footprint has the wrong pin numbering or that a high-speed net has no defined return path. A short, repeatable review catches many expensive mistakes before fabrication. It does not replace a full design review; it makes the obvious checks hard to skip.

1. Compare the schematic with the physical intent

Open the schematic and PCB side by side. Confirm connector orientation, pin-one markers, mounting holes, fuse polarity, LED direction, test-point labels, and the location of serviceable parts. A design can be electrically connected and still be impossible to assemble or plug into the surrounding system.

Check every power entry for protection, current rating, and a defined return path. Verify that the expected current does not pass through a narrow neck, thermal relief, or an accidental split in the reference plane.

2. Review footprints before reviewing aesthetics

For each nontrivial part, check pad numbering against the manufacturer drawing. Pay special attention to mirrored connectors, bottom-view package drawings, exposed pads, diode polarity, and mechanical keep-outs. Compare the 3D model with the actual mating component when the connector or enclosure fit matters.

For tiny marked passives found during prototype inspection, the SMD resistor code calculator is a convenient cross-check. It should support the released BOM, not replace it. The BOM and placement file remain the source of truth for production.

3. Check the power and thermal paths

List every rail and record its maximum current, expected ripple, protection device, regulator, and load. Then inspect the physical path from source to load. The shortest schematic path is not always the lowest-impedance PCB path.

For MOSFETs, regulators, drivers, and power resistors, verify copper area, thermal vias, exposed-pad land pattern, and nearby heat-sensitive parts. If the design uses a switching converter, inspect the high di/dt loop and keep the feedback network away from the switch node.

The MOSFET reference at MOZ Electronics can help structure the device review, while the component-sourcing workflow at MOZPCB is useful for checking approved alternates, lifecycle risk, and traceability before the release package is locked.

4. Make the stackup and constraints explicit

Do not release a high-speed board with “controlled impedance” as an informal note. Record the layer stackup, dielectric thickness, copper weight, trace geometry, tolerance, and the nets that require a target impedance. Confirm that the selected fabricator can build that stackup consistently.

MOZPCB’s controlled-impedance PCB guidance is a useful reference for connecting trace width to the complete stackup and return-path decision. Run the final design-rule and impedance checks against the manufacturing stackup, not a generic calculator preset.

5. Review the assembly and test package

The release is incomplete if it contains only Gerbers. Include the fabrication drawing, assembly drawing, centroid or pick-and-place data, BOM with manufacturer part numbers, polarity information, stencil notes, panelization requirements, and first-article acceptance criteria.

Check that no component is accidentally marked DNP, no alternate has been omitted from the AVL, and no test point is hidden under a shield or bracket. MOZPCB’s PCB assembly guidance helps connect those documents to stencil, reflow, AOI, X-ray, and inspection considerations.

The five-minute release sequence

Compare connectors, pin one, mounting, and keep-outs.
Review footprints for polarity, mirrors, exposed pads, and mechanical fit.
Trace every power rail and inspect its thermal path.
Confirm stackup, return paths, impedance rules, and design-rule results.
Open the exported manufacturing package and verify that the files match the released revision.

Finally, record the reviewer, date, revision, and unresolved assumptions. Octatronics’ technical resources can help provide application context when a release decision depends on power, communications, or industrial operating conditions.

The check is intentionally short. Its value comes from doing it every time, before the board becomes a purchase order.

References

SMD resistor code calculator
MOSFET reference at MOZ Electronics
MOZPCB component-sourcing workflow
MOZPCB controlled-impedance PCB guidance
MOZPCB PCB assembly guidance
Octatronics technical resources

The BOM Is a Technical Document, Not Just a Shopping List

Fri, 28 Aug 2026 09:35:53 +0000

When a prototype works, teams often freeze the BOM too early. The electrical value may be correct, but the package, temperature grade, lifecycle status, approved vendor, moisture sensitivity, and replacement rules are still undefined. That is where many production delays begin.

What a production-ready line should contain
For each critical component, record the manufacturer part number, package and footprint, electrical limits, temperature grade, compliance requirements, lifecycle status, approved sources, and acceptable alternates. For capacitors and inductors, include voltage, ripple current, bias or saturation behavior, and tolerance. For semiconductors, add gate charge, thermal resistance, switching limits, and any firmware or configuration dependency.

The word “equivalent” is not enough. A substitute can match the pinout and still have a different RDS(on), gate threshold, startup time, leakage current, thermal path, or protection behavior. Qualification should compare footprint, electrical limits, functional behavior, thermal performance, and compliance evidence.

This is especially important for power switches and connectors. A MOSFET selection reference can help organize the initial search, but the final decision must use the converter waveform, junction-temperature estimate, and gate-drive conditions from the real design.

Add lifecycle risk before the purchase order
A BOM review should ask four questions:

Is the part active, NRND, EOL, or already obsolete?
Is the quoted lead time based on normal stock or allocation?
Can an alternate be approved without a PCB respin?
Which parts must be bought through an authorized channel with lot traceability?
The answers affect design, procurement, and manufacturing at the same time. MOZPCB’s component-sourcing workflow describes a useful approach: identify hard AVL lines, flag long-lead and lifecycle risks, document approved substitutes, and verify the kit against the released BOM before assembly.

Small markings can cause large errors
Prototype repair work also exposes a basic problem: many SMD components are tiny or unmarked. A resistor marked 472 is 4.7 kΩ under the common three-digit code, while an MLCC may have no marking at all. EIA-96 codes add another layer of interpretation. When the board, BOM, and placement file disagree, measure the part and verify the manufacturer data rather than guessing. The SMD resistor code calculator is a quick cross-check for common markings.

Design for the assembly process
A good BOM is connected to the assembly drawing, centroid file, stencil notes, polarity rules, DNP lines, MSL handling, and inspection plan. For fine-pitch or mixed-technology boards, the manufacturing package should state the intended reflow sequence and the acceptance criteria for AOI, X-ray, and functional test. PCB assembly guidance is relevant when the design is moving from a hand-built prototype to a repeatable small-batch process.

Finally, keep a change record. When a part is replaced, record why it changed, what was tested, and which production revisions are affected. A BOM that captures those decisions becomes a reliability tool—not just a list of prices.

References
Octatronics technical resources
MOZPCB component sourcing