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

Similar Messages

How to use PXI Star Trigger for PXIe-5663 in PXIe-1075 chassis

HI all,
I have this sytem configuration:
PXIe-8135 controller. Windows 7 64-bit, RFSA 2.7.5. NI-SYNC 3.4.1
PXIe-1075 chassis
PXIe-5663 (2x)
PXIe-6672 Timing & Sync Card (slot #10)
I want to trigger the recording of my Digitizer with an external trigger.
The External Trigger is connected to PFI0 of the PXIe-6672 Timing card.
Then, the PXIE-6672 card routes the trigger to the backplane of the PXIe-1072 (Destination "NISYNC_VAL_PXITRIG0")
The PXIe-5663 are triggered with “NIRFSA_VAL_PXI_TRIG0_STR” as the source.
The trigger fires my PXIe-5663 correctly, but the timing is not tight (> 5ns).
I would like to use the PXI Star trigger instead, I think that I should be able to acheive much better synchronization with this.
But NI-RFSA won't let me do this:
When I try to call
"niRFSA_ConfigureDigitalEdgeStartTrigger(rfsa_session, NIRFSA_VAL_PXI_STAR_STR , NIRFSA_VAL_RISING_EDGE)", I get the error:
"Specified Route Cannot Be Satisfied, Because the Hardware Does Not Support It"
I don't understand why the PXIe-5663E would not be able to use that Route.
Any idea?
Regards,
Serge
Serge Malo, ing.
Concepteur logiciel
Software Developer
T (514) 842-7577 x648 | [email protected]

That explanation isn't quite right. Usually, even PXIe modules have a connection to PXI_Star. The PXIe standard added the PXIe_DStar trigger buses, and it also preserved the PXI_Star bus from the PXI standard.
However, there is an additional twist in this situation. I'm assuming that your PXIe-5663 includes a PXIe-5622 as the digitizer. It turns out that a synchronization technique called NI-TClk has eliminated the need for our more recent digitizers to rely on triggering from PXI_Star. I was able to find some documentation that includes this information, here and here. Given that, I think you have two options that should result in better synchronization.
The first option is to use TClk; I found an example program that demonstrates using TClk to acheive phase coherent signal acquisition across two 5663s. The second option is to use cables of matched length to connect two PFI front panel terminals of the timing board (6672) to the PFI1 front panel terminals of the digitizers (5622). The timing board would accept the external trigger on PFI0 and then issue triggers on PFI1 and PFI2 with around 500 ps of skew (manual, page A-4) . The digitizers would use NIRFSA_VAL_PFI1_STR as the trigger. I hope one of these solutions will meet the demands of your particular application.
I will also follow up with the owners of the RFSA product documentation to see if we can include a note about why PXI_Star is not supported in some cases.
James Blair
NI R&D

PXI-4070 DMM in PXIe-1075 Chassis not found

I have a PXIe-1075 chassis and four PXI-4070 DMMs. I orginally had the four DMMs in slots 2,3, 4 & 5 but descided to move the modules around including two of the DMMs so they are in slots 16 and 17. When I did this the DMMs are not found in Measurement and Automation Explorer. If I remove the module in slot 3 (PXIe-2531) they will reappear. The main reason for moving the modules was to maximize through put because slots 2 through 4 share a PCIe switch (as do slots 15 through 18).
Slots 2 through 5 and 15 through 18 should be hybrid compatiable. Are there rules for mixing hybrid and PXIe modules?

Chris,
I don't know about the original problem, but you can get the reconfiguration effect in device manager. Open device manager, select view->by connection, and then start expanding things until you find your device. On my Windows 7 PC the hierarchy starts with something like [computerName]->[ACPI x64-based PC]->[Microsoft ACPI-Compliant System]->[PCI bus]->[something Root Port]->[PCI standard PCI-to-PCI bridge]...
Go to the PCI-to-PCI bridge listed under the root port and above the devices in your chassis, right-click and select "uninstall". Open Measurement and Automation Explorer and delete the devices (they should be non-present). Then either reboot or go to device manager's munu item action->scan for hardware changes. That should cause Windows to re-find all your devices.
- Robert

[svn:fx-trunk] 11702: ASDoc fix for FLEXDOCS-1075

Revision: 11702
Author:   [email protected]
Date:     2009-11-12 09:29:17 -0800 (Thu, 12 Nov 2009)
Log Message:
ASDoc fix for FLEXDOCS-1075
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXDOCS-1075
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/BorderSkin.as

Using Keysight M9037A Controller in a NI PXIe-1075 Chassis, need to add a slave PXIe-1065 Chassis

Hello,
I have a bit of an odd configuration and I was hoping someone could confirm whether or not the PXIe-8374 will fulfill my needs or not, and if there is some other product that will.
Our master chassis is a NI PXIe-1075. It has a Keysight M9037A controller installed, which is working perfectly with all of the PXI cards we have installed in the chassis. However, we have a PXIe-1065 Chassis that we now need to make a slave to our PXIe-1075. In the case that we were using an NI controller, I know that a NI PXIe-8374 in the master and a NI PXIe-8370 in the slave would be the solution. However, it is unclear to me wheter or not the NI PXIe-8374 will work in a chassis (even an NI chassis) with an non-NI controller. I was hoping someone would be able to clear that up for me.
Thanks,
Alex

Thank you. That's what I suspected, but I wasn't sure.
Part of my confusion came from a paragraph in the related datasheet (found at http://www.ni.com/datasheet/pdf/en/ds-327 ):
"National Instruments provides several chassis expansion MXI products you can use to create multichassis PXI systems that interface to the same system computer. The system computer in the master PXI chassis can be either an NI embedded controller or a PC connected via an NI remote controller."
It kind of implies that the chassis expansion MXI products only work with PCs or NI embedded controllers, and not with other embedded controllers.

Where can I find 3D model step files for PXIe-1073 chassis?

I need 3D model step files for the PXIe-1073 chassis. Does anyone know where I can get them?

Eduardo,
I again apologize for the extremely long delay. Our R&D department has completed your request, and it can be found online, here: http://digital.ni.com/hardref.nsf/websearch/99B2D43123FBABE1862578B60077848F?OpenDocument&node=20053...
Paul Davidson
Sound and Vibration Software Staff Product Support Engineer
National Instruments

PXIe-8370 in PXIe-1075 Chassis cannot seen on MAX

Hi All,
I have 8370 controller and 1075 chassis. I installed all the required software and drivers but I could not see my controller and devices on MAX. In Winwods Device Manager, there is a device as "National Instrument SMBus Controller". In system tab, there are lots of PCI-PCI standart bridges and 2 of them are not installed correctly(yellow pointer).
I have formatted the computer, changed the computer but the problem is same. What are your solution suggestions?
Solved!
Go to Solution.

Hey hwfyn,
The first thing I would check is to make sure that the NI Device Loader Service is running in MAX. If you can see the device installed in Device Manager but it is not showing up in MAX this is usually the reason. For instructions on checking this see the following article:http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649 Please post back with the results of this step.
Regards,
Kevin
Product Support Engineer
National Instruments

Need ac distribution schematic for PXI-1045 chassis

I have a PXI-1045 chassis that the "power on" button doesn't work properly on. The chassis is on all the time. The only way to turn it off and on is to unplug the AC cord or plug it in. I have dis-assembled the chassis and checked/replaced the power switch and the problem remains. I am looking for an AC distribution schematic so that I can further troubleshoot this chassis.
Any ideas on where I can find this?

Hi boog,
Being that your chassis stays on, have you tested your PXI-1045 chassis with the Remote Voltage Monitoring and Control Connector? You should be able to power off the chassis by connecting the Inhibit pin (pin 5) to a Logic Ground pin such as pin 1 or 9. The Inhibit Connector is discussed on page 2-9 of the NI PXI-1045 User Manual.
You may also want to consider sending your chassis in for repair. The KnowledgeBase, here, shows the process for sending your NI device in for repair.
Tunde S.
Applications Engineer
National Instruments

PXIe-1075 Power switch will not turn off chassis

Hi,
I think I am having trouble turning my PXIe-1075 chassis off with the front mounted power switch. When I press the power switch, the green LED will ficker and the PWR LED on my PXIe-8360 MXI card will flicker from green to red and then back to green. I have a PXI-1042 chassis as well that seems to turn off properly. The switch on my PXI-1042 chassis has two positions, but the switch on my PXIe-1075 only seems to have one position. I am in a spot where I will need to power off my chassis to move it occasionally. Does it sound like my PXIe-1075 chassis has an issue? Am I missing something? I also tried holding the power switch. This will cause all the installed modules active light to turn off, but the PWR light on the switch and the PWR light on the MIX card will stay the same.

Hello,
The 1075 has two modes for shutdown. You can select between the modes with the 'inhibit' switch on the back of the chassis. When this switch is in the default position, the chassis will power down when you shut down the controller in the chassis (I'm not sure if it will automatically power down with the MXI connection when you shutdown the PC- I do not believe it will). When the switch is in the manual position, the chassis does not shut down with the controller and you must use the Inhibit signal on pin 5 of the Remote Inhibit and Voltage Monitoring connector. I believe your chassis is in 'Manual' mode. More information on this is available in the manual on page 2-12:
http://www.ni.com/pdf/manuals/372537b.pdf
I do not think that the power button on the front can be used to power off the chassis.
Jon F.
Applications Engineer
National Instruments

PXI 5154 into PXIe-1075 fried socket

So, I just tried installing a PXI 5154 into a PXIe-1075 chassis. I followed the instructions that came with the card, but after powering on the chassis, there was no hardware detection wizard, and no LED light came on. I was going to try it in a different slot, but when I slid the card out of the chassis, I saw that the socket looked burned (see image attached). I'm not sure what I did wrong, and now I'm worried that I might have damaged some of the other cards that were installed in the chassis. So my question is two-fold: 1.) Any idea what went wrong here? 2.) Any way to tell if the chassis itself is somehow damaged? 3.) If the damage wasn't caused by some user-error on my part, is there any sort of warantee / replacement for the card?
Thanks
Solved!
Go to Solution.

