Programming - Revision history

Programming at 02:48, 2 February 2025

2025-02-02T02:48:15Z

← Older revision		Revision as of 19:48, 1 February 2025
Line 22:		Line 22:
	Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read		Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read

			= Using Github =

			Github stores a main copy of a 'repository' (collection of files) on the server, and you can clone/checkout a local copy to make changes. To bring your changes to the server, you need to commit and push, although you may need to branch and then create a pull request. You can learn more [https://docs.github.com/en/desktop/overview/getting-started-with-github-desktop here]. The SVN documentation below is similar to git, such as similar methods of resolving merge conflicts
	= Using SVN =		= Using SVN =

	SVN works, in essence, by tracking changes made to the robot code. A "master" copy is kept on the server, and you work off a local copy that you have "checked out" from the server. You make changes, add new features, etc. then you send the changes back to the server (commit).		SVN works, in essence, by tracking changes made to the robot code. A "master" copy is kept on the server, and you work off a local copy that you have "checked out" from the server. You make changes, add new features, etc. then you send the changes back to the server (commit).

	All team laptops have an SVN client already installed called Tortoise SVN. This works using context (right-click) menus in Windows Explorer. Tortoise SVN has an in-depth guide on how to use it [https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug.html here], but the following sections are short versions of how to use it for programming on the team.		All team laptops have an SVN client already installed called Tortoise SVN. This works using context (right-click) menus in Windows Explorer. Tortoise SVN has an in-depth guide on how to use it [https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug.html here], but the following sections are short versions of how to use it for programming on the team.

	== Initial Setup: Checking Out ==		== Initial Setup: Checking Out ==
Line 32:		Line 35:

	# Open Windows Explorer on your laptop		# Open Windows Explorer on your laptop
	# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!'''		# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!'''
	# In the Explorer window, right-click to open the context menu		# In the Explorer window, right-click to open the context menu
	# Choose "SVN Checkout...." from the menu		# Choose "SVN Checkout...." from the menu
	# In the new window that opens, you need to enter this year's SVN URL (look for that on the [[2022:Programming\|2022 build season programming page]]!) into the box labelled '''URL of repository'''. Keep all other options on this screen as-is and hit "OK"		# In the new window that opens, you need to enter this year's SVN URL (look for that on the [[2022:Programming\|2022 build season programming page]]!) into the box labelled '''URL of repository'''. Keep all other options on this screen as-is and hit "OK"
	# You will be prompted for username and password. Enter your SVN username and password, then hit OK. '''Because the laptops are shared, you should make sure that "Save Authentication" is unchecked!'''		# You will be prompted for username and password. Enter your SVN username and password, then hit OK. '''Because the laptops are shared, you should make sure that "Save Authentication" is unchecked!'''
	# You should now have a new folder named "thunderbot''YEAR'''". This is your new working copy of the robot code and is the folder you will open up in VSCode.		# You should now have a new folder named "thunderbot''YEAR'''". This is your new working copy of the robot code and is the folder you will open up in VSCode.

	== Updating Your Local Copy ==		== Updating Your Local Copy ==
	"Updating" will fetch changes made by other people on the team from the server and merge them into your local working copy of the code. '''You should try to do this at the start of a meeting/work session''' or whenever you need to pick up the work done by others so your local copy does not fall too far out of sync with the "master" copy on the server. You also '''need to do this before you can send your changes to the server (commit)'''.		"Updating" will fetch changes made by other people on the team from the server and merge them into your local working copy of the code. '''You should try to do this at the start of a meeting/work session''' or whenever you need to pick up the work done by others so your local copy does not fall too far out of sync with the "master" copy on the server. You also '''need to do this before you can send your changes to the server (commit)'''.

	This process does not delete or overwrite any local changes you have made!		This process does not delete or overwrite any local changes you have made!
Line 48:		Line 51:
	# Choose "SVN Update" from the menu		# Choose "SVN Update" from the menu
	# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!!''')		# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!!''')
	# If all goes well, you will have an updated local copy with all changes made by others. If someone else was working on the same file(s) as you have local changes, it is possible you will get what is known as a "conflict". This will need to be [[#Resolving Conflicts\|resolved]] before you proceed with any additional changes or committing.		# If all goes well, you will have an updated local copy with all changes made by others. If someone else was working on the same file(s) as you have local changes, it is possible you will get what is known as a "conflict". This will need to be [[#Resolving Conflicts\|resolved]] before you proceed with any additional changes or committing.

	== Resolving Conflicts ==		== Resolving Conflicts ==
Line 54:		Line 57:
	Sometimes when you update there will be changes others have done that "conflict" with changes you have made or new stuff you have done locally and your update will result in conflicts.		Sometimes when you update there will be changes others have done that "conflict" with changes you have made or new stuff you have done locally and your update will result in conflicts.

	# The conflicted files will be marked in Windows Explorer with special icons and also listed in the output of your Update. They will also likely cause VSCode "build" to fail.		# The conflicted files will be marked in Windows Explorer with special icons and also listed in the output of your Update. They will also likely cause VSCode "build" to fail.
	# Open the conflicted source code files in VSCode and "resolve" the conflicts. The areas with conflicts will be marked directly in the file and look something like this:		# Open the conflicted source code files in VSCode and "resolve" the conflicts. The areas with conflicts will be marked directly in the file and look something like this:
	#:<pre>		#:<pre>
	#::<<<<<<< .mine		#::<<<<<<< .mine#:: int x = 0;
	#:: int x = 0;
	#:: if (y > 10)		#:: if (y > 10)
	#::: x += 1511;		#::: x += 1511;
	#::=======		#::=======
	#:: int x = 1;		#:: int x = 1;
	#:: if (y < 0)		#:: if (y < 0)#::: x -= 1511;
	#::: x -= 1511;
	#::>>>>>>> .r7</pre>		#::>>>>>>> .r7</pre>
	# You can see here that you have two versions of code, separated by special markers. Your version of the changes is between ~~<<<<<~~ and ==== and marked "mine". The changes someone else made to that same area of the code are between ==== and ~~>>>>>~~ and marked with the SVN revision they were made.		# You can see here that you have two versions of code, separated by special markers. Your version of the changes is between <<<<< and ==== and marked "mine". The changes someone else made to that same area of the code are between ==== and >>>>> and marked with the SVN revision they were made.
	# You will need edit the file to "resolve" the conflict; edit the code to be what the end result should be -- this could be deleting the other person's changes entirely, abandoning/deleting your changes and leaving the other person's changes in place, or some combination of the two. Once it looks as it should, remove the special marking lines.		# You will need edit the file to "resolve" the conflict; edit the code to be what the end result should be -- this could be deleting the other person's changes entirely, abandoning/deleting your changes and leaving the other person's changes in place, or some combination of the two. Once it looks as it should, remove the special marking lines.
	# Repeat that process for all "conflicted" sections of the file and for any other "conflicted" files.		# Repeat that process for all "conflicted" sections of the file and for any other "conflicted" files.
	# Once you have fixed the conflicts, you need to tell SVN you have done so. Open Windows Explorer to your project folder and browse down to the location of the conflicted file(s) in the project. Select the conflicted file(s), right click, choose Tortoise SVN, then choose "Resolve".		# Once you have fixed the conflicts, you need to tell SVN you have done so. Open Windows Explorer to your project folder and browse down to the location of the conflicted file(s) in the project. Select the conflicted file(s), right click, choose Tortoise SVN, then choose "Resolve".

	== Committing Your Changes to the Server ==		== Committing Your Changes to the Server ==
Line 76:		Line 77:
	# Verify your code builds properly (use the normal VSCode build process)		# Verify your code builds properly (use the normal VSCode build process)
	# Have a '''programming mentor''' review your changes!		# Have a '''programming mentor''' review your changes!
	# Open Windows Explorer and browse to your project location. Right-click your changed file(s) or the top-level project directory (thunderbotYYYY) and choose "SVN Commit" from the menu.		# Open Windows Explorer and browse to your project location. Right-click your changed file(s) or the top-level project directory (thunderbotYYYY) and choose "SVN Commit" from the menu.
	# Enter a brief description of what you are changing! Examples: "initial new code to control shooter", "fixed motor spin direction on intake", etc.		# Enter a brief description of what you are changing! Examples: "initial new code to control shooter", "fixed motor spin direction on intake", etc.
	# Hit OK		# Hit OK
	# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!''')		# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!''')
Line 94:		Line 95:
	*[[index.php?title=Media:Programming.pdf\|C++ Overview Slides]]		*[[index.php?title=Media:Programming.pdf\|C++ Overview Slides]]
	*[[PreSeason_Create_Test_Project\|<font color="#0066cc">Create Test Project</font>]]: Do this before starting any lessons		*[[PreSeason_Create_Test_Project\|<font color="#0066cc">Create Test Project</font>]]: Do this before starting any lessons
	*[[Preseason_Build_Project\|<font color="#0066cc">Build a Project</font>]]		*[[Preseason_Build_Project\|<font color="#0066cc">Build a Project</font>]]
	*[[Preseason_Deploy_Code\|<font color="#0066cc">Deploy a Project to Robot</font>]]		*[[Preseason_Deploy_Code\|<font color="#0066cc">Deploy a Project to Robot</font>]]

	== Lessons ==		== Lessons ==

Programming: /* FRC and WPILib References */

2025-02-02T02:42:26Z

FRC and WPILib References

← Older revision		Revision as of 19:42, 1 February 2025
Line 9:		Line 9:

	*[http://docs.wpilib.org FRC Control System Documentation]		*[http://docs.wpilib.org FRC Control System Documentation]
	*[https://first.wpi.edu/wpilib/allwpilib/docs/release/cpp/index.html FRC C++ WPILib API Docs]		*[https://first.wpi.edu/wpilib/allwpilib/docs/release/cpp/index.html FRC C++ WPILib API Docs]
	* CTRE Phoenix - Third party software drivers used to talk to Talon SRX's over CAN bus:		* CTRE Phoenix - Third party software drivers used to talk to Talon SRX's over CAN bus:
	**[https://github.com/CrossTheRoadElec/Phoenix-Documentation CTRE Phoenix Docs] - Verbose documentation and detailed guides		**[https://github.com/CrossTheRoadElec/Phoenix-Documentation CTRE Phoenix Docs] - Verbose documentation and detailed guides
	**[http://www.ctr-electronics.com/downloads/api/cpp/html/index.html CTRE Phoenix API] - API Reference		**[http://www.ctr-electronics.com/downloads/api/cpp/html/index.html CTRE Phoenix API] - API Reference
			*REV - Third party software drivers used to talk to Spark maxes/flexes
			**[https://docs.revrobotics.com/revlib REVLib] - Docs on REV code

	= Quite Useful Things to Remember =		= Quite Useful Things to Remember =

Programming: /* Programming Sub-pages and Links */

2025-02-02T02:39:31Z

Programming Sub-pages and Links

← Older revision		Revision as of 19:39, 1 February 2025
Line 1:		Line 1:
	= Programming Sub-pages and Links =		= Programming Sub-pages and Links =

	*[[SVN_Setup\|SVN Setup]]		*Github [https://frc1511.github.io/ Docs] and [https://github.com/frc1511 Repos]
	*[http://www.svn.penfieldrobotics.com/ Online browsing of our SVN Tree]		*[[SVN_Setup\|SVN Setup]]
	*[[Team_Laptop_Info\|Team Laptop Info]]		*[http://www.svn.penfieldrobotics.com/ Online browsing of our SVN Tree]
			*[[Team_Laptop_Info\|Team Laptop Info]]

	= FRC and WPILib References =		= FRC and WPILib References =

Programming: /* Initial Setup: Checking Out */

2023-01-14T22:50:43Z

Initial Setup: Checking Out

← Older revision		Revision as of 15:50, 14 January 2023
Line 30:		Line 30:

	# Open Windows Explorer on your laptop		# Open Windows Explorer on your laptop
	# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!!'''		# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!'''
	# In the Explorer window, right-click to open the context menu		# In the Explorer window, right-click to open the context menu
	# Choose "SVN Checkout...." from the menu		# Choose "SVN Checkout...." from the menu

Programming: /* Initial Setup: Checking Out */

2023-01-14T22:50:13Z

Initial Setup: Checking Out

← Older revision		Revision as of 15:50, 14 January 2023
Line 30:		Line 30:

	# Open Windows Explorer on your laptop		# Open Windows Explorer on your laptop
	# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!'''		# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!!'''
	# In the Explorer window, right-click to open the context menu		# In the Explorer window, right-click to open the context menu
	# Choose "SVN Checkout...." from the menu		# Choose "SVN Checkout...." from the menu

Programming: /* Updating Your Local Copy */

2023-01-14T22:35:38Z

Updating Your Local Copy

← Older revision		Revision as of 15:35, 14 January 2023
Line 45:		Line 45:
	# Right-click the top-level (thunderbotYYYY) folder		# Right-click the top-level (thunderbotYYYY) folder
	# Choose "SVN Update" from the menu		# Choose "SVN Update" from the menu
	# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!''')		# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!!''')
	# If all goes well, you will have an updated local copy with all changes made by others. If someone else was working on the same file(s) as you have local changes, it is possible you will get what is known as a "conflict". This will need to be [[#Resolving Conflicts\|resolved]] before you proceed with any additional changes or committing.		# If all goes well, you will have an updated local copy with all changes made by others. If someone else was working on the same file(s) as you have local changes, it is possible you will get what is known as a "conflict". This will need to be [[#Resolving Conflicts\|resolved]] before you proceed with any additional changes or committing.

Line 90:		Line 90:
	= Programming Preseason =		= Programming Preseason =

	*[[Media:Programming.pdf\|C++ Overview Slides]]		*[[index.php?title=Media:Programming.pdf\|C++ Overview Slides]]
	*[[PreSeason_Create_Test_Project\|<font color="#0066cc">Create Test Project</font>]]: Do this before starting any lessons		*[[PreSeason_Create_Test_Project\|<font color="#0066cc">Create Test Project</font>]]: Do this before starting any lessons
	*[[Preseason_Build_Project\|<font color="#0066cc">Build a Project</font>]]		*[[Preseason_Build_Project\|<font color="#0066cc">Build a Project</font>]]

Heydowns: /* Initial Setup: Checking Out */

2022-06-30T18:30:07Z

Initial Setup: Checking Out

← Older revision		Revision as of 11:30, 30 June 2022
Line 33:		Line 33:
	# In the Explorer window, right-click to open the context menu		# In the Explorer window, right-click to open the context menu
	# Choose "SVN Checkout...." from the menu		# Choose "SVN Checkout...." from the menu
	# In the new window that opens, you need to enter this year's SVN URL (look for that on the [[2022:build season programming page]]!) into the box labelled '''URL of repository'''. Keep all other options on this screen as-is and hit "OK"		# In the new window that opens, you need to enter this year's SVN URL (look for that on the [[2022:Programming\|2022 build season programming page]]!) into the box labelled '''URL of repository'''. Keep all other options on this screen as-is and hit "OK"
	# You will be prompted for username and password. Enter your SVN username and password, then hit OK. '''Because the laptops are shared, you should make sure that "Save Authentication" is unchecked!'''		# You will be prompted for username and password. Enter your SVN username and password, then hit OK. '''Because the laptops are shared, you should make sure that "Save Authentication" is unchecked!'''
	# You should now have a new folder named "thunderbot''YEAR'''". This is your new working copy of the robot code and is the folder you will open up in VSCode.		# You should now have a new folder named "thunderbot''YEAR'''". This is your new working copy of the robot code and is the folder you will open up in VSCode.

Heydowns at 16:10, 18 January 2022

2022-01-18T16:10:32Z

← Older revision		Revision as of 09:10, 18 January 2022
Line 19:		Line 19:

	Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read		Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read

			= Using SVN =

			SVN works, in essence, by tracking changes made to the robot code. A "master" copy is kept on the server, and you work off a local copy that you have "checked out" from the server. You make changes, add new features, etc. then you send the changes back to the server (commit).

			All team laptops have an SVN client already installed called Tortoise SVN. This works using context (right-click) menus in Windows Explorer. Tortoise SVN has an in-depth guide on how to use it [https://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug.html here], but the following sections are short versions of how to use it for programming on the team.

			== Initial Setup: Checking Out ==
			To get the initial copy of the robot code for this year on to the laptop you are working on, you will "check out" the project from the SVN server:

			# Open Windows Explorer on your laptop
			# Browse to a location on the computer to keep your working code - the desktop, the Documents folder, or a the top level of the C drive are all good locations. '''You may wish to make a folder with your name on it to make it clear to other users of that laptop that this is your working copy!'''
			# In the Explorer window, right-click to open the context menu
			# Choose "SVN Checkout...." from the menu
			# In the new window that opens, you need to enter this year's SVN URL (look for that on the [[2022:build season programming page]]!) into the box labelled '''URL of repository'''. Keep all other options on this screen as-is and hit "OK"
			# You will be prompted for username and password. Enter your SVN username and password, then hit OK. '''Because the laptops are shared, you should make sure that "Save Authentication" is unchecked!'''
			# You should now have a new folder named "thunderbot''YEAR'''". This is your new working copy of the robot code and is the folder you will open up in VSCode.

			== Updating Your Local Copy ==
			"Updating" will fetch changes made by other people on the team from the server and merge them into your local working copy of the code. '''You should try to do this at the start of a meeting/work session''' or whenever you need to pick up the work done by others so your local copy does not fall too far out of sync with the "master" copy on the server. You also '''need to do this before you can send your changes to the server (commit)'''.

			This process does not delete or overwrite any local changes you have made!

			# Open Windows Explorer and browse to the folder where your local working copy is on the laptop.
			# Right-click the top-level (thunderbotYYYY) folder
			# Choose "SVN Update" from the menu
			# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!''')
			# If all goes well, you will have an updated local copy with all changes made by others. If someone else was working on the same file(s) as you have local changes, it is possible you will get what is known as a "conflict". This will need to be [[#Resolving Conflicts\|resolved]] before you proceed with any additional changes or committing.

			== Resolving Conflicts ==

			Sometimes when you update there will be changes others have done that "conflict" with changes you have made or new stuff you have done locally and your update will result in conflicts.

			# The conflicted files will be marked in Windows Explorer with special icons and also listed in the output of your Update. They will also likely cause VSCode "build" to fail.
			# Open the conflicted source code files in VSCode and "resolve" the conflicts. The areas with conflicts will be marked directly in the file and look something like this:
			#:<pre>
			#::<<<<<<< .mine
			#:: int x = 0;
			#:: if (y > 10)
			#::: x += 1511;
			#::=======
			#:: int x = 1;
			#:: if (y < 0)
			#::: x -= 1511;
			#::>>>>>>> .r7</pre>
			# You can see here that you have two versions of code, separated by special markers. Your version of the changes is between <<<<< and ==== and marked "mine". The changes someone else made to that same area of the code are between ==== and >>>>> and marked with the SVN revision they were made.
			# You will need edit the file to "resolve" the conflict; edit the code to be what the end result should be -- this could be deleting the other person's changes entirely, abandoning/deleting your changes and leaving the other person's changes in place, or some combination of the two. Once it looks as it should, remove the special marking lines.
			# Repeat that process for all "conflicted" sections of the file and for any other "conflicted" files.
			# Once you have fixed the conflicts, you need to tell SVN you have done so. Open Windows Explorer to your project folder and browse down to the location of the conflicted file(s) in the project. Select the conflicted file(s), right click, choose Tortoise SVN, then choose "Resolve".

			== Committing Your Changes to the Server ==
			Once you have completed a good amount of new code, you will want to "commit" it to send it to the server and so that others can access your changes.

			# Verify your code builds properly (use the normal VSCode build process)
			# Have a '''programming mentor''' review your changes!
			# Open Windows Explorer and browse to your project location. Right-click your changed file(s) or the top-level project directory (thunderbotYYYY) and choose "SVN Commit" from the menu.
			# Enter a brief description of what you are changing! Examples: "initial new code to control shooter", "fixed motor spin direction on intake", etc.
			# Hit OK
			# Enter your username/password for SVN ('''make sure that "Save Authentication" is unchecked!''')


	= Preseason Software Installation =		= Preseason Software Installation =

Programming: /* Preseason Software Installation */

2022-01-12T02:29:22Z

Preseason Software Installation

← Older revision		Revision as of 19:29, 11 January 2022
Line 22:		Line 22:
	= Preseason Software Installation =		= Preseason Software Installation =
	Here are instruction and download links if you want to install the software to your own computer:		Here are instruction and download links if you want to install the software to your own computer:
	*# '''THESE INSTRUCTIONS AND LINKS ARE FOR 2021 ONLY!'''		* '''THESE INSTRUCTIONS AND LINKS ARE FOR 2021 ONLY!'''
	*# '''MAKE SURE TO DO THESE IN ORDER!'''		* '''MAKE SURE TO DO THESE IN ORDER!'''
	*# Install WPILib - [https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-2/wpilib-setup.html Instructions] and [https://github.com/wpilibsuite/allwpilib/releases/download/v2021.3.1/WPILib_Windows64-2021.3.1.iso Download Link]		*# Install WPILib - [https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-2/wpilib-setup.html Instructions] and [https://github.com/wpilibsuite/allwpilib/releases/download/v2021.3.1/WPILib_Windows64-2021.3.1.iso Download Link]
	*# Install CTRE Phoenix Libraries [https://github.com/CrossTheRoadElec/Phoenix-Releases/releases/download/v5.19.4.1/CTRE_Phoenix_Framework_v5.19.4.1.exe Download Link]		*# Install CTRE Phoenix Libraries [https://github.com/CrossTheRoadElec/Phoenix-Releases/releases/download/v5.19.4.1/CTRE_Phoenix_Framework_v5.19.4.1.exe Download Link]
	*# '''If you are just doing programming you can skip this step!''' This step is only needed if you want the Driver Station Software: install FRC Game Tools using [https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-2/frc-game-tools.html these instructions].		*# '''If you are just doing programming you can skip this step!''' This step is only needed if you want the Driver Station Software: install FRC Game Tools using [https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-2/frc-game-tools.html these instructions].


	= Programming Preseason =		= Programming Preseason =

Programming at 02:28, 12 January 2022

2022-01-12T02:28:11Z

← Older revision		Revision as of 19:28, 11 January 2022
Line 1:		Line 1:
	<div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output">
	= Programming Sub-pages and Links =		= Programming Sub-pages and Links =

Line 5:		Line 4:
	*[http://www.svn.penfieldrobotics.com/ Online browsing of our SVN Tree]		*[http://www.svn.penfieldrobotics.com/ Online browsing of our SVN Tree]
	*[[Team_Laptop_Info\|Team Laptop Info]]		*[[Team_Laptop_Info\|Team Laptop Info]]
	~~</div> </div> </div> </div> </div> </div>~~

	= FRC and WPILib References =		= FRC and WPILib References =
Line 15:		Line 13:
	**[http://www.ctr-electronics.com/downloads/api/cpp/html/index.html CTRE Phoenix API] - API Reference		**[http://www.ctr-electronics.com/downloads/api/cpp/html/index.html CTRE Phoenix API] - API Reference

	~~<div class="mw-parser-output">~~

	= Quite Useful Things to Remember =		= Quite Useful Things to Remember =
Line 22:		Line 19:

	Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read		Color sensor proximity reading ranges from 0-2048, the higher the value the closer the surface. A reading of ~300 or greater is enough for a reliable color read
	<div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"><div class="mw-parser-output"> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>

	= Preseason Software Installation =		= Preseason Software Installation =