What I personally accomplished this week:
This week I worked with Justin and Sean on refinement of our nvaigation, demo, and integrating some reprinted parts, as we encountered navigation and structual integrity issues on sunday night.
Progress Status:
I have not printed the new storage attachment yet, but I am also not really worried about that, as it would not affect any of the functionality of the rest of the system. For the parts of the system that matter, we are on track.
Deliverables for next week:
Print the storage attachment
Continue to work on navigation and the final demo with Justin and Sean
Verification:
Sean and I performed verification testing for Physical movement/battery runtime. For physical movement, we ran basic movement scripts for moving/turning at different speeds and verified that we could go a desired speed. For example, if we wanted to go ~0.15m/s for mapping, we would need to have our left and right motor duty cycles at 18 and 21 respectivley. For our desired speed of 1m/s, the motors no longer had to be run at different speeds, as we were now in the standard duty cycle operating range for the motors (41-91), meaning that we can move properly. For the battery testing, we just charged the battery and had the system run everything while doing loops at ~1m/s. We could do this for over 45 minutes repeatedly, so we well exceeded our goal of a 30 minute runtime. Movement and power working properly means that we can properly direct the robot, so our constraint becomes giving the proper directions through navigation, not following them.
More testing was done as a group of 3, so see Justin’s report for that.