Hey,
I just wanted to be thorough about what may have happened in this situation to cause this thermal event. Most often when we see this sort of thermal activity, it is due to a shot in the chassis that may have been caused by bent pins on the back plane.
These sort of events don't happen often, but it is possible that bent pins can occur when a user tries to insert a card into a slot that is not compatible.
If you look on the back of your card, you can see that there is a physical difference between the connectors of the PXI and PXIe cards.
This is a good picture that shows the different types of slots that you can see in a PXI/PXIe chassis. As you can see, there is a difference between timing slots, Express slots, PXI slots, and Hybrid slots. Each of these different types have a different symbol associated with them on the front of the chassis. The different symbols are explained in more detail in this KnowledgeBase article.
What I am hypothesizing may have happened, is that you may have inserted a PXI hybrid card into an express slot. When this happened, it possible that two pins from the backplane of the chassis became jammed into one slot in the digitizer, causing a short.
It is important to be familiar with what types of cards are compatible with the different slots in the chassis. We are committed to making our documentation as clear and as thorough as possible, so if any documentation concerning this is unclear, we are concerned with how we can improve the documentation to account for this.
Regards,
Regards,
Leah
National Instruments
Applications Engineer

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.

Using PXI-6682(H) in PXI Express chassis to replace backplane clock

