LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

No Targets and Devices


@cbutcher wrote:

@JensG69 wrote:

Hi Bob,

 

a link to the next readme, this time NI CompactRIO 21.0

 

It states:

"Note  The myRIO-1900 and myRIO-1950 are not supported in NI CompactRIO 21.0 and Drivers. Use version 20.5 or earlier for these devices."

 

Regards, Jens


Huh?! Aren't the myRIOs current hardware? I don't see anything on the Store that seems to indicate they're EoL or "mature"... seems odd to drop support in the drivers.

 

Or is this just that the cRIO driver no longer contains it, and there is still a suitable 2021 driver, it just isn't part of the CompactRIO group? (I couldn't see a 2021 myRIO Toolkit or Software Bundle, but then I also don't know if the contents of those are relevant or they are instead the Express VIs and default FPGA personality and so on).


myRIOs are "current hardware", and according to people I consulted at NI, they expect to have at least a 4-5 year future as hardware.  As for Software, NI did not release a LabVIEW 2020 version of the myRIO Software Toolkit (which largely precluded "getting started with myRIO" with LabVIEW 2020 -- I've been using LabVIEW 2019 quite satisfactorily).  I asked an NI Executive if a myRIO Software Toolkit would be released for LabVIEW 2021, and he replied that it was coming, but might be a little late (I anticipate a month or so).  It was certainly not available at the beginning of this week ...

 

Bob Schor

0 Kudos
Message 11 of 22
(2,346 Views)

@clicks wrote:

Thanks for the comments. I understood that not all devices are supported on LV 2021(64). But I can not add any device. Also, I can not add any DAQmx task (they are also not recognized in existing projects). There must be something wrong with the insallation. I did install everything with the Package Installer. What can I do to find out what is wrong or fix the problem ?   


Can you see the devices in MAX? (You originally mentioned some configuration via MAX, so perhaps yes?)

 

Can you post a list or screenshot of the packages installed that match the following search in NI Package Manager: "Support for LabVIEW 2021"? (don't use quotes).

 

When I carry out this search, I get results like the following (A subset below, I have 32+64 bit installed, but perhaps not the same packages for each):

  • NI CompactRIO FPGA Target Support for LabVIEW 2021 (various bitness, common files etc)
  • NI CompactRIO Module Support for LabVIEW 2021
  • NI myRIO FPGA Target Support for LabVIEW 2021 (32-bit)
  • NI System Configuration Support for LAbVIEW 2021 (32 + 64 bit, two packages)
  • NI-DAQmx Support for LabVIEW 2021 (32, 64)

I expect the one in bold is probably important, but that's just a guess at what you might be missing.

 

If you don't have some of these, and you think you should, you can search the "Packages" tab (if you don't have a packages tab, click on the Gear/Settings icon at the top right and choose the "Show available packages and ..." option) and install them 'manually' from there.

Typically these packages are installed as "recommended" during the installation of LabVIEW or cRIO modules, but what gets picked up for specific packages is sometimes confusing to me (and I often unselect options from that list, if you do the same it's possible you unchecked something you needed).


GCentral
0 Kudos
Message 12 of 22
(2,336 Views)

thanks cbutcher for the hints. 

 

The NI CompactRIO Module Support for LabVIEW 2021 was installed. The same for the DAQmx Support. 

 

I gave up on LV 2021 and focus now on LV 2020. I have installed both 32 and 64. The 32 looks all good: DAQmx, IMAQmx, USRP, CompactRIO, all is there. The 64 bit version again has the original problem: I can not add daq tasks in a project, projects with existing daq tasks show a yellow attention icon for the tasks, I can not add any CompactRIO devices etc. 

 

I checked for the installed packages and all support packages are installed: 

clicks_0-1630568831576.png

I also tried to repair all these packages, or even uninstall and reinstall them. The 64 bit LabVIEW does not recognize the devices of daq tasks. 

There seams to be something wrong with the installation of 64 bit LabVIEW. I have this problem with the 2019,2020 and 2021 versions. the 32 bit versions work ok. 

What else can I try to make the 64 bit versions work? 

 

 

 

0 Kudos
Message 13 of 22
(2,310 Views)

It may simply be that there is not yet 64bit support for cRIO.
Indeed it may not be an advantage on the RIO side to have 64bit code, so keeping the code 32bit on the PC side would keep the interface leaner and cleaner.

Just stick with 32bit LabVIEW.
I'm only on 64bit as I'm not using MAX in my current role at all, otherwise I still wouldn't dare drop 32bit - it's far better supported and more stable for small connected devices.

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 14 of 22
(2,303 Views)

Hey James_W, thanks for the recommendations. I use LV 32 whenever I can, but I have some big projects that involve Vision and large data streams from USRP that run all on LV 64. I need to upgrade to at least LV 20 but I am stuck. So there is no way around.  Not only CompactRIO is not showing up, but also no DAQmx Tasks! I need them. 

 

0 Kudos
Message 15 of 22
(2,297 Views)

So I think there are definitely more devices supported in 32-bit than 64-bit, as an example (but again, I don't claim to have exactly the same/correct set of packages in 64-bit as 32-bit) I see this for 2021:

 

cbutcher_0-1630576357183.png

Note that although lots of devices aren't there, there are some (in case it's not obvious, that's 32-bit on the left and 64-bit on the right).

 

Conversely in 2019, I see this for the "Create Project" window:

cbutcher_1-1630576526325.png

 

and for the targets and devices:

cbutcher_2-1630576573748.png

 

In 2019, the RT Module wasn't available for 64-bit, and I don't have a PXI chassis, so probably I never chased down the packages. I will note for the images above that the following are installed:

  • NI CompactRIO (v19.0.0)
  • NI CompactRIO Driver (v19.0.0)
  • NI CompactRIO FPGA Support for Real-Time Embedded Targets
  • NI CompactRIO FPGA Target Support for LabVIEW 2019 (32-bit and 64-bit, two packages)
  • NI CompactRIO Module Support for LabVIEW 2019 (v19.0.0) (note this is an x86 package, not shown in the title but the package name, hover in NIPM)
  • NI-RIO cRIO Firmware for NI Linux-RT Real-Time Embedded Targets (v19.0.0)
  • NI PXI Platform Services (v17.0.0)

I think getting RT targets working in 64-bit LabVIEW before 2021 is unlikely to work (not to be confused with the bitness of the target, which is often 64-bit... go figure).

 

In LV2021, it should be possible to do some things, and get at least some targets, but as crossrulz noted in the first page, a lack of FPGA support for many targets makes it less relevant/appealing (at least for me).

 

Note that lots of DAQmx devices usually don't show up in the New Targets and Devices window - that is (afaik) for remote devices that can be programmed at least in principle without a connected PC (although the DAQmx driver is relevant to e.g. cRIO-904x, which can use DAQmx and also run without a PC, they appear in the New Targets and Devices list just fine, as do the cDAQ controllers like cDAQ-9134).

Which device(s) are you actually trying to use?


GCentral
0 Kudos
Message 16 of 22
(2,293 Views)

@clicks wrote:

Hey James_W, thanks for the recommendations. I use LV 32 whenever I can, but I have some big projects that involve Vision and large data streams from USRP that run all on LV 64. I need to upgrade to at least LV 20 but I am stuck. So there is no way around.  Not only CompactRIO is not showing up, but also no DAQmx Tasks! I need them. 

 


Also worth noting is that you don't have to write your RT code in the same IDE as your desktop code. So you can write RT code and FPGA code in 32-bit, then compile and upload the RTEXE, and then go ahead and use 64-bit LabVIEW to program the desktop application.

 

This gives you more memory in the location where you probably actually have more memory available, just at the cost of having to give up a bunch of disk space for two installations.


GCentral
0 Kudos
Message 17 of 22
(2,292 Views)

It is actually about DAQmx-Tasks not DAQmx Devices. When I open a project in LV 2020(64) it looks like this (note the daqmx tasks in yellow): 

clicks_0-1630582792428.png

 

 

I can also not add any DAQmx-Task in the project. And also no targets (like the USRP). There is something wrong with the installation and I need to fix this. But what else can I do? 

 

in LV 2020(32) it's ok, but my application needs to run on 64 bit and has done so in LV 2019. 

clicks_1-1630583237981.png

 

 

0 Kudos
Message 18 of 22
(2,265 Views)

@clicks
as has been previously stated,
You are confusing the Dev environment with the deployment.

you can develop in LabVIEW 32bit and deploy to 32 or 64bit systems, however if you develop in LabVIEW 64bit you can ONLY deploy to 64bit systems. It looks like the tasks you have are not supported in 64 bit LabVIEW...

but that is not a problem, compile from 32bit LabVIEW and install on a 64bit OS and they will run fine - they just won't use ALL of the processing power available to the PC.

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 19 of 22
(2,259 Views)

Dear James 

Indeed I am very confused about your weired comments. My Application needs much more than 4 GB of Ram (video buffering and USRP streaming). I can not run it under 32 bit, not in the dev environment and also not compiled. I am not confusing dev environment and deployment as you wrongly suppose.  

DAQmx tasks should be very well supported under LabVIEW 2021(64). And as I clearly indicated, I can not add any DAQmx task under a project in LV 2021(64). There is clearly somthing wrong with the installation and I am asking for some help how I could identify and solve the problem. 

 

 

 

0 Kudos
Message 20 of 22
(2,247 Views)