Now this used to work but there is either a bug or I'm doing something stupid. Please remember there is no need to run ULP's now to import Eagle. Once you have your Eagle part/s in an eagle .lbr file you should be able you simply go to your EasyPC library dialogue and click "Add File" and select the .lbr file for each of the schematic/footprint/component tabs. However every time I now try this now I get an unable to open file error !!!
Can someone else try this please ... WIN7 64 bit
Iain By the way the .lbr files that I am using are downloaded from SnapEDA
I just tried (V22.0.1) what you described and got a similar "Failed to open from file C;|.....\....*.lbr. However, I'm not aware that this method ever worked? I though that you had to import the part in Eagle first and then export to EasyPC? Why not use the new SamacSys component Library Loader feature in V22? (I know it has it's limitations).
Sounds likely that the original LBR file from Snap EDA was not in the newer XML-style file format which is why we couldn't read it until it had been updated through Eagle.
I just wonder why EasyPC went the SamacSys route when SnapEDA already supports Pulsonix and has a much wider range of Components available. Can't be that much difference between the two library systems (probably about the same as between Design Spark & EasyPC?). "Commercial sensitivity" no doubt!
quote:Sounds likely that the original LBR file from Snap EDA was not in the newer XML-style file format which is why we couldn't read it until it had been updated through Eagle.
I'm just trying to import a component from Samacsys (Arduino Nano) and, although there is a directory in the download named Easy PC the component within doesn't import. There is no mention of Easy PC in the pdf file of instructions from the Samacsys website.
Edit to add: OK. The Eagle part imports but is total crap so I'll just make my own. ------------------------------------------------------- Birthdays are good for you: the more you have, the longer you live ... and I've had lots of them so I should know!
Edited by - John Baraclough on 01 Dec 2018 16:15:38
John, I find this all the time ...... the library component just isn’t the way you would like so you end up doing your own. I’ve even found footprints that are just not quite right .... by the time you’ve double checked everything and tweeted them your sometimes better just doing your own from scratch and knowing it’s correct and in the form you prefer.