• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. (SPMHGE-779): Place replicate module component net profiles...

Stats

  • State Suggested Answer
  • Replies 1
  • Answers 1
  • Subscribers 165
  • Views 140
  • Members are here 0
More Content

(SPMHGE-779): Place replicate module component net profiles incompatible with design module instance 'CR_xxxxxx_MAPPED1_1'. Instance not modified.

TT202608257415
TT202608257415 5 days ago

Hi,

I get the following error in OrCAD X PCB Professional 25.1-2025 S030 [3/25/2026] Windows SPB 64-bit Edition: (SPMHGE-779): Place replicate module component net profiles incompatible with design module instance 'CR_xxxxxx_MAPPED1_1'. Instance not modified.

This error appears when I try to replicate apply an MDD file. Please see below workflow hat leads up to the error. 

1. Extract an mapped module from an existing board (origin.BRD) by selecting module --> RMB "Place replicate update" and save as origin.MDD

2. Create new board (new.BRD) and import netlist from origin.BRD

3. Quickplace all components and select all components --> RMB "place replicate apply" --> choose origin.MDD

4. The module attaches to the cursor ready to be placed --> then placed within outline.

5. PCB Editor is busy for 10 seconds and places the module in the outline, but in the command window the above mentioned error appears.

I tried to find information online but I cannot find any explanation of this error or the severity of this error (can it be ignored?). And what does it exactly mean that the instance is not modified?

Thanks in advance.

  • Sign in to reply
  • Cancel
Parents
  • JuanCR
    0 JuanCR 4 days ago

    The error SPMHGE-779 typically indicates a mismatch in the net connectivity or component properties (Device/Value) between the module definition (.mdd) and the instance in your design.

    Ensure that the net assignment profile for the components matches. The tool cannot automatically resolve matches if the netlists are inconsistent.

    If you need to bypass these checks (e.g., when using different component values in different groups), select the module instance and choose the Place Replicate Update option. This opens a dialog where you can disable Device Name / Value matching options.

    If you encounter SPMHGE-779 during a module replacement or update, follow these steps to resolve the incompatibility:

    1. Disband the Existing Group:

      • Switch the application mode to General Edit (Setup > Application Mode > General edit).
      • In the Find tab, enable Groups and select the problematic module instance.
      • Right-click and select Disband group. This removes the module association while keeping the components in place.
      • Re-apply the new or updated module using Place replicate apply in Placement edit mode.
    2. Verify Component Status:

      • Ensure all components intended for the module are UNFIXED. Use the unfix command if necessary to allow the tool to include them in the replication process.
    3. Check for Shape Conflicts:

      • By default, dynamic shapes in a module are converted to static shapes during application to prevent conflicts. If you need to maintain dynamic shapes, you can set the environment variable disable_module_shape_convert.
    4. Bypass Property Checks (Workaround):

      • As noted in previous investigations, if the mismatch is due to non-critical properties like "Device Name" or "Value," you can use the Place Replicate Update command and disable the matching options for these specific properties to bypass strict checks.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • JuanCR
    0 JuanCR 4 days ago

    The error SPMHGE-779 typically indicates a mismatch in the net connectivity or component properties (Device/Value) between the module definition (.mdd) and the instance in your design.

    Ensure that the net assignment profile for the components matches. The tool cannot automatically resolve matches if the netlists are inconsistent.

    If you need to bypass these checks (e.g., when using different component values in different groups), select the module instance and choose the Place Replicate Update option. This opens a dialog where you can disable Device Name / Value matching options.

    If you encounter SPMHGE-779 during a module replacement or update, follow these steps to resolve the incompatibility:

    1. Disband the Existing Group:

      • Switch the application mode to General Edit (Setup > Application Mode > General edit).
      • In the Find tab, enable Groups and select the problematic module instance.
      • Right-click and select Disband group. This removes the module association while keeping the components in place.
      • Re-apply the new or updated module using Place replicate apply in Placement edit mode.
    2. Verify Component Status:

      • Ensure all components intended for the module are UNFIXED. Use the unfix command if necessary to allow the tool to include them in the replication process.
    3. Check for Shape Conflicts:

      • By default, dynamic shapes in a module are converted to static shapes during application to prevent conflicts. If you need to maintain dynamic shapes, you can set the environment variable disable_module_shape_convert.
    4. Bypass Property Checks (Workaround):

      • As noted in previous investigations, if the mismatch is due to non-critical properties like "Device Name" or "Value," you can use the Place Replicate Update command and disable the matching options for these specific properties to bypass strict checks.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information