Spring 2017 BiPed – BiPed Prototype/Walking Experiment

By: Alexander Clavel (Project Manager)

Approved by: Alexander Clavel (Project Manager)

Table of Contents

Introduction

The BiPed projects goal is to be able to create a walking bipedal robot that is able to perform static walking. The definition of static walking is walking that remains constantly balanced throughout the robots entire walk. In theory, when the power to the robot is cut off, the BiPed should stay standing and balanced. This is one of our main requirements. This blog post shows the process of building one of the prototypes.

Design/Construction

The overall construction which included buying all the parts and materials and then assembling them together took a little less than a day. We decided to go with a design that was found through reserach on youtube of walking bipeds. We were looking to find something simplistic as to be able to stay light on the material as well as the power draw on the electrical components. The BiPed we based this prototype off can be found here in a video. In the video, the biped uses a straight leg with no linkage and uses circular motion to walk forward. It is also a very small design that reaches a little under 20 centimeters in height which is something we would like to incorporate in ours.

Gear Box

Figure 1

Figure 2

This was the first attempt at using a gear/pulley combination to drive the robot. The white round gears on the outside of the wood area in figure 1 show the rotational movement that the legs would be taking during the walking motion and the actual legs would be connected to the metal pegs sticking out. The rubberband in the pulley in figure 1 would wrap up to the pulley that is attached to the motor in figure 2. I tried using a 1 to 1 ratio for the pulley on the shaft to the pulley that will drive the 2 gears next to it. From reasearch done and experience with cars, I learned that using a smaller radius for the driver to a larger radius produces more torque, but less speed. For our requirements we will be needing that torque to be able to drive the robot, but we will also need to keep it fast enough to pass our speed requirement. From this reasoning I tried a 2 to 1 or 3 to 1 for the purpose of testing the walking motion. The two additional bevel gears in figure 2 were to work towards a solution for the balancing problem, but it was never completely finished due the professor not liking the design of our feet (which overlapped each other) so the design was to be changed anyways.

Leg Design/Movement

Figure 3

As stated before, there is a single wooden board for the legs that use a rotational motion for the legs. Figure 3 shows a side view of the gear box where the legs would be attached. The bottom of the robot is to the right of the image. This being just a test, I placed the pegs very close to the shaft because I just wanted to at least see if it would rotate. The final product would have to have a larger radius from peg to shaft so that the robot will be able to get a decent distance with each step. Again our design was kicked back because the feet  that were attached were overlapping to account for the balancing. Without the overlapping feet, the balancing mechanism at the top of the robot would have had to be completed.

Conclusion

Figure 4

Figure 4 shows the entire main body of the biped attached. Again the rubberband is connected from the pulley in the gearbox to the pulley driver connected to the motor. The legs were not added to the image, but again, they are connected to the metal pegs sticking out on the sides. To restate it, the gear at the top of the robot is vestigal at this point and doesn’t serve a purpose for this prototype but should play a bigger part in the final product. When completely assembled, the robot shows that it does indeed give a clean walking motion while being held in the air. When placed on the ground the robot does “walk”, but it was a very rough, sloppy, and unbalanced motion. As it moves forward it does wobble side to side to a large degree, but at a very slow pace. Concluding comments would be that:

  • It does perform a walking motion
  • It does not stay balanced without the overlapping feet unless a balancing mechanism can be created
  • The walking speed is very slow.

There will need to be more adjustments to the prototype for application on the final product.

Referrences

  1. http://www.blocklayer.com/pulley-belteng.aspx
  2. http://tech.txdi.org/gearsandpulleys
  3. https://www.youtube.com/watch?v=Z7N0xCDVzIA&feature=youtu.be

Spring 2017 BiPed – D.C. Motor Stress Experiment

By: Abraham Falcon (Electronics and Control)

Approved By: Alexander Clavel (Project Manager)

Table of Contents

Introduction

Electronics and Control engineer job is to do an experiment on the D.C. motor to see if it can the handle the weight needed for the biped to walk. The following experiment was to determine if the chosen D.C. motor can handle the Biped’s total weight while one foot is off the ground and the other supports the entire system. The maximum stress weight of the Biped was chosen to be at 500 grams which is also what was used to determine out projects mass allocation. The test was also done to calculate exactly how much power consumption came from the D.C. motor and to determine if this would be acceptable to last up to the 30 minutes duration for the Pacman Game.

Experiment

 

Table of results:

Servo Motor Stress Weight Operating Voltage (Volts) Stress Current

(Amps)

Pololu 200:1 Plastic Gearmotor 500 grams 6 volts 100 mA

 

This experiment was done by hooking up the D.C.  motor to a battery rated at 6 volts and with a digital multimeter in series. The weight of 500 grams was attached to a custom-built pulley wheel that was attached to the shaft of the D.C. motor. Also the radius of the custom-built pulley wheel was measured out to be about 1cm.

Here is an example of the D.C. motor connection without the weight and you can see that with no load the D.C. motor runs at the highest of 62.289 mA

The setup from above picture was used but added a custom-built pulley wheel to the motor with a weight of 500 grams. The D.C. motor lifted the weight of 500 grams and the current was measured. From observation, this D.C. motor can handle the stress weight of the biped at 500 grames and the current was measured to be at its highest of 100 mA. All recorded results from this experiment is listed on the table of results above.

Here below are two pictures of the custom-built pulley wheel which was used for the experiment of Biped’s stress weight.

Conclusion

