W2K crashes with PCI-GPIB

I am using a PCI-GPIB card under W2K, with driver version 1.60. All diagnostics
indicate that the card is functioning correctly, and there are no hardware
conflicts. I am able to use WaveStar to communicate with the Tektronix 694C
scope. When using Excel/VBA macros to control an oscope, W2K crashes to
a blue screen, with the message:
Hardware Failure
Please Contact Hardware Vendor
A hard reset is required to re-start the system. There is no error logged
by W2K, and using NI Spy reveals no consistent macro command that is causing
the failure. I have followed all the suggestions in the Troubleshooter,
Knowledge Base, etc. I have tried a different PCI-GPIB card from an known-good
system. I have tried this card in a
different, identical system. Any other
suggestions would be greatly appreciated.
Thanks,
Cory Allen

I am using a Pentium III 733/Intel VC820 motherboard/256M RAM/Matrox Millenium
G400 that was built by our IT dept. In addition to the GPIB card, there
is an Intel PRO/100+ network card, an In-Target Probe (ITP) card, and a SoundBlaster
Live (which has since been removed, reducing the frequency of the crashes,
but not eliminating them.). I have tried a variety of PCI slot configurations.
Thanks,
Cory
"Eric Singer" wrote:
>What type of computer are you running? Please indicate the make and model.>>Thanks,>Eric
Singer>"Cory Allen" wrote in message>news:[email protected]..>>>>
I am using a PCI-GPIB card under W2K, with driver version 1.60. All>diagnostics>>
indicate that the card is functioning correctl
y, and there are no hardware>>
conflicts. I am able to use WaveStar to communicate with the Tektronix>694C>>
scope. When using Excel/VBA macros to control an oscope, W2K crashes to>>
a blue screen, with the message>>> Hardware Failure>>>> Please
Contact Hardware Vendor>>>> A hard reset is required to re-start the system.
There is no error logged>> by W2K, and using NI Spy reveals no consistent
macro command that is>causing>> the failure. I have followed all the suggestions
in the Troubleshooter,>> Knowledge Base, etc. I have tried a different PCI-GPIB
card from an>known-good>> system. I have tried this card in a different,
identical system. Any>other>> suggestions would be greatly appreciated.>>>>
Thanks,>> Cory Allen>>>>

Similar Messages

I have problems with pci-gpib card under windows me, What I need to know what to do in order to fix this problems?

Hi, I have installed a pci-gpib card in my computer, I have a problem with
installation, the message of troubleshooting wizard is as follow:
"One or more missing GPIB interfaces.
There are several reasons why you might encounter this problem:
Reason: Your GPIB interface is incorrectly installed.
Solution: Please verify that your GPIB interface is correctly installed
and rerun the NI-488.2 Troubleshooting Wizard.
Reason: You are using a non-Plug-and-Play interface (e.g., AT-GPIB/TNT,
GPIB-PCII/IIA, GPIB-ENET) and you did not use the Add New Hardware Wizard
to add the interface to your system properly.
Solution: Click th
e Add Hardware button and the Add GPIB Hardware wizard
will guide you through the process of adding GPIB hardware.
Reason: For the GPIB-USB and GPIB-1394, the host controller (USB or 1394)
must be working properly in order to use the GPIB interface.
Solution: Click on the System Details button for details about the USB and
1394 host controllers.
Reason: For the PCMCIA-GPIB and PCMCIA-GPIB+, the PCMCIA host controller
must be working properly in order to use the GPIB interface.
Solution: Use the Windows Device Manager to verify that your PCMCIA host
controller is functioning correctly. Start the control panel by selecting
"Start>>Settings>>Control Panel", open the System icon and select the
Device Manager page. If you select "View devices by type", you can look at
the PCMCIA socket properties to ensure it is correctly enabled."
And on system details the message is the next:
"USB Driver type: USB universal host controller"
"This version of windows does not su
pport IEEE 1394."
I am using Windows Me, so i want to know what i need to do to fix this
problems.
Best regards.

If you have a PCI-GPIB card, you needn't worry about the USB port or whether or not Windows ME supports 1394. All you need in NI-488.2 version 1.70 from National Instruments. Install this driver and then insert your card. Windows should detect the card and find the proper driver.
If this did not happen in the proper sequence, look in the device manager and see if the card was installed as an "other device". If this happens, remove the card in the device manager and have windows redetect it. If this is not a solution, you may consider the ask an engineer page at www.ni.com/ask. Provide as many details as possible.

HP 3478A DMM not seen with PCI/GPIB 488.2

