Custom Output For Allegro

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Add option to include/exclude unwanted layers  from output file such as - 
DFA BOUND TOP
DEV TYPE
ASSEMBLY BOTTOM
etc.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
mahmoodv99 Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 16 Jan 2016 Status: Offline Points: 93	Post Options Post Reply Quote mahmoodv99 Report Post Thanks(0) Quote Reply Topic: Custom Output For Allegro Posted: 10 May 2016 at 10:29pm
	Add option to include/exclude unwanted layers from output file such as - DFA BOUND TOP DEV TYPE ASSEMBLY BOTTOM etc.



chrisa_pcb Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 29 Jul 2012 Location: San Diego Status: Offline Points: 772	Post Options Post Reply Quote chrisa_pcb Report Post Thanks(1) Quote Reply Posted: 11 May 2016 at 9:35am
	Hmm.. i'll consider it. How critical is this feature and what is the typical usage of when it is needed?

mahmoodv99 Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 16 Jan 2016 Status: Offline Points: 93	Post Options Post Reply Quote mahmoodv99 Report Post Thanks(0) Quote Reply Posted: 11 May 2016 at 8:43pm
	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 Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 17 Oct 2013 Status: Offline Points: 91	Post Options Post Reply Quote GrungyRemnant Report Post Thanks(0) Quote Reply Posted: 19 May 2016 at 7:12am
	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