Performing this experiment, it showed that this Pololu 200:1 Plastic Gearmotor will allow for the Biped to be able to walk and also shows that for the current, the power consumption is low enough for the D.C. motor to be able to last for 30 minutes. This experiment concluded that this D.C. motor will work and it does fit our requirements for this Biped. In the references section, there is a video starting from 5:01 till 6:02 that shows how the custom-built pulley wheel was made and used for this experiment. The second reference was also a basing of the setup of this experiment to lift the weight and measure the current of the D.C. motor.

References

  1. https://www.youtube.com/watch?v=YGjBOsd9Z2g&index=2&list=FLoSP5pt7W0bsWc1xuJASmww
  2. https://www.clear.rice.edu/elec201/Book/motors.html

Spring 2017 End of Semester Game “Pacman”

By: Alexander Clavel

Apporved By: Game Committee

Table of Contents

Game Committee Members:

Amber Scardina – TRC President

Alexander Clavel – BiPed Project Manager

Nicholas Jacobs – Spiderbot Project Manager

Jesus Enriquez – Velociraptor Project Manager

Overview:

The BiPed and Velociraptor will participate in a game of PacMan. Both robots will start on opposite ends of a maze with the BiPed initially acting as PacMan and trying to avoid the other robot. The BiPed and the Velociraptor will attempt to collect as many “dots” or points as possible within the allotted time limit. The Velociraptor will initially act as the “ghost” and try to catch Pacman before the end of the game while also collecting points. The game will start once the Spiderbot has reached its position and begins video feed. The game will last a maximum of 30 minutes.

Rules:

–   Spiderbot will walk into the maze and then place itself above the maze for video set up

   Biped will start off as “Pacman” while the velociraptor starts as the “ghost”

  Both robots will start in different ends of the maze

   There will be red dots on the ground which will be “counted” and displayed on both robots as they pass over a dot.

–   If the Velociraptor reaches and “eats” the BiPed before the 30 minutes then the raptor wins

   If the Velociraptor does not “eat” the BiPed then the winner will be determined by who has the most dots counted.

   There will be special grid squares to make the velociraptor vulnerable to being “eaten” and will reverse the rolls

–   If the BiPed can reach the velociraptor within the time limit then the velociraptor loses.

   Live aerial video feed will be provided by the Spiderbot

   Time limit of 30 minutes OR when the ghost catches Pacman OR when one group reaches 5 dots first.

–   If a robot falls over, that will count as a deducted point and they will start again at their starting area.

–   Points will be deducted at the end of the game by subtracting the endgame amount from the number of times the robot has fallen

View and Control:

      BiPed and Velociraptor will view the gaming field through video feed provided by the Spiderbot

      Both Robots will be controlled through the arxterra control panel

Terrain:

      35 in x 56 in area

–       Flat paper taped across the tiled floor of the classroom

      No physical walls

–       The Maze will be printed on paper

      7 inch width for walkways for the robots

      Roof with steel area for magnet and supports made of wood for the spiderbot height TBD

 

Game map to be updated , Dots to be added***

SpiderBot and Velociraptor Starting Point – Left Opening

BiPed Starting Point – Right Opening

Spring 2017 BiPed – Servo Ankle Stress Experiment

By: Abraham Falcon (Electronics and Control)

Approved by: Alexander Clavel (Project Manager)

Table of Contents

Introduction:

Electronics and Control engineer job is to do an experiment on the servo motor to see if it can the handle the weight needed to perform the funtion of turning at the ankle. The following experiment is to know if the chosen servo motor can handle the Biped’s weight. The stress weight of the Biped was chosen to be at 500 grams as to be the maximum weight, but our actual weight should be lower than this. The experiment is also to see if the power consumption of the servo will exceed our maximum of 500 mA.

Experiment:

Table of results:

Servo Motor Servo Location Stress Weight Operating Voltage (Volts) Stress Current

(Amps)

HXT900 Micro Servo Ankles 500 grams 3.3 volts 270 mA

This experiment was done by hooking up the servo motor to the arduino and the digital multimeter in series. The weight of 500 grams was attached to a servo plastic gear with a radius of 1cm.

 

Here is an example of the servo connection without the weight and you can see that with no load the servo runs at the highest 71.961 ma.

The setup from above picture was used but added the weight of 500 grams. To simulate the weight of the ankle from Biped weight the servo was put upside down and observed if the full rotation of the gear on the servo with the weight performs well. By observing the weight on this servo, it can handle the stress weight of the biped and the current was around 270 mA.

Conclusion:

The experiment was preformed and showed that this HXT900 Micro Servo will make Biped be able to turn on the ankles and the current shows that the power consumption is under 500 mA. This experiment concluded that this servo will be effective for the ankles to turn. In the references section shows a video of the servo torque test of this type of servo chosen and this was a guide to perform this experiment.

Referrences:

  1. https://www.youtube.com/watch?v=dCgiE0xpToI&index=11&list=FLoSP5pt7W0bsWc1xuJASmww&t=168s

Spring 2017 BiPed – PCB Schematic

By: Abraham Falcon (Electronics and Control)

Approved by: Alexander Clavel (Project Manager)

Table of Contents

Introduction:

Electronics and Control engineer is to create a custom PCB and to layout the components to be used. The PCB components are a PCA9685 PWM expander, pin headers for the LEDs and a pin header for the color sensor.

 

Eagle Cad Schematic:

The Biped PCB schematic below shows what the main components are to be use with the 3Dot board, which is the color sensor and a LED counter.

This PCB schematic is the third version and to be used on the Biped mainly for the game. Previous PCB schematics had two extra servos from the main design of the biped. As we moved forward with the design of the Biped, the customer stated that the power was the be supplied without an external battery. Power should soley be provided by the 3Dot board battery. The servos were eliminated to reduce the power consumption and therefore the PCB schematic above is the final version to be used with the 3Dot Board.

