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.

Similar Messages

XServe with hardware RAID card and headless install

Today, while trying to remotely install Mac OS X Server 10.4 ("Tiger") on an Apple XServe G5 with hardware RAID card, I discovered that it did not report the IP address of the server (booted from CD) with the sa_srchr command as it did with Mac OS X Server 10.3. With Mac OS X Server 10.3, I could boot the server from the CD, use the sa_srchr command from a remote machine to find the IP address, ssh into the server and user megaraid to create or recreate the RAID volumes using the internal drives in the server.
When I boot the XServe from the Mac OS Server 10.4 CD and run the sa_srchr command from a remote computer, I get "No Longer Used" in the place where the IP address should be (as it was in 10.3 Server and as it is described in the current, 10.4 Server, "Command Line Administration" manual).
Example: localhost#2xCPUFormat#No Longer Used #xx:xx:xx:xx:xx:xx#Mac OS X Server 10.4#RDY4PkgInstall#3.0#512
Just as an experiment, I threw the Mac OS X Server 10.4 DVD into an iMac G5 and booted it. Using the sa_srchr command, I get the same "No Longer Used" where the IP address should be.
Does anyone know:
Is this a problem with the original "Mac OS X Server 10.4.0" installation CDs? Do I need 10.4.1, 10.4.2 or 10.4.3 CD/DVD media?
Has this functionality been removed from Tiger install discs? Is there another way to create the RAID volumes?
I know that I can use the Mac OS X 10.3 Server disks to work around this, but it doesn't seem like I should have to...
Justin Sako
Leander ISD

Are you sure you have the 10.4 Admin Tools installed on the 'client' machine? I've seen this happen when trying to set up a 10.4 server from a machine with 10.3 Admin Tools installed. Try deleting the Admin Tools from your client machine, and re-install from a 10.4 DVD.
iBook G4 Mac OS X (10.4.3)

XServe G5 unable to boot from raid 5 partition (Apple PCI raid card)

I've installed Leopard Server on a raid 5 partition, on a XServe G5 with an Apple PCI raid card, but I can't boot from that partition.
This server was running on 10.3 server with the same partition since 4 years and they where no problem.
Somebody have a suggestion ?
Spec : write cache off, readahead off, iopolicy direct / 3 hard drives Apple 80GB

Post to the appropriate forum under Server Products.

Has anyone tried 1 terabyte drives with Apple G5 PCI RAID card 1M9699g?

I am planning on setting up RAID 5 on one of my PPC G5 Xservers with an Apple PCI RAID card and 3 Hitachi 1 terabyte HDs. At $180 a drive and a $300 or so for a card this seems like a good setup. Has anyone tried this or have any suggestions.

It worked, for about $860 I now have a 1.8 TB xServer

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

PCI RAID Card -- jumper settings?

Hello and thanks, the folks in these forums have always been very helpful.
Installing the PCI Raid card into the G5 was a little more involved than I expected, and while I was getting it seated one of the jumpers fell off. I don't know which one, and I am not going to install it into the new server until I get the card set up correctly.
I cannot find a pic or diagram of the default positions of these jumpers, or information on whether they even matter. The manual has no information on this aspect of the card.
Thanks again,
Steve

Thanks so much for your help.
No, it is this one below, a SATA Raid card that only works with the internal drives. I would provide a link to the manual, but it will be no help as it provides no jumper-block charts or descriptions.
PCI Hardware RAID card
This 64-bit/66 MHz PCI card provides enhanced reliability and performance to Xserve G5's internal Serial ATA (SATA) drives using a hardware RAID controller. Bypassing the on-board hard drive controllers, this card provides three independent 150MBps Serial ATA controllers backed by a high-performance RAID processor and 64MB of RAID controller cache with an on-card backup battery.
The PCI Hardware RAID controller provides RAID level 0, 1 and 5 capabilities to the Apple Drive Module bays and is managed by a provided command-line management tool. Multiple logical drives can be created, and each logical drive supports different RAID levels, different stripe sizes, and different cache policies. In the case of a drive failure in a protected RAID 1 or 5 configuration, drives can be hot-swapped and the RAID set can be rebuilt on to a new drive online while the server continues to serve data.
Note: RAID levels 0 and 1 require a minimum of 2 Apple Drive modules; RAID level 5 requires 3 Apple Drive modules. Apple recommends drive modules of the same size for each RAID set. The hardware RAID card does not support FireWire Target Disk mode.

What is the best e-Sata PCI RAID card for Mavericks.

What is the best e-Sata PCI RAID card for Mavericks. Bought a new MAC PRO with Mavericks and the older PCI 1095,3124 that I used on older MAC Pro does not work. The MAC sees it, but the drivers never show up as being installed. If I could find drivers that work or a recommended PCI card it would be appreciated.
Thanks

