Milestone 1 Report

Milestone 1 Report (Prepared by: Joshua Burkhart)

Intended Progress: Describe the features/components you wanted to complete by this milestone.

By this point in time, we had intended to research parts, order parts, receive parts, assemble the GPS shield, and begin interfacing the GPS Shield with an arduino.

Progress To Date: Describe what the team have been doing towards completing the tasks involved in realizing the current milestone objectives.

Progress to date is on schedule with our goals. Currently, we are configuring a virtual machine in the eos lab that will enable us to interface with the arduino microcontroller.

Projected Progress: What will you do in the next project phase in terms of code development, testing, integration and debugging. How will the team adjust its workload in order to compensate for current rates of progress in the chosen development areas, and how will work towards the next milestone be organised.

The current project phase involves interfacing the GPS unit with the arduino microcontroller. Code development will be in C with special regard payed to minimal resource use. Testing our work will consist of using a multimeter to test power is going from arduino to correct pins on GPS unit. Debugging may include resoldering resistors, capacitors, or integrated circuits on the GPS shield; reconfiguring virtual usb, serial, or other ports for the guest vm in the eos lab; or correctly configuring proprietary compilers for use with the arduino microcontroller. The current rate of progress is on-schedule. No scheduling adjustments are required at this milestone. Work will continue as planned towards the next milestone.

Problems Encountered: Comment on any significant problems with technical progress or group management. This is a chance to get input from the team's instructor on fruitful avenues for addressing technical problems or group management issues.

• The electric motors and chassis did not include a voltage controller, foreseeably  making variable speed difficult.
• The physical lab computers in both arch and eos labs include a c compiler that is incompatible with the arduino microcontroller. Because the system administrator is weary of installing a compatible c compiler, we will use a virtual machine.

Conclusion: Brief overview of the status of the group and project overall.

In conclusion, though some difficulties have been encountered, we remain on schedule.