RTSI cable configuration with PCIe 1433 card

Hi All:
I tried to trigger my line camera with RTSI signal.
The layout is: trigerr signal is generated from one PCI card 6259 (Dev2/ctr0). The line camera is connected with one PCIe 1433 card, and the two cards were connected with RTSI cable.
The problem is that how to register or configure PCIe 1433 with RTSI cable in MAX, it seems I can only configure PCI card within RTSI cable ......
If it is true, how should I do to rout the trigger signal to the camera, such as "route Dev2/ctr0 to Trigger line 0"?
Below is printscreen of MAX Configuration. Attached is my VI.
thanks a lot.
Bob
Attachments:
Triggered with RTSI from DAQ.vi ‏63 KB
camera configuration.jpg ‏218 KB

Thanks a lot, the post helped.
But I am still confused with the details:
To camera and PCIe 1433 configruaration, as the attached pictures shows: RTSI is configurerd as Camera Control Line as number "2"; the exposure control of camera is defined as "triggered".
In previous attached VI, you may find that the IMAQ configurer trigger is applied to define trigger type as "RTSI", trigger number as "2".
About ttrigger signal from PCI 6259 (Dev2), digital pulse is generated and output terminal is defined as ctr0 ( seems only ctr0 or ctr1 is option).
So I still do not know how to route signal from "Dev2/ctr0" to "Imag0 CCL 2" in labview.
By the way, I read the online example "LL Triggered Ring using DAQmx Pulse Train", http://www.ni.com/example/29476/en/. Within this VI, the DAQmx Connect Terminals VI is applied to route the counter's output to a RTSI pin so the signal can be used by the IMAQ device. However Dev2/ctro is not recognized as scour terminal, only other items such as PFI, APFI or RTSI are avaible, and output signal source is also limited with similar things, sounds like just internal connectrion with Dev2.
thanks a lot.

Similar Messages

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.

