Home > Community > Blogs > PCB Design > what s good about allegro pcb editor ecsets and ref des values 16 6 has a few new enhancements
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the PCB Design blog (individual posts).


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

What's Good About Allegro PCB Editor ECSets and Ref Des Values? 16.6 Has a Few New Enhancements!

Comments(0)Filed under: PCB design, SPB, Allegro PCB Editor, Constraint Manager, PCB Editor, PCB, design, Constraint-driven PCB Design flow, Grzenia, Allegro 16.6, 16.6, constraints, Cadence, Cadence Design Systems, electronics design

Beginning with the 16.6 Allegro PCB Editor, the environment variable UPDATE_ECSET_REFDES is now the default behavior.

Read on for more details …

Most Electrical Constraint Sets (ECSets) will map based on Reference Designator (RefDes) values. It is sometimes the only thing that is unique for pins in a topology:

In this picture, U21 and U44 have the same SI model and the same pin use. So the only way to differentiate them is by RefDes.

This topology may not map the same way if the design is re-sequenced (RefDes re-numbering). The RefDes renaming can be an automatic process for the whole design or done manually for one component.

In order to address this, the environment variable UPDATE_ECSET_REFDES is made the default behavior. It will change the RefDes in all ECSets based on updates in the design.

For example if U21 is renamed to A-1 in the .brd file, the same will happen to any instance of U21 in the ECSets contained in the .brd.

A new variable, NO_UPDATE_ECSET_REFDES, is added in the 16.6 release to disable the feature described above.
The variable NO_UPDATE_ECSET_REFDES  can be added either at the Allegro command line or in your local env file.


Please share your usage of this capability.

Jerry “GenPart” Grzenia


Leave a Comment

E-mail (will not be published)
 I have read and agree to the Terms of use and Community 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.