- Other Fluke companies:
- Fluke
- Fluke Biomedical
- Fluke Networks
- Fluke Process Instruments
How MET/CAL Software Determines the 9500B Active Head in v6.1X
Determination of Active Head requirement
MET/CAL software attempts to determine the minimum capability active head which is required to execute a 9500 statement. For example the following statement specifies a 3.2 GHz, 1 Vpp, 50 Ohm leveled-sine wave signal from the 9500:
1.001 9500 3.2GH 1Vpp LS S L
This signal requires at least a 9530 Active Head. However at run time, the statement will also execute if a 9560 Active Head is physically used.
In addition MET/CAL also attempts to determine the output channel that the signal is routed to. If no explicit output channel is specified, channel 1 is presumed. Therefore the above statement, by itself, will generate the following entries in the procedure header:
CONFIGURATION: Datron 9500 (G3)
CONFIGURATION: Datron 9530 on channel 1
(G3) specifies that a 9500/3200 or 9500B/3200 is required.
The output channel may be specified using the M9500 FSC.
1.001 M9500 CH2
1.002 9500 3.2GH 1Vpp LS S L
In this case, the entries in the procedure header would be:
CONFIGURATION: Datron 9500 (C5,G3)
CONFIGURATION: Datron 9530 on channel 2
Note the 9530 is now required on channel 2. (C5) has also been added since Option 5 (five channel output is required).
Now, the above process for determining the Active Head requirement works fine as long as MET/CAL can correctly determine the output channel that will be used at run time. However, problems can occur when MET/CAL procedure writers use a subprocedure to perform test which is redundant over multiple UUT inputs. For example a typical scenario is the following:
The UUT is a four channel oscilloscope.
The manufacturer's service manual lists the steps necessary to perform
a bandwidth test.
The manual then dictates that the test be performed on each input channel.
The procedure writer develops a channel independent subprocedure to perform a bandwidth test.
(c) 2001 Fluke Corporation, All rights reserved MET/CAL Procedure
=============================================================================
INSTRUMENT: Sub Bandwidth Test
DATE: 2001-09-12
AUTHOR: Fluke
REVISION: 1.0
ADJUSTMENT THRESHOLD: 70%
NUMBER OF TESTS: 1
NUMBER OF LINES: 26
CONFIGURATION: Datron 9500
CONFIGURATION: Datron 9530 on channel 1
=============================================================================
STEP FSC RANGE NOMINAL TOLERANCE MOD1 MOD2 3 4 CON
1.001 HEAD ANALOG BANDWIDTH CHECK - CHANNEL [M100]
# .
# .
# .
1.002 9500 0.600Vpp 3MH LS S L
# .
# .
#
1.006 END
Note the subprocedure header only requires a 9530 on channel 1, because no M9500 statement is included. The M9500 statement is omitted to make the subprocedure channel independent.
The procedure writer then writes a main procedure which calls the bandwidth subprocedure for each UUT channel.
(c) 2001 Fluke Corporation, All rights reserved MET/CAL Procedure
=============================================================================
INSTRUMENT: Main
DATE: 2001-09-12
AUTHOR: Fluke
REVISION: 1.0
ADJUSTMENT THRESHOLD: 70%
NUMBER OF TESTS: 4
NUMBER OF LINES: 31
=============================================================================
STEP FSC RANGE NOMINAL TOLERANCE MOD1 MOD2 3 4 CON
1.001 LABEL CH1_BANDWIDTH
1.002 M9500 CH1
1.003 CALL Sub Bandwidth Test
1.004 JMPL CH2_BANDWIDTH
1.005 EVAL dummy
2.001 LABEL CH2_BANDWIDTH
2.002 M9500 CH2
2.003 CALL Sub Bandwidth Test
2.004 JMPL CH3_BANDWIDTH
2.005 EVAL dummy
3.001 LABEL CH3_BANDWIDTH
3.002 M9500 CH3
3.003 CALL Sub Bandwidth Test
3.004 JMPL CH4_BANDWIDTH
3.005 EVAL dummy
4.001 LABEL CH4_BANDWIDTH
4.002 M9500 CH4
4.003 CALL Sub Bandwidth Test
Note the main procedure header does not list a 9500 or any active heads as required. Now if the procedure is executed, the M9500 statements in the main procedure will designate the output channel to be used before each call to the subprocedure. The 9500 run time driver will use this information when the 9500 statement is executed to select the correct output channel. However, when the driver attempts to designate the Active connected to this output channel as "used," an error will be generated. The error at this point is due to the run time driver attempting to use a traceable asset, the active head, which was not required by the main procedure or any subprocedure as indicated in the header.
To avoid this problem, the main or subprocedure header must contain configuration lines for the actual output channels that will be used. The most straight forward way to accomplish this is to include "dummy" statements in the main procedure that force the configuration lines to be generated.
(c) 2001 Fluke Corporation, All rights reserved MET/CAL Procedure
=============================================================================
INSTRUMENT: Main
DATE: 2001-09-12
AUTHOR: Fluke
REVISION: 1.1
ADJUSTMENT THRESHOLD: 70%
NUMBER OF TESTS: 4
NUMBER OF LINES: 51
CONFIGURATION: Datron 9500 (C5,G3)
CONFIGURATION: Datron 9530 on channel 1
CONFIGURATION: Datron 9530 on channel 2
CONFIGURATION: Datron 9530 on channel 3
CONFIGURATION: Datron 9530 on channel 4
=============================================================================
STEP FSC RANGE NOMINAL TOLERANCE MOD1 MOD2 3 4 CON
1.001 JMPL CH1_BANDWIDTH
1.002 M9500 CH1
1.003 9500 3GH 1Vpp LS S L
1.004 M9500 CH2
1.005 9500 3GH 1Vpp LS S L
1.006 M9500 CH3
1.007 9500 3GH 1Vpp LS S L
1.008 M9500 CH4
1.009 9500 3GH 1Vpp LS S L
1.010 LABEL CH1_BANDWIDTH
1.011 M9500 CH1
1.012 CALL Sub Bandwidth Test
1.013 JMPL CH2_BANDWIDTH
1.014 EVAL dummy
2.001 LABEL CH2_BANDWIDTH
2.002 M9500 CH2
2.003 CALL Sub Bandwidth Test
2.004 JMPL CH3_BANDWIDTH
2.005 EVAL dummy
3.001 LABEL CH3_BANDWIDTH
3.002 M9500 CH3
3.003 CALL Sub Bandwidth Test
3.004 JMPL CH4_BANDWIDTH
3.005 EVAL dummy
4.001 LABEL CH4_BANDWIDTH
4.002 M9500 CH4
4.003 CALL Sub Bandwidth Test
4.004 END
- Home
- Products
- New Products
- Electrical Calibration
- RF Calibration
- Data Acquisition and Test Equipment
- Temperature Calibration
- Humidity Calibration
- Pressure Calibration
- Flow Calibration
- Process Calibration Tools
- Calibration Software
- Service and Support
- All Calibration Instruments
- Handheld Test Tools
- Purchase Info
- News
- Training and Events
- Literature and Education
- Service and Support
- About Us