Download from RC back to computer?

[Eldarion]

To avoid this type of problem in the future, maybe it would be a good idea if teams taped a CD with the code on it to the robot before mothballing it?

That way, 5 years down the line when no one on the team had the code, it will be sitting there on the CD with the robot.

Just a thought!

[EricH]

Originally Posted by Eldarion

To avoid this type of problem in the future, maybe it would be a good idea if teams taped a CD with the code on it to the robot before mothballing it?

That way, 5 years down the line when no one on the team had the code, it will be sitting there on the CD with the robot.

Just a thought!

CVS server. (CVS stands for Concurrent Versioning System.) What it does is it keeps old versions of code and changes to said code around for until they are removed. This way, you can make a change and still get your working code back if the new code "dies". Not only that, but multiple programmers can work on the same code without having to send each other code bits or even talk to each other. (To use here: keep the most recent code for each year on the server, until that robot dies totally and completely. Then use code to teach newbies...) Just be careful--mechanicals and photographers may also want to use the CVS to share stuff! (By the way, I'm not a programmer and don't know how to set one up.)

[Astronouth7303]

Originally Posted by EricH

CVS server. (CVS stands for Concurrent Versioning System.)

I'd recommend Subversion over CVS. It is less painful to set up, more flexible in terms of operations, and less quirky.

Just be warned: The 2004-2005 controllers used the PIC18F8520, while the 2006-2007 controllers use the PIC18F8722. Code compiled for one will not work on the other. It may be easier to swap the controllers.

[ericand]

We used subversion, but when we tried using branches late in the project, we had a lot of trouble getting things to merge back and sync up. If you have a pointer to any documents that cover this with examples I would greatly appreciate hearing about it.

We used the command line and tortise SVN for a windows GUI. I've read the SVN manual and tortise documentation about branches, but I think I'm missing something since I don't think it should be so hard.

Originally Posted by Astronouth7303

I'd recommend Subversion over CVS. It is less painful to set up, more flexible in terms of operations, and less quirky.

Just be warned: The 2004-2005 controllers used the PIC18F8520, while the 2006-2007 controllers use the PIC18F8722. Code compiled for one will not work on the other. It may be easier to swap the controllers.