| Week | Brian | Gabriel | Group |
|---|---|---|---|
| Week 1, May 2th – 8th | Soldered headers to RTK boards, measured and tuned cutting blade to spin at 5k RPMs, and gathered parts to build docking station. (2 hours) | Built test tank for remote troubleshooting and started compiling code for function. (2 hours) | Quick meeting on how to proceed building the mower. (20 minutes) |
| Week 2, May 9th – 15th | Created the Docking station and installed known working items. (2 hours) | Researching and developing code for movement and GPS integration. (2 hours) | First class meeting with Prof. Notash. Provided updates on on our status and where we are going. We also met up as a group to exchanged components and discuss our next steps. (1 hour) |
| Week 3, May 16th – 22nd | Updated block diagram and flowchart, installed blade shroud, and started creating electronics enclosure. (5 hours) | Worked on code for mower movement. Tested moving forward, backwards, and turning in place. Further research on RTK coding. (5 hours) | Class meeting with Prof. Notash. We discussed the current progress and our next tasks we wish to cover. (30 min) |
| Week 4, May 23rd – 29th | Installed most of the electronics in the created housing and started wiring up the system. Begun research on the L298N h-bridge and how to integrate into the project (6 hours) | Tested mower movement on grass. Tested different speed settings in the coding. Increased overall mower speed by 50%. Created two alternative cutting paths using python. Further research on RTK coding. (5 hours) | Class meeting with Prof. Notash, discussed current progress and suggestions from the industry experts. In our group meeting, we discussed integration of the RTK units into the project. (2 hours) |
| Week 5, May 30th – June 5th | Fully integrated the L298N H-Bridges and full power tests. Made first movement tests on the mower unit itself. Rerouted power wires for a better look. Modified code to work with mower unit better. Started research on wireless controls. (12 hours) | Performed several tests with the GPS module including an accuracy test, a mower handheld response test and a movement test on the ground. Setup basic code structure for mower auto movement. (7 hours) | Meeting with Prof Notash resulted in suggesting further research on H-Bridges and creating a skid plate for the battery. Team meeting was short, code was transferred over from test mower to the PALM mower and discussed troubleshooting with the RTK units. (2 hours) |
| Week 6, June 6th – June 12th | Modified Rasp Pi to have 90 deg HDMI cable and 2 USB extenders for easier testing and data input. Updated power button with 12V 3A push button. Finished Wiring the cutter blade power system. Updated controller code to activate cutter blade. Performed power drain test discovered Rasp Pi has no standby or sleep mode. researched use of Witty Pi board for power savings. (6 hours) | Setup RTK base/rover configuration which allows for much greater accuracy. Performed tests in base/rover mode. Worked on GPS waypoint code, and compass code. (6 hours) | Meeting with Prof Notash resulted in suggesting GPS accuracy tests under obstructions like trees. The group got met at to perform GPS tests in an empty parking lot and to discuss the the work to be done in the following week (3.5 hours) |
| Week 7, Jun 13th – June 19th | Started to research develop controller apps and GUI for the mower. Reorganized wiring for easier identification. Upgraded Rasp Pi with Witty Pi addon board for power management. Troubleshot GUI interfaces and phone apps for remote access. Finished building Electronics housing. Performed systems tests to verify power controller board. Started drafting design for safety bumper sensors in Fusion 360. Updated website documents. (32 hours) | Worked on integrating the compass code into the GPS code (6 hours) | Meeting with Prof Notash with updates to controllers and GPS testing. Recieved approval for Witty Pi addon board. Group meeting for next steps in controller development and GPS functionality. (1.5 hours) |
| Week 8, June 20th – June 26th | Started testing charging time and run time of the mower. Further organized wring. Started creating Schematics. (12 hours) | Worked on refining GPS and compass integration. Worked on allowing user to select initial values for program variables and having the program permanently save those variables for later use even after mower shutdown. (7 hours) | Group meet up together to perform system tests and coding tests on the mower for automation. (6 hours) |
| Week 9, June 27th – July 3rd | Upgraded the cutter blade H-Bridge, upgraded the front bumper sensor flaps to larger setup, integrated inductive charge system from the docking station to the mower, conducted charge/discharge tests. (12 hours) | Worked on obstacle sensor coding and integration with main code project. Worked on further refining compass and GPS code. Worked on design report. (4 hours) | Meeting with Prof. Notash requested progression on inductive charge system and documentation. No group meeting, we communicated with each other on what we were to do and kept each other updated on progress throughout the week. |
| Week 10, July 4th – 10th | Worked on inductive charge booster circuit, created drawings and tables for the report, tested mower run time on full battery, Applied Loctite to mower screws, updated website and added 35 pages to the report. (26 hours) | Worked on refining all aspects of mower code. Tested each feature of the mower in various scenarios. Researched GPS information. Worked on report. (22 hours) | Meeting with Prof Notash resulted in changing inductive charge booster specs. Requested more work on Report. Quick team meeting on work capacity distribution. |
| Week 11, July 11th -17th | Continued working on the report, created tables and figures. (8 hours) | Worked on report, finalized coding, and testing (15 hours) | Meeting with professor to discuss important missing information for next meeting |
| Week 12, July 18th – 24th | Reorganized and finalized the report, updated website. (10 hours) |