PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

NI PXI 5644/5646 equipment : nisyscfg.lib:Find Hardware.vi Error -2147220623

Hello, 

I'm troubleshooting a project when switching a source code that have been developed with the 2013 version of LabVIEW to the 2015 Version. 

These are the releases of the software and the drivers that i'm using : 

- Labview 2015 with p3 patch

- NiVST 15.02

- Ni Sync 15.01

- Ni System Configuration Runtime 15.0

The vi Nisyscfg.lib:Findhardware returns the error  -2147220623 with LabVIEW 2015 but it worked well with LabVIEW 2013 . 

Does any developer experienced such problem when switching to the 2015 release of LabVIEW ?

Any suggestion for this problem would be appreciated . 

 

Mourad FAKHFAKH 

Signal Processing Engineer 

M3systems France

 

Afficher l'image d'origine

 

0 Kudos
Message 1 of 3
(3,801 Views)

Hi Mourad_FAKHFAKH 

 

Are you by chance using the NI-RIO driver? I was able to find a similar issue with a VST involving different versions of RIO:

 

http://digital.ni.com/public.nsf/allkb/265822A546F1E28186257C13006639B9?OpenDocument

 

I found another document detailing that error code for the VST and IDLs. 

 

http://www.ni.com/product-documentation/14998/en/

 

What exactly does the error message say? 

 

Thanks

-Jayk

RF R&D
National Instruments
Message 2 of 3
(3,782 Views)

Hi Bumblebee_Tuna,

Thank you for your response, I finally found the solution for my problem. 

Here attached a snapshot of the Vi with which I have been having trouble.

 

The find hardware vi itself didn't caused the error, it's rather the vi's output when linked with 'System Hardware' property node.

The Property node System hardware outputs the -2147220623 error with the following error message :

 

Possible reasons  :

NI System Configuration:  (Hex 0x80040371) Property does'nt exist for the following ressource.

 

Executing this VI alone just ouputs the following error ( before erasing the error ) . When included in a project, the vi causes a freezing GUI .

The solution for my problem was just to refresh the input session constant. It may be due to the fact that the hardware plugged to the PXI board has been changed .

I hope this will be useful. 

 

Mourad FAKHFAKH 

Signal Processing Engineer 

M3systems France

 

Afficher l'image d'origine

0 Kudos
Message 3 of 3
(3,767 Views)