GT RoboJackets - Recent changes [en]

Git

2012-05-17T02:15:40Z

init:

← Older revision		Revision as of 02:15, 17 May 2012
(11 intermediate revisions not shown)
Line 1:		Line 1:
	Git is the [[version control system]] used by RoboJackets for much of the code (we've moved some stuff over from SVN).		Git is the [[version control system]] used by RoboJackets for much of the code (we've moved some stuff over from SVN).

-	~~=Note: this page~~ is a ~~work in progress!!!=~~	+	This guide is really short. To learn more about how Git works and how you can use it, see the [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git website].


	==Setup==		==Setup==
	* [http://git-scm.com/downloads Download Git]		* [http://git-scm.com/downloads Download Git]
-	* Each commit you make has your name and email address on it. Tell Git ~~what~~ these are with these commands:	+	* Each commit you make has your name and email address on it. Tell Git who you are with these are with these commands:
	<code>		<code>
	:$ git config --global user.name "George P. Burdell"		:$ git config --global user.name "George P. Burdell"
Line 14:		Line 14:
	==Commands==		==Commands==
	These are common commands that will get you started. There are more but you can discover those on your own.		These are common commands that will get you started. There are more but you can discover those on your own.
		+	The commands are all shown from the command-line. There are graphical tools available but a good command-line understanding will help in using the graphical tools.

-	When using git through command line, first change your directory to the repository. So if your code is on your desktop in a folder called "repo", execute this command.	+	When using git through command line, first change your directory to the repository. So if your code is on your desktop in a folder called "repo", execute this command:
		+	<code>
		+	:'''$ cd ~/desktop/repo'''
		+	</code>

		+
		+	===init===
		+	To start tracking an existing project with Git, cd to your project folder and use the init command. This sets up your project as a git repository.
		+	<code>
		+	:'''$ cd ~/desktop/myproject'''
		+	:'''$ git init'''
		+	</code>

	===clone===		===clone===
-	~~This will be~~ the ~~first~~ command ~~you run before you start~~ to ~~work on~~ a ~~project for the first time. It will ask the server for a list~~ of ~~files at a certain location and then download those files to your computer. These files then become the ''working copy'' that you can edit~~.	+	Use the clone command to make a copy of an existing repository.

-	~~The commands are all shown from the command-line. There are graphical tools available but a good command-line understanding will help in using the graphical tools.~~
-
-	~~Usage:~~
	<code>		<code>
-	:'''$~~prompt:~~ git clone <remote-path>'''	+	:'''$ git clone <remote-path>'''
-	:'''$~~prompt:~~ git clone <remote-path> <local-path>'''	+	:'''$ git clone <remote-path> <local-path>'''
	</code>		</code>
	* The remote path is the location of a directory on a Git server that has the files you want to check out. This will usually be given to you by the project lead or maintainer.		* The remote path is the location of a directory on a Git server that has the files you want to check out. This will usually be given to you by the project lead or maintainer.
Line 32:		Line 40:

	===add===		===add===
		+	When you make changes in a repository that you'd like to commit, you must first add them to the "staging area". You can add changed files individually or add them all at once.
		+	<code>
		+	:'''$ git add myFile.c'''
		+	:'''$ git add --all'''
		+	</code>

	===commit===		===commit===
		+	Once you add your changes to the "staging area" using the add command, you can commit them to your repository. Comment your commit so when others read it, they'll know what types of changes you made.
		+	<code>
		+	:'''$ git commit -m 'Added new files to control the flux capacitor' '''
		+	</code>

	===push===		===push===
		+	When you commit to your repository, they are added to the history only in your local repo. To add those changes to another repository, you use the push command.
		+	<code>
		+	:'''$ git push <remote-repo> <branch>
		+	</code>
		+	* Note: usually you'll be working on the master branch.

	===pull===		===pull===
		+	If a remote repository has commits that you'd like to have in your repository, you can pull them.
		+
		+	<code>
		+	:'''$ git pull <remote-repo> <branch>'''
		+	</code>

	[[Category:How to Guides]]		[[Category:How to Guides]]

RC12EEtodo

2012-05-17T00:02:50Z

New page

- '''Make sure all motor connectors are swapped out for the new black ones.'''
There's at least one control board that still needs this.

- '''Inspect all control boards.'''
We have several that we know work, but some of the ones we used last summer need repair. There are also some that are almost completely populated, but are still missing a few parts. We're keeping track of the board number and their status with this google doc:
[https://docs.google.com/spreadsheet/ccc?key=0AlyFWYS4vx-5dHhNblB6NDJyNk1PUkFtb1FiN1hJNkE#gid=0]
To inspect them, first determine if they are completely populated. The main clue for this will be the presence of the IMU and the radio chip. The IMU is the chip indicated here with the arrow near the bottom, and the IMU is those top two chips: [http://i.imgur.com/qo7E3.jpg]
Notice in that picture that there are some resistors missing next to the FPGA. That's ok, those parts don't get populated. Once you've determined that a board is populated, note it in the google doc, and spend a minute or two just eyeballing solder joints and looking for anything that might be a short. Then use the microscope to inspect suspicious joints or anything you couldn't see with the naked eye. Note that there will be an intentional short on exactly two adjacent FPGA pins. That's not a mistake, those need to be shorted. All other FPGA pins shouldn't be shorted.

-'''Test inspected control boards'''
The easiest way to test them is to put them in a robot and try to drive it. If it works, note it on the google doc. If not, note that as well and what doesn't work. You can get more information by plugging in the control boards via USB to the field computer or any computer running linux (you also need to plug a battery in the control boards; they can't be powered under only USB). You'll see a new device under /dev/robot. If you don't, that's an immediate sign that there's some kind of assembly error. Note that it will only appear if you plug in a board that's already been programmed. If you finish populating one of the new boards and then try to plug it in, nothing will happen because it has no code on it. The immediate priority is making sure the assembled boards all work, so we'll worry about the new ones after that. Once you see the robot show up, you can use picocom to connect to it and use it's built in terminal. Run "picocom /dev/robot" and then "status". That will print out diagnostic information about the board and everything that is connected to it.

-'''Repair control boards that don't work'''
I think there's one board that needs an FPGA replaced, and there may be one that needs some FETs on the bottom replaced. If that's true, you'll discover which ones they are through testing.
-Make encoder wires and ball sensors
We had a hard time last summer getting encoder wires to work for long periods of time. We need to make more. I think we also need more ball sensors. IR LEDs and photodiodes are in the box of new parts we got a couple weeks ago.

-'''Populate new 2008 kickers'''
I'm not sure if these have been ordered yet, but once they arrive, they need to be populated. There's really nothing special about populating it, except the LT3757 needs to be done with hot air. There's a ground pad under the chip that has to have a good electrical connection to the pad on the board. To do that, use a regular iron to put down a little solder on the pad on the board, then put the chip down and use hot air.

-'''Low priority tasks'''
These include populating the new antenna boards (look at the other ones to see how. It's just a trim cap and an antenna connector). We don't have the crimper to make the pigtails that get soldered to the antenna boards, so if we really need to, we can harvest them from the old plexi antennas. We'd rather not have to do that though.

RoboCup Electrical 2012

2012-05-16T23:57:28Z

Current Activities:

← Older revision		Revision as of 23:57, 16 May 2012
Line 3:		Line 3:

	==Current Activities==		==Current Activities==
		+	* [[RC12EEtodo\|2012 EE To Do List]]
	* [[RC12KickerRebuild08\|2008 Kicker Rebuild]]		* [[RC12KickerRebuild08\|2008 Kicker Rebuild]]
	* [[RC12KickerRebuild11\|2011 Kicker Rebuild]]		* [[RC12KickerRebuild11\|2011 Kicker Rebuild]]

Git

2012-05-16T05:28:35Z

← Older revision		Revision as of 05:28, 16 May 2012
(8 intermediate revisions not shown)
Line 1:		Line 1:
	Git is the [[version control system]] used by RoboJackets for much of the code (we've moved some stuff over from SVN).		Git is the [[version control system]] used by RoboJackets for much of the code (we've moved some stuff over from SVN).

-	Note: this page is a work in progress!!!	+	=Note: this page is a work in progress!!!=


-	===Setup ~~Git=~~==	+	==Setup==
	* [http://git-scm.com/downloads Download Git]		* [http://git-scm.com/downloads Download Git]
	* Each commit you make has your name and email address on it. Tell Git what these are with these commands:		* Each commit you make has your name and email address on it. Tell Git what these are with these commands:
-	:"'$ git config --global user.name "~~John Doe"'~~"	+	<code>
-	:"'$ git config --global user.email ~~johndoe~~@~~example~~.~~com'"~~	+	:$ git config --global user.name "George P. Burdell"
		+	:$ git config --global user.email gburdell@gatech.edu
		+	</code>

	==Commands==		==Commands==
-	These are common commands that will get you started. There are more but you can discover those on your own.	+	These are common commands that will get you started. There are more but you can discover those on your own.
		+
		+	When using git through command line, first change your directory to the repository. So if your code is on your desktop in a folder called "repo", execute this command.
		+
		+
	===clone===		===clone===
	This will be the first command you run before you start to work on a project for the first time. It will ask the server for a list of files at a certain location and then download those files to your computer. These files then become the ''working copy'' that you can edit.		This will be the first command you run before you start to work on a project for the first time. It will ask the server for a list of files at a certain location and then download those files to your computer. These files then become the ''working copy'' that you can edit.
Line 17:		Line 23:
	The commands are all shown from the command-line. There are graphical tools available but a good command-line understanding will help in using the graphical tools.		The commands are all shown from the command-line. There are graphical tools available but a good command-line understanding will help in using the graphical tools.

-	Usage:<br>	+	Usage:
		+	<code>
	:'''$prompt: git clone <remote-path>'''		:'''$prompt: git clone <remote-path>'''
-	:"'$prompt: git clone <remote-path> <local-path>'"	+	:'''$prompt: git clone <remote-path> <local-path>'''
		+	</code>
	* The remote path is the location of a directory on a Git server that has the files you want to check out. This will usually be given to you by the project lead or maintainer.		* The remote path is the location of a directory on a Git server that has the files you want to check out. This will usually be given to you by the project lead or maintainer.
	* The local path is the location to store the files. If you don't specify a local path, Git will place create a new folder in the current directory with the same name as the copy on the server.		* The local path is the location to store the files. If you don't specify a local path, Git will place create a new folder in the current directory with the same name as the copy on the server.
Line 25:		Line 33:
	===add===		===add===

		+	===commit===
		+
		+	===push===
		+
		+	===pull===

	[[Category:How to Guides]]		[[Category:How to Guides]]

Version control system

2012-05-16T05:08:42Z

← Older revision		Revision as of 05:08, 16 May 2012
(One intermediate revision not shown)
Line 9:		Line 9:

	The most well known version control systems include:		The most well known version control systems include:
-	* [~~http://en.wikipedia.org/wiki/Concurrent_Versions_System Concurrent Versions System~~] ~~(CVS)~~	+	* [[Git]]
	* [[Subversion]] (SVN)		* [[Subversion]] (SVN)
-	* [http://en.wikipedia.org/wiki/BitKeeper BitKeeper]

Git

2012-05-16T05:07:26Z

New page

Git is the [[version control system]] used by RoboJackets for much of the code (we've moved some stuff over from SVN).

Note: this page is a work in progress!!!

===Setup Git===
* [http://git-scm.com/downloads Download Git]
* Each commit you make has your name and email address on it. Tell Git what these are with these commands:
:"'$ git config --global user.name "John Doe"'"
:"'$ git config --global user.email johndoe@example.com'"

==Commands==
These are common commands that will get you started. There are more but you can discover those on your own.
===clone===
This will be the first command you run before you start to work on a project for the first time. It will ask the server for a list of files at a certain location and then download those files to your computer. These files then become the ''working copy'' that you can edit.

The commands are all shown from the command-line. There are graphical tools available but a good command-line understanding will help in using the graphical tools.

Usage:<br>
:'''$prompt: git clone <remote-path>'''
:"'$prompt: git clone <remote-path> <local-path>'"
* The remote path is the location of a directory on a Git server that has the files you want to check out. This will usually be given to you by the project lead or maintainer.
* The local path is the location to store the files. If you don't specify a local path, Git will place create a new folder in the current directory with the same name as the copy on the server.

===add===

[[Category:How to Guides]]

Main Page

2012-05-16T04:47:17Z

← Older revision		Revision as of 04:47, 16 May 2012
Line 61:		Line 61:
	* ''[[How to Guides]]''		* ''[[How to Guides]]''
	* [[Subversion]]		* [[Subversion]]
		+	* [[Git]]
	* [[Wtodo\|Wiki and Server TODO]] Wiki and server feature requests		* [[Wtodo\|Wiki and Server TODO]] Wiki and server feature requests
	* [[Info\|RoboJackets Information]]		* [[Info\|RoboJackets Information]]
	* [[TE Sessions Book]]		* [[TE Sessions Book]]
	\|}		\|}