exception C0000005 in niNIESR100 tAllImmediateTapSupervisor

[kbowers1]

I am getting a Dr. Watson exception error in niNIESR100 at random during execution of my application.  It is always located within tAllImmediateTapSupervisor::~tAllImmediateTapSupervisor.  It occurs more frequently if I am running two instances of the application which occurs whenever I am testing two ECUs from the same PC.  In this case I am sharing the NiDAQ hardware between the two instances of the application code.

I am currently running version 7.1 of LabWindows, the previous version of code was developed with 7.0 and didn't exhibit this problem.  One other item that changed was that I am now incorprating the UIR file into the executable.

Ken

[Wendy L]

Hello kbowers1,

Were you able to isolate the problem to a particular function call or line in your program?  If so, that would be helpful in isolating the source of the problem.  Is the function a DAQ call, or a CVI call?  Are you using any other driver software other than NI-DAQ?  Is the problem caused by one of those function calls?  If you run your application in debug mode within the CVI environment, do you get the same error?  Also, if you do not embed the UIR file in the executable, is the problem still apparent?

Thanks.

[kbowers1]

Wendy,

I was hoping someone from NI would be able to tell me what this function call was.  The exception occurs after several days of running so it isn't easy to track down.  If I knew what niNIESR100 was (I am assuming it is an NI dll) and what the tAllImmediateTapSupervisor was, I might be able to narrow down where the error is occuring in my code.

Thanks,

Ken

[kbowers1]

Wendy,

I rechecked the message.  It is actually nNIESR100 and tAIImmediateTapSupervisor (nNIESR100::tAIImmediateTapSupervisor::~tAIImmediateTapSupervisor).

Ken

[Wendy L]

Hello Ken,

From my research, the tAIImmediateTapSupervisor function is related the NIDaqmx driver.   So I suspect the problem lies in one of your DAQmx function calls.  Which version of the NIDAQ driver are you using?

Thanks.

[kbowers1]

Both the PC running the application and my development PC have DAQmx version 7.3.  Neither system has traditional DAQ installed.

Ken

[Hal_L]

Hi Ken,

I noticed that you are currently using NI-DAQmx 7.3.  Our latest version of this driver is NI-DAQmx 7.5.  Could you upgrade to this driver and see if you still get that same error?  It is a free download from the National Instruments website.  

Also, which version of Windows are you using and do you still get the error if you embed the UIR file in your executable?

Regards,
Hal L

[kbowers1]

I'll try the upgrade and let you know what happens, this may take some time since the test runs for two months and at this point I'd rather not interrupt it.  Basically, the problem has appeared to have gone away now that only one instance of the application is running.  Both instances access the same DAQ hardware so it is likely some type of conflict.  The application is written to not allow access to the DAQ card if it is in use which is something that took a fair amount of time to implement when switching from traditional to DAQmx.  I did have it functioning with DAQmx and my application built in CVI 7.0 but the problem has re-appeared now that it has been rebuilt in 7.1.

On the uir issue, this is the first time I have embedded the uir into the application.  The working version from 7.0 had the uir separate.  I will try it with the separate uir as well to see if that changes anything.

Ken

[kbowers1]

The new version of NI-DAQ did not correct the problem.  Neither did separating the UIR file from the executable.  Has anybody been able to determine what the actually fault code indicates so I can try to track down the problem.  Any chance there will be a version of Easy IO for NI-DAQmx?  I never had an issue with that software running with multiple instances accessing the same hardware.

Ken 

[Otis]

Ken,

I was looking thru some of the issues that you've mentioned you ran into and it sounds like this problem is pretty specific to the application that you are making.  But then after trying to look into the issue some more I found that I'm not really sure what it is that you are trying to do in your application. 

For example, you mentioned that you are getting a particular error, but I don't know exactly why that is occurring.  Which command is giving you the problems? 

What is it that you are actually trying to do with your application?  When you are executing your code and getting the error, does it only occur when executed as an EXE?  Or are there also similar issues when using the development mode?

Finally you said that you are trying to have multiple programs accessing the same device at the same time.  Why is this occurring?  Can you place any checks to make sure that you don't run the two applications at the same time?

I'm just trying to gain a better broader perspective so that we can maybe find a way to workaround what you are encountering. 

Thanks,