The PCB needs to communicate with the 3Dot board and the PCA9685 PWM expander will handle this. The PCA9685 PWM expander handles multiple PWM pins as the 3Dot board does not provide. Connecting multiple devices to the PCA9685 PWM expander will communicate to the 3Dot board through the I2C bus.

There will be two LEDs for the Biped to represent the eyes that are colored red and signify that the robot is indeed on. The other LED which is green is to represent a counter for collecting colored dots from the “end of semester” Pacman Game. All the LEDs connect with a 1k Ω to PWM expander, which these resistors are to limit the amount of current going through the PWM expander for protection. The LEDs are not physically connected to PCB board therefore it will use pin headers so the LEDs can freely be placed anywhere around the Biped.

For the Biped to sense the color dots from the game it will be using a Adafruit RGB Color Sensor and this sensor will also not be physically connected. The colored dots are placed on the floor therefore the color sensor must be placed on the foot to sense the color dots. The pin headers have the connection needed to connect to the 3Dot board and be powered by it. The pin headers connect to the I2C bus from the 3Dot board, which are SDA and SCL. Also from the 3dot board the power and ground can be connected to the sensor provide from 3Dot board connection. The pin headers are placed so that the color sensor can freely be placed anywhere on the biped and for this design we chose it to be on the foot.

The other components on the PCB schematic were provide from the product website, where they also provided Eagle Cad files. All the components are surface-mount devices. These components were left alone as the product works with it.

Conclusion:

The completed PCB schematic is simple but pushed our design to have less power consumption and to participate in the “end of semester” Pacman Game. The completed PCB Schematic is sent to the manufacturing engineer to layout the PCB and to be completely assembled.

Referrences:

  1. http://www.mouser.com/ProductDetail/NXP- Semiconductors/PCA9685PW118/?qs=sGAEpiMZZMvKM5ialpXrmnWDpPMxsdrM
  1. http://www.mouser.com/ProductDetail/Broadcom-Avago/HLMP-3301/?qs=sGAEpiMZZMsx4%2fFVpd5sGeS9q14uN1KF
  1. http://www.mouser.com/ProductDetail/Broadcom-Avago/HLMP-3507/?qs=sGAEpiMZZMsx4%2fFVpd5sGbU8v9L8Znih
  1. https://www.adafruit.com/products/1334

Preliminary Project Plan

By Martin Diaz (Project Manager)

Adan Rodriguez (Mission System and Test)

Moses Holley ( Electronics and Control)

John Her (Manufacturing)

Edgardo Villalobos (Solar Manufacturing)

 

Table of Contents

WBS

By Martin Diaz (PM),

Adan Rodriguez(Mission,Systems)

 

The work breakdown structure organizes the work needed to complete the project by putting task under each engineer. For our WBS the work of the system engineer was organized into 3 blocks, System Design, Software, and system tests. The work of the ENC engineer was organized into 4 blocks, Electronic Design, Research/Experiments, Microcontroller and PCB, and finally MCU Subsystem and control. The work of the Manufacturing engineer was broken down into  5 blocks, Mechanical Design, Research, 3D simulations, and manufacturing parts and assemblies, and assemble Mini-Pathfinder.

 

Schedule

By Martin Diaz (PM)

The project schedule was created by using Project Libre. Each Task in the WBS was put as task into Project Libre and then the start and end dates were assigned. When a task depended on a other task to be finished first dependencies were assigned. This can be done by clicking and dragging arrows to other boxes. The program will automatically adjust the task.

Burndown

By Martin Diaz (PM)

The Burndown is a chart that shows how much work is left to complete the project vs time.  The Burndown was calculated by moving the task in the schedule to columns in excel and then assigning the percent completion for each task. The ideal percent completion and real percent completion were then plotted vs time.

Power Allocation

By Adan Rodriguez (Mission and Systems)

John Her (Manufacturing)

Moses Holley (ENC)

Edgardo Villalobos (Solar-Manufacturing)

 

The power rating for all of the components on the Power Allocation Report list were calculated using specification sheets of corresponding components. We approximated our mission duration to be 1 hour (one fourth the duration of the Pathfinder’s mission due to our rover being one fourth scale in size). Using the specification sheets to find current ratings of the components, we multiplied the current ratings by one hour to calculate power ratings in milliamp-hours. For the motor drivers, we looked at the power consumption of the IC and divided the operating voltage to get the current draw (0.78W/6V=130mA). The I2C I/O Expander is rated for output of 25 milliamps per pin and we will be utilizing 6 pins implying a total power consumption of 150 milliamp-hours. The Project Power Allocation was set to be slightly higher than the total Expected Power. Note that the Project’s Power Allocation value was used to aid in determining which battery to choose for our mission.

Mass Allocation

By Adan Rodriguez (Mission and Systems)

John Her (Manufacturing)

Moses Holley (ENC)

Edgardo Villalobos (Solar-Manufacturing)

 

Estimates of the 3Dot Board and Custom SMD Board were based off the fact that they are similar in size to the Raspberry-Pi Board (31 millimeters x 66 millimeters). The chassis, solar panel and suspension system were weighed with a scale. Corresponding Sources of expected weights is provided under the Source column. The Project Mass Allocation was set to be slightly higher than the total Expected Weight.

Cost Allocation

By Adan Rodriguez (Mission and Systems)

John Her (Manufacturing)

Moses Holley (ENC)

Edgardo Villalobos (Solar-Manufacturing)

 

