Are the libraries posted online compatible with versions 4.1 and 5?
Are the libraries posted online compatible with versions 4.1 and 5?
On 2008/Jun/21 4:31 PM, in article g3jofb$f4$1@cheetah.cadsoft.de, "Talal
Itani" <titani@verizon.net> wrote:
Are the libraries posted online compatible with versions 4.1 and 5?
All libraries are readable with the latest version of EAGLE, in this case 5.
EAGLE 4.1 would only be able to read libraries that were posted with EAGLE
4.1 or before. The descriptions do not generally include this information
so its a bit hit or miss from my experience. You could sort of tell from
the date posted, but that's not 100%.
Cheers,
James.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ ~
~ James Morrison ~~~ Stratford Digital ~
~ ~
~ email: sales@eagletoolkit.com ~
~ fax: 888.701.8097 ~
~ web: http://www.eagletoolkit.com ~
~ ~
~ Online EAGLE Dealer for US and Canada ~
~ EAGLE Design Experts ~
~ EAGLE Enterprise Toolkit ~
~ ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On 2008/Jun/21 4:31 PM, in article g3jofb$f4$1@cheetah.cadsoft.de, "Talal
Itani" <titani@verizon.net> wrote:
Are the libraries posted online compatible with versions 4.1 and 5?
BTW, only post to one newsgroup. I didn't see the cross-posting until my
response showed up in both.
Cheers,
James.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ ~
~ James Morrison ~~~ Stratford Digital ~
~ ~
~ email: sales@eagletoolkit.com ~
~ fax: 888.701.8097 ~
~ web: http://www.eagletoolkit.com ~
~ ~
~ Online EAGLE Dealer for US and Canada ~
~ EAGLE Design Experts ~
~ EAGLE Enterprise Toolkit ~
~ ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Talal Itani wrote:
Are the libraries posted online compatible with versions 4.1 and 5?
As I understand it the library format is different between the two.
Version 5.0 can read the old and the new format, V4.x only the old format.
In practice, if you create an object with V4.x it will be usable with
both versions. If you create it with V5 it will be available only to
version 5 users.
Markus
Hello,
Is there a method for converting newer libraries to older versions? Maybe a
utility or a copy and paste method?
Thanks for any help,
Charlie
"James Morrison" <spam2@stratforddigital.ca> wrote in message
news:C482E41F.61A1C%spam2@stratforddigital.ca...
On 2008/Jun/21 4:31 PM, in article g3jofb$f4$1@cheetah.cadsoft.de, "Talal
Itani" <titani@verizon.net> wrote:
Are the libraries posted online compatible with versions 4.1 and 5?
All libraries are readable with the latest version of EAGLE, in this case
5.
EAGLE 4.1 would only be able to read libraries that were posted with EAGLE
4.1 or before. The descriptions do not generally include this information
so its a bit hit or miss from my experience. You could sort of tell from
the date posted, but that's not 100%.
Cheers,
James.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ ~
~ James Morrison ~~~ Stratford Digital ~
~ ~
~ email: sales@eagletoolkit.com ~
~ fax: 888.701.8097 ~
~ web: http://www.eagletoolkit.com ~
~ ~
~ Online EAGLE Dealer for US and Canada ~
~ EAGLE Design Experts ~
~ EAGLE Enterprise Toolkit ~
~ ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'm also looking for a utility or a way to convert back from 5.x to
4.1x, something that runs on OS X would be nice...
I was testing the freeware version of 5.1, evaluating it under OS X and
I loaded my custom 4.16 library into 5.1 and must have hit save and now
4.16 won't load the library any more...
Anyone know how to get out of this mess other than by upgrading or
recreating all the footprints??
On 2008-07-15 01:21:55 +0930, "Jim Bob" <cdblues2000@yahoo.com> said:
Hello,
Is there a method for converting newer libraries to older versions? Maybe a
utility or a copy and paste method?
Thanks for any help,
Charlie
"James Morrison" <spam2@stratforddigital.ca> wrote in message
news:C482E41F.61A1C%spam2@stratforddigital.ca...
On 2008/Jun/21 4:31 PM, in article g3jofb$f4$1@cheetah.cadsoft.de, "Talal
Itani" <titani@verizon.net> wrote:
Are the libraries posted online compatible with versions 4.1 and 5?
All libraries are readable with the latest version of EAGLE, in this case
5.
EAGLE 4.1 would only be able to read libraries that were posted with EAGLE
4.1 or before. The descriptions do not generally include this information
so its a bit hit or miss from my experience. You could sort of tell from
the date posted, but that's not 100%.
Cheers,
James.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ ~
~ James Morrison ~~~ Stratford Digital ~
~ ~
~ email: sales@eagletoolkit.com ~
~ fax: 888.701.8097 ~
~ web: http://www.eagletoolkit.com ~
~ ~
~ Online EAGLE Dealer for US and Canada ~
~ EAGLE Design Experts ~
~ EAGLE Enterprise Toolkit ~
~ ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Armitage wrote:
I'm also looking for a utility or a way to convert back from 5.x to
4.1x, something that runs on OS X would be nice...
I was testing the freeware version of 5.1, evaluating it under OS X and
I loaded my custom 4.16 library into 5.1 and must have hit save and now
4.16 won't load the library any more...
Anyone know how to get out of this mess other than by upgrading or
recreating all the footprints??
Somehow my first post vanished while typing, sorry if it shows up as well.
Anyhow, try this: Place all the parts from your custom library onto a
schematic, store in 4.1-compatible (I sure hope 5.0 can do this ...),
open in 4.1, then execute the ULP that creates a custom library from all
the parts used in that schematic. IIRC the ULP is called somethin g like
exp-project-lbr.ulp
Now rename that library to what it used to be. Oh, and this time maybe
run a backup before trying any file shuffling
--
Regards, Joerg
http://www.analogconsultants.com/
Tom Armitage wrote:
I'm also looking for a utility or a way to convert back from 5.x to
4.1x, something that runs on OS X would be nice...
I was testing the freeware version of 5.1, evaluating it under OS X and
I loaded my custom 4.16 library into 5.1 and must have hit save and now
4.16 won't load the library any more...
Anyone know how to get out of this mess other than by upgrading or
recreating all the footprints??
One more hint, from Lewin on the embedded NG: See if Eagle didn't write
*.l#n backup libraries when you accidentally saved. The old one might
still be among those.
--
Regards, Joerg
http://www.analogconsultants.com/
On 2008-09-01 10:30:55 +0930, Joerg
<notthisjoergsch@removethispacbell.net> said:
Tom Armitage wrote:
I'm also looking for a utility or a way to convert back from 5.x to
4.1x, something that runs on OS X would be nice...
I was testing the freeware version of 5.1, evaluating it under OS X and
I loaded my custom 4.16 library into 5.1 and must have hit save and now
4.16 won't load the library any more...
Anyone know how to get out of this mess other than by upgrading or
recreating all the footprints??
One more hint, from Lewin on the embedded NG: See if Eagle didn't write
*.l#n backup libraries when you accidentally saved. The old one might
still be among those.
Thanks for the ideas but they didn't work for me.
1) Eagle 5.x doesn't seem to have the facility to save schematics in
the old format (at least I couldn't find how to do it) sinking your
first idea
2) None of the backup libraries (*.l#n files) survived either, I guess
I am just a nervous saver and have gotten into the habit of saving
often whether I need to or not!
Normally this stops you from getting into trouble with corrupted files!
An upgrade it is then for me.....
A note to CadSoft - it might have been nice to have a message box flash
up warning the user about incompatibility issues when saving a
schematic/board/library generated from an old version within the new
version of EAGLE....
Tom Armitage wrote:
On 2008-09-01 10:30:55 +0930, Joerg
<notthisjoergsch@removethispacbell.net> said:
Tom Armitage wrote:
I'm also looking for a utility or a way to convert back from 5.x to
4.1x, something that runs on OS X would be nice...
I was testing the freeware version of 5.1, evaluating it under OS X
and I loaded my custom 4.16 library into 5.1 and must have hit save
and now 4.16 won't load the library any more...
Anyone know how to get out of this mess other than by upgrading or
recreating all the footprints??
One more hint, from Lewin on the embedded NG: See if Eagle didn't
write *.l#n backup libraries when you accidentally saved. The old one
might still be among those.
Thanks for the ideas but they didn't work for me.
1) Eagle 5.x doesn't seem to have the facility to save schematics in the
old format (at least I couldn't find how to do it) sinking your first idea
2) None of the backup libraries (*.l#n files) survived either, I guess
I am just a nervous saver and have gotten into the habit of saving often
whether I need to or not!
Normally this stops you from getting into trouble with corrupted files!
An upgrade it is then for me.....
A note to CadSoft - it might have been nice to have a message box flash
up warning the user about incompatibility issues when saving a
schematic/board/library generated from an old version within the new
version of EAGLE....
If you want to avoid the upgrade (personally I'm not convinced about v5 yet)
then if you have v4 designs that use your custom libs then you can at least
extract part of your library from these designs using the exp-project-lbr
ulp. Depending on how extensive your lib was this may be a route to
recovering most of it.
cheers
David