Ports

We handle communication over a SerialPort. We have a SerialPortWrapper class that handles the traffic over the ports. We then have an SDPPort class, which provides a very elementary unfinished GUI for port monitorring and at the very end, we have a basic RobotPort. This has 3 methods:

• ping() - The system finds robots by sending the string "ping" to all the ports and waiting for a response. Fred responds with "pang". Our teammate responded with "pong". This is how our system figures out which robot is where. Your robot must be able to respond to the string "ping"!
• stop() - Your robot should have a command that stops it from moving (actual wheels only, no need to stop anything else).
• halt() - Your robot should have a failsafe way of stopping everything. This method will send that command to the robot.

Your particular robot will probably have more commands. That is where interfaces come in. Fred implemented two additional interfaces. The FourWheelHolonomicRobotPort and the PropellerEquippedRobotPort. The reason for this cumbersome way of implementing commands is that this way other classes can use the ports and type cast them to the interface class. This is why your robot could reuse our 4 wheel holonomic drive and port interface WITHOUT actually being an instance of Fred and still be navigable by the navigation system.

This is the structure: