RF Measurement Devices

cancel
Showing results for 
Search instead for 
Did you mean: 

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.

 

I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 

 

I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 

 

I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 

 

The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

0 Kudos
Message 1 of 30
(7,375 Views)

I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 

 

When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 

0 Kudos
Message 2 of 30
(7,359 Views)

The last 2 screenshots.

Download All
0 Kudos
Message 3 of 30
(7,358 Views)

Hello Brindlaj0113,

 

In reference to error 1445, the Dynamic Path subvi within MT Initialize Receiver(RFSA).vi tries to figure out if it is being run in the development system or runtime. Therefore it expects mod_Set Reciever(RFSA).vi to be at the same level as its caller, but this doesn't look like its the case. The best solution is to not use the Runtime Engine on a non-deployed system. There really isn't a good use case for it since it has to relink most of its VIs and is very slow that way. If its deployed, just make sure the Dynamically called VIs are in the SupportVIs directory at the same level as the caller. If the other errors persist when using the developement environment on a non-deployed system, then let me know which errors stick around and we may continue trouble shooting.

Regards,

Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments
Message 4 of 30
(7,333 Views)

Hi ,

I have the same problem using Labview Runtime Engine 2011 and Teststand 2010 SPI

There is some action/news to solve the problem ?

 

Thank you

 

0 Kudos
Message 5 of 30
(7,109 Views)

Hello maestroyoda,

 

Will you please share your current setup so that I'll be better able to assist you?  What type of hardware are you using in your application?  Which software and versions are you using?  Do you get an error on your development machine or is the error limited to your deployment machine?  Do you have screenshots that you can provide?

 

Thank you.

 

Regards,

 

Marcus 

Marcus M.
PXI Product Support Engineer
National Instruments
0 Kudos
Message 6 of 30
(7,082 Views)

Hello Marcus

The setup of my application is

PXIe 1065

NI 5600+NI5620

Labview 2011

TS 2010Sp1

NIRFSA 2.4.5

Spectrum measurement toolkit 2.6.1

 

The application have to get a Peak and frequency measurement of an RF 433MHz signal . The problem is that when switch from LV Runtime engine To LV development sistem in TS the Vi  is broken because there is a link error with the nipxi5600u.dll.

Moreover , i note that when  run my application more than one time the ram occupation increase at every run and if try to make a continuous run i recieve Error -17000 out of memory. 

 

In attachment the vi that i use to get the measurement so you can help me to understand if there is  something wrong  on the application .

 

Thank you

 

MaestroYoda

 

 

 

 

0 Kudos
Message 7 of 30
(7,073 Views)

Hi MaestroYoda,

 

When you run the VI continuously how long does it take for the memory to become full?  Does it take only a few runs or does the program run for a long time before the memory becomes full?  

 

I have looked at your code and have found no apparent reasons that the code should be causing a memory leak.  I am going to get a NI 5600 + NI 5620 and will run the code to do some troubleshooting on my end.  

 

In the mean time will you please post a screenshot of your TS setup and the error message that occurs in your sequence? 

 

Regards, 

 

Marcus

Marcus M.
PXI Product Support Engineer
National Instruments
0 Kudos
Message 8 of 30
(7,056 Views)

Hi Marcus

The test that i'm performing takes all night long but it stops after about 4 hour of working for memory error .

I run the my test sequence using a UI ( this is a simple LV UI model modified  in attachment the main VI so you can eventually verify if there is something that can cause the memory problem)

In attachment you can find

the screenshot of the Dll error i told you last time ,

the Screenshoot of TS configuration

And a Zip file that contain the TS model that i'm using, a copy of sequence file and the UI main vi

So you can better investigate and understand the setup

 

 

Thank you for help

 

 

 

 

 

Download All
0 Kudos
Message 9 of 30
(7,041 Views)

Hi MaestroYoda,  

 

Thanks for sending me screenshots of the error and also you TestStand model.  I looked at the screenshots and I saw that you were getting an error bing in the one titled "ErrorLoading".  Will you please hover over that error bing on the bottom right of the screen and please let me know what the error is?  Then, please go to Tools>>Update VI Calls and then let me know if the error bing still remains after this.  

 

Thank you,

 

Marcus 

Marcus M.
PXI Product Support Engineer
National Instruments
Download All
0 Kudos
Message 10 of 30
(7,015 Views)