Competition code is found in project Carbi.
If in doubt, go to screensteps live.
Useful screensteps references:
Control system hardware review
Setting up the development environment
Talon SRX References:
Talon SRX Technical Resources
Software Reference Manual (Found under FRC FIRST POWERUP Software API section)
Also in the same section are .CRF files for updating firmware, Java API documentation, and other useful documents.
The main branch master is for competition code only. Any changes should be made in their own branch based off master so if something goes horribly wrong, the branch can be reverted and the code in master is preserved. If there is finalized code in a development branch, open a pull request so it can be merged into master. Only cyamonide (Simon) or suchaHassle (Jason) will be accepting these.
See issues tab for what needs to be done next with the projects. If you plan on taking care of one of the items on the list, please assign yourself to the issue, and reply with your intent to work on it, and also the branch that you will be contributing to. Any questions should also be stated in reply to the issue; they will be answered as soon as possible.
For most people, a GUI is easiest to use. Watch this video in this playlist to learn how to use it.
If you don't mind using a command line, watch everything in this great tutorial by The Net Ninja, found here.
- Learn how to write good commit messages and maintain the integrity of this repository by reading this useful guide by Chris Beams.
- Do not commit more than one change. Instead, each commit should be representative of a single change.
- Code should work at every commit so that if anything needs to be reverted, we won't have everything broken.
- If you're in the nine out of ten times where the code doesn't work, elaborate in the body of the commit message.
- Experiments should be carried out in branches, and merged with the main branch only when it works and is decidedly a welcome addition to the final robot code.