Hi All,
I'm really new at this so watch out... I have an old 3478A which is compliant with the old HP-IB (GPIB) connector and I'm trying to communicate with it using a PCI/GPIB 488.2 card. I found some drivers for Labview and that's wonderful but it simply doesn't work. The automation explorer also doesn't see the device. What am I doing wrong? I read somewhere that you have to enable some old drivers but I the message was somewhat unclear now I'm just desperate. Please help someone.
OS : win XP
Labview: 7.1
thanks

It is possible the cable is faulty. The cables I am using are National Instruments 763061-02 RevC; Type-X2. These cables work on all of the instruments I am using. Check the configuration of your GPIB Card, I have provided screen captures of my current settings that are working for me.
1. As before use the Measurement and Automation Explorer to get to the GPIB Bus under devices.
2.Right click on the GPIB Bus and select properties, you should see the following screen.
3. Click the Configure and on the next screen click Software>> button to see all of the options.
Try these settings(I have not made any changes these should be Default).
Message Edited by AndrewAlford on 11-25-2005 02:23 PM
Andrew Alford
Production Test Engineering Technologist
Sustainable Energy Technologies
www.sustainableenergy.com
Attachments:
ConfigGPIB.JPG ‏39 KB
GPIBconfig.JPG ‏14 KB

Problems with pci--gpib-300k from computerboards

hallo,
i have problems with my gpib-card, win95 and 2000 identify this card
corectly but labview not, the max 2.0 find not cards.......have everyone the
self card and can help????
(sorry for my bad english..)
bye & thanks...
Thomas

Thomas,
The short answer is the MAX will not recognize non-NI devices. NI-MAX was designed to recognize and interface with National Instruments' boards such as our PCI-GPIB, AT-GPIB/TNT, etc. With the introduction of MAX2.0 and NI-VISA2.5, there was an added capability to recognize some Hewlett-Packard boards but even then, configuration of them must be done from an HP interface.
LabVIEW will interface with the board fine but MAX is designed specifically to interface with our drivers for our boards.
Ryan Mosley
National Instruments, Applications Engineer
http://www.ni.com/exchange

GPIB Enet/100 with PCI-GPIB

Is the a timeframe with the release of a GPIB Driver
capable of supporting both the Enet device and an installed GPIB-PCI card within the same computer?

The next version of the 488.2 driver will support the ENET and PCI GPIB cards together for Win 2000/NT/XP. We canot give a release date at this time but it will be on the web when we do.

Computer won't boot with PCI-GPIB card installed

I'm running a windows XP system with Labview 7.1 installed. I have installed the GPIB drivers, but when I insert my PCI-GPIB card, the computer will not boot(it freezes before the POST). I'm running a Shuttle "MK40VN" KM400 Chipset Motherboard.

Well, nevermind, I just verified that the card is in fact fried.

[SOLVED] kernel crash with PCI wifi card