The current battery that we intend to buy may be switched out for a different battery after the Mini Pathfinder is built and tested for its power efficiency. About one third of the products that will make up the Mini Pathfinder will be free of charge due to our team members already possessing certain products. Corresponding sources of expected pricing is provided under the Source column. Because the Mini Pathfinder didn’t have a cost requirement the Project Cost Allocation was set to be slightly higher than the total Expected Cost.

Spring 2017 BiPed Preliminary Project Plan

Alexander Clavel – Project Manager

Jacob Cheney – Missions, Systems, and Tests

Abraham Falcon – Electronics and Control

Mikaela Hess – Manufacturing and Design

Phong Nguyen – Manufacturing and Design

Table of Contents

Work Breakdown Structure (WBS):

By Alexander Clavel (Project Manager)

Figure 1: WBS

The Work Breakdown Structure shows the responsibilities and tasks of each member of the team. It breaks down the individual tasks and specifies exactly which division and or person it falls under. Figure 1 shows the breakdown for the BiPed Project. The structure was derived from working with the level 1 requirements previously established, the product breakdown structure, as well as the different design innovation methods we used. To set specific tasks, we had to look at what had to be done on the product as well as what we could do. These can all be referenced to the Spring 2017 Preliminary Design Document that was completed previously.

Project Schedule:

Top Level & System/Subsystem Schedule:

Figure 2

Figure 3

The project schedule gives a timeline overview of the work that needs to be done and it what time frame it needs to be completed in. Figure 2 depicts the top level schedule and the entire timeline of the BiPed project. The schedule is broken down into 4 phases which include planning, design, assembly, and project launch. The planning phase mainly consists of research required for the project as well as coming to a clear definition of the mission objectives. After the planning phase comes the designing of the BiPed. Considering that a BiPed has yet to be built using DC motors, this is proving to be a difficult part of our engineering process. Assembly comes next with project completion and project launch in conclusion.

In Figure 3 the schedule is broken down even further to specify tasks for each individual. These tasks can be traced back to the Work Breakdown Structure and include purchasing components to modeling and prototyping. Some of these jobs are ongoing throughout the project while some have specific deadlines that need to be met.

Burndown and Project Percent Completion:

Figure 4

Figure 4 is a representation of our progress by percent. The vertical axis is a measurement of the percentage of tasks that need to be completed while the horizontal axis is the number of weeks. The blue line is the ideal percentage of work that should be done while the orange line is the percentage of work that we have actually done so far. We fell behind in the beginning in terms of tasks that need to be done but we were able to make up about 30% of the work. Most of that work is still currently in progress and not yet complete.

System Resource Reports:

By Jacob Cheney (Missions, Systems, and Test)

The Mass Report shows the weight of each individual component of the system and the total of all of them combined. For some of our parts, we looked at previous semesters to get a better approximation of how much some of these components weigh. Others were found elsewhere on the web or measured by the manufacturing engineer. For the entire system, our initial calculations of the Total Expected weight came out to 392.95 grams. This lead to a Total margin of 145 grams and a Contingency of 152.05 grams.

The power resource report shows the division of current throughout the Biped system. Current estimates for each component are based on their respective datasheets. Our calculations for the total expected current came out to be 1150 mA. This left us with a total margin of 610 mA and a contingency of 660 mA.

Project Cost Estimate:

The Cost Report lists all of the parts and materials needed along with the purchase price for each. The Total Expected Cost for everything came out to $180.50 with a Total Margin of $54 and a contingency of $73.50.

Mini-Pathfinder Spring 2017 Preliminary Design Document

Martin Diaz (Project Manager)
Adan Rodriguez (Mission Systems and Test)
Moses Holley ( Electronics and Control)
John Her ( Manufacturing – Chassis)
Edgardo (Manufacturing – Solar )

Table of Contents

Program Objective/Mission Profile

Objective

By Martin Diaz (Project Manager)

The Mini-Pathfinder will follow and support a walking robot in a to-be-negotiated Battle. The Mini-Pathfinder will autonomously follow it’s respective robot and provide video support. An operational solar polar will also be used by the Mini-Pathfinder.

http://web.csulb.edu/~hill/ee400d/S%2717%20Project%20Objectives%20and%20Mission%20Profile.pdf

 Requirements

Level 1 Requirements

By Martin Diaz (Project Manager)

  1. L1-1 Mini Pathfinder shall be completed by Friday, May 19, 2017 (According to CSULB final exam schedule)
  2. L1 -2 Mini Pathfinder shall use a 3Dot Board Microcontroller with a custom SMD l2C shield.
  3. L1 -3 Mini Pathfinder shall provide video support by keeping its respective robot in view. (At a distance to be specified by customer.)
  4. L1 -4 Solar Panels on the Mini Pathfinder shall power a led.
  5. L1-5 Solar Panels should charge the battery of the Mini Pathfinder.
  6. L1-6 Mini Pathfinder shall be capable of autonomous operation.
  7. L1-7 Mini Pathfinder will also have the ability to switch from autonomous to being remote controlled, by Arxterra application or control panel, in event of autonomous system failure.
  8. L1-8 Mini Pathfinder shall be scaled in size to the Sojourner Rover. (Scale to be determined by customer)

Level 2 Requirements

By Adan Rodriguez

  1. L2-1 Mini Pathfinder Chassis shall hold 3Dot Board within its Chassis,
  2. L2-2 Mini Pathfinder shall use 6 motors to drive the 6 wheels.
  3. L2-3 Mini Pathfinder shall use a LG k10 phone for the camera system.
  4. L2-4 The dimensions of the rover should be 170.16mm(L)x125.66mm(W)x78.54mm(H).
  5. L2-5 The dimensions of the rover will be 1:3.82. scale to the soujouner
  6. l2-6 The motors shall be inside the wheels and thus not exceed a diameter of  27.86mm.
  7. L2-7 The Mini Pathfinder shall utilize ultrasonic sensors to track it’s lead robot.

