• 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. Custom IC SKILL
  3. detect and optional remove dangling/floating schematic lines...

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 6887
  • Members are here 0
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

detect and optional remove dangling/floating schematic lines?

drdanmc
drdanmc over 7 years ago

Anyone have a good skill approach to detecting and removing floating or dangling schematic lines?  For example, consider a schematic which had a bunch of 3 terminal resistors which were replaced with 2 terminal resistors.  Now there are little stubs that used to connect to the 3rd terminal.  These may be lines which are a single segment with a label on it or they may be wires that route some distance and connect to a net.

I can think of some hacks involving a while loop that calls mks = setof(X cv~>markers X~>parent~>objType =="line") and then deletes lines and then schCheck(cv) to update the markers but that seems a bit ugly.

Thanks

-Dan

  • Cancel
  • skillUser
    skillUser over 7 years ago

    Hi Dan,

    Maybe iterate over wire segments to identify those that are over a symbol but not over a pin?  Use dbGetOverlaps() or similar to look under both ends of the wire segment, if neither is over a pin shape (and perhaps checking that at least one point is inside an instance selection box, maybe even specifically resistors) then this could be a wire segment that you are looking for [I can imagine some cases where a wire performs a bend right next to the resistor before connecting to the pin and thus being flagged, but better to find false positives than miss some wires].

    Hope this helps,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • drdanmc
    drdanmc over 7 years ago in reply to skillUser

    Thanks for the suggestion.  I was able to get something more or less working.  The couple of tricks were:

    keep_wire = nil

    foreach(pt fig->points

      ;;you can use a single point "bounding box"

      ;;restrict to wire/drawing lpp and top cv to get wires:

      r = dbGetOverlaps(cv list(pt pt) list("wire" "drawing") 0)

      ;; restrict to lines and paths

      r =  setof(X r member(X~>objType list("line" "path")))

      when(length(r) > 1 keep_wire = t) ;; we have a wire or path on this end

      ;; now look for connections to a symbol pin (1 == look this level and 1 down)

      r = dbGetOverlaps(cv list(pt pt) list("pin" "drawing") 1 ) 

      when(length(r) > 0 keep_wire = t) ;; we have a pin connection

    )

    unless(keep_wire dbDeleteObject(fig))

    feels like a real hack and it will miss things like a wire that has a jog in it but is otherwise not connected.  But still, better than nothing.

    On a different note, what is the magic in this forum to paste code in a more code-like format?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 7 years ago in reply to drdanmc

    Hi Dan,

    I use the full editor (which, of course, has just changed) and edit the HTML/source to change the 'p' tags to 'pre' tags and then further surround the SKILL with 'code' tags - each of 'pre' and 'code' need a start and end tag, but this seems to allow the code to stand out and read a little better.  I think Andrew uses a filter to add coloring to his code (I sometimes add bits by hand to color comments and so on).

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RK56
    RK56 over 7 years ago in reply to drdanmc

    Hi,

    Why not look for net names which do not connect to any instance?

    -Ramakrishnan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to skillUser

    I have a CGI script to format my code library - it uses this under the hood (in essence):

    enscript --color --language=html -Eskill --output=- code.il > code.html

    If you then display code.html in a web browser, you can copy and paste the formatted code into the forum.

    That said, I do remember having to ensure I use an older version of enscript (1.6.1) because some of the italics were a bit odd in 1.6.4 (I can't quite remember though - this was going back a few years).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to Andrew Beckett

    Sorry - I was wrong. I use enscript v1.6.5.1 because it fixed the earlier bugs in v1.6.4. I was looking at an old internal email when I was trying to use an older version with the scheme language mode; I later switched to the skill highlight mode.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • drdanmc
    drdanmc over 7 years ago in reply to RK56

    The basic situation that started this was changing from some 3-terminal resistor symbols where the 3rd terminal typically had a little stub of  wire labeled as VDD or VSS.  After switching to a 2-terminal symbol, that stub was not needed but of course VDD and VSS still went to instances in other parts of the schematic so deleting by net name wasn't effective.

    -Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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