HI,
I id install and start to use arch just two weeks ago :-)
I was able to solve problems until now.
I am not sure if this is problem of arch kernel, maybe it will be general.
I did insert PCI wifi card to my PC with arch. Card is Z-COM XI-626 : LAST LINE:
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
00:1c.7 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
03:00.0 IDE interface: VIA Technologies, Inc. VT6415 PATA IDE Host Controller
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
06:00.0 PCI bridge: ASMedia Technology Inc. ASM108x PCIe to PCI Bridge Controller (rev 01)
07:00.0 Network controller: Intersil Corporation ISL3874 [Prism 2.5]/ISL3872 [Prism 3] (rev 01)
It start to work very nicely, I could connect to the network with NetworkManager in gnome.
BUT
after while connection is not working.
the is in message LOG:
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 6 07:53:10 localhost NetworkManager[686]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Policy set 'Auto moje_wifi' (wlan0) as default for IPv4 routing and DNS.
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Activation (wlan0) successful, device activated.
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 6 07:53:10 localhost dbus[661]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 6 07:53:10 localhost dbus[661]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 6 08:02:58 localhost kernel: [ 1889.872241] Pid: 0, comm: swapper Tainted: G C 3.1.4-1-ARCH #1
Dec 6 08:02:58 localhost kernel: [ 1889.872243] Call Trace:
Dec 6 08:02:58 localhost kernel: [ 1889.872244] <IRQ> [<ffffffff810c6cfd>] __report_bad_irq+0x3d/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872252] [<ffffffff810c713d>] note_interrupt+0x14d/0x210
Dec 6 08:02:58 localhost kernel: [ 1889.872255] [<ffffffff810c5079>] handle_irq_event_percpu+0xc9/0x2a0
Dec 6 08:02:58 localhost kernel: [ 1889.872257] [<ffffffff810c5298>] handle_irq_event+0x48/0x70
Dec 6 08:02:58 localhost kernel: [ 1889.872259] [<ffffffff810c7a7a>] handle_fasteoi_irq+0x5a/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872262] [<ffffffff81016992>] handle_irq+0x22/0x40
Dec 6 08:02:58 localhost kernel: [ 1889.872265] [<ffffffff8140d01a>] do_IRQ+0x5a/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872268] [<ffffffff81409c6e>] common_interrupt+0x6e/0x6e
Dec 6 08:02:58 localhost kernel: [ 1889.872269] <EOI> [<ffffffff8131d3aa>] ? poll_idle+0x3a/0x80
Dec 6 08:02:58 localhost kernel: [ 1889.872273] [<ffffffff8131d383>] ? poll_idle+0x13/0x80
Dec 6 08:02:58 localhost kernel: [ 1889.872275] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 08:02:58 localhost kernel: [ 1889.872277] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 08:02:58 localhost kernel: [ 1889.872280] [<ffffffff813e6912>] rest_init+0x96/0xa4
Dec 6 08:02:58 localhost kernel: [ 1889.872282] [<ffffffff8194fc15>] start_kernel+0x3bf/0x3cc
Dec 6 08:02:58 localhost kernel: [ 1889.872285] [<ffffffff8194f347>] x86_64_start_reservations+0x132/0x136
Dec 6 08:02:58 localhost kernel: [ 1889.872287] [<ffffffff8194f140>] ? early_idt_handlers+0x140/0x140
Dec 6 08:02:58 localhost kernel: [ 1889.872289] [<ffffffff8194f44d>] x86_64_start_kernel+0x102/0x111
Dec 6 08:03:05 localhost NetworkManager[686]: <info> (wlan0): roamed from BSSID 00:19:0A:01:1A:66 (moje_wifi) to (none) ((none))
Dec 6 08:03:05 localhost kernel: [ 1896.943757] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:07 localhost kernel: [ 1898.942477] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:10 localhost kernel: [ 1902.180399] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:12 localhost kernel: [ 1904.179118] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:14 localhost kernel: [ 1906.177838] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:16 localhost kernel: [ 1908.176557] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:18 localhost kernel: [ 1910.175277] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:20 localhost kernel: [ 1912.173997] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:22 localhost kernel: [ 1914.172716] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:24 localhost kernel: [ 1916.171436] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:26 localhost kernel: [ 1918.170157] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:28 localhost kernel: [ 1920.168875] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:30 localhost kernel: [ 1922.167595] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:32 localhost kernel: [ 1924.166315] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:32 localhost kernel: [ 1924.279547] ------------[ cut here ]------------
Dec 6 08:03:32 localhost kernel: [ 1924.279553] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Dec 6 08:03:32 localhost kernel: [ 1924.279555] Hardware name: System Product Name
Dec 6 08:03:32 localhost kernel: [ 1924.279556] NETDEV WATCHDOG: wifi0 (hostap_pci): transmit queue 0 timed out
Dec 6 08:03:32 localhost kernel: [ 1924.279558] Modules linked in: fuse ext2 mbcache snd_hda_codec_hdmi orinoco_pci orinoco cfg80211 snd_hda_codec_realtek i915 drm_kms_helper drm i2c_i801 hostap_pci hostap i2c_algo_bit i2c_core eeepc_wmi asus_wmi sparse_keymap rfkill psmouse pci_hotplug serio_raw snd_hda_intel mei(C) snd_hda_codec iTCO_wdt iTCO_vendor_support snd_hwdep snd_pcm snd_timer snd evdev r8169 mii pcspkr intel_agp intel_gtt button video lib80211 wmi processor soundcore snd_page_alloc btrfs zlib_deflate crc32c libcrc32c hid_a4tech usbhid hid sd_mod ahci pata_acpi libahci pata_via libata xhci_hcd ehci_hcd scsi_mod usbcore
Dec 6 08:03:32 localhost kernel: [ 1924.279599] Pid: 0, comm: swapper Tainted: G C 3.1.4-1-ARCH #1
Dec 6 08:03:32 localhost kernel: [ 1924.279600] Call Trace:
Dec 6 08:03:32 localhost kernel: [ 1924.279602] <IRQ> [<ffffffff81061b9f>] warn_slowpath_common+0x7f/0xc0
Dec 6 08:03:32 localhost kernel: [ 1924.279610] [<ffffffff81025047>] ? intel_pmu_enable_all+0xa7/0x110
Dec 6 08:03:32 localhost kernel: [ 1924.279612] [<ffffffff81061c96>] warn_slowpath_fmt+0x46/0x50
Dec 6 08:03:32 localhost kernel: [ 1924.279615] [<ffffffff8107e472>] ? __queue_work+0xe2/0x490
Dec 6 08:03:32 localhost kernel: [ 1924.279617] [<ffffffff81364377>] dev_watchdog+0x257/0x260
Dec 6 08:03:32 localhost kernel: [ 1924.279620] [<ffffffff81071e61>] run_timer_softirq+0x131/0x440
Dec 6 08:03:32 localhost kernel: [ 1924.279622] [<ffffffff81364120>] ? qdisc_reset+0x50/0x50
Dec 6 08:03:32 localhost kernel: [ 1924.279624] [<ffffffff8101c139>] ? read_tsc+0x9/0x20
Dec 6 08:03:32 localhost kernel: [ 1924.279626] [<ffffffff810691c0>] __do_softirq+0xb0/0x270
Dec 6 08:03:32 localhost kernel: [ 1924.279629] [<ffffffff81096158>] ? tick_dev_program_event+0x48/0x110
Dec 6 08:03:32 localhost kernel: [ 1924.279631] [<ffffffff8109623f>] ? tick_program_event+0x1f/0x30
Dec 6 08:03:32 localhost kernel: [ 1924.279634] [<ffffffff8140c76c>] call_softirq+0x1c/0x30
Dec 6 08:03:32 localhost kernel: [ 1924.279637] [<ffffffff81016a15>] do_softirq+0x65/0xa0
Dec 6 08:03:32 localhost kernel: [ 1924.279639] [<ffffffff810696ce>] irq_exit+0x9e/0xc0
Dec 6 08:03:32 localhost kernel: [ 1924.279641] [<ffffffff8140d10e>] smp_apic_timer_interrupt+0x6e/0x99
Dec 6 08:03:32 localhost kernel: [ 1924.279643] [<ffffffff8140afde>] apic_timer_interrupt+0x6e/0x80
Dec 6 08:03:32 localhost kernel: [ 1924.279644] <EOI> [<ffffffff81279e9b>] ? intel_idle+0xcb/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279649] [<ffffffff81279e7d>] ? intel_idle+0xad/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279651] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 08:03:32 localhost kernel: [ 1924.279654] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279657] [<ffffffff813e6912>] rest_init+0x96/0xa4
Dec 6 08:03:32 localhost kernel: [ 1924.279659] [<ffffffff8194fc15>] start_kernel+0x3bf/0x3cc
Dec 6 08:03:32 localhost kernel: [ 1924.279662] [<ffffffff8194f347>] x86_64_start_reservations+0x132/0x136
Dec 6 08:03:32 localhost kernel: [ 1924.279664] [<ffffffff8194f140>] ? early_idt_handlers+0x140/0x140
Dec 6 08:03:32 localhost kernel: [ 1924.279666] [<ffffffff8194f44d>] x86_64_start_kernel+0x102/0x111
Dec 6 08:03:32 localhost kernel: [ 1924.279668] ---[ end trace 6f3b132eb24e1d2e ]---
Dec 6 08:03:32 localhost kernel: [ 1924.279669] wifi0 Tx timed out! Resetting card
Dec 6 08:03:32 localhost kernel: [ 1924.279694] hostap_pci: wifi0: resetting card
Dec 6 08:03:34 localhost kernel: [ 1926.278267] wifi0 Tx timed out! Resetting card
Dec 6 08:03:36 localhost kernel: [ 1928.163754] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:36 localhost kernel: [ 1928.276987] wifi0 Tx timed out! Resetting card
Dec 6 08:03:38 localhost kernel: [ 1930.162473] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:38 localhost kernel: [ 1930.222552] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:38 localhost kernel: [ 1930.262615] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:38 localhost kernel: [ 1930.262619] wifi0: Port type setting to 1 failed
Dec 6 08:03:38 localhost kernel: [ 1930.275703] wifi0 Tx timed out! Resetting card
Dec 6 08:03:40 localhost kernel: [ 1932.261129] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:40 localhost kernel: [ 1932.261131] wifi0: MAC port 0 enabling failed
Dec 6 08:03:40 localhost kernel: [ 1932.261150] hostap_pci: wifi0: resetting card
Dec 6 08:03:43 localhost kernel: [ 1934.463052] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:43 localhost kernel: [ 1934.463064] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:45 localhost kernel: [ 1936.461771] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:45 localhost kernel: [ 1936.501864] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:45 localhost kernel: [ 1936.501866] wifi0: Port type setting to 1 failed
Dec 6 08:03:45 localhost kernel: [ 1936.521925] wifi0: MAC port 0 enabling failed
Dec 6 08:04:13 localhost kernel: [ 1964.923031] hostap_pci: wlan0: resetting card
Dec 6 08:04:15 localhost kernel: [ 1967.125469] wlan0: interrupt delivery does not seem to work
Dec 6 08:04:15 localhost kernel: [ 1967.125474] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:04:17 localhost kernel: [ 1969.124179] wifi0: interrupt delivery does not seem to work
Dec 6 08:04:17 localhost kernel: [ 1969.164257] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:04:17 localhost kernel: [ 1969.164259] wlan0: Port type setting to 1 failed
Dec 6 08:04:17 localhost kernel: [ 1969.184273] wlan0: MAC port 0 enabling failed
Dec 6 08:06:13 localhost kernel: [ 2084.846529] hostap_pci: wlan0: resetting card
Dec 6 08:06:15 localhost kernel: [ 2087.048638] wlan0: interrupt delivery does not seem to work
Dec 6 08:06:15 localhost kernel: [ 2087.048649] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:06:17 localhost kernel: [ 2089.047356] wifi0: interrupt delivery does not seem to work
Dec 6 08:06:17 localhost kernel: [ 2089.087406] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:06:17 localhost kernel: [ 2089.087407] wlan0: Port type setting to 1 failed
Dec 6 08:06:17 localhost kernel: [ 2089.107404] wlan0: MAC port 0 enabling failed
Dec 6 08:08:13 localhost kernel: [ 2204.769302] hostap_pci: wlan0: resetting card
Dec 6 08:08:15 localhost kernel: [ 2206.971827] wlan0: interrupt delivery does not seem to work
Dec 6 08:08:15 localhost kernel: [ 2206.971832] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:08:17 localhost kernel: [ 2208.970532] wifi0: interrupt delivery does not seem to work
Dec 6 08:08:17 localhost kernel: [ 2209.010630] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:08:17 localhost kernel: [ 2209.010634] wlan0: Port type setting to 1 failed
Dec 6 08:08:19 localhost kernel: [ 2211.009274] wlan0: interrupt delivery does not seem to work
Dec 6 08:08:19 localhost kernel: [ 2211.009275] wlan0: MAC port 0 enabling failed
Dec 6 08:10:13 localhost kernel: [ 2324.691574] hostap_pci: wlan0: resetting card
Dec 6 08:10:15 localhost kernel: [ 2326.891711] wlan0: interrupt delivery does not seem to work
Dec 6 08:10:15 localhost kernel: [ 2326.891716] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:10:17 localhost kernel: [ 2328.890393] wifi0: interrupt delivery does not seem to work
Dec 6 08:10:17 localhost kernel: [ 2328.930472] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:10:17 localhost kernel: [ 2328.930473] wlan0: Port type setting to 1 failed
Dec 6 08:10:17 localhost kernel: [ 2328.950482] wlan0: MAC port 0 enabling failed
Dec 6 08:12:13 localhost kernel: [ 2444.616669] hostap_pci: wlan0: resetting card
Dec 6 08:12:15 localhost kernel: [ 2446.818212] wlan0: interrupt delivery does not seem to work
Dec 6 08:12:15 localhost kernel: [ 2446.818218] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:12:17 localhost kernel: [ 2448.816887] wifi0: interrupt delivery does not seem to work
Dec 6 08:12:17 localhost kernel: [ 2448.856917] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:12:17 localhost kernel: [ 2448.856919] wlan0: Port type setting to 1 failed
Dec 6 08:12:17 localhost kernel: [ 2448.876938] wlan0: MAC port 0 enabling failed
Dec 6 08:14:13 localhost kernel: [ 2564.540113] hostap_pci: wlan0: resetting card
Dec 6 08:14:15 localhost kernel: [ 2566.741388] wlan0: interrupt delivery does not seem to work
Dec 6 08:14:15 localhost kernel: [ 2566.741394] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:14:17 localhost kernel: [ 2568.740062] wifi0: interrupt delivery does not seem to work
Dec 6 08:14:17 localhost kernel: [ 2568.780120] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:14:17 localhost kernel: [ 2568.780121] wlan0: Port type setting to 1 failed
Dec 6 08:14:17 localhost kernel: [ 2568.800135] wlan0: MAC port 0 enabling failed
Dec 6 08:16:13 localhost kernel: [ 2684.463514] hostap_pci: wlan0: resetting card
Dec 6 08:16:15 localhost kernel: [ 2686.664525] wlan0: interrupt delivery does not seem to work
Dec 6 08:16:15 localhost kernel: [ 2686.664530] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:16:17 localhost kernel: [ 2688.663241] wifi0: interrupt delivery does not seem to work
Dec 6 08:16:17 localhost kernel: [ 2688.703314] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:16:17 localhost kernel: [ 2688.703315] wlan0: Port type setting to 1 failed
Dec 6 08:16:17 localhost kernel: [ 2688.723340] wlan0: MAC port 0 enabling failed
Dec 6 08:18:13 localhost kernel: [ 2804.386357] hostap_pci: wlan0: resetting card
Dec 6 08:18:15 localhost kernel: [ 2806.587699] wlan0: interrupt delivery does not seem to work
Dec 6 08:18:15 localhost kernel: [ 2806.587704] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:18:17 localhost kernel: [ 2808.586422] wifi0: interrupt delivery does not seem to work
Dec 6 08:18:17 localhost kernel: [ 2808.626468] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:18:17 localhost kernel: [ 2808.626471] wlan0: Port type setting to 1 failed
Dec 6 08:18:19 localhost kernel: [ 2810.625118] wlan0: interrupt delivery does not seem to work
Dec 6 08:18:19 localhost kernel: [ 2810.625121] wlan0: MAC port 0 enabling failed
please, have anybody idea what is wrong?
thanks for help / tips ...
Last edited by jancici (2012-03-21 08:47:06)

