Do you plan to manage this as a or integrate it into a Central Library ?
Note: Xpedition supports IPC-2581 and ODB++; use the one you created. If only Allegro ASCII or EDIF is available, use Xpedition’s Allegro translator or import utilities.
Supports the translation of Altium component libraries into Xpedition's Central Library ( .lmc ) format. Key Workflow Steps
The Altium to Xpedition Translator User Guide provides instructions for converting PCB design, schematic, and library data from Altium Designer to Siemens Xpedition Enterprise. The guide details requirements for importing design files, including mapping layers and converting libraries for successful migration. Access the official guide through the Siemens Support Center or within the Xpedition installation directory. Altium Design Software Import-Export Support
Resolve all electrical and manufacturing violations in Altium before exporting. altiumr to xpeditionr translator user guide exclusive
A robust translator precisely converts existing ECAD library data into Xpedition's central library format. This ensures that symbols and footprints remain identical to the original design, eliminating double data entry.
Once both are imported, you must manually link the new schematic to the new PCB file to re-establish cross-probing and design integrity. 3. Post-Import Checklist
Siemens EDA has partnered with semiconductor vendors to make reference designs available in Xpedition format. If a reference design is not yet available on the vendor's site, the Project Migration Wizard can be used to translate the Altium version directly. Translation guides and configuration files are available for this specific use case, streamlining the process for hardware engineers working with evaluation boards and application reference designs.
Siemens provides a dedicated that can translate Altium reference designs into Xpedition format. The wizard comes with translation guides and configuration files specifically developed for converting Altium designs. Do you plan to manage this as a
: Use the XDX Designer tools to link the newly translated schematic and PCB files, enabling cross-probing between the two editors. Key Features and Best Practices
| Error Message | Root Cause | Solution | | :--- | :--- | :--- | | "Unsupported primitive: Region" | Altium has a complex cutout in a polygon. | In Altium, convert polygon to separate pour outlines. | | "Netlist mismatch: 12 nets missing" | Altium PCB ASCII had unnamed copper islands. | Run Tools » Netlist » Configure in Altium; assign dummy nets to islands. | | "Padstack XYZ not in library" | Translator generated a custom pad size not in Xpedition lib. | Note the dimensions (e.g., 1.2mm round ). Create it manually in Library Manager. | | "Board outline is open loop" | Altium defined outline as multi-segment lines (not a closed polygon). | In Altium, use Design » Board Shape » Define from Selected Objects . Re-export. |
Xpedition separates logical symbols from physical padstacks and footprints via the Central Library. Load the Altium *.PcbLib ASCII file into the translator.
Based on the documentation for Altium, here is a notable exclusive feature typically detailed in that guide: Supports the translation of Altium component libraries into
Navigate to for the PCB design and select Protel PCB ASCII File (*.PcbDoc) .
The most common translation errors stem from:
For the exact workflow, refer to the Siemens Support Center document: – Section 4.3 (“Parameter Mapping”) and Section 5.2 (“Conditional Cell Assignment”).