PM made sense - 6 yrs ago when disk drives were much slower. Today it is a bottleneck.
SAS makes more sense. Outside of SSD, no disk drive maxes out by itself one PM interface (an SSD will) but it also means just two drives are enough to do so. So check out why to avoid PM:
www.macperformanceguide.com

OS drive + RAID 1 with Apple RAID card

I have a G5 Xserve with the RAID card and three ADM drives. How do I set up Megaraid to have a single non-raid drive and a RAID 1 mirror? I installed the OS onto one of the drives after a "destroyconfig". When I create the RAID with drives 1 and 2, the drive 0 is lost. THe only way I found to make it work was with a soft RAID 1 in disk utility.

How do I set up Megaraid to have a single non-raid drive and a RAID 1 mirror?
I'd go with not connecting one of the drives to the RAID card.
When you installed the card you replaced three short SATA cables with three long ones - one per drive.
Just replace one of the long ones with one of the original short ones. This will reconnect one of the drives back to the motherboard, leaving two drives connected to the RAID card.
Kind of a hack, for sure, but in lieu of having a JBOD mode in megaraid it seems like the simplest solution.

2010 Mac Pro with Apple RAID card - "Drive carrier 00:03 removed"

I've got a 2010 Mac Pro with the Apple RAID card and 4 internal identical Seagate ST32000641AS 2TB drives inside.
I've never had a problem with the RAID card (either battery or in operation) except for one thing:
Almost every time I shut the machine down (which I try to do as rarely as possible), it keeps losing Drive 3, the spare.
(See RAID Utility event log snippet below.)
[I wish I could understand why this Apple RAID card keeps losing the spare across power-cycles/reboots, but I digress.]
So I just adopted it as the spare and it spawns the rebuild and many hours later, everything's fine again.
... until the last time I rebooted (Jan. 2nd).
After the usual "I lost the spare" message upon login, it began the rebuild.
But this time, about 11 1/2 hours later the rebuild stopped and RAID Utility reported "Drive carrier 00:03 removed".
Bay 3 is now missing in the Controller view.
I powered off the system last night, and left it off overnight. Today I took all the drives out, blew the dust off and reseated them.
Same thing. Drive 3 is still missing, and now the rebuild task aborted.
The drive bay location shouldn't matter, right? Can I swap the Bay 3 drive with the Bay 4 drive?
I figure one of two things would happen:
(1) It will report Bay 3 as being there but Bay 4 as being missing, same situation as is now. Meaning the problem is in the Bay 3 spare drive.
(2) It will report Bay 3 as being missing (despite a 'good' drive being present) and Bay 4 will be the (unattached) spare, and the RAID set will be unviable. Meaning the problem is with the drive bay itself, not whatever drive is plugged into it.
If "Drive carrier removed" is trying to tell me the disk is bad, why do I not see any log messages about it? I suppose a spare that never gets used could go bad from lack of use, but ... no messages at all?
Hesitant to plunk down $160 on a new spare disk if the present one isn't actually dead ...
% sudo raidutil list raidsetinfo
                                     Total     Avail
Raidsets      Type       Drives       Size      Size Comments
RS1           RAID 5     1,2,4      5.23TB    0.00MB Rebuild: 0% complete
% sudo raidutil list driveinfo
Drives Raidset       Size      Flags
Bay #1 RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
Bay #2 RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
Bay #4 RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
Event log snippet:
Saturday, January 11, 2014 8:15:19 AM PT
Background task aborted: Task=Rebuild,Scope=DRVGRP,Group=RS1
informational
Friday, January 3, 2014 3:50:28 AM PT
Drive carrier 00:03 removed
informational
Thursday, January 2, 2014 4:29:37 PM PT
Marked drive in bay 3 as a global spare
informational
Thursday, January 2, 2014 4:29:28 PM PT
Adopted drive in bay 3
informational
Thursday, January 2, 2014 4:28:34 PM PT
Degraded RAID set RS1 - No spare available for rebuild
critical
Saturday, December 7, 2013 5:35:17 PM PT
Marked drive in bay 3 as a global spare
informational
Saturday, December 7, 2013 5:35:08 PM PT
Adopted drive in bay 3
informational
Saturday, December 7, 2013 5:34:11 PM PT
The "RedundancyScrub" command could not be executed. (Invalid request or invalid parameter in the request.)
warning
Saturday, December 7, 2013 5:34:03 PM PT
Degraded RAID set RS1 - No spare available for rebuild
critical
Friday, December 6, 2013 4:56:47 AM PT
Battery finished conditioning
informational
Thursday, December 5, 2013 9:53:44 PM PT
Battery started scheduled conditioning cycle (write cache disabled)
informational
Friday, September 6, 2013 10:53:11 PM PT
Battery finished conditioning
informational
Friday, September 6, 2013 3:41:33 PM PT
Battery started scheduled conditioning cycle (write cache disabled)
informational
Saturday, June 8, 2013 3:41:35 PM PT
Battery finished conditioning
informational
Saturday, June 8, 2013 8:37:49 AM PT
Battery started scheduled conditioning cycle (write cache disabled)
informational
Thursday, May 30, 2013 4:09:51 PM PT
Marked drive in bay 3 as a global spare
informational
Thursday, May 30, 2013 4:09:42 PM PT
Adopted drive in bay 3
informational
Thursday, May 30, 2013 4:08:59 PM PT
Degraded RAID set RS1 - No spare available for rebuild
critical
Thursday, May 30, 2013 3:32:29 PM PT
Degraded RAID set RS1
warning

