Cadence PCB Best Practices

Electrical and Mechanical Design Incremental Data Exchange

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

Contents of this Issue

Navigation

Page 14 of 27

Electrical Design, Mechanical Design Incremental Data Exchange in Allegro PCB Editor October 2019 15 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. IDX Data The Baseline File When a baseline is established from the Allegro PCB Editor, or imported into Allegro PCB Editor, the data defined as baseline is attached to the Allegro drawing. This baseline is referenced each time an IDX import or export is run. When exporting a proposed change, the current data in the design drawing is compared to the baseline. If new object is added, or an existing object is changed when compared to the baseline, those objects are listed in the export GUI. As objects are imported or selected for exported IDX specific properties are used to maintain a transaction history of that object. For detailed information on IDX properties, see IDX Properties. When Allegro PCB Editor is used to initiate a baseline or propose a change to the MCAD tool, it is required that the transaction file created by the MCAD tool be imported when no new proposals are returned. It is not required to import the transaction file if counter-proposals are passed as incremental changes, as the current status of the preceding proposed changes are contained within the incremental file. Incremental Files Incremental files contain the changes to a design after comparison with the baseline. The items exported from Allegro PCB Editor are selected by the Allegro PCB designer in the export GUI. The incremental file may contain new objects, changed objects, deleted objects, and previous transaction status when applicable. When Allegro PCB Editor exports incremental data, an increment value will be embedded into the exported file name. Transaction Files The Transaction file records all actions taken during the Allegro/MCAD data exchange process. As each incremental file is imported, the status or action taken on each item in the proposals is recorded into the transaction file as well. In a sense, a transaction history is being kept throughout the exchange process. When Allegro initiates a baseline or proposes a change to the MCAD tool, it is required that the transaction file created by the MCAD tool be imported when no new proposals are returned. It is not required to import the transaction file if counter-proposals are passed as incremental changes as the current status of the preceding proposed changes are contained within the incremental file.

Articles in this issue

view archives of Cadence PCB Best Practices - Electrical and Mechanical Design Incremental Data Exchange