Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI-4351 error on initialization

Hello,
 
I have a question concerning the PXI-4351 card.  I have written a little program in LV 8.0.1 using the latest version 2.51 instrument drivers for the 4351 card.  The first step in the program is calling the Initialize function with the Reset flag set True.  The first time this is run, it works correctly.  However, when the program stops and I run it again, I get an error saying that a dll memory allocation or something occurred at the initialization function and I need to exit LabVIEW.  I don't recall the exact error message.  This error occurs continuously until the PC is shutdown and the PXI chassis is power cycled.
 
If I set the Reset flag to False for the Initialization VI, this error does not occur and I can run the program over and over again.
 
I guess I was just curious if anyone else has seen this.  I'm fine with not resetting the device, but it seemed like it should work.
 
Thanks for any input,
Jon
0 Kudos
Message 1 of 3
(3,093 Views)
Jon,

I was wondering if you were closing the DAQ session towards the end of your program. Closing the session is always a good idea to do because it makes sure all the resources are released when you are done using them.

Are you able to duplicate this error in a different program? You might try and run a 435x example that ships with LabVIEW to see if you still see the same error occur after the code is run once. If you still having issues with the error in other programs please let me know the exact error you are seeing.

Have a great day,
Brian Platt
0 Kudos
Message 2 of 3
(3,080 Views)
Hi Brian,
 
Thanks for the response.  I was closing the DAQ session at the end of the program.  Basically, the whole thing was initialize/reset the device, take some samples, close the device.  The first time through it worked, but the next time running it, the error occurred.  This also occurred if I tried running an example.  The error wasn't an error code per se, it was the generic error that pops up if you try to link to a dll incorrectly or a run bad dll.  Something about a memory exception and labview's memory space may be corrupt.
 
I have to get some other projects running, but if I get a chance, I will duplicate and copy the error and the exact sequence to get it to occur.
 
Thanks,
Jon
0 Kudos
Message 3 of 3
(3,054 Views)