Improper import of schematic symbol or footprint from Ultra Librarian - Page 1
Forum section: electronics / general

author: logancane
author_rank: Regular Contributor
timestamp: August 07, 2021, 11:25:10 am
content: Hi everyone,I'm just wondering if anyone else comes across the same problem that I do on a very regular basis.So what I'll do is1. Download a symbol and footprint package from Ultra Librarian for Altium2. Extract the contents of the zip folder into their own folder,3. Go into Altium and run the script,4. Select the text file and press import5. Get a message saying something about this version does not support some kind of text standard (I get this every time whether or not it works so I don't think this is relevent)6. Go to my schematic and add component7. Usually the library is already open so I go to select my symbol so that I can use it in my schematic.But over half of the time when I do this, the schematic symbol hasn't loaded. Instead there is an empty schematic symbol called compoent. Then I'll go into the components .Schlib file and it is empty. Sometimes the .Pcblib file suffers the same fate. (I always double check to make sure that both are supposed to be supplied)The weird thing is that 9/10 times if I repeat the exact same process, it worksBecause of that it is only a mild annoyance but it's happened enough times to me that I want to know why. I did some googling but nothing came up.Has this ever happened to you?

author: AJbotic
author_rank: Newbie
timestamp: January 20, 2022, 01:32:28 am
content: Yes, this happens to me on a regular basis. Next time, instead of reimporting. Close the empty schlib or pcblib, then simply reopen them. This has worked for me every time. I think the files show up in the project panel before they are finished loading, then we double click them too early too. This is just my guess.

author: free_electron
author_rank: Super Contributor
timestamp: January 20, 2022, 06:53:29 pm
content: Your big issue is item 1. using ultralibrarian , snapeda or samasys for anything.Those parts are full of mistakes .seriously ? who makes opamp symbols like that ? this needs to be a 3-part split. what is this ? arduino style schematics ?They are not even trying. this should be arranged properly. inputs left, outputs right , power top , ground bottom. and logically sequenced.This is a disaster of a footprint. the corner pads are too close. all pads are too long , there is silkscreen over copper , the soldermask is too narrow and none of the pads use rounded corners. there is no via farm or windowpane design on the thermal pad.Molex drawingTheir implementation. The anchoring pads orientation is wrong , the pin order is wring and pin 1 sits in the wrong corner ! The symbol is not representative of the actual part and the anchoring pads are not called out. And where is the 3D model ? Molex website has it ... why is it not in there ?There is a very descriptive terminology for this kind of stuff: sheite.

author: AJbotic
author_rank: Newbie
timestamp: January 24, 2022, 11:27:29 pm
content: @free_electron is accurate concerning trustworthiness for all those resources. I've used them all and I've been burned by them all. I don't recommend ignoring them completely though either. Instead I've adjusted my workflow to take what's useful and leave the rest behind. Instead of blindly adding these components to my library, I'll only add the features I want, layer by layer to ensure what I bring in matches my convention, my library layer stack, and the component datasheet. This is (for me) a happy medium WRT time optimization between the two extremes of blind trust in ulltralib/snapeda/samacsys vs. building every component from scratch using the component mechanical drawings and other resources.

author: free_electron
author_rank: Super Contributor
timestamp: January 25, 2022, 12:46:38 am
content: TRY THE CELESTIAL ALTIUM LIBRARY