PXI 2515 Bus to Dut Connection

Hi all,
I'm trying to make a connection from an SMU through the PXI 2515 to an IC pin to do a continuity test (protection diodes), I've already confirmed their presence on benchtop equipment.
I'm using the "niSwitch Making Connections on a Switch" VI which I modified; everything seems to work just fine when making a connection from busa or busb to dutctrl5, dutctrl4, dutctrl1, and dut31 through dut26. Please refer to the following diagram: http://zone.ni.com/reference/en-XX/help/375472A-01/switch/2515_independent/#MakingAConnection
However, if I try to make a connection to any other dut#, it seems as if the switch is not closing.
From the diagram, I'm assuming that channel 1 on the "niSwitch Connect Channels" VI should be "busaiso0" and channel 2 should be "dut25" to make a connection; I get no errors but I can tell that the switch is not closing, because I reach the compliance limit that I have defined.
Are you supposed to somehow close the switch between "busa" and "busaiso0"? Do I need to include "niSwitch Controlling an Individual Relay" VI somewhere do do that?. Thanks for any suggestions/or help.
Juan
Solved!
Go to Solution.

Hi Juan,
When I tried to make a connection from busa to dut25 I did get an error that that path does not exist.  Based on the Hardware Diagram we actually have to make separate connections between the busa and the other buses on the PXI 2515.  If you make the busa -> busaiso0 connection at the same time you make the busaiso0 -> dut25 connections then busa should be connected to dut25 without error.  
The same strategy can be used to go further up the bus.  For example, to connect busa to dut0 you would have to make the following connections:
busa -> busaiso0; 
busaiso0 -> busaiso1; 
busaiso1 -> busaiso2; 
busaiso2 -> dut0;
I hope this is helpful!
Andy K.
Applications Engineer
National Instruments

