7. Electronics Design Automation

Due 2024/03/19

nfr glyph, ft230 led

How to use this document

Please refer to instructions in the week02 weblog entry

Conceive

  1. This week focused on designing and producing circuits. We used components from the Fab Lab list of materials (mostly supplied by Digi-Key).
  2. Producing a circuit is like building a train set with features such as switches and crossing gates.

Assignment

To do Done
Group assignment ⬇
Use the test equipment in your lab to observe the operation of a microcontroller circuit board (as a minimum, you should demonstrate the use of a multimeter and oscilloscope) Yes
Document your work on the group work page and reflect what you learned on your individual page Yes
Use logic analyzer Yes
Individual assignment ⬇
Redraw one of the echo hello-world boards or something equivalent, add (at least) a button and LED (with current-limiting resistor) or equivalent input and output, Yes
Check the design rules, Yes
Make it, Yes
Test it. Yes

Learning outcomes

To do Done
Select and use software for circuit board design. No
Demonstrate workflows used in circuit board design. No

Checklist

Have you? Done
Linked to the group assignment page? Yes
Documented what you have learned in electronics design? No
Explained problems and how you fixed them? No
Included original design files (Eagle, KiCad, etc.)? No
Included a ‘hero shot’? No

kicad to modsproject workflow inkscape, gimp http://fabacademy.org/2021/labs/kamplintfort/students/mattissen-gerhard/assignments/week05/ add arduino libraries https://www.electronics-lab.com/project/getting-started-with-the-new-attiny-chips-programming-the-microchips-0-series-and-1-series-attiny-with-the-arduino-ide/ ftdi mac drivers https://ftdichip.com/drivers/vcp-drivers/

Context

  1. Syllabus FAW07
  2. Assessment FAW07
  3. Tutorial FAW07
  4. Video FAW07
  5. Review FAW07

Comprehend

  1. Designing and producing circuits (mainly for mechatronics systems) happens when an electronic circuit meets all of the interface requirements of an embedded system. Mechatronics, Auslander, p.ix
  2. Embedded systems
    1. Form of system
      1. Types
        1. Continuous dynamics
        2. Discrete dynamics
        3. Hybrid systems
        4. Composition of state machines
        5. Concurrent models of computation
      2. Design constraints, embedded systems, lee, p.xvi
        1. Sensors and actuators
        2. Embedded processors
        3. Memory allocation
        4. Input and output
        5. Multitasking
        6. Scheduling
    2. Function of system
      1. Sense the environment
      2. Run programs
      3. Communicate with mechanical subsystem
      4. Actuate mechanical subsystem

Take Caution

  1. Human
  2. Machine
  3. Environment

Calibrate

Control

  1. Material-machine interface
    1. Materials
      1. Embedded systems may be able to detect material characteristics
      2. Fixtures
      3. Tools
    2. Machine-controller interface
    3. Controller-CAM interface
    4. CAM-design interface
      1. Designs may be translated by computer-aided manufacturing (CAM) software into a form that embedded systems can read.
      2. Embedded systems translate machine code derived from designs into actions for the mechanical subsystem to perform.
      3. These commands may be represented by changes in voltage or current
    5. Design-human interface

Create

  1. Human-science interface
  2. Human-industry interface
  3. Human-art interface
  4. What assumptions can we break?

Review week5 electronic design tutorial

  1. Eagle CAD tutorial
  2. D(difference)Access library commands through library manager, open schematic window first, click on available library, select library then select use button, also, I do not see a lib folder in Eagle folder
  3. T( tip) screen shot windows, apple key+ shift+ S. click on notification to open preview of clipboard, save snip
  4. T, ERC,( electrical rules check & DRC), design rules check, visible under tools in board mode
  5. T, ground= GND, add it from the library, use search, use the one in the splice library
  6. T, use the stop icon in the tool bar to stop adding components
  7. T, in the tutorial, Do not overlook the schematic download link after the sample-schematic heading
  8. T, name nets attached to components
  9. T, to connect two components, use NET NAME LABEL on the nets of both
  10. T, I got stuck on connect nets, I noticed that tutorial topic7.4 refers to Eagle resources, (the link also appears at the bottom of the tutorial page) the spark fun schematic tutorial provided the information that NAME is under EDIT, the connect option appears when the user repeats a name
  11. N,(note), I restarted making the tutorial circuit schematic in Eagle
  12. T, moving components together so they touch and then moving them apart creates a NET
  13. T, in Design Manager, to change values, select a part, right click on it, open symbol, tap also works
  14. p,(problem), warning CTS & RTS warning from ERC, I am using board traces from tutorial to identify the second pins, no traces on board, approving warnings
  15. T, had to activate Avoid Obstacles in order to copy example trace
  16. T, Eagle offers a Rip up everything option
  17. T, View> Grid, use to change snap to amount
  18. T, Use Group, Change( wrench), Width-20 mm, then control+ right click to change width of traces@ the same time
  19. T, Use selection filter tab to isolate layers, isolate dimension layer, use Move tool to change size of yellow dimension frame
  20. T, To draw on a layer with draw tools, select layer in tool bar, that changes pen color

kicad import snapeda symbols and footprints https://support.snapeda.com/en/articles/2651507-how-to-import-into-kicad nadieh gives a good blow-by-blow of kicad design here http://fabacademy.org/2021/labs/waag/students/nadieh-bremer/blog/week-6/ https://www.reddit.com/r/KiCad/comments/titbox/erc_warns_symbol_has_been_updated_in_library/ no grounding; cleaning trace collisions by resizing pads and moving edge cut. moving edge cut lines did not seem to change Gerber output in Bantam. So, I erased all of the old ec and created a new one. checking svg output for missing traces at top of circuit. the problem with the top of the circuit in bantam was that i used refresh which updated the front cu file but not the edge cut file. so the old, unedited edge cut kept truncating the updated front cu file. i use kicad gerber for the trace output and mods project for the interior. this seems fairly efficient. bantam accepts gcode directly. ERC, DRC SCHEMATIC recreating circuit from another source. I label connection points of ICs and protocol headers. usb, ftdi, updi, jtag. workflow (process) of circuit embedded programming: receive command from programming device using a given protocol to change to a programmable state, eg., flash; program the IC to perform some action (upload functions to computer), test computer program to see if computer performs the desired task. debug program if necessary. the knowledge to perform this workflow will come from understanding the communication protocols (pins used and commands to change states of IC) that enable programming device to control IC and datasheets of ICs. do not forget no connect flag (q) jumper for 5v vcc v. 3.3v vcc? does updi use 5v? what vcc does ftdi take? delete only traces: https://forum.kicad.info/t/how-to-delete-all-tracks-in-pcbnew/27844 new york state map svg https://commons.wikimedia.org/wiki/File:Map_of_New_York_County_Outlines.svg illustrator ungroup; direct select; drag county outlines, delete