KB: Update PCB Removes Components Due to Legacy Schematic File Extensions

Altium Designer Altium Designer
In some legacy Altium projects, running Update PCB may attempt to remove all PCB components, while functions such as Footprint Manager, netlist generation, and component synchronization fail to recognize schematic components correctly. This can occur when schematic files use legacy extensions such as S01 or S02. Although Altium Designer can open and display these files, they may not be fully recognized as native schematic documents for compilation-dependent operations. Renaming the schematic and PCB files to supported Altium document types, re-adding them to the project, and recompiling restores normal Update PCB processing and component recognition.

概略

In some legacy Altium projects, running Update PCB may attempt to remove all PCB components, while functions such as Footprint Manager, netlist generation, and component synchronization fail to recognize schematic components correctly. This can occur when schematic files use legacy extensions such as S01 or S02. Although Altium Designer can open and display these files, they may not be fully recognized as native schematic documents for compilation-dependent operations. Renaming the schematic and PCB files to supported Altium document types, re-adding them to the project, and recompiling restores normal Update PCB processing and component recognition.
AIでさらに深掘り:

Solution Details

Legacy Projects Show Missing Component Behavior

In some legacy projects, updating the PCB from the schematic fails even though the schematic appears normal. The issue may initially appear to be schematic corruption because components are visible and selectable, but several system functions do not recognize them correctly.

  • Update PCB attempts to remove all components from the PCB.
  • Footprint Manager reports No Valid Components To Change.
  • Parameter Manager and Update from libraries warning stating that the Project must be compiled first.
  • BOM report generates no component entries.
  • Project Component Links dialog shows empty schematic component lists.
  • Schematic components are visible and selectable but not recognized by system tools.
  • New components placed on the schematic are also not recognized.

Windows File Explorer listing Altium PCB project files, including .PrjPcb, .PcbDoc, and generated output files .s01 and .s02.

Altium error dialog stating “No Valid Components To Change,” with a red error icon and an OK button, indicating an action failed because no applicable components were found. Altium error dialog stating “Project must be compiled first,” with a red error icon and an OK button, indicating the attempted action requires compiling the project before proceeding. 

Altium Designer Bill of Materials dialog for a PCB project, showing an empty BOM table with zero items listed, indicating no components detected for the selected schematic files (.s01, .s02)

Altium Designer “Edit Component Links” dialog showing schematic and PCB component matching; schematic side lists no components for .s01/.s02 files, while PCB components are listed, preventing component pairing.

Unsupported Extensions Block Compilation Processing

The root cause is that the schematic files use legacy extensions such as .S01 and .S02. Altium Designer can open and display these files, but they may not be recognized as valid native Altium schematic documents for all compilation-dependent operations. As a result, components that appear normal on the schematic are not processed correctly by features that rely on successful project compilation and component recognition.

This distinction is important because document visibility alone does not guarantee that the files are participating correctly in project processing. Operations such as Update PCB, component synchronization, linking, and netlist generation depend on recognized native document types.

Use Native Document Types For Recovery

  • Permanent solution: Rename the legacy schematic and PCB files to supported native Altium document extensions and re-add them to the project.
  • Temporary workaround: Create a new schematic sheet and move the design contents to it using Edit » Refactor » Move Selected Subcircuit To Different Sheet. This may restore functionality temporarily but does not address the root cause.

Rename Files And Rebuild The Project

  1. Close the project in Altium Designer.
  2. Rename schematic files with legacy extensions such as .S01 and .S02 to .SchDoc.
  3. Rename PCB files to .PcbDoc.
  4. Reopen Altium Designer.
  5. Remove the original files from the project.
  6. Add the renamed native Altium documents back into the project.
  7. Compile the project and confirm that compilation completes successfully.
  8. Run Update PCB again.
  9. Verify that:
    • Components remain on the PCB.
    • Footprint Manager opens without reporting invalid components.
    • Component links can be updated successfully.
    • Netlist generation behaves as expected.
    • Update PCB completes normally.

Additional Notes

  • This issue can be mistaken for schematic corruption because the schematic remains viewable and editable.
  • During troubleshooting, creating a new schematic sheet and moving the design contents to it may temporarily restore Update PCB functionality.
  • The workaround should not be considered a permanent fix. The underlying issue is the use of unsupported legacy file extensions.
  • When working with older projects, verify the document extensions before investigating more complex schematic or component issues.

References

問題が見つかった場合、文字/画像を選択し、Ctrl + Enter キーを押してフィードバックをお送りください。