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

Similar Messages

LV12 How to configure PXI-4070 DMM current function?

Dear all
I have a problem about LV12 software to config PXI-4070 DMM current function.
my vi...NI DMM initial >>>NI DMM reset >>> NI DMM Configure Measurement (Current function) >>> NI DMM Reading >>>>
When I testing with my vi, the calibrator (source) error "Current Compliance Voltage Exceeded".
but when I testing with DMM front panel 3.0, the calibrator can generated current and PXI-4070 can reading.
Please help me to solve this problem.
Regard,
Sermsak.
Solved!
Go to Solution.

The error looks like it is related to a power supply or an SMU that is trying to source something out of its specified range.
Info about compliance:
http://zone.ni.com/reference/en-XX/help/370736L-01/ni_dc_power_supplies_help/compliance/
http://zone.ni.com/reference/en-XX/help/370736L-01/nidcpowerviref/nidcpower_query_in_compliance/
Things to consider:
1) Where in the code is the error occurring?
2) Can you run example NI-DMM code? (from Help>>find examples>>Hardware I/O>>Modular Instruments>>NI-DMM)

How can I find an example about acquiring waveform data by software trigger using PXI 4070 DMM?

Anybody could proivde an example or simliar about acquiring waveform data by software trigger using PXI 4070 DMM?
Thanks!

hi there
from the NI main page go to the developer zone http://www.ni.com/devzone/dev_exchange/ex_search.htm. select "LabVIEW" and "Digital Multimeter (DMM)" and search for "4070". then you'll find some examples.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Programmatically get the PXI slot that the PXI-4070 (DMM) is in?

I am looking for a way to find out what slot my DMM's are in and their model and S/N.
So far I have been able to get back the info for NI-Switch devices, DAQs and a range of Pickering Cards.
For the NI-DMM’s I have so far only been able to get the S/N model and name via the IVI Drivers.
I have attached the code I have so far so you can get a better idea of what I am trying to achieve.
Solved!
Go to Solution.
Attachments:
Get PXI Card ID.vi ‏29 KB

Use "niModInst Open Installed Devices Session" for NI-DMM
Then use "niModinst Get Installed Device Attribute" to get the slot number
Returns an integer attribute specified by the attribute ID parameter for a device specified by the session in and index in parameters.
Valid Values
Slot Number—the slot (for example, in a PXI chassis) in which the device is installed. This attribute can only be queried for PXI devices installed in a chassis that has been properly identified in MAX.
Chassis Number—the number of the chassis in which the device is installed. This attribute can only be queried for PXI devices installed in a chassis that has been properly identified in MAX.
Bus Number—the bus on which the device has been enumerated.
Socket Number—the socket number on which the device has been enumerated.
Omar

NI PXI 4070 DMM repair instructions

HI,
Is ther any repair Instructions & maintanance support for PXI DMM 4070?
if so can please share the document

Sorry, I found an help from NI website
It seems that I missed the cable connecting from MUX front to DMM input, as shown in attached file.
It it's correct, please advise me what it the name of that cable?
Thank you.
Van.
Attachments:
9babdcae1525.gif ‏59 KB

Error -1074117754 thrown when sequence tries to initialize PXI-4070

My customer is reporting that when TestStand attempts to initialize hardware at the start of the product test sequences, the system throws an error -1074117754. He believes that it's associated with the PXI-4070 DMM, as he also cannot talk to the card with the soft front panel. Has anyone seen this code before? Any ideas what it means? Any known fixes? Thanks!

Issues concerning this error have typically indicated faulty hardware in the past, so you may have to RMA it. However, before you try that, try the following troubleshooting steps:
- Reboot
- Re-install DMM drivers (make sure to use the newest version: 2.6)
- Try the card in a different PXI slot
- Try the card in a different PXI chassis
- Try a different DMM in the same PXI chassis and see if it works
Again, we've seen this issue before, so if it persists, contact support so you can send it in for repair.
Elijah Kerry
Senior Product Manager, LabVIEW
Follow my Software Engineering for LabVIEW Blog

Pxi 4070 input impedance

I am trying to modify the input impedance of the pxi 4070 dmm with the NI DMM property node. When I set the input impedance to greater than 10 giga ohms, I am getting an error outputted after running niDMM Configure Measurements Digits.vi. The signal that I am measuring is 5V, so I should be able to use the 10 giga ohm input impedance. I set the niDMM Configure Measurements Digits to autoscale. Could this be an issue that the pxi-4070 is not allowed to have its input impedance changed when the dmm is set to autoscale?

You are correct. When the range is selected, the API automatically selects the input impedence. If you need to do this programmatically based on the measurement, then you could use a case structure that checks the range being used and then sets the input impedence based on this. Do you know if the value you are trying to read at the time would set the range to a value that is compatible with the input impedence?
Thanks,
Sean Newton
Applications Engineering Specialist - Semiconductor Test
National Instruments

Pxi 4070 protection

Hello,
I have a PXI 4070 DMM card, and I set the voltage measurement range to 1V. What happens, if the input gets 15V? Will the card be damaged, or is there any protection against higher voltages?

