MIO-16E-4 does not run in a PCI express to PCI expansion box

[yanping]

My MIO-16E-4 board does not run in the PCI express to PCI expansion box. I am using a NI-DAQmx8.6.0 driver.  My colleague is using a same PCI expansion box and his MIO-16E-4 board can run without any problem. We are using the same type of computer. The only difference is that he is using a NI-DAQ traditional driver. Is the NI-DAQmx driver causing the problem?

[Christian Mergl]

Hey,

The DAQmx driver supports your MIO Card. How do you determine that your card does not work?

Christian

[yanping]

The DAQmx driver supports our MIO Card. If I put this card inside the main computer, it can run without problem. Since our computer only has two PCI slots and we are using them for other cards, we have to put the MIO-16E-4 card outside the computer via a PCI expansion box. Once it sits in the expansion box, data acquision can not finish properly any more. The error message is either data underflow or overflow on the bus.    

[Christian Mergl]

So, the card works, but you get errors with your application.

I don't know why exaclty this expansions chassis configuration is resulting in this errors, however if you tell me the error numbers I'm pretty sure we find some hints to get rid of them.

Christian 

[yanping]

Hi Christian, Thanks for your reply.

Here are some errors that I had:

1. NIMEX_startTask failed...
??? Error using ==> NIMEX_startTask
The specified resource is reserved. The operation could not be completed as specified.
Task Name: _unnamedTask<0>

Status Code: -50103

2. Error using ==> NIMEX_readAnalogF64
      NIMEX_readAnalogF64: Invalid NIDAQmx TaskHandle: NULL.

3. NIMEX_Callbacks/processDoneCallbackInMatlabThread - NIDAQmx status indicates warning: The specified operation cannot be performed because a task has been aborted or a device has been removed from the system. Handle this situation as required by the application and then, if appropriate, attempt to perform the operation again.
Task Name: _unnamedTask<55>

Status Code: -88709

4.  NIMEX_Callbacks/processDoneCallbackInMatlabThread - NIDAQmx status indicates warning: A transfer was aborted because of a hardware error on the bus on which the transfer was occurring.
Task Name: _unnamedTask<9E>

Status Code: -50413
5.NIMEX_Callbacks/processDoneCallbackInMatlabThread - NIDAQmx status indicates warning: A hardware buffer has overflowed.
Task Name: _unnamedTask<A5>

Status Code: -50409

6. NIMEX_Callbacks/processDoneCallbackInMatlabThread - NIDAQmx status indicates warning: A transfer was aborted because of a hardware error on the bus on which the transfer was occurring.
Task Name: _unnamedTask<79>

Status Code: -50413

[AnalogKid2DigitalMan]

Sounds like the expansion box is at fault, I doubt that DAQ vs DAQmx is the issue.

Can you put the MIO card inside the PC and move one of the other cards to the expansion box to see if there is any difference?

-AK2DM

[Christian Mergl]

Yes, I agree, seems that there is somethings wrong with the chassis.

I would also suggest to change the chassis under each other and the cards to get sure.

Christian 

[yanping]

Yes, that was exactly what I have done. I put the MIO card back to the computer chassis and it can run without any error. So the simple thought was something wrong with our PCI expansion box. Of course, I tried another a brand new computer and a brand new expansion box. The result was the same. I was very frustrated, because my colleage has almost the same type of computer with same type of expansion box and his MIO card runs well inside the box. The only difference is that he is using the traditional driver for his application. That's why I posted my message here. I don't know whether the new driver is more demanding than the traditional driver which causes the problem.

[yanping]

sorry, I should put it this way:

I don't know whether the new driver is more demanding than the traditional driver, which is not compatible with such external PCI slots.