Repository for Autonomous Vehicle Challenge (AVC) by A-Team, as part of ENGR101 at Victoria University of Wellington
- Ahmed Mohamed (Ahmedmohame1)
- Hardware (Designing shape of robot and 3D printing, working with others in their hardware-related jobs)
- Andrew McGhie (mgoo)
- Networking (Communicating with starting gate)
- Class Planning (Planning how the different class will fit together)
- Code Integration (Merging all of our code together)
- Benjamin Percy (Radroaches)
- Wall Quadrant Tracking (Making robot react to processed information from IR sensors)
- Sensors (Making use of camera sensor information)
- Daniel Bakes (CenturionBakes)
- Motors (Making the robot move and coding movement functions)
- Dylan Chong (dylan-chong)
- Project Management (Distributing tasks, overseeing project)
- Devops (Git management, setting things up and making sure everyone can get started coding)
- PID (Controlling direction of the pi, reacting to camera data)
- Jonah Ease (dayyad)
- Sensors (Making use of IR sensor information)
- Navigation (Algorithms to navigate through the line and wall mazes)
--- //: ********************************************************************** //: **********************************************************************
[//]: **********************************************************************Note: This log hasn't been updated by most of us
(based off milestones from project plan)- Everyone: Produce AVC Plan
- Ahmed, Daniel: Get robot to move
- Dylan: Sort out a GitHub repository
- Dylan (+Everyone): Distribute roles
- Andrew: Start writing Networking code
- Ahmed: Begin planning ideas for model
- Ahmed, Daniel: Get motors working
- Ben: Be able to SSH into Pi
- Daniel: Begin making robot move in straight line
- Dylan: Organise team meetings
- Jonah: Start looking up how to convert IR sensor readings into distance
--- //: **********************************************************************
- [x] Dylan: Move logs to GitHub readme and have it be up to date None - Dylan - Moved logs from AVC Team Notes (Google Doc) to GitHub readme - Added checklists from Team Notes doc and added tasks for next week - Removed all the movement branches from GitHub to prevent anyone from committing to them (I had to merge the movement-straight-line branch and then delete the AVC_movement file to do so). None--- //: **********************************************************************
- [x] Everyone, Ahmed: Complete Skeleton robot design (functional parts and structure only) - Position of sensors have been planned - [ ] Daniel: Have AVC follow straight lines - Motor code is still in progress (motors do work, buthave been disconnected) - [ ] Ahmed: Create ball bearing for robot - We may not need a ball bearing - we will decide later if we need it (not crucial) - [x] Andrew, Dylan: Plan classes and methods - Classes have been planned - [x] Dylan: Add method stubs to test-module files for others to work on - Method stubs have been added to test-module files - [x] Ben: Be able to receive data from camera - The camera works, but algorithm in progress - [ ] Jonah: Be able to sense distance from IR sensor - IR Sensor code is still in progress (need catch up) - [x] Dylan: Record cost of parts so far (3D printed parts don't cost, so budget not a high priority) - Dylan - Got the camera temporary code working (copied from the Kaiwhata wiki) and can remotely compile and run it (worked with Ben) - Made a template for the IR sensor (test project) for Jonah - Began planning how the main loop will work- Jonah Andrew tought me the correct method for laying out the methods and classes that i will be working with this week, also got Eclipse hooked up with git hub
Extra Info
- Ahmed has been able to print off some parts to attach sensors to, and get some recycled parts to hold the robot
--- //: **********************************************************************
- [ ] Ahmed: Produce body prototype - [ ] Andrew: Robot can successfully talk to gate - [ ] Ben: Data from camera is processed to give information on the line - [ ] Daniel: Robot can follow curved lines - [ ] Dylan: Robot can be in different states - [x] Jonah: Get IR sensor working (Continued) - Dylan - Had a look at Ben's code, tidied it up, and tested it (stuck in a loop somewhere) - Dylan - Started looking PID code from wiki, and trying to understand it - Helping with coding problems - Wrote an auto-pulling from git script for the pi - Jonah - Finally got the IR sensor working fully and tuned. It now responsed to getLeftDistance,getRightDistance and - getMiddleDistance.- Dylan
- Completely refactored PID code (from wiki) to be more useful as its own class
- (with Andrew) Went over class plan with everyone so we all know how it's going to be organised
--- //: **********************************************************************
- [ ] Everyone: Robot is complete - [ ] Ahmed: 3D Print body design and add it to the robot - [ ] Dylan: Robot is tested - Dylan - Completed tests for some of the things I needed to test in PID file - Dylan - Got camera code somewhat working - Calibrated motor base slow speeds - Fixed back wheel - Worked with Jonah to add camera - Dylan - Collected data on motor speeds and used that to create a function that will give the left and right motors equivalent speeds. - Altered motor test-module code to use my new speed functions--- //: **********************************************************************
- Dylan - Added some more calibrated motor speeds - Calibrated left and right rotation in movement test module - Merged the camera, movement and pid code in the camera test module - Modified pid code to get it to work - Removed some blue tack on the robot and helped Ahmed with building the new design - Dylan - Calibrated some more motor speeds - Found problem causing motor controller not working - Testing PID and trying to get it working in real life - Dylan - Tidied up code in the main project - Working with Andrew trying to get the PID working - Got a very basic line following algorithm to work - Dylan - Recalibrated even motor speeds with Daniel (with the small wheels) - Recalibrated P and D values in PidController.cpp with Andrew - Dylan - Wrote some code to detect the number of whites in the left, centre, and right sections of the camera (using Andrew's idea) and throw errors if there is enough in appropriate sections to show that there is an intersetion - Worked with Andrew to get the robot to follow the left turn at intersections--- //: **********************************************************************
- Dylan - Added some more calibrated motor speeds - Calibrated left and right rotation in movement test module - Merged the camera, movement and pid code in the camera test module - Modified pid code to get it to work - Removed some blue tack on the robot and helped Ahmed with building the new design - Dylan - Calibrated some more motor speeds - Found problem causing motor controller not working - Testing PID and trying to get it working in real life - Dylan - Tidied up code in the main project - Working with Andrew trying to get the PID working - Got a very basic line following algorithm to work - Dylan - Recalibrated even motor speeds with Daniel (with the small wheels) - Recalibrated P and D values in PidController.cpp with Andrew - Dylan - Wrote some code to detect the number of whites in the left, centre, and right sections of the camera (using Andrew's idea) and throw errors if there is enough in appropriate sections to show that there is an intersetion - Worked with Andrew to get the robot to follow the left turn at intersections--- //: **********************************************************************
- Working on navigating intersections on the line - Worked with Andrew (and Ben and Jonah) adjusting line PID, line navigation, and turning in the maze - Competition day