Creative Solutions

By Martin Diaz (Project Manager)

During our brain writing exercise we were tackling the problem of what video system will we use and how will we implement it. Several cameras were chosen and we reviewed the pros and cons of each. We choose to try our camera phone since it has capabilities of using the arxterra app and wifi capabilities to send the video. But we quickly ran into the problem of how and where will it be placed on a small chassis. A standing phone will not work because it would interfere with solar panel placement and will not be a model of the sojourner. We concluded to have a layered structure with a phone sandwiched between solar panels and the chassis. The chassis will hold the electronics and the phone will use a periscope to achieve a forward looking view from the rover.

 

Another possible solution that we realized during our different perspective exercise was tracking a color or led on the lead robot. This idea came up after viewing our task through nature’s point of view and imagined a mouse looking for cheese. This solution will need further research.

Creativity Presentation

 

 

System Design

Work Breakdown Structure

By Martin Diaz (PM) and Adan Rodriguez (Mission and Systems)

The WBS shows what work is assigned to each division. Mission Systems is assigned to work on arduino program and arxterra control. Manufacturing is assigned to use CAD software to design the rover. ENC is assigned to make the schematic of the custom PCB.

Product Breakdown Structure

By Adan Rodriguez (Mission and Systems) and Martin Diaz(PM)

The PBS shows the components parts or finished product of each system. The diagram shows the components of what the chassis, 3Dot board and custom PCB, etc. will contain.

Electronic Design

System Block Diagram

by Adan Rodriguez (Mission, Systems, and test)

We plan to use the motor controller on board the 3Dot. Due to our rover needing 6 motors a expansion board will be needed. Expansion board is going to be our custom PCB that will contain 2 more motor controllers and interface with our sensors. Bluetooth will connect to a phone for manual control. Solar panel will connect to our battery to charge.

Interface Definitions

By Moses Holley (Electronics and Control)

The information above explains the ports of the microcontroller that is connected to the TB6612FNG dual motor drivers, I2C expansion PCB, and the Bluetooth module. Essentially, we will be using the capabilities of the 3Dot board to operate the robot remotely that controls the components on our control custom PCB.

Fritzing Diagram

By Moses Holley

The fritzing diagram gives a visual display of the interfacing at work. The I2C column mentioned in the interfacing definition is the Arduino Leonardo Board on Fritzing.The is not a specified I2C chip created within Fritzing, so we used the Leonard Board’s ports. We also mapped ATmega32u2 breakout board’s ports for the connection of the ATmega32U4 MCU. All of the wires are color coded accordingly to give an easy view of each component.

 

Sources

  1. https://learn.sparkfun.com/tutorials/tb6612fng-hookup-guide
  2. https://www.arduino.cc/en/Hacking/PinMapping32u4
  3. https://cdn-learn.adafruit.com/downloads/pdf/atmega32u4-breakout.pdf
  4. http://duino4projects.com/wp-content/uploads/2013/04/
  5. http://Ardunio_leonardo_pinout.jpg
  6. https://www.arduino.cc/en/Reference/Wire

 

Mechanical Design

by John Her (Manufacturing – Chassis)

 

The design of our rover will follow the Sojourner rover of the Pathfinder mission. It will be a scale sized model encompassing the 3dot board within the chassis. It will continue to utilize the rocker bogie suspension and will have six motors driving the six wheels. The Sojourner rover has dimensions of 65cm(L)x48cm(W)x30cm(H) [1]. The 3dot board is 69mm(L)x35mm(W) [2] and will be enclosed within the chassis. We will also be using a smart phone as the camera system. The smart phone we will be using is the LG K10 phone which has dimensions of 146.6mm(L)x74.8mm(W)x8.8mm(H) [3]. The scale model will be as small as possible to fit the dimensions of the 3dot board. Since it has to be to scale, it can only be as small as our largest part. In this case, the phone will be our largest part. The phone will lay flat underneath the solar panel array and above the chassis containing the electronics, including the 3dot board. The Sojourner rover uses solar cells that are 4cm(L)x2cm(W) [4] that are arranged to fit in a 14(L)x18(W) array.

Multiplying the lengths and the widths gives the total length of 4cm/cell*14cells = 56cm and width of 2cm/cell*18cells = 36cm wide. This gives a length to width ratio (56/36=1.556) of 1:1.56. Given the length of the cell phone is 146.6mm, a scaled down solar panel of the Sojourner with the same length will have to be 94.243mm wide which is 19.443mm wider than the phone at 74.8mm. Due to the scale of our rover, an exact replica of the solar array may not be possible and may have to just be a full rectangle shape. If we are to compare the size of the solar array from the Sojourner rover and compare it to what will fit over the phone, we can obtain our scale for our rover model which is (560mm/146.6mm = 3.819) 1:3.82. Using this scale, the dimensions of our rover should be 170.16mm(L)x125.66mm(W)x78.54mm(H). Looking at the size of the wheels [5] of the Sojourner rover, we can see that it has a wheel diameter of 137mm and a width of 60mm. If we apply the scale of our rover (137mm/3.82), it gives us a wheel diameter of 35.86mm and a width (60mm/3.82) of 15.71mm. If we make the wheels have a 2mm thickness with 2mm of clearance for the motors, this gives us the option to use a motor of at most a diameter of 27.86mm since the motors will be in the wheels. To determine the size of the chassis containing the electronics, a replica paper model was printed and measured [6]. Looking at the 1:15 scale version of the model, the solar cell array was measured at 57mm(L)x43mm(W) and the chassis was measured at 39mm(L)x27mm(W)x17mm(H). The length of the chassis is 1.46 times smaller than the solar array and the width is 1.59 times smaller. When comparing the length of paper model of the chassis to the height, the height of the chassis is 2.294 times smaller. If we apply these scales to our determined solar panel size of 146.6mm(L)x94.243mm(W) then the length and width of our chassis should be 100.3mm(L)x59.18mm(W). Then comparing the length of the of this (100.3mm) to the height, 2.294 times smaller, then the height of the chassis should be 43.72mm(H). These dimensions for the chassis should provide enough clearance to contain the 3dot board.

