Routage PCI/PXI

Bonjour,
Je travaille actuellement avec deux cartes (NI PXI-6683H et NI PXIe-6672) dans le châssis (NI PXIe-1082) et j'aimerai mieux comprendre comment communique les cartes entre elles.
Dans le but de m'exercer, j'ai connecté le port PFI0 d'une carte au port PFI0 de l'autre via la fonction labview "DAQmx Connect Terminals.vi" :
Jusque là, tout va bien, la connexion s'est bien produite et le signal en PFI0 va bien jusqu'au second.
Cependant, où passe l'information ? Via la connexion PXI_TRIG ? (Il semblerait que non puisque j'ai tenté de déconnecter Le port PFI0 des TRIGS <0;7> et le signal passe toujours..)
Via l'interface PCI alors ? Si oui, avez vous un schéma explicatif, permettant d'interagir avec celle ci, car MAX ne m'indique pas d'autre chemin depuis le périférique PXI-6683H. 
Attachments:
ni PXIe-6672.PNG ‏64 KB
ni PXI-6683H.PNG ‏59 KB

jallen_100,
The MXI-3 Cabling Options FAQ knowledgebase article may have some of the information that you are looking for. Here are two of the sections that I hope you find useful:
Please note that National Instruments does not produce any type of bulkhead connector for MXI-3, because they might produce unacceptably high error rates that would degrade MXI-3 performance. Due to the proprietary design of MXI-3, it is highly recommended that it not be installed in permanent structures using feedthrough panels and bulkhead connectors. These types of connection solutions(bulkhead, feedthrough panels, etc.) have not been tested by National Instruments and we cannot guarantee performance or compatibility.
With that said, for the copper MXI-3 cable, the cable and connector type is called HSSDC (High Speed Serial Data Connector). This specific connector was produced by AMP, part number 1324640-2.
I hope this helps,
Eric K
Applications Engineering
National Instruments

