PXIe-1073 sytem not detected

I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
Any ideas on how to fix this issue ?
Thanks
Jeet

Hi Matt
Sorry for delay in replying.
After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
In the picture, you can  see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
The attached pic shows NI-MAX and device manager snap shot.
Please advise.
Thanks
Jeet
Attachments:
nimax dev man.jpg ‏316 KB

Similar Messages

  • MXI3 (NI PXI-8330) board not detected. Not powering up, no link light.

    MXI3 (NI PXI-8330) board not detected. Not powering up, no link light. Cable looks fine. Any ideas?

    PeteMan,
    I will need to know in more detail how your system is behaving to give you better tips, so please feel free to send me more information.
    For now, let me send you a couple of troubleshooting tips:
    Cable connection
    Make sure both ends of the copper cable are well connected to the PCI-MXI-3 and the PXI-MXI-3 boards. Be careful when disconnecting the copper connectors. you need to push down the plastic connector so it does not get damaged. Damaged connectors could result in bad MXI-3 links.
    If the connector has not been used properly, it could be broken (this rarely happens). Make sure you are not connecting the cable backwards.
    Power - Up order.
    It seems you are controlling your PXI chassis using a PCI-to-PXI extender (copper cable). Make sure you are powering up the PXI chassis BEFORE powering up the PC.
    PXI is built on top of the CompactPCI spec, so it uses the PCI high speed bus. The MXI-3 extender is really a PCI-to-PCI bridge toyour computer, so for your PC, all the slots in the PXI chassis look like more PCI slots. In other words, your computer suddenly has more PCI slots.
    It is very important to power up the PXI chassis first before powering up the computer, because at power up the PC enumerates all PCI slots. If the PXI chassis is OFF during boot up, the slots in the PXI chassis will never get enumerated and your PC will never see the board installed in the PXI chassis.
    Normal Power up LED sequence
    Each MXI-3 board has four LED light on its front panel: two green lights (POWER and LINK) and two orange lights (Tx and Rx). When you power up the PXI chassis you should see one green light and one orange light ON steadily (POWER and ). Then, when you power up the PC, both green lights shoudl be ON steadily and the orange lights shoudl flicker.
    If you do not see this behaviour at power up, most probably one of your boards its damage.
    If you have another MXI-3 extender kit, try to set up the system mixing the boards from the two kits to try isolate which board is the one that is damaged.
    Run the MXI-3 Optimization Software
    The MXI-3 Optimizaton Software makes sure that the link between the PC and the PXI chassis has been set up properly. It will show you an error otherwise.
    MXI-3 Software Version 1.15 for Windows 95/98/NT/2000/ME
    The PC powers up fine if the PXI chassis is OFF, but if I turn on the PXI chassis first and then try to power up my PC, my PC does not boot
    There are several things that could be causing this behaviour:
    It could be that your PC has an old BIOS that has issues detecting PCI-to-PCI bridges. You could try upgrading the BIOS.
    A part of the hardware could be damaged. If you have a main-stream computer (like a DELL or HP PC, for example), test your MXI-3 extender in it to make sure that the hardware is in good conditions. Main-stream computers tend to use new Motherboards with good BIOS.
    There are more tips in the following KnowledgeBase:
    KB 267FAS5P : MXI-3 Troubleshooting Guide
    Hope this helps,
    Claudia Lorente
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • PXI-6602 is not detected by M&A

    Hello,
    I have a PXI-1033 (integrated MXIe card) chassis with a PXI-6602 module installed in it.
    Measurement & Automation Explorer shows only PXI System (Undifined), please see attached file (1.jpg). In the list "Identify as" I can not see NI-1033 controller. Before that I have installed software form "NI PXI Platform Service". When I choose NI-1033 controller from CD the message "could not import controller information" is appeared, when I choose any other controller, Measurement & Automation Explorer shows "chassis" which I can identify as PXI-1033. But there is no possibility to detect PXI-6602 card by Measurement & Automation Explorer.
    System information: Win XP, LabView 8.5.1,NIDAQ922f0 drivers are installed.
    So, the questions:
    1. Why there is no DAQmx branch in Measurement & Automation Explorer tree with PXI-6602 card? 
    2. How can I test my PXI-6602 card (it absolutely new, but...)?
    3. How it is possible to install correct controller for PXI-1033 chassis?
    Thank you.
    Attachments:
    1.jpg ‏141 KB

    Hello,
    the problem discussed in the previous message was fixed and here is the solution:
    After additional investigation it was found that the issue is with "This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system. (Code 12)". This topic was discussed (http://digital.ni.com/public.nsf/allkb/04C12CB4A5143ECC862572DC007B8DF6). But it did not help. I updated the BIOS in my Laptop (Dell Vostro 3300) from A05 to A09 version. But it did not help again.
    After that I found a "MSI-Express BIOS Compatibility Software". Installation this software fixed the problem.
    Hope this information will be helpful.

  • NI PXIe 8361 card not detected

    Hello,
    I have a problem with a NI card.
    I had my NI PXIe 8361 card mounted on a windows XP, connected to a PXIe1073 frame. It all worked fine.
    Since then, I changed my PC, I now have a new one with windows 7. 
    I've installed LabView, DAQmx but when I insert the card into the computer and connect it to the frame, nothing happens. 
    -> on the card the green leds are on
    -> on the frame the green power led is on but the link led is off
    -> in the device manager of NI MAX I don't see any NI PXIe 8361
    despite various attempts it won't work, did I missed something? something more to install?
    Thanks in advance for your help.

    Pierre24 wrote:
    There was nothing in the slot before, first use of it.
    There are other slots and I've already tried them, same result.
    I don't have any other card to test :/
    But what can be the problem with the PC ? I think everything is installed, lights on the card are green and the PC is new with much higher performances than the old one.
    Looks like you need to install PXI Platform Services. http://www.ni.com/download/pxi-platform-services-14.0/4897/en/

  • PXI-8532 DNET card is not detected in MAX

    Hi all,
    I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
    Slot 1= PXI-8106 Controller
    Slot 2= PXI-6259 card(AI)
    Slot 3= PXI-6509 card(DI,DO)
    Slot 4= PXI-8532 Card(DNET)
    In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
    PXI-6259 (PXI1 Slot2)
    PXI-6509 (PXI1 Slot3)
    The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
    In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
    Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
    DNET driver version - 1.6.4
    Thanks,
    Raja
    Solved!
    Go to Solution.

    Dirk,
    Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
    New driver - NI-Industrial Communications for DeviceNet 2.1
    But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
    By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
    After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
    Old DNET function palette - Instrument IO>>DNET
    New DNET function palette - Industrial Communications
    My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
    With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
    Error Code ="-1074388957" - The Interface is invalid or unknown.  Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
    With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
    1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
    2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
    Thanks,
    Raja
    LV 2009, Windows XP

  • Pxi cards on 1000b cahssis not detected under windows 98

    my mxi-3 card is being detected on windows startup (mxi-3 optimization software is running correctly) but all other pxi cards on my 1000b pxi chassis are not detected.

    Anis,
    Well, I always prefer to try the simplest things first. In this case, that would be fully powering down the chassis and the computer. Then powering on the chassis first, and a few seconds later, powering on the computer. If this doesn't help, then you would probably want to try any or all of the following troubleshooting steps to try and isolate the problem:
    - Try removing all but the mxi-3 and one other card from chassis and then try booting up.
    - Try placing the pci mxi-3 card in a different slot in the computer.
    - Try uninstalling and reinstalling all the NI software on your computer. (better yet, format and reinstall).
    - Try the pci mxi-3 card in a different computer.
    - Try a different set of mxi-3 cards (if available)
    - Check
    device manager to see if there are any errors or warnings.
    So those are the things that I would try. If after all that you still have no luck connecting you may have a hardware problem and need to RMA (Return Materials Authorization) your hardware.
    Please post back with what you find.
    Regards,
    Jed R.
    Applications Engineer
    National Instruments

  • Can i use PXIe-1073 with an embedded PXIe controller PXIe-8108

    I have a PXI express chassis PXIe-1073 with an integrated controller MXI-Express controller PCIe-8361. I now want to use the chassis as a standalone system with an embedded controller.
    (a)Can i use PXIe-1073 chassis with PXIe-8108 embedded controller
    (b)Can i use a windows based laptop to control the PXIe-1073 via the PCIe-8361 integrated controller.

    Hello kanad,
    The PXIe-1073 is a MXI-integrate chassis.  This means that the MXI card that would normally go into the controller slot (slot 1) is built into the chassis.  The PCIe-8361 or Expresscard8360 are placed into the desktop or laptop, respectively, and connect to the chassis.  The cards in the PXIe-1073 then appear as if they are part of the desktop of laptop.
    Since the controller is built into the chassis, the PXIe-1073 does not have a slot 1.  Controllers, such as the 8108 can only be plugged into slot 1.  Therefore, the PXIe-1073 can only be controlled by the desktop or laptop MXI link.  It cannot run standalone with an embedded controller.
    Consider reading page 1-3 and 1-6 in the manual below:
    NI PXIe-1073 User Manual and Specifications
    Regards, 
    George T.
    Applications Engineering Specialist
    National Instruments UK and Ireland

  • PXIe-1073 not detected

    I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64.  I have the latest version of Labview, NI-DAQmx, etc.  The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge").  The chassis and installed DAQ card are not detected in MAX.
    I am actually transferring this system from an older computer.  I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software".  There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
    After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll".  This proceeded to occur every time I tried to load Windows.  I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601".  I was finally able to load the last known good configuration and uninstall the software.
    When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point.  It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts.  Why is the computer unable to recognize the chassis without it?  What else can I do to solve the problem?

    Hello Bob_mcbob,
    After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
    As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
    Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
    Jim St
    National Instruments
    RF Product Support Engineer

  • NI Scope Sorf Front Panel will not detect NI PXI-5122

    Hello,
    I am trying to use NI Scope Soft Front Panel 2.7f0 to acquire simple waveforms;
    however it will not detect my NI PXI-5122. I have confirmed that the digitizer
    works under MAX 4.2.1 and can see waveforms under the test panel. I have
    installed NI Scope 3.3.1 on my machine and have updated the driver on the PXI
    to version 3.3.1. Any ideas on what is wrong?
    ~Buck

    It is unclear from your post whether or not the 5122 is on the same physical device as you are running the soft front panel (SFP).  The SFP only works on local devices.  It does not have the capability to attach to RT or remote systems (MAX does).  However, if you are running Windows on your PXI controller or are using MXI to control the chassis, there is another issue.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • NI PXI-1033 not detected if turned on after PC

    Hi,
    I noticed that MAX does not detect the presence of the NIPXI-1033 if it is turned on after the PC.
    There is a programmatic solution to resynchronize the device? My application using C # and C + +.
    thanks
    Roberto Guerzoni
    Solved!
    Go to Solution.

    Thank you Roberto
    It is normal what happens. Your PC has to see the device during the boot up. It is a BIOS matter. 
    Have a great weekend!
    Antonios

  • How to determine what card is in what slot of a PXIe-1073 unit programmab​le

    How can i programmable determine what card is in what slot of a PXIe-1073 unit I have a PXI-4063 and a PXI-2503 in a 1073 chassis. I use the DAQmx Device Product Type to to find the 2503 matrix card but it woun't return the 4065 product type.

    Hi cjp1,
    The KnowledgeBase article Programmtic PXI Slot Detection walks you through the steps to do this. There is also a community example called Read PXI an PXIe Card Serial Numbers Programatically that demonstrates the type of LabVIEW architecture you can use to do it. 
    You should first ensure that all of your modules can be identified and self-test in MAX. 
    In case the above hyperlinks don't work, you can copy-paste the addresses below:
    http://digital.ni.com/public.nsf/allkb/2342900AED0​2975A86256BD800764C8B
    https://decibel.ni.com/content/docs/DOC-20207
    Jeff Munn
    Applications Engineer
    National Instruments

  • PXIe 1073 Input Grounding

    Hello,
    I was wondering how the grounds from the hybrid slots of a PXIe 1073 chassis are connected within the chassis. I'm using 3 PXI 6255 cards, though I don't believe that makes a difference. What I'm looking for is whether they are tied together or not, or similar information. Thank you.
    Solved!
    Go to Solution.

    BVeezy wrote:
    UPDATE: I was incorrect. Please refer to the following KB:
    http://digital.ni.com/public.nsf/allkb/02A451C0A88​A3EAE8625702F0059C98E
    Regards,
    Brandon V.
    Applications Engineer
    National Instruments 
    Yeah, I discovered that not long ago.  Every ground on DAQ cards are tied to the chassis ground.  It is just that each type of ground (DGND, AGND) have their own planes on the card itself.  And chassis ground will be going to Earth Ground, in case that matters to you.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • MXI-3 interface not detected?

    Hello to you all,
    I was using PXI/PCI 8335 with PXI 1000B chassis. Everytime I run the MXI-3 optimization it says MXI-interface not detected.
    I checked the LEDs.
    For PXI-8335, the PWR and RX were both solid on, one green and the other orange. For PCI-8335, the PWR and TX (nor sure it's TX or RX, just the one in the same row with PWR) were both solid on, one green and the other orange.
    No LINK light.
    The whole system was powered in proper sequence and the fibre optic cable was fine.
    So there seems to be something wrong with the cards.
    I was wondering is there any way to know particularly which one of PXI-8335 and PCI-8335 doesn't work well without replacing them one by one, since I don't have any extras?
    Like, does the LED tell other information except they are not linked?
    Thank you in advance.
    Yaqiong

    Yaqiong,
    In general you can't differentiate between a bad transmitter on one side or a bad receiver on the other, so it's often hard to tell which side is bad.
    In your case, it sounds like one side or the other has a broken transceiver.  Power and RX on both sides means the boards aren't communicating at all, meaning a transceiver is bad, or a cable is bad in both directions, or a cable is not plugged in or is plugged in backwards.  If you power it up without a cable you should get the same LED behavior -- PWR and RX, the two LEDs next to each other.
    If that's the case (same LEDs without a cable as with a cable), you should be able to tell which card is bad if you connect both ends of a half cable to one card (a loopback).  On a working card connecting RX to TX will "link" to itself according to the LEDs (at least it did for me on both the PCI and PXI card).  On a broken card you'll get something else.
    - Robert

  • NI PXIe devices cannot be detected

    Hello, I am 1-year-user of NI instrument. I am using NI PXIe-1062Q. I have some problems with several NI PXI devices installed on this NI PXIe1062Q. My devices are:
    1. NI PXIe-8115
    2. NI PXI-4071
    3. NI PXIe-6556
    4. -
    5. NI PXI-5922
    6. NI PXI-4132
    7. NI PXI-6541
    8. NI PXI-6602
    As attached in the pictures, only the NI PXIe-6556 are detected and the green LED is on. But the other devices are not detected and their green LEDs are off. 
    I have used these NI PXI-4071 and NI PXI-5922 before for measurement and they worked well. Several days ago I replaced NI PXIe-6556 with NI switch NI PXIe 2527, and the new device are detected.
    But after I want to use other devices again, I found that other devices cannot be detected.
    Could anybody help me to solve this problem?
    Thank you before
    Attachments:
    NI error 2.JPG ‏116 KB
    20150413_120628.jpg ‏2743 KB

    Hello bilox,
    This is certainly strange and unexpected, so let's see what other information we can dig up about your system to identify the root cause of this issue, as there could be many different possibilities to sort through.
    The first thing NI support will typically ask from you is a MAX report that details the system software and the hardware as reported by MAX. You can find out how to generate the report here: Using MAX Technical Report to Document Measurement & Automation Explorer (MAX) Configuration Informa...
    Besides this, I'll go through a checklist of items to help narrow down the reason for this issue.
    Check your device manager to see if the instruments not detected by MAX are identified by your OS. If so, it could indicate MAX is not appropriately displaying your instruments. You can also check here if the system is identifying the devices and their appropriate device drivers correctly.
    Speaking to device drivers, are they up to date for the OS you are using? The version of MAX? Are you coming off an image or a clean machine that used to have device drivers on it? Did you uninstall any SW lately? The device drivers are required to identify SW in your machine.
    If you remove all the HW in your chassis and add each instrument one at a time, are they detected? This takes some time, so if it were me, I'd remove the 6556 to see if any other instrument is detected. If so, then take those results and mix/match to try and identify if a particular instrument is causing the behavior.
    If you have a spare chassis, try changing it out to see if the issue follows the chassis, the controller, or the instrument.
    Hopefully, this provides enough information to continue troubleshooting and finding the answer to the issue. If you need more online resources, you may always visit ni.com and ni.com/support for more help online. If you continue having issues, you may want to email/call one of our Application Engineers to assist you with further troubleshooting steps for your system.
    Thank you for the follow up information.
    Kyle A.
    National Instruments
    High Speed Digital I/O Product Support Engineer - R&D

  • Pxie-1073 trigger

    Can the PXIe-1073 drive/monitor the PXI trigger lines?

    Hello Robert,
    I have not seen any software that can monitor and display the information of the PXI Trigger Bus that is in the backplane of the PXI. A workaround is using an external card that can be used to export this lines to the front panel of the PXI. Some of the cards that can help with this are the 6652 or the 6653 timing and synchronization cards.
    On the following link you should be able to see an example on how to export a Trigger to a PFI line:
    https://decibel.ni.com/content/docs/DOC-2350
    Also, I would like to show you some articles that speaks how to manipulate the trigger lines:
    Using PXI Timing and Triggering Functionality
    http://digital.ni.com/public.nsf/allkb/BD37A128B1DF27F3862570FC0072359D
    Routing PXI Trigger Lines Across the Buses of Multisegment PXI Chassis
    http://digital.ni.com/public.nsf/allkb/CA9A49FA50393C4186256DC200774E2B
    Signal Routing for PXI Devices - NI Digital Waveform Generator/Analyzer Help
    http://zone.ni.com/reference/en-XX/help/370520J-01/hsdio/hsignal_routing_pxi/
    I really hope this answer properly your question. If not, please let me know so I can see how I can assist you further.
    Regards,
    Luis C.
     

Maybe you are looking for

  • Support Package error

    Hi Experts, Currently i am installing suppport package for  PI 7.10. SP : SAP_BASIS. Just newly installed the sap system -> after kernel upgrade, i applied latest SPAM verion - 27. NowBusiness package SAP -basis is in the process. I started the packa

  • Pictures in PDF Forms (Adobe Acrobat Pro 9)

    Hello everyone, I have a situation where I need two drop downs determine which picture to display.  I have been reading on this topic and see that the best solution (that I have come across) would be to make a button into a picture and toggle the vis

  • All my browsers quit upon launch; keychain issue?

    Strange problem, possibly a corrupted keychain issue; any browser I open in my main user; quits and goes poof. But I can open a browser in another user. I rebuilt my directory; repaired my disk; repaired perms...same prob. In one user it says login k

  • Mass Change in PO conditions

    Hi All We have defined a custom condition type in PO. There are some POs which were created long back. Business wants to change the value of this condition type...There are so many POs that business does not want to go to each PO and manually change

  • Creating new pages

    I am writing a cookbook and have finished page 1 but I can't figure out how to get to page 2. I read the response stating to just continue writing; however, I can't just continue with the next recipe because it would cut it in half at the end of the