Skip to main content

Week 20 (Feb. 27, 2019): Power Electronics – Battery & Amplifier


Since last week, I have been working on the current amplifier for the induction charger.

We decided to abandon using the TPS53313 step down voltage regulator-current amplifier IC (rated at a maximum of 6A continuous output current) because we found that supplying +5V to a 3.7V LiPo battery was possible and safe. Additionally, charging a LiPo battery at 6A was found to be dangerous; the battery should be charged at 25% of the capacity rating (.25 x C), or .25 x mAh. In the case of the 6600mAh battery, it should be recharged at a rate of 1.65A or less. The last reason is that dealing with a surface mount device (SMT) is a bit difficult.

I started out using a BJT NPN transistor (model: 2N3904), something I was most familiar with. However, its datasheet states that it has a 200 mA maximum continuous collector current rating. This is a significantly low current. Most, if not all, fast charging adapters today have a 2 A charging rate. While I don’t want to charge the LiPo batteries at 2 A, since it could be dangerous (it’s recommended to charge at 0.25C, or 25% of the battery’s capacity.

Instead, I am planning to use another type of BJT NPN transistor, specifically the MJE270G Darlington Pair transistor, which has a maximum continuous collector current rating of 2A (https://www.mouser.com/datasheet/2/308/MJE270-D-110810.pdf).

Additionally, instead of using the 7.4V 2600mAh LiPo battery that the Small-Scale Controls Team last semester used, I am aiming to use a 3.7V 6600mAh LiPo battery instead. The rationale behind this possible change is because the 6600mAh battery has a higher capacity (6600mAh), meaning the more charge it will hold and the longer it will take to discharge, being able to hold out much longer before being charged again. So, for the 6600mAh battery, a safe charging rate is 0.25 x 6.6Ah = 1.65A. But just to be even safer, 1.5A would probably safer.  

After some testing last week, 3.7V can indeed power the Arduino MEGA (which is normally powered at 5V) and a 12V DC motor, albeit it provides less power to the Arduino and the motor. However, there is still more than enough power to drive the gimbal motor at our target speed of at least 1.084 m/s. As a side note: at 3.7V, the clock speed is approximately 16 MHz, while at 5V, the clock speed is approximately 20 MHz (http://www.gammon.com.au/forum/?id=11497).

Comments

Post a Comment

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...
Post a Comment
Read more

Week 26 (Apr. 10, 2019): Programming – Python and Arduino Communication

The Python code and the Arduino code are able to run successfully on their respective boards, i.e. the Raspberry Pi in the tablet and the Arduino in the pod car. However, the Raspberry Pi is having issues sending data to the Arduino via the XBee RF (radio-frequency) module, specifically the user-input data. Whenever the user inputs the pickup station, destination, and selects a pod car, the Serial Monitor on the Arduino IDE does not show any of the data. Investigating further, we plugged the XBee module into one of our laptops, then opened the XCTU software’s (the software which deals with RF modules) Serial port as well. Now, whenever the user inputs the stations, we can see on the XCTU Serial Monitor that the receiving XBee does get the pickup station, destination, and pod car number, but the three inputs are all found between jumbles of random characters. As displayed in the screenshot of the XCTU software below, if the user inputs pickup station 2, destination station 5, and sele...
Post a Comment
Read more

Week 29 (May 1, 2019): CAD of Induction Charger Hub & Podcar Door, then 3D Printing

This week, while David worked on the Raspberry Pi and the Arduino code, Patrick completed the CAD (computer-aided-design) models. We had to create 3D solid modeling of two parts: the induction charging hub to hold the induction transmitter coil and the pod car door to hold the induction receiver coil. Over the weeks, the CAD models underwent several revisions. The induction hub saw two revisions, with the third design being the final version. Because the 3D printer available to us in the shop, the Prusa Mark3 i2, had a bed length of 10 inches, we had to restrict the length of the charging hub to a safe 9.5 inches. Version 1 simply entailed us placing the hub on the side of the bracket and then screwing it into place on the bracket’s side via the two holes at the top: For version 2, in addition to placing the hub on the side of the bracket and then screwing it into place on the bracket’s side via the two holes at the top, the bracket would wrap around the two bracket...
Post a Comment
Read more