³Ô¹Ïtv

Separate aperture selection from exposure

An aperture is a defined imaging shape. A circular aperture can form a round flash or sweep a line with a width related to its diameter. Other apertures can represent rectangular, obround or more complicated shapes. The identifier is a reference to that definition, not the dimension itself. D10 does not mean a ten-mil line, a ten-millimeter hole or the tenth copper layer.

Selecting D10 establishes the current aperture for subsequent operations that use it. Selection alone does not put a feature onto the image. This is useful when investigating a supposedly missing pad: first look for the operation that uses the aperture, then check the definition and coordinate context. Finding a definition in the header does not prove it is ever flashed.

The distinction is particularly important when a file arrives without its original context. Modern Gerber carries aperture definitions in the file. Older Standard Gerber may depend on a separate table. If those definitions are missing, the problem belongs to RS-274D recovery and aperture tables. Guessing the shape from a familiar D number can make the picture plausible while leaving the dimensions wrong.

D numbers have two different jobs

Gerber D-code step explorer

Follow the current point through a short example

Consider a teaching sequence that selects a 0.30 mm circular aperture, moves to X0 Y0, and draws to X10 Y0. The move establishes the start point without exposing a connecting line from an earlier location. The draw then sweeps the selected aperture along the horizontal segment. A later selection of a 1.20 mm circle followed by a flash at X10 Y5 creates a separate circular feature.

In the worksheet, this sequence produces five readable steps: select, move, draw, select and flash. The result names the coordinates and the chosen identifier so that you can follow the state change without decoding a full file. Change the final Y coordinate and regenerate the result to see that the earlier geometry does not change merely because the final point moved.

The example is intentionally not a standalone Gerber file. It has no coordinate-format declaration, unit command, file attributes or end-of-file record. Those omissions keep the teaching task narrow; they are not export recommendations. Do not paste the example into a production archive or infer that a command list accepted by the worksheet is accepted by a CAM system.

Why coordinates cannot be read in isolation

Real files can encode coordinates without an explicit decimal point according to a declared format. A string of digits therefore needs its format and unit context before it has a physical dimension. Changing a decimal interpretation can scale every feature while preserving the apparent shape. A viewer that auto-detects the wrong convention can make a valid file appear damaged.

Coordinate omission also matters. An operation may specify only one axis while retaining another established value. The teaching explorer permits an omitted axis only after both coordinates have been established, and it requires a move before a draw. This is a deliberate guardrail for the example. It is not a complete implementation of every legal initialization or modal behavior in the format.

When investigating scale, measure two independent known dimensions and compare them with the drawing. The millimeter and mil conversion reference helps check arithmetic, but it does not identify an unknown file format. Preserve the source before trying alternative reader settings. Record which setting produced which observation instead of repeatedly saving modified copies over the original.

Regions, arcs and polarity change the interpretation

The simple phrase D01 draws a line needs context. Outside a region, a draw uses the current aperture along the defined path. Within a region, draw operations define contour segments that contribute to an area. Treating a region contour as an ordinary stroked trace can produce a substantially different image. The worksheet rejects region commands instead of pretending to interpret them.

Interpolation controls whether a path is straight or curved. Arc commands also require the relevant center or offset information and interpretation rules. A D01 operation with an arc context is not the same task as the straight segment in the example. If your support question involves curves, provide the surrounding commands and the original file, not just the line containing D01.

Polarity and other image operations can add or clear areas. A feature that appears in an intermediate operation may not remain in the final image. Aperture macros, blocks and repeated structures add further context. These are reasons to use a conforming viewer and the official specification for real data, not reasons to infer corruption whenever a file contains commands beyond the introductory examples.

A flash is not a drilled hole

A D03 flash produces an image feature using the selected aperture. A round feature on a copper layer may be a pad, a test point or another conductive shape. It does not, by itself, order a drill operation through the board. Hole fabrication requires the agreed drill or routing data and relevant layer-span and plating information.

This distinction prevents a common release error: inspecting copper pads and assuming all holes have been delivered. Load the drill data with the artwork, compare hole centers with their intended pads and inspect mechanical holes separately. For slots, confirm the routed shape and its intended plating rather than treating a drawn rectangle or obround copper pad as sufficient instruction.

The NC drill file guide explains that separate manufacturing task. If the receiving workflow uses an integrated archive, the ODB++ versus Gerber comparison can help identify where the equivalent information is carried. The format choice changes the packaging, not the need to communicate the actual hole requirements.

Diagnose an apparent artwork error without creating a new one

Start with an untouched copy and note the source revision, affected layer and viewer version. Open the same file in an independent suitable viewer. Compare known dimensions, aperture definitions and the final image around the suspect feature. An annotated screenshot can identify the location, but the text file and settings are needed to reproduce the interpretation.

If the two views disagree, distinguish a parser limitation from missing data. Check whether the file uses a supported format revision and whether the viewer understands its region, polarity and macro constructs. Do not replace advanced constructs with guessed simple flashes unless the result is deliberately re-engineered and verified against an authoritative design.

For a manufacturing enquiry, give ³Ô¹Ïtv the full current fabrication release and a short description of the discrepancy. State what you expected, what was observed and which dimension or feature matters. The exported teaching report can help explain your reasoning, but it is optional. A precise question with original data is more useful than a blanket request to fix all D codes.

A disciplined way to investigate an unfamiliar command

First preserve the source and identify the format declaration. Read a small region around the command rather than changing an isolated number. Aperture, position, interpolation and polarity state may have been established earlier. Record what the official syntax says separately from what a viewer actually displays. If two viewers disagree, reduce the issue to a minimal example and retain the original file for comparison.

For a production question, include the affected layer, expected feature and a marked image with dimensions. A description such as missing pad does not tell the reviewer whether the cause is absent data, a viewer setting, clipping, polarity or a manufacturing interpretation. The shortest useful handoff explains which observation is reproducible and which explanation remains a hypothesis.