Skip to main content

Week 5 (Sept. 26, 2018): Presentation #1 (Goals & Specifications) Reflection & Gimbal Motors


Today, we delivered the first out of three Senior Project Presentations. The objective of our presentation was to discuss our team goals as well as our refined, conclusive design specifications.

Although we stated, in our Presentation #1, that I would oversee the software side of the small-scale model and David would be in charge of the hardware, our duties will more than likely overlap with each other due to the interdependent nature of controls and mechatronics systems. In other words, a circuit and a controller are meaningless without the hardware, and the hardware, such as actuators, cannot be controlled without a programmed controller and driver. And, once again, our duties will also overlap with Small-Scale Bogie and Small-Scale Track, with more interaction with the Bogie team due to the bogie-motor connection.  

Having said this, at the conclusion of our presentation, we received some feedback from Dr. Furman. He brought to our attention brushless gimbal motors, as is used for the cameras found on commercial drones, as another consideration for the selection of the motor to be connected to the bogie. I performed some research into these types of motors.

Brushless gimbals are wound for very low speed (i.e. lots of turns of thin wire) and specifically made to be used in fine control applications. They are A good place to purchase them is at iflight-rc.com. The one found on the website, the iPower Motor GBM5208H-200T, can lift 4 kg-cm, which is equivalent to 0.392 N-m. They are 63 mm in diameter and 24.5 mm in height, making them much smaller and However, it does require 11.1 V to operate and is more expensive, compared to the cheaper 5 V servos I have experience with, making our decision between using a gimbal or servo motor undecisive once again. Although this website does discuss the advantages of each, we still have to consider the power requirement of each motor: 11.1 V will require a larger battery pack compared to 5 V. We will have to consult with the Bogie team to determine what kind of motor will be required to motorize the pod car.   

Comments

Post a Comment

Popular posts from this blog

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

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