Quote:
Originally Posted by Russ Beavis
Depending on the cost of a spare cRIO (hopefully we'll get that info soon), you might want to consider dueling software teams - one with C/C++ and one with LabVIEW.
Another option to consider is a LabVIEW-based Dashboard app and C/C++ robot programming. There's definitely room for both.
You may even be able to use C code within LabVIEW and have high-level "systems engineers" coding in LabVIEW and "low-level software engineers" coding in C. However, I'm not sure whether the FRC version of LabVIEW will provide Code Interface Nodes or similar for integration with C code.
|
LabVIEW Full for FRC supports call library nodes. You can build a .out file from your C/C++ code using the WindRiver tools and then call that code from LabVIEW using the Call Library Node. The entry points that you want to call from LabVIEW need to be C functions (and C calling convention). Code Interface Nodes are not supported on the cRIO... they are deprecated even on Windows favoring Call Library Nodes.