nilesru.dll

[Adrianwong]

Hi,

I am using ni-6515 digital I/O in my project. I faced some problems when i run my application overnight. An error message "The application or DLL c:\windows\system32\nilesru.dll is not a valid windows image. Please check this against your installation diskette." will prompt up. Is the error caused by my operation system of NI software.

Is it normal the availibility of the physical memory keep decreasing while the VI is running.

The pc is running windows XP and labview 8.5 with AUG07 drivers installed. Thanks for helping.

[Paul_C.]

Hi Adrian,

I'm not sure why you are getting that error message but it might be due to an improper install or corruption of installed components.  The nilesru.dll is a National Instruments DLL and the error may be due to you running out of physical memory in your application which is causing the dll to crash.  We need to determine if your application has a memory leak.  Memory leaks typically occur due to loops that are allocating resources every iteration and never deallocating them.  I would take a look at the article here.  This article explains a common reason for getting memory leaks in a DAQmx application.  I would also recommend taking a look at our example code.  This can be found by going to Help » Find Examples » Hardware Input and Output » DAQmx and searching for a similar application type.  You might try running a continuous example overnight and see if you are getting the same DLL error prompt.  This will help us determine if the problem is being caused by your application or your installation of LabVIEW.  If you are getting a similar error with a example program, it might be best to try and uninstall and reinstall of LabVIEW.  Please let me know the results.

I hope this helps,
Paul C.

[Adrianwong]

Hi Paul,

I am now testing the software with several computers. Will let u know once i have the result. Thanks for ur big helps.

Regards,

Adrian

[Adrianwong]

Hi Paul,

I still facing the same problem with other pc but there is not error displayed. Just the windows hang and slow response. Please find my code attached. Please advice. Thanks

Regards

Adrian

[samantham]

Hello,

The I/O Testing code is continuously looping.  The code that is being looped consisting mainly of two simple sub VIs (Input.vi and Output.vi) called repeatedly for each line of several ports.  I have one side question … if you are using a NI 6515, which only has 32 lines, where are you getting eight different ports?  Or are you reading from four ports and then writing to the same ports?  Please confirm if this is the case or if you have more than one NI 6515.  The sub VIs you are calling start by initializing the digital task then reading or writing to the line and last clearing the task. 

The fact that you are looping code that is creating and ending several tasks is what is slowing you down and taking up resources.  Please look to some of National Instruments shipping examples in the Example Finder.  The examples that coincide with your sub Vis are “Read Dig Chan.vi” and “Write Dig Chan.vi”.  Please note how they first create, start, looping only the read or write, and then close the task.  This structure only creates one task while the VI is running.  This structure could be multiplied to accommodate the number of lines/channels you are working with, where each line only has one task created for the entire time the VI runs overnight.  I hope this information is helpful. 

[Adrianwong]

Hello Samantham,

Thanks for ur reply. I am using only one NI 6515. It has 32 input and 32 out. Yes, i did refer to the example code. "Read Dig Chan.vi" and "Write Dig Chan.vi". . Does the "clear tast" release the resources?? I knew creating and ending task will slow down the process. I did it that way cause the IO testing is just a simple and straight foward vi i use to test the operation of handler. The real operation just call input.vi and output.vi for several times. I will try to modified the code according to the example code and let u know the result. Thanks.

[samantham]

Hello,

Yes, the DAQmx Clear Task VI does release the resources; however this method of execution will still slow you down bases on the high number of task calls in one loop and the fact that you are running the program for a prolonged period of time. 

 

[Adrianwong]

Hello Samanthan,

I had modified the code and only open and close once at the begining and ending of the program. It been running for 2 days and no error yet. Thanks for your helps.

Regards,

Adrian