Need cntrller.ini for PXI Chassis

I need to configure an RT for use with my VXI system. My VXI embedded controller seems to be missing this file. Any help?

Hi NANOBOU,
I'm not 100% clear on what you are doing when it asks for that file.  Do you have any hardware installed in the PXI-1036?  If so, what is it?  It's possible that getting the latest drivers will update MAX and possibly fix the problem.
In the meantime, please check out our MXI Troubleshooting guide.  Some of these hints might help:
http://digital.ni.com/public.nsf/allkb/484f81e6570ad803862569ed007aaa41
http://digital.ni.com/public.nsf/websearch/61B9E985DC3025BD862569EB00718360?OpenDocument
Thanks,
mike

Similar Messages

  • 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?

  • Assembly part number for individual PXI chassis slot blockers?

    I need the individual assembly part numbers (not the catalog or packeaged kit number) for the standard 3U PXI chassis slot blockers.  The ones we have accumulated are stamped with the part numbers below but I need to know if this is the part number for the "assembly" with fasteners, or just aluminum plate.
    1 slot   185365C-01
    2 slot   185365C-02
    4 slot   185365C-04
    also is there a there 3 slot available (perhaps a -03)?
    Thanks,
    Darrow

    Hi Darrow,
    The part numbers listed above are indeed for the plates. Those three sizes are the only ones available through National Instruments; unfortunately there is no three-slot plate.
    Best regards,
    Tim

  • PXISYS.ini for a PXIe-1065

    Where can I get or verify that I have the correct PXISYS.ini for a PXIe-1065 chassis?
    The PXISYS.ini that is located in the Windows directory contains -1 for PCIBusNumber and PCIDeviceNumber all the slots
    PCIBusNumber = -1
    PCIDeviceNumber = -1
    PXISYS.ini is attached.
    I believe this is the cause of all the slots showing as Unknown or Empty
    Thanks
    Omar
    Omar
    Attachments:
    pxisys.ini ‏5 KB
    Chassis.ini ‏2 KB

    Hi Omar,
    You can get a new pxisys.ini file from this webpage. You'll basically have to download the peripheral driver. I'm also linking this article for your reference that describes the pxisys.ini.
    Best regards,
    Rohan B

  • 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

  • How do you configure multiple PXIe chassis to share Tclk synch with the 6672 timing module?

    Hi,
    I have two PXIe chassis, each with a number of digitizers (configured through NI-SCOPE). Each chassis has a PXIe 6672 timing module. I have downloaded the sample VI from:
    http://zone.ni.com/devzone/cda/epd/p/id/5254
    which deals with PXI chassis. My question is this: in the VIs at the above link (and in fact all VIs I've seen for using the 6672 for sharing triggers), the VI needs access to the resource identifiers for both Master and Slave timing modules, how do I access the (remote) slave resource identifier from the master chassis? I feel like I'm missing something obvious, but can I do this using just an ethernet connection, or do I need another module to enable the master chassis to view the devices on the slave chassis in MAX? 
    Thanks for any help you can provide,
    Cillian

    Those example VIs are written to be used when a single host PC is controlling multiple chassis so there is just one computer running the program.  Since both of your chassis have their own controllers it will be necessary to run a program on each (one as master, the other as slave).  You can modify the code from that example to create and Master and Slave VIs.  For the Master you will call the VIs as specified in case 0 of the example; for the Slave you will call the VIs as specified in the default, 1 case of the example.
    You will also want to send a signal from the Master to the Slave to let the Slave know that the clock is being generated.  You could use TCP/IP or a PFI line to do this.  The basic order of events should be as follows:
    1. VI runs on Slave to configure it to accept a clock.
    2. VI runs on Master to begin outputing the clock.
    3. Master sends a signal to Slave to let it know that the clock is being generated.
    4. Continue with the rest of your program.
    Let me know if you have any questions about this.
    Barron
    Applications Engineering
    National Instruments

  • Detect and employ PCI or PXI chassis

    I'm currently on a project which has historically bee based around a PCI backplane (in a desktop PC) containing a couple of PCI-6229 cards and a PCI-7833R. This forms the core of a testrig of which there are about 25 instances worldwide. In addition, we also support many rigs which are cored around a NI PXI chassis.
    There is a drive to replace the PCs and we have opted for a for smaller footprint unit having fewer PCI slots. These are being equipped with an MXI extender card to a PXI backplane. This means in future, we need only keeps spares in the PXI format. Supporting two sets of backplanes containing near-identical hardware without implementing two near-identical pieces of software does present its problems: The FPGA bitmap build for the PCI version of the card will not open through the reference type for the PXI version of the card. We need to have a PCI and a PXI version of the bitmap. Irritatingly, the source code for these two is identical.
    The first part of the solution is to establish which backplane we're using. This is straightforward. Supplying the VISA Find Resource function with the appropriate search string will identify if any PXI backplanes are connected. (Figure 1.)
    Next, we need to maintain references to both FPGA VIs. Figure 2 illustrates how the FPGA to be used can be opened and proposes a structure in which the references to all available FPGA types (this example actually has four FPGA bitmaps which might be selected). In each of the other cases, the appropriate bitmap is selected in the Open FPGA Reference VI. Further, in each case, the reference is wired to the appropriate component from the cluster. (For calibration records, we also find it necessary to return the serial number of the card, but that portion of this code can be ignored.) Notice that the FPGA_Type component of the cluster is used to control which bitmap loads and which Ref component is used to store its Reference. This is necessary because the reference types are different for each bitmap.
    Having set FPGA_Type, Figure 3 shows how to employ the selected resource. A separate Read/Write Control must be coded for each FPGA type.
    Closing the resource also requires a case for each FPGA type.
    I hope anyone else planning a stepped migration between backplanes can make use of this.

    To program any DAQ card for use in Linux you need to use Register Level Programming. Unfortunately, Register level programming for the counter/timer products based on the NI-TIO ASIC (includes the 660x boards) is not supported.

  • Need extender box for PC-6031E because of limited slots on PC

    Due to size limitations in instrument console latest mini tower DELL offerings do not have sufficient slots.
    We would need at least two external for PCI-6031E cards. Any NI solutions available?
    Thanks, Fran

    Hello Fran,
    There are a few different NI solutions for your particular situation.  First, you could consider some of the many USB DAQ products offered by NI.  Additionally, there is the option of a MXI interface.  WIth MXI, you can use a PCI device, such as the PCI-8133 to control a PXI chassis.  You could then put any number of PXI devices (including PXI E Series devices, like the PXI-6031E) in the PXI chassis.  Finally, I've noticed that some newer computers now have PCI Express slots as well as PCI slots.  We also offer a PCI Express DAQ device, the PCIe-6259.  Please feel free to re-post if you have any questions about any of these products.  Hope this helps
    -Alan A.

  • Seeking help for PXI card Installati​on Procedure Guidance

     I have PXI-1042 Chassis with PXI Card numbers 2503 MUX , DIO and AIO cards.  We are running LabWindows CVI with TestStand 3.0.I have to load all of the above into a new system.  I wanna know the step wise procedure i need to follow for using these above mentioned cards w.r.t INSTALLATION process. May i get the document OR link OR any suggestions i need to follow.???
    Thank you in advance

     I have PXI-1042 Chassis with PXI Card numbers 2503 MUX , DIO and AIO cards.  We are running LabWindows CVI with TestStand 3.0.I have to load all of the above into a new system.  I wanna know the step wise procedure i need to follow for using these above mentioned cards w.r.t INSTALLATION process. May i get the document OR link OR any suggestions i need to follow.???
    Thank you in advance

  • Compatability of LabView RT with Third Party( NOT N.I ) PXI chassis

    I want to use NI LabView and LabView RT, some PXI chassis of N.I and
    some PXI chassis of Third Party( not N.I ) for diversity, How I will Install
    Pharlap ETS ( LabView RT ) on those third party PXI's.
    More simply
    Third party PXI chassis and controllers support LabView RT or not?
    Note: Mark Andre Hary [email protected] of Sensing Systems LLC answer to this question as:
    "You can't.  I think NI bought Pharlap, and they do not offer board support packages (BSPs) for non-NI PXI controllers.  There is no way to get LabVIEW-RT running on a controller not purchased from NI.  You will have to use a standard RTOS like Linux,VxWorks, or QNX.
    Regards

    Hello,
    You can install LabVIEW RT ETS on a third party PXI controller just as if it were a PC.  Check the requirements that a PC needs to have in order to run LabVIEW RT ETS.
    Check the following link:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/cb3434da94466dd286256e9e006bb775?O...
    Ricardo S.
    National Instruments

  • Use NI LabView and LabView RT with third party PXI chassis

    I want to use NI LabView and LabView RT, some PXI chassis of N.I and
    some PXI chassis of Third Party( not N.I ) for diversity, How I will Install
    Pharlap ETS ( LabView RT ) on those third party PXI's.
    More simply
    Third party PXI chassis and controllers support LabView RT or not?
    Note: Mark Andre Hary [email protected] of Sensing Systems LLC answer to this question as:
    "You can't.  I think NI bought Pharlap, and they do not offer board support packages (BSPs) for non-NI PXI controllers.  There is no way to get LabVIEW-RT running on a controller not purchased from NI.  You will have to use a standard RTOS like Linux,VxWorks, or QNX.
    Regards

    As described in the web links below, the only way to run LabVIEW Real-Time for ETS on a third-party system would be to follow the procedure for desktop PC computers. You may find that your third party PXI controller may meet the requirements listed in the below link and you will be able to run Real-Time on the controller. If you decide to do this, you will need to purchase the LabVIEW Real-Time Desktop Deployment license (also linked below). After purchasing the deployment license, you will be sent boot disks that will install the real-time OS onto your system. There is no need to purchase Pharlap ETS from Ardence directly.
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/cb3434da94466dd286256e9e006bb775?OpenDocument
    http://sine.ni.com/nips/cds/view/p/lang/en/nid/13751
    Instead of using LabVIEW Real-Time for ETS, you could use LabVIEW Real-Time for RTX instead. This system allows you to run Windows and the Ardence Real-Time eXtensions (RTX) real-time kernel concurrently on one machine. Currently device support for LabVIEW RT for RTX systems is limited to RIO devices. This is all described in the below link.
    http://zone.ni.com/devzone/conceptd.nsf/webmain/9cc60298315a687e86256e78007b3a96
    I hope this answers your question.
    Regards,
    Kristi H - National Instruments

  • Where to find connectors for PXIe plugin card

    Can anyone help with information about XP4/XJ4 connectors for PXIe: Suitable vendor type numbers?
    We want to make a custom card to plug into a PXIe-1071 chassis - but only need the 3.3V power from the chassis. But after long search I was unable to find a type number for such a connector. XJ4 is the smallest but obviously any of the connector types will do as they all have power pins.
    Solved!
    Go to Solution.

    Hello heel.
    I have searched in our internal papers, and according to my findings we are using ERNI as a manyfactor for our connectors.
    ERNI
    Also, since you want to design for own PXI board, you might be able to find some usefull information in the PXI specifications.
    PXI Systems Alliance
    I hope you can use this information.
    Best Regards
    Alex E. Petersen
    Certified LabVIEW Developer (CLD)
    Application Engineer
    Image House PantoInspect

  • Computing Requirements in Multiple PXI Chassis System

    I have acquired a two PXI Chassis system, each with their own embedded controller (PXIe-8108 and PXIe-8130).  I would like to control all instruments (simultaneously) in both chassis from a central location (either a laptop or one of the embedded controllers).  What is the best configuration for this and will using one controller have enough power to drive two fully populated PXIe-1065 chassis?
    (I am aware of the different configurations for control (MXI, etc.) and am more concerned with instrument performance, data buffers become full quickly etc., in using one PC controller)
    THANKS!

    Hi JMU_ISAT,
    The PXIe-1065 chassis uses a four link configuration where there is an x4 link going to slots 7, one to slot 8, another to slots 9-14.  There are also an x1 link converted to PXI that goes to slots 2-7 and another x1 link converted to PXI that goes to slots 11-13 and 15-18.  Each x4 link gives 1 GB/s of bandwidth and each x1 link converted to PXI will provide 125 MB/s of bandwidth.  These bandwidths are theoretical maximums where overhead and chip design reduces the bandwidth somewhat.  
    The PXI-8130 has four x4 links with the four link configuration so it will be able to get the full chassis bandwidth.  The PXIe-8108 has four x1 links which will limit the bandwidth to 250 MB/s for slot 7, slot 8, and slot 9-14.
    To synchronize the measurements across both chassis you will need a timing and synchronization module such as the PXIe-6672 in the timing slot of each chassis.  This will allow you to route the clock of one timing module to the other and then use that clock to override the backplane reference clock of each chassis.  Now each module can use the 10 MHz reference clock to synchronize to each other.
    In order to control both chassis from one controller, you can run windows on one controller and LabVIEW RealTime on the other controller allowing you to distribute code from the windows controller to the LabVIEW RealTime controller.  The other method would be to run a MXI connection from one chassis to the other to daisy chain the chassis.  Since the most you can get out of a single slot of the PXIe-1065 is an x4 link, this would limit the total bandwidth of the daisy chained chassis to 1 GB/s theoretical maximum.
    I hope this information is helpful!
    Andy K.
    Applications Engineer
    National Instruments

  • Do NI PXI Chassis support 3.3V PXI?

    Newer DSPs, e.g. TI TMS320C6415, which have a PCI interface built in, only support 3.3V PCI levels. Therefore, the PXI chassis must operate at the 3.3V level as well. In addition, the cards, such as MXI-3 need to operate at those same levels. Will they? If not, does NI have any migration plans to 3.3V? Also, if 3.3V is not supported, then does NI have any suggestions for how to use a 3.3V only chipset in a new design which is intended to fit into a NI PXI cardcage? Thanks.

    National Instruments PXI chassis and cards are keyed for 5V operation, and there are not any current plans to migrate to a 3.3V setup. We currently do not have a solution for using a 3.3V-only card in one of our chassis.
    Ryan Tamblin
    Applications Engineer
    National Instruments

  • How many PXI Chassis can be connected (Daisy Chain)on MIXI Express.

    How many PXI Chassis can be connected (Daisy Chain)on MIXI Express?
    Regards
    Prabhakant Patil

    Hi Prabhakant
    Based on the MXI-Express datasheet and the MXI-4 Series User Manual "The PCI specification makes provisions for up to 255 bus segments to simultaneously exist in a PCI hierarchy and MXI-4 hardware provides everything needed to support those provisions." 
    I'll get back to you after speaking to a specialist.
    Kind Regards
    Chris | Applications Engineer NIUK

Maybe you are looking for