Skip to main content

Week 22 (Mar. 13, 2019): Battery Clarification and Boost Converter

To begin today’s post, we will make a slight rectification to our earlier posts. In prior posts, we stated that we are going to use a 3.7V Lithium-polymer (LiPo) battery. However, more specifically, we are using a 3.7V Lithium-ion (Li-ion) battery. While there are some differences between the two types of batteries, since they are both lithium-based batteries, they utilize the same chemistry for the most part.

Li-ion batteries are the ones that are found in most cellular phones. We found that these batteries are more favorable to use in our project than their LiPo counterparts. Whereas LiPo batteries suffer from a shorter lifespan, Li-ion batteries are more efficient and have higher power density, meaning they contain a large amount of energy in a small package. Furthermore, Li-ion batteries cost less than LiPo batteries. Even though Li-ion batteries are “potentially dangerous”, we won’t be driving heavy loads, and we will be testing in an open environment, rather than a confined space. A comparison of the two batteries is best summarized in the image below:  


The second part of today’s post concerns the powering of our circuit. In a post we made a few weeks ago, we mentioned that the 3.7V battery would be good enough to power the Arduino MEGA. According to this website, at 3.7V, the MEGA’s clock speed is approximately 16MHz, while at 5V, the clock speed is the complete 20MHz. So, running the MEGA at 3.7V, would run it at 80% of its full clock speed. We initially tested whether or not this would work and power the Arduino. It did work with just the Arduino and the RFID. However, we found that it did not work with the Arduino, RFID, LED, ultrasonic sensor, and motor driver all connected because while the RFID runs at 3.3V, the LED and ultrasonic sensor both run at 5V. Thus, we looked for a way to resolve this issue.

Our solution came in the form of a boost converter, which increase voltage at the cost of decreasing current. We chose the MT3608 boost converter, and after testing, we found it was able to boost the 3.7V battery voltage up to the desired 5V (with a maximum of 28V) to power the circuit: the Arduino, RFID, LED, ultrasonic sensor, and motor driver. We chose this particular board for several reasons:
 - the boosted voltage can be easily adjusted with the on-board potentiometer;
 - it’s easy to integrate into our circuit;
 - it contains a protection circuit to avoid over-voltage charging;
 - it possesses lower operating voltage (i.e. minimum voltage required to power it);
 - it could be delivered the quickest as it was from Amazon Prime, and it was a pack of 10. 

The other option we had was to use OPAMPs, but we couldn’t find an OPAMP with low enough operating voltage (i.e. minimum voltage required to power it), unless it was a surface-mount chip (SMT). For example, if got an OPAMP that required 9V to operate, we would need a 9V battery, and the mini-battery charger we will be using can only charge up to 5V. The 9V battery would have to be recharged with the large Lithium battery charger, which cannot fit into the pod car. This would defeat the purpose of using a more portable charger and the implementation of induction charging. An image of the boost converter is shown below, as well as the Amazon purchase link with all of the product details:   


On a final note, Dr. Furman listed some places for fabrication during class. Although this was directed more towards the track teams, this was helpful in case we need to manufacture something small: Allen Steel in Redwood City and Master Metal and Vender Bender on De La Cruz Blvd in San Jose. 

Comments

Popular posts from this blog

Week 30 (May 8, 2019): Prototype Evaluation Day, Final Circuit, Incorporating 3D printed parts, Final Presentation, Posters, & Maker Faire

Today, we held Prototype Evaluation Day. Like the rest of the senior project classes, the advisor walks around the classroom, evaluating the senior project apparatuses, asking the student teams to demonstrate their devices, and explain their design, though processes, and results. Dr. Furman and Ron examined and inspected the Full-Scale model, then the Half-Scale model, and lastly, us, the Small-Scale Team. We had completed our circuit to power one pod car and one of the two induction charging stations prior to Evaluation Day, so we were able to successfully demonstrate the pod car driving around the track as well as the induction charging. While we were still troubleshooting issues with the tablet’s Raspberry Pi communicating with the Arduino, the Arduino is still capable of operating on its own, so we could at least demonstrate the motor driving the pod car around the track and through the offline stations. Depicted below is our final circuit that powers the pod car: Dep

Week 28 (Apr. 24, 2019): Final motor selection – Mini-Stepper Motor

Since last week, we have been trying to run the new brushless DC motor; however, it is still difficult to control, let alone its speed. Therefore, we had to pursue our alternative motor, the mini-stepper motor that runs at 5V. Found in Arduino starter kits, this mini-stepper motor is accompanied by its dedicated motor driver board, the ULN2003, which is a chip containing a series of Darlington pair transistors. An image of the stepper motor and the ULN2003 board is shown below:   Sources: https://www.adafruit.com/product/858 https://www.amazon.com/gp/product/B01CP18J4A/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1   We were able to successfully run the new mini-stepper motor with the sample code included with the Arduino starter kit. One benefit to using the sample code is that it utilizes the Stepper library’s functions. One use function is the setSpeed( ) function, which allows the user to set the RPM speed of the stepper motor. We found that the maximum spe

Week 9 (Oct. 24, 2018): Presentation #2 (Primary & Alternative Design Concepts) Reflection & Eliminating GPS as a Possibility

Earlier this week, to prepare for our presentation on October 24, I looked into different GPS modules. Unfortunately, I concluded that it was not possible to implement one. Recently, I learned in my ME 190 class (Mechatronics System Design) that GPS is not very accurate, as it does not have a fine resolution. Within a 10-meter radius, the satellite cannot distinguish whether the object is at the 1-meter mark or if it’s at the 9-meter mark; in other words, the object that the GPS is attached to will just be a big dot on the map. To illustrate my point, a map is shown below. The top image depicts the position of the GPS user represented by a large dot. That dot covers 10-meters, as the bottom image shows smallest measurement that that can be achieved by zooming in is 10-meters. After travelling nine-meters in one direction, the GPS has not updated the location of the dot. Additionally, the object would have to be travelling faster than 1 m/s; we aimed to have the podcar travel at around