Skip to main content

Week 21 (Mar. 06, 2019): ME 195B - Presentation #1 (Prototyping Stage) Reflection

Today, we presented our first presentation of our second semester of ME 195B - Senior Design Project, making it our 4th presentation overall, throughout the entire duration of senior project, since last semester. 

Please refer to our Presentation #1, embedded below. 

Up to now, we have gathered all of our major components and are starting to prototype one small-scale podcar. Although, if we find that we need to buy a smaller component, we do so immediately to get ahead of the delivery time. Besides the gimbal motor and the accompanying ESC (electronic speed control), we have tested all the parts and have found that they all work individually. 

Despite the fact that there's limited information on gimbal motors on the internet, we found some Arduino code to run the gimbal motor and ESC. However, regarding the connections, we have all but one connection - the connection between the ESC and the battery; all we need is an XT60 connector to connect the ESC to the battery; it is currently in delivery. After the presentations today, we will make the gimbal motor connections and test the motor. 

Following our Presentation #1, we received some questions from Dr. Furman primarily about the gimbal motor. Because we don't yet have the XT60 connector, and thus haven't been able to test the gimbal motor, we could not answer his questions properly. 

Dr. Furman asked us two questions that we would now like to retroactively answer. 

The first question was if we were sure that gimbal motors are intended to be run slowly. Our answer is: not necessarily. The speed can be controlled, albeit to a limited degree, with a potentiometer connected to the Arduino. The Arduino will read analog readings from the potentiometer as its knob is turned. Accordingly, the Arduino code will set a proportion to scale the potentiometer readings to a speed value to write to the ESC. 

The second question he asked us was if we will be controlling the speed of the motor. To answer, we will find a good speed and then set the potentiometer reading permanently. We will also make the motor start at a lower speed, and then accelerate to the desired speed. We will accordingly gear down the motor, as it seems the lowest possible speed of the gimbal is still too fast. 

After completing these prerequisite actions, we will then ensure all the components to run together and complete one podcar. We will have to complete one podcar prior to Presentation #2 so that we can present good progress, and from there, it will be easier, as we would simply have to replicate our actions to the other podcars.

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