Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 16217
  • 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

Schematic property cleanup in Capture 16.6

mlenander

I'm trying to clean up some old schematics that drew parts from different locations, and hence have different formatting. I'm running into issues with how to make changes to entire pages or the whole design. The fixes are easy part by part, but there are hundreds of them. Many options seem to be unavailable when using the search function, like setting property visibility.

  1. How can I set the visibility of properties across the whole design based on their value? I'd like to turn off the "Package" property visibility for 0603 parts and turn it on for 0402 parts.
  2. Is it possible to merge properties? I have some parts that use "Manufacturer Part Number" and some that use "MFR PN". I'd like to move the "Manufacturer Part Number" to the "MFR PN" if "MFR PN" is empty, but not if "MFR PN" already exists.
  3. Is there any way to preserve a "Manufacturer Part Number" that is displayed on the schematic after merging with "MFR PN" in #2? It should switch to a "MFR PN" so I can delete the deprecated property but maintain the positioning, font, etc.
  4. How do I merge all occurrence properties into the instance properties? I am using a simple, non-hierarchical design. Occurrences are unnecessary, but some of the parts have them. Unfortunately, the occurrence contains the more up to date information where they exist. The function in Accessories "Push Occ. Properties Into Instance" only moves the Part Reference and PCB Footprint, but there are other relevant user properties like manufacturer part number and company part number that don't get pushed.
  5. Is it possible to delete empty properties across the entire design? I have a bunch of parts that contain properties that must have come from some kind of template but were never filled in. For example, I have connectors with a "Plating" property that is blank. I also found some resistors with the nonsensical "Wavelength" property that is also blank. These sorts of properties clutter up the property spreadsheet and in some cases are completely inappropriate.

Thanks.

Parents
  • mlenander

    The Export/Import Properties is extremely helpful. That should let me do most of the things I want to. It also made it clear what the "empty" properties actually are. Instead of containing <null> when exported they are a null string or blank cell in Excel. I can generate them by copying a blank cell from Excel and pasting it into the Edit Properties spreadsheet in Capture.


    Is there no similar way to export displayed properties for an instance of a part? I was hoping for some way to export all of the lines/text that make up the schematic symbol along with the pin locations/properties, displayed properties with their settings and position, and part location on the schematic. That would let me script changes to virtually all aspects of the schematic. But if that doesn't exist, I'll just have to work around it.


    Thanks for your help.

Reply
  • mlenander

    The Export/Import Properties is extremely helpful. That should let me do most of the things I want to. It also made it clear what the "empty" properties actually are. Instead of containing <null> when exported they are a null string or blank cell in Excel. I can generate them by copying a blank cell from Excel and pasting it into the Edit Properties spreadsheet in Capture.


    Is there no similar way to export displayed properties for an instance of a part? I was hoping for some way to export all of the lines/text that make up the schematic symbol along with the pin locations/properties, displayed properties with their settings and position, and part location on the schematic. That would let me script changes to virtually all aspects of the schematic. But if that doesn't exist, I'll just have to work around it.


    Thanks for your help.

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.