did u make sure that the Hetero property is proper and equal for all the symbols
Thanks for the response,
The 'hetero' property was equal for each of the 3 symbols. As to whether it was proper or not I do not know?
The most common things that I find wrong with a HETERO type 3 definition:
· Each fracture must have the same properties
· Every single fracture must have every single property value identical unless it is something like PINSWAP that must be different.
· HETERO property must not exceed 255 characters and includes only the symbol name, not its extention. (symname vs. symname.1)
· Minimum required properties: DEVICE, PKG_TYPE, REFDES & HETERO
· Each fracture must have unique pin numbers
The symbols will "live" independantly - each its own ASCII file in a library and are joined by the HETERO property.
Get the symbols to package together before introducing DxDataBook. After you get that working, TechNote mg26021 details two use cases for HETEROs in DxDataBook.
Thanks for the response, this starts to make things clearer for me.
However, I do not know what you mean by "Get the symbols to package together before introducing DxDataBook". Can you expand on this please?
Run the netlister (Tools > PCB Interface) and make sure all the pieces are grouped in the same REFDES.
OK, I see what you mean. The output from ViewPCB create netlist indicates the bits of my symbol have been correctly assigned to the same ref des
So far so good then. How the tool gets this right I do not know. It would help my understanding and ability to fix problems in the future if I had some idea of what was going on in the background here.