LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI-4110 Cards failing since upgrading to Calibration Executive 3.4

Since we upgraded to Calibration Executive 3.4 all of our PXI-4110 Cards have been failing the following:

 

Calibration As Found
Channel As Found DMM Reading As Left DMM Reading Test Value Low Limit Reading High Limit PassFail
2 0.999942 A 0.999942 A 0.25000 A 0.99557 A 0.94065 A 1.00432 A Failed
2 0.999991 A 0.999991 A 0.50000 A 0.99524 A 0.93736 A 1.00474 A Failed
2 0.999761 A 0.999761 A 0.75000 A 0.99370 A 0.94076 A 1.00582 A Failed

 

This failure occurred on 3 brand new cards and I have even tried the last PXI-4110 before upgrading and it also failed these test and when an adjustment is attempted I receive the following error:

 

Error -300010 occurred at Get UserField Data.vi

Complete call chain:
     cex_UtilityGetUserFieldData.vi
     cex_UtilityGetUserFieldDataByIndex.vi
     _NI 4110_Get Channel Range and Level.vi
     Adjust_NI 4110_Current Out Accuracy.vi
at step Adjust Current Output Accuracy

 

I am using a Agilent 34401 for the DMM.

 

0 Kudos
Message 1 of 12
(2,995 Views)

Hi Stubnar,

 

Are you Calibrating in manual mode or auto? Based the Calibration Procedure these are the recomended devices:

 

4110.png

 

 

Best Regards,

Jignesh P

Applications Engineer

Best Regards,
Jignesh Patel
Principal RF Software Engineer
0 Kudos
Message 2 of 12
(2,974 Views)

How do I know if I am doing Manual or Auto? I know that I have to set all the resistance values and change leads for each channel

 

Also I have a:

NI PXI-1036 Chassis

I am not sure what the model of the Power Supply is (we have been using it for over 3 years though.)

For a resistance load we use a combination of a ESI DB877 and a HP 6060B depending on the resistance needed for the test that is failing we use the ESI DB877.

For the DMM We use the Agilent 34401 I have also tried the NI-4071 with the same results.

 

Could any of these be a problem with the new test?

 

0 Kudos
Message 3 of 12
(2,953 Views)

Hi Stubnar,

 

This seems to be an different issue then I had originally thought.

 

When you are using non-recommended devices for calibration what you would generally have to do is select "Enter Unsupported Instruments" in the set up steps and enter your data manually.

 

Since you are getting errors with the PXI-4071 this may be a different issue. Let me take a look into this issue.

 

Best Regards,

Jignesh P

Applications Engineer

Best Regards,
Jignesh Patel
Principal RF Software Engineer
0 Kudos
Message 4 of 12
(2,928 Views)

Hi Stubnar,

 

I need to get few pieces of information from you. I would like for you to generate a MAX Technical report and you can do so by following the instructions here. Along with the Technical report can you also post back with the calibration report? This will help us investigate this issue further.

 

Best Regards,

Jignesh P

Applications Engineer

Best Regards,
Jignesh Patel
Principal RF Software Engineer
0 Kudos
Message 5 of 12
(2,921 Views)

JVP

 

Here are the files you wanted. Sorry this took so long. The hard drive on the computer that we have the Calibration Executive software on died and we had to reinstall everything. So and I tried to run another card with the same results the calibration report I am sending you is from today. I sent the reoprt in two formats XLS and PDF.

 

0 Kudos
Message 6 of 12
(2,897 Views)

Stubnar,

 

Thanks for the information. JVP is out of the office so I will be helping you out for the time being. We will try to get back to you soon regarding next steps.

 

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 


0 Kudos
Message 7 of 12
(2,880 Views)

Any word on this issue yet?

0 Kudos
Message 8 of 12
(2,861 Views)

Stubnar,

 

I am getting your information to the Cal Exec domain experts. I will repost here when I hear back.

 

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 


0 Kudos
Message 9 of 12
(2,846 Views)

Stubnar,

 

One of the initial inclinations after reviewing your reports is that the 3.4 4110.mdb file may be corrupted. I have attached the file here to replace your file. Let me know if this works.

 

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>


0 Kudos
Message 10 of 12
(2,817 Views)