Sources

  1. http://solarsystem.nasa.gov/missions/pathfinder/indepth
  2. https://www.arxterra.com/3dot/
  3. http://www.phonearena.com/phones/LG-K10_id9838
  4. https://mars.jpl.nasa.gov/MPF/roverpwr/power.html
  5. http://www.kiss.caltech.edu/workshops/xterramechanics2011/presentations/lindemann.pdf
  6. http://jleslie48.com/jj_sojourner/SojournerRover_PaperModel.pdf

Design and Unique Task Description

Encapsulation Trade Off Study

by Egardo Villalobos (Manufacturing – Solar)

As the Manufacturing Engineer for the solar panels on the Mini Pathfinder, I am required to come up with a solution in in powering an LED on the Mini Pathfinder and, if possible, to fully power the Mini Pathfinder. Another thing we want to work on is the solar cell encapsulation because we’d like to find a way to make these cells modular so that a cell can easily be replaced.  

 

PLEXIGLASS

Plexiglass provides a lightweight, anti-reflective surface and is classified as a scratch resistant surface. Although plexiglass is virtually impossible to break and scratch resistant, it can scratch much easier than glass. If this material is used to encapsulate the solar cell, we’d be able to acquire it from Home Depot or other similar store. This glass would then be used to cover the panel. To get the right shape out of the glass, we could use a dremel grinder to cut to size. The size of the glass would be the same size as the panel, which still need to be measured. The downside to using plexiglass is that the solar cell needs to be sandwiched using other materials, such as resin, which costs the same as buying one already encapsulated.

Source:

  1. Plixiglass http://www.plexiglas.com/export/sites/plexiglas/.content/medias/downloads/sheet-docs/plexiglas-optical-and-transmission-characteristics.pdf
  2. Materials http://sinovoltaics.com/learning-center/materials/ethylene-vinyl-acetate-eva-film-composition-and-application/
  3. Materials http://www.dunmore.com/products/solar-back-sheet.html

 

EPOXY COVERED SOLAR CELLS

Solar cells could be bought already encapsulated with a UV resistant epoxy and are usually meant to charge phones and other toys. Each cell is independently encapsulated making it easier to remove and add new cells. These cells are also polarity based, which could require wires instead of tabbing wires, also making it easier to switch cells. Using these cells would cost about the same as buying all the materials, using the plexiglass sandwich method.

 

Sources:

  1. Array http://www.samlexsolar.com/learning-center/solar-cell-module-array.aspx

ENC Task

  • Experiment with motors to obtain torque ratings.
  • Build breadboard circuit for PCB testing.
  • Update Fritzing diagram

Manufacturing Task

  • Build or simulate Prototype
  • Solar Panel Prototype

Mission and Systems Task

  • Work on arxterra application and arduino program.

 

Spring 2017 BiPed Preliminary Design Document

Table of Contents

The BiPed Team:

Alexander Clavel – Project Manager

Jacob Cheney – Missions, Systems, and Test

Abraham Falcon – Electronics and Control

Mikaela Hess – Manufacturing and Design

Phong Nguyen – Manufacturing and Design

Program Objectives/Mission Profile:

By Alexander Clavel (Project Manager)

The customer has asked for a 7th generation robot that will be able to walk with the use of DC motors in replacement of servos. Based on the request of the customer, the bipedal robot will participate in the “end of semester” game. During the game, the robot will do battle with the velociraptor while using video support that is provided by the spider bot and pathfinder rover. With live video feed, the biped will be controlled with the Arxterra phone application to complete its mission.

Spring 2017 Requirements:

Project: Level 1 Requirements

By Alexander Clavel (Project Manager)

  1. The biped shall be able to achieve a static walk using dc motors.
  2. The Biped should be able to turn.
  3. The biped shall be able to participate in the “end of game” semester.

As stated by the customer

    4. The biped shall be controlled with the use of the Arxterra phone application.

As dictated by rules of the game

    5. The biped shall utilize a 3Dot board with custom SMD I2C shield.

As dictated by rules of the game

     6. The biped should be able to operate for an hour.

     7. The biped should be able to achieve dynamic walking.

     8. The biped shall fit within the classroom cabinets (size to be determined)

As instructed by the customer

     9. The biped shall be completed by the last day of class on Monday, May 15th, 2017.

As listed in the school schedule

MST: Level 2 System/Subsystem Requirements:

By Jacob Cheney (Mission, Systems, and Test)

  1. The BiPed shall have a Bluetooth v 4 .0 BLE Transceiver integrated circuit that will be able to communicate with an Android or iPhone.
  2. To maintain balance while static walking, the Biped shall use two servos as ankles to shift the center of gravity.
  3. The 3Dot Board shall receive commands from the Arxterra app via Bluetooth Transceiver. It will then decode and transmit data to the DC motors and servos.

E&C: Level 2 System/Subsystem Requirements:

By Abraham Falcon (Electronics and Control)

