I use the NI linux device driver for GPIB. But though writing (ibwrt) and reading (ibrd) seem to work alright, I keep getting 'EABO' error. Does anyone know how I can prevent this?

[linuxdriver]

I've run out of ideas!

[Ketan Vyas]

EAB0 error is a time out error. Try changing ibtmo to various settings and see whether that solves the problem. How about setting up EOI and EOS attributes?

[linuxdriver]

Unfortunately none of that prevents the error from occurring. Strangely enough, the read and write operations seem to be working correctly. Also the driver does not really wait for the timeout to occur but just exits. However, it does keep saying EABO...

[Ketan Vyas]

What exactly does the error say? Try upgrading your driver to the latest one ( if you don't have the latest driver ) from our ftp site ftp.ni.com and see whether that solves the problem. Can you explain in little detail what is happening?

[linuxdriver]

Okay. The following is an example of what happens within ibic :


488.2 (0): ibsic
[0130] ( cmpl cic atn )

488.2 (0): ibdma 0
[0130] ( cmpl cic atn )
previous value: 1

488.2 (0): send 1 "*IDN?\n" NULLend
[c128] ( err timo cmpl cic tacs )
error: EABO
count: 6

488.2 (0): receive 1 50 STOPend
[c124] ( err timo cmpl cic lacs )
error: EABO
count: 42
48 65 77 6c 65 74 74 2d H e w l e t t -
50 61 63 6b 61 72 64 2c P a c k a r d ,
20 38 36 34 38 43 2c 20 8 6 4 8 C ,
33 38 34 37 4d 30 30 32 3 8 4 7 M 0 0 2
33 30 2c 20 42 2e 30 34 3 0 , B . 0 4
2e 30

Although "*IDN?" does return information that is read by using "receive"
the error "EABO" keeps occurring. When I send commands to set the frequency of the signal generator, for instance, the frequency does get set to the desired value but it still says "EABO". However the driver does not really wait for the Timeout period to expire but does the job and exits. The "\n" is all that is required by the signal generator for termination...

[linuxdriver]

I went to the NI ftp site and found 2 versions of the driver that seemed more recent than the .6 version I am using. Those were versions .8 and .8.1. I have tried using both versions but have got nowhere I am afraid. Exactly the same error occurs. I am not able to program (using C) because of these errors... I am attaching a file showing info. about configuration of board and device. Please let me know if I am doing something wrong...

[linuxdriver]

I just wanted to let you know that there is a slight difference in the way the new driver works. The device I am attempting to remotely control uses a new line character to terminate strings written by it. The latest version of the driver seems to more accurately recieve data from the device, in reponse to "Receive" command in ibic, I see data terminated with a 0a character.

Also, I have enabled dma. But EABO continues to occur!

[linuxdriver]

I'm happy to tell you that the problem has been solved. I moved the IRQ jumper to a different setting and now I don't get the EABO error anymore. Thanks for your help.

[lasershack]

Hi, Could you please tell me how you set the IRQ jumper to solve problem. I am facing same problem. Thanks a lot.