LabVIEW
program board with Labview tools
Hi shabgol,
@shabgol wrote:
1-Which boards can be programmed with Labview tools? just National Instrument,
2-Does NI boards(SBRIO 9637) program only with labview tools?
- Yes.
- This depends on the OS of that specific sbRIO (read its datasheet)! When it is based on NI-Linux then you can also use specific Linux tools, otherwise you should use LabVIEW only…
@GerdW wrote:
Hi shabgol,
@shabgol wrote:
1-Which boards can be programmed with Labview tools? just National Instrument,
2-Does NI boards(SBRIO 9637) program only with labview tools?
- Yes.
Small correction: With the Linx (NI LabVIEW Hobbyist Toolkit) you can also target a Raspberry Pi and a Beaglebone Black directly (although Beaglebone Black is at this point probably more a historical option as I don't quite see it around a lot anymore).
Other than that, yes LabVIEW does not support 3rd party embedded controller boards. There were some attempts to provide a Toolkit to support that on other embedded controllers but that model turned out to be unsupportable. In order for someone to be able to adapt the Toolkit to a specific board (s)he had to be a full featured embedded software developer with very detailed knowledge about the target board in question. Such people are almost never willing to even think about using LabVIEW for their work, since they can create applications much quicker with the dedicated development tools for the platform.
This leads to the situation that those who could master this feat, are all very unlikely to ever even want to work with LabVIEW and the ones wanting to use LabVIEW on such a hardware are simply not capable to adapt the Toolkit to their hardware. And NI can't for obvious reason support all the zillion embedded controller targets out there themselves. I would estimate that the cost for an adaption of that toolkit to a specific hardware target was anywhere between $20k to $100k to get it not only up and running to allow creating a hello world console application from LabVIEW but actually be able to create real applications. And that doesn't necessarily include additional hardware driver interfaces for various analog/digital and communication channel interfaces. These are always application specific and not always easy to generate either. And there simply hasn't been anyone really willing to foot such a bill for a specific target. NI obviously neither, aside from a few example implementations for specific targets, as they don't get a single penny from those boards.