UCS C220 M3S with PCI mezzanine card raid SAS 2008M-8i :((

Hello
May be someone has already spend a little time with this configuration. the main stuff is my ucsc doesn't think he has disk to boot one even if with CIMC I see the opposite.
I configure with server conf utility ucs-cxx-scu-3.1.3b.iso with raid1 and as I have 2 UCS C220M3S I do also with Raid0 on another one. the trick is when I install ESXI 5.1 (VMware-VMvisor-Installer-5.1.0-799733.x86_64.iso) during install the setup od VMware detect the disk and install on it but after reboot always same storie no disk !!!
I don't see where to do something ??? So If someone encountered this problem, my be has already find the trick
The bios is C220M3.1.4b.0 and I have also a PCI Broadcom 5709 1Gbps 4 port NIC on slot 2 on both UCSC
here is the config 2xXeon CPU E5-2650 @2.00Ghz with 64 GB of Ram.
Any idea is welcome
Cheers
CX
and for the one configure with raid1

UCS C220 M3S with PCI mezzanine card raid SAS 2008M-8i
file attach UCSC220M3S right setup.pdf give illustrated answer
Point was VM distribution but bios which does not see SAS PCI Mezzanine Ctrl
Thanks to PDI help

How to measure frequency with PCI-4474 card

Hi,
I'm trying to measure frequency with PCI-4474 card.
Any sample code available?
Thanks.

Hi,
Thank you for posting the the NI forums. There aren’t any example programs that ship with the DSA drivers. Will you be using this with the Sound and Vibration Toolkit? If so, there are numerous examples that install with this software package. Check out the LabVIEW Example Finder >> Toolkits and Modules >> Sound and Vibration Toolkit.
In addition to this, you could also use the signal processing VIs that ship with LabVIEW. There are also examples that ship with LabVIEW that use these VI in Example Finder >> Analyzing and Processing Signals FFT and Frequency Analysis. There is an entire Signal Processing palette that should contain the functionality that you need.
I hope this helps. Post back if you have further questions.
Ed W.
Applications Engineer
National Instruments

[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 ...

Front audio with PCI sound card?

Well, the front audio on my Antec P160W worked perfectly with the integrated sound, but I changed to my SoundBlaster Audigy Player because of the HORRIBLE audio quality. Now the front audio ports don't work. What do I need to do to make it work again? I'm not going back to the integrated.
At first I thought that I had to put the connectors for the front audio on the sound card, but the manual of it doesn't show any of those features.

I was wondering that myself. The only thing I think you could possibly do is have both the onboard and the pci sound card enabled and use the onboard sound just for the headphones. I have no tried this yet as I do have the cables connected to the mobo but I have the onboard sound disabled.

Trouble NetBooting Xserve G5 with PCI RAID Card

Has anyone else had problems NetBooting Xserve G5 with the PCI RAID card installed?
I've got a Dual 2.0 GHz and Dual 2.3 GHz Xserve G5 that both can't seem to NetBoot consistently. On the very odd occasion they do netboot but not very oftern. When you set the NetBoot volume from the Startup Disk system preference and reboot, they just fail to boot and eventually their fans go crazy.
I have other Xserve G5s that NetBoot just fine. I've tried different network cables and swapping switch ports with Xserves that work, but it hasn't helped.
Could it be something on the NetBoot server?
Looking at the system log on the NetBoot server you can see the "bootpd" request from the booting server. I don't have a graphics card install in the Xserves being NetBooted so don't know what's being displayed on the server's console.
The NetBoot server is an Intel-based Xserve (Late 2006) running 10.4.11.

that seems to be the next step here: find or purchase a new card to test the existing drives.
i had wondered if these cards aren't compatible with the 750 gb drives. does anyone know?
also, would a bad battery cause such craziness? does the battery keep read/write cache data on the 64mb on-card memory for just this purpose? i haven't found much documentation on the apple branded cards.
thanks for your help.

Apple Cinema Display 23-inch with PCI graphics card on a PC...?

My wife has a Dell Dimension 2400 PC along with a Mac G4. The Mac will obviously drive the 23-inch display with no problem, but the PC has on-board graphics which are awful. The only improvement is via a PCI graphics card, and a KVM switch (using the DVI interface on both Mac and PC). Does anyone know of an inexpensive PCI graphics card which will cope with the 23-inch display? Gaming is not on the list of priorities, but page layouts for posters and small (8-page) brochures is what it's needed for.
The Dell's operating suystem is XP Professional, and the G4's is Tiger. Thanks for any help.
Chris

I got the blue&white G3 w SDRAM/6GB.
do you think http://www.amazon.com/gp/product/B00DC1P8VA/ref=ox_sc_act_title_1?ie=UTF8&psc=1& smid=A1EF9OE38VX40W
will solve this? I believe I need a DVI-D female to VGA male adapter?
That adapter is for connecting a VGA display to a computer's DVI port.
If your computer has the ATI Rage 128 graphics card it will have one DVI port and one VGA port. It won't run both ports simultaneously.
If the display has a DVI plug, plug it into the computer's DVI port. No special cable or adapter is needed, but the computer may not support the resolution of the 23".
If the display uses ADC (Apple Display Connector)
<http://upload.wikimedia.org/wikipedia/commons/thumb/0/09/AppleDisplayConnector.j pg/220px-AppleDisplayConnector.jpg>
you will also need a DVI to ADC adapter
<http://www.amazon.com/Apple-DVI-ADC-Display-Adapter/dp/B00011KHT2>

HP p7-1174 locks on startup with PCIe parallel card installed (SYBA SD-PEX1005)

Hello, I just purchased a PCIe parallel card from SYBA for my HP p7-1174 (AMD A8, 8GB, W7 64bit) and upon installing it locks up after the HP blue screen (it locks on a black screen with a DOS cursor blinking). Tried different ports, same result. I installed the card on another computer (HP p6774y, AMD Phenom II, 6GB, W7 64bit) and it works flawlessly. Does anybody know of any configuration prior to installation of the card that I would have to do? Any input is greatly appreciated.

Follow up: The Rosewill RC-302e works flawlessly.

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.

Section of the data collected with PCI 1422 card connected to a CCD camera looks step-like

I am using the PCI 1422 card with a DALSA CA-D1-0128T camera to acquire and save fluorescence data from a heart stained with a potentiometric dye. The camera is set to work at 490 frames per second. My acquisition program (made using a producer consumer loop in Labview 2009) works fine most of the times, but sometimes a small section of the collected data looks step-like (not continuous). I have attached herewith a word document containing a snap of the data. Could you please give me some suggestions as to why this happens and how can I rectify it?
Thanks in advance
Anuj Agarwal
Attachments:
Doc1.doc ‏123 KB

Hi Anuj,
First, this sounds like a very cool application. What are you measuring? Is it in vivo?
I believe that I see what you are referring to--is it where your cursor is that you are seeing the "step" problem? Also, could you give us a little more information aboutwhat type of data we are looking at? Is this some sort of image analysis data?
In terms of code structure, due to the way that LabVIEW handles image data types (it is essentially a pointer to the data instead of the data itself), I wouldn't recommend passing an image via a queue.
So, please let me know a bit more about what type of data we are looking at, and what your code looks like, and I'll be happy to help.
Cheers,
Marti C
Applications Engineer
National Instruments
NI Medical

64 channel 1450 Hz data logging with PCI-6033E card, on-line averaging and viewing the raw and averaged signal in CWGraphs.

I'm acquiring 64 channels at sampling rate of about 1450kHz continuously and showing the data second by second in a CWGraph. Now, I would like to add an on-line averaging for all of those 64 channels and show it in another CWGraph. The averaging should occur with respect of external trigger and the sample should consist of about 100ms prestimulus and 500ms poststimulus period. Has anybody been handling this sort of things? How it's solved with ComponentWorks and Visual Basic?
I'm using double Pentium 700MHz processors and NI-DAQ PCI-6033E card.

1. To get started with external triggering check out the examples in the Triggering folder that install with CW under MeasurementStudio\VB\Samples\DAQ\Triggering.
2. Create a prestimulus buffer that always contains the latest 100 ms of data. Just modify the CWAI1_AcquiredData event to transfer ScaledData (the data acquired) to your prestimulus buffer. See how there will always be a prestimulus buffer of data regardless of trigger state?
3. On the trigger, you can use the same CWAI1_AcquiredData event to route the data into poststimulus buffer and average the 2.
I see something like this:
if no trigger
100 ms of data to prestimulus buffer
if trigger
500 ms of data to poststimulus buffer
averaging and display function
reset trigger and buffers
good luck
ben schulte
application engineer
national instruments
www.ni.com/ask

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.

Video capture with PCI-1407 card

I need to capture and analyze RS-170 and RS-343 video to answer the question, does it meet specifications [synch voltage, normal image resolution, etc] and would like to do so with a PCI-1407. Can I do anything with RS-343?

The NI-1407 is designed to work with EIA RS-170 and CCIR cameras. If your camera follows either of those specs, then the 1407 will work.
RS-330 is a standard recommended by EIA for signals generated by closed-circuit TV cameras scanned at 525/60 and interlaced 2:1. The standard seems similar to RS-170, but H-sync pulses are absent during V-sync.
With that said, I don't think an RS-330 camera will work with a 1407, but I've never tried it... The 1407 requires H-sync signals so we know where to separate lines. Without those signals, the 1407 will not be able to sync with the camera.
Kyle V.

Precise trajectory control with PCI Step Card and triggered buffer

Hello,
I'm trying to use PCI STep 4OX card for precise trajectory control. Every 200ms I'm putting motion tasks into buffer and I'm using external 10ms trigger input for this buffer. For duration about 100ms per one tick of trigger is fine, but I need make change in position every 10ms and it seems unusable.
Where is the problem? What is maximal duration of trigger puls, what max freq. of this pulses ... etc.
Thank you for your answers and suggestions,
Vaclav Maixner
System Engineer

The board you are using is quite old and most probably will not give you the perfomrance you need. I would recommend upgrading your board to one of the 7334 series motion controllers that will surely giveyou that kind of performance throuogh their preemptive start fucntionality.

RTSI cable configuration with PCIe 1433 card

Similar Messages

Maybe you are looking for