PADS · PCB Design · Decal and Footprint

Reading an SOIC Footprint and a PPG Schematic as Separate PADS Examples

2026-08-01 · updated 2026-08-01 · Hyeongrok Ryu

My notes on a six-pin SOIC decal and an OPA2333, filter, logic, and layout capture as two separate PADS examples.

Series
PADS PCB Design · 3
Type / level
study-note · intermediate
Tools
PADS Logic, PADS Layout
01Why I kept the screens separate

A checkpoint in the study sequence for this note.

02Six-pin SOIC dimensions

A checkpoint in the study sequence for this note.

03Pin numbering and direction

A checkpoint in the study sequence for this note.

04PPG signal chain

A checkpoint in the study sequence for this note.

A compact concept path generated from this post's table of contents.

Why I kept the screens separate

I reopened a Decal Wizard capture and a separate PPG schematic/layout capture from the same study folder. Nothing in the saved material proves that the six-pin SOIC decal was used in the PPG design. I therefore placed them beside each other as two PADS exercises instead of inventing a shared part flow.

An independent six-pad SOIC decal example beside a separate OPA2333, filter, SN74LVC logic, and layout example
The panels come from separate saved captures. Their placement does not imply that they share one package.

Six-pin SOIC dimensions

The Decal Wizard screen uses six SMD pins with pad width 0.6 mm and length 1.05 mm. Pin pitch is 1.27 mm along a row, while the distance between row centers is 2.65 mm. I initially mixed up lead span and row pitch, so I mapped each number back to a line on the package drawing.

Saved PADS Decal Wizard screen with six-pin SOIC dimensions
I converted my saved Decal Wizard screen to WebP without metadata.
ItemEntered valueReference
Pin count6three on each side
Pad width0.6 mmshort pad dimension
Pad length1.05 mmoutward from body
Pin pitch1.27 mmspacing within one row
Row pitch2.65 mmdistance between row centers
Pairing each number with its geometric reference made the wizard inputs less ambiguous.

Pin numbering and direction

The stored screen uses counter-clockwise numbering and a visible pin-1 mark. After building a footprint, I need to compare that numbering with the schematic symbol before checking anything else. A correct outline with the wrong pin map would still produce the wrong netlist.

PPG signal chain

The separate PPG schematic screen shows OPA2333 amplification stages, RC filtering, and an SN74LVC-family logic stage. The signal is amplified and bandwidth-limited before it reaches the logic interface rather than being connected directly. I do not identify the visible OPA2333 package with the six-pin decal from the other capture.

Saved PADS screen with OPA2333 stages, SN74LVC logic, and early Layout placement
This is the actual saved PADS schematic and early placement view.
PPG input
  → OPA2333 amplification
  → RC filtering and gain
  → OPA2333 output stage
  → SN74LVC logic interface
  → placement view in the PPG capture
I kept only the functional blocks visible in the saved screen and did not invent component values or cutoff frequencies.

What the layout screen shows

The same capture places a PADS Logic schematic beside a PADS Layout placement view. It shows that parts and connectivity reached the layout stage. A design screen alone does not establish fabrication, completed DRC, or measured PPG performance.

My next check

Next I will compare the six-pin decal against its actual package drawing, including pin 1, pad dimensions, and courtyard. For the PPG design, I need a part-to-footprint mapping before inspecting packaging, net names, and unrouted connections. Until that mapping exists, I will keep the captures as separate artifacts.

Sources used

Publication first-page preview