0

5522A MET/CAL Error

I'm having the issue of my 5522 retaining error prompts made outside of MET/CAL. For instance, "Compliance Voltage Exceeded...", while running something externally, then opening a procedure to run something else, and that error message popping up. The same thing happened with the "12 Hour Zero Needed." I zeroed as soon as I got in to work, and then ran a procedure an hour later, and the first message to pop up inside MET/CAL was "12 Hour Zero Needed."

The 5520 did not save these messages. I'm wondering if this is a glitch particular to me, or if it's a 5522 thing. I can of course "Advance" past the error, but I'm curious as to whether this was intended.

Little more information, when I first configured my system to use the 5522 (it's about 3 days old at my lab, was a demo unit before then), it would spit out switch range notifications even though the procedure didn't require them. I added the alias "5520" to the 5522 and it went away. The system recognizes it as a 5522 so... Idk. Just a little confused.

3 comments

Date Votes
0
Avatar
Chad D.

Hello nci_skye, you are correct, this behavior is intended and operates this way by design to ensure that there are no potential safety concerns.  MET/CAL detects any latched SRQ (service request) which is present in your 5522A due to past activities.   Before launching the MET/CAL procedure, sending a *CLS command (using NI-MAX or another method) will clear the SRQs, or you can inhibit them by sending *SRE 0 (again in NI-MAX or another method), or you can always just cycle the 5522A's power to clear them too.

0
Avatar
Steve Consterdine

Hi Chad,

This appears to contradict Met/Cal's usual behaviour.  For example, in earlier versions, Met/Cal would  automatically perfom this reset for Standards, such as the 5700 and 5500 series etc.  Has this now changed for ALL calibrator's or just the 5522? and I'm guessing the 5502 as well?  Or is my memory playing tricks ;-)

 

0
Avatar
Chad D.

Hi Steve, the first command sent by MET/CAL is an *IDN? query to identify that the instruments available on the bus satisfy procedure requirements.  This is sent before a *CLS;*RST, so any latched SRQs present in calibrators connected to the bus will be detected by MET/CAL's SRQ handler.  To test this, I created a short test case, and turned on IEEE trace mode (Debug > Trace > IEEE-488 I/O) in the 8.0 Editor.

Test Case procedure:

 1.001 5700 1V 1% 2W 2.001 5520 1V 1% 2W 3.001 5522A +Voltage = 1 V 3.002 MATH MEM = MEM1 3.003 MEMCX 1V 1%
 
 
IEEE trace output from running this procedure in Simulation Mode:
ib_wrt : 5 bytes ib_wrt : 0-04 : *IDN? ib_trd : 15 bytes ib_trd : 0-04 : FLUKE,5522A,0,0 ib_wrt : 5 bytes ib_wrt : 0-04 : *OPT? ib_trd : 1 bytes ib_trd : 0-04 : <lf> ib_wrt : 5 bytes ib_wrt : 0-15 : *IDN? ib_trd : 15 bytes ib_trd : 0-15 : FLUKE,5700A,0,0 ib_wrt : 15 bytes ib_wrt : 0-15 : *CLS;*RST;*OPT? ib_trd : 94 bytes ib_trd : 0-15 : "Wideband<sp>Module<sp>","5725<sp>Attached<sp><sp><sp>","5205<sp>Attached<sp> ib_trd : 0-15 : <sp><sp>","5215<sp>Attached<sp><sp><sp>","5220<sp>Attached<sp><sp><sp>" ib_wrt : 5 bytes ib_wrt : 0-11 : *IDN? ib_trd : 32 bytes ib_trd : 0-11 : FLUKE,5520A,0000000,1.3+1.0+1.0+ ib_wrt : 5 bytes ib_wrt : 0-11 : *OPT? ib_trd : 6 bytes ib_trd : 0-11 : SC1100 ib_wrt : 26 bytes ib_wrt : 0-04 : *SRE<sp>104;*ESE<sp>61;*RST;*OPC ib_wrt : 7 bytes ib_wrt : 0-04 : *ESE<sp>60 ib_wrt : 9 bytes ib_wrt : 0-04 : UUT_FLUSH ib_wrt : 16 bytes ib_wrt : 0-15 : *CLS;*RST;*SRE<sp>8 ib_wrt : 28 bytes ib_wrt : 0-11 : *CLS;*RST;*SRE<sp>8;*ESE<sp>1;*OPC ib_wrt : 9 bytes ib_wrt : 0-11 : UUT_FLUSH run : enter procedure "X" run : 1.001 5700 1V 1% 2W

Please sign in to leave a comment.