Quote:
Originally Posted by teekon
-- What would be the pros and cons of having different languages like java and c++? I feel comfortable with just using c since thats all we have had so far and i dont really want to learn another language because then that puts me back this year. I think some upgrades on the motion board would be nice though! -- Teekon 
I was also wondering if any one has tried programming their robot using LabView? -- Teekon |
I think this might be going off track for this thread, but not sure what other related threads it might go with, so i'll just put it here...
I agree that its a good idea to stay with C... it works great for the application.
On your note about LabVIEW, I've used it before, its ok, but, its near impossible to document your code, EVERYTHING is passed by value, the 'code' (pictures) you make get really complicated to follow... but yes, i know the interaction it provides between various sensors, platforms and interfaces (the first thing i did with labVIEW in about 5 minutes from out of the box to application running was flip a switch hooked to a USBdaq, and it sends me an email saying "you hit the switch"), not to mention so simple its scary integration of extremely powerful vision processing.
Other than that, I can't see IFI/FIRST putting a processor big enough to run
LabVIEW Embedded. It only runs on 32bit processors like Blackfins, mot PowerPCs, mot ColdFires, etc. While the cost IS comming down for big 32bit dsp-type processors, i don't think its cheap enough yet to happen.
Cool idea though...
-q
p.s. In the defense of lab view... imagine having
ONE OF THESE for a coprocessor!!!!!