owned this note   changed 6 years ago  
Linked with GitHub

Electronics concepts

Input devices #1 [Guillem]

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
28/03/2019

Core ideas

  • Why we need sensors
  • Neurons, I/O and Bio indicators
  • Sensing the environment
  • Close loop systems
  • Inferring metrics
    • Bike speed from counting wheel turns
    • Water tank distance from distance from above
  • Composed sensors
    • Radar: emitter (output) and receiver (input) working in sync
  • Complex post processing: Compur vision
    • From a list of colors (pixel matrix) to meaningful data (i.e. object location based in color tracking)

How to choose and use a sensor

The section is aimed at INPUTS (sensors) but many concepts work also for OUTPUTS (motors, LEDs)

Input devices #2 [Guillem]

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
29/03/2019

Playing with your Hello Board

When the ATtiny is not enough: Other microcontrollers!

The ATtiny can do amazing things but will require us to optimize the code to an uncessary level when we just want a protoype…

  • ATtiny44

    • Example board: HelloBoard
    • FLASH 4KB
    • RAM 256B
    • Pro: Digital and Analog Inputs and Outputs
    • Con: No Hardware I2C or Serial

  • ATtiny84

    • Example board: HelloBoard
    • FLASH 8KB
    • RAM 256B
    • Pro: Digital and Analog Inputs and Outputs
    • Con: No Hardware I2C or Serial

  • ATMEGA328

    • Example board: FabDuino
    • FLASH 32KB
    • RAM 2KB
    • Pro: Hardware I2C, Serial and SPI
    • Con: No USB Hardware (requires an FTDI)

  • ATSAMD21G18

    • Example board: Adafruit Feather M0
    • FLASH 256KB
    • RAM 32KB
    • Pro: Multiple I2C, SPIs, Serial and full speed USB
    • Con: No WIFI or Bluetooth

  • ESP32

    • Example board: ESP32 Feather Board
    • FLASH 4MB
    • RAM 520KB
    • Pro: WIFI and Bluetooth
    • Con: No USB Hardware (requires an FTDI)

Output devices #1 [Victor]

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
04/04/2019

  • Actuating, closing the loop.
  • Controlling electricity to generate movement or light.

Types of actuator


  • Electromagnetic

    • DC motors
    • Brushless motors
    • Servo motors
    • Stepper motors
    • Relays, solenoids, valves, etc
    • Speakers

  • Electroluminescence

    • Leds
    • RGB
    • Addressable
    • LCD's (polarized light and liquid crystal)

  • Piezoelectric

    • Buzzer and speaker.

  • Fab Academy sensors

Controlling outputs

  • LED's
    • One color, PWM for intensity
    • RGB, PWM
    • Addressable -> libraries guides
    • Charlieplexing image
  • DC motor
    • H-bridges
  • Brushless motor
    • Search
  • Stepper Motor
  • Buzzer and Speaker
    • Arduino Tone function
    • Amplifiers

How to wire an output?

How to code for an output?

More outputs recipes














Debugging inputs and outputs [Victor]

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
05/04/2019

  • Divide and conquer.
  • Always subdivide the system as much as posible.
  • Metodic tests

Hardware

  • Prototyping before building
    vs
  • Multimeter checks
  • Continuity before and after soldering components
  • Voltages
  • Isolating hardware parts, cutting traces, solder bridges, jumpers, designing for debug.
  • Unconsistent tests –> heat or power problems.

Software

  • Creating small sketches for testing specific parts
  • Using Serial print.
  • Using defines to build a better Serial Print debug
  • Using comments to disable code
  • Structuring the code in functions
  • Always review compiler error messages.
  • Get someone else to review your code

Advanced inputs and outputs recipes and coding [Guillem]

Select a repo