I have a PXI-6682H in a PXIe-1075 which I use for event timestamping. I also have a PXIe-6672 card in the timing slot.
I would like to replace the 10 MHz backplane clock to use the 6682 as a GPS disciplined oscillator and synchronize multiple PXI chasses.
I understand from the block diagram in the manual that the PXI-6682H does not possess the connection to directly replace the backplane clock as the PXI-6682 does in a PXI chassis.
Is there any way for me to replace this clock? Perhaps using an external connection? If so could you briefly explain how this would work and what software steps would be required?

Hello Gregoryng,
It might work since the PXIe-6672 and the PXIe-6674T are both timing and synchronization modules, but the best option would be the PXIe-6674T, which is able to work with other protocols such as GPS while the other cannot. It seems that in the video they use GPS.
I think the PXIe-6672 will not work for this with the PXI-6682H, but you can give it a try.
The one in the video seems to be a PXIe-6674T.
Regards.
Ernesto.

MAX does not detect my PXI-5122 and PXI-6551 cards in a PXI-1045 chassis.

I have been using a PC with MXI-3 to PXI-1045 chassis to develop LabView TestStand code. Things are fine on my development PC. [Software configuration report attached nireport_rich.txt].
I have a 2nd PC set aside to test my deployment packages. I installed a GPIB card and MXI-3 card in my deployment test PC, and loaded a bunch of hardware drivers. [Report attached nireport_depPC_0006.txt]
All the PXI cards are found just fine when my development PC is connected, but when I power up my deployment PC (with MXI-3 connected to the 1045 chassis) -- I can't import the development configuration [exported from development PC] because the deployment PC does not see the PXI-6551 DIO card in slot 6 [PXI6::10::INSTR] and the PXI-5122 card in slot 13 [PXI8::15::INSTR].
I keep reviewing the hardware driver versions installed, and the only small difference that I see at this point is that the deployment PC has a slightly older version of NI-Switch.
Anybody have any ideas of what I can try next? I'm out of ideas.
. . . . hmmm, can't seem to attach more than one file, so here's the software info on the deployment PC
NI Software Information:
CVI Run-Time 7.0.0.395
NI-DAQ 7.3.0f1
NI-DAQmx 7.3.1f0
NI Script Editor 1.1
NI-DMM 2.3.1
     Soft Front Panel 2.3.0
