The transition from Altium Designer to Siemens Xpedition Enterprise is handled through a Project Migration Wizard, which automates the conversion of schematics, PCB layouts, and library data. Detailed procedural instructions are officially documented in the "Altium to Xpedition Translator User Guide" available on Siemens SupportNet. Phase 1: Pre-Translation Preparation

Before initiating the translator, you must ensure the source Altium data is in a state the Xpedition migration tools can interpret.

Synchronize Design: The Altium schematic and layout must be fully synchronized (Forward/Back Annotate) before export to prevent connectivity discrepancies.

Export as ASCII: Save your Altium PCB files in ASCII format (*.PcbDoc saved as PCB ASCII). The translator typically cannot process Altium's proprietary binary formats directly.

Clean Up: Remove redundant data, such as unused pads or unplaced components, to simplify the conversion database. Phase 2: Executing the Translation

Siemens provides a wizard-driven interface within Xpedition to manage the import.

The document you are looking for is the Altium® to Xpedition® Translator User Guide, which is an official Siemens EDA document. This specific guide is not publicly hosted for open download because it is considered proprietary; however, it is accessible to licensed users through the Siemens Support Center (formerly SupportNet). How to Access the Official Guide

To obtain the primary "exclusive" user guide, you should follow these steps:

Visit Siemens Support: Log in to the Siemens Support Center.

Search the Documentation: Search for the "Altium to Xpedition Translator User Guide" within the Xpedition product documentation section.

Check Community Attachments: Some configuration files and simplified translation guides are occasionally shared in the Siemens Community for specific uses, such as translating semiconductor reference designs. Key Technical Insights from the Translation Process

While the full manual is behind a login, the following critical steps and considerations are standard for the Altium-to-Xpedition workflow:

Project Migration Wizard: Xpedition uses a built-in Project Migration Wizard to handle the translation of Altium-created designs.

Mandatory Files: For a successful translation with correct design hierarchy, you must provide the *.PrjPcbStructure file along with the main *.PrjPcb file.

Pre-Translation Synchronization: It is strongly recommended to ensure your schematic and layout are fully synchronized within Altium before starting the export to avoid data discrepancies.

Mapping Files: A mapping file is typically required to reconcile differences in pin naming between Altium schematics and Xpedition footprints.

Library Translation: Components, padstacks, and cell definitions are usually handled through Library Services in Xpedition to ensure they integrate correctly into the Central Library.

It seems you're looking for a user guide on translating designs from Altium to Xpedition, which appears to be a specific and technical requirement. The task involves converting PCB (Printed Circuit Board) designs from Altium Designer to a format compatible with Xpedition, likely Mentor Graphics Xpedition, a tool used for PCB design and layout.

While I don't have a specific user guide or document titled "Altium to Xpedition Translator User Guide" or similar, I can provide you with a general approach on how to achieve this translation. This process might require some manual adjustments and understanding of both software systems.

Phase B: Run the Standalone Translator

  1. Launch Altium to Xpedition Translator.
  2. Input Tab:
    • Source File: Browse to MyDesign_Prep.PcbDoc.
    • Netlist File: Browse to MyDesign.NET.
  3. Layer Mapping Tab (Crucial):
    • The translator will show a preview. Map Altium Mechanical 1 → Xpedition BOARD_OUTLINE.
    • Map Altium Keepout → Xpedition PLACE_BOUND.
    • Ignore Altium Drill Drawing layers unless you want non-electrical geometry.
  4. Preferences Tab:
    • Check: "Convert Polygons to Plane Shapes" (Converts Altium hatched pours to Xpedition dynamic planes).
    • Check: "Regenerate Teardrops" (Altium teardrops become Xpedition teardrops via post-process).
    • Uncheck: "Translate 3D Models" (Avoid crash).
  5. Hit Execute. The output will be a folder containing:
    • MyDesign.PCB (Xpedition board file)
    • MyDesign.hkp (Netlist and rules)
    • MyDesign.log (Translation report)

Phase C: Execution & Log Analysis

Click "Translate" . Do not walk away. Watch the console log.

Common Error Codes:

  • Error 401: "Footprint pad stack mismatch" -> Go back to Altium, remove octagonal pads (Xpedition uses round/oval/square only).
  • Warning 223: "Net name truncated" -> Xpedition limits net names to 256 characters; Altium does not. Shorten excessively long hierarchical net names.

Challenges and Considerations

  • Design Intent: Maintaining the original design intent during translation can be challenging. High-speed design constraints, differential pairs, and net classes may need special attention.

  • Component Models: Ensuring that all component models are accurately translated or available in Xpedition is critical. This includes not just physical footprints but also simulation models.

  • User Interface and Workflow Differences: Familiarization with the Xpedition environment and its workflow is necessary, as it may differ significantly from Altium.

Part 6: Exclusive Troubleshooting Matrix

| Problem | Symptom | The Translator Fix (Not Altium) | | :--- | :--- | :--- | | Missing Vias | Via holes appear, but no annular rings | Run translator with -convertMicroViaAsStandard true via command line | | Solder Mask Inverted | Pads are covered, copper is exposed | In mapping file, add <SwapMaskLayers>true</SwapMaskLayers> | | Component RefDes Shifted | Reference designators are 10mm away from body | Re-run with -preserveTextJustification true flag | | Netlist Corruption | "Net '$N_0001' not found" | This is a legacy Altium unique ID mismatch. Use -regenerateUIDs true |

Step 3: 3D Model Reconciliation

Altium stores 3D bodies as STEP embedded in the PCB. Xpedition prefers external .stp files referenced in the Cell Editor.

  • Go to 3D View. If components are floating, run Tools > 3D > Update Step Models from Library.

3. Translation Methods

  • Direct Import if Supported: Check if Xpedition directly supports Altium Designer files (.PcbDoc, .SchDoc). If so, use that.
  • Neutral File Conversion: Use neutral formats like ODB++ or IPC-2581 for translation.
    • ODB++: A comprehensive format that includes all design data. Altium can export ODB++, and Xpedition can likely import it.
    • IPC-2581: Another standard format for exchanging PCB design data.

Phase C: Import into Xpedition Layout

  1. Open Xpedition Layout (formerly Expedition PCB).
  2. Go to File » Import » Design Data...
  3. Select "Altium PCB ASCII" as the source type.
  4. Point to the .PCB file generated.
  5. In the "Padstack Mapping" dialog:
    • Click "Auto-Match by Size." Manually fix any Unknown padstacks by referencing your Central Library.
  6. Click Import.
-->