A new beta version of EAGLE is now available for download.
for details about how to get, install and use it.
In order to enable you to test the advanced features of
this new version, like PASTE from a file with multiple
sheets, there is a limited time Professional license file
contained in bin/betatest.key of your EAGLE installation
directory. The Installation Code is listed inside that file.
The changes since the previous version are:
- Make RUN accept selected object from context menu (identifiable by ingroup()).
- The ROUTE command now supports routing of "Differential Pair" signals.
- The RATSNEST command prefers open wire ends when generating airwires
for Differential Pair signals.
- The maximum number of net classes has been increased to 16.
- SET CONTEXT objecttype text commands enables the definition of
userdefined context menu entries.
- The new command VARIANT can be used to define assembly variants.
Assembly variants define whether a given part is actually populated
on the board, and what value and technology it has (if different from
- You can access assembly variants by opening the dialog under
- If a drawing contains assembly variants, the action toolbar shows a new
combo box that allows you to select one of these variants.
- The VALUE command always changes the value of a part in the currently
selected assembly variant.
- The new User Language objects UL_VARIANTDEFS and UL_VARIANTS, as well as
the new members UL_SCHEMATIC.variantdefs, UL_BOARD.variantdefs,
UL_PART.variants and UL_ELEMENT.variants can be used to access assembly
variants from a User Language Program.
- The new User Language functions setvariant() and variant() can be used
to set and query the current assembly variant.
- The new User Language members UL_PART.populate and UL_ELEMENT.populate
can be used to determine whether a part has to be populated in the
current assembly variant.
- The new placeholder >ASSEMBLY_VARIANT can be used to display the name of
the current assembly variant. ASSEMBLY_VARIANT can therefore no longer be
used as an attribute name.
- The new command line option -A can be used to specify a particular
assembly variant when running the CAM Processor.
- The commands ADD, CHANGE PACKAGE | TECHNOLOGY, REPLACE, UPDATE and VALUE
can only be used if no assembly variant is active.
- The new command MEANDER can be used to balance the lengths of
differential pair signals, or to increase the length of a signal segment
to a given target length.
- Fixed handling ':' in file names under Linux and Mac OS X.
- The netpost() function has a new optional parameter to set the content
type of the posted data.
- The Mac OS X version of EAGLE now requires an Intel Mac. It no longer runs
on PPC machines.
- The reading direction of vertical texts can now be selected from "up"
and "down" in "Options/User interface".
- BGA escape routing solution as a Ulp. Start with 'run route-bga element'.
- Texts can now have one of nine different alignments, consisting of
combinations of left, right, center, top and bottom.
- The new option CHANGE ALIGN can be used to change the alignment of
- The User Language object UL_TEXT now has the new data member 'align'.
- Any wires and polygons in signal layers (1-16) drawn in a package
that are connected to a pad or smd are now considered electrically
connected to that pad/smd. This allows the definition of arbitrary
See "Help/Editor Commands/PAD|SMD/Arbitrary Pad Shapes".
- The 'rank' parameter is now obsolete for polygons in packages.
Package polygons in signal layers that are not connected to a pad/smd will
be handled as if they had a rank of 0.
- The new command DIMENSION can be used to draw dimensions.
See "Help/Editor Commands/DIMENSION".
- The new User Language object UL_DIMENSION can be used to access dimension
- The new option CHANGE DTYPE can be used to change the type of
- The internal resolution of EAGLE has been increased by a factor of 32.
It used to be 0.1 micron and is now 0.003125 micron. This allows drawings
in imperial units to use exact values for multiples of 1/4, 1/8, 1/16,
1/32 and 1/64 mil.
- The maximum drawing area is now 4x4 meters (about 150x150 inch).
- If a User Language Program directly handles coordinates or sizes in
editor units and needs to know the actual value of one editor unit, it
needs to be adjusted to use the new value.
- The new User Language functions inch2u(), mic2u(), mil2u() and mm2u()
can be used to convert the respective units to internal editor units.
- Due to the increased resolution of coordinates, any approved ERC or DRC
errors from older versions can no longer be recognized as such. Therefore,
when you run the ERC/DRC after updating a file to version 6, these errors
will show up again and you may have to approve them again.
- Once you overwrite a project file (eagle.epf) from an older version with
this new version of EAGLE, the dimension values in it will be stored in
a different format. If you then load such a file with an old version of
EAGLE, all menu entries (like wire widths or drill diameters) will fall
back to their default values.
- Fixed handling "\n" in the eaglerc file.
- Multiple pads can now be connected to the same pin.
- If a pin is connected to multiple pads, and the pad name is visible on
the pin, the smallest of all pad names connected to that pin is displayed,
followed by an asterisk ('*') to indicate that there is more than one pad.
- The CONNECT command can now handle several pad names at once, to create
a connection of several pads to one pin.
- The new keywords ALL and ANY in the CONNECT command control whether all
or any of the pads in a multiple pad connection need to be routed in the
- The User Language data member UL_PIN.contact is deprecated, because a pin
can now be connected to multiple pads. It will work for backwards
compatibility and as long as only one pad has been connected to the pin,
but will cause a runtime error when used with a pin that is connected to
more than one pad. Use the new loop member UL_PIN.contacts() instead.
- The new User Language data members UL_PIN.route and UL_CONTACTREF.route
tell whether all or any of the respective contacts need to be routed.
- The new polygon pour style "cutout" can be used to define polygons that
get "subtracted" from all other signal polygons within the same layer.
See "Help/Editor Commands/POLYGON/Polygon cutouts".
- In older versions of EAGLE the COPY command was used solely to copy objects
within a drawing, as opposed to the Windows behavior, where COPY places a
copy of the selected objects (i.e. the GROUP) into the system's clipboard.
As of version 6, EAGLE's COPY command primarily behaves the same way as in
other Windows applications, by putting a copy of the current group into the
clipboard. The original functionality of copying selected objects, or
copying library objects between libraries, is still fully available, which
is especially important to keep existing scripts and ULPs working.
What has also often irritated Windows users is that in EAGLE the CUT
command has only copied the current group to the clipboard, but did not
actually delete the group from the drawing. Since a CUT command that
deletes the group would not be of much use in a board/schematic pair that
is connected via forward-&backannotation, the CUT command has been
removed from the main pulldown menu and the command button toolbar. It is
still fully available from the command line or within scripts. The command
SET Cmd.Copy.ClassicEagleMode 1
restores the old behavior of both the COPY and the CUT command. Note that
this setting only takes effect the next time you open an editor window.
- The PASTE command can now paste a complete consistent board/schematic pair
into the currently edited project. See "Help/Editor Commands/PASTE/Pasting
from a file".
- The EAGLE file format has been changed from binary to XML.
- The complete definition of the EAGLE file format can be found in the
- Existing files will be automatically updated to the new format when
they are saved with version 6.
- The pin direction "I/O" has been changed to "io" (without the slash).
Wherever a pin direction is allowed in command line input, the old value
will still be accepted for compatibility with earlier versions, but in the
XML files only "io" will be used.
- The User Language member function UL_SHEET.parts is deprecated and should
no longer be used. Use the new function UL_SHEET.instances instead.
The old function is still available for compatibility with ULPs written
for older versions.
- Supply layers (i.e. layers with names that start with a '$') are no longer
treated special. Layers for supply signals now need to be realized using
- When a board drawing from an older version of EAGLE is loaded, any supply
layers it contains will be renamed by moving the '$' to the end of the
name. This makes sure automated scripts that treat a supply layer as
"negative" don't make a mistake, while still indicating that layer as
having been a supply layer. The functionality of the supply layer is
replaced by a signal polygon with the proper name, using the minimum wire
width from the net class of that signal. The polygon is drawn into the
former supply layer as a rectangular shape, covering the area defined by
any wires in the Dimension layer, by pads or by vias. The Autorouter setup
is modified in such a way that the layer containing the generated polygon
is activated (with preferred direction '*'), and the costs for that layer
set to 99 in all passes.
After updating a board with supply layers from an older version, make
sure you run the RATSNEST command to verify whether all pads are still
connected to the respective signal.
- The User Language constants PAD_SHAPE_ANNULUS, PAD_SHAPE_THERMAL,
VIA_SHAPE_ANNULUS and VIA_SHAPE_THERMAL are now obsolete.
They are still tolerated for compatibility with old ULPs, but no pad or via
will ever have such a shape.
- The command line options '-a' and '-t' are no longer supported, because
the CAM Processor doesn't use Annulus or Thermal symbols any more.
For compatibility with existing scripts, these options are still
tolerated, but they have no effect.
- The aperture shapes "annulus" and "thermal" are no longer used by the
- Any parameters referring to "Annulus" or "Thermal" have been removed
from the eagle.def file. They are still tolerated when using such a file
from an older version of EAGLE, but they have no effect.
- Most of the parameters related to Thermal and Annulus have been removed
from the "Supply" tab of the Design Rules dialog.
- The AUTO command no longer clears the UNDO buffer (unless an existing job
- The CHANGE command now checks whether the selected object already has the
requested property value, and changes it only if not. This may result in an
actual CHANGE command not generating an UNDO step, because nothing has
changed at all.
- Creating or reordering schematic sheets no longer clears the UNDO buffer.
- Removing a schematic sheet no longer clears the UNDO buffer.
- The GATESWAP command now leaves the 'smashed' property of instances in place.
- Nets now only keep their name in the PASTE command if they have a label
or are connected to a supply pin, and that label or pin is actually in the
group. In V5 this decision was made independent of whether such a label
or pin was actually in the group.
- SET UNDO_LOG ON|OFF is no longer a global setting, but acts only upon the
editor window within which it is executed (in case of a consistent
board/schematic pair it works on the other window as well).
- Fixed updating sheet numbers in the ERRORS dialog when reordering,
inserting or deleting sheets.
- The number of technologies per per device is no longer limited to 254.
- The number of package variants per device set is no longer limited to 254.
- The valid range of values for pin and gate swap levels is no longer
limited to 255.
- Any changes made to the net classes with the CLASS command are now fully
handled by UNDO/REDO.
- Changes to the Design Rules are now fully handled by UNDO/REDO.
- If the ERC establishes consistency between a board and a schematic, it now
stores this fact in the UNDO buffer. When going back in the UNDO history
to a point before consistency was established, the forward-/backannotation
will be disabled again. Note that doing REDO will not automatically
Storing the fact that consistency has been established also truncates the
UNDO buffer at that point.
- The status bar of the editor window now contains indicators that show
whether the drawing has been modified, and whether forward&backannotation
- The BOARD command no longer clears the UNDO buffer of the schematic if a
board is newly generated.
- The frame object is now properly handled when rotated with the MOVE
command. Note, though, that the orientation of letters and digits in the
frame borders doesn't change when a frame is rotated.
- The UNDO command (as well as the REDO command) now displays in the status
bar what kind of command was undone (or redone) and how long ago that
command has been executed. If the command was originally executed in the
board, and UNDO was done in the schematic, it will also indicate that
(and vice versa).
- The new option LIST in the UNDO command opens a dialog that contains the
entire contents of the undo buffer. You can navigate through the list of
undo/redo steps by click&dragging the list delimiter, or by directly
clicking on any given step you wish to go back or forward to. If there
are several steps between the current delimiter position and the clicked
list item, all steps in between will be executed in the proper sequence.
Going upward in the list means doing UNDO, going downward results in REDO.
CAUTION: this is a very powerful tool! By going all the way back in the
UNDO list (which can be done with a single mouse click) and executing any
new command, the undo buffer will be truncated at that point, and there
is no way back! So use this with care!
- The User Language objects UL_BOARD, UL_SCHEMATIC, UL_SHEET and UL_SYMBOL
new have the new data members 'description' and 'headline'.
- The DESCRIPTION command now also works in schematics, sheets, boards and
- If the first parameter to the DESCRIPTION command is an asterisk ('*'),
the description of the library or schematic will be modified, as opposed to
an individual device set, package, symbol or sheet.
- If the DRC command is given an asterisk character ('*') as the first
parameter, the Design Rules dialog will be opened and allow editing the
Design Rules, without triggering an actual check when the dialog is
- The sheet thumbnails in the schematic editor now display the headline of
the sheets' descriptions as their caption.
- The sheet combo box in the schematic editor now displays the headline of
the sheets' descriptions.
- The context menu of the sheet thumbnails in the schematic editor has the
new option "Description" which can be used to edit the description of a
- The CLASS command now accepts class names that start with digits, as long
as they are not a plain integer number.
- Pasting is now done via the system's clipboard. This allows groups to be
copied from one instance of EAGLE into an other.
A detailed description of all changes can be found in the files
UPDATE and HISTORY.beta that come with the betatest archive.
Please do not post problem reports as a reply to this message!!
Start a new thread with a descriptive subject for each report (this
makes handling these reports a lot easier for us).
If possible, please post in ENGLISH rather than German to allow
international testers to follow the threads.
CadSoft Computer GmbH
Registergericht: Amtsgericht Traunstein HRB 5573
Geschäftsführer: Dipl.-Ing. Klaus Schmidinger, Thomas Liratsch