<-- Week 12

WEEK 13
[ INPUT DEVICES ]

Week 14 -->


WEEK'S GOALS:

1. DESCRIBED YOUR DESIGN AND FABRICATION PROCESS USING WORDS/IMAGES/SCREENSHOTS.(Done)
2. EXPLAINED THE PROGRAMMING PROCESS/ES YOU USED AND HOW THE MICROCONTROLLER DATASHEET HELPED YOU.(Done)
3. EXPLAINED PROBLEMS AND HOW YOU FIXED THEM (Done)
4. INCLUDED ORIGINAL DESIGN FILES AND CODE(Done)


ACHIEVEMENTS THIS WEEK:

(i) INPUT DEVICES

1. MOTION DETECTOR-PIR Sensor Module with own board.
  • Helps sense motion over a distance and by intensity
  • Switch off LED when motion detector PIR Sensor doesnt sense movement.
2. Button as an input
  • Executes an SMD LED on pressing the button
  • Interated within the board.
Note: OSCILLOSCOPE was used to read the data of button board

3. IR sensor as an input to Atmega 328 board

(ii) OUTPUT DEVICES:

1. Pizo-Buzzer
  • When the board's IR or PIR detects movement, the buzzer sounds in a given pattern
2. LED
  • When the board's IR or PIR detects movement, the LED lights up in the same pattern as the buzzer
3. Servo Motor
  • Using Firefly and Arduino, managed to make the servo rotate directly through a firefly INterface. Note: Board used was arduino for this one case.

TASKS AT HAND:

NO PENDING TASKS

WEEK's START:

So this week started with Neil having asked Vigyan ashram students to check the way they mill a PCB since none of them were getting neatly milled boards. Havnig managed to get good results from the old Modela, Suhasji asked me to explain all others in deep the proper way to mill and tips regarding customised boards among other settings and arrangements on the modela. So the first two days went by teaching others everything there was to the older modela and all about the offline version of MODS and each of its settings in deep. Am glad that no board since then at VA went milled with any rough surfaces to them and the no. of bits that broke reduced too.

1


NOTE: Vigyan Ashram is known as "Fablab 0" , it is one of the remotest labs with very minimal internet access , therefore, we have been using old version of Fab module which is an offline version.

1


(i) INPUT DEVICE as IR with (ii) OUTPUT DEVICE as Buzzer

Final Electronics: Obstruction Detection Sound System x 2 boards




I designed a cuboid kit for my final project where in i designed my own board with atmega328 IC. In the video above, you will see an Ir sensor connected with my board pin headers IR sensor (GND, VCC, DATA PIN), then two pins of buzzer (GND, SIGNAL) connected to the board and lastly, my own FABISP connected to the board's (GND, RESET, VCC, MOSI, MISO, SCK) for power and programming before. In this cuboid kit i basically later included switches so that every switch can be used for a specific board assembled in the cuboid.

1



In above picture, you will see my final project and my output/input board of Atmega 328.

(i) INPUT DEVICE as PIR with (ii) OUTPUT DEVICE as LED


In the video below you will see i am using my designed board of Attiny 44 which has pin header, programming pins, resonator and IC for sensors i plan to use both Ir sensor and Motion sensor.

Final Electronics: Obstruction Detection Sound System



In the above video, you will see i am doing Motion sensor with my another ATTiny 44 input board.

1


STEPS to make this board:
  • DESIGNING: I designed this board on Eagle, made its schematic adding components like ATtiny 44, resonator, Pin header2x3 and 1x6, connecting , checking ERC for errors

  • 1


    Using Fabisp to program it

    1


    Motion Sensor which has three pins GND, VCC and data pin which i connected to my Attiny44.

    1


    1


    Above images are my cut file and trace file for my Attiny board 44.

    1


    1


    1



    Design Process:

  • Its great to understand Eagle with its DRC, ERC features, so as always I set components on schematic , connect them, to avoid mess I connected a GND sign to GND and used that everywhere wherever I wished to connect GND, for example, I want my pin 4, 8, 10 connect to GND, it will look very messy to connect all of them together plus sometimes they don’t connect well, so I type ADD on command, look for GND component in the library, connect it to GND of my IC which defines that wherever I use GND that pin will be connected to GND on IC.
  • I keep moving all components a bit to check if they are well connected and also do ERC to check errors. I switch to board where I do DRC, that is, design rules where I can change the thickness , distance of my routing.
  • I keep setting components in different positions and autoroute till I feel that they are not very close and wont shot. After that sometimes, when I don’t like my auto routing so I manual routed those parts.
  • Importing File:

  • PNG with 1000 resolution.
  • Photoshopped for cut file.

  • Milling:

  • I first used 1/64 mill, where I kept my diameter as 0.06 and z as -0.06, whereas z default is -0.1
  • I then used 1/32 for cut file, there I didn’t made any changes.
  • Soldering:

  • I always start by soldering the IC first.
  • Also I keep testing my connections with multimeter so that I don’t get to know errors after everything is complete.
  • Programming:

  • While my board was milling, I took an Arduino and tried motion sensor with it and PIR sensor.


  • Finally I needed to make my makefile and for that i coded in the Arduino IDE-complied it and then did 'MAKE' with the makefile from its location in GIT bash through my board ,

    (iii) INPUT DEVICE as PIR with (ii) OUTPUT DEVICE as LED on ARDUINO


    1


    Setting up Arduino:

  • First i started working on Arduino, where I connected motion sensor to Arduino and a LED to Arduino. As a part of my final project, I need a motion sensor for my container wherein if no motion is detected the lights turns off, so for that I designed my board in Eagle,
  • CODE:

    So my codes are below:
    I took them from internet first but while I was uploading it showed “ serial undefined”, after repeated trials I preferred coding myself referring the previous one with no Serial.
                    

    FTDI Pinout

    Codes tested

    MOTION SENSOR with LED

    (ii) OUTUT DEVICES

    My output devices was done this week so as to do just one board to tackle both input and output as it made more sense to me to do it this way.