Abraham Falcon (Electronics and Control)

  1. The Biped will use two DC Motors for each hip for the walking movement.
  2. The Biped will use two Servo Motors for each ankle for a legs side movement.
  3. The Biped will use two Servo Motors for a turning movement.
  4. The Battery’s duration will last up to an hour.
  5. DC motor shall operate at 5 Volts for a static walk.
  6. Servo Motor shall operate at 5 Volts for a static walk.

Source Material:

https://www.arxterra.com/3dot/

M&D: Level 2 System/Subsystem Requirements:

By Mikaela Hess (Manufacturing and Design)

  1. The Biped will have a height restriction in order for it to fit in the closet with dimensions to be determined.
  2. The Biped will have legs designed to hold up the weight of a 3 dot board, Arduino, servos and the DC Motors.
  3. The Biped shall have an implemented design that makes the legs close together for better control of the center of gravity in order to achieve static walking.
  4. The Biped shall optimize the constant speed of the Biped for an hour by designing a leg that optimizes each length of each step in order to play the end of the semester game.
  5. The Biped should add an additional feature to the static design in order to achieve dynamic walking

Design Innovation:

Alexander Clavel ( Project Manager )

Through research of previous semesters requirements and final results, we developed our own areas of focus to create solutions for. Until now, most BiPed projects utilized servos to achieve walking, but ours will require the use of DC motors. As of yet, walking with DC motors has not been achieved so that has become our main area of focus. The Theo-Jansen approach gives us an initial approach to accomplish walking. Taking the “end of semester” game into consideration, the robot will also need to be balanced and be able to turn. Some ideas that were elicited from our creative exercises were to bring the legs closer in to allow for an easier shift in the center of gravity. Using the creative method, we devised different possible solutions for these problems.

Creativity Solution Slides

Systems/Subsystem Design:

By Jacob Cheney (Mission, Systems, and Test)

Product Breakdown Structure:

The product Breakdown Structure (PBS) is used to plan and display the outcomes of our project. The goal is to break down the product as much as possible to ensure nothing is overlooked. The hierarchical structure begins with the final product at the top followed by subcategorized elements below.

 

http://web.csulb.edu/~hill/ee400d/Lectures/Week%2004%20Modeling/e_Product%20Breakdown%20Structure.pdf

Good PBS Example (Velociraptor)

Electronic System Design:

System Block Diagram

The System Block Diagram shows the outputs for the ports of the DC motors, Servo motors, and the input for external power. The LDO 5V Regulator is used to increase the 3Dot board output voltage to the operating voltage for the Servo Motors. An Android or iPhone device with an Arxterra App will be used to control the Biped.

Source Material:

Fall 2016 Biped – Updated System/Software Block Diagrams  

 

Interface Definitions

 

Mechanical Design

By Mikaela Hess (Manufacturing and Design)

Pictured above is the initial idea that the Manufacturing engineers have designed. As can be seen above, we have the DC motors moving in the center of the body of the biped in order to have better control of the center of gravity. To make this happen, we must create a distance between the two DC motors large enough so that the two servos sized feet can be picked up and land onto the ground without disturbances. To go without the disturbances, we must create a distance of one servo between the DC motors, and an additional ⅕ of an inch of room to adjust for human error. Next, we placed the body on top of the DC motors, facing the other way in order to counteract the weight of the DC motors on either side, for better stability. This idea of having a long body was actually created from the Creative Project, where we forced a truck onto our biped design. The overall size of this Biped is to be under 10 inches. The body of the Biped is expected to be no more than 3 inches and the servo on the feet are expected to be no higher than 1 inch. With those calculations and the 1-inch radius in which the leg is designed to move around, the actual leg is to be designed in a total of 4-5 inches.

The actual walking of the biped is broken down into 5 steps here. In order to follow this design, the pictures are color coded according to the design’s components. In blue we have the representation of the circular path created by the DC motor and the pink segment. The pink segment is a sturdy piece of material that is directly linked to the DC motor and has a loose joint connection to the leg of the Biped, or the yellow piece in the picture above. Both legs start off in position one where the legs are bent and at rest at x and y equal zero on a radian circular graph. One leg then shifts its weight over by moving the leg over at an angle theta from resting position to the side by a servo. Once that is done, the DC motor then turns on and moves the pink segment to the negative pi over two positions on the same radial circular graph. This makes the body shift upward and lifts the other leg along with the body. After the segment goes to negative pi over two, it will move to pi on the radian graph, the ankle with resume its original position, causing the biped to take a step and then the legs will be programmed to reach equilibrium and resume its original position. Once that happens, the other leg repeats the same process and vice versa. Overall, the Biped should walk.

Once this design was created, I sent more photos and information to a Michael Oran Tobin, a Control Systems Engineer for California with PE Certification #CS7494. Once I had explained the servo use and parameters of the total design, it was made clear that my design would fail. What I failed to notice was the joint at the knee and the segment (yellow and pink where they connect), was that because there was no control onto that joint that the body could give out. As well, my design required precision that only DC motors with rotary encoding. A recommendation was made to use either a memory wire that straightens when current is given and loosens when there is none, or to use a servo at the knee for better control. The servo at the knee was decided to be a better option due to the memory wire being in early production and may not be able to handle the weight of the servo and leg. After going over the entire design, Michael Tobin strongly recommended doing more research on how humans walk and to consider how humans move their feet towards the center of gravity line to walk and then moves outward for better balance. As well, he suggested using a second wheel for better control of the joints. These pictures and ideas are pictured below and were made by Michael Tobin.