okay, I did blacklist hostap_pci, I did find out that with orinoco_pci module it is more stable
BUT
sometimes it hang up with same error message
Dec 6 23:03:45 localhost kernel: [ 2465.908317] ------------[ cut here ]------------
Dec 6 23:03:45 localhost kernel: [ 2465.908324] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Dec 6 23:03:45 localhost kernel: [ 2465.908326] Hardware name: System Product Name
Dec 6 23:03:45 localhost kernel: [ 2465.908328] NETDEV WATCHDOG: eth1 (orinoco_pci): transmit queue 0 timed out
Dec 6 23:03:45 localhost kernel: [ 2465.908329] Modules linked in: fuse ext2 mbcache snd_hda_codec_hdmi snd_hda_codec_realtek orinoco_pci orinoco r8169 cfg80211 mii
i915 drm_kms_helper drm snd_hda_intel evdev snd_hda_codec mei(C) i2c_algo_bit rfkill intel_agp psmouse wmi i2c_i801 i2c_core intel_gtt snd_hwdep snd_pcm button proc
essor video snd_timer snd soundcore snd_page_alloc btrfs zlib_deflate crc32c libcrc32c hid_a4tech usbhid hid sd_mod ahci pata_acpi libahci xhci_hcd pata_via libata e
hci_hcd scsi_mod usbcore
Dec 6 23:03:45 localhost kernel: [ 2465.908365] Pid: 0, comm: kworker/0:1 Tainted: G C 3.1.4-1-ARCH #1
Dec 6 23:03:45 localhost kernel: [ 2465.908366] Call Trace:
Dec 6 23:03:45 localhost kernel: [ 2465.908368] <IRQ> [<ffffffff81061b9f>] warn_slowpath_common+0x7f/0xc0
Dec 6 23:03:45 localhost kernel: [ 2465.908375] [<ffffffff81025047>] ? intel_pmu_enable_all+0xa7/0x110
Dec 6 23:03:45 localhost kernel: [ 2465.908378] [<ffffffff81061c96>] warn_slowpath_fmt+0x46/0x50
Dec 6 23:03:45 localhost kernel: [ 2465.908381] [<ffffffff810f1743>] ? perf_ctx_unlock+0x23/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908383] [<ffffffff81364377>] dev_watchdog+0x257/0x260
Dec 6 23:03:45 localhost kernel: [ 2465.908386] [<ffffffff81071e61>] run_timer_softirq+0x131/0x440
Dec 6 23:03:45 localhost kernel: [ 2465.908388] [<ffffffff81364120>] ? qdisc_reset+0x50/0x50
Dec 6 23:03:45 localhost kernel: [ 2465.908390] [<ffffffff8101c139>] ? read_tsc+0x9/0x20
Dec 6 23:03:45 localhost kernel: [ 2465.908392] [<ffffffff810691c0>] __do_softirq+0xb0/0x270
Dec 6 23:03:45 localhost kernel: [ 2465.908395] [<ffffffff81096158>] ? tick_dev_program_event+0x48/0x110
Dec 6 23:03:45 localhost kernel: [ 2465.908397] [<ffffffff8109623f>] ? tick_program_event+0x1f/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908400] [<ffffffff8140c76c>] call_softirq+0x1c/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908403] [<ffffffff81016a15>] do_softirq+0x65/0xa0
Dec 6 23:03:45 localhost kernel: [ 2465.908404] [<ffffffff810696ce>] irq_exit+0x9e/0xc0
Dec 6 23:03:45 localhost kernel: [ 2465.908407] [<ffffffff8140d10e>] smp_apic_timer_interrupt+0x6e/0x99
Dec 6 23:03:45 localhost kernel: [ 2465.908409] [<ffffffff8140afde>] apic_timer_interrupt+0x6e/0x80
Dec 6 23:03:45 localhost kernel: [ 2465.908410] <EOI> [<ffffffff81279e9b>] ? intel_idle+0xcb/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908415] [<ffffffff81279e7d>] ? intel_idle+0xad/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908417] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 23:03:45 localhost kernel: [ 2465.908419] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908422] [<ffffffff813f8944>] start_secondary+0x202/0x209
Dec 6 23:03:45 localhost kernel: [ 2465.908424] ---[ end trace 58cac98ca8b4102b ]---
Dec 6 23:03:45 localhost kernel: [ 2465.908433] eth1: Tx timeout! ALLOCFID=0128, TXCOMPLFID=03eb, EVSTAT=808b
maybe I need some more modern card, something with atheros chipset ...

