The source code for OpenDS is available on GitHub at https://github.com/Boomaa23/open-ds.

OpenDS may be used without restriction for the purpose of testing robots by teams and individuals. Please see the license for further uses.

If you find a bug or issue with OpenDS, please report it on the "Issues" section of the GitHub here.

For protocol changes in future years, OpenDS is easily modifiable. Ports, IP addresses, display layouts, and packet creation/parsing are all re-formattable.

There are three main classes that need to be implemented for a new protocol year:

• PacketParser
  • Package: com.boomaa.opends.data.receive.parser
  • Example: Parser2020
  • Description: Parses received packet data that is not contained within tags (e.g. standard data across all packets of that type)
  • Implementation: Create four classes that extend the above class, one for each connection (e.g. TCP and UDP for RoboRIO and FMS). Make all four classes sub-classes of a single class Parser20XX with the same naming scheme found in the example.
• PacketCreator
  • Package: com.boomaa.opends.data.send.creator
  • Example: Creator2020
  • Description: Creates packets to send to the RoboRIO or FMS based on GUI inputs and other status sources.
  • Implementation: Create four methods in a single class. Make the class extend the abstract class PacketCreator, and implement all the methods. This is a good place to access GUI data through the JDEC.
• ElementUpdater
  • Package: com.boomaa.opends.display.updater
  • Example: Updater2020
  • Description: Updates the previously positioned GUI elements with data from the parsers.
  • Implementation: Make a new class that extends the abstract class ElementUpdater. This will contain methods to update the GUI from each packet stream, and methods to reset the elements should connection to the remote (RoboRIO/FMS) stop.

The SendTag and ReceiveTag classes should be fully updated for the additional years' sent and received (from the perspective of the driver station) tags. Use Null[Send/Receive]Tag if none, or Ref[Send/Receive]Tag.yearOfAction(int year) if it is the same as another year. Consider using the DataBase system for year-centric data storage and identification.

Make sure that naming schemes are followed. Add another integer entry to the array DisplayEndpoint:VALID_PROTOCOL_YEARS when all three main classes have been created. This will allow the selection of the new protocol by the user. Put in decreasing year order.