LabVIEW
Labview 2020 Community Edition - Does it support Legacy Hardware?
Solved!
@pazarci wrote:
I am not an experienced labview user, but I have taken advantage of the community edition, installed daqmx 15.5.1 without a problem and I am using my 12 year old ni-usb 6009 usb daq module without a problem. I was hesitant at the beginning because it was not clear whether it would work, so I made an image backup of my system drive in case it does not work and I need to go back. I am using win10 pro 20h02 edition on an Asus n752vx notebook.
15.5 doesn't support 2020 officially, but I'm happy to hear it worked for you.
Though, if you check daqmx 20 it supports the 6009. 😉
@RochelleS wrote:
@rolfk wrote:
But, the Community Edition is supposed to contain (if it doesn't already in the Beta) an updated and NI maintained version of the Linx Toolkit which allows to target LabVIEW to single board computers of the Raspberry Pi and BeagleBone Black family. This while not truely real-time enabled like the RIO targets from NI, works very much like one of the RIOs where you develop your code on your computer and deploy it to the respective target board to be executed there. Linx also supports Arduino but not as target to deploy LabVIEW code on. Rather you develop an application in your favorite Arduino IDE and deploy it to the board and then Linx comes with communincation libraries to talk to that app from LabVIEW over serial or TCP/IP.
This is not really true... In my experience, LINX basically turns an Arduino/BBB/R-PI into a DAQ like device that needs to always be "tethered" to a host computer running LabVIEW. Now that "tether" can be USB (Arduino) or Ethernet (R-PI/BBB) even wireless but it has to be there. LabVIEW is not really running on the target device, but a small stub that communicates with a LabVIEW application running on the host PC is.
It is true. You can do exactly what rolfk mentioned. I've done it myself. You can even have it set to automatically run on SBC bootup.
@RochelleS wrote:
@billko wrote:
@RochelleS wrote:
@rolfk wrote:
But, the Community Edition is supposed to contain (if it doesn't already in the Beta) an updated and NI maintained version of the Linx Toolkit which allows to target LabVIEW to single board computers of the Raspberry Pi and BeagleBone Black family. This while not truely real-time enabled like the RIO targets from NI, works very much like one of the RIOs where you develop your code on your computer and deploy it to the respective target board to be executed there. Linx also supports Arduino but not as target to deploy LabVIEW code on. Rather you develop an application in your favorite Arduino IDE and deploy it to the board and then Linx comes with communincation libraries to talk to that app from LabVIEW over serial or TCP/IP.
This is not really true... In my experience, LINX basically turns an Arduino/BBB/R-PI into a DAQ like device that needs to always be "tethered" to a host computer running LabVIEW. Now that "tether" can be USB (Arduino) or Ethernet (R-PI/BBB) even wireless but it has to be there. LabVIEW is not really running on the target device, but a small stub that communicates with a LabVIEW application running on the host PC is.
It is true. You can do exactly what rolfk mentioned. I've done it myself. You can even have it set to automatically run on SBC bootup.
With an interactive Front Panel on the PI?
It doesn't have to have a UI to be LabVIEW code running on a target. And to be sure, my application running on the PI has real, physical buttons on it, so it does have an interactive front panel - just a physical one, not a virtual one.
