Successful translation starts before you even open the converter. A messy Altium design will result in a messy Xpedition design.
If you are an existing Xpedition user, the internal is your primary asset. Siemens supports the direct translation of reference designs created in Altium through PMW, utilizing specific translation guides and configuration files designed for this conversion.
Altium’s Clearance and Width rules . You must recreate: altiumr to xpeditionr translator user guide exclusive
If you will regularly receive Altium designs, create a using Xpedition’s VBAPI.
The translator is primarily used to convert Altium schematic and layout files into formats compatible with Xpedition. Successful translation starts before you even open the
Altium frequently embeds absolute paths. Xpedition relies on variable paths (e.g., $CENTRAL_LIBRARY ). Ensure your ee.ini or project configuration files are updated to recognize the Altium source directories.
1. Introduction to the Altium to Xpedition Translation Utility Siemens supports the direct translation of reference designs
The translation process utilizes the Siemens Data Management or Layout toolset configuration.
This occurs when Altium geometric primitives use custom arcs that exceed Xpedition's vertex resolution limits. Before translating, use Altium’s "Convert Polygon to Lines" utility to simplify high-density paths. Pro-Tip: Process Libraries Separately From Layouts
[Altium Schematic (.SchDoc)] ---> [xDX Designer Translator] ---> [Siemens Schematic] [Altium Layout (.PcbDoc)] ---> [xPCB Layout Translator] ---> [Siemens PCB Design] [Altium Library (.SchLib)] ---> [Library Manager] ---> [Central Library (.lmc)] Critical Data Mapping Matrix Data Class Altium Source Format Siemens Xpedition Target Format ASCII / Binary .SchDoc xDX Designer Project Database PCB Layout ASCII .PcbDoc xPCB Layout Database ( .pcb ) Schematic Symbols .SchLib / Integrated Library Central Library Symbol Block ( .sym ) Component Footprints .PcbLib / Integrated Library Central Library Cell ( .cel ) Phase 1: Pre-Migration Database Conditioning