Migration Guide to Allegro

Migration Guide for Allegro Platform Products

Issue link: https://resources.pcb.cadence.com/i/1180190

Contents of this Issue

Navigation

Page 79 of 128

Migration Guide for Allegro Platform Products Core Allegro Platform Back-End Products October 2019 80 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. ■ Constraint Manager files are now XML-based and use new extensions. To run validation checks when editing or creating these files, use the new schema (XSD) validation files, which are available at /share/pcb/ consmgr/schemas. ■ Front-end Constraint Manager files, such as .dcf, pstcmdb.dat, pstcmbc.dat, are now single-file databases. On saving a pre-17.x design for the first time, these files will be overwritten with the new single-file databases. ■ The default units of constraint values have been changed to length-based units from time-based units. ■ In 17.x, differential constraints captured in both, the physical, and electrical domains, will now honor values from the following: ❑ Physical domain: if the object is not part of a differential pair ❑ Electrical domain: if the object is part of a differential pair Differential constraints captured in both the physical and electrical domains are as follows: ❍ DIFFP_PRIMARY_GAP ❍ DIFFP_COUPLED_PLUS ❍ DIFFP_COUPLED_MINUS ❍ DIFFP_MIN_SPACE ❍ MIN_LINE_WIDTH ❍ DIFFP_NECK_GAP ❍ MIN_NECK_WIDTH ■ In 17.x, Class-Class and Region-Class-Class objects will no longer inherit constraints from their parent Class objects. ■ The base copy files, which reflect information used in the previous flow, are included in the destination database (schematic or layout). The schematic Constraint Manager File Extension Constraint file .dcfx Technology file .tcfx Customization file .wcfx

Articles in this issue

view archives of Migration Guide to Allegro - Migration Guide for Allegro Platform Products