Author Topic: EAGLE V7 - Beta version available  (Read 5706 times)

0 Members and 1 Guest are viewing this topic.

Offline IanJ

  • Supporter
  • ****
  • Posts: 1060
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
EAGLE V7 - Beta version available
« on: June 17, 2014, 07:05:55 pm »

Note: As further beta's are available see further down this thread.

« Last Edit: July 08, 2014, 04:28:10 pm by IanJ »
Ian Johnston
Manufacturer of the PDVS2 & PDVS2mini

Offline IanJ

  • Supporter
  • ****
  • Posts: 1060
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
Re: EAGLE V7 - first beta version available
« Reply #1 on: June 17, 2014, 07:17:31 pm »

Update from Version 6 to Version 7

If a version 6 drawing is edited in version 7 and the new autorouter or
hierarchical design are not used, the drawing remains down compatible to version 6.
If these features are used this compatibility is lost once a drawing is saved.
For this we recommend to make backup copies before editing version 6 drawing files
in version 7.

Release notes for EAGLE 6.91.1

* Hierarchical design:

  - General:
    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
    and IC201).
    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
    properties dialog.
  - 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.
    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 delivers only the parts on schematic main level).

* Autorouter:

  - 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.
    In particular:
     - 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.

* 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
     - 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.
  - Installation:
     - 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
             http://<server name>:8090
          as adress, where <server name> is the network name or IP adress of the
          server computer.
          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

* Platforms:

  - Official support for MAC OSX 10.9.

* Miscellaneous:

  - EAGLE now has a new set of icons.
  - 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

* Bugfixes:

  - 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
    invalid values.
  - 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
    'Value' field.
  - Fixed context menu entry RATSNEST on polygons.
Ian Johnston
Manufacturer of the PDVS2 & PDVS2mini

Offline Wilksey

  • Super Contributor
  • ***
  • Posts: 1172
Re: EAGLE V7 - first beta version available
« Reply #2 on: June 18, 2014, 11:10:10 am »
Hmm, not boding well, just installed the beta and selected free and the beta test license and each time it says "Inconsistent License Data Code 110" and will not run!
Anyone else had any issues with this?

Offline theatrus

  • Frequent Contributor
  • **
  • Posts: 346
  • Country: us
Re: EAGLE V7 - first beta version available
« Reply #3 on: June 19, 2014, 01:02:45 am »
Licensing changes are obnoxious.  |O
Software by day, hardware by night;

Offline Wilksey

  • Super Contributor
  • ***
  • Posts: 1172
Re: EAGLE V7 - first beta version available
« Reply #4 on: June 19, 2014, 11:25:18 am »
All they have done is rip out their old license system and replaced it with FlexLM.

I still can't get the bloody thing to run!

Offline IanJ

  • Supporter
  • ****
  • Posts: 1060
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
Re: EAGLE V7 - first beta version available
« Reply #5 on: June 19, 2014, 04:05:08 pm »
Running fine here (64-bit Win7).

You aren't running any other Flex licensed software are you.............just thinking if maybe you already have drivers loaded or something.

Ian Johnston
Manufacturer of the PDVS2 & PDVS2mini

Offline Wilksey

  • Super Contributor
  • ***
  • Posts: 1172
Re: EAGLE V7 - first beta version available
« Reply #6 on: June 20, 2014, 12:27:22 pm »
Hi Ian,

Probably, but that shouldn't matter! If I am, they all run fine!

Offline IanJ

  • Supporter
  • ****
  • Posts: 1060
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
Re: EAGLE V7 - first beta version available
« Reply #7 on: July 08, 2014, 04:26:55 pm »

The 2nd beta of V7 is now available. V6.91.2

The only differences in the update file I can see are:-

* Miscellaneous
  - The new IDF export (implemented as ULP) is available as entry 'IDF' under
    'Export' of the board editor's pulldown menu.

* Bugfixes
  - Fixed the wrong position of element attributes in newly generated boards
    after initial display.

Ian Johnston
Manufacturer of the PDVS2 & PDVS2mini

Offline Wilksey

  • Super Contributor
  • ***
  • Posts: 1172
Re: EAGLE V7 - Beta version available
« Reply #8 on: July 15, 2014, 07:56:21 pm »
Well, wonders will never, I actually managed to install the freeware version of 7.0.0 WITHOUT any "license" issues!!
They seem to have changed the icons, that's about as far as i've explored so far.

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo