Stats

  • Locked Locked
  • Replies 4
  • Subscribers 165
  • Views 14244
  • 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

How to force annotate to increment only the two last numbers of a component

Daniel Tormo

Hello,

I am using Allegro Design Entry HDL version 17.2-2016.

We have a pretty big design (42 pages), and we have a company directive that says to set the numbering of each component to 4 numbers, the first two numbers corresponding to the page number.

For example, all resistors of page 6 will start as R06xx, being xx the number of resistor on that page. All capacitors presents in page 15 will start as C15xx, being xx the number of the capacitor on that page.

I am using scripts to reset the LOCATION property to $LOCATION=R? in order to restart the resistor naming (auto property a $LOCATION=R?).

However, is there a way of setting this to, for instance, $LOCATION=R06xx in order to tell Allegro to set only the last two numbers of the component?

Best regards,

Daniel Tormo

Parents
  • Daniel Tormo

    Hello,

    does anyone know if this is possible? Some colleagues told me it is, but they do not know how.

    Thank you,

    Daniel

  • DavidJHutchins
    in reply to Daniel Tormo

    I don't believe the Pacakger-XL allows anything like what you want :(

    I previously developed a tool to do something like this that would generate an was-is list of refdes that could be imported into layout using the 'reftxt' command, which could then be back-annotated to the schematic

Reply
  • DavidJHutchins
    in reply to Daniel Tormo

    I don't believe the Pacakger-XL allows anything like what you want :(

    I previously developed a tool to do something like this that would generate an was-is list of refdes that could be imported into layout using the 'reftxt' command, which could then be back-annotated to the schematic

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.