Home » CadSoft Support Forums » eagle.announce.eng » EAGLE version 7.0 released!
|EAGLE version 7.0 released! [message #156307]
||Mon, 14 July 2014 18:13
Registered: August 2010
A new major version of EAGLE is now available for download at|
The changes since the previous version 6.6 are:
* Hierarchical design:
Since version 7, an EAGLE schematic can be designed and organized using
schematic subunits called 'modules'. They can be created by the new command
MODULE and then be edited like schematic sheets.
With the MODULE command a module can be used in the normal schematic
by creating a 'module instance', a simple symbol representing the module.
With the new command PORT it is possible to create interfaces from nets
inside the module to the upper schematic level.
Ports are attached to module instances and can be connected with nets
just like pins of a part instance.
Beside nets, also simple types of busses can be exported this way.
Modules can be used multiple times by creating multiple module instances.
Modules can also contain module instances of other modules. This way,
an arbitrary depth of the hierarchy is possible.
The board creation from the schematic produces a similar result as if the
design was made without hierarchies.
For syntax and behaviour of MODULE and PORT see our online help.
- Naming rules and mechanism:
Special naming rules are used to identify the elements and nets of a module
instantiation. Each module has it's own namespace:
Part IC1 may exist in module ModX and another part IC1 in module ModY.
If used in a schematic (by 2 different module instances) the corresponding
elements in the board are identified using the module instance name as prefix
and ':' as separator or by adding a module instance specific offset to the
index in the name (e.g. with offset 100 and 200 the element names are IC101
The offset can only be used for module instances on schematic main level
and only for parts and their elements. For parts from deeper levels and for
nets the prefix notation is always used.
- Assembly variants for modules, adaption for boards:
Within modules, assembly variants can be defined just like in version 6 for a
whole schematic. Module assembly variants are limited to the module parts.
Module assembly variants can be used via the module instance(s). For each
module instance a specific module assembly variant can be selected (see the
MODULE command for details). There is no direct switching between assembly
variants in a module, but the element's value, populate state and attributes
in the board are set following the chosen variant in the corresponding module
If used on schematic main level, the VARIANT command works for the parts on
main level like in version 6.
The assembly variant definitions are now kept only in the schematic.
For standalone boards, variants are no longer supported, but it's possible
to set the populate states of elements with the CHANGE command or in the
- Modules can have descriptions that can be edited with the DESCRIPTION command.
Module sheets can have descriptions just like other sheets.
- The EDIT command has been extended to edit and move module sheets.
The editor's sheet combobox additionally contains all module sheets.
- The REMOVE command allows removing individual module sheets or complete modules.
- The RENAME command supports renaming of modules.
- Description, renaming of modules, moving of module sheets (also across modules
or from/to main schematic), removing of sheets and modules is also available
in the sheet thumbnails. A property dialog for modules can be opened via
the context menu for module sheets.
For details on the command extensions of DESCRIPTION, EDIT, REMOVE and RENAME
see the online help.
- If a board is created from a hierarchical schematic the elements are grouped
by their module instance inheritance.
- For module instances the SHOW command highlights all elements and signals
generated via this module instance.
For parts in a module the SHOW command highlights all related elements
according to the instantiations of the module in the hierarchy.
- In order to avoid inconsistencies between a part and it's elements or between
a net and it's signals in a hierarchical design, several commands cannot be
executed in the board and have to be done for the correponding part or net
to be annotated to the elements or signals it relates to. Among others NAME
and VALUE are such comands.
This limitation is only for entities within a hierarchy and if there is
- The EXPORT command for partlists, netlists, pinlists and netscripts has been
extended to export hierarchical structures.
- The PRINT command has been extended to print in a hierarchical way, meaning
that the sheets of a module are printed for each use in a module instance
with the according part names, net names and assembly variant.
- User Language:
The new object types UL_MODULE, UL_MODULEINST, UL_PORT and UL_PORTREF have
been introduced to access modules, module instances, ports and port references
within a schematic.
The schematic's modules can be accessed with UL_SCHEMATIC.modules(),
the module instances on a sheet with UL_SHEET.moduleinsts(),
the ports of a module with UL_MODULE.ports() and a net's port references with
UL_NET.portrefs() resp. UL_SEGMENT.portrefs().
The new loop member UL_SCHEMATIC.allparts() delivers all parts including
"virtual" parts generated by module instantiations (the existing
UL_SCHEMATIC.parts() delivers only the parts on schematic main level).
- Multiple variants:
EAGLE's autorouter now supports multithreaded calculation of variants using
multiple core processors. The autorouter dialog has been split up into an
initial main dialog for general settings and a routing variant dialog to
adjust and monitor individual variants.
The parameters in the main dialog determine how many variants are generated
and which concrete parameters they use.
- With 'Effort' (low, medium or high) it can be determined how many variants
will be calculated.
- With 'Auto grid selection' on, the autorouter uses it's own heuristics to
determine grids for the routing variants. If it is off, the user can set
a fix grid to be used for all variants.
- For each of the signal layers a preferred direction can be defined as well
for all variants. With the new setting 'Auto' the autorouter will try several
combinations on it's own.
- The number of simultaneously running variants can also be limited.
With the 'Continue' button a number of variant parameter sets are calculated
and the routing variant dialog appears. It allows to adjust the
parameter set for each variant or to add or delete variants in a list.
Each parameter set is like the set of autorouter parameters known from
previous EAGLE versions.
The variant calculation can be started from this dialog.
With the variant list in the dialog it's possible to step through the
variants and watch the routing progress like in prior EAGLE versions.
Once finished, the user can decide directly which variant to keep and end
the job or keep the variant results for later evaluation.
If cancelled, the job can also be continued later.
It is possible to save and load the parameters defined in the main dialog
in a control (ctl) file. The parameter set of an individual variant can
also be saved and loaded as a control file. It is compatible to prior EAGLE
- New routing algorithm ('TopRouter'):
In the autorouter main dialog there's also an option to add a 'TopRouter'
variant which is using a new routing algorithm based on a gridless and
topological approach. This algorithm creates a sketch of the routed signals
and then uses EAGLE's traditional autorouter optimization steps to fulfill
the Design Rules.
In the average the TopRouter produces considerably less vias than the
traditional approach. The user can run a job with variants for both and
decide later which of the variants he prefers.
- New model:
- The EAGLE licensing model and mechanism has been replaced by a new solution
based on Flexera FlexNet Licensing. Flexera is a software specialist for
licensing solutions (see www.flexerasoftware.com).
- The licenses are either node-locked or floating licenses:
Node-locked means that the license is bound to one or more computers,
floating means that a license server is involved on a server computer.
Licenses can be used by any client computer that has a connection to the
server computer. When EAGLE is started from a client installation,
EAGLE contacts the license server and checks out a license.
The license server takes care that not more users than the number of seats,
for which the license is valid, can use the license simultaneously.
When an EAGLE client stops his session the license is automatically returned
to the license server and is free for other users.
- All EAGLE multi user licenses are floating licenses now, all single user
licenses are node-locked licenses that can be used on two different computers.
- Like in prior EAGLE versions, each license is issued as a license file.
- The Freeware and Freemium license models will not change.
- The new licenses are not back compatible to be used for older EAGLE versions.
- Ordering, HostIDs:
- For ordering a license, the HostID(s) of the computer(s) need to be provided.
The HostIDs are unique computer identifiers.
For multi user licenses the HostID of the server computer is necessary.
Together with the other licensee information, CadSoft can create a license
and provide it for download.
- The HostID can be retrieved in 2 ways:
- Download and execute the tool 'lichostid' that is available on our website.
- If the user has already EAGLE installed on his computer he can run it as
freeware. In the EAGLE licensing dialog the HostID is displayed.
There is also a link to our online shop that transfers it.
It can then be used for ordering a license.
- An installation code is no longer necessary.
- Single user:
To license a single user EAGLE installation, it's only necessary to provide
the license file via the licensing dialog.
- Multi user:
- Server side:
A license server package is necessary and can be
downloaded from CadSoft's download page. There are 3 packages for the 3
different platforms Windows, Linux and MAC. It depends on the server com-
puter's operating system. After downloading and unzipping this package,
the license server which is the executable 'lmadmin', needs to be started.
Once it runs, there's a web interface for accessing the license server.
It can be accessed in a web browser by entering
as adress, where <server name> is the network name or IP adress of the
With the web interface the license file can be imported by the server.
- Client side:
For any client installation only the license server name needs to be
provided via the EAGLE licensing dialog. EAGLE remembers the server name
for future sessions.
- Further details on our new licensing can be found in the manual and on our
- Official support for MAC OSX 10.9.
- On Windows the default installation path in the setup dialog has been changed
from the Windows program folder to
C:\EAGLE-<version> (<version> being the full EAGLE version string).
Also an early check is done whether the user rights (in particular regarding
registry entries) are sufficient for the installation with appropriate messaging.
- EAGLE now has a new set of icons. With the Options/User Interface dialog it
can be switched between the new and the classic EAGLE icon set.
- The new option MERGE in the DRC command can be used to merge additional
Design Rule parameters to the active Design Rules in the board drawing.
- Now the arrows of DIMENSIONs end at the center of the extension lines.
- Now changing of a MITER is only possible if the adjacent wires are equal
in width, style and layer.
- In the attributes dialog of devices and in the UPDATE dialog for selection
of a new technology the sorting of technologies has been changed to
- The new IDF export (implemented as ULP) is available as entry 'IDF' under
'Export' of the board editor's pulldown menu.
- eagle.scr: Added units inch to some settings to avoid a possible wrong
- Added sample 'ti-launchpad' from Texas Instruments to the EAGLE
- Now the origins of not populated elements are visible again if the regarding
layer is active.
- Fixed removing an assembly variant from a part (by choosing the default values)
on the currently selected assembly variant.
- Fixed proper restore of the current value in parameter comboboxes after
- Fixed mirroring polygons in signal layers during COPY.
- Fixed Default button in the GRID dialog (in schematic context the value
is now again 0.1 inch).
- Prohibition to use board layers in schematics.
- The properties dialog of labels does no longer contain an unintended
- Fixed context menu entry RATSNEST on polygons.
- Fixed the wrong position of element attributes in newly generated boards
after initial display.
CadSoft Computer GmbH
Registergericht: Amtsgericht Traunstein HRB 5573
Geschäftsführer: Thomas Liratsch
|Re: EAGLE version 7.0 released! [message #156314 is a reply to message #156307]
||Tue, 15 July 2014 02:52
Registered: March 2009
On 07/14/2014 02:13 PM, Walter Spermann wrote:|
> A new major version of EAGLE is now available for download at
> The changes since the previous version 6.6 are:
> * Hierarchical design:
Yay! At last! Shame I won't get to use it, because...
> * Licensing:
> - New model:
> - The EAGLE licensing model and mechanism has been replaced by a new solution
> based on Flexera FlexNet Licensing. Flexera is a software specialist for
> licensing solutions (see www.flexerasoftware.com).
> - The licenses are either node-locked or floating licenses:
So when I upgrade my computer, I have to get permission from the gods to
run software I've already paid for? I've been down that road with other
products, and it's a royal pain. No thanks, I'll pass.
I guess it's finally time to make the switch to KiCad.
|Re: EAGLE version 7.0 released! [message #156337 is a reply to message #156307]
||Tue, 15 July 2014 12:32
Registered: December 2009
Walter Spermann wrote on Mon, 14 July 2014 14:13|
* Hierarchical design:
Excellent. This has been a long time coming.
However, I don't see any mention of the two other important features that have made it not worth updating from version 5 yet. These are some say to define "sub-nets" in the schematic or a more native understanding of "shorts" we currently use to get around that, and a means to tell Eagle that everything within a package is OK, and to not generate tons of nuisance DRC errors due to overlaps, abutting pads, and the like.
Perhaps there is some improvement here. However, the existing auto-router works pretty well. It seems that most people don't know how to use it properly, and therefore don't get good results and end up complaining, but it's actually a pretty decent tool in ver 5. This is a documentation issue, not a code issue.
My biggest issue with the autorouter is when making 2 layer boards where the bottom layer is a ground plane to the extent possible. I can set the cost for routing in that layer high, and that does keep traces off that layer. But, the vias and traces produced that way tend to be clumped, even when the hugging parameter is set to 0. The metric of how much a ground plane is broken up is not the number of islands, but the maximum dimension of any island. 5 jumper traces all in a clump is therefore worse than the same 5 jumpers spread out from each other so that the ground plane can flow around them.
All EAGLE multi user licenses are floating licenses now, all single user licenses are node-locked licenses that can be used on two different computers.
I understand you want to avoid fraud, but this is no way to treat your honest customers. We have three full licences here, although Eagle is installed on more than three computers. For example, I have Eagle on my main computer here at work, on my home computer (I work from there sometimes), and on a floating laptop. Those are all three "my" machines, and Eagle is never run simulataneously on any of those three. These three machines are in different locations, and the laptop is what I bring to customer sites. It is unreasonable to require separate node-locked licences for these three machines, and I certainly don't want the unreliability and sometimes the outright impossibility of having to connect to a license server.
A license server just adds another layer of administration hassle and inevitable wasted time when things don't go right. That will eventually happen on a weekend when I try to get a high priority project done for a customer by Monday morning. I've dealt with license servers before. It might sound like a nice concept, but things don't always go right. What a pain. No thanks. I want everything local on my machine so that I don't have to rely on the network or anything else.
The node-locked license brings up other questions. What happens when I upgrade a machine? Can I contact you and have you move my license from the old machine to the new? If you don't trust me in the first place, how are you going to trust me that the old machine really is being retired and I'm not just trying to get a free license on a additional machine?
If you really believe you were being substantially ripped off before, then you should be able to make the new node-locked licenses much cheaper than the previous ones. If node-locked really is cheaper than before, then I can kindof see the point.
All around, as a long-time customer of Eagle, this leaves a bad taste in my mouth.
|Re: EAGLE version 7.0 released! [message #156541 is a reply to message #156314]
||Tue, 22 July 2014 17:40
Registered: March 2007
Reece R. Pollack wrote:|
> So when I upgrade my computer, I have to get permission from the gods to
> run software I've already paid for? I've been down that road with other
> products, and it's a royal pain. No thanks, I'll pass.
At least on Linux, it seems to be enough to change the MAC address of
your new computer to be same as on your previous computer. It seems to
use first wire inbterface, normally eth0. So you should also store
output of ifconfig for later use.
|Re: EAGLE version 7.0 released! [message #156545 is a reply to message #156541]
||Tue, 22 July 2014 18:33
Registered: July 2013
> At least on Linux, it seems to be enough to change the MAC address
> your new computer to be same as on your previous computer. It seems
> use first wire inbterface, normally eth0. So you should also store
> output of ifconfig for later use.
Are you sure that the hostID will be 'only' dependent of hardware ?
That's the question I ask 2 days ago on the 'support (English)' forum.
I don't care is it's only based on the MAC address. I just want to be
sure that I would not have to beg a new license each time I upgrade my
linux (when I says upgrade is I re-install the OS, I just keep the
To view any images and attachments in this post, visit:
|Re: EAGLE version 7.0 released! [message #156786 is a reply to message #156785]
||Mon, 04 August 2014 09:54
Registered: July 2013
I had a response from Jorge Garcia, have a look at
This post was about the possibility of server license for 1 user only,
but you there is an answer to your question: you can contact Cadsoft and
they will proceed a new license. Of course, they will probably not, if
you ask 3 new license every month !!!
Jorge also confirms that hostid is hardware dependent, and don't depend
on OS, see
(/thread/36629/l/hostid-is-hardware-dependant-only) . I bought the
update, and I can confirm that is not OS dependent since I get the same
ID with Linux and XP (on my laptop I have a dual boot.) So it will not
change with OS or drivers updates.
I think that host ID will depend on the serial of the main part of the
To view any images and attachments in this post, visit:
Current Time: Mon Apr 24 09:27:31 GMT 2017