05-23-2020 12:26 PM
The LabVIEW 32 bits sample call a Property Node attached to an IVI driver 32 bits and is working. The IVI driver is initialized through a call to LabVIEW IVI warpper ivi.* that call the generic Ivi_InitWithOptionsAndGetError, then call Property Node and last is calling LabVIEW IVI warpper ivi.* closing function Ivi_CloseAndGetError. The 32 bits sample works and return the value of chosen property of the PropertyNode. In LabVIEW 64 bits the PropertyNode sample that uses the same LabVIEW IVI generic wrappers for Ivi_InitWithOptions and Ivi_CloseAndGetError that I assume call LabVIEW 64 bits IVI would call same PropertyNode. The PropertyNode sample shows OK but return an error code 12 as (arg1) that refers to the only property called that remains without response. I tried many IVI drivers for different instruments and while PropertyNode works always for LabVIEW 32 bits is always failing for LabVIEW 64 bits? I attached a screen shot of my PropertyNode sample with (arg1) error.
05-23-2020 02:46 PM
If this is a standard NI driver, make sure that you install your drivers all over again after you installed LV 64-bit. This makes all your drivers "aware" that you have a new version of LabVIEW to provide driver support for.
05-25-2020 02:44 PM
This is not a standard NI driver but a proprietary IVI driver that uses LabVIEW Tools->Instrumentation->Import LabWindows/CVI Driver Wizard to convert my driver .fp interface file to labVIEW standard IVI functions. All my 64 bits IVI driver are installed after LabVIEW 64 bits has been installed.The 64 bits IVI driver interface works OK in other programmimg languages as C, C++, C# and VB.NET without any problem. The labVIEW 32 bits IVI drivers works fine too so I assume with a high probability that the blockage is part of LabVIEW 64 bits usage of Property Node that must be different than the usage of same PropertyNode in LabVIEW 32 bits.
05-25-2020 04:20 PM - edited 05-25-2020 04:21 PM
Oops I didn't read carefully enough.