NI-FGEN 2.2.1
     FGEN Soft Front Panel 2.2
NI-488.2 Software 2.30
IVI Compliance Package 2.2 2.2
LabVIEW Run-Time 7.0
Measurement & Automation Explorer 3.1.1.3003
Measurement Studio 6.0
     For Visual Basic
          ActiveX User Interface 7.0.0.344
          ActiveX 3D Graph 7.0.0.344
          ActiveX DataSocket 4.2.2.1
NI-USI 1.0.2
NI-HSDIO 1.2.1.3
NI-HWS 1.2.2.0
NI-PAL Software 1.8.2.0
NI-SCOPE 2.7.0f5
     SCOPE Soft Front Panel 2.1.0
NI Spy 2.2.0.12
NI-SWITCH 2.30.49153
NI-TClk 1.2
TestStand 3.1
NI-VISA 3.2
     visa32.dll 3.2.0.19
     NiVisaServer.exe 3.2.0.19
     NIvisaic.exe 3.2.0.19
LabVIEW Run-Time 7.1

Hello Maggie,
Appreciate your assistance and reply.
The pxisys.ini and pxiesys.ini files are modified by me with referring to
1)PXI System Alliance PXI-2 SW spec,
2)PXI-6 SW spec,
and 3)pxisys.ini pxiesys.ini generated by MAX v5.3.0f0 with NI PXIe-1075 + NI PXIe-8133.
The content in pxisys.ini/pxiesys.ini generated by MAX looks like simple. Consequently, I modified and checked it line by line according to actual hardware of PXES-2590+PXIe-3975. Then, MAX just list devices as described in the first post. I tried to find the root cause but in vain.
Is this minor issue can be related any incorrect tag lines in pxisys.ini or pxiesys.ini I posted?
Is any suggestion tests I can do to troubleshoot root cause?
Looking forward your reply.
Cheers,
KL Tseng

PXIe 8262 streaming performance with HDD 8264 on a PXIe 1062Q chassis