How do I configure my PCI-GPIB cards so that one is a controller and the other is a device being controlled by the first card

I have 2 PC's, both fitted with PCI-GPIB cards. One will be the system controller and the other will be a device on the GPIB bus. How do I configure both cards using LabWindows/CVI v7.0 to achieve this ? What commands are used to send and receive the data ?

Hi Pete,
For the controller board you don't really need to do anything. By default the GPIB interface is configured as controller.
The non-controller can be configured in MAX. Right-click on the interface, uncheck the ono-controller box and change the primary address. It is usually a good idea to set these parameters programatically. Use ibpad to set the primary address and ibrsc to release system control.
For the controller you can use a device descriptor (using ibdev) or a board descriptor (ibfind).
You can only open a reference to the non-controller board using ibfind (ibfind("gpib0"), for example). This will open a board reference. You cannot use a device reference because that implies that the board is capable of addressing the bus. On
ly the system controller can.
Here are some links I found on the web on this subject:
Passing GPIB Control -- System Controller vs. Controller In Charge
Tutorial: Programmatic File Transfers over the GPIB
Example: Using a C Program as a GPIB Non-Controller with LabVIEW as the GPIB Controller
Example: Serial Polling Between Two Computers (Controller and Non-controller)
Hope this helps.
DiegoF
National Instruments.

