Hi again!
I came across this very useful link:
HTML Code:
http://4hv.org/e107_files/public/1163365705_65_FT17832_linuxgpib.pdf
basically I have used the wrong driver. The (wrong) driver I have been using is shown in
Code:
[ 411.894111] gpib: registered lpvo_usb_gpib interface
[ 411.894116] lpvo_usb_gpib:usb_gpib_init_module - done
The lpvo_usb_gpib.ko driver is not the correct one. So i had to use ni_usb_gpib.ko (according to the above link). In order to do so I typed:
Code:
modprobe ni_usb_gpib
Then I had to change the board type in the gpib.conf file:
Code:
cd etc/
gedit gpib.conf
The board_type entry according to the same link i posted above, has to be changed to board_type = "ni_usb_b"
Code:
interface {
minor = 0 /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */
board_type = "ni_usb_b" /* type of interface board being used */
name = "violet" /* optional name, allows you to get a board descriptor using ibfind() */
pad = 0 /* primary address of interface */
sad = 0 /* secondary address of interface */
timeout = T3s /* timeout for commands */
eos = 0x0a /* EOS Byte, 0xa is newline and 0xd is carriage return */
set-reos = yes /* Terminate read if EOS */
set-bin = no /* Compare EOS 8-bit */
set-xeos = no /* Assert EOI whenever EOS byte is sent */
set-eot = yes /* Assert EOI with last byte on writes */
/* settings for boards that lack plug-n-play capability */
base = 0 /* Base io ADDRESS */
irq = 0 /* Interrupt request level */
dma = 0 /* DMA channel (zero disables) */
/* pci_bus and pci_slot can be used to distinguish two pci boards supported by the same driver */
/* pci_bus = 0 */
/* pci_slot = 7 */
master = yes /* interface board is system controller */
}
After these changes configuration
runs smoothly and when i send an *IDN? with
I get a nice reply from my instrument:
Code:
trying to read 100 bytes from device...
received string: 'THURLBY THANDAR, QL355TP, 429732, 2.05-2.00
'
Number of bytes read: 45
gpib status is:
ibsta = 0x2100 < END CMPL >
iberr= 0
ibcnt = 45
It seems to be working now but when I run my Labview program I get an error after GPIB WRITE:
Code:
Error 0 occurred at GPIB Write in Test.vi
Possible reason(s):
LabVIEW: Error connecting to GPIB driver or device.
This might be a different(?) story. However I will keep this thread [UNSOLVED] for a bit more and hopefully I will close it asap.
Thanks!
Bookmarks