Hello,
I have a PXIe 1062Q chassis, running Win XP, with one 8262 connected to an HD8264 and two PXIe 6537 installed, all the three board being on the express slots (3, 4 and 5). Running the benchmark application for testing the streaming speed (Win32FileIO) I get something like 100 MB/s with data chunks of about 4 MB, and around 140 MB/s with chunk of 64 M. How can improve these results toward the theoretical limit off 600 MB/s? Is there any software/driver trick to be applied?
And, in case, which is the best way to exploit the 8262 from C++ written code (using the NI libraries)? Is there anything similar to the Win32FileIO library? I tried using the RAID system from a c++ test program, and the performance seems very poor, while I would need, if not the 600 MB/s rate, at least something around 200 MB/s of continuous streaming.
Thanks in advance,
Piero.
Solved!
Go to Solution.

Hi Neil,
I actually have a 8130 controller, and in fact that was not the problem: I found the problem being the file-caching performed by Windows file system. If you use standard fstream calls from C source code you cannot bypass it, but by using Windows native call (CreateFile(...), WriteFile(...) APIs) and setting the flag for no data caching or buffering inside the call, I managed to get the full bandwith of 600 MBytes/s.
Anyway thanks for the quick reply!
Piero
I'm guessing you have a controller that only
supports x1 PCI Express. The PXIe-8130 is our highest-bandwidth
controller, with four x4 links going to the chassis. In the case of
the 1062, each of slots 3, 4 and 5 get a dedicated link from the
controller. x1 links max out at about 200 MB/s and x4 links max out at
800 MB/s.
So your first step is to use an embedded
controller or use MXI Express x4 instead of x1 back to a host
computer. While the PXIe-8130 is the best for high-bandwidth data
transfers, the PXIe-8106 should also be sufficient for your needs.
If
you want to stream data to disk from a PXIe-6537, it is already built
into DAQmx. You simply specify a file name, and the data goes to
disk. If you want to stream *from* disk, you'll have to do that on
your own. Here is a C/CVI example for streaming digitizers to disk
using a C API and the Windows File I/O functions.
Neil
Principal Engineer
National Instruments

How do you configure multiple PXI 1011 chassis' in MAX?

I have two PXI 1011 chassis'. The first has the MXI-3 card hooked to a MXI-3 PC card through fiber. The second chassis has an 8176 controller and the 6052e GPIB card. Both chassis have multiple SCXI cards. The problem is the configuration in MAX. MAX 3 picks up the MXI-3 card and chassis with all the SCXI modules, but will not pick up the 8176 chassis. This 8176 is hooked to the PC through a CAT5 ethernet switch.I know there are problems with multiple chassis configuration, but I'm sure I'm just missing something here.

Hi,
So it sounds like you have two PXI systems that are not connected or related to each other, is that right? Since your PXI chassis connected via MXI-3 is working fine, we�ll take that out of the equation.
It sounds like you are trying to configure your PXI-8176 system as a Remote System through an Ethernet connection. Is your PXI-8176 running Windows (if so which version) or Real-Time (RT) operating system?
If you are running Windows XP on the PXI-8176 and also on your computer you can use XP Remote Desktop to control your PXI-8176 system through Ethernet (see the following link for information on that):
http://digital.ni.com/public.nsf/websearch/C074C33F4DE3FA5186256D3D007788DA?OpenDocument
Another option is to use Remote Device Access (RDA) to cont
rol your SCXI modules and DAQ board (6052E). RDA will only work with Traditional NI-DAQ, it is not supported in NI-DAQmx. I�ve included a couple of links for KB�s that have more information on RDA for you.
http://digital.ni.com/public.nsf/websearch/3a4d2f5f4354e53a862568c0006a8bc0?OpenDocument
http://digital.ni.com/public.nsf/websearch/5CC9792C6CD4A34C862565BC0072D5DF?OpenDocument
If you ordered your controller only with Real-Time on it you can use the following document to configure and troubleshoot your PXI-8176 RT system.
http://www.ni.com/support/install/install_configure_6.htm
I hope this helps you.
Regards,
Doug K.
National Instruments

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

Similar Messages

Maybe you are looking for