Proteus DISCUSSION

What should a Proteus output-job profile include for a repeatable PCB release?

Started by kk2424 Proteus output jobsGerber exportPCB releasedrill filesassembly data
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

What should a Proteus output-job profile include for a repeatable PCB release?

kk2424 Proteus Forum
#1

The Proteus 9.2 Output Job Manager can retain export settings in a reusable profile. How would you organize a release profile for a board that needs fabrication and assembly?

The aim is to avoid sending Gerbers from one revision with a BOM or placement file from another. Which outputs should be generated together, and what checks still belong outside the export operation?

Reference: Labcenter: Proteus 9.2 release notes (https://www.labcenter.com/whatsnew/9.2/).

Community replies 3

Re: What should a Proteus output-job profile include for a repeatable PCB release?

#2

Generate the copper, mask, silkscreen, outline and required drill outputs from the same saved design revision. Include a fabrication drawing or readme identifying layer order, thickness, finish and special requirements. For assembly, include the BOM, placement data and drawings that identify polarity and unpopulated parts. Use revision-specific folders so a later export cannot silently replace a released package.

Re: What should a Proteus output-job profile include for a repeatable PCB release?

#3

Validate the package with an independent viewer. Check that the outline is closed, holes are correctly classified, units and coordinate origins agree, and the intended layers are present. Placement files also need an orientation check against the assembler's convention. Automating the export repeats the selected settings; it cannot determine whether those settings match a particular manufacturer's requirements.

Re: What should a Proteus output-job profile include for a repeatable PCB release?

#4

Archive the profile and output manifest with the exact submitted files. A useful release process first saves the design, updates copper fills, runs checks, generates all outputs and reviews the resulting package. Keep a short record of accepted exceptions. If an output is manually edited afterward, record that modification or regenerate it from the design so the archive remains explainable.

TEP COMMUNITY