LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 08-26-2009, 05:11 AM   #1
Weining
LQ Newbie
 
Registered: Aug 2009
Posts: 5

Rep: Reputation: 0
Question NI PCI-GPIB doesn't work with linux-gpib-3.2.11 under Suse 10


Hi,

I'm working with
- Linux 2.6.16.60-0.39.3
- Suse 10
- NI PCI-GPIB card
- NI GPIB-USB-HS interface
- driver linux-gpib-3.2.11
- a GPIB device(YOKOGAWA 7651, a programmable DC source) with address 6
, and the output of lspci is:
[CODE]00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
Code:
1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
00:13.0 Communication controller: National Instruments PCI-GPIB (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV36GL [Quadro FX 1100] (rev a1)
Now I can use ibtest to write something to the GPIB device with NI GPIB-USB-HS, but not with the NI PCI-GPIB.

What I have done are:
1. configure the /etc/gpib.conf for NI PCI-GPIB board as:
Code:
interface {
	minor = 0	/* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */
	board_type = "ni_pci"	/* type of interface board being used: "ni_pci" for NI PCI-GPIB, "ni_usb_b" for NI GPIB-USB-HS  */
	name = "gpib0"	/* 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 */
}
2.Load the driver module by
Code:
pcvk25:/home/wnhao # modprobe tnt4882
3.Set up the driver by
Code:
pcvk25:/home/wnhao # /usr/local/sbin/gpib_config --minor 0
4. Execute the ibtest, then the following message shows up:
Code:
pcvk25:/home/wnhao # ibtest
Do you wish to open a (d)evice or an interface (b)oard?
        (you probably want to open a device): d
enter primary gpib address for device you wish to open [0-30]: 6
trying to open pad = 6 on /dev/gpib0 ...
You can:
        w(a)it for an event
        write (c)ommand bytes to bus (system controller only)
        send (d)evice clear (device only)
        change remote (e)nable line (system controller only)
        (g)o to standby (release ATN line, system controller only)
        send (i)nterface clear (system controller only)
        ta(k)e control (assert ATN line, system controller only)
        get bus (l)ine status (board only)
        go to local (m)ode
        change end (o)f transmission configuration
        (q)uit
        (r)ead string
        perform (s)erial poll (device only)
        change (t)imeout on io operations
        request ser(v)ice (board only)
        (w)rite data string
: w
enter a string to send to your device: F1SA1E
sending string: F1SA1E

gpib status is:
ibsta = 0xc100  < ERR TIMO CMPL >
iberr= 14
EBUS 14: Bus error

ibcnt = 0
(F1SA1E is a command for YOKOFAWA 7651 to set a voltage of 1V)
5.In order to load the module during the boot process, adding the following commands to the file /etc/init.d/boot.local
Code:
/sbin/modprobe tnt4882 #load the driver module for NI PCI-GPIB
#/sbin/modprobe ni_usb_gpib #load the driver module for NI GPIB-USB-HS
/bin/sleep 2
/usr/local/sbin/gpib_config --minor 0
/bin/chgrp gpib /dev/gpib*
, and restart the computer, then run ibtest again:
Code:
gpib status is:
ibsta = 0x8000  < ERR >
iberr= 1
ECIC 1: Board not controller in charge

ibcnt = 0
6. I follow the above steps 1-5 to configure NI GPIB-USB-HS and test it, it does set the right voltage on the YOKOGAWA 7651.

My questions are:
1. What does the "Board not controller in charge" mean?
2. why are there various errors in step 4 and 5? Do the statements
/sbin/modprobe tnt4882
/usr/local/sbin/gpib_config --minor 0
work differently in console and in the boot.local file?
3. Is there anything wrong during my configuration?

Any help would be appreciated!

Best regards,
Weining
 
Old 09-18-2009, 03:18 AM   #2
Weining
LQ Newbie
 
Registered: Aug 2009
Posts: 5

Original Poster
Rep: Reputation: 0
Red face

Hi,

this question may only answered by myself.

I have installed NI488.2 Version 2.5 but haven't uninstall it before using the driver linux-gpib-3.2.11. That's the reason!

So what I have done is to uninstall the NI488.2 v2.5, then install the linux-gpib-3.2.11 again, then the PCI-GPIB board works.

Sorry for disturbing who have tried to resolve it, and best regards,
Weining
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] NI AT-GPIB ISA card with linux-GPIB 3.2.11 driver: failed to allocate ioports bluefan Linux - Hardware 13 08-19-2009 10:06 AM
configuring linux-gpib for pcmcia-gpib card Calibus Linux - Hardware 0 03-21-2006 07:07 AM
need 64bit GPIB drivers. know where? LaserNut Linux - Software 1 10-31-2005 02:59 PM
Drivers for National Instruments GPIB Card not Working MadScience314 Linux - Hardware 4 10-31-2005 01:45 PM
GPIB interface on REDHAT7.3 rpinatel Linux - Hardware 2 09-02-2003 09:28 AM


All times are GMT -5. The time now is 07:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration