NI-Tclk Error When Committing Session

[jrasco]

Hello,

I have three 6556s driving/capturing digital I/O in a PXIe-1065.  It is a straight forward application that has been working for several years.

Recently, I have been getting the error 250033 (NI-TClk Committed a Session and the instrument driver reported an error.)  There is a knowledge base page for such an error:

http://digital.ni.com/public.nsf/allkb/7AD9D646FEA83270862573C60071DCBC

This KB article targets PCI devices that have RSTI cables manually installed and configured in MAX.  With the for PXIe chassis, this configuration is not appicalbe, yet I still get the error.  It used to happen occasionally but lately it is happening all the time.  My systme is basically unusable right now because of this.

Any ideas?  Could this be a HW issue in the card itself?

Thanks!

[jmoody]

Do you receive the same error using just two of the 6556's?  If so, does it occur if you switch around which two you're using at a given time?  Basically does any combination of two eliminate the error in order to see if one of the cards is having problems?  Also are all of the TCLK sessions being closed properly?

[jrasco]

TestStand reports a session index of 2 along with the error message.  I did re-seat all of the modules but I haven't swapped them to see if the error follows the module or the slot number.  That's a good idea though.  I'll give it a try.

TClk itself doesn't have a session to close, at least as far as I can tell.  There is no TClk Close VI.  I do properly close the niHSDIO sessions.  I've even tried resetting the modules manually from MAX after the failure shows up in case the closing procedure is somehow interrupted or mishandled.  (It didn't work.)

Jacob