PXI bus mastering?

I honostly dont know what PXI bus mastering is, but I belive I need to find out pretty soon. I have a project in which I will be needing to take in 16 million samples, 8 million on 2 channels from a PXI-5102 digitizer, and then analyze. The board itself i know can not handle this, but what it can do is "16 million samples to host RAM via PXI bus mastering " This is great, I need 16 million samples, now... how do I do this? Anyhting to get me in the right direction would eb greatly appreciated, thank you very much.
-Mark

""I honostly dont know what PXI bus mastering is, but I belive I need to find out pretty soon."
I do not think you have to worry about what it is unless you plan on dropping this device in a non-NI chassis or do not plan on using NI-drivers.
PXI bus mastering
is a method interfaces can use to control the PXI bus in order to transfer dat from on-board buffers into system memory (or other devcies).
"Back in the Old days" (i.e. 30MHz CPU's) bus mastering was not available on all PCI busses. THen latter on it was available in some PCI slot on some computers but but not all (i.e. 400 Mhz CPU's).
I have never heard of an issues re: bus mastering in PXI chassis.
So...
Drop that board in a PXI chassis and load up NI-DAQ, configure it, and you should be
good to go. NI did all of the hardwork for you!
If want to be certain before purchasing the board just tell ask the sales person to have someone send you an e-mail indicating that the devices will do "X". I have done this anytime I was less than certain re: the fine print in a device spec.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

  • The problem of 8431/4 borad on PXI bus

    Hello,
    when I connect the PXI-8431/4 board to the PXI bus in QNX system, I find that there is only one "PCI Mem Address" record.
    But the other boards(e.g. NI PXI-6602,NI PXI-6250) have two "PCI Mem Address".
    you can see the following detail trace:
    Class          = Unknown (Unknown)
    Vendor ID      = 1093h, National Instruments
    Device ID      = 70b9h, Unknown Unknown
    PCI index      = 0h
    Class Codes    = ff0000h
    Revision ID    = 0h
    Bus number     = 20
    Device number  = 13
    Function num   = 0
    Status Reg     = 280h
    Command Reg    = 117h
    Header type    = 0h Single-function
    BIST           = 0h Build-in-self-test not supported
    Latency Timer  = 20h
    Cache Line Size= 10h un-cacheable
    PCI Mem Address = f6406000h 32bit length 4096 enabled    //PXI-6250
    PCI Mem Address = f6405000h 32bit length 4096 enabled
    Max Lat        = 0ns
    Min Gnt        = 0ns
    PCI Int Pin    = INT A
    Interrupt line = 10
    CPU Interrupt  = ah
    Class          = Communication (Other)
    Vendor ID      = 1093h, National Instruments
    Device ID      = 70deh, Unknown Unknown
    PCI index      = 0h
    Class Codes    = 078000h
    Revision ID    = 0h
    Bus number     = 20
    Device number  = 14
    Function num   = 0
    Status Reg     = 280h
    Command Reg    = 117h
    Header type    = 0h Single-function
    BIST           = 0h Build-in-self-test not supported
    Latency Timer  = 20h
    Cache Line Size= 10h un-cacheable
    PCI Mem Address = f6407000h 32bit length 4096 enabled   //PXI-8431
    Subsystem Vendor ID = 1093h
    Subsystem ID        = 70deh
    Max Lat        = 0ns
    Min Gnt        = 0ns
    PCI Int Pin    = INT A
    Interrupt line = 10
    CPU Interrupt  = ah
    Is there any problem?
    Because there is only one Mem Address in QNX system, the interface function acquireBoard() will be  returned by Error: bar1 map: invalid argument.
    Therefore, it can not be initialled in QNX system.

    Maybe it just gets two memory card.

  • Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?

    Colleagues,
    Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?
    Which will be the maximum transfer rate for continuous data recording?
    Thank you,
    Sergey
    Sergey

    Sergey,
    The PXI-8210 can connect to any SCSI 2 compliant device. If the RAID controller is SCSI 2 and appears just like a hard drive in the operating system, then you can send data directly to the RAID array. The problem is that the driver for the PXI-5112 does not yet support continuous acquisition. The on-board 16MB or 32MB buffer stores the data until the entire acquisition is completed. Once the acquisition complete, all of the data is transferred from the on-board buffer to the hard drive. After that happens, the NI 5112 is ready for another acquisition.
    Best Regards,
    Jace Curtis
    NI Applications Engineering

  • DMA Bus-Mastering

    Hi, first, sorry about my english...well i just run sandra2004, because i see a kind of problem but i m not sure what should be...well all is fine, but, my hard drive ( Maxtor 40 Gb 7200 rpm, ata 133 ) has a 3418 Kb/s transfer...this is a shame, but sandra tell me that i have a  problem with DMA Bus-mastering.
    How can i fix this problem????
    My system:
    Barton 2500+
    K7N2-L ( Delta )
    Maxtor ATA 133 40Gb 7200
    2 x 256 Mb DDR Dual Channel ( Samsung )
    Gforce 4 MX 440 64 Mb DDR 4x ( MSI )

    Google for ATTO, download, install and run. You'll get very accurate results. Sandra lies quite frequently.

  • Problem: KT3 Ultra, Maxtor HD, and PCI Bus Mastering

    Hello, and thanks for taking the time to read this plea for help.  I have a KT3 Ultra motherboard with an AMD Athlon XP 1800+ processor and a Maxtor D740X (MAXTOR 6L080J4) 80 GB hard drive that I purchased back in March and originally used on my old computer with no difficulty.
    Unfortunately, on my KT3 Ultra, if I enable PCI Bus Mastering in the BIOS, the system refuses to boot from the hard drive.  It boots fine if PCI Bus Mastering is turned off, but I strongly suspect that I am not getting full UDMA-class throughput with PCI Bus Mastering turned off, which I desperately need because I want to do video capturing with my ATI All-In-Wonder Radeon card.  Also, the HD LED does not light up disk activity on that hard disk.  I know that the HD LED works and is hooked up correctly because it lights up to show activity on a hard disk I have installed on the second IDE channel.  I have tried hooking the 80 GB drive to the IDE RAID ports, but the system hangs in the IDE RAID BIOS and will not boot.
    This week, I also tried backing up, wiping the HD clean, and running the PowerMax diagnostic programs, all of which said the HD was operating perfectly.
    With PCI Bus Mastering on, I am able to boot from a CD ROM and at least get into my Linux system, but I can't boot into Windoze 98 that way.
    I am using the LILO boot loader, but I have also wiped it off with "fdisk /mbr" and tried to boot with PCI Bus Mastering turned on -- no dice there either.
    I've fiddled with every relevant BIOS setting and searched in vain for an answer.  Something tells me that the UDMA interface on the hard drive may be defective -- the hard drive was an open box special.
    Any help that anyone can provide would be very much appreciated.
    Thanks,
    Will Snyder

    Hi,
    I have KT3 Ultra ARU and Maxtor D740x 60GB too. I have no problem enabling PCI IDE BusMaster. You have done pretty good troubleshooting there and I'm on your back to say it's the harddisk's fault.
    Have you tried other hard drive? Have you tried with other IDE cables?
    fyi, UDMA is still enabled without PCI IDE busmaster. But I would suggest you to go claim for a hdd swap instead.

  • How to Progrmatic​ally reinitiali​ze a PXI bus

    Our application is to develop a functional test fixture for one of our production boards that is usually installed in the NI PXI-1042 chassis with the PXI-8196 embedded controller running XP pro.
    We are using  a Chroma ATE 52906 extender card to test our UUT so we can access the board during test. The 52906 extender card allows us to turn off power to the UUT, replace the UUT, then turn power back on without rebooting the host computer(PXI-8196 ) which saves us considerable test time.
    We use the following process to change UUT's
    1. Go into Device Manager, look under Other Devices and select the UUT (shows up as: PCX Custom (OEM) PCI 9656 Board), then select Action --> Uninstall.
    2. Turn off the 52906 extender card and replace the UUT.
    3. Turn on the 52906 extender card and wait for the UUT to boot up.
    4. Go into Device Manager, select the computer icon at the top of the device tree, then select Action --> Scan for Hardware Changes.
    5. The Found New Hardware Wizard will open. Follow the steps and allow the wizard to automatically search for and install the driver.
    6. The UUT is ready for test.
    My goal is to accomplish steps 1, 4 and 5 programatically using LabVIEW.
    Any Ideas
    Thanks,
    Joe.
    "NOTHING IS EVER EASY"

    We are not disabling the bus, we are just wanting to do a scan for new hardware so that it will Re-initialize the bus so that we can talk to our board. We use the generic windows driver for communication and it does not recognize that it has new hardware until we tell windows to scan for new hardware. Does anyone know of a dll or windows API that will do this.
    Thanks,
    Joe.
    "NOTHING IS EVER EASY"

  • Why does it take so long to clear a task (with DMA transfer) using the PXI bus?

    I am migrating a system which used to use a PCI-6133 (8 channel simultaneous AI) and PCI-6733 (8 channel AO) to one that uses a PXI-6133 and PXI-6733 mounted in a PXI-1033 chassis.
    In general, things seem to work (synchronized AI/AO running near the maximum rate on both devices), with the one exception that clearing an AO task on the PXI-6733 takes forever (on the order of 20-30 seconds).
    Even when I try the sinewave generation for the PXI-6733 in the MAX test panel it takes the same amount of time to stop the task. If I switch to using interrupts as the transfer mechanism, it stops immediately.
    I tried using the interrupt transfer mechanism on my more demanding set of synchronized tasks, but that does not produce the right behavior (even though it does not give any errors).
    Is there any trick (or better diagnostic) to help get my tasks working with DMA under PXI that used to work fine on PCI?
    Thanks in advance!
    Solved!
    Go to Solution.

    Hi Patrick,
    I'm using a PCIe-8361 controller. The computer is a Dell T5500 workstation running Windows 7 x64. I see the problem every single time I try to clear a task running on the PXI-6733, including my example using the Measurement & Automation test panel (from the very first time I try the Sinewave Generation onward). I can try other parameters in the test panel, but I don't need to adjust anything from the defaults (e.g., Rate = 1000) to get the behavior. I will also try installing the PXI chassis in a few other computers we have here just to confirm that it's not computer specific. From your line of questions I can at least gather that there's nothing obvious (like a known bug with the PXI-6733) and that I should expect this configuration to work.
    Thanks for your help and I'll post any other findings I obtain.

  • PXI/MXI bus monitor for data transfer

    Hi,
    I want to monitor the data transfer in a MXI/PXI bus. Is there any tool for that? else, can we write our own tool using some APIs?
    Kindly let me know.
    Regards,
    Priya.

    I am not aware of any such tools available with NI
    Here are some places where you will find info on PXI architecture if that will help you :
    http://forums.ni.com/ni/board/message?board.id=270&message.id=694&requireLogin=False
    http://zone.ni.com/devzone/cda/tut/p/id/2722
    http://zone.ni.com/devzone/cda/tut/p/id/3886
    http://zone.ni.com/devzone/cda/tut/p/id/3221

  • Pxi ethernet streaming

    hi
    i want to know if anyone has experimented with streaming using ethernet on a PXI(e) platform? i want to stream from a 100 Msps PXI digitizer to a non-pxi PC?
    what are the issues at hand...?
    currently my system is windows XP, ethernet gigabit on a host controller... i have also looked at PXI 8234..although for vision applications...could it be used...although i will have to get it..donot have it right now...
    can anyone explain to me as well, how the data is routed from host digitizer such as 5122 - PXIe bus-controller-ethernet...etc
    it would be a great help
    thanx

    Hey Dannn,
    Streaming data via ethernet is realatively straightforward.  On your non-PXI chassis, are you running Labview there? The starting point is to check out the data server-client example that is available with the Labview distribution.  If you are looking for high performance, Simple TCP-IP Messaging (STM) API that has been developed by NI.  This API abstracts some of the basic tasks that you will always be doing but not to the point of Shared Variables (which seem to have a lot of issues).
    I can't think of any gotchas that you have to look out for.
    Hope this helps.
    Matt
    Matt Richardson
    Certified LabVIEW Developer
    MSR Consulting, LLC

  • ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

    Hello forum members!
    we recently purchased  a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
    I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
    basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
    First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
    Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
    is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my  timing controller working or the chassis installed?
    We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
    PXIe-3985 ADLINK PXIe Embedded controller
    NI PXIe-1062Q PXIe chassis
    NI PXIe-6672 Timing Module
    And in case if there is an update or workaround which solves the issue.
    The system has Win7 32bit installed.
    Many thanks to every answering user

    Hi emanuele83,
    which version of PXI Platform Service do you use?
    Can you please upgrade to a current version?
    Here is a download link:
    PXI Platform Services 14.1 - National Instruments
    http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
    This may solve the issue.
    Best regards,
    Andi

  • Pushing the limits of continuous high-speed DAQ + processing, with PXI-6115 + PXI-8360

    Hi all,
    I'm trying to do continuous high-speed data acquisition + processing. I currently have:
    Chassis: PXI-1042Q
    AI card: PXI-6115 (x2)
    Link: PXI-8360
    PC CPU: Intel Xeon W3503 (dual-core, 2.40 GHz)
    RAM: 4 GB
    The idea is to continuously grab 8 channels' worth of analog inputs, scan for "events", and if found, log the events to disk.
    My client would like to use the maximum sample rate of 10 MHz, but I found that above 5 MHz, DAQmx Read.vi can no longer keep up (e.g. at 6 MHz, it takes 110 ms to read 100 ms' worth of data).
    Im thinking of getting beefier components, but I'm not sure where the bottleneck is. Here are some thoughts:
    1) The MXI Express link
    The PXI-8360 is rated for a sustained throughput of 100 MB/s.
    I'm not sure how big the data is. PXI-6115's ADC is 12-bit. Does that mean each datum transferred through the MXI cable is 1.5 bytes? Is the data padded? Or is it 8 bytes per datum, because Dbls are being transferred?
    2) The CPU
    In Resource Monitor, I notice that the CPU usage is 0% at 60 kHz, 8% at 61 kHz, and 50% at 70 kHz (meaning that one core is maxed out). I'm surprised that it keeps up all the way until 5 MHz though.
    What causes this high CPU usage? Is it due to the conversion of the data into 1D array of waveforms?
    3) Something else?
    Have I missed something completely? Is what I'm describing even possible?
    Thanks in advance for any advice!

    Hello,
    Each sample will take up 2 bytes, 12 bits data + 4 empty bits. so the PXI-PCI 8360 is only able to transfer a maximum of 50S/s in this case.
    Also, because the PXI bus is shared among all of the cards, two PXI 6115 cards will be trying to transfer 80MS/s or 160MB/s.
    Finally, since the PXI 6115 are DAQ family cards, their specifications aren't really written for continuous data acquisition at the upper end of their sample rate, but I'm interested to know if you can get up to 10MS/s with only one card operating at a time?
    -Jim B
    Applications Engineer, National Instruments
    CLD, CTD

  • Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

    I have a PXI-1042 with PXI-MXI-3 interface kit. In the chassis I have inserted an OEM PXI module. When I run MAX, all I see is PXI System->PXI Bus 0->PXI0::MEMACC. Is this correct? How do I see the other modules?

    Darren,
    The only PXI modules that show up under the PXI System option in MAX are those cards that are registered with NI-PAL or NI-VISA. For 3rd party cards, it depends on how their particular driver functions. If the vendor creates their drivers based on NI-VISA, then the device will show up in MAX.
    If the vendor created a Windows-specific driver, then there is no way that NI-VISA can find any information on the device, nor can it communicate with it. An example of this is a CompactPCI SCSI or Ethernet card, which is supported by a driver that is native to Windows. NI-VISA does not detect such devices.
    It is important that you contact the manufacturer of your 3rd party modules and find out if they are NI-VISA complient devices.
    Regards,
    Andrew Mier
    au
    Applications Engineer
    National Instruments

  • NI5112/5122 digitizers performances in a pxi system

    I�ve to configure a PXI based signal processing system, composed of:
    -PXI chassis + 8186 Controller,
    -N.2 NI5112 8-bit digitizers (or N.2 NI5122 14-bit digitzers).
    I want to configure a four channels acquisition system, performing a continuous data acquisition in Labview environment, and I need of some confirmations about transfer rate limitations.
    I�d like to know the theoretical maximum (continuous) transfer rate between the four channels and the controller (with 8-bit 5112 configuration or with 14-bit 5122 one).
    For simplicity we can think that without data storage and processing.
    I know that the PXI bus performs a rate of 133 Mbytes/sec, so in a configuration of N.4 acquisition channels, we obtain 133/
    4 = 33 Mbytes/sec for every channel.
    This is simply 33 Msample/sec in a 8-bit NI5112 configuration, while becomes 33/2 = 16.5 Msample/sec in a 14-bit NI5122 one.
    Is that right?
    Are there other bottle necks (related to the acquisition cards or to the controller)?
    Thank you in advance.

    Hi
    yes your calculation is right even if these are pure theoretical values becouse they would depend on your PC performance and other data traffic present on the PCI bus due to other boards (like video, ethernet etc.).
    Between the two options the 5122 will be better for a longer time frame acquisition due to the higher onboard memory that will offer a maximum of 256MByte/Ch instead of 32MByte/Ch (128Msample 14 bit/Ch vs 32Msample 8 bit/Ch) and also for the SMC architecture that will offer advanced timing & synchronization features even if the higher resolution (14bits) will decrease the potential transfer rate in a continuos acquisition.
    If you want to learn more about the SMC architecture and its advantages you can look the link here attached.
    http://zone.
    ni.com/devzone/conceptd.nsf/webmain/63CA1E64DA2AAA3486256DE90003F124?opendocument
    Hope this help
    Luigi

  • Bus master with MXI-2 stops Windows XP clock

    We are experiencing an issue with our MXI-2 modules in our VXI test systems. We recently implemented a module that has bus master capabilities. Up until now, all of our modules have been slaves. We have noticed that when our module requests the bus, we get a bus grant from the MXI-2 slot 0 controller and we can perform our register reads and writes to our other slave modules, we release the bus and everything looks good. However, we have noticed that our PC system real-time clock is losing time when we do this. It appears as long as we request the bus, the OS stops servicing real-time clock interrupts. In fact, if we request the bus for more than about 5 seconds, our PCs will reboot which is really strange. We are running Windows XP for an operating system. Has anyone else run in to this issue before? Any help/advice you could lend us would be appreciated.

    I am going to jump in here.
    >Thanks for clarify, do your programmers
    have the “Date and Time Properties” window open to do this? When the
    clock is no longer updating, is the rest of windows >responsive? Can you
    have other programs running in the background?
    Yes we can have the "Date and Time Properties" window open but it
    really does not matter, the entire windows box is frozen, nothing works,
    not even the mouse.  Later on, the windows box will come back to life
    as if nothing has happened -- except the clock will be wrong, compared
    to the clock on the wall.
    >To get some more information about your system: What all
    hardware are you using? Specifically, what is this module with bus
    master capabilities?
    Various off the shelf PC's (Mostly Dell's)  Windows XP, automatic updates.  The VXI module with the bus master capabilities is an
    in house design.
    >What
    version of NI >VXI and NI VISA are you using?
      We think we have the very latest drivers, but that does not really
    matter as we have seen this problem occur no matter what the driver
    versions.  The latest drivers we have installed on the test machine are VXI 360 and (NIVXI360.EXE) and Visa 4.6
    (visa460full.exe).
    Problem occures on _ALL_ driver versions, both the MXI-2 and also the new MXI (PCI-Express version)
    >And just so there is no confusion in the lingo,
    specifically what “bus
    master capabilities” does this device have?
    Please explain.
     >Also, can you
    >elaborate on
    what you mean by “bus grant”.
     VXI bus grant signal.  (given after the module requests the VXI bus)
    >Additionally
    please describe how you have you VXI system Architected. A host computer
    running XP, MXI-2 connection to a VXI chassis with assorted modules is
    >pretty basic, please elaborate how your system differs, a picture may be
    helpful. Did you change the “hardware configuration” in MAX on your
    controller?
    No nothing has been changed.  Everything should be at default values -- do we need to change them ?
    >Also, please elaborate on your
    Application environment and what function calls you are using to
    accomplish this. Posting your code would be beneficial here as well.  Code is pretty simple, will post again if necessary.
    Ok, I am going to speculate here, but perhaps the NI VXI drivers have interrupts disabled or the MXI hardware is causing an interrupt storm ? -- not sure how else to freeze the processor on the PC side of the MXI interface.
    The problem (maybe?) can be boiled down to the following:
      1) A board in the VXI chassis starts to do bus mastering
      2) Software running on the PC with the MXI interface deceides to call a "viIn" function in the NI visa library (and the VXI bus is busy)
      3) The PC becomes "frozen" until the bus mastering is over (sometimes it spontaneously re-boots)
      4) The PC comes back to life, but was "frozen in time" so the clock is wrong compared with the wall clock, sometimes up to 
           10 minutes out of 20 and also lost the ability to do other useful work while it was frozen.
    Thanks

  • What is the best way to Query for a PXI Chassis in TestStand

    Hi All,
    I have some benches that have a PXI Chassis and others without. 
    I would like to Query for the Chassis and if it isn't there I will use another method of testing.
    Is there a way to query for the chassis and if there is how?
    Thanks
    Message Edited by glennjammin on 10-09-2009 09:23 AM
    Test Engineer
    L-3 Communications
    Solved!
    Go to Solution.

    Hi,
    You could use the VISA Find Resource function. If you get back PXI[bus]::device[::function][::INSTR] or PXI[interface]::[bus-]device[.function][::INSTR] then you have a PXI chassis
    regards
    Ray Farmer
    Regards
    Ray Farmer

Maybe you are looking for