Direct transfer
One-click or very-low-click export of the currently open PCB, without a normal file-browsing and import step.
Transfer the currently open PCB design from your PCB CAD directly to PhCNC / PhPNP using the CAD system's own native ODB++ exporter.
No Gerber export. No manual ZIP handling. No intermediate conversion.
Each Bridge uses the exporter supplied by the PCB CAD vendor. TELENET handles the surrounding workflow and the handoff of the resulting ODB++ project.
| PCB CAD | Supported version | Bridge type | Installation note |
|---|---|---|---|
| KiCad | 10+ | Executable IPC plugin | Automatic; restart KiCad after install or update. |
| Altium Designer | 17+ | Toolbar integration | Automatic; close Altium for reliable install or update. |
| EasyEDA Pro Desktop | 3.2+ | Desktop extension | The prepared .eext package is imported manually. |
| OrCAD X / Allegro | 25.1+ | SKILL / Tcl integration | Requires Siemens ODB++ Inside; CAD processes must be closed for changes. |
| Autodesk Fusion Electronics | Tested with build 2704.1.53 | Fusion Add-In | Automatic; restart Fusion after install or update. |
ODB++ Bridge is not an ODB++ converter. The open PCB is exported by the CAD system itself, then passed to the selected PhCNC / PhPNP application.
One-click or very-low-click export of the currently open PCB, without a normal file-browsing and import step.
Available layers, components, nets, drill and PnP information are preserved by the native CAD exporter.
The generated project is submitted to PhCNC / PhPNP without manually extracting an ODB++ archive.
If a target cannot be launched, the generated archive remains in the Bridge folder and clipboard fallback is available.
Bridge management: PhCNC / PhPNP detects supported installed PCB CAD systems and provides an ODB++ Bridge Plugins interface for enabling, installing and updating integrations.

The Bridge is registered as an executable IPC plugin and adds an O++ button to PCB Editor. It works with the current board, saves as needed and uses kicad-cli for native ODB++ export.
If the KiCad API is disabled, PhCNC / PhPNP can enable it automatically while KiCad is closed. KiCad must have run at least once so its configuration exists. If the target is unavailable, the generated archive and clipboard path remain available.
This integration targets KiCad 10+. It is not the legacy KiCad 8 Python Action Plugin mechanism.

Transfer the currently open KiCad PCB through KiCad's native ODB++ exporter directly into PhCNC LSSE and continue immediately with PCB CAM processing.
Transfer the currently open KiCad PCB and available ODB++ component information directly into PhPNP for Pick & Place preparation.
The Bridge adds an O++ button and supports both the legacy toolbar interface and newer ActiveBar behavior. It uses Altium's native ODB++ output and hands the generated project to PhCNC / PhPNP. PCB panel projects are supported.
Installation: close Altium Designer before Bridge installation or update. The integration backs up the user toolbar configuration before modifying it.

The Bridge package is prepared automatically, but EasyEDA requires manual confirmation when importing its .eext extension.
easyeda-odbpp-bridge_vX.Y.Z.eext file.EasyEDA Pro Desktop is supported. EasyEDA Standard and the browser edition are not targets of this Bridge.


SKILL / Tcl startup integration adds OrCAD ODB++ Bridge to the Manufacturing menu. The Allegro PCB engine uses the native vendor flow supplied by Siemens ODB++ Inside for Cadence Allegro, which must already be installed.
Installation, update and removal: fully close OrCAD X / Allegro. In practice, orcadx.exe, allegro.exe and unison.exe must not be running.
The vendor exporter asks whether to extract net impedance average. This Siemens-controlled dialog is expected; either Yes or No permits valid ODB++ generation.

The automatically installed Fusion Add-In adds ODB++ BRIDGE to Utilities in the 2D PCB workspace. Modified writable PCBs are saved first, then Fusion's native ODB++ exporter runs silently with no manual ODB++ export dialog in the normal workflow.
The Bridge replaces its deterministic generated archive, detects export completion and hands the result to PhCNC / PhPNP. If no target is available, the archive remains available and its path is copied to the clipboard.
The production workflow has been regression-tested end to end with Autodesk Fusion build 2704.1.53.

Open a PCB in the supported CAD system, then use its O++ or ODB++ Bridge command.
The most recently started PhCNC / PhPNP product is the current target. Starting PhCNC after PhPNP selects PhCNC; starting PhPNP afterward selects PhPNP.
If the target is running, the project is submitted to it. If it is not running, the selected application starts automatically.
If the target is missing or cannot start, a successfully generated ODB++ project is not lost. It remains in the Bridge working folder and the archive/path is placed on the Windows Clipboard for manual use.
If PhCNC / PhPNP is in CNC mode, the incoming import is ignored.
The Bridge is CAD-independent. The generated native ODB++ project can be used for PCB CAM in PhCNC products or assembly preparation in PhPNP.