Altiumr To Xpeditionr Translator User Guide Exclusive Access

Execute a global text resize operation on the silkscreen layer. Unmatched naming conventions in the source project.

After translation, immediately run the Database Integrity Check in Xpedition ( Tools » Data Cleanup » Check Database ). A clean report means you have successfully bridged the EDA chasm.

: Altium's pad stacks are defined directly within the footprint. The translator extracts these and populates the Xpedition Padstack Manager. altiumr to xpeditionr translator user guide exclusive

: Nested split plane shapes in Altium losing their net identification boundaries.

Target the primary Altium Project file ( .PrjPcb ) or individual .SchDoc files. Execute a global text resize operation on the

: Save Altium PCB files in a binary format or ASCII , depending on the specific translator version being used.

For boards under 8 layers and 500 components, the Altium-to-Xpedition translator achieves ~90% fidelity in 2 hours of work (including cleanup). For high-density, high-speed, or rigid-flex designs, use the translator only for placement/route seed data, then recreate constraints and rules manually in Xpedition’s CES. A clean report means you have successfully bridged

Align Altium’s routing layers (e.g., Top Layer, Internal Plane 1) with Xpedition’s defined Layer Stackup.

Ensure every component on the schematic matches its corresponding database or library definition.

Configure the conversion of design rules. Note that Altium rules (flexible) do not map 1:1 to Xpedition rules (stringent).

Verify that the number of nets in the source Altium design matches the imported Xpedition design.