Similar Messages

  • How to test the PCI/PXI 4461

    when i receive a new card, how to test it?
    when i click the "self-test" in the Measurement & Automation Explorer,it shows that "the device has passed the self-test."
    is that means the card is ok?
    or i should make other test to confirm?what test should i do?

    You can also use the test panels in MAX to test each channel of input or output after they are terminated. This is a good verification that your signal conditioning, wiring, etc is working as expected before getting LV involved.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Where can I find camera file for TM-6702(pulnix) for pci/pxi-1409?

    Thanks!

    You should be able to use the 60Hz progressive scan camera file.
    If this does not work you may want to reffer to this Application Note for more information about working with nonstandard video types.
    Hope this helps.
    Amaury
    NI Applications Engineer

  • HELP! I need to be able to remove power from a PXI chassis and replace a card without rebooting the whole system

    I do not have particulars on the controller, but I am sure it's an NI chassis
    and NI regular controller that has a serial cable leading back to the PC.
    I am making this PXI rack into a debug rack for instrument cards,
    so I need to be able to remove power from just the PXI chassis
    and then replace the card with another one
    or the same one and then turn the power back on and restart a
    diagnostic test on the card WITHOUT
    having to reboot the PC.
    Is there a PCIe bridge setup that would allow me to do this?
    Is there software that I need that can accomplish this?

    Yes
    The Chassi is a NI PXI 1045
    and the controller is a NI-PXI-8331
    Let me re-enumerate my requirements:
    Background:
    I have a number of NI cards as well as other manufactured cards in the system.
    One of these cards in the NI system is considered to be a UUT.
    That is, I am using the NI card cage system and other cards in the system to test a CARD
    during a manufacturing test of said UUT CARD.
    The UUT uses a PLX 9030 for it's PCI interfacing.
    This UUT is not designed for hot swap, and I do not bieleve it is plug and play.
    Requirement:
    1. I need to be able to shut off the chassis and remove the UUT when the test finishes, replace the tested UUT
    with a unknown UUT, re-apply power and then test the new UUT WITHOUT having to reboot the PC.
    I have tried several things, such as disabling the PCIe busses in the windows control panel, and then removing power
    replacing the UUT with the next one, re-applying chassis power and then re-enabling the bus and SOMETIMES it works.
    I need a very robust way to do this.
    I also bought a CHROMA PXI-52906-E extender card with bus switches on it, so that I can remove power to the UUT
    without shutting off the chassis. The card is supposedley designed so that when power is re-applied to the UUT, the necessary
    signals to boot the PXI PCI interface is conducted, but I think something else has to be written to the card's PCI registers.
    I am by no means an expert in PCI/PXI, 
    but I seem to have exhausted all of my reserach online in how to meet my requirements.
    Perhaps there is a way for the NI8331 controller to capture PCI configuration data to the card's on system boot,
    and then "replay it" to my UUT after I re-apply power to the UUT?
    Or perhaps PLX makes such a tool?
    Any ideas?

  • How to get PXI 5152 working in LabVIEW 7.0

    Hi,..I recently purchased a PXI 5152 digitiser. The driver CD had NI Scope 3.4 which, when installed worked fine. But it also installed NI DAQ MX 8.5 (min. requirement) and removed my older version of DAQMx.. This new version DAQMx 8.5 does not support LV7.0. (My APE is LabVIEW 7.0.) So I can't get any DAQMx I/0 blocks from LabVIEW.
    When I uninstalled DAQMx 8.5, NI Scope 3.4 also got removed. Then I rolled back to my old config of DAQ and Scope 2.5. But now my digitiser is not recognised.
    Where can I get a 5152 digitiser driver(NI SCOPE) that works for LV7.0 also.(I was unable to find one from NI website. They all needed LV7.1 or later)
    I am using a PXi system with PXI - 8175 controller.

    Hi,
    Sorry I did not realize you had a PXI-5152 and like it was posted by one of my co-workers the PXI-5152 will only be supported on NI-Scope 3.2 or later.  The NI-Scope 3.2 requires LabVIEW 7.1 or later.  In this case you options are like Sam said upgrading LabVIEW or getting a new digitizer.
    From the list you posted on the previous thread you should be looking at: LabVIEW 8.5 Compatibility Information. For your timing and your DAQ device we can check the driver in this website: NI-DAQ Driver Support: PCI/PXI Devices .
    Now for the PXI-8175 we need to take a look at the minimum requirements for LabVIEW 8.5 and the best place to search for this data would be here: Release Notes.
    I hope it helps
    Jaime Hoffiz
    National Instruments
    Product Expert
    Digital Multimeters and LCR Meters

  • Counter output PCI 6229

    Hi all, 
    i have a little problem with NI pci 6229. I want generate a pulse train on both counter CTR 0 and CTR 1. I look the example that run on machine but i dont find the pin , with the oscilloscope, with y train pulse. I check the between Dgnd and PFI 8 ( pin2 ) but i dont see a train. 
    How can i solve ? What is the correct pin couter out on NI PCI 6229 ? it is referred to Dgnd? 
    tanks

    Hi,
    the terminal for a counter output task is PFI12 and not PFI8. The PFI 12 has the default Pin number 2.
    NI PCI/PXI-6229
    http://zone.ni.com/reference/en-XX/help/370466W-01/device_pinouts/6229_pinout/
    Have a nice day.
    Regards,
    A.

  • Issue with PXI 6528 test panels

    We are using a real time 8106 controller in a PXI rack with some 6528 digital I/O boards. We have loaded all necessary drivers to the system and can see the cards in Max but are unable to run Test panels as the options to set the port bit states are greyed out. Has anyone had experience of this ?
    Thanks
    Peter Heseltine

    Hi Peter,
    The NI PCI/PXI-6528 device provides 24 isolated input channels and 24 isolated output channels that are not bidirectional. Are you getting the same behavior on ports 3-5.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Register level programming for PCI 6733

    The information provided online for RLP with PCI-6733 is very limited. Only the register map for PCI-6713 is provided @ http://www.ni.com/pdf/daq/us/release_ni67xx.pdf.
    However, how the board maps its resources on the PCI bus is not clear. So could you please provide the following information
    1. What the manual means by "Base Address" and "Window Address".
    2. What is mapped by each of the boards BARs (Base Address Registers).
    3. The difference of registers between PCI-6713 and PCI-6733.
    If possible, could you please provide a detailed reference for this Analog Output board as for other boards, such as PCI-DIO-96.

    Maybe you don't need the MITE manual after all. My documentation (from 2003) lists only the "DAQ-STC Technical Reference Manual - Part Number 340934B-01" and "PCI/PXI 671x/673x Register Map". I don't know where I got the information about the MITE -- one comment in my code suggests comedi.org, while another one mentions I started rewriting the code to get rid of the comedi stuff (so there must be information available from somewhere else, probably extracted from the DDK).
    IIRC the MITE is only used once, for initialization.
    I'm sorry I can't provice any code, but the driver I wrote is not openly available. 
    Warning: Some of the DAQ-STC information was wrong in the version I used, I had to use trial & error for some of the funtionality.
    Check out: 
    http://digital.ni.com/manuals.nsf/websearch/E929838D7D0EE50986256728007FEADF?OpenDocument&node=132100_US 
    http://digital.ni.com/public.nsf/websearch/15f094f65a17e3af8625660d0018a20a?opendocument
    Message Edited by Thorsten Jens on 08-22-2008 08:17 AM
    Message Edited by Thorsten Jens on 08-22-2008 08:22 AM

  • PXI-8195 won't boot after installing LV RT 7.1.1

    Dear all,
    I just installed LV RT 7.1.1 on my RT Target.
    Unfortunately after doing so I am no longer able to boot the Target.
    It just stops after BIOS POST with a blinking cursor in the first line on the connected screen.
    Changing to SaveMode in BIOS allows me to boot into save mode and to connect with the target through MAX
    The following software is installed on the target:
    - DataSocket for LV RT 4.2
    - Intel 8254x Ethernet Driver 1.1.1.3.0
    - LV RT 7.1.1
    In another post I found that one is required to install NI-VISA and VISA Server. Is this correct?
    I tried to do so but I am prompted with pending dependencies to NIINI 2.6. GREAT!!!
    Next step will be to download an VISA update hoping to get rid of those dependencies?
    Any input is appeciated.
    Grüße
    Phili

    Hi Phili,
    which type of controller do you use? Does the system really has an 8254x Ethernet Chip
    onboard or an additonal PCI/PXI-Board with this Chipset?
    If you have no important software on the controller left (can be saved via FTP), you can
    try to format the RT-Target in safe-mode by right-clicking in MAX ...
    Regards, Thomas.

  • Program identifies the pxi chassis

    I have a utility in Lab Windows CVI 2012 that runs on a PC, PXI or PXIe. I would like the program to be able to identify which of these it is running on.
    Right now we have a read of a device in the PXI chassis, just initialize a switch card, if it is successful, we have the PXI or the PXIe. My concern is if that one card is not present, also this results in a run time error if the card is not there, or if it is a PC.
    I would really like something to read directly from the PXi, a serial or device number or something. Sort of like we have in our code to read the type of CAN device, first we get the CAN device number, then the device type:
    /* find "can_num" for NI CAN device (just not USB) */
    Status = ncGetHardwareInfo(can_num, 1, NC_ATTR_HW_FORMFACTOR, 4, port_check);
    /* use "can_num" from PCI, PXI, or PCMCIA Device to get port number */
    Status = ncGetHardwareInfo(can_num, 1, NC_ATTR_INTERFACE_NUM, 4, port_check);
    Is there any such function to read the PXI chassis?

    Hi Ken-this-..., 
    I think what you want is DAQmxGetDeviceAttribute().  Here is a link to a similar post:
    http://forums.ni.com/t5/LabWindows-CVI/How-to-detect-PXI-chassis-cards-and-their-serial-numbers-in-C...
    Peter T
    Applications Engineer
    National Instruments

  • PCIe 6320 et labview 7.1

    Bonjour,
    Voila j'ai une application a développer pour un client avec une carte PCIe 6320 la version du DaqMX fourni avec la carte est la 9.1.7. Seulement le client m'a fourni une version de labview en 7.1 D :
    La version DaqMX 9.1.7 est compatible avec la carte mais pas avec Labview 7.1.
    J'ai installé une version DaqMx 8.6 celle ci est compatible avec lavbiew 7.1 mais avec la carte (impossible de l'installer).
    Comment faire ?
    Y a t'il une version DaqMX compatible avec la carte PCIe6320 et Labview 7.1.
    Cordialement
    Johan CAILLET

    Bonjour,
    Merci d'avoir posté sur le forum NI.
    Malheureusement,  pour utiliser la carte PCIe 6320, une version  de labVIEW 8.5 ou postérieur est nécessaire.
    Veuillez trouver ci-dessous quelques liens susceptibles de vous intéresser :
    NI-DAQ and LabVIEW Version Compatibility (for Windows)
    NI-DAQmx and NI-DAQ Driver Support: PCI/PXI Devices
    Cordialement Samuel G.
    Samuel G. | Application Engineer Team Leader
    Certified LabVIEW Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Été de LabVIEW 2014
    12 présentations en ligne, du 30 juin au 18 juillet

  • PXI-8320 MXI-2 software/h​ardware install problems.

    Attempting to install a PXI-8320 MXI-2 bridge. My PXI chassis is connected to a PC via a PCI-PXI MXI-3 bridge. I have just received a new PC running Windows XP with Labview 7.1. I cannot find the MXI-2 interface in Measurement Explorer. I do get a find new hardware for the PXI board, but it cannot install a driver. As far as I know, all of the appropriate software was pre-installed. I am stumped. Any help would be appreciated.

    Have you installed NI-VXI? The MXI-2 interface requires our VXI driver, NI-VXI, which is not automatically installed with LabVIEW. The latest version is available on our web site at http://www.ni.com/support/vxi/drivers.htm.

  • Error initializing a PXI 6602

    Hello,
    In a PC runnig RedHat Linux I have a PXI 6602 inserted in a PCI slot using a PCI-PXI adapter. Lspci reports the following message for this board: "!!! Unknown header type 7f". Does somebody know if this means that the board is defect ?
    Thanks

    What kind of PCI-PXI adapter are you using?
    Is there any way you can try this in an actual PXI slot? Try another machine with the same adapter?
    What specific distribution of RedHad are you using?
    Peter Flores
    Applications Engineer

  • Unreliable access to PXI boards

    I am using a PXI-1033 chassis with PXI-5405, PXI-6541, and PXI-5105 connected to a PC via PCI-PXI 8331 MXI.  The first time I loaded the drivers and software, then turned off the PC (Windows 7), then I switched on the PXI-1033 and all of the boards were identified and access LEDs turned on.  Several days later, when switching on the PXI-1033, the chassis powered on successfully and was linked, but the PXI boards' access LEDs never turned on.  I tried several times switching on and off in different orders with no success.  Each time, the devices showed up in device manager, so I tried re-installing the drivers.  That day the devices worked correctly again.  But now, 1 week later, the access LEDs do not turn on!
    I need a solution that doesn't require reinstalling all drivers everytime I want to use the devices.
    Thanks!

    Hello rpfrancis,
    When the access lights on your modules are not turning on, do the cards themselves still function (can you get input/output from them)?  Do the devices still show up in MAX?  You are correct in turning on the PXI-1033 chassis first.  You will always need to boot the chassis first, then the PC.
    Also, have you taken a look at the troubleshooting section of one of your module's user manual?  There is a section about access LEDs not turning on that gives steps to try to fix the issue.  It sounds like you may have already done a couple of the steps, but I recommend trying the each step in the manual.  Let me know!
    Regards,
    Joe S. 

  • Using PCI resource via NI-VISA server

    I need to use a PCI resource (NI 6221) installed on a server from a client via NI-VISA server.
    I use this system with GPIB and TCP/IP resources: all resources connected on the "server" are accessible.
    Is-it a NI-VISA server limitation?

    Hello,
    You might be able to use your PCI DAQ board with NI-Visa. At least you should be able to get your VISA resource name from your DAQmx board.
    Here are some links on our website which may help :
    http://digital.ni.com/public.nsf/allkb/1321A882CB5​75512862572D400602EDB?OpenDocument (Programmatically Get VISA Resource Name of PXI DAQ Card Using DAQmx)
    http://decibel.ni.com/content/docs/DOC-5344 (Search VISA resources to find Custom Aliases)
    Just to remind you that NI is not recommending to access your DAQ boards this way.
    Other related links :
    http://digital.ni.com/public.nsf/allkb/9C4E9FD0C74​69BC286256F100074EADC?OpenDocument (How Do I Use NI-DAQmx Base with PCI/PXI Devices on Windows?)
    http://zone.ni.com/devzone/cda/tut/p/id/4713 (Using the VISA Driver Development Wizard and NI-VISA to Develop a PXI/PCI Driver in Windows)
    Regards,
    Yannick D.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Du 30 juin au 25 août, embarquez pour 2 mois de vidéo-t'chat ! Prenez place pour un voyage au coe...

Maybe you are looking for