• 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. PCB Design
  3. Extracting Multiple Nets from PCB Editor into SigXplore...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 164
  • Views 16450
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Extracting Multiple Nets from PCB Editor into SigXplorer

archive
archive over 17 years ago

I hope that this question is appropriate for this forum

I am using the "L" version of PCB Performance and SigXplorer and am still somewhat new to them.

I am trying to use the Topology Extract feature to extract a net into SigXplorer. The net is actually divided into 2 individual nets with 2 net names. Net #1 is routed from the driving source to one side of a series terminating resistor. Net #2 connects the other side of the term. resistor to the receiver.

Using Topology Extract, I can only seem to extract one net or the other (including the resistor) into SigXplorer. How do I specify that I want to extract the entire net (from source to receiver)?

Thank You

Nick


Originally posted in cdnusers.org by nipri
  • Cancel
  • archive
    archive over 17 years ago

    Hi,
    the SQuest & SigExp must recognize the net as xnet, for that you need to assign a SI model to the serie resistor.
    Doron.


    Originally posted in cdnusers.org by darmoni
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi and thanks for the reply!

    The resistor is part of a resistor pack to which I have created / assigned an IBIS device model. I assigned all of my IBIS models through the Setup Adviser.

    How are Xnets created? Is this done through the Constraint Manager? My installation of 16.0 seems to have some problems with the help files!

    Nick


    Originally posted in cdnusers.org by nipri
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    if you created it right then it should work.
    you either didn't creat a valid part or didn't assign it in the advisor,
    make sure that the value field is a number only (10 not 10R or such).
    also i think that it should be a spice model device not ibis model.
    good luck.
    Doron.


    Originally posted in cdnusers.org by darmoni
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    You have to assign a dml model to the rpack and the rpack has to have the property of being a discrete for this to work correctly. SourceLink has a good example of an Rpack with common pins and the create e spice model will do standard rpacks automatically.


    Originally posted in cdnusers.org by Kalevi2
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    >>You have to assign a dml model to the rpack<<

    Actually, I used the IBIS file generator in Model Integrity to make an Ibis model for the resistor pack which has 8 isolated resistors (not bussed, no common pin) I then converted the Ibis device model to DML and assigned it to each resistor pack in my design through the Adviser. The value field is set to the value of the resistor (47) with no other chars.

    When I extract either net into SigXplorer, the resistor also ports in with the correct pins on the resistor pack that the nets are connected to and the correct R value (47) also ports in. It's only the other net and its driver or receiver that doesn't port in.

    >>the rpack has to have the property of being a discrete<<
    Where do I set this?

    >>SourceLink has a good example of an Rpack with common pins<<
    Im in the process of looking for this now.

    Nick


    Originally posted in cdnusers.org by nipri
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
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.

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

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