The PXI 4070 does have input protection that is designed to protect the device from overload conditions. In the NI Digital Multimeters Help there is a section called Handling High DC Voltages which says that the input protection will engage when the signal exceeds about 15V when on the 10V range or lower for the PXI-4070. The behavior is that the input will change and look like a constant current.
The input protection circuit will protect your board from damage however I would not recommend designing a test that would rely on this if you can avoid it. It will not damage the PXI 4070 but it will take a little time to recover from this overload state before you can continue to make low voltage measurements. There is a caution about regularly relying on the protection circuit if you have a switch in your system because there will be current transients that can degrade the lifetime of your switch.
Steve B

PXI-4070 with PXIe-1062Q+NIe-8360+Labtop Why? Max not found instrument.

Dear all
my condition
PXI-4070 with PXIe-1062Q+NIe-8360+Labtop
Window XP SP3
NI-DMM 3.1
Why? Max not found instrument.
found PCI Device "PXI10:15::INSTR
see picture
How to fix this problem?
Best Regard,
Sermsak.
Attachments:
PXI-4070.jpg ‏42 KB

Hello,
Is it possible to take another picture of MAX? That one is very pixilated and I can't quite make out the configuration/error. Does the chassis show up? Every now and then MXI compatibility software is needed for certain BIOS versions so this may be the cause. Did the system work ever before?
Thanks,
Eric E.

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

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.

Measuring digital signals coming from the HSDIO (PXI-6542) with the DMM (PXI-4070)

Hello,
in attachment you can find the program I'm using for my measurement: I'm generating and acquiring digital signals with the PXI-6542 and at some trigger point of one of those digital signals I'd like to capture the measured values on a plot with the Digital MultiMeter (PXI-4070).
It does work if you configure the generation repeat mode as continuous, but if you do have a finite repetition (repeat count is 1) it doesn't react on the trigger, as if it can't find a trigger. On the other hand, if you have a finite repeat count of 30 or more it does react and triggers correctly again.
First I though it had something to do with autocalibration before the measurement takes place, but If you do a highlight execution (stepping through the program) it looks like it measures before the generation session is initialized.
Is there a way to measure correctly when the repeat count is only 1?
Thanks in advance,
Jürgen

Hey Jürgen. I apologize that you haven't gotten an answer yet to your post. I looked at your code and had some questions. What is the source of your trigger to your DMM? I see that you're exporting the data active event to PFI1, and your comments indicate that PFI1 and PFI2 are connected to give you a start trigger for your digital acquisition. Exporting the data active event with a finite or continuous pulse should only give you a single edge per run, though - you wouldn't get a pulse each time. Is your trigger coming from a data line? I didn't see any line in your included data that would indicate a single pulse.
The other thing that I noticed is that you've got no timing dependency between your HSDIO code and your DMM code - they're in parallel with each other. Thus you could get different results run-to-run, since it's not deterministic as to which parallel "thread" that LV will start on first. LV may switch back and forth several times, but let's say that LV reaches the HSDIO Start command before reaching the DMM Start command - in that case, the HSDIO device may finish it's entire operation before the DMM ever starts looking for a trigger, and thus never get the trigger at all. I'm not sure why this would explain why you're seeing the finite case work and the continuous case not, but I wanted to point it out because it could bite you down the road.
I hope some of this this helps get you going in the right direction. I'd also suggest posting HW-centric questions in the appropriate form. There are Digital forums and DMM forums that might help you reach people that will be more familiar with your particular hardware.
Chris

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

DMM PXI 4070 synchronisation trigger généré par PXI6229 (Daq M)

Bonjour,
Je cherche a synchroniser 2 DMM PXI 4070 avec un trigger interne.
Les 4070 ne génerant pas de trigger, je me tourne vers une Daq PXI6229 pour le générer.
ci-joint, le code qui ne fonctionne pas, mais qui donne une idée de la fonction...
Quelqu'un pourrait-il me dire ou est l'erreur ?
Les entrées trigger des PXI 4070 sont notifié TTLx ; faut-il router le signal généré par la 6229 ? et sur quelles lignes ? (dev1/pxi_trig0) ?
Merci.
Ludis
Résolu !
Accéder à la solution.
Pièces jointes :
DMM_PXI4070_Sync.Trig_PXI6229.vi ‏30 KB

Bonjour,
La méthode proposée est correcte: il s'agit en effet de générer un signal créneau avec la sortie compteur0 de la carte DAQ et d'utiliser ce signal créneau en tant que trigger pour les 2 cartes DMM.
Le routage du signal peut se faire en externe (cabler physiquement le terminal Counter0 Output de la carte DAQ à l'entrée TRIG de la DMM et choisir cette entrée au niveau de la configuration du trigger de la DMM) ou en interne.
Pour router le signal en interne, il faut utiliser un noeud de propriété de voie pour la tâche compteur afin de reconfigurer le terminal de sortie (voir pièce jointe). On choisira par exemple "PXI Trigger line 0". Au niveau de la configuration du trigger sur la tâche DMM, il faudra choisir en tant que source de trigger la même ligne (TTL0 = PXI Trigger Line 0).
Cordialement,
Thomas B. | CLAD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Inscrivez-vous gratuitement aux Journées Techniques : de l'acquisition de données au contrôle/com...
Pièces jointes :
Reconfiguration du terminal de sortie du compteur à l'aide d'un noeud de prop.png ‏20 KB
Counter Pinout - terminaux par défaut.png ‏40 KB
trig source property.png ‏65 KB

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

PXI-4070 DMM in PXIe-1075 Chassis not found

Similar Messages

Maybe you are looking for