Week 4 (Sept. 19, 2018): Skimming through the Python Program

Today, after a visit from Colin, who was a tremendous wealth of knowledge as he was on the Small-Scale Controls team last year, I began sifting through the Python Programming in order to prepare for understanding how the Raspberry Pi operating the LCD touchscreen for user interface is programmed. I plan on taking the lead on the software aspect of the controls system, while David will be in charge of hardware for the most part. However, we will work together as much as we can as the two aspects are dependent on each other: the hardware cannot function properly with the software, while the software is useless if it has nothing to be implemented upon.

Last year’s Python code is found on the team’s Google document “Small Scale Controls ME 195B Term Paper” in Appendix 4 on page 55.

I was able to read and understand the first half of the program due to Python’s simple syntax as well as its similarity with Java, C, and Arduino. For example, the purpose of the first chunk of “if-elif” statements is as follows: if the XBee module has checked in a Station 1, display “01” on the LCD touchscreen. The XBee module is the wireless communication module used to communicate between the Arduino, located inside each podcar, and the Raspberry Pi, located inside the LCD touchscreen for the mobile application.

To make this happen, the RFID tag and receiver will determine if the pod car has arrived at that station; this signal will be sent to the Arduino in the pod car; the Arduino will communicate with the XBee module #1 attached to it; XBee module #1 will wirelessly communicate with XBee module #2 on the Raspberry Pi within the LCD touchscreen; lastly, XBee module #2 will tell the Raspberry Pi if the podcar is indeed at Station 1.

Comments

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

Patrick Barrera's Progress for Spartan Superway

Search This Blog