View Single Post
  #68   Spotlight this post!  
Unread 23-09-2008, 16:10
BLAQmx's Avatar
BLAQmx BLAQmx is offline
Software Engineer
no team (National Instruments)
Team Role: Engineer
 
Join Date: Sep 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 100
BLAQmx is a glorious beacon of lightBLAQmx is a glorious beacon of lightBLAQmx is a glorious beacon of lightBLAQmx is a glorious beacon of lightBLAQmx is a glorious beacon of lightBLAQmx is a glorious beacon of light
Re: Programming with the 2009 controller

Quote:
Originally Posted by steveg
One thing I haven't seen, though, is cost. Is LabView embedded royalty-free? If you're paying even a few $/processor that uses it, I can see how that would be a major detriment to the industry adopting it. I think there's a couple reasons why many people who develop microcontroller applications, would shy away from LV. If you're doing something more than just a simple task, it's really easy to become limited, by code size, core frequency, etc... and there's still the conception that things like LabView have a huge amount of overhead.
The LabVIEW Embedded Module for ARM is royalty free. There is no deployment license for LabVIEW Embedded Module for ARM.

Its always interesting to hear about the amount of "overhead" LabVIEW incurs. One should keep in mind that when C was first developed many engineers stated the same thing regarding overhead. Luckily as compilers improved so did engineers opinion of C. Furthermore LabVIEW is extremely optimized compared to inline C for multi-threaded muti-core programming.

When the LabVIEW Embedded code is deployed to a (supported ) ARM processor it is converted into C++ code. While this is not as efficient as programming in C the difference may eventually be unnoticeable. Isn't that the whole point of innovation?

In regards to the 2009 controller there should little performance difference between LabVIEW and C/C++.
__________________
NI FIRST Community: Where to go for LabVIEW, Wind River, cRIO-FRC, and NXT support.