Power Pig wrote:
"Hesitant to plunk down $160 on a new spare disk if the present one isn't actually dead ...
% sudo raidutil list raidsetinfo
                                     Total     Avail
Raidsets      Type       Drives       Size      Size Comments
RS1           RAID 5     1,2,4      5.23TB    0.00MB Rebuild: 0% complete
I was talking about this.
This looks like a RAID 5 setup without the parity to me. I would said it basically a RAID 0.
Also you metioned "I guess that previous spare must really have gone 'bad', despite having never been used! "
I wiped everything out, I selected the 3 disks and clicked on "Create RAID Set" with RAID5 selected and the "Use unassigned drives as spares" option checked. The 3rd disk has always been marked as the spare ever since then. You do not have a choice to create a "RAID5 setup without the parity". If I wanted a RAID0 I would have chosen a RAID0! raidutil now says
% sudo raidutil list raidsetinfo
                                     Total     Avail
Raidsets      Type       Drives       Size      Size Comments
RS1           RAID 5     1,2,3,4    5.23TB    0.00MB No tasks running
Every time the system would 'lose' Drive 3 on boot, I would just keep rebooting until it was 'found', and then manually re-assign the now-'floating' drive as the spare - and the RAID would rebuild.
There was never a problem until the day that prompted this post - when it would not find Drive 3 no matter what I did. I turned the Mac Pro off for several hours until the drives had all cooled down and it still did not find the drive. I left the machine on but unmounted the degraded volume until I got the new replacement drive.
I really don't understand what you are getting at. It's like you are trying to tell me I set it up as a 4-drive RAID5 with no parity(!) and that I was in grave danger because one of the disks was gone. The actual RAID contents (spread across Drives 1, 2 and 4) were never in danger, unless a 2nd disk had failed while the spare was not seen by the Apple RAID card. I wasn't too worried about that happening.

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

Best Throughput for RAID - Internal SATA vs. PCI RAID Card

Hi, we're upgrading our old server, which has been on an upgraded G4. We put 3 SATA drives in it, connected to a Highpoint 1820a RAID card running RAID 5.
We're moving this to an older G5 1.6 GHz model (2003). It currently has 2 internal SATA drive bays, but I know can be expanded with an adapter kit. It also has just plain PCI slots (not PCI-X or PCIe).
So I'm wondering what would provide better performance (throughput I guess):
• Using the 2 internal bays with a software RAID 1?
• Putting our old Highpoint RAID card in the PCI slot and running RAID 1 or possibly RAID 5 (with another drive)?
I know the RAID card doesn't use the processor for RAID functions, but I think in a RAID 1 it's fairly minimal, correct? I'm mostly wondering if the older basic PCI slot would bet the bottleneck in a fast system compared to the onboard SATA controllers?
THANKS!

Well, we're most concerned with data security and reliability. We're not streaming video or anything else that would demand extreme throughput. The server is mostly serving files to 4-5 users. So I imagine the performance gains would only be noticed when opening/closing files off the server, correct?
And we already own the Highpoint card, which has 8 internal SATA ports, so we'll probably use this. It works fine on PCI bus. So we can run this with 4 drives in either two RAID 1s (boot & files); a RAID 5, or a RAID 10.
We'll probably stick with Western Digital or Seagate 'enterprise' SATA drives, such as the WD RE3.
So, do you think we would see much real-world difference between the different RAID options (RAID 1 software, RAID 1 hardware, RAID 5 hardware, RAID 10 hardware)?
Thanks!

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.

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

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

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.

Trouble NetBooting Xserve G5 with PCI RAID Card

Similar Messages

Maybe you are looking for