You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

39 lines
3.0 KiB

  1. Eagle Plugin Implementation Notes. 2017 Russell Oliver
  2. Below is some notes on the correspondence between Eagle schematics and symbols libraries and the
  3. KiCad equivalent.
  4. Eagle libraries are a many to many listing of symbols and footprints connected by a device set and
  5. device definitions. They are embedded in the schematic and board files if there are used, and
  6. therefore the schematic symbols and footprints can be recovered from either file.
  7. An Eagle device set definition is the information needed to represent a physical part at the
  8. schematic level including the functional gates of the device. Each gate is lists the symbol to be
  9. displayed for that gate. This is equivalent to a KiCad symbol unit. Since the symbol is defined
  10. outside of the device set, multiple devices sets in the library can use the same symbol for a gate.
  11. Lower to a device set, is the device definition. This establishes the link between the schematic
  12. symbols and a physical part through the 'connect' elements. These map the symbol pins for each gate
  13. to the physical pins provided by the package (footprint) definition. An Eagle Symbol outlines the
  14. layout of graphical of items including pins. Pins for multi gate symbols are generally labelled
  15. per their function, i.e. input / output. An Eagle symbol pin is not numbered but merely labelled. A
  16. connect element gives the pad number for each pin found in that gate. Therefore the equivalent
  17. KiCad pin number is read from the connect element pad number. Since an Eagle gate is equivalent to
  18. a KiCad symbol unit, the graphical items for that unit will be copied from the Eagle symbol for
  19. that gate and will be unique for that unit. This will yield duplication of the graphical elements
  20. if the same symbol is used for multiple gates but the conversion will be complete.
  21. An Eagle sheet contains a list of instances, which are equivalent to KiCad schematic component
  22. entries. An instance describes the part, the gate used and its location on the sheet. This is
  23. translated into the equivalent KiCad symbol with the given unit number.
  24. Eagle 'plain' items describe graphical items with no electrical connection, such as note text,
  25. lines etc. Of importance is the use of wire elements to describe both electrical connections and
  26. graphical items. A wire element will act as an electrical connection when defined within a net and
  27. segment. Anywhere else it is a graphical line. The layer for the wire element will change the
  28. displayed colour for the wire. Connections between regular wires and busses occur when a wire ends
  29. on a bus segment. When translated to KiCad a bus connection symbol is created. Within an Eagle
  30. schematic there can be multiple sheets in a flat hierarchy. For each sheet, there is a list of
  31. electrically connected nets. Each net is broken up into graphically connected segments, defined by
  32. a list of wires and labels. Labels remain associate with wires of that net segment, even if they
  33. are not located on a wire element. This necessitates the movement of such a label to the nearest
  34. wire segment within KiCad.