Thread: Programming old robots
View Single Post
  #2   Spotlight this post!  
Unread 26-10-2011, 18:12
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
  
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,801
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Programming old robots
To begin with you can just keep the programs that are already on them, for driving and mechanisms they'll have workable controls already setup. (2014 robots?)

If your purpose is to teach programming, then the software for the IFI controllers will depend on the year/model, but you can cobble together freeware/student versions/old IFI sw to make a working C environment. There are a few threads on doing that, and we can help.

The cRIO controllers could be programmed in free Java tools, but the cRIO and your programming environment will have to have compatible setups for that. If you have both 2009 and 2010 robots, then they could already be imaged for Java if the team originally programmed in that, but they might have different generations of cRIO images, and would need different WPI libraries to match. Probably meaning you need to connect with another local team long enough to get your cRIO's imaged for Java, then take and freeze the current Java WPI libraries to use in the future with those cRIOs.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Last edited by Mark McLeod : 26-10-2011 at 18:29.