Browsed by
Category: Team Updates

4/26 Team Update

4/26 Team Update

Zeyi worked on integration this week and improving the user interface. He changed the map to have multiple items on a single node to help the product become more robust. He also changed the node list and item list to display the remaining nodes and items on the planed route. Overall, he has more descriptive changes on his personal update. Zehong further improved his algorithm and further integrated with Zeyi’s user interface. There were some bugs when integrating, and Zehong…

Read More Read More

4/19 Team Update

4/19 Team Update

This week, integration was the main theme for our group. We also had some individual tasks we had to do to help smoothen the integration. Carlo’s focused on integrating the range sensor code with Zeyi and Zehong’s work. He also focused on altering the design to improve the feasibility of the sensors. Finally, he has been preparing for the demo and methods to present the sensors in the presentation. To get a more detailed description, please read his weekly update….

Read More Read More

4/12 Team Update

4/12 Team Update

Zehong mainly worked on updating the algorithm further to add additional details. The algorithm now can start and end at different nodes. This helps decrease the limitations of the algorithm. In addition, Zehong focused on generating maps this week to help showcase exactly what is going on. He then ran multiple tests to make sure he is accounting for all possible scenarios. For more detailed descriptions, please read his update. Zeyi continued on improving the user interface and the additional…

Read More Read More

4/5 Team Progress week 8

4/5 Team Progress week 8

This week, during our meetings, we have discussed and planned for methods of integration for week 9 and 10. Everyone in the team has made substantial progress in their individual components. Zeyi has finished the majority of basic functions of the User Interface for our website. The intergration portion would be intergrating to Zehong’s algorithm to calculate the most optimal path and planned path given by the algorithm. A more detailed description of Zeyi’s progress is in his weekly report….

Read More Read More

3/29 Team Progress week 7

3/29 Team Progress week 7

This week, we were able to meet a few times to discuss our progress and what we would need to work more on in the following weeks. Zeyi has been continuing to work on the website and creating that interactive portion of our project. A more detailed explanation can be found in Zeyi’s personal weekly update. Zehong has been focusing on creating the algorithm and user test cases to midigate exceptions to the program. A more detailed explanation can be found…

Read More Read More

3/14 + 3/22 Team Update Week 5 + Week 6

3/14 + 3/22 Team Update Week 5 + Week 6

3/14 The week of Spring break, our team mainly wanted to get the physical components ready and begin the initial phase of creating our physical portion of our project. This week would be the transition between the planning and initial setup. We communicated mainly virtually as most of us were not at the same location during spring break. We also began with setting up our sensor testing. We felt it was important to start working on the physical components of…

Read More Read More

3/8 Team Progress week 4

3/8 Team Progress week 4

This past week we placed the final orders for all our parts, began the initial assembly of the AutoCart system, started interfacing the Raspberry Pi with the line following sensors, and are working on the user inteface that customers will interface with. These are all being done in parallel in order to maximize efficiency. We are striving to have the line following sensor interface and user interface done by the end of spring break in order to start system integration…

Read More Read More

3/1 Team Progress Report Week 3

3/1 Team Progress Report Week 3

This week we worked together on finalizing the design of our AutoCart. We first worked creating slides to convey our design during the presentation. After getting feedback, we worked on modifying our design and putting it down in words in a design document. During the process, we also delved deep into the sensor interfaces and Roomba api to make sure as much as possible that there are no compatibility issues.

Zeyi and Carlos Progress Report Week 2

Zeyi and Carlos Progress Report Week 2

Looked into how the user interface would communicate with the Raspberry Pi. Studied the python interface web socket (https://websockets.readthedocs.io/en/stable/intro.html). Decided to keep the user interface local on the Raspberry Pi, and have it displayed to user through a touch screen (Pi Foundation Display – 7” touchscreen). Researched the rangefinder and load sensor. Decided on load cell amplifier hx711 and ultrasonic module hc-sr04 in the end. Looked into how the hardwares listed above could be connected to the Raspberry Pi. Added the…

Read More Read More

2/16 Carlos and Zehong Progress Week 1

2/16 Carlos and Zehong Progress Week 1

We have found 2 separate iRobot Create API python wrappers that we want to test on the Roomba in order to verify that all of the listed functions work as intended. The first API that we found is: https://github.com/simondlevy/BreezyCreate2 . And the second is: https://bitbucket.org/lemoneer/irobot/src/default/ The second API claims to provide all of the functions from the original iRobot Create API (linked below) and is the one we will choose if it truly has all of the functions implemented. Otherwise,…

Read More Read More