PCI-GPIB/Win2000 blue screen-resolved yet?

Hi,
I have been kind of out of the loop lately, so can anybody enlighten me
on the subject?
Has the blue-screening (BAD POOL CALLER) error with PCI-GPIB board under
win2000 resolved yet and everything is hunky-dory, or it's still there?
Sincerely
Yuri

Hello-
This error is caused by a faulty process that does not close GPIB sessions. With these orphan sessions, a call to open another GPIB session will cause Windows to assert this screen.
The solution to the problem is to call ibonl(ud,0) for each session that is open. This typically needs to occur just before terminating the process using GPIB.
If this solution is not working, please write back.
Randy Solomonson
Application Engineer
National Instruments

AT-GPIB & PCI-GPIB

Hi:
My Question is a compatible issue AT-GPIB and PCI-GPIB.
I'm going to replace the PC to New One.
Old PC : Windows 95 with AT-GPIB.
New PC : Windows NT4.0 workstatiion with PCI-GPIB.
GPIB Instrument : NEFF 470(www.neff.com)
Replacing PC, no compatible problem to communication the NEFF470?
And One more important Problem.
The PCI-GPIB Card is working well in Windows 2000.
But Windows NT4.0 Workstation, there is some problem.
please see attached capture file. I think the problem is driver Software...
I tried but fail with the driver(ni488216.exe) which downloaded at ni homepage.(NI Home->support->drivers&updates->All software Version->GPIB->All Versions(Left side)->GPIB->NI-4882(win32)Version 1.60 for WindowsNT.
Please Help Me.
Thank You.
Attachments:
gpiberror#1.jpg ‏48 KB
gpiberror#2.jpg ‏18 KB

Hello,
There will be no compatibility problem with the NEFF470 if the PC is replaced.
Is there a specific reason why you are installing NI-488.2 ver 1.6? Ver 1.7 is our latest software for NT. Are you installing the software before the hardware? When exactly do you get the message displayed in the Error #1 screenshot? Is it after you boot up for the first time after inserting the card? Don't worry about the interface not being verified, there are a number of reasons why that could be happening, none of which affect the functionality of the card.
Ray K
NI Applications Engineer

Problems with Tru64 UNIX 5.1b PCI-GPIB driver development

I am using your NI488.DDK product to develop a PCI-GPIB device driver for Tru64 UNIX 5.1b3. I have experience porting other device driver from 4.x to 5.1b and thought that this would not be too hard. The driver that I have developed loads and configures ok. It allows for the IBFIND of /dev/gpib0 minor #255 to work fine because a bus table is built for it during the probe/attach. When I try an IBFIND on /dev/gpib_dev/dev1 I get an error from ni_Cp2BusPtr for minor #51 because no table is created for the devx devices during driver initialization. I don't see where this was done in the example ib.c code provided for Tru64 Unix 4.x, am I missing something?

This is really an update to my original posting for those of you who may have similar concerns.
The source code provided as part of the NI488DDK kit is not really a fully functional driver with the same capabilities as they provided in the device driver that they devloped for Tru64 UNIX 3.x and 4.x. The the "ib" commands supported by the DDK driver is a subset of the entire ni488 suite. None of the device specific "ib" command are supported, neither is ibask. Device commands are written to the bus as character strings that contain device addresses and command.

ADC testing with pci 6534/GPIB

is it possible to test linearity of ADC with pci 6534 or with agilent GPIB
please provide some .vi examples to test adc
thanks

Well, an ADC is an analog-to-digital converter. The 6534 is just a digital board. So on that basis alone, the answer is no, you can't use it to test linearity of an ADC with that board. I have no idea what you mean by "with agilent GPIB". This is somewhat meaningless, as it doesn't refer to anything.
As for VI examples to test ADC, this is completely dependent on the hardware you have.
I would suggest contacting your local NI sales office, as they will be capable of helping you pick out the right hardware for what you have and need to do.

PCI-GPIB, 488.2 not working on my G5 OS10.4 with LabVIEW 7.1?

I've followed the intstructions posted this summer from ScottieB for installing NI-488.2 v2.3 on my Mac G5 with OS 10.4.2. (See for example message id=13246). It seems that the driver is now installed correctly, but the NI-488.2 Troubleshooting Wizard fails. The first of three tests passes, i.e., the NI-488.2 Software Presence Verified, but the next one fails. The hardware is not detected apparently. The hardware is a new PCI-GPIB.
ScottieB, or anyone else have any advice?
Thanks for your time.
Sean

Sean,
That's odd...I know you said it's a new card, but could you confirm that it works okay in another machine? PC or Mac? (10.3 might be better if you have one of those around so you don't have to go through all the Tiger steps, just load NI-488.2 v2.3 up and it should "just work"). There is the issue of potentially needing a firmware update, but the troubleshooting wizard should alert you to that fact if it is necessary (again, don't run the firmware update on Tiger, bad things happen).
Let me know.
Scott B.
GPIB Software
National Instruments

Connecting a HP3497A with a NI PCI GPIB card.

Hello, I would like to be able to connect the above mentioned HP product with a NI PCI GPIB card. As I have no prior experience with this equipment, I wanted to know what basic important steps I would have to take to achieve this?

Mbugua,
On the hardware end you'll need a GPIB cable to connect the card with your instrument. On the software side, you'll need the NI-488.2 driver. Please follow this link to download the proper driver version for your OS. I highly recommend that you use LabVIEW 7.0 to communicate with the instrument. If you prefer text-based programming LabWindows/CVI 7.0 would be a great choice. You can check out www.ni.com/idnet to download a library of functions to even further ease communication with t
he HP3497A (currently there is a download designed for CVI).
There are a great deal of manuals available online. Please navigate to www.ni.com and choose "support" to search through them as well as our Knowledge Base.
Please follow the following procedure of installation:
1) Install LabVIEW or LabWindows/CVI (or both)
2) Install NI-488.2 (hardware driver for the PCI-GPIB)
3) Insert the PCI-GPIB into your computer
Regards,
Alan
Applications Engineer
National Instruments

PCI-GPIB compatible with Genrad 1687-B Megahertz LC Digibridge?

I am trying to use a Genrad 1687-B Megahertz LC Digibridge with a recently purchased NI PCI-GPIB card.
The Digibridge works normally from the front panel. The GPIB card and the cable work normally with another GPIB instrument.
However, the "Measurement and Automation Explorer" does not detect the instrument. When I "Scan for Instruments", the pretty animation displays for a while and then the scan fails because it did not find any instruments.
Is there possibly an incompatability between this instrument and the newer GPIB specification? The instrument documentation mentions IEEE 488-1978 (not 488.1 or 488.2).

I doubt that your instrument is incompatible with the newer GPIB specification. Do you get any indication of an error on the instrument following a Scan for Instruments? Do you know what the instrument's GPIB address is? It must be a different address than the GPIB controller. The address of the GPIB controller is probably 0.

W2K crashes with PCI-GPIB

Similar Messages

Maybe you are looking for