Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Error 88705 on PCI-6280

Solved!
Go to solution

After getting error 88705, PCI-6280 board was removed but MAX still sees the board and cannot be deleted in attempt to re-install in new slot.  Any ideas?

0 Kudos
Message 1 of 7
(1,993 Views)
Solution
Accepted by topic author TJRatman
08-27-2015 04:09 PM

TJ,

 

When you say that it can't be deleted, is the option simply grayed out? This is after the card has been removed from the system completely?

Could you also tell me what version of the DAQ drivers you are using as well as the operating system with this computer?

 

I found a knowledge base regarding the 88705 error that you may want to go through as well: http://ae.natinst.com/public.nsf/webPreview/89A6279147AA994A862572DF00491BCA

The issue could be with MAX or with a process not running, so let me know about the above and if the KB helps at all so we can look in to this further if need be. Thanks.

 

Timothy

Timothy S.
PXI & VXI Platform Product Support Engineer
0 Kudos
Message 2 of 7
(1,969 Views)

Yes, the delete option was grayed out even with the board removed.  I have been in contact with a Labview Technician about this problem (case 1652819).  I originally posted this question because I didn't think our group here had technician support.  Thanks.

0 Kudos
Message 3 of 7
(1,962 Views)

I've followed up with the Engineer that you are working with through the phone support channel. Please continue with that path until we can get the issue resolved. Once we have gotten to that point, we'll get the solution information posted here as well.

Timothy S.
PXI & VXI Platform Product Support Engineer
0 Kudos
Message 4 of 7
(1,942 Views)
I am facing a similar issue now. Has this issue been resolved? What was the solution?
0 Kudos
Message 5 of 7
(1,833 Views)

Thanks Tim, but problem already fixed.  Don't remember now what it was.

0 Kudos
Message 6 of 7
(1,825 Views)

Joes51385,

 

From what I can tell going through the notes from this particular issue internally, it appears to have been resolved through clearing the MAX database. The issue looked to be caused by a corruption of the MAX database causing the card to continue to identify when it wasn't in the system. In that regard, I'd recommend looking through the What is the Process For Removing MAX Database Corruption? document and then letting us know if you have further troubles.

Timothy S.
PXI & VXI Platform Product Support Engineer
0 Kudos
Message 7 of 7
(1,816 Views)