Topics

Attendance

• Allen Brown - Scalawags mentor
• Gary Oliver - Scalawags mentor
• Jeff Rice - Scalawags student (soon mentor)

Attendance has been weak since the competition season. In particular the PHS and CHS members have disappeared. I would like to hear ideas for how we can get them to come. [By the way, we had more laptops than people.]

Current Documentation

• ElectricalPower20041107.html -- Electrical Power connections
• ElectricalNodes20041107.html -- Electrical Communication Links
• CvsInstructions20041111.html -- How to use CVS
• ProtocolCommandTable20041007.html -- Packet and Commands: Tabular definition
• ProtocolCommandState20041107.html -- Packet and Commands: BNF and State Diagrams
• DirectoryStructure20041022.html -- How the project is organized on disk
• Pictures/CallSequence20041114.gif -- Heirarchy of calls from packet on down.
• Pictures/cn_overview20041213.gif -- How the cn software will look.
    Dia source

Meeting Notes

We had the Scalawags 2005 robot to work with. We got it talking on the serial interface to a laptop. We made some serial cables for that purpose.

We had the CV coprocessor. Unfortunately it was unbootable. We were not able to reflash it to fix the problem. We need to get a working coprocessor to grab the kernel image. I had left the Scalawags coprocessor in my car. (I had to use the van to carry the robot.)

Plans for 2005 off-Season

• Co-processor. priority: 1
• Data logging in the co-processor. priority: 2
• Interfacing 5V sensors to the co-processor. priority: 3
• Good diagnostics framework. priority: 4
• PID for servos. priority: 5 [example doc]

Possible Training during 2005 off-Season

Rather than explicit training, we can learn the skills below as we need them while debugging.

• C (of course)
• Soldering
• How to use Voltmeter effectively
• How to use Oscilloscope
• How to use Logic Probe

Schedule

• April 22 - location: Alpha-Omega
  • Reflash the kernel on the coprocessor board.
  • Connect the FRC to the coprocessor board and test/debug existing software.
• April 29 - location: Alpha-Omega
  • Datalogging.
• May 6 - location: Alpha-Omega
  • Move sensors and code to deal with them from the FRC to the coprocessor.
  • Test/debug.