LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

R series runtime resource selection

Hi,

 

I have multiple NI -7841R PCIe cards installed in PC so when I created host aplication (wich was eventualy an exe) I created a drop down selection menu so user could decide wich resource (RIO 0, RIO 1....etc) will be alocated. It was all great with LV2011 and FPGA module 10.1 and 12.4. I deployed the aplication on fresh windows7 PC with a 7841R PCIe card. I installed the LV 2011 runtime and RIO drivers and aplication worked flawlesly - by that I mean user could select  FPGA resource in aplication. 

Then came LV2012 nad FPGA tools 13.x. I recompiled FPGA VIs and rebuild main aplication. On Development machine everything worked fine - again by that I mean user could select FPGA resource in aplication. OK so far so good. On the same target PC that aplication worked previously I installed LV2012 runtime (LV2011 runtime was left untouched - just in case)  and deployed the aplication. Suddenly I was not able to select the resource by the drop down menu (it was grayed out). I tried all options in "Configure Open VI FPGA reference" hoping it will solve the problem but non works. What is strange is that MAX on target PC (MAX came with 7841R drivers) sees the FPGA card just fine.

 

I noticed even stranger thing: If I build exe application with option "disconnect type definitions" and select VI in "Configure Open VI FPGA reference" then deployed aplication requires controls / typedefs of FPGA(!!!!!) part! That did not ever happen in all the years I'm working with FPGA.

 

Any ideas?

 

Cheers

 

0 Kudos
Message 1 of 4
(2,600 Views)

Hi!

 

The problem that you've described seems like a compatibility issue to me. Make sure to update to the 12.0 version of the NI-RIO driver, as this is the one that handles FPGA support, and also this is the version in which support for LabVIEW 2012 was added. 

 

If this does not help, please tell me if there are any major differences in the Development and Target environments (OS, drivers, or such).

 

Kind regards:

 

Andrew Valko

National Instruments

Andrew Valko
National Instruments Hungary
0 Kudos
Message 2 of 4
(2,536 Views)

Hi ValkoA,

 

I think the compatibility is the issue here aswell, however I find it strange that no message at runtime is thrown about that. The system finds the 7841R fine through MAX but, my deployed app throws no error msg. I intentionally left error cluster unconnected so that runtime would give me some info but there was none. At least the host FPGA hook should throw driver version incompatibility if nothing else....

As for the differences in the Development and Target environments: OS is the same on both PCs, drivers of RIO on target PC are older as those on development PC.

I wil try updating target PC's RIO drivers as you sugessted and will let you know if problem is fixed.

 

regards,

 

D

0 Kudos
Message 3 of 4
(2,521 Views)

Dear D,

 

I would suggest using an error wire instead of automatic error handling, as it is disabled on .exe applications. Just create an indicator to the error output, you can even remove it later, or replace it with a Simple Error Handler.

 

Regards:

 

Andrew Valko

Andrew Valko
National Instruments Hungary
0 Kudos
Message 4 of 4
(2,515 Views)