![]() ![]() ![]() This would be what I would try if I were you, though - place those attributes into the footprint file, along with the attributes that ACADE wants it to have (like PTAG, etc). But, I can't say if that works for just any attribute. I know that some users have added the RATING1 attribute to their circuit breaker footprints, and that ACADE pushes the value held for that attribute in the schematic, into its correlating footprint. However, if those attributes already exist in the block file, that step is just skipped over. For instance, a terminal will get different attributes than DIN rail. These attribute insertions are controlled by the component family of the schematic symbol. From there, it will insert what it needs to ensure the footprint's function in the software. ![]() When you insert a footprint, ACADE evaluates the block file to see what attributes it contains. Because of this, ACADE by default keeps 'blank' footprints (meaning, no attributes) that will have the proper attributes inserted by the software. What those attributes are, depends on the nature of the component represented by the footprint. In order for a footprint to function normally, it requires certain attributes. Normal footprint insertion behavior in ACADE: The vast majority of footprints don't hold attributes in their block files by design, ACADE inserts those at insertion time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |