EABO error from IBRD with Analyst software-Applied Biosystems Qtrap

[wtjewell]

 Hello,

 I have an Applied Biosystems/AB Sciex Qtrap 2000 mass spectrometer which used an NI GBIP card for communication.  The MS is fine but when I try to acquire data, the Analyst software gives a "Failed to Acquire Data" error.

I rebooted everything multiple times, reseated the GPIB card, etc.   One clue I got was an error msg "The GPIB command <Packet.send GPIB> resulted in an EABO error."    It looks like this is a Timeout error.  I went into the AB

diagnostic software and increased the timeout from 300 msec to 1 and then 3 and even 10 secs but no dice.   I can also get the "EABO error-Operation aborted" in the AB Diagnostic software if I send an IBRD command.

 Any suggestions?   Should I reinstall the gpib.sys file? Or should I go snooping with NI Spy and other NI goodies?  I can get a little under the hood with the AB diagnostic software but the main Analyst software doesnt give me anything.

 Many thanks for any ideas,

-Will Jewell

[wtjewell]

 I should add that this system has been working flawlessly for ~6 years and, as a matter of fact, was used ~1 hour before this error cropped up.

So it makes me think it might be a software corruption type thing or something.......

[Thør]

Try to open up MAX, and open a VISA test panel to your resource.  Can you use this to successfully send commands to your device?  It seems like the device isn't responding to commands anymore, and this would be a good way to check.

[wtjewell]

 Thanks, I was able top open up Max and communicate with the device.  I was still getting the EABO error though.   As I was burrowing around, though, I noticed that the data drive (D:) was actually completely full

as one of the users had managed to acquire a 4GB(!) data file.  I freed up some room and all was well.   So it turns out that the problem wasnt with the PCIB card or bus but that's the error I was seeing.

I"m guessing that the instrument was trying to return it's data string, Windows was saying "no way, we're full!" and so I ended up getting the timeout error.  Sound right?

Thanks for your help.

[Thør · Accepted solution]

Yeah that'd definitely be a problem.  Glad you were able to figure it out!