First Thoughts ..

Although I've been involved with Student Robotics from the start of this academic year, I perceived most of the electronics - including some of the components I have worked on - as nothing short of witchcraft. Never having seen a schematic for any of the boards until yesterday, I had only the beautiful yet chaotic PCBs to indicate the inner workings. Although I had a collection of acronyms and techno-babble to associate with each of the boards, I had little confidence in ever understanding the complete design.

This all changed yesterday after some well spent hours going through each of the sub-assemblies in tern with Rob. Through doing this I now have a much more complete model in my mind of how everything fits together and more importantly, how things can be fixed, improved and updated. Although I may have to reside to never understanding some details such as the custom linux distro and image recognition, at least I know enough to do by best to distribute these jobs to people who know more about them.

Pressing Issues
The most pressing of which are the budget and some kind of sensible schedule. The electronics budget with the gift of hindsight should be manageable and hopefully well founded. As for the schedule, this involves the regrettable chore of admitting how little time there is once the PCB manufacturing time, Component procurement latency and travel plans are crossed off the calendar.

Yet More Pressing Issues
This would be the (working title:) " new people to SR play around with kit and find lots of bugs and problems, day". My thoughts on how it should be run are:

1. Split group into two, ideally with equal numbers of soft/hardware people
2. Task 1: Get 'forwards-backwards' code running on both robots
3. Task 2: Team A play with the vision system, attempting to use all of its features such as block coordinates and colour recognition. Meanwhile Team B focus on the servo board. They will develop code to test the servo boards limits and expose any bugs
   
4. Task 3: Team A add the IO board and use it to further improve vision system tests, eg. use LED output to indicate number of blocks present. Team B use the IO board with analogue inputs and combine this with a mechanism of sorts and access how useful it is.
5. Task 4: Combine all the boards together to create a robot which does something interesting, eg, avoids /attracted to blocs,
6. Task 5: If time, both teams try and 'break' the IDE. Attempt to find its weaknesses and failings and offer suggestions for improvements.
7. Summary: As well as stopping after each task to discuss bugs and findings, there will be one big summing up session. Both teams present their conclusions to the group and we make note of the important ones
   

Goals

• Everyone gets to know everyone else
• Everyone else gets to know the electronics and kit that we've got to work with
• We find out about bugs we might have missed
• Everyone generates some ideas for improvements
• New people get excited and interested in what's going on
• New people demonstrate skills/interests that they have
• The IDE gets some much needed attention
• We finally get to play with the kit, instead of the schools

Here's hoping...