R60 9459AT8 - is the USB2 on the PCIe bus?

I have an excellent R60, Type 9459AT8, with an SSD, and would like to minimize disk reads and writes. I've already set up the TRIM and configured my Xubuntu file system with no swap. I'd like to put the swap on a (physically) tiny flashdrive, so I can figure out what the max read/write speed would be. I sure would like to know if the left-side USB 2 port is on the PCIe bus or not, and whther it works at high-speed (480 Mbps), full-speed (12 Mbps), or low-speed (1.5 Mbps).

Hi! HERE's a widget that you'll like for temp monitoring. And HERE's the Apple Doc you wanted to find. Tom

Similar Messages

  • What is the PCI bus performance of the 1422?

    I'm currently using an IMAQ PCI-1422 to acquire images from a camera. The image size is 1280x1024 @ 8-bits a pixel. Currently the camera can only run freely at 20 fps. So this data rate is roughly 26 MB/s. The IMAQ card seems to be able to acquire these images at that rate. However, I need to be able to retrieve these images into system memory at the same rate. At this time, I've only managed to retrieve the images at around 12 fps which is about 16 MB/s. Is this all I can reasonably expect from this card? There is no other activity along the PCI bus except for perhaps minor updates to the video display.
    I'm acquiring images using a Grab. I use a callback on the Buffer Done signal to trigger an acquisit
    ion running in another thread. Actually, I'd prefer to the acquisition in the callback itself, but I am uncertain as to how the callback is implemented and what I can and can't do in a callback. Is there documentation somewhere that I'm missing?
    Oh yeah. I'm using MSVC++ and Windows 98.
    Thanks

    I tried the example and removed the clipping the ROI to the size of the canvas and also took out the image plot to make sure we would get accurate times. I get the same frame rate with that example as I did with my own code (around 12 fps). Also, I neglected to mention that for my own code I placed calls to timers just before and just after the call to imgGrab, and the time difference is what you would expect: about .083 seconds (average) to retrieve one frame.
    I know nothing about the internal structure of the PCI-1422, but considering that we are retrieving images from the same SDRAM memory that is being used to acquire images, are we seeing some sort of bus contention on the PCI-1422 itself? Also, the camera I'm using is an evaluation board, and I have access
    to the schematics and should soon have access to the CPLD design. So I can verify the design of the camera itself. I'm glad to hear that you expect to be able to transfer at 45MB/sec. That probably means that there is something not quite right either in the camera interface or perhaps in the computer system being used. But if you have any other ideas, I'd be glad to hear them.
    Thanks for the response.

  • [Bumblebee]Failed to initialize the NVIDIA GPU at PCI:1:0:0.

    Hi!
    I've instaled Arch about a month ago and now wanted to check my nvidia card using Bumblebee, but have some errors…
    [wicu@arch:~]$ optirun -vv minecraft
    [ 4859.259278] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [ 4859.404191] [DEBUG]optirun version 3.0.1 starting...
    [ 4859.404220] [DEBUG]Active configuration:
    [ 4859.404226] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [ 4859.404242] [DEBUG] X display: :8
    [ 4859.404254] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia-bumblebee:/usr/lib32/nvidia-bumblebee
    [ 4859.404265] [DEBUG] Socket path: /var/run/bumblebee.socket
    [ 4859.404276] [DEBUG] VGL Compression: proxy
    [ 4859.536971] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 4859.537027] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 4859.537053] [DEBUG]Socket closed.
    [ 4859.537086] [ERROR]Aborting because fallback start is disabled.
    [ 4859.537094] [DEBUG]Killing all remaining processes.
    [wicu@arch:~]$ sudo journalctl // here is only part when I tried use bumblebee
    Nov 26 17:48:43 arch kernel: NVRM: failed to copy vbios to system memory.
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238670] [WARN][XORG] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238729] [WARN][XORG] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238765] [WARN][XORG] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238819] [ERROR][XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238826] [ERROR][XORG] (EE) NVIDIA(0): check your system's kernel log for additional error
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238830] [ERROR][XORG] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238835] [ERROR][XORG] (EE) NVIDIA(0): README for additional information.
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238841] [ERROR][XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238847] [ERROR][XORG] (EE) NVIDIA(0): Failing initialization of X screen 0
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238853] [ERROR][XORG] (EE) Screen(s) found, but none have a usable configuration.
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238858] [ERROR][XORG] (EE)
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238863] [ERROR][XORG] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238868] [ERROR][XORG] (EE)
    Nov 26 17:48:43 arch bumblebeed[303]: [ 4139.238873] [ERROR]X did not start properly
    Nov 26 17:48:43 arch kernel: NVRM: RmInitAdapter failed! (0x30:0xffffffff:739)
    Nov 26 17:48:43 arch kernel: NVRM: rm_init_adapter(0) failed
    // xorg log
    [ 4859.510]
    X.Org X Server 1.13.0
    Release Date: 2012-09-05
    [ 4859.511] X Protocol Version 11, Revision 0
    [ 4859.511] Build Operating System: Linux 3.6.3-1-ARCH x86_64
    [ 4859.511] Current Operating System: Linux arch 3.6.7-1-ARCH #1 SMP PREEMPT Sun Nov 18 10:11:22 CET 2012 x86_64
    [ 4859.511] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=70a6cff9-bcf7-42eb-9ba1-73953e023617 ro quiet
    [ 4859.511] Build Date: 08 November 2012 07:09:29PM
    [ 4859.511]
    [ 4859.511] Current version of pixman: 0.28.0
    [ 4859.511] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4859.511] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4859.511] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Nov 26 18:00:43 2012
    [ 4859.511] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
    [ 4859.511] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4859.511] (==) ServerLayout "Layout0"
    [ 4859.512] (==) No screen section available. Using defaults.
    [ 4859.512] (**) |-->Screen "Default Screen Section" (0)
    [ 4859.512] (**) | |-->Monitor "<default monitor>"
    [ 4859.512] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 4859.512] (**) | |-->Device "Device1"
    [ 4859.512] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 4859.512] (**) Option "AutoAddDevices" "false"
    [ 4859.512] (**) Not automatically adding devices
    [ 4859.512] (==) Automatically enabling devices
    [ 4859.512] (==) Automatically adding GPU devices
    [ 4859.512] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 4859.512] Entry deleted from font path.
    [ 4859.512] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 4859.512] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 4859.512] Entry deleted from font path.
    [ 4859.512] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 4859.512] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 4859.512] (++) ModulePath set to "/usr/lib/nvidia-bumblebee/xorg/,/usr/lib/xorg/modules"
    [ 4859.512] (==) |-->Input Device "<default pointer>"
    [ 4859.512] (==) |-->Input Device "<default keyboard>"
    [ 4859.512] (==) The core pointer device wasn't specified explicitly in the layout.
    Using the default mouse configuration.
    [ 4859.512] (==) The core keyboard device wasn't specified explicitly in the layout.
    Using the default keyboard configuration.
    [ 4859.512] (II) Loader magic: 0x7fcc40
    [ 4859.512] (II) Module ABI versions:
    [ 4859.512] X.Org ANSI C Emulation: 0.4
    [ 4859.513] X.Org Video Driver: 13.1
    [ 4859.513] X.Org XInput driver : 18.0
    [ 4859.513] X.Org Server Extension : 7.0
    [ 4859.513] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 4859.513] setversion 1.4 failed
    [ 4859.516] (--) PCI:*(0:1:0:0) 10de:0de9:17aa:3901 rev 161, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/524288
    [ 4859.516] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4859.516] Initializing built-in extension Generic Event Extension
    [ 4859.516] Initializing built-in extension SHAPE
    [ 4859.516] Initializing built-in extension MIT-SHM
    [ 4859.516] Initializing built-in extension XInputExtension
    [ 4859.516] Initializing built-in extension XTEST
    [ 4859.516] Initializing built-in extension BIG-REQUESTS
    [ 4859.516] Initializing built-in extension SYNC
    [ 4859.516] Initializing built-in extension XKEYBOARD
    [ 4859.516] Initializing built-in extension XC-MISC
    [ 4859.516] Initializing built-in extension SECURITY
    [ 4859.516] Initializing built-in extension XINERAMA
    [ 4859.516] Initializing built-in extension XFIXES
    [ 4859.516] Initializing built-in extension RENDER
    [ 4859.516] Initializing built-in extension RANDR
    [ 4859.516] Initializing built-in extension COMPOSITE
    [ 4859.516] Initializing built-in extension DAMAGE
    [ 4859.516] Initializing built-in extension MIT-SCREEN-SAVER
    [ 4859.516] Initializing built-in extension DOUBLE-BUFFER
    [ 4859.516] Initializing built-in extension RECORD
    [ 4859.516] Initializing built-in extension DPMS
    [ 4859.516] Initializing built-in extension X-Resource
    [ 4859.516] Initializing built-in extension XVideo
    [ 4859.516] Initializing built-in extension XVideo-MotionCompensation
    [ 4859.516] Initializing built-in extension XFree86-VidModeExtension
    [ 4859.516] Initializing built-in extension XFree86-DGA
    [ 4859.516] Initializing built-in extension XFree86-DRI
    [ 4859.516] Initializing built-in extension DRI2
    [ 4859.516] (II) LoadModule: "glx"
    [ 4859.516] (II) Loading /usr/lib/nvidia-bumblebee/xorg/modules/extensions/libglx.so
    [ 4859.526] (II) Module glx: vendor="NVIDIA Corporation"
    [ 4859.526] compiled for 4.0.2, module version = 1.0.0
    [ 4859.526] Module class: X.Org Server Extension
    [ 4859.526] (II) NVIDIA GLX Module 310.19 Thu Nov 8 01:12:43 PST 2012
    [ 4859.526] Loading extension GLX
    [ 4859.526] (II) LoadModule: "nvidia"
    [ 4859.526] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 4859.526] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 4859.526] compiled for 4.0.2, module version = 1.0.0
    [ 4859.526] Module class: X.Org Video Driver
    [ 4859.526] (II) LoadModule: "mouse"
    [ 4859.527] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
    [ 4859.527] (II) Module mouse: vendor="X.Org Foundation"
    [ 4859.527] compiled for 1.13.0, module version = 1.8.1
    [ 4859.527] Module class: X.Org XInput Driver
    [ 4859.527] ABI class: X.Org XInput driver, version 18.0
    [ 4859.527] (II) LoadModule: "kbd"
    [ 4859.527] (WW) Warning, couldn't open module kbd
    [ 4859.527] (II) UnloadModule: "kbd"
    [ 4859.527] (II) Unloading kbd
    [ 4859.527] (EE) Failed to load module "kbd" (module does not exist, 0)
    [ 4859.527] (II) NVIDIA dlloader X Driver 310.19 Thu Nov 8 00:53:33 PST 2012
    [ 4859.527] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 4859.527] (--) using VT number 7
    [ 4859.527] (II) Loading sub module "wfb"
    [ 4859.527] (II) LoadModule: "wfb"
    [ 4859.527] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 4859.527] (II) Module wfb: vendor="X.Org Foundation"
    [ 4859.527] compiled for 1.13.0, module version = 1.0.0
    [ 4859.527] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 4859.527] (II) Loading sub module "ramdac"
    [ 4859.527] (II) LoadModule: "ramdac"
    [ 4859.527] (II) Module "ramdac" already built-in
    [ 4859.527] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 4859.527] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 4859.527] (==) NVIDIA(0): RGB weight 888
    [ 4859.527] (==) NVIDIA(0): Default visual is TrueColor
    [ 4859.527] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 4859.527] (**) NVIDIA(0): Option "NoLogo" "true"
    [ 4859.528] (**) NVIDIA(0): Option "UseEDID" "false"
    [ 4859.528] (**) NVIDIA(0): Option "ConnectedMonitor" "DFP"
    [ 4859.528] (**) NVIDIA(0): Enabling 2D acceleration
    [ 4859.528] (**) NVIDIA(0): ConnectedMonitor string: "DFP"
    [ 4859.528] (**) NVIDIA(0): Ignoring EDIDs
    [ 4859.534] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 4859.534] (EE) NVIDIA(0): check your system's kernel log for additional error
    [ 4859.534] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
    [ 4859.534] (EE) NVIDIA(0): README for additional information.
    [ 4859.534] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    [ 4859.534] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 4859.534] (II) UnloadModule: "nvidia"
    [ 4859.534] (II) UnloadSubModule: "wfb"
    [ 4859.534] (EE) Screen(s) found, but none have a usable configuration.
    [ 4859.534]
    Fatal server error:
    [ 4859.534] no screens found
    [ 4859.534] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 4859.534] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
    [ 4859.534] (EE)
    [ 4859.534] Server terminated with error (1). Closing log file.
    [wicu@arch:~]$ lspci | grep VGA
    3:00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    14:01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630M] (rev a1)
    [wicu@arch:~]$ primusrun minecraft
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    asdf
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    27 achievements
    208 recipes
    Setting user: Druedain, -4246576297828159265
    primus: fatal: failure contacting bumblebee daemon
    [18:05:39 - wicu@arch:~]$ primusrun minecraft
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    asdf
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    27 achievements
    208 recipes
    Setting user: Druedain, -7896572405277476304
    primus: fatal: failure contacting bumblebee daemon
    [wicu@arch:~]$ systemctl | grep bumblebee
    35:bumblebeed.service

    [wicu@arch:~]$ dmesg | grep nvidia
    782:[ 6.776816] nvidia: module license 'NVIDIA' taints kernel.
    784:[ 6.784411] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
    [wicu@arch:~]$ cat /etc/bumblebee/bumblebee.conf
    # Configuration file for Bumblebee. Values should **not** be put between quotes
    ## Server options. Any change made in this section will need a server restart
    # to take effect.
    [bumblebeed]
    # The secondary Xorg server DISPLAY number
    VirtualDisplay=:8
    # Should the unused Xorg server be kept running? Set this to true if waiting
    # for X to be ready is too long and don't need power management at all.
    KeepUnusedXServer=false
    # The name of the Bumbleblee server group name (GID name)
    ServerGroup=bumblebee
    # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
    # server exits.
    TurnCardOffAtExit=false
    # The default behavior of '-f' option on optirun. If set to "true", '-f' will
    # be ignored.
    NoEcoModeOverride=false
    # The Driver used by Bumblebee server. If this value is not set (or empty),
    # auto-detection is performed. The available drivers are nvidia and nouveau
    # (See also the driver-specific sections below)
    Driver=
    ## Client options. Will take effect on the next optirun executed.
    [optirun]
    # The method used for VirtualGL to transport frames between X servers.
    # Possible values are proxy, jpeg, rgb, xv and yuv.
    VGLTransport=proxy
    # Should the program run under optirun even if Bumblebee server or nvidia card
    # is not available?
    AllowFallbackToIGC=false
    # Driver-specific settings are grouped under [driver-NAME]. The sections are
    # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
    # detection resolves to NAME).
    # PMMethod: method to use for saving power by disabling the nvidia card, valid
    # values are: auto - automatically detect which PM method to use
    # bbswitch - new in BB 3, recommended if available
    # switcheroo - vga_switcheroo method, use at your own risk
    # none - disable PM completely
    # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
    ## Section with nvidia driver specific options, only parsed if Driver=nvidia
    [driver-nvidia]
    # Module name to load, defaults to Driver if empty or unset
    KernelDriver=nvidia
    Module=nvidia
    PMMethod=auto
    # colon-separated path to the nvidia libraries
    LibraryPath=/usr/lib/nvidia-bumblebee:/usr/lib32/nvidia-bumblebee
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia-bumblebee/xorg/,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    ## Section with nouveau driver specific options, only parsed if Driver=nouveau
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    [wicu@arch:~]$ cat /etc/bumblebee/xorg.conf.nvidia
    Section "ServerLayout"
    Identifier "Layout0"
    Option "AutoAddDevices" "false"
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "ConnectedMonitor" "DFP"
    EndSection

  • X-Fi XtremeGamer doesn't work, is pci bus the cau

    Hello,
    warning: lengthy post ahead
    I've recently bought an X-Fi XtremeGamer and an old thinclient pc, with the idea of making a small, low-power mp3 player. The thin client has a VIA C3 533Mhz processor, 256Mb ram, and a single PCI slot (used for the X-Fi).
    However, when I install the X-Fi and the drivers, it just doesn't seem to work: while it shows up in the device manager without any error indication, it doesn't produce any sound at all. The audio console behaviour is odd as well: changing modes causes it to completely freeze up, and I can't select any speaker configuration, even tough I have analog speakers connected to the green jack.
    I'm running a fresh installation of Windows XP SP2, disabled the on-board audio and removed the drivers for the on-board audio. I've already tried cleaning and reinstalling the X-Fi drivers, but the result stays the same. Trying to change sound levels in microsoft's sound manager doesn't make a difference either. I've tested the sound card in another, 'regular' pc, and it works fine.
    Because there's absolutly no documentation to be found for this thinclient, I can't determine the exact version of it's PCI bus. However, based on the keying, it appears to use 5V signalling. This shouldn't be a problem for the X-Fi, since it's keying indicates it can use both 5V and 3.3V pcI busses. However, I was able to determine that the PCI slot does *not* provide -2V, as it is supposed to. Could this be the cause of the X-Fi's malfunctioning?
    Thanks

    This is really a bad issue. I think unless you are in the warranty period please change it once again and more over please if possible perform the deleting task over there
    God never made his work for man to mend vmware_happy.gif

  • How do i generate the TTL pulse from PCI 6024E DAQ card

    Hi, I'm trying to write a program which generates a single TTL pulse when it is run. My goal is to generate the pulse, send it to the output channel of my PCI 6024E DAQ card, and then use a BNC cable, to display the signal on the oscilloscope. I have written the code and I think it appears fine but when I try to view the signal on the scope I am unable to see the pulse. I have tried slowing down the sweep on the scope and have adjusted the voltage and time scales but have not seen any response. After examing my DAQ card, I noticed that none of the PFI/TRIG terminals on the card are wired; the output channel connects to terminals for DAC0OUT and Ground. I'm wondering if this pin needs to be wired in orde
    r to generate the pulse since PFI0/TRIG1 is the start trigger terminal. Any help would be appreciated. Thanks.
    Attachments:
    ttl.vi ‏26 KB

    Hi,
    You are looking for a retriggerable pulse generation. Please check the Generate Retriggerable Pulse (DAQ-STC).vi example that ships with LabVIEW.
    Regards,
    RamziH.

  • What's the dynamic range of PCI-6289?

    Dear Sir:
    Could you tell me the dynamic range of PCI-6289?
    Is there any difference using PCI-4472 or PCI-6289 when measuring vibration signal?
    Thank you!
    Regards,

    Hello,
    The PCI-4472 would be best suited for vibration measurments. It has 24-bit resolution, Simultaneous Sampling, Hardware Time-to-Frequency Domain Conversion, 110 dB Dynamic Range, and hardware filtering. See the following Link for more details on the 4472: http://sine.ni.com/apps/we/nioc.vp?cid=10572〈=US
    The 6289 was not built with vibration analysis in mind, the the dynamic range is not spec'd.
    Let me know if you have any further questions.
    Sean C.

  • Trouble in the configuration of a PCI-6013

    Hi:
    I´m triying to get the MAX to recognize my PCI-6013 but i haven´t been able to get the DAQ board configured. I installed the package included with the board that contains LabVIEW 6.01 evaluation software and NI-DAQ 6.9.Of7 repeatedly, and then installed the board in a pci slot for several times. WindowsXP recognizes new hardware but when i try to install it no driver is found. I tried it whith the NI-DAQ 7.0 and the board got configured, but when i run a program i developed with the same board in another pc (and it worked perfectly) y get a 10001 error, something about wrong string orther or something like that. I thouth that maybe it had to do with the wrong channel definition (i did it as virtual channels, for an analog
    input and 8 analog I/O). Well, i would like to get the sistem going with the NI-DAQ 6.9.Of7 since it worked in the past in another Pc ,or some hint in why i get that error working with the NI-DAQ 7.0. I would really apreciate any help, and thank you in advance, it´s nice to be able to rely in someone else with more knowledge and that is willing to help the others. Thank you again.

    I am not quite sure why the disk which shipped with your PCI-6013 included version 6.9.0f7. The PCI-6013 is one of our newer boards, and as such, is only supported by NI-DAQ 6.9.3 or Traditional NI-DAQ 7.0. These are the only two versions of the driver which will support this board.
    Traditional NI-DAQ 7.0 and NI-DAQ 6.9.3 are completely compatible. The VIs which you will use in LabVIEW to program your PCI-6013 are the same. Both of these drivers are available for free download from our web site.
    As for the -10001 error you are receiving, usually this has to do with an error in the channel string applied. Please see the following Knowledge Base article on our website for more information on this error.
    How Do I Handle the DAQ -10001 Error?
    http:/
    /digital.ni.com/public.nsf/websearch/42643645D554D15986256A250054ACEB?OpenDocument
    Regards,
    Justin Britten
    Applications Engineer
    National Instruments

  • HT204384 What are GT/s?- "Computers that use the PCIe bus express their speed as GT/s"? and what else is the card slot used for?

    If I understand correctly the card slot on the Macbook Pro is for flash memory? Can it be used for anything else?

    Read http://support.apple.com/kb/HT3553?viewlocale=en_US&locale=en_US
    for information on the card slot.
    GT/s is gigatransfer per second. It takes into account the overhead of the PCIe bus.
    Allan

  • How is to set the input range of PCI-MIO-16E-1 (6070E) to be 0 to +5V?

    How is to set the input range of PCI-MIO-16E-1 (6070E) to be 0 to +5V? Thank you very much.

    Hi x2am,
    Here is a link to a document about setting input range limits.
    DAQ Input Limits
    Hope this helps!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • 'The cable for the PCI Ethernet is not plugged in' error

    Hi everyone, I've installed a PCI network card for my G5, 1.8 (later model) single processor, and checked to make sure the card has the Realtek chips.
    I've tried the D-Link DGE-528T which is meant to be OSX compatible but to no avail. I get the 'The cable for the PCI Ethernet is not plugged in' message. I've then tried the Pluscom with Realtek 8169 chip and again, get the same message.
    I have a good understanding of networking, have installed several drivers, sometimes manually and I've used the terminal to recode the permissions. I've also removed the extension cache file but still no luck. I've also made sure to follow each install path from the package file and remove any older drivers. I've also installed the card in slot 1.
    I don't think it is the card. Does anyone have any other ideas I could try?

    Where did you get the drivers?
    I've heard of people using D-Link routers, and even D-Link's USB/Wireless adapter, but I've never encountered anyone using a D-Link PCI ethernet card. A quick search didn't find any drivers and without that you're not going to get very far. I'm mildly impressed that the OS recognizes the card at all.

  • Does performing a DAQmx Clear Task on a PCI-4474 card change the state of the IEPE current?

    Does performing a DAQmx Clear Task on a PCI-4474
    card change the state
    of the IEPE current?  If the IEPE current was on, does it remain
    on even though the task as been cleared?  If the IEPE current
    remains on, then I assume I don't have to wait for the IEPE current to
    settle if I make a new Task and start a new measurement--is this
    correct?
    Thank you in advance for your help.
    Ken

    DAQmx Clear Task should not turn off IEPE current. You will have to explicity set IEPE current to On (for that channel) whenever you use any of the AI channels on your 4474 in order to keep the IEPE On because the IEPE for all channels in the AI subsystem will be set to the default state (Off) unless explicitly configured. That said, if you clear a task that had IEPE On, and then initialize a new task and set IEPE On, the IEPE will be uninterrupted and there should be no need to wait for the IEPE to settle. Other components of your measurement system might need time to settle if their state was changed between tasks (DUT, sensor, AC coupling, etc.)
    Doug
    NI Sound and Vibration

  • If you are having issues installing the new Win 7 PCI/PCIe driver.

    If you have a problem with updating to the new Win 7 driver, you may need to do a virgin re-install.
    Uninstall PatchMix and the drivers from the uninstaller, or from add/remove programs.
    Power down and remove the PCI card.
    Boot up and let windows do it's own clean up.
    Power down and re-insert the PCI card.
    Cancel windows hardware wizard if it pops up, (and it should), then install the most recent PatchMix and beta driver updates.
    You may need to load a new factory template in PatchMix, and then rebuild any custom session templates you had.

    Now, do you have to disconnect your printer everytime that you want to use it? If so, this is just a temporary fix and that's not something that you should have to do with regularity.
    It's GLARING, the amount of people who are having issues with this software. Is APPLE listening to its customers? I'm to the point where I'm about to NOT recommend an I-Pod to anyone that asks. If they do, that's what I'm recommending. I'll also steer them to this website so that they can see with their own eyes, the problems that everyone is having.
    This is totally ridiculous. I've been trying for THREE weeks to get my POS I-Pod Shuffle to download songs through I-Tunes 7.0. It's clear to me that these designers of this software haven't got a clue.
    Sorry for the rant but I've had it with this junk.

  • The difference in the action of IgnoreHWSerNum of USB2.0 and USB3.0

    I googled around a lot but was unable to find an answer to this problem, So I am putting it here.
    I simply want that for a USB port, the assigned COM port number does not change for devices with a different serial numbers.
    On investigating I found out that by configuring IgnoreHWSerNum Key in the Registry, registration of Serial Numbers for a device can be ignored.
    Hence I set the IgnoreHWSerNum in the following Registry Key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
    To Test I inserted one of the device in the USB 2.0 port.
    The device was detected as COM3
    Then I tried an another simillar device with different serial number in the same port.
    I could confirm that this one was also detected as COM3
    On checking the entries corresponding to "Vendor ID" and "Product ID" in the following Registry Key
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB
    .. I cannot find the serial numbers of the devices, which is obvious.
    But when I try these two devices in a USB 3.0 port I get different COM port number for each.
    1st device: COM5
    2nd device: COM7
    On checking the entries corresponding to "Vendor ID" and "Product ID" in the following Registry Key
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB
    ... I find the devices serial number, which means that the IgnoreHWSerNum entry did not work.
    Does it mean that IgnoreHWSerNum registry settings does not work for USB 3.0? Or is there another place for the settings?
    If not then how can I assign fixed COM port numbers to the devices with different serial numbers for USB 3.0?
    Any help is appreciated!

    I am seeing the same behavior as mentioned by mr.p-funk.
    I am setting IgnoreHWSerNumXXXXYYYY = 1 in the Registry for a specific printer model (VID=XXXX, PID=YYYY).
    When each printer of the SAME model is connected to the same USB2.0 port, the "ignore serial number" works as expected,
    (i.e. multiple printers of the SAME model can be connected to the SAME physical USB port on the PC without creating a different "print queue".)
    However, when connecting the 2 printers to a USB3.0 port, it does NOT work. Instead, it behaves as though IgnoreHWSerNumXXXXYYYY
    in Registry is set to 0 instead of 1. (i.e. each printer of the SAME model gets a NEW print queue when connected to the SAME USB port on the PC.)
    I work for a printer manufacturer, and being able to "Ignore the USB Serial Number" is something we use with customers quite often.
    So, if there is a way to make this work when the printer is connected to a USB3.0 port on the PC, we need to know about it.
    Sorry Alex Zhaozx, but Kate Li's response is NOT the answer to the question. She only describes the behavior a user will see when this Registry setting (=1) is working correctly,
    i.e. with a USB2 port. We are asking about HOW to make it work with a physical USB3.0 port on the PC.

  • HT201758 Will a USB3 External Drive work in the USB2 port?

    Will a USB3 External Drive work in the USB2 port?

    Some do and some do not. You should read the technical information carefully to determine if it's USB 2.0 compatible.

  • I am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

    i am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

    Hello;
    The first thing you need to figure out is the shape of the trigger pulse needed.
    In case you just need a logic high TTL pulse, you can use one of the digital lines of your DAQ device.
    In case you need a pulse train (multiple trigger pulses), you will need to configure one of the general purpose counters to accomplish that task.
    You can find examples in both Labview and NI-DAQ showing how to program your DAQ board to accomplish both approaches.
    Hope this helps.
    Filipe A.
    Applications Engineer
    National Instruments

Maybe you are looking for

  • Best Buy Just Lost a Long Time Customer

    I am sharing this with the community and Best Buy to showcase the epitome of poor customer service as it relates to a "one-size-fits-all" policy, to warn others, and to tell Best Buy that they've lost a good customer. On Black Friday, I purchased a n

  • Root element required

    SDNers, I have created a message type in XI and have exported the XSD. When I try to import the XSD in the syndicator, I get an error message: Root element required. Thanks in advance. + JT

  • Can I delete all of my information on an ipad without disrupting my iphone?

    Can I delete all of my information & details on an ipad & without disrupting my iphone?

  • This forum is running very slowly for me....

    Hi, I'm on a new 24" iMac and for the most part things have been running well. But starting yesterday, this forum started running very slow. Especially today, just clicking the link to this forum from my bookmark takes at least 2 minutes to go throug

  • Safari 4 slow, crash, shutdown problems? Three solutions to try...

    There are many posts addressing Safari 4's slowness and worse. I had these problems and cured them with three fixes: 1. Empty Cache periodically - Still tried and true. For me, a blank screen trying to load is the cue to empty cache - page then pops.