Sensors, Controls and Programming
september 30, 2013 6:30-6:45 PM
Power, sensors, controls and programming:
Sensors:
-2 photovoltaic sensors, on each side
-communicate with fans tell it to increase power or go in a certain direction
-correct path of travel
-sense close enough to payload
-robotic arm, how far it should go and how much it should turn, have to know the quadrants
Controls:
-Arduino, programming
-controlling fans, speeds and voltage given to the fans
-levitation fan
Power:
-circuitry
-battery
*ask about different fans from different groups
Sensors:
-2 photovoltaic sensors, on each side
-communicate with fans tell it to increase power or go in a certain direction
-correct path of travel
-sense close enough to payload
-robotic arm, how far it should go and how much it should turn, have to know the quadrants
Controls:
-Arduino, programming
-controlling fans, speeds and voltage given to the fans
-levitation fan
Power:
-circuitry
-battery
*ask about different fans from different groups
october 1, 2013 8-9PM
![Picture](/uploads/1/6/5/3/16539604/1380767180.jpg)
Members Present: Kushal, Alexa, Charles
- 3 servos
- 2 photvoltaic sensors
- sensors to correct pre-programmed route
- gives signal to position hovercraft properly
- Arduino programmed
- payload, beacon transmitting continuously
- sonar? (might be too much)
- touch whiskers as a possible idea under consideration, tell the arm to rotate or change directions
- need to ask about fans in order to find out what battery is needed
- need to introduce photvoltaic sensor to the environment so it knows what it's looking for (has to know to follow the black line, tell it that blacks is good)
October 15, 2013 8-10 PM
Members Present: Alexa and Charles
Members Absent: Kushal -3 photovoltaic sensors -find where to get the, price -need to know the propulsion fans we are going to use -compare notes with steve -kushal needs to figure out his design for the arm in more, detail, three servos, balsa wood -needs to figure out the building materials for the arm -charles can provide the programming -jumper wires, cables -1 Arduino, breadboard for testing -soldering in the end -put the Arduino on some balsa wood to protect it -resistors -mosfets -transistors -whiskers, touch sensors and wire (Kushal for more information) -ir beacon given, ir reciever -work with the power and propulsion group to figure out the circuitry they connect it to battery, we connect to arduino and sensors -don't need actual code yet -testing on the track, time -a couple led lights for testing purposes http://www.adafruit.com/products/161 -specs of photoresistor Charles has -photoresistors -can't add much to powerpoint right now, need more information from other groups Milestone 3: -pseuocode -circuit diagram work with power group Kushal: Payload delivery. Discuss the structure of your payload delivery device and how it will function. Sensors and actuators. Present your sensors and actuators and discuss the rationale for their placement on your craft. Control algorithm. Discuss your control strategy and present a flowchart or pseudocode of your control algorithm. A reader should be able to make sense of how your hovercraft will navigate and carry out the mission. • Assembly drawing of complete vehicle with all components. Clearly identify the location of each component relative to the center of pressure of the hull. • Wiring schematic(s). Possible Proplems: -encounter logic error with programming, a situation with sensors we have not anticipated beforehand -sensors may not behave as anticipated -arduino fire, break arduino -come up with more later -materials acquisition
Your browser does not support viewing this document. Click here to download the document.
Kushal's Payload Information |
What get done and by When:
-find materials:
Find all materials by Friday October 18, look into the type of photo resistor Charles has -discussions to be had:
Set up a time to talk with the power and propulsion group and Kushal -Charles find photo resistor and make a list of the specs -make pseudocode more detailed and organized in the form of a flow chart, discuss with Steve ideas Charles Thursday October 17 -payload delivery work with Kushal on sensors for that Kushal? Get powerpoint and report sections done by Monday. Finalize and fix anything on Monday before. Sensors and actuators. Present your sensors and actuators and discuss the rationale for their placement on your craft. Charles Control algorithm. Discuss your control strategy and present a flowchart or pseudocode of your control algorithm. A reader should be able to make sense of how your hovercraft will navigate and carry out the mission. Charles and Steve • Assembly drawing of complete vehicle with all components. Clearly identify the location of each component relative to the center of pressure of the hull. everyone • Wiring schematic(s). everyone Possible Problems: -encounter logic error with programming, a situation with sensors we have not anticipated beforehand -sensors may not behave as anticipated -arduino fire, break arduino -come up with more later -materials acquisition Alexa Payload delivery. Discuss the structure of your payload delivery device and how it will function. -drawings or design of payload -the materials needed for it and where to get them and prices Kushal |
Payload Delivery:
Robotic Arm will consist of three servo motors that are connected by light wood or plastic. We still need to determine how much weight we need to balance.
This is from some research I did:
Servo motors have three wires: power, ground, and signal. The power wire is typically red, and should be connected to the 5V pin on the Arduino board. The ground wire is typically black or brown and should be connected to a ground pin on the Arduino board. The signal pin is typically yellow, orange or white and should be connected to a digital pin on the Arduino board. Note that servos draw considerable power, so if you need to drive more than one or two, you'll probably need to power them from a separate supply Be sure to connect the grounds of the Arduino and external power supply together.
This is for the programming team (Steve and Charles):
attach(int) : Turn a pin into a servo driver. Calls pinMode. Returns 0 on failure.
detach() : Release a pin from servo driving.
write(int) : Set the angle of the servo in degrees, 0 to 180.
read() : return that value set with the last write().
attached() : return 1 if the servo is currently attached.
refresh() : You must call this at least once every 50ms to keep the servos updated. You can call it as often as you like, it won't fire more than once every 20ms. When it does fire, it will take from .5 to 2.5 milliseconds to complete, but won't disable interrupts.
setMinimumPulse(uint16_t) : set the duration of the 0 degree pulse in microseconds. (default minimum value is 544 microseconds)
setMaximumPulse(uint16_t) : set the duration of the 180 degree pulse in microseconds. (default maximum pulse value is 2400 microseconds)
Robotic Arm will consist of three servo motors that are connected by light wood or plastic. We still need to determine how much weight we need to balance.
This is from some research I did:
Servo motors have three wires: power, ground, and signal. The power wire is typically red, and should be connected to the 5V pin on the Arduino board. The ground wire is typically black or brown and should be connected to a ground pin on the Arduino board. The signal pin is typically yellow, orange or white and should be connected to a digital pin on the Arduino board. Note that servos draw considerable power, so if you need to drive more than one or two, you'll probably need to power them from a separate supply Be sure to connect the grounds of the Arduino and external power supply together.
This is for the programming team (Steve and Charles):
attach(int) : Turn a pin into a servo driver. Calls pinMode. Returns 0 on failure.
detach() : Release a pin from servo driving.
write(int) : Set the angle of the servo in degrees, 0 to 180.
read() : return that value set with the last write().
attached() : return 1 if the servo is currently attached.
refresh() : You must call this at least once every 50ms to keep the servos updated. You can call it as often as you like, it won't fire more than once every 20ms. When it does fire, it will take from .5 to 2.5 milliseconds to complete, but won't disable interrupts.
setMinimumPulse(uint16_t) : set the duration of the 0 degree pulse in microseconds. (default minimum value is 544 microseconds)
setMaximumPulse(uint16_t) : set the duration of the 180 degree pulse in microseconds. (default maximum pulse value is 2400 microseconds)
Arduino Code Worked on during class
![]()
|
![]()
|
![]()
|
![]()
|
![]()
|
![]()
|
Copyright © 2013 by Alexa Tsintolas. All rights reserved.