{"id":2047,"date":"2016-09-05T12:31:23","date_gmt":"2016-09-05T10:31:23","guid":{"rendered":"http:\/\/priit.ati.ttu.ee\/?page_id=2047"},"modified":"2020-09-26T10:24:13","modified_gmt":"2020-09-26T08:24:13","slug":"eagle","status":"publish","type":"page","link":"http:\/\/priit.ati.ttu.ee\/?page_id=2047","title":{"rendered":"Eagle"},"content":{"rendered":"

Getting started<\/strong><\/h3>\n

Open Eagle<\/p>\n

Open Directories, add the custom library location. Separate with semicolon.
\n\"Eagle\"<\/p>\n

Eagle comes with set of default libraries which include wide variety of components. For removing libraries, right-click on the libraries folder and select “Use none”. To use a custom library in a project, locate the library and job fairs near me<\/a> select use.
\n\"Deselecting
\n\"Enable
\nCreate a new project, add a new schematic. This opens schematic editor. The newly created file will NOT <\/strong>save automatically, so save the file. CTRL + S.<\/strong>
\n\"Eagle\"<\/p>\n

Building a schematic<\/h2>\n

On the schematic editor window there are two main areas – tools and worksheet. In the worksheet use scroll wheel to zoom and and middle click to move in the schematic. Lets add a new component. Edit – Add…<\/strong><\/p>\n

For example we can search for NAND gate in the 7400 series. Searching in the components library in Eagle can be little tricky, because the very exact keywords are needed. We can overcome this  by inserting the keywords between wildcards<\/em> (*). This brings up more components related to the keyword.
\n\"Adding
\nTo place the component, select it and then click OK<\/strong>. Component can be rotated with the right mouse button. It is possible to add unlimited number of selected components, so when the desired amount of components are placed, exit the add-mode with ESC. <\/strong><\/p>\n

Creating a connection between the components can be done with NET<\/strong> tool, not to be confused with WIRE<\/strong>, which is used for drawing on different layers (technically can be used to draw  net layer as well).
\n\"Net\"\"Wire\"<\/p>\n

Connection can be left  “hanging” by pressing ESC<\/strong>.
\n\"Wire
\nNaming a net is done with Name <\/strong>tool. This allows creating connections without actually connecting the wires on the schematic.
\n\"Net<\/p>\n

To see and place the name on the schematic use Label<\/strong> tool.
\n\"Label<\/p>\n

Verifying the connections is done with Show<\/strong> tool or by moving the component.<\/p>\n

All the tools can be used on the individual components or on the component group. To select the group, use Group. <\/strong>After selecting the group, choose an action to perform on a group. Eagle also displays a helpful https:\/\/xjobs.org\/<\/a> messages on the bottom right corner.
\n\"Group\"Hints!!\"<\/p>\n

After finishing up the schematic,  switch the view to board layout.
\n\"To<\/p>\n

Board layout<\/h2>\n

Before anything else its recommended to use and set a grid. <\/strong>This sets the snap-grid for the components and wires. Alternative grid is accessed with holding down Alt<\/strong>. Notice the imperial units.
\n\"Set<\/p>\n

Start positioning the components onto the working area. Components are connected via airwires, which represent shortest possible way to connect two points. After moving the component into place hit Ratsnets <\/strong>command. This will calculate new airwires.
\n\"New<\/p>\n

Placing components is crucial to smooth routing process and since there are no strict guidelines to this, here’s few tips:<\/p>\n

    \n
  • If possible group the components into functional blocks and route them<\/li>\n
  • Use ground planes<\/li>\n
  • Start with connectors and terminals at the edges of the board<\/li>\n
  • Good design tends to be symmetrical, but don’t compromise board size and electrical parameters<\/li>\n
  • Avoid round and 90 degree bends where possible<\/li>\n
  • Wider wires have less electrical resistance and inductance plus they are cheaper to manufacture<\/li>\n
  • Play around<\/li>\n<\/ul>\n

    Main tools of the routing process are Route <\/strong>and Ripup <\/strong>which do as they say.
    \n\"Route\"
    \nWhile routing it is possible to switch the top and bottom layer route with clicking <\/strong>the scroll wheel<\/strong>. Changing the route mid-route creates via<\/strong> which is also accessible from the toolbar.<\/p>\n

    Most of the cases, it is recommended to use ground planes. This is accomplished by Polygon <\/strong>tool. Draw the polygon around the board, then use Name<\/strong> tool to connect it to a ground net. This makes routing much easier.<\/p>\n

    After routing everything the ratsnest command should output \"Finally\". Now its time to run DRC<\/strong> or Design rules check. Load the .dru file and press Check<\/strong>. This will highlight overlapped routing, clearance and dimension errors.
    \n\"DRC\"<\/p>\n

    About autorouter<\/strong><\/p>\n

    Eagle comes packaged with autorouter which is free to use. Autorouting algorithms and techniques are very complex and sophisticated, but without proper configuration for the autorouter, the routing is by no means ideal. While sometimes it gives very good results for small areas of the board, the bulk of the design should be and is usually done by hand.
    \n\"You<\/p>\n

     <\/p>\n\n \n \n Last modified: 2020-09-26 10:24:13\n","protected":false},"excerpt":{"rendered":"

    Getting started Open Eagle Open Directories, add the custom library location. Separate with semicolon. Eagle comes with set of default libraries which include wide variety of components. For removing libraries, right-click on the libraries folder and select “Use none”. To use a custom library in a project, locate the library and job fairs near me […]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":1269,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/pages\/2047"}],"collection":[{"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2047"}],"version-history":[{"count":28,"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/pages\/2047\/revisions"}],"predecessor-version":[{"id":2402,"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/pages\/2047\/revisions\/2402"}],"up":[{"embeddable":true,"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=\/wp\/v2\/pages\/1269"}],"wp:attachment":[{"href":"http:\/\/priit.ati.ttu.ee\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}