View Single Post
  #41   Spotlight this post!  
Unread 14-11-2007, 12:48
EricS-Team180's Avatar
EricS-Team180 EricS-Team180 is offline
SPAM, the lunchmeat of superheroes!
AKA: Eric Schreffler
FRC #0180 (SPAM)
Team Role: Engineer
 
Join Date: Apr 2002
Rookie Year: 2001
Location: Stuart, Florida
Posts: 561
EricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond reputeEricS-Team180 has a reputation beyond repute
Re: Opinions wanted: LabView-based controller?

Quote:
Originally Posted by Chris Hibner View Post

More recently, products have been developed to "cut out the middle man" (i.e. the software engineer) and automatically generate the C code from the block diagrams.
The aerospace industry incorporated "pictures-to-code", starting back in the 1980's. It never truly eliminated the middle-man, since we aero's needed software engineers to develop and maintain the process and keep porting it to new hardware platforms!

Easy-C for FTC and FRC is a pretty decent implementation of the concept. While we use Easy-C for all our FTC teams' programming, we teach C and write customized code at the FRC level.

After trying out LabView 2 years ago, in the pilot project, and after reading through this thread, I have to align myself with those who'd accept LabView as an option for coding the FRC, but - please - not the only option.

Thanks,
Eric
__________________

Don't PANIC!
S. P. A. M.