![]() |
![]() |
Custom Output For Allegro |
Post Reply ![]() |
Author | |
mahmoodv99 ![]() Advanced User ![]() Joined: 16 Jan 2016 Status: Offline Points: 93 |
![]() ![]() ![]() ![]() ![]() Posted: 10 May 2016 at 10:29pm |
Add option to include/exclude unwanted layers from output file such as -
|
|
![]() |
|
![]() |
|
chrisa_pcb ![]() Moderator Group ![]() ![]() Joined: 29 Jul 2012 Location: San Diego Status: Offline Points: 772 |
![]() ![]() ![]() ![]() ![]() |
Hmm.. i'll consider it. How critical is this feature and what is the typical usage of when it is needed?
|
|
![]() |
|
mahmoodv99 ![]() Advanced User ![]() Joined: 16 Jan 2016 Status: Offline Points: 93 |
![]() ![]() ![]() ![]() ![]() |
We are not using DEV TYPE and DFA BOUND TOP. So if you add option to exclude this, we can reduce our QA procedure for footprint verification.
|
|
![]() |
|
GrungyRemnant ![]() Advanced User ![]() Joined: 17 Oct 2013 Status: Offline Points: 91 |
![]() ![]() ![]() ![]() ![]() |
You should consider using SKILL to do any customization that you would like.
We don't run the scripts generated by the wizard directly. They are all run though a SKILL routine where we customize the features to suit our needs. For example making the Place_Bound_Top match the physical size of the component, create a DFA_BOUND_TOP shape to be more useful when using the DFA Constraints, or automatically assigning the DFA_DEV_CLASS to company approved values base on the footprint name/size. The options are endless. I think its the best way to handle this for any company's unique requirements. Regards, Chris |
|
![]() |
Post Reply ![]() |
|
Tweet |
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |