Software - Pantherbotics/FRC2016_Stronghold GitHub Wiki

2/6/2016

Summary of the day

Lots of things... We fixed the RoboRio (it now runs the correct version), fixed the CAN bus system, and got the pneumatics to work. We have the robot communicating wireless, although the USB connection is much stabler.

  • Decisions: Not much...
  • Concerns:
  • Need to get some sort of feedback to the DS (steal System.in)
  • Changes:
  • Fixed the CAN bus system
  • Update RoboRio and CAN device firmware
  • Fixed pneumatic system (mostly)
  • Next Steps:
  • Set Robot AP to Robot Bridge so that it extends the Pantherbotics wifi.
  • Get the arm working
  • Auton
  • Image Rec/Graphics
  • Networking Tables/Dashboard
  • Mix Kotlin in?
  • Update provided by: Joshua Freedman (d4rkfly3r)

2/2/2016

Summary of the day

General software for robot has been finished: once we have everything wired, we should have a working robot after tweaking a few ports. The beta-gradle branch has been pushed to master, and everyone should backup their code and re pull from master. Please DO NOT push directly to the master branch, make a new branch/fork it and then make a PR, Roger or I will accept/merge it.

  • Decisions: Started adding in failure/success callbacks using new Java 8 Method Reference Syntax.
  • Concerns: Need to make sure all programmers understand the stuff.
  • Changes: Added the initial code for all subsystems and commands.
  • Next Steps:
  • Documentation to an extent, need for anyone to relatively easy understand what different lines of code do.
  • Setup ports in the RobotMap to the correctly corresponding ports of the IOs.
  • Start image processing library | This will be in an independent branch labeled Imaging, please do not edit it without permission.
  • Start NetworkTables/SmartDashboard stuff. This is partially what the callback feature will be used for.
  • Update provided by: Joshua Freedman (d4rkfly3r)

2/1/2016

Summary of the day

Motor connectors wired. 3D print model for pneumatic tank bracket started.

  • Decisions:
  • Concerns:
  • Changes:
  • Next Steps:
  • Update provided by:

##1/30/16

Summary of the day

Josh completed the objective agreed upon yesterday - the End Effector and Arm has been added to the map. The electronics have not been finished yet, so we can not yet upload to the robot.

  • Decisions: None.
  • Concerns: People other than Josh need experience programming, so we should get more students to make the changes.
  • Changes: Added the End Effector and Arm code initial code into the RobotMap and OI.
  • Next Steps: Add functions/methods for moving the Arm, Firing the Launcher, and Intake.
  • Update provided by: Mr Rice (RoboticRice)

##1/29/16

Summary of the day

Since the test-bed robot has been dissembled to use the electronics for the current robot design, there is no working robot to upload code to. We are waiting for the electronics to at least be operational (if not complete) on the current robot.

  • Decisions: Decided on the next goal.
  • Concerns: Since the robot construction has fallen behind, there has been nothing to program yet, which gives the programming team less time to program and test before we bag & tag the robot.
  • Changes: None.
  • Next Steps: 1) Test the electronics configuration on the current robot by uploading a sample code, and 2) Program the command/subsystem for the Kicker/Launcher mechanism.
  • Update provided by: Mr Rice (RoboticRice)

##1/22,23,25/16

Summary of the day

Not much.

  • Decisions:
  • Concerns:
  • Changes:
  • Next Steps:
  • Update provided by: vickyjjj

1/21/16

Summary of the day

Connected robot to server on lab so we can have internet and connected robot at the same time. Worked on by Mike and Roger. Josh also got around 20 licenses for IntelliJ for a year for club members who will be on the software team.

  • Decisions:
  • Concerns:
  • Changes:
  • Next Steps:
  • Update provided by: vickyjjj

1/16,18,19/16

Summary of the day

Not much.

  • Decisions:
  • Concerns:
  • Changes:
  • Next Steps:
  • Update provided by: vickyjjj

1/15/16

Summary of the day

Got camera working for the test set up. Made a few miscellaneous changes in the network set up, e.g., automatic startup and management scripts for automatically restarting the internet connection in the event that the bridge computer goes down.

  • Decisions:
  • Concerns:
  • Changes:
  • Next Steps: graphic options for the status displays.
  • Update provided by: Roger

1/13/16

Summary of the day

Determined the appropriate team tools for the development of the software, along with the documentation team.

  • Decisions: Github/HuBoard will be used for tracking milestone, issues, and as a version control system; Slacker will be used for team collaboration/communication.
  • Concerns: Push to external website. Need reliable internet connection.
  • Changes: HuBoard & Slacker have added integration to github.
  • Next Steps: Talk to potential programmers, teach them the tools, and layout an organized structure for creating and committing code.
  • Update provided by: Joshua F