Overall, the design needs to reconfigured. More servos and research need to be done in order to create a working and walking Biped. The difficulty in this task is that most designs for biped are made using solely servos or stepper motors, which means this Biped leg design has to be made from scratch, but with help from other engineers and more research, it should be made possible. Also, a discussion with the project team and customer should be set up in the near future to discuss the use of more servos or motors.

Mechanical Design (Continued)

By Phong Nguyen (Manufacturing and Design)

This picture shows us a biped design based on human structure (hip, knees, and feet). As shown above, we decided to design the Biped with two DC motors for each hip, two servo motors for each ankle, and two Servo Motors for a turning movement. The DC motors are responsible for lifting up the whole leg while the servo motors will be used to shift the center of gravity. If we want to turn left or turn right, the servo motor at ankle will be able to accomplish that like last semesters biped. Under the foot, we will use high friction material such as sandpaper, rubber, or plastic. 

http://robogames.net/symposium/2007/07-108-Vaidyanathan-AnnaUniv-AnalysisofBipedalWalkingRobot.pdf

http://embeddedprogrammer.blogspot.com/2012/08/simulation-of-humanoid-robot.html

Design and Unique Task Descriptions:

Electronics and Control

By Abraham Falcon (Electronics and Control)

Biped Electronics and Control Design Process/Analysis

According to 3Dot Board specifications, it only supports 5V Turbo Boost for driving DC motors and for the Servo Motors to be operated at 5V. Using a rated 12V DC Motor to be power at 5V to measure the current draw at no load conditions and stall current to know the maximum current the motor will use to determine the Biped Battery total current it can supply. Also, for a Servo Motor to be power at 5V to measure no load current and stall current to determine the maximum current it will draw to know what battery is needed.

 

Biped Electronics and Control Tasks

  • Choose DC Motors to be compatible with the 3Dot Board’s TB6612FNG Dual Motor Driver.
  • Choose Servo Motors to be compatible with the 3Dot Board’s Two 3.7v Micro and Ultra-Micro Servo ports using a Voltage Regulator.
  • Perform Trade-Off Study on DC Motors to select for Biped for the 3Dot Board.
  • Perform Trade-Off Study on Servo Motors to select for Biped for the 3Dot Board.
  • Do Servo Motor Analysis to know what are the specs on a load condition on the Servo Motor and know how much mass it can handle at its maximum current.
  • DC Motor Analysis to determine the maximum current under a load condition and know what is the maximum mass it can handle.
  • Measure all currents of the motors to know the total current for the Biped Battery’s Specifications.
  • Select a Power supply that will handle all the current that the motors are consuming.
  • Create a Fritzing Diagram and test it on a breadboard to assure its properly working.
  • Use Eagle CAD to create an electrical schematic (PCB).
  • Using Arduino IDE to program the DC Motors and Servo Motors to work properly and to be successful.

Source Material:

Fall 2016 Biped – Updated Schematics  

http://arxterra.com/goliath-fall-2016-preliminary-design-documentation/

Manufacturing and Design

By Mikaela Hess (Manufacturing and Design)

Manufacturing Tasks

  • Measure the cabinet’s height and reduce it by one inch and make that the height requirement (so there is room for error).
  • Perform Trade-Off studies to see what implemented structures are used to make a robot walk using DC motors.
  • Weigh out the servos and DC motors, 3 Dot Board, and Arduino to know the total weight capacity.
  • Design a foot that has better grip and curvature for a smoother transition in steps.
  • Perform a Trade-Off study to see what materials are the lightest and sturdiest material to handle the weight.

 

Biped 2016 Fall – Final Documentation

Introduction Project Overview

Project Objective

Team Biped will produce a two legged 6th generation toy biped robot that will replace the traditionally used servos with a dc motor and achieve static walking. By utilizing the 3Dot Board, the robot will participate in the end of semester, December 14th, 2016, game called: Save the Human.

Mission Profile

Biped shall compete, alongside other toys such as Goliath and Velociraptors, in an end of semester approximately hour long game: Save The Human. Biped should successfully walk, using Goliath’s live video feed as the field of view, from the opposite end of the room to the finish area without coming into contact with a Velociraptor. The Biped will  maneuver through multiple obstacles by turning through walls, sensing color pads, and stepping through uneven terrain placed on top of Linoleum floors.

build4

Project Features

A key component of our design is replacing the ankles with servos. The ankle servo eliminates having to use two dc motors to accomplish a pivot turn. The placement of the servos provides a strategic way to balance on on foot and then turn the entire body to face the desired direction.

 

turning

Requirements

System Block Diagram

Interface Definition

Interface Matrix and Cable Tree

 

Mission Command and Control

Software Design

Arxterra App Communication

Custom Commands

custom-comands

Electronics Design

Component Selection and Trade Off Studies

Electronic Experiments

 

Firmware

PCB Schematics

PCB Layout

lay1

lay

Hardware Design

Hardware Experiment

Hardware Selection – Trade Off Studies

 

Verification and Validation Test

Project Status

Updated Mass and Power

Cost Report

 

Vendor Item Unit Price Quantity EE Dept. /Total EE Dept. Extended Cost
1 LOWE’S Miscellaneous Hardware 54.31 54.31
2 Mouser Electronics 27.82 27.82
3 Pololu Hardware (Motor/Gearbox/ Wires) 9.55 9.55
4 Hobby People Electronics (Battery/ Connectors) 16.33 16.33
5 Oshpark Color Pad PCB 0.60 0.60
6 Oshpark Shield PCB 20.45 20.45
Total: 129.05
Allocated Budget 125.00

Schedule and Burndown

Resources

[1] Project video

[2] PDR

[3] CDR

[4] Eagle Design

[5] Biped Code

[6] Solidworks 

[7] Animation/ Simulation

[8] PCB layout