PXI 1010 Chassis power failed.

Now one PXI 1010 backplane power failed on PXI section, but SCXI side can power on.I ever checked nad reset circuit breaker, no help. I need your help! Who will give me a kind hand?

Roger,
If you have already checked the circuit breaker and have verified that it is not tripped, more than likely there is a power failure with the PXI portion of the power supply. I would create a phone service request at www.ni.com/ask. We can only handle returns through our phone support. At that point, if you indicate that you have a damaged product, we can work with you to get it fixed.
Regards,
Andrew M
National Instruments

Similar Messages

  • What is the memory for a NI PXI-1010 Chassis?

    What is the memory for a NI PXI-1010 Chassis?
    If it does contain memory what are the sizes and types? And how can it be sanitized to bring it to an unclassified state?
    Thanks, CT
    Solved!
    Go to Solution.

    1010 is a chassis, and doesn't have memory. Memory is on the controller.

  • Anyone know what can cause the MXI-3 and PXI-1010 chassis to prevent PC bootup?

    Situation: The PC locked up with the display blank. The PC would not bootup (not even POST) after power was cycled (several attempts).
    Resolution: Simple. The chassis power was cycled and the PC was fully operational.
    Background: The PC is a Dell Dimension 733 running WIN98 and used daily for production test. The test program is a combination of TestStand, instrument dll's and Labview.

    Hi,
    If the pci-mxi-3 is locking up the computer the most common cause for this is a bad mxi-3 card. To check this you will want to try the mxi-3 card and chassis with another type of computer. If it doesn't boot in more than one computer of different types you will want to return the board to national instruments for repair.
    Another thing that we have seen in some computers is interference or noise from the power supplies interrupting communication through the mxi-3 devices. The only thing you can really try in this case is to move the pci-mxi-2 card to another slot in the pc and see if it works, or try using a different type of pc.
    Power cycling the chassis is not a valid solution as this will drop the mxi-3 link and then you will no longer be able to talk to de
    vices in the pxi system. You always need to successful power the pxi-mxi-2 card and chassis before you power up your pc.
    Best Regards,
    Amy Hindman
    Applications Engineer
    National Instruments

  • PXI-1042 Chassis power switch LED is steady red

    When attempting to turn on the PXI-1042 Chassis, the power switch LED turns steady green for ~2 seconds, and then turns steady red and remains in this state.  All modules were removed (PXI-8330, PXI-6704, PXI-5411, LeCroy PXD 1021 digitizer) with the AC plug removed, and when powering up the chassis again with the AC plug re-inserted, the LED went through the same process, remaining at steady red.  This issue arose after our building underwent a power outage, and during this outage the chassis was in standby mode, the AC power plug was still attached to the chassis, but the power to the surge protector (to which the other end of the AC power plug was attached) was turned off.  To my knowledge, there were no surges when power to the building was restored.  Does anyone know what could be causing this problem (possible power surge?), and can it be remedied/repaired?  Thanks.

    Thanks for the advice.  I contacted NI but they were unable to offer a cheap replacement fan, nor is our part still under warranty, but I was able to get in touch with the fan manufacturer to get the identical one (Mechatronics P/N: E9225X12B1FSR).  It actually runs on 12 VDC and has a tachometer output, which I'm assuming the chassis reads to determine whether or not to power up all of the attached devices.
      -Myles

  • Can't configure a SCXI chassis (PXI-1010) with a PXI-8176 and a PXI-6052E.

    I have a PXI-1010 chassis with a PXI-8176 running Windows 2000. In the rightmost PXI slot, I have a PXI-6052E. The remaining PXI slots are either empty or have misc. modules in them. I have a SCXI-1520 in the leftmost SCXI slot.
    I am trying to get MAX to recognize my SCXI chassis with the SCXI-1520. When I try to add the SCXI chassis in MAX by right-clicking "Devices and Interfaces" or "NI-DAQmx", I leave the communication mode to communicate on the PXI backplane, choose SCXI slot zero, and find that the communication device field is greyed out where I want to choose the PXI-6052E. For some reason,the wizard used to add an SCXI chassis does not see my PXI-6052E pluged in to the leftmost sl
    ot. Strangely, MAX does see the PXI-6052E in the "Devices and Interfaces" tree. I verified that the 6052E is working correctly. I also verified that the pxisys.ini file is in the WINNT directory. What is the problem?

    I am first trying to install the SCXI chassis using the SCXI 1520 user manual. I put a PXI-6052E in the right-most PXI slot and the SCXI 1520 in a SCXI slot. On page 1-12 of the SCXI-1520 user manual, it instructs me to power up the chassis, right-click on MAX "devices and interfaces", choose the correct chassis, and click finish. The problem is, after I click finish, a window appears that forces me to choose a DAQ device. The SCXI chassis doesn't configure correctly because the wizard doesn't see the PXI-6052E.

  • Max and Automation will not recognize my scxi portion of my PXI-1050 chassis

    I have a PXI-1050 chassis with a PXI-8187 controller.  As most of you know the chassis is a PXI/SCXI combo chassis.  When I go to measurement and autoation explorer using NI-DAQ 6.9.3, and whatever version of explorer that comes with that,  All my devices are listed, the PXI-6071, PXI-6030 and 31 etc.  But when I right click on the device and create a new device the option I have to use is PXI-1010 chassis, becuase there is no option for a PXI-1050.  The entry is created but it will always fail the self check.  "Unable to test chassis at this time".  Anyone familliar with this problem?  I looked on NI.com to find a PXISYS.ini file for this chassis but with no luck. 
    Thanks
    Bill

    Bill,
    The PXI-1050 must be configured as a PXI-1010 chassis in Traditional DAQ. The PXI-1010 and PXI-1011 are legacy versions of the PXI-1050 and PXI-1052 chassis, respectively, but Traditional (Legacy) NI-DAQ only has native support for the legacy version of the chassis. But the two chassis are virtually the same.
    Also you might consider upgrading to the newer version of the Traditional DAQ driver. It can be downloaded for free by going to www.ni.com and then clicking on Drivers and Updates. Currently the newest version is 7.4.2.
    Have a great day,
    Brian P.

  • 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

  • How to install a pci-6030e in a pxie-8102 chassis

    I removed a PXI-6030E multifunction IO card from a PXI-1010 chassis, which is installed in a SCXI backplane.  I can now see the device in Devices and Interfaces under the PCIe-8102 chassis, but it only lets me use a visa test panel.  I have no idea how to use the visa test panel and none of the options make sense.  From everything I've read, I should be able to use this device through DaqMX, but when I try to add a new DaqMX device, and select new analog voltage input -- or any input for that matter -- it says no supported devices found.  I'm totally lost, but i know on the old PXI box it was able to show up through DawMX, but I think that was because it was on the SCXI backplane.  I don't understand what's going on, but surely this isn't NI trying to force me to use SCXI is it?? I'm trying to resurrect this PXI card because i need to make some simple analog measurements and it seems a shame to replace it considering all the money i spent on it before.

    HI David,
    The behavior that you are seeing is definitely odd. When you are measuring the dedicated 5V output with your DMM what ground are you referencing? After you click Run on the Test Panel when measuring an AI channel you see a constant 10V, correct? Which pins is your input signal connected to when running this test?
    Finally, what is the other chassis that you have which was working?
    Brian H. -- Applications Engineer

  • MIO 6070E doesn't work properly in PXI 1010

    How do you do?
    I'm trying to set a DAQ/condtol system with PXI 1010 chassis and LabVIEW. The hardware are PXI 1010, MIO 6070E, SCXI 1163R and 1102 to control relay and log temperature data. The system that consist of SCXI 1000 chassis with 1163R and 1102 via MIO 6062E on same LabVIEW code works properly. However, SCXI 1163R and 1102 that doesn't worked simulataneously in PXI 1010 chassis via MIO 6070E with muliplexed connection. If temperature can be get and relay doesn't work and vice versa if relay work. When I change the connection of 1163R from 6070E to DIO 6602 in MAX, both of function works simultaneously. But I think it's not all right.
    Surely checked MAX and even pxi.ini file. And no suggestion from Korean expert
    except it's wierd and time has passed meaninglessly. Beg your help.

    Dear Mr. Spencer,
    Thank you very much for your answer.
    I'm trying to control electric devices with relay by 1163R and get temperature data from those devices by 1102 SCXI module. I checked the jumpers in 1163R for MIO and connected two modules to 6070E for PXI in MAX. However the operation is still impossible.
    As you expected, I receive error code 10007 or 10004 when I stop the operation. Frankly I don't know what the error messages means because there was no error when I developed the LabVIEW code in 6030E and SCXI 1000 chassis.
    Wishing your kind respose again,
    Best Regards,
    Sung Ki Kim

  • Fix for PXIe-1075 Chassis 3.V V Drift?

    I have a PXIe-1075 chassis which is exhibiting the type of voltage drift behavior described in Document ID 52DD5OL3.  The serial number matches with the numbers described in the document as one of a series which should be returned to NI for repair.
    As I'm on quite a tight budget, and the unit was purchased used (on Ebay), I'm wondering if anyone out there has any familiarity with this problem, and the manner of repair required.  I'm assuming that warranties are way out on this one.  I might attempt the repair myself.
    The KnowledgeBase document suggests that the problem is related to a connector problem on the PXIe-1075 chassis power shuttle.  Can anyone suggest more specifically which connector is the problem, and how it might be corrected by a capable, enthusiastic, and adventurous engineer?
    Thanks!
    Jon

    Hello Grandmaster_P!
    The unit's S/N: V08X16632
    Once again, this unit was purchased second-hand.  Can I still get warranty work on it?  It was originally a part of NI's RF road show, but ended up on ebay a few years back, where I purchased it from a freight recovery warehouse in Salt Lake City, UT.
    If it was not covered, have you any idea what this sort of repair might cost?
    Thanks!
    Jon

  • Automatic power-down of PXI-1033 chassis. Noisy chassis fan.

    I went to use my PXI chassis today. I always keep it powered, but today it wasn't on when I went to use it. Turns out that there's an automatic power down if the fan 'fails'. So I removed the chassis power, and then repowered the chassis. Heard a noisy fan - like one of the blades were hitting something solid. And I only heard something when the chassis was in the 'big fan down' orientation It was the big fan on the 'bottom' of the unit which cools the boards. To fix this, I removed the air filter, and then the wire screen, and then the wire fan protector. I rebent the 4 legs of the wire fan protector (be sure to rebend both elbows of each leg) so that it sits farther away from the fan blades. Put it back to gether, and now no sound.
    Solved!
    Go to Solution.

    Apparently my PXI chassis is part of a 'fan replacement' recall.
    See http://digital.ni.com/public.nsf/allkb/B9BB6E483EDB5353862578180081FA6A

  • PXI Chassis Power LED Flashing Red: What to do?

    My NI PXI-1042 keeps blinking red the Power LED. I know it means the voltage is out of the specs. What to do?

    FilipeTaveiros wrote:
    But it is not continuously red.. It is blinking red.. Thanks for your help. Anyone? 
    This is copied right out of the manual: 
    The chassis power switch has an integrated LED. This LED indicates one
    of three different conditions:
    • If the power switch LED is steady green (not flashing), the chassis is
    powered on and operating normally.
    • If the power switch LED is flashing green, the air-intake temperature
    has exceeded the chassis operating range.
    • If the power switch LED is flashing red, the power supply outputs are
    not within voltage regulation requirements.
    You either have a power supply problem, or you are loading it down with too many modules.  Try running it empty and see what the light does. 
    Using LabVIEW: 7.1.1, 8.5.1 & 2013

  • MAX detects PXI-MXI-4, but fails to detect non-NI chassis

    MAX detects PXI-MXI-4, but fails to detect non-NI chassis. My system is as follow:
    NI PCI-6552 (NI DAQmx device)
    NI PXI-MXI-4/ PXI-8331 (PXI system)
    Elma chassis, with CompactPCI backplane (chassis and cPCI)
    When I run MAX, it successfully detects PCI and PXI with the model number listed. However, the chassis is unidentified. Although my chassis is made by Elma, not NI, it has been confirmed that my Elma chassis, as well as the CompactPCI backplane that comes with the chassis, is compatible with the PXI.
    When I clicked on "other chassis", the chassis.ini (driver) file is asked. But I've confirmed with Elma that no driver is required for the chassis.
    What might be the problem? Thank you very much.
    Manson

    I'm having a similar problem, and from reading the above, it's not clear what one is to do if the chassis and link vendors say "there are no driver files, and none are needed" and NI says, "you must have the appropriate files, which are provided by the vendor."  Specifically, I have a Jasper Electronics PXI chassis and a Hartmann StarFabric link (PCI bridge).  My NI devices in this chassis (6071E, 6533) have always worked fine, and MAX displays them correctly under Traditional Devices and under DAQmx Devices.  The PXI chassis shows up as "unidentified" in MAX, but this has never caused any problems before (and I've seen the same benign error with other non-NI PXI chassis).  However, now that I'm using DAQmx, I'm trying to do the following:
        DAQmxConnectTerms("/Dev3/PXI_Trig0", "/Dev3/PFI5", DAQmx_Val_DoNotInvertPolarity);
    where Dev3 is a PXI-6533.  When I start my task, I get the error message "Driver cannot complete the route, because the only way to make the route requires a trigger bus line, and no trigger bus has been configured in MAX for this device."  The documentation seems to imply that identifying the chassis will automatically create or recognize the appropriate PXI trigger lines.  Since the vendors don't supply any ini files, I tried faking it out as as PXI-8150 system with a PXI-1000 chassis, using the NI ini files; this resulted in entries for both NI cards appearing under "Chassis 1 (PXI-1000)", e.g.
    PXI5::11::INSTR (PXI-6533)
    PXI5::12::INSTR (PXI-6017E)
    although their properties (in the pane to the right of the tree view) show their chassis and slots as "unknown."  When I run my code, I still get the error message about needing to configure a trigger bux in MAX.  Just for grins, I tried the same thing but with RTSI0 instead of PXI_Trig0, and got the same error.  I created an RTSI cable under DAQmx Devices in MAX, and that made no difference.  Help!
    Thanks,
    Larry

  • PXIE-1065 Chassis makes clicking sound and will not power up.

    Came in from the weekend to my few week old PXIe-1065 chassis making a clicking sound near the ac power cord and it will not power on. I removed all the cards from the chassis and it stops clicking, but as soon as I replace the controller (PXIe-8133) it starts clicking again. Is this an ac power supply failure in the chassis. I also noticed there was no filter elements over the fans in the rear of the chassis like my smaller (PXIe-1082) chassis. Could this have led to the failure?
    -Jeremy

    Hi uyt,
    There are a few troubleshooting steps to take here that might show where the problem lies. Have you tried any other embedded controllers in the control slot of this chassis? Do they show the same behavior? Have you tried that controller in your other chassis? Depending on which one the issue follows, I would be inclined to guess that part is damaged in some way and needs to be RMAed.
    In response to your suspicion: I would be extremely surprised if you were delivered a part without a physical component and many of our newer chassis do not have the fan filter you are referring to, so that is likely not the issue.
    Feel free to call in to our support line at 866-275-6964 to troubleshoot the system with one of our engineers before RMAing the device.
    Ben R.
    Modular Instruments Product Marketing Engineer
    National Instruments

  • MAX PXI-1010 test fails to find SCXI modules

    I cannot get MAX PXI-1010 test to find SCXI-1104 modules installed. They are connected to DEVICE 1: PXI-6040E (through PXI-SCXI Internal Bus). I'm am running Windows95, Labview 5.1, MAX 1.0.1. DAQ driver 6.5.1. I tried removing and replacing the PXISYS.INI file but this did not help. Embedded Controller is a PXI-8156. Tried two different chassis and a different DAQ card. I even removed each card and checked all the connectors and tried only one module, still no luck. Missing?

    Hello,
    Is this module an 1104 or an 1104C? Are you missing any other modules that are installed or is it the just the 1104 that can't be found? Have you tried using a different 1104? Make sure that your controlling DAQ device is installed in the right-most PXI slot.
    If none of these suggestions help, try uninstalling and reinstalling NI-DAQ. Let me know the results of these suggestions.
    Sincerely,
    Sean C.

Maybe you are looking for

  • SSO within XI

    Hello all, I implemented SSO on one System and it's working fine withing the "java world". The spring form java-world into abap world is working also. But the spring from abap-world into java-world is not working. Each time when I invoke one transact

  • UDV Syntax Issue

    Hello Experts, The following UDV code works until I add the WHERE clause, at which time I get a syntax error near keyword WHERE: DECLARE @x INTEGER SET @x = $[$3.2.NUMBER] WHERE $[$3.1.0] = 'Mileage' SELECT CASE WHEN @x BETWEEN 1 AND 19 THEN 10 WHEN

  • Adobe Acrobat 7.0 no longer converts docs to pdf

    How can I get filemaker activated again? I keep receiving an error message and update but it doesn't take. Am I just sol becasue I'm now using Office 2007? Thanks!

  • Rework activities in operation level in routing

    HI SAP GURUS, As per blue print   rework is to be treated  as a additional operation in the routings, where ever required. In shop floor control activities  client  requires for a check for rework activity  in each operation level , they have 21 oper

  • IPhone sync error when trying to back up locally

    Whenever I try to get a backup on my local hard drive I get an error that states "iTunes could not back up the iPhone "[iphone name]" because an unknown error occurred (0x2411F865).  Does anyone know how to fix this? Btw, I have an iPhone 4S if that