Similar Messages

  • PXI 2515 to Dut cable connection and proper connection to GND

    Hi all,
    I am interfacing a testing board (DIB) to pxi-2515 switch. The switch will connect PXI-4130 SMU & PXI-6552 to the DUT  in order to characterise multiple tests.
    I  will use 68-Pin VHDCI connector on my board to connect to 2515 via NI SCH68-C68-D4 cable. I won't be using all the dut channels. Based on the pin diagram http://zone.ni.com/reference/en-XX/help/375472A-01/switch/2515_independent/#MakingAConnection ; How should I connect GND pins from right connector to my board connector?
    I am a bit confused, Should I connect all of the GND pins to my board's ground? Or can I choose certain GND pins to connect to my board's ground (since I won't be using all dut channels in the 2515--i.e.do certain GND pins have correspondace with certain dut pins?)?
    The left connector in 2515 is connected to PXI-6552 DI/O. Would GND pins in right connector (which connects to DUT) be refrenced to GND through left connector (through the 6552 system ground)? Or should I always connect everything to my DUT system ground?
    I would appreciate any clarification!
    Thanks,
    Sami
    Solved!
    Go to Solution.

    Hi Sami,
    The PXI-2515 will share the ground line between the DUT and the HSDIO card when using the GND lines. All the GND pins share the same physical ground, so it shouldn't matter which pin you use for each channel. Just make sure you have each DUT's ground wired to a GND pin. Typically there are multiple GND pins distributed across the connector simply to allow easy access to the ground from multiple channels without having to connect multiple wires into one ground pin.
    Does that make better sense?
    Hopefully this helps.
    Chris G
    Applications Engineer
    National Instruments

  • Error-200284 for PXI-1010 MXI-3 fiberoptic connection to a PXI-6533.

    In the instruction lab in which I work, we have two types of systems:
    1)SCXI-1000 chassis connected by copper to a PXI-6035E card in a PC.
    2)PXI-1010 chassis connected by fiberoptic from a MXI-3 to a PXI-6030E card in a PC.  A PXI-6533 handles the digital I/O.
    We have LabVIEW8.5.1 running on both types of systems.  On the SCXI-1000 system, the LabView example Acq&GraphVoltage-IntClk-DigStart.vi runs just fine.  It does not run on the PXI-1010 systems.  Instead, I eventually get Error-200284.  In both cases we use PFI0 or PFI1, and digital ground, for the triggers, connected to lines 38, 39, and 33, respectively, in the SCXI-1302 terminal block, which connects to an SCXI-1180 feedthrough panel.
    I searched the forums and all ni.com for information on this problem, and have not been able to find any relevant information.
    Joseph D. Rudmin

    Hi Joseph,
    I think I'm starting to understand the problem you are having. Unfortunately, since on a SCXI module, all channels are generally multiplexed through AI0, the PXI/SCXI backplane only shares the necessary channels i.e. one AI channel and any required timing signals. Therefore, even if though you are using the SCXI-1180 module with a SCXI-1349 communicating adapter, you will not be able to access the other channels on your PXI-6030E since there is no physical connections being made to those channels in the backplane. There are 2 solutions around this problem:
    1. You can use an SCXI-1349 cable assembly to connect the front of the PXI-6030E module to the back of the SCXI-1349 adapter. This way the unused pins on the DAQ module can be accessed through the SCXI-1180.
    2. You can decide not to use the SCXI-1180 and simply use a standard 68-pin terminal block with your PXI-6030E and connect your 5V sync pulse to the PFI pins. This will still allow you to sample off of the SCXI-1100 since those channels are connected via the backplane.
    Here's a link to our online KnowledgeBase article which talks about this issue. 
    Can I Connect The SCXI-1180 To An SCXI Module In A PXI-1010 To Use The Additional Analog Input Chann...
    Please let me know if this answers your question.
    S_Hong
    National Instruments
    Applications Engineer

  • PXIe 8108 Rebooting whenever i connected to Max

    Hi,
    Iam Using PXIe 1082 chassis and pxie8108 controller. Pxi system having Dual Mode boot configuration (Windows/Other os boot and Labview RT Boot).If i boot with windows then no problem it is detecting in Max. If i trying to boot in Labview RT, monitor which is connected with Pxi system shows the following message
    Transferring Control to user program
    Can't find suitable device for drive C
    LabVIEW Real - Time Boot Loader
    Build Time: Oct 22 2009 11:01:12
    (C) Copyright 2002 - 2007 National Instruments Corporation
    Error booting hard drive boot program.
    Max system identification name:Ni - PXIe8108-2F12CD1D
    LabVIEW Real-Time Single-Core Kernel found '2' CPU cores.
    Consider installing NI RT Extensions for SMP (Multicore Support) module from MAX
    Initializing network... Link Local IP address assigned.
    Device 1 - MAC address:00:80:2f:12:cd:1d: - 169.254.103.152 (primary)
    System state: No software installed
    if i connect Pxi with other PC MAX then Pxi system is rebooting...
    in above Pxi message it is showing" Error booting hard drive boot program". This is the problem for Pxi Reboot ?
    Can any one help me to solve the issue...
    Vijay

    Hi Vijay,
    I suspect that this issue is because your system does not contain an RT compatible partition for installing LabVIEW RT.
    If your system is configured for dual booting Windows and RT, then you need to have two partitions on your disk, one for Windows (typically NTFS) and a second for LabVIEW RT (either FAT32 or Reliance).
    Since you already have windows on the target, you should first boot into Windows and attempt to create a second FAT32 partition for RT if you have some unpartitioned space available on your disk (depending on the version of Windows, they may require 3rd party tools).  Another option is to freshly install Windows on the disk using the NI-provided OS Recovery media, which has installation options for configuring a disk to support dual-boot Windows and RT.
    As to your original issue as described I have forwarded on your problem internally for further investigation - in general simply lacking a formatted partition should not cause RT safemode to reboot.  In your specific situation, however, it would still be best for you to configure the paritions from within Windows anyway instead of using the tool in MAX to ensure that the Windows partition is correctly preserved.
    Cheers,
    JoshH

  • 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-8331 MXI-4 interface connection error

    I am using the PXI-8331, PCI-8331 MXI-4 to control chassis PXI-1042.  I installed the cards, software and connect chassis to the desktop.  MAX window recognizes the chassis but on the chassis status under General tab, a message of "The MXI- connection to this chassis timed out" appears.  For this reason, I could not see other modules on the chassis. 
    How do I solve this problem?
    Thanks
    Phuc

    Hi Phuc,
    It looks like there is already a discussion forum discussing the same issue: PXI MXI chassis timeout
    Thanks,
    Best regards,
    Rohan B

  • Nmea 2000 over pxi - can bus (NI PXI-8460/2​)

    Hi,
    I gonna purchase an Automatic Test Equipment (ATE) based on NI PXI.
    (LabWindows/CVI, Win7)
    One of the features of my ATE is to test a NMEA2000 network (read and write masseges).
    Can I use the NI PXI-8460/2 module to test the NMEA2000 network?
    If yes, what else do I need except of that module (software, hardware)
    If not, what can I use instead of a CAN-BUS module?

    Hello easo,
    All of our CAN cards will work with a network as long as it is CAN compliant. In order to program our CAN cards all you will need is our CAN driver. Please let me know if you have any other questions. Have a great day!
    Best Regards,
    Adam G 
    National Instruments
    Applications Engineer

  • Oracle service bus and database connectivity

    Since currently OSB does not support Adapter Framework, what are currently options for using DB Adapter type functionality in Oracle Service Bus (ALSB).
    It seems JMS and other transports are very well supported, but how do we use DB Services?
    Please if someone can provide some insight into this.
    thanks

    Oracle Service Bus 10gR3 contains the JCA framework which will eventually allow us to exploit the whole set of JCA adapters currently in use in BPEL Process Manager. Over the next few months several JCA adapters will be certified to be used with Oracle Service Bus - the Database adapter is one of the first of these.
    As for SOA Suite and WebLogic bundling, let me explain. SOA Suite contains the following products:
    BPEL Process Manager
    Business Activity Monitoring
    Business Rules
    Web Services Manager
    Complex Event Processing
    B2B
    ESB (the old Oracle ESB product)
    Service Bus (formerly AquaLogic Service Bus from BEA)
    This does not come with an application server as the suite is hot-pluggable (i.e. can be used with a number of application servers). However, the preferred (and cheaper) approach is to purchase SOA Suite and WebLogic Suite (which contains iAS, WebLogic Enterprise Edition, Coherence, JRockit with 100ms deterministic garbage collection and WebLogic Operations Control). This is because some of the elements of the SOA Suite only currently run on iAS (B2B) and some only run on WebLogic Server (Oracle Service Bus) although in the future these will also become hot pluggable.
    To find out more, check out the SOA Suite and WebLogic Suite pages below:
    [SOA Suite|http://www.oracle.com/technologies/soa/soa-suite.html]
    [WebLogic Suite|http://www.oracle.com/appserver/weblogic/weblogic-suite.html]
    You will find the DataSheets are particularly useful for giving you an overview of the suite.
    Hope that helps.
    Chris

  • PCMCIA card problem; bus not working -- connection to logic board was loose

    The PCMCIA WiFi adapter on my good ol' TiBook recently stopped working all of a sudden. (OS X wasn't automatically recognizing the adapter as it used to, and the power LED on the card itself wasn't lighting up.) I thought the adapter itself was broken, but discovered the problem was with the slot itself after trying a brand new adapter in the slot.
    I came across this post by user "eww" that ended up fixing the problem in less than a minute. As eww had said:
    ...Check to make sure your PCMCIA card cage's connection to the logic board hasn't worked loose, as they sometimes do. Release the keyboard (instructions are in your owner's manual) and flip it gently back onto the wrist rest. Look for a brown tab under the normal position of the D and X keys. That's the card cage's connector to the logic board. Press it down firmly; if it moves or clicks at all, it was loose and probably not making good contact. Test again after returning the keyboard to its place.
    This worked perfectly for me. I'm posting it here so hopefully it can benefit someone else with the same problem I had. Thank you, eww!

    Hi, Mihira. You're quite welcome. It's always nice to hear that an old post continues to be useful.

  • How to connect a Compact RIO to a PXI System

    Hello,
    I want to connect my cRIO-9074 with my PXI System.
    First of all my Hardware configuration:
    1. "PXI-1036" Chassis with "PXI-8101" Embedded Controller and "PXI-8231" Ethernet
    2. "cRIO 9074" Integrated 400 MHz Realt-Time Controller
    3. "NI 9144" EtherCAT slave chassis
    The PXI System is connected with my Network through the Ethernet-Port on the "PXI-8101" Controller. The "NI 9144" is connected with the "cRIO 9074" through their EtherCAT Ports. That works without a problem.
    Now I want to connect my "cRIO-9074" with my PXI-System through the Ethernet Port on the "PXI-8321", but I can't find a way to get this work.
    In MAX I configured the second Ethernet Port on the PXI as "TCP/IP" with a IP and Subnet. Then I connected the cRIO and turned it on.
    But I can't find the cRIO anywhere in MAX or in a LabView Realtime Project.
    When I configure the "PXI-8321" as a EtherCAT Port, I can connect my "NI 9144" with it and use it in a LabView Project. But configured as Ethernet and connected with the "cRIO 9074" it doesn't works.
    Is there any way to get this working? Or is this not possible with my Hardware?
    I know I could connect the cRIO and PXI through a Switch with my Network and then use both in a LabView Real-Time Project. But I want to build a mobile Measurement-Station with as few devices as possible. If there is no other way I will use a Switch, but without would be better.
    Thankful
    Daniel Löffler

    Hi Daniel,
    it is not possible to connect cRIO-9074 Controller with the PXI System through the Ethernet-Port, because the RT cRIO Controller can not behave as a slave. cRIO Controller is always configured as a master, never as slave. The extension Chassis 9144 is configured as a slave, so you can use it with your cRIO Ctrl or with PXI Ctrl as well. Connection PXI-Ctrl, cRIO-Ctrl, NI 9144 is not possible.
    Best regards,
    ENIA
    NI Germany

  • NI 1073 PXI chassis

    HI
        I have a new chassis 1073
        If in MAX I try to open a Visa Test panel I receive this warning message( cf the attached capture file) it isa usual?
        We develop a PXIe card( arb wavefor generator) with PLX8311 PXIe-local bus bridge. When we plug this card in the chassi the computer don't success to "see" it. When we test we know that   there is  no activity on receive line (A5 B5 line3 on connector) ( when check on pcie connector on the computer mother board  we see activity on this lines) why?
        the pin A2 (PRSNT#) will be pulled down?( or connect directly to GND?)
    The signal level PXIe and PCIe are the same? ( we work with an evaluation bord with the same bridge on PCIe and it work fine) 
    Thanks for help
    Dina 
    Attachments:
    PXIeChassis1073.nitrace ‏6 KB

    Dina,
    Here are a few things to check.
    - A5/B5 should be connected to the PLX 8311's TX lines through capacitors (standard PCIe levels).  TX --> cap --> A5/B5
    - C5/D5 should be connected to the PLX 8311's RX lines (standard PCIe levels).  RX <-- C5/D5
    - Refclk is not a standard PCIe level.  It's LVPECL instead.  So it should should be AC-coupled and rebiased/terminated.  As I recall, this suggested bias is a 56 ohm resistor to GND and a 475 ohm resistor to 3.3V (50 ohm Thevenin equivalent, center point of voltage around half the normal swing of PCIe's HCSL clock lines).  The PLX bridge may have different requirements.  RefClk <-- [bias resistors] <-- cap <-- E4/F4
    - PRSNT# (A2) should be pulled down or connected directly to GND, though it's not used in a 1073.
    Robert

  • PXI Platform Services and VISA 3.3.1

    I have a customer who is complaining about the two unidentified PCI devices listed in Windows XP Device Manager.  I understand this situation is caused by the bridges between the PXI bus segments on the PXI-1045 chassis I have connected.  I also understand that installing the PXI Platform Services software will correct this situation.
    My concern is that the install of PXI Platform Services also attempts to install a newer version of VISA and NI-MAX.  For example, PXI Platform Services V2.1 tries to load VISA 4.0 and NI-MAX 4.1.
    Is there a version of PXI Platform Services that is compatible with VISA 3.3.1 and NI-MAX 3.1.1?
    I realize that these are old versions, but due to software configuration constraints, I can not update this software without re-certifying 250+ UUT Test Programs, which is time-consuming and expensive.
    Thank you in advance for your assistance!

    Hey cmelo258,
    I have some bad news for you, the oldest version that I could track down was Platform services v2.0.1.  It contained no readme, so I tried installing it and it tries to install VISA 3.5.1 and MAX 4.0.3.  Hopefully, someone else has better news for you.
    ColeR
    Field Engineer

  • Generate PXI Trigger Signals with PXI-6115

    Hello,
    I have a question.
    I have a PXI-6115 and some other card in my mainframe.
    These other cards nee 10 Mhz pulses on line PXI-Star1 and 2.5 MHz on PXI_trg7.
    So I thought to apply (somewhere on my PXI 6115 card) 10 MHz, divide the 10 MHz with a counter to 4 and route all this things to the backplane.
    But I don't understand how to do this.
    There are no good examples.
    And as far as I know the PXI-6115 isn't yet supported by DAQ-MX.
    Can anybody give me some good advises or tips, white paper or so to make me solve my problem ???
    Thanks Ruediger

    I don't have time to write any example snippets right now, but I'll try to provide you the general idea and hopefully you can take it from there.
    First, it's not clear whether you want to generate the 10 MHz from the 6115 and send it to other devices in the system or accept the 10 MHz externally and route it to the rest of the system.  If you're bringing in the signal externally, I would simply using the DAQmx Connect Terminals VI to route the signal from a PFI line on the front connector of the board to one of the PXI trigger bus lines in the backplane.  Check out the routing table in MAX to see what routes are possible.  To perform this route, the driver will have to route through Counter 0 so you won't be able to use Counter 0 for anything else.
    If you want to generate 10 MHz from the 6115, I would create a continuous pulse train task on Counter 0 using the CO Pulse Ticks version of the Create Channel VI with a value of 2 for both the high ticks and low ticks input.  However, to achieve 10 MHz clock on a PXI trigger line, you'll have to perform a couple of modifications that typically aren't done with counter tasks.  First, you'll need to use the DAQmx Export Signal Property Node to route the Counter Output Event to the desired PXI trigger line.  You can find this property by navigating the following menu hierarchy Events->Counter Output Event->Output Terminal.  By default, the driver routes this event to the Ctr0Output pin on the front connector of the board.  Using this property will override this behavior and route the output of the counter to a PXI trigger line instead.  Second, you will need to change the output behavior of the Counter Output Event from toggle to pulse.  This can be through the Events->Counter Output Event->Output Behavior property.  Normally, when generating pulse trains, the high ticks and low ticks parameters from the Create Channel VI determine the frequency and duty cycle of the pulse train.  When the high ticks count expires, the output of the counter toggles.  The low ticks value is then loaded into the counter, and the counter output toggles again when the low ticks value expires.  This process repeats to produce a pulse train of the desired frequency and duty cycle.  Since the counter uses a 20 MHz timebase and has a minimum low ticks and high ticks value of 2, you can only produce at maximum a 5 MHz pulse train using the toggle behavior.  However, by changing the output behavior from toggle to pulse, the counter output will issue a short pulse each time the high ticks and low ticks counts expire yielding a 10 MHz clock signal.
    Now that you have the 10 MHz signal taken care of, you need to generate a 2.5 MHz signal from it.  My guess is that since you have a 6115, you already have plans for the AI engine so I'll describe a route that uses AO instead.  First, create an AO task to perform continous waveform generation.  Use the DAQmx Channel Property Node and set the Use Only Onboard Memory property to true.  Setting this to true will cause the driver to download the waveform once upon starting the task and replay the waveform from the onboard FIFO.  Since you're only using this task to generate a clock, you don't really care about the data and this will prevent unneccessary traffic across the PCI bus.  Next, use the DAQmx Timing Property Node to set the Sample Clock->Timebase->Source to the PXI Trigger line that you're generating the 10 MHz clock on, and set the Sample Clock->Timebase Divisor to 4 (10 MHz / 4 should give you a 2.5 MHz sample clock).  Last, use the DAQmx Export Signal Property Node to set the Clocks->Sample Clock->Output Terminal to the PXI Trigger Line you want to generate the 2.5 MHz signal on.
    It requires some creative programming, but you should now have a 10 MHz and 2.5 MHz signal routed onto two different PXI Trigger lines.  I know this solution is a bit involved so if you have any further questions be sure to post back.

  • PXIe-1065 Trigger lines

    Hi all
    I'm trying to acquire data on 7 PXIe-6358 boards. All these boards are put in a PXIe-1065 chassis which is connecte to a RMC 8354 throught a MXI 8360. In order to synchronize all boards togethet i use a PXI 6682H board which will generate a clock and a start trigger on two PXI trigger lines.
    I made some test on a PXIe 1075 chassis and everything seems to work fine. I moved then on a PXIe-1065 chassis and now i'm having some problem when i try to acquire data on the 7 boards. When i have more than 5 boards, it seems at least one board doesn' receive either the clock or the start trigger.
    Then trigger are configured in MAX to go through all 3 bus. When i configure only 5 boards (wherever in the slot) i works fine. But when i declare more than 5 boards i have the problem again.... It seems you cannot connect more than 5 boards to the trigger lines.
    Does someone have an idea...

    Ok, i found the problem, it has nothing to do with the PXIe 1065 chassis.
    In my application i use the PXI 6682H to generate the start trigger and a clock. The acquisition tasks are waiting for the trigger to start the acquisition. In my case when i switched the chassis, the PXI 6682H becomes a master (in the old configuration it was parameter as a slave). When it is configured as a slave i check that the board is synchronized with the master (this can takes a little time). When i am the master i doesn't wait (cause i am already synchronized). Therefore, in that case the start Trigger is generated before all instances of the PXIe-6358 are started, and they wait indefinitively the trigger ....
    I modify the code in order to wait a certain amount of time (even if the PXI6682 is configured as the matser) , and now its works properly ...

  • Release date for PXIe Modules

    I had a couple of questions about PXIe:
    1) I see that a controller and chassis have been released, when will Digitizers and DAQ cards be released?
    2) It is my understanding that a PXI card that is plugged into the PXIe
    chassis will work, but NOT receive the 1GB/s bandwidth, is this
    true?  In other words, PXI cards do not get the bandwidth upgrade,
    just PXIe cards.
    3) I saw in the PXIe tutorial that PXI cards can be sent in and the J2
    pin port will be replaced to make it into a PXIe hybrid card. 
    Would this card gain the benefit of the 1GB/s bus speed?
    Thank you in advance,
    Austin McElroy

    I'll answer your last two questions:
    >>It is my understanding that a PXI card that is plugged into the PXIe
    chassis will work, but NOT receive the 1GB/s bandwidth, is this
    true?  In other words, PXI cards do not get the bandwidth upgrade,
    just PXIe cards.
    There are different types of slots in PXI Express chassis. A PXI card can be plugged into a hybrid slot or a PXI slot. A PXI slot can only accept a PXI card. A hybrid slot can accept a PXI card or a PXI Express card. In order to insert a PXI card into a hybrid slot, it must have the J2 connector replaced as you stated. Some PXI cards do not have a J2 connector and these need no modification.
    PXI and PXI Express cards use different types of busses to connect to the system. PXI cards use only the PXI (PCI) bus while PXI Express cards use a PCI Express link. Electrically, the two busses are not compatible or interchangeable. Hybrid slots support both busses, but a card only uses one or the other. The bandwidth available to a PXI card does not increase if it is plugged into a hybrid slot as the PXI card will only use the PXI bus, not the PXI Express bus.
    >>I saw in the PXIe tutorial that PXI cards can be sent in and the J2
    pin port will be replaced to make it into a PXIe hybrid card. 
    Would this card gain the benefit of the 1GB/s bus speed?
    No, this card still connects using the PXI (PCI) bus. The PXI Express bus in the hybrid slot will not be connected to the PXI card. The PXI card will not be able to access the bandwidth provided by the PXI Express bus.
    This is a subtle point, but a PXI card that has been modified to work in a PXI Express hybrid slot is known as a "hybrid slot-compatible PXI module". A "PXIe hybrid card" seems to imply a card that uses both the PXI Express and PXI busses. I doubt such a card would ever be designed.

Maybe you are looking for