View Single Post
  #52   Spotlight this post!  
Unread 24-04-2012, 01:39
AustinSchuh AustinSchuh is offline
Registered User
FRC #0971 (Spartan Robotics) #254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Feb 2005
Rookie Year: 1999
Location: Los Altos, CA
Posts: 803
AustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond repute
Re: TI and future Jaguars

Quote:
Originally Posted by techhelpbb View Post
The problem that will crop up is that FIRST is going to want to approve something so they'll need to see something tangible in operation. If you create something for one or many existing modules on a PC and it doesn't change the possibly already approved software in that module then it shouldn't be a problem. However, if you alter the module's software you the open proverbial can of worms.
That is definitely an issue. Though once again, you could do what they did for the Jaguars, and add it in after a year as a firmware upgrade. And who says that the interpreter has to be fancy or anything? Forth, basic, scheme(!)... There has to be a simple interpreter already out there. Scheme would be really easy to write, too. There is very little to no syntax. Or something like Logo, or ...

One of the really valuable parts of having a control language is that you can run things that matter and are custom at very high frequencies (1khz), and it can be sandboxed so that FIRST is always in control. Without having to mess with extra hardware which adds significant development and manufacturing challenges.
Reply With Quote