-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

MET/CAL V7.20 Service Pack 1

Jan 09 2008

File name "readme720sp1.txt"

-------------------------------------------------------------------------------
Section 1:  Table of Contents -------------------------------------------------
-------------------------------------------------------------------------------

	1. Table of Contents

	2. Introduction

	3. Problem Reports

                Corrections made between V7.20 and V7.20 SP1.

	4. Enhancements

		Post-V7.20 enhancements included in V7.20 SP1.

	5. Beta Features

-------------------------------------------------------------------------------
Section 2:  Introduction ------------------------------------------------------
-------------------------------------------------------------------------------

	MET/CAL V7.20 SP1 is a service pack that corrects a number of defects
	in MET/CAL V7.20.  In addition, MET/CAL V7.20 SP1 implements a number
	of product enhancements.  Refer to sections 3 and 4 below for details.

	Refer to "readme720.txt" for a description of enhancements and
	corrections in V7.20.

	You must have MET/CAL V7.20 (or later) installed before installing
	MET/CAL V7.20 SP1.

	V7.20 SP1 includes:

		(1) Instructions for installing the service pack:

			MC720SP1_Instructions.txt

		(2) A readme file that describes all of the changes since
		    V7.20:

			readme720sp1.txt

		    (This is the file you are currently reading.)

		(3) New MET/CAL Editor executable:

			mce32.exe

		    The version is 7.20x.

		(4) New MET/CAL Run Time executable:

			mcr32.exe

		    The version is 7.20x.

		(5) New MET/TRACK executable:

			mettrack.exe

		    The build # is 444.

		(6) Updated ".ini" file for flexible standards:

			user_config_instr.ini

		(7) Dynamic link libraries:

				dblicenz.dll
				genrpt.dll
				metgendb.dll
				rpt32.dll
				text.dll

		    Some of the DLLs are unchanged from the V7.20 release.
		    However, "metgendb.dll" and "text.dll" have been updated.

		(8) Updated MET/CAL message file:

			mctext.mdb

		    New messages have been added.

		(9) Updated on-line help files.

		    All on-line help files changed since the V7.20 release
		    are included in V7.20 SP1:

			5320.hlp
			5520.hlp
			8560.hlp
			8566.hlp
			8568.hlp
			8590.hlp
			8846.hlp
			acc.hlp
			ask.hlp
			disp.hlp
			eval.hlp
			head.hlp
			_ieee.hlp
			ieee2.hlp
			m4418.hlp
			m4419.hlp
			m8901.hlp
			m8902.hlp
			math.hlp
			mem2.hlp
			memc.hlp
			memi.hlp
			mess.hlp
			metcal.hlp
			n5531.hlp
			opbr.hlp
			port.hlp
			reset.hlp
			rslt.hlp
			set.hlp
			vset.hlp
			wait.hlp

		(10) Updated guardbanding documentation:

			Guardbanding.pdf

		(11) Updated and new accuracy files:

			11667a.acc
			11667b.acc
			1403-d_100pF_95_1yr.acc
			1403-g_10pF_95_1yr.acc
			1409-1000uF_95_1yr.acc
			1409-100uF_95_1yr.acc
			1409-10uF_95_1yr.acc
			1409-f_1nF_95_1yr.acc
			1409-l_10nF_95_1yr.acc
			1409-t_100nF_95_1yr.acc
			1409-y_1uF_95_1yr.acc
			271.acc
			29a.acc
			3336a.acc
			3336b.acc
			3336c.acc
			4418.acc
			4419.acc
			5320.acc
			5320a_load.acc
			5520.acc
			5520_99.1yr
			5720.acc
			5720_95pct_180dy.acc
			5720_99.1yr
			83484a.acc
			83630b.acc
			8508.acc
			8508a_7000k.acc
			8560.acc
			8566.acc
			8568.acc
			8590.acc
			86100a.acc
			8842_99_1yr.acc
			8901.acc
			8902.acc
			8903.acc
			9100.acc
			9640.acc
			Fluke_80K-15_1yr_95CF.acc
			Fluke_80K-6_1yr_95CF.acc
			Guildline_9211A_1yr_95CF.acc
			Guildline_9336_100G_1yr_95CF.acc
			Guildline_9336_100M_1yr_95CF.acc
			Guildline_9336_100T_1yr_95CF.acc
			Guildline_9336_10G_1yr_95CF.acc
			Guildline_9336_10M_1yr_95CF.acc
			Guildline_9336_10P_1yr_95CF.acc
			Guildline_9336_10T_1yr_95CF.acc
			Guildline_9336_1G_1yr_95CF.acc
			Guildline_9336_1P_1yr_95CF.acc
			Guildline_9336_1T_1yr_95CF.acc

-------------------------------------------------------------------------------
Section 3:  Problem Reports  --------------------------------------------------
-------------------------------------------------------------------------------

	----> 8920 FSC Readings Not Valid with NMEAS > 0 (with MOD4 blank,
	      'N', or 'C')

		Report Number:  45445
		Resolved:       Jan 09 2008
		Application:    MET/CAL

		In MET/CAL V7.20, and prior versions, the 8920 FSC does not
		store valid readings in memory register MEM when NMEAS is
		greater than 0 and the MOD4 field contains any code other than
		'S'.

		This error has been present since July 2002.

		The only easy work-around is to use the 8920 FSC with NMEAS
		set to zero.

		V7.20 SP1 corrects this problem.

	----> P525 FSC Automatic Connection Message Fails with P03 Pressure Module

		Report Number:  45443
		Resolved:       Jan 09 2008
		Application:    MET/CAL

		In MET/CAL V7.20 automatic connection messages for the 525
		FSC with the P03 pressure module do not work.

		For example:

			P525 0.300psi 4% P03

		fails due to a missing connection message.

		The error message generated is:

			E3186: No connection message for pressure module
			       525A-P03 (device code 176).

		V7.20 SP1 corrects this problem.

	----> 8845 FSC Generates Accuracy Lookup Error When Range Locked To
	      750 VAC In Fast Mode ("D4") With Configured 8846A

		Report Number:  MC-3437, MC-3438
		Resolved:       Jan 03 2008
		Application:    MET/CAL

		In MET/CAL V7.20, when the 8845 FSC is used with a configured
		Fluke 8846A an accuracy lookup error occurs in the 750 VAC
		range in "fast" mode.

		For example, the following statements cause this error to
		occur when used with an 8846A:

			1.001  M8845  RNGLK 750V
			1.002  8845   230.0V	     50H	       D4 N  2W

		V7.20 SP1 corrects this problem.  The driver now uses the
		"1000V" section of the accuracy file for both the 750 and
		1000 VAC ranges, and the 8845 accuracy file has also been
		updated to accomodate this driver change.  An updated 8845
		accuracy file ("8845.acc") in included in V7.20 SP1.

	----> 5320 Driver Reports Operation Complete (OPC) Timeout When
	      Line/Loop Scan Or Manual Mode Selected

		Report Number:  MC-3356
		Resolved:       Jan 02 2008
		Application:    MET/CAL

		When the 5320A performs a scan it may take up to 38 seconds
		when Line/Loop mode is selected, and Line/Loop is set to
		SCAN or MAN.

		In MET/CAL V7.20 the OPC setup timeout is set to 10 seconds
		unconditionally.  This means that an OPC timeout will occur
		if the 5320A performs a scan that takes longer than 10 seconds.

		V7.20 SP1 increases the timeout to correct the problem.

	----> 5320 FSC High Resistance Upper Limit Incorrect

		Report Number:  MC-3433
		Resolved:       Jan 02 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the high resistance upper limit enforced
		by the 5320 FSC is incorrectly set to 100 GOhm.  V7.20 SP1
		corrects the limit.  The limit is now set to 10 GOhm.

	----> 5320 Driver Fails When Action is "Slew"

		Report Number:  MC-3435
		Resolved:       Dec 07 2007
		Application:    MET/CAL

		In MET/CAL V7.20 statements that specify "Slew" as the action
		fail to execute correctly.  The 5320A reports the error:

			-113,"Header error"

		The underlying problem was that the 5320A run time driver
		did not include "SAFety" in the SCPI command header.

		V7.20 SP1 corrects this problem.

	----> 5320 Slew Dialog Shows Incorrect Resolution When Using
	      Resistance Multiplier

		Report Number:  MC-3434
		Resolved:       Dec 07 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 driver's slew dialog does not
		display the correct resolution when the procedure statement
		includes the parameter "ResistanceMultiplierOn".

		V7.20 SP1 corrects this problem.

	----> VSET Help File Does Not Document "Tol_Ref = System_Actual"

		Report Number:  44250
		Resolved:       Nov 26 2007
		Application:    MET/CAL (Documentation)

		MET/CAL V7.20 added support for the specification of
		"System_Actual" as a valid value for the VSET "tol_ref"
		parameter.  However, the on-line help for the VSET FSC failed
		to document this change.

		V7.20 SP1 includes an updated VSET help file that documents
		the change.

	----> Table Permissions Displayed Incorrectly for Segregate User

		Report Number:  MC-3429
		Resolved:       Nov 16 2007
		Application:    MET/TRACK

		In MET/TRACK V7.20, if a user is assigned to a segregate,
		it is possible for the table permissions to be displayed
		incorrectly.  The problem is that the query issued to the
		database to retrieve table permissions does not filter based
		on the user's segregate.  Permissions for the base tables
		may appear to "randomly" reset privileges for segregate views.

		V7.20 SP1 includes an updated version of MET/TRACK that
		corrects this problem.

		MET/TRACK Build #444 or later is required.

	----> 5500 & 5520 Evaluations in Some Measurement Modes
	      Fail When NMEAS > 1

		Report Number:  44800
		Resolved:       Nov 06 2007
		Application:    MET/CAL

		In MET/CAL V7.20, and earlier versions, 5500 and 5520 FSC
		evaluations in certain measurement modes fail when measurement
		uncertainty is enabled and NMEAS > 1.

		The problem affects the following modes:

		5500A
		MOD3    Mode
		----    ----
		TN      Thermocouple Measurement (open TC detection off)
		ZM      SC600 UUT Input Impedance Measurement

		5520A
		MOD3    Mode
		----    ----
		HM      Humidity Measurement
		TN      Thermocouple Measurement (open TC detection off)
		ZM      SC600 or SC1100 UUT Input Impedance Measurement

		For example:

			ASK+ K U
			VSET NMEAS = 2
			5520         50.00Z         1.0%          ZM 2W

		demonstrates the problem.  The problem is that the UUT value
		("UUT Indicated") is reported as zero.

		The problem has been corrected in V7.20 SP1.  V7.20w or
		later is required.

	----> 8901 & 8902 FSCs Updated for AM/FM Residual Specs

		Report Number:	MC-3420,MC-3421,MC-3422,MC-3423,MC-3424,MC-3425
		Resolved:       Nov 05 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the 8901 and 8902 FSCs have been modified
		so that:

		(1) When the M8901 FSC Nominal field specifies a Modulation
		    Frequency of 0 Hz, and the 8901 MOD3 field is "AM",
		    Residual AM accuracy is returned for the measurement.

		(2) When the M8901 FSC Nominal field specifies a Modulation
		    Frequency of 0 Hz, and the 8901 MOD3 field is "FM",
		    Residual FM accuracy is returned for the measurement.

		(3) When the M8902 FSC Nominal field specifies a Modulation
		    Frequency of 0 Hz, and the 8902 MOD3 field is "AM",
		    Residual AM accuracy is returned for the measurement.

		(4) When the M8902 FSC Nominal field specifies a Modulation
		    Frequency of 0 Hz, and the 8902 MOD3 field is "FM",
		    Residual FM accuracy is returned for the measurement.

		This enhancement involved changes to both the 8901 and 8902
		FSCs, as well as changes to the corresponding accuracy files.

		V7.20w or later is required.

	----> VSET On-Line Help Fails to Document TOL_REF = SYSTEM_ACTUAL

		Report Number:  44676
		Resolved:       Oct 31 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the VSET/TSET/INI parameter TOL_REF was
		enhanced to support a new value ("SYSTEM_ACTUAL").  This was
		documented in the V7.20 readme file, but was not documented
		in the on-line help for the VSET FSC.

		V7.20 SP1 includes updated on-line help for the VSET FSC
		that covers TOL_REF = SYSTEM_ACTUAL.

	----> No Error Message for Invalid NVI FSC Dimensionless Numeric Value

		Report Number:  44559
		Resolved:       Oct 25 2007
		Application:    MET/CAL

		In MET/CAL V7.20, and earlier versions that support NVI FSCs
		(not including the 6100 FSC), NVI statements that specify an
		illegal value for a parameter that requires a dimensionless
		numeric value fail to generate an error message.  The error
		is detected -- MET/CAL does not compile the statement,
		but it's confusing due to the lack of an error message.

		For example, the statement:

			5320 TripCurrentMultiplier = TCM

		cannot be compiled, but no error message is generated.

		FSCs affected are 5320, 9640, N5531, and PSA.

		V7.20 SP1 corrects this problem.

		Requires V7.20v or later.

	----> High Voltage Danger Window ("Safety Symbol") May Be Off-Screen

		Report Number:  44556
		Resolved:       Oct 25 2007
		Application:    MET/CAL

		In MET/CAL V7.20, and earlier versions, the safety symbol
		(i.e., the high voltage lightning bolt warning) is positioned
		close to the upper right corner of the parent window (Run
		Time or Test Run).

		This means that if the user positions the parent window so
		that the upper right corner is substantially off-screen,
		the safety symbol window may be either partly or entirely
		off-screen when it pops up.

		In MET/CAL V7.20 SP1 the initial position of the "Safety
		Symbol" window has been adjusted to prevent the window
		from being off-screen, regardless of the position of the
		parent window.

		V7.20v or later is required.

	----> Due Date Calculated Incorrectly When Invalid Cal Interval
	      Type Specified

		Report Number:  MC-3270
		Resolved:       Oct 15 2007
		Application:    MET/TRACK

		In MET/TRACK V7.20 (Build #434) is a user enters an invalid
		cal interval type (for example, "Y"), MET/TRACK calculates
		an incorrect due date.

		In V7.20 SP1 MET/TRACK has been changed so that if a user
		enters an invalid interval type, a pop-up error dialog
		is displayed.

		Build #443 or later is required.

	----> MET/CAL Fails To Close Package File After Unpack Operation

		Report Number:  43811
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		In MET/CAL V7.20, the Editor does not close a package file
		(<file>.pkm) after completing an unpack operation.

		Not closing the package file prevents it from being deleted
		until the Editor is closed.

		MET/CAL V7.20 SP1 resolves this problem.

		V7.20u or later is required.

	----> Leakage Current Documented Incorrectly for Differential and
	      Passive Modes in 5320 FSC On-Line Help

		Report Number:  MC-3407
		Resolved:       Oct 11 2007
		Application:    MET/CAL Documentation

		In MET/CAL V7.20 the "LeakageCurrent" section of the 5320
		help file does not correctly describe the way the FSC
		(driver) functions.

		V7.20 SP1 includes an updated 5320 help file that corrects
		the documentation.

	----> 5320 Statement Using Ground Bond Resistance Mode Generates
	      Accuracy Lookup Error When Evaluation Quantity is "MaxCurrent"

		Report Number:  MC-3406
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		In MET/CAL V7.20 there's an accuracy file lookup error when
		using the 5320 FSC in ground bond resistance mode when the
		evaluation quantity is "MaxCurrent".

		An example of a statement that generates the error is:

			5320 Mode=GBR; Res=0.025 Ohm +MaxCurrent=10 A; Oper

		The error message generated is:

			E132: FSC 5320 required accuracy data not found in
			      Accuracy file.

		V7.20 SP1 resolves this problem.

		The solution required a change to the MET/CAL FSC, not the
		5320 accuracy file.

		V7.20v or later is required.

	----> 5320 Statement Using High Resistance Mode Generates Accuracy
	      Lookup Error When Evaluation Quantity is "MaxVoltage"

		Report Number:  MC-3405
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		In MET/CAL V7.20 there's an accuracy file lookup error when
		using the 5320 FSC in high resistance mode when the evaluation
		quantity is "MaxVoltage".

		An example of a statement that generates the error is:

			5320 Mode=HR; Res=0.5 MOhm; +MaxVoltage=500 V; Operate

		The error message generated is:

			E132: FSC 5320 required accuracy data not found in
			      Accuracy file.

		V7.20 SP1 resolves this problem.

		The solution required a change to the MET/CAL FSC, not the
		5320 accuracy file.

		V7.20v or later is required.

	----> Copy To C2376 Using Dutch Regional Settings Fails

		Report Number:  MC-3398
		Resolved:	Oct 02 2007
		Application:    MET/TRACK

		In MET/CAL V7.20, using MET/TRACK build #434, copying field
		C2376 may fail when using Dutch regional settings.

		The fractional part of a numeric price value, when using a
		comma (',') as the decimal symbol, is omitted when the copy
		is performed.

		V7.20 SP1 resolves this problem.  MET/TRACK build #442 or
		later is required.

	----> PM 6306 Capacitance Measurement At 100 Hz Fails

		Report Number:  42218
		Resolved:	Sep 10 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 6306 FSC fails when a 1 microfarad
		capacitance measurement at 1 V, 100 Hz is attempted.

		The MET/CAL procedure statements that generate the error are:

			M6306	1V
			6306	1.0000uF      100H	      N  4W

		The commands the MET/CAL driver sends to the PM 6306 to
		implement the MET/CAL statements shown above are:

			*CLS;SIN;MEA_FAST OFF;RNG_HOLD OFF;FRE 100;AC_LEV 1;
			DC_BIAS OFF;PARAM IMP;POS_FIX C;MODE AUTO

		After this command sequence is sent the driver queries the
		PM 6306 to check for errors.  The driver always detects an
		error at that point:

			ERROR 170/ILLEGAL PARMETER.

		On investigation it was discovered that, due to firmware
		differences between the PM 6034 and the PM 6306, the command
		shown above fail due to the inclusion of "POS_FIX C" in the
		command sequence.

		The limitation on the use of the POS_FIX command applies to
		"SIN" mode.  Changing "SIN" to "CONTIN" removes the "ILLEGAL
		PARMETER" error.  However, continuous measurement mode is
		not appropriate for MET/CAL's purpose.

		The PM 6304 and PM 6304C do not have this issue, because they
		don't support the POS_FIX command.  Instead, the "LOCK C"
		command is used with the 6304[C].

		This problem is resolved in MET/CAL V7.20 SP1.  The 6306 FSC
		no longer includes the "POS_FIX" command in command strings
		sent to the instrument.  This change does not affect the
		capacitance value read from the instrument by MET/CAL.

	----> Source Copy To Memo Field Fails

		Report Number:  MC-3266
		Resolved:	Aug 28 2007
		Application:    MET/TRACK

		In MET/CAL V7.20 (MET/TRACK build #434) a source copy from
		any field into a memo field fails because the updated value
		is not saved when the record is saved.

		An example is a source copy from I4260 to C2384.

		The underlying problem is that when copying from one field
		to a memo field, an internal status flag indicating that
		the value of the copied-to field has changed is not set.
		This causes the field to be omitted when the SQL "INSERT"
		statement is constructed to save the record.

		V7.20 SP1 corrects this problem.  MET/TRACK build #441 or
		later is required.

	----> Error Configuring Default Serial Port In Chinese Windows

		Report Number:  MC-3380
		Resolved:	Aug 27 2007
		Application:    MET/CAL

		In MET/CAL V7.20, when running under Chinese Windows, the
		following error may be generated when using the MET/CAL
		"Configuration" menu to set the default serial port to "None":

			E2194: Internal Error: Can't get index for "None"
			       in COMM port combo box.

		V7.20 SP1 corrects this problem.

	----> Segregate User May Encounter Error When Deleting Location Record

		Report Number:  MC-3379
		Resolved:	Aug 23 2007
		Application:    MET/TRACK

		In MET/CAL V7.20, a MET/TRACK error may be generated in the
		following way:

			1) Create a new segregate (such as "test").
			2) Assign an asset with location history to this
			   new segregate.
			3) Associate a user with the new segregate, making
			   sure the security level is 4 or 5 for this user.
			5) Login to MET/TRACK as this segregate user.
			6) Attempt to delete a location record for an asset
			   in the user's segregate.

		V7.20 SP1 corrects this problem.  MET/TRACK build #440 or
		later is required.

	----> MET/TRACK Fails When Customer List Exceeds 32767 Customers

		Report Number:  MC-3375
		Resolved:	Aug 16 2007
		Application:    MET/TRACK

		In MET/CAL V2.0 MET/TRACK generates an overflow error
		when editing the customer list if the number of customers
		exceeds 32767.

		V7.20 SP1 corrects this problem.  MET/TRACK build #438
		is required.

	----> 5320 FSC RCDC With Evaluation Quantity "MaxCurrent" Causes
	      Limits Error

		Report Number:  MC-3373
		Resolved:	Aug 15 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the following "5320" statement:

			1.001 5320 Mode = RCDC; +MaxCurrent = 10 mA;
			1.001 5320 TripCurrent = 10 mA
			1.001 5320 Setup

		generates the error message:

			E1407: FSC 5320: Cannot determine limits for
			       +MaxCurrent in amps.

		V7.20 SP1 corrects this problem.

	----> 9640A FSC Amplitude Modulation Limits Error With Triangle Wave

		Report Number:  MC-3369
		Resolved:	Aug 08 2007
		Application:    MET/CAL

		In MET/CAL V7.20, due to a mistake in the manual, the 9640 FSC
		did not support the true capabilities of the instrument in AM,
		specifically, when using an internal triangle wave.  Using an
		otherwise legal setting for the instrument, MET/CAL returns:

			E7743: FSC 9640: "Modulation Frequency = 200 kHz"
			       is outside the legal range. Limits are 20Hz
			       to 10kHz.

		In actuality, the limits are:

			When carrier frequency < 125 MHz, the allowed
			(triangle) rate is 20 Hz to 220 kHz.

			When carrier frequency >= 125 MHz, the allowed
			(triangle) rate is 20 Hz to 100 kHz.

		The AM limits check has been corrected in MET/CAL V7.20 SP1.

	----> "ZR" Cannot Be Specified in P525 Statement with PA5

		Report Number:  42894
		Resolved:	Aug 07 2007
		Application:    MET/CAL

		In MET/CAL V7.20 a problem in the P525 FSC prevents the
		following statement from being compiled:

			P525 1.000bar N ZR PA5

		MET/CAL generates the following error message when an attempt
		to compile the above statement is made:

			E4387: FSC P525: Pressure (NOMINAL Value) must be
			       zero when MOD3 is "ZR".

		This error message is valid for non-absolute pressure modules,
		but is not valid for the PA5, which is an absolute module.

		V7.20 SP1 resolves this problem.  (V7.20r or later is
		required.)

	----> P525 Statement Generates "Connection Message Not Valid" Error

		Report Number:  42883
		Resolved:	Aug 07 2007
		Application:    MET/CAL

		In MET/CAL V7.20 there's an error in the P525 FSC when a
		525A-PA5 pressure module is used.  For example, executing
		a statement like this:

			P525 1.000bar 0.2U PA5

		generates the error:

			E2705: Connection message number (<n>) is not valid.

		(The value displayed as <n> in the error message may be any
		integer value.)

		This problem cannot be worked around by disabling automatic
		connection messages.

		V7.20 SP1 resolves this problem.  (V7.20r or later is
		required.)

	----> 5320 High Resistance Mode Maximum Test Voltage Incorrectly
	      Calculated When Multiplier Specified

		Report Number:  MC-3366
		Resolved:	Jul 17 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC incorrectly calculates the
		maximum test voltage when the multiplier is used.

		For example, the 5320 statement:

			1.001  5320 Mode = HR; TestVolt = 5000 V
			1.001  5320 +Res = 1.00 GOhm; ResMultOn

		incorrectly generates the error message:

			E7743: FSC 5320: "TestVolt = 5000 V" is outside the
			       legal range.  Limits are 0V to 1.575 kV.

		V7.20 SP1 corrects this problem.

	----> Error in 5320 FSC Line/Loop Resistance Accuracy Calculation

		Report Number:  MC-3365
		Resolved:	Jul 17 2007
		Application:    MET/CAL

		In V7.20 the 5320 FSC accuracy calculation fails to include
		the 1% + 15 mOhm adder when using line/loop impedance source
		in "correction scan" and "correction COMP" modes.

		V7.20 SP1 corrects the accuracy calculation by including
		the required adder.

	----> Error in 5320 FSC High Resistance Accuracy Calculation

		Report Number:  MC-3364
		Resolved:	Jul 17 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC high resistance mode accuracy
		calculation failed to account for footnote #1 (in the
		extended specifications).

		The footnote states:

			[1] Uncertainty is valid to 500 volts.	For test
			voltages above 500 V, add 0.1 % for each 200 V above
			500 V.

		In V7.20 SP1 the 5320 FSC now includes the additional
		uncertainty for voltages above 500 V in high resistance mode.

	----> 5320 FSC Accuracy Lookup Error in Meter Mode

		Report Number:  MC-3363
		Resolved:	Jul 17 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the following statements:

			1.001  5320 Mode = Meter; +Volt = 5 V; Measure
			1.002  MEMC 5.0V           1%

		incorrectly generate the following accuracy lookup error:

			E1699: Error determining reference accuracy from
			       "5320" statement.

		V7.20 SP1 corrects the problem.

	----> NVI FSCs Fail To Prevent Multiple Parameters When Action Is
	      "Reset"

		Report Number:  42415
		Resolved:	Jul 13 2007
		Application:    MET/CAL

		Due to a missing compile-time error check in the NVI FSCs
		(name/value instrument FSCs) the V7.20 MET/CAL Editor allows
		statements with the action specifier equal to "Reset" and
		with one additional parameter to be specified.

		In fact, when the action is "Reset" no other parameters
		should be allowed in the NVI statement.

		Example:

			N5531 Reset; Freq = 100 MHz

		In V7.20 the Editor compiles the statement shown above
		without errors.  However, an error message should be generated
		indicating that when "Reset" is specified no other parameters
		are allowed.

		This problem does not affect the "6100" FSC, but it affects
		all other NVI FSCs in V7.20:  5320, 9640, N5531, and PSA.

		V7.20 SP1 resolves this problem by adding the missing
		error check.  (V7.20o or later is required.)

	----> M4419 FSC Does Not Allow Default On Channel A & Table Name On
	      Channel B

		Report Number:  42332
		Resolved:	Jul 05 2007
		Application:    MET/CAL

		In all versions of MET/CAL that support the Agilent E4418B
		or E4419B, up through and including V7.20m, the M4419 FSC
		does not allow the procedure to specify that the default
		calibration table is to be used for channel A and a non-default
		calibration table is to be used for channel B.

		The problem is that in order to specify that the default
		calibration table is to be used on channel A it is necessary
		to leave the TOLERANCE field in the M4419 statement blank.
		To specify a non-default table for channel B it is necessary
		to specify the table name, in quotes, in the MOD2-through-CON
		fields of the M4419 statements,  However, since the field
		recognition and parsing code in the M4419 FSC implements
		exactly the same rules for the channel A and channel B table
		names, it always recognizes the name specified for channel
		B as a valid channel A table name, and moves the table name
		to the TOLERANCE field.

		Therefore, for example, if the procedure writer enters:

			FSC    RANGE NOMINAL  TOLERANCE  MOD1    MOD2  3  4 CON
			M4419  F256  8481A               8484A      "t1"

		MET/CAL compiles the statement as:

			FSC    RANGE NOMINAL  TOLERANCE  MOD1    MOD2  3  4 CON
			M4419  F256  8481A    "t1"       8484A

		This problem is resolved in V7.20 SP1.	(V7.20n or later
		is required.)

		The M4419 FSC now allows the word "Default" to be optionally
		entered into the TOLERANCE field.  "Default" is equivalent
		to <blank> in that it indicates that the default cal table
		for the sensor is to be used.  However, since it occupies
		the field, it allows MET/CAL to realize that a subsequently
		entered table name must be a channel B calibration table.

		Using the example shown above, the statement should now be
		entered as:

			FSC    RANGE NOMINAL  TOLERANCE  MOD1    MOD2  3  4 CON
			M4419  F256  8481A    Default    8484A      "t1"

	----> Case Changed in Unrecognized Discrete String Parameter Values
	      in Name/Value Instrument FSCs

		Report Number:  42165
		Resolved:	Jun 21 2007
		Application:    MET/CAL

		In MET/CAL V7.20, MET/CAL alters the case of unrecognized
		discrete string values in name/value instrument FSC statements.

		The following FSCs are affected:

			5320
			6100
			9640
			N5531
			PSA

		If the discrete string value is recognized by doing a
		case-insensitive comparison against values stored in an
		internal table, then the value string is converted to the
		representation in the external table.

		Example 1:

			As-entered text:  9640 ModulationWaveForm = sine
			As-printed test:  9640 ModulationWaveForm = Sine

			(This is correct.)

		However, when the value string is not recognized, MET/CAL
		reprints it with the first character upper-case, and the
		remaining characters lower-case.

		This algorithm may cause a problem when the value string
		contains an embedded construction that references a
		MET/CAL variable.  The problem does not occur with MET/CAL
		"registers" because register names are case-insensitive.
		Named variables, however, are case-sensitive, so changing
		the case to lower-case invalidates the reference if the name
		contains upper-case characters after the 1st character.

		Example 2:

			As-entered text: MATH @Waveform = "Sine"
			                 9640 ModulationWaveForm = [V @Waveform]
			As-printed text: MATH @Waveform = "Sine"
			                 9640 ModulationWaveForm = [v @waveform]

			(This is not correct.  The variable name "@Waveform"
			has been changed to "@waveform".)

		Work-arounds for this problem are:

			(1) Use a lower-case variable name.

			(2) Transfer the variable value to a string
			    register and specify the register name in the
			    [v ...] construction in the NVI FSC discrete
			    string value specification.

		This problem is not specific to V7.20.	All NVI FSCs in all
		versions up to and including V7.20k are affected.  The 6100
		FSC is affected as well.

		V7.20 SP1 resolves this problem.  (V7.20l or later is
		required.)  When a discrete string parameter value in an
		NVI FSC statement contains embedded special constructions
		it is now left unchanged when the line is reprinted by the
		procedure compiler.

	----> 9640 Expanded Uncertainty Incorrect When Units are dBm or dBuV

		Report Number:  39994
		Resolved:	Jun 21 2007
		Application:    MET/CAL

		MET/CAL V7.20 does not correctly calculate the expanded
		uncertainty for 9640 statements in which the evaluation
		quantity is specified in dBm or dBuV.

		The calculation is done properly in linearized units
		(watts).  The problem arises in the last step when MET/CAL
		back-converts the uncertainty to logarithmic units (in this
		case dBm or dBuV).

		V7.20 SP1 resolves this problem.

	----> Safety Symbol Not Displayed In Some Cases

		Report Number:  40951
		Resolved:	Jun 20 2007
		Application:    MET/CAL

		In V7.20, and earlier versions, in certain situations MET/CAL
		fails to display the "Safety Symbol" high voltage warning.

		The problem occurs when there are multiple signals present,
		and one or more signals involving non-voltage units are set
		up prior to the unsafe signal.

		For example, a procedure that does the following:

			525 1Z S
			5520 100V S

		exhibits this problem.

		As a practical matter, this situation was unlikely to arise
		prior to the addition of the MATH FSC "SafeOn" and "SafeOff"
		functions.  However, with the release of V7.20, which included
		"SafeOn" and "SafeOff", tests where the system reference is
		sourcing a safe non-voltage signal, and the UUT is sourcing
		a dangerous voltage, may occur.

		V7.20 SP1 corrects this problem.

	----> Incorrect Value for User-Defined Date Field Returned by
	      "metgendb.dll"

		Report Number:  42118 (MC-3344)
		Resolved:	Jun 19 2007
		Application:    MET/CAL Run Time

		In MET/CAL V7.20, and probably in earlier versions as well,
		when "metgendb.dll" is called to retrieve the value of a
		user-defined date field, the returned value is invalid.

		For example, the value returned is like this:

			'2007-06-19'

		The surrounding single quotes shown above are part of the
		returned value, but should not be.  The returned value
		should be:

			2007-06-19

		It's likely that the same problem exists for all database
		date fields, but that has not been confirmed.  The specific
		problem reported affected the user-defined field 2372.

		The problem is compounded by the fact that when "metgendb.dll"
		is queried to determine the maximum length of field 2372,
		it reports that the maximum length is 10 characters.  If the
		calling program provides a buffer of exactly the required
		length, then, when the query for the value is performed,
		"metgendb.dll" reports that the return value is too small
		for the provided buffer.  (That's true, but only because
		"metgendb.dll" is attempting to return an invalid value.)

		This problem manifests itself in the MET/CAL Run Time
		application a reference to a user-defined date field is
		included in one of the prompt files (pre-prompt, pass-prompt,
		or fail-prompt).

		For example, adding this line to the pass-prompt file:

			Field 2372 :D: F2372$ 2372

		suffices to generate the problem.

		V7.20 SP1 corrects this problem.  (Any version of
		"metgendb.dll" dated June 19 2007 20:55 or later corrects
		this problem.)

	----> Measurement Uncertainty Parameters Not Reliably Retrieved
	      from Database

		Report Number:  41960 (MC-3341)
		Resolved:	Jun 08 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the database-specified measurement uncertainty
		parameters are not reliably retrieved by MET/CAL.

		The parameters in question are:

			"Coverage Factor"
			"Number of significant digits for output"
			"Use Student's T"
			"Number of Measurements"

		Specifying these parameters in the MET/CAL initialization
		file or in a procedure (using VSET or TSET) works reliably.

		This problem is probably present in all versions of MET/CAL
		that support measurement uncertainty (up to and including
		V7.20i).

		The reason the problem has not been reported previously is
		most likely a combination of:

			(a) Since measurement uncertainty may not work
			    out of the box for all procedures, it generally
			    makes sense to enable it selectively in individual
			    procedures that have been reviewed and tested
			    for measurement uncertainty compliance.

			(b) The operation of retrieving the parameters listed
			    above from the database operates properly some
			    of the time.  (The internal source of the problem
			    was traced back to an unset integer variable.
			    If the initial value of the variable happened to
			    be non-zero, the parameters were retrieved from
			    the database properly.  If the initial value of
			    the variable happened to be zero, the default
			    values of the parameters were used.)

		The problem is resolved in V7.20 SP1.  (V7.20j or later
		are required.)

	----> Run Time Post Run Prompt Data Not Reset After Database Error

		Report Number:  41906 (MC-3340)
		Resolved:	Jun 06 2007
		Application:    MET/CAL Run Time

		In MET/CAL Run Time V7.20, and probably prior versions, a
		problem related to the run time pre-prompt and post-prompt
		windows occurs as a side-effect of a database related error.

		The initial problem, which leads to the problem reported here,
		is that when a Post Run prompt for a user-defined
		date field (like 2372) is added, "metgendb.dll" reports that the
		maximum length for the field is some value, N, but then
		attempts to send back N+2 bytes.  (This happens because
		it surrounds the date with single quotes.)  Since MET/CAL
		allocates a buffer of exactly N+1 bytes, not N+3 bytes,
		"metgendb" then generates an error indicating that the
		value to be returned is too long for the buffer provided.

		MET/CAL traps the error in the Post Run prompt module,
		generates an error message, and aborts the procedure.  The
		secondary problem is that when MET/CAL aborts the procedure
		it fails to free the internal prompt data built up for the
		post prompt window.  This leads to a situation where, when
		another procedure is run, without having exited from the Run
		Time application, the pre-run prompts are appended to the
		left-over post-run prompts, and things get thoroughly confused.

		Resolved in V7.20 SP1.	The Run Time application now releases
		internal memory used for prompt window data after a database
		error occurs.  (Requires V7.20h or later.)

	----> Missing Error Check When M5520 Nominal Units are Ohms

		Report Number:  41904 (MC-3339)
		Resolved:	Jun 06 2007
		Application:    MET/CAL Editor

		In V7.20 and prior the M5520 FSC compile time checks
		incorrectly allow the statement:

			M5520   1kZ

		to be compiled.

		In fact, it should be necessary to specify "IMPED" in the M5520
		RANGE field when M5520 NOMINAL field units are ohms ("Z").

		This leads to a floating point exception when the subsequent
		associated statement is checked:

			5520         -3D        0.1U          1kH           SI

		Resolved in V7.20 SP1.  Requires V7.20i or later.

	----> Erroneous ACV-to-ACV Settings Conflict Determination in 9100 FSC

		Report Number:  MC-3336
		Resolved:	Jun 05 2007
		Application:    MET/CAL

		In MET/CAL V7.20, and prior versions, the 9100 FSC incorrectly
		determines that a possible settings conflict exists in a
		transition from:

			(FUNC SIN, VOLT 60, FREQ 50)

		to:

			(FUNC SIN, VOLT 70, FREQ 50)

		Because the FSC run time believes there may a settings
		confict, it therefore programs the 9100 to 1 V @ 60 Hz,
		before attempting to send the commands to program the
		instrument to 70 V @ 50 Hz.

		This prevents the following procedure from operating as
		designed.  The UUT is a low impedance device that must be
		ramped up from 20 V to 70 V. Transitioning directly from 1
		V to 70 V causes an overload condition.

			9100 20V 50H SI S 2W
  			SCPI [@9100]func sin;:volt 40
  			SCPI [@9100]func sin;:volt 60
  			SCPI [@9100]func sin;:volt 70
  			9100 600 70.0V 1.5% 0.005U 50H SI 2W 

		In V7.20 SP1 the 9100 FSC run time has been updated so that
		it no longer incorrectly concludes that a transition from
		60 V @ 50 Hz (sine) to 70 V @ 50 Hz (sine) represents a
		possible settings conflict.

	----> Port Configuration Construction Fails with 55XX & 58XX
	      Pass-Through Ports

		Report Number:  41535 (MC-3332)
		Resolved:	May 18 2007
		Application:    MET/CAL

		In MET/CAL V7.20 there's an error in the Port Configuration
		construction that prevents making a direct reference to a
		pass-through serial port on a Fluke calibrator.

		The problem applies to the following COM ports:

			COM5500
			COM5520
			COM5800
			COM5820

		An example of a construction that no longer operates correctly
		in V7.20 is:

			PORT [PCOM5500,300,N,8,1,N]

		The problem does not occur when the COM port specifier
		is omitted.  This means that the problem does not generally
		affect procedures where the UUT is on the pass-through port.
		For example, it's still ok to configure COM5500 as the
		default serial port, and then include a construction like:

			PORT [P300,N,8,1,N]

		in the procedure.

		The problem is therefore really specific to cases where a
		reference instrument is being accessed on the pass-through
		port.

		The underlying problem was introduced when support for
		COM ports COM5 to COM16 was added to MET/CAL.  Due to a
		parsing error, the designators COM5500, COM5520, COM5800,
		and COM5820 were taken to be the same as COM5.

		Resolved in V7.20 SP1.  (Requires V7.20g or later.)

	----> 5320 FSC Run Time Does Not Set IDS UUT Output Resistance

		Report Number:  MC-3329
		Resolved:	May 14 2007
		Application:    MET/CAL

		In MET/CAL V7.20 when a 5320-based leakage current test like
		the following:

			1.001 5320 Mode = IDS; +LeakageCurrent = 3.50 mA
			1.002 5320 UUTOutputResistance = 1000 Ohms
			1.003 TARGET -m
			1.004 MEMI Enter UUT reading in milliamps:
			1.005 MEMCX 20 3.50mA 2.5% 0.05U

		is executed, the 5320 FSC run time fails to set the UUT
		output resistance to the value specified.

		V7.20 SP1 corrects this problem.

	----> 5320 Statement Specifying High Resistance Short Causes Run
	      Time Error

		Report Number:  MC-3324
		Resolved:	May 03 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the following statement:

			5320 Mode=HR; +Res=0 Ohm; Short

		generates the following error message when executed:

			E2075: Fluke 5320A: -220,Invalid parameter

		In V7.20 SP1 the 5320 FSC run time has been updated to
		correctly implement the specified operation.

	----> 5320 FSC Missing Error Check To Prevent Measuring Test Voltage
	      when High Resistance Source Short Selected

		Report Number:  MC-3323
		Resolved:	May 03 2007
		Application:    MET/CAL Editor

		In MET/CAL V7.20 the 5320 FSC compile time checks fail to
		generate an appropriate error message for the following
		statement:

			5320 Mode=HR; +TestVolt=0 V; Res=0 Ohm; Short; Setup

		The 5320A cannot measure the test voltage when
		"High Resistance Source Short" is selected.

		V7.20 SP1 corrects this problem.

	----> 5320A Accuracy File Specifies NA for GBR & Line/Loop Current
	      Measurement Accuracy

		Report Number:  MC-3322
		Resolved:	Apr 25 2007
		Application:    MET/CAL (Accuracy File)

		In MET/CAL V7.20 the 5320 accuracy file fails to specify
		specifications for ground bond resistance and line/loop
		current.

		V7.20 SP1 includes an updated 5320 accuracy file that includes
		the proper specifications.

	----> 8845 FSC Frequency Upper Limit Incorrect

		Report Number:  MC-3321
		Resolved:	Apr 19 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 8845 FSC allows frequencies up to
		300 MHz to be specified.  This upper limit is incorrect.
		The limit should be 300 kHz.

		V7.20 SP1 corrects the frequency upper limit.

	----> 5320 FSC LowResistance TestCurrent Limits are Incorrect

		Report Number:  MC-3315
		Resolved:	Apr 11 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the following statement:

			5320 Mode=LR; Res=5 Ohm; +TestCurrent=200 mA; Setup

		generates the error message:

			E7743: FSC 5320: "+TestCurrent = 200 mA" is outside
			       the legal range. Limits are 0A to 5 mA.

		This error message is not valid.  The maximum test current
		at 5 ohms is 250 mA.

		V7.20 SP1 corrects this problem.

	----> Fluke 80K-40 Not in List of Standards Used When 5320 Statement
	      Specifies "Probe = 40 kV"

		Report Number:  MC-3314
		Resolved:	Apr 09 2007
		Application:    MET/CAL Run Time

		In MET/CAL V7.20, when a 5320 FSC statement specifies
		"Probe = 40 kV", the 5320A is programmed to expect the
		Fluke 80K-40 "40 kV" probe to be connected to the 5320A
		METER INPUT V and COM terminals.  The 80K-40 is a traceable
		reference used for the measurement and should be included
		in the list of standards used written to the database when
		the calibration results are saved.  However, the Run Time
		application fails to include the 80K-40 in the list of
		standards used.

		V7.20 SP1 corrects this problem.

	----> Standards Table Update Fails with Multiple Aux Devices &
	      Dynamic Asset Prompt

		Report Number:  40210 (MC-3292)
		Resolved:	Feb 26 2007
		Application:    MET/CAL

		In MET/CAL Run Time V7.20 there are some situations in which
		the application fails to successfully update the Standards
		Table in the database at the end of a calibration.

		The failure scenario occurs in the following circumstance:

			(1) Multiple secondary devices of the same model
			    are configured.

			(2) The asset number of the secondary device required
			    by the procedure is not specified in the system
			    configuration information.	(In this case the
			    Run Time application prompts for the asset number
			    just prior to procedure execution.)

			(3) The secondary device used by the procedure is
			    not the first occurence of that model listed in
			    the system configuration information.

		If the three conditions described above are met MET/CAL
		prompts for the asset number of the secondary device,
		but then associates the entered asset number string with
		the wrong secondary device.  Then, at the conclusion of
		the calibration, the application has an empty asset number
		string for the secondary device.  That, in turned, causes the
		operation which updates the database Standards Table to fail.
		This generates the error:

			E5490: Can't add standard () to cal event information
			       in database.  Function error.

		The problem is resolved in V7.20 SP1.  (A MET/CAL Run Time
		build later than Feb 26 2007 4:06 PST is required to obtain
		the correction.)

	----> Error When Changing the Number of Configured IEEE-488 Boards

		Report Number:  40103 (MC-3289)
		Resolved:	Feb 20 2007
		Application:    MET/CAL

		In MET/CAL V7.20 attempting to change the number of configured
		IEEE-488 boards from 1 to 2 causes the following error
		message to be generated:

			E596 : The address of the second IEEE-488 board must
			be specified when the number of IEEE-488 boards is 2.

		A work-around is to manually edit the MET/CAL initialization
		file and change the value of "ib_ioaddr" from "210" to
		"210, 220".

		It's not entirely clear what triggered the problem.  Probably
		the MET/CAL Install Program performed an invalid upgrade
		step by causing 2-board systems to revert to "ib_nport=1 and
		ib_ioaddr=210".  Then, when the "Configure":"IEEE-488 Boards"
		window is used to correct the problem, error 596 is generated.

		Since the error check applies only to Ziatech and NI PC2B
		boards, neither of which is supported in Win32, there is no
		reason to continue to do the check.  V7.20 SP1 resolves the
		problem by removing the error check.

	----> Lookup of Cal Table Values Fails When CTAG Length Exceeds 15

		Report Number:  39612 (MC-3268)
		Resolved:	Feb 16 2007
		Application:    MET/CAL

		In V7.20 when the CTAG for a database calibration record
		exceeds 15 characters attempts to read calibration table
		field values fail.

		This problem causes the MATH FSC function "CAL" to fail.

		The underlying problem involves calls to the "metgendb.dll"
		function "M_DB_GetCTAGs_4_MTAG".

		For example, when the CTAG string for a cal record is
		"A1234567890:1168000975", calling "M_DB_GetCTAGs_4_MTAG"
		causes the CTAG "A1234567890:116" to be returned.  Note that
		only the first 15 characters have been preserved.

		V7.20 SP1 resolves this problem.  (Actually, V7.20a with build
		date 2007-02-16, or later, is required.)  Updated versions of
		"metgendb.dll", "mcr32.exe", "mce32.exe", and "mctext.mdb"
		are all required.

	----> 9500B/3200 Dual Leveled-Sine with 2 9530 Active Heads Incorrectly
	      Limited to 1.1 GHz

		Report Number:  39988 (MC-3281)
		Resolved:	Feb 12 2007
		Application:    MET/CAL

		In V7.20, and all previous versions that support the Fluke
		9500B, the 9500 FSC incorrectly limits the frequency upper
		limit to 1.1 GHz for dual leveled sine tests in which two
		9530 active heads are used.

		The 9500B/3200 with two 9530 Active Heads is specified as:

			0.1 Hz to 550 MHz
			5 mVpp to 2.5 Vpp

			550 MHz to 2.5 GHz
			5 mVpp to 1.5 Vpp

			2.5 GHz to 3.2 GHz
			5 mV to 1 Vpp

		V7.20 SP1 includes an updated 9500 FSC that implements the
		correct frequency limit.

	----> MEMC/MEMCX Tests with Dimensionless Evaluation Quantity May
	      Crash MET/CAL

		Report Number:  40009 (MC-3284)
		Resolved:	Feb 09 2007
		Application:    MET/CAL Editor and Run Time

		In V7.20 a MET/CAL crash is caused by any test where:

			(a) there's an instrument setup statement in which
			    the evaluation quantity is dimensionless and
			    no pseudo-units string (e.g. "V/V") is used to
			    annotate the dimensionless value, and

			(b) the ASK 'U' flag is set (i.e., "ASK+ U"), and

			(c) there's a MEMC or MEMCX evaluation in the test.

		As a practical matter, there's no way to cause this situation
		when using a traditional instrument FSC (like "5700"), because
		a units string must always be part of the NOMINAL field.

		However, with name/value instrument FSCs, the situation
		described above may arise.

		Below is an example of a 6100-based test (discovered by a
		customer) that causes the Editor and Run Time to crash when
		the MEMCX statement is executed:

			1.001  6100         L1VRange            =   336 V
			1.001  6100         L1VAC               =   230 V
			1.001  6100         L1VFlickerDepth     = 0.402 %
			1.001  6100         L1VFlickerFrequency = 13.5 Hz
			1.001  6100         L1VFlickerShape     =  Square
			1.001  6100         +L1VFlickerPST      =       1
			1.001  6100         Frequency           =   50 Hz
			1.002  MEMCX        1.00           TOL

		Notice that the evaluation quantity in the 6100 statement
		is "L1VFlickerPST".  This is a dimensionless quantity.
		The value is 1, without any units.

		MET/CAL V7.20 SP1 corrects this problem.

	----> MEMC/MEMCX Help File Does Not Correctly Describe Units Quoting

		Report Number:  40008 (MC-3283)
		Resolved:	Feb 08 2007
		Application:    MET/CAL Documentation

		Beginning with V7.00, MET/CAL has supported a syntax for
		quoting the units string in the NOMINAL field of a MEMC or
		MEMCX statement in order to override the standard parsing
		algorithm.  The override is used where the first letter of the
		units name is a valid SI units prefix.	For example, "mmHg"
		is interpreted by MET/CAL as milli-mHg.  In other words,
		the base unit is meters of mercury, and the units prefix is
		milli ('m').  In order to force MET/CAL to interpret "mmHg"
		as a base unit itself it's necessary to surround the units
		string with single quotes.  For example:

			MEMC 100'mmHg' 1%

		In V7.20 and prior the MEMC/MEMCX help file does not correctly
		document this.	It states that double quotes should be used,
		rather than single quotes.  Furthermore, the help file states
		that an alternate method is to precede the units string with
		an underscore ('_').  The software does not implement the
		underscore mechanism.

		V7.20 SP1 resolves this problem.  The service pack includes
		an updated MEMC/MEMCX help file that should be placed in
		the MET/CAL help directory in place of the file distributed
		with V7.20.

	----> Marginal Pass Count in Calibration Table Incorrect with
	      Guardbanding Enabled

		Report Number:  39974 (MC-3279)
		Resolved:	Feb 06 2007
		Application:    MET/CAL

		In V7.20 the marginal pass count (field 2350 in the Calibration
		Table) is not correctly determined when procedure execution
		results in one or more FAIL test results, and guardbanding
		is enabled.

		The problem is that, when guardbanding is enabled, MET/CAL
		V7.20 marks any test result for which the error as a percentage
		of the test tolerance exceeds the marginal pass threshold as
		a Marginal Pass.  In fact, no result which is a Fail or Fail
		Indeterminate result should be considered a Marginal Pass,
		even though the error exceeds the threshold.  This error is
		present for both MEMC/MEMCX and instrument FSC evaluations.
		The error is not present when guardbanding is not enabled.
		The error does not depend on the specific guardbanding
		method.

		The error is present in all versions of MET/CAL that support
		guardbanding.  (Guardbanding was introduced in V7.10.)

		V7.20 SP1 corrects the problem.

	----> RESET FSC Error When UUT RESET Statement Follows Other RESET
	      Statements

		Report Number:  39932 (MC-3278)
		Resolved:	Feb 02 2007
		Application:    MET/CAL

		In V7.20 there's an error in the execution of RESET
		statement-specified commands when a RESET command for the UUT
		precedes one or more other RESET commands for user-configured
		references.

		On the second and subsequent execution of the RESET commands,
		knowledge of the IEEE-488 or serial address of user-configured
		references to which RESET commands are directed has been lost.
		This causes MET/CAL to attempt to send those commands to
		the UUT.

		This problem has been present since support for using RESET to
		reset the UUT was added (V6.10).

		To summarize, the problem appears in procedures which:

			(1) contain RESET statements for both the UUT and
			    at least one user-configured reference, and

			(2) the execution of the RESET statement for the
			    UUT precedes the execution of at least one RESET
			    statement for a user-configured reference.

		A work-around is to specify the UUT RESET command after
		the RESET commands for the user-configured references have
		been specified.

		V7.20 SP1 corrects this problem.

	----> [V ...] Construction Fails in WAIT FSC When One or More Spaces
	      Follow 'V'

		Report Number:  39931 (MC-3277)
		Resolved:	Feb 02 2007
		Application:    MET/CAL

		In V7.20 the [V ...] special construction fails in the WAIT
		FSC when:

			(a) The construction appears in the time specification
			    portion of the statement, and

			(b) one or more spaces appear after the 'V'.

		For example:

			math x = 10
			wait -t [v x] message

		fails, but this:

			math x = 10
       			wait -t [vx] message

		succeeds.

		The underlying issue is that the first white-space delimited
		word after the "-t" is taken to be the entire <time>
		specification.	Therefore, in the first example shown above
		the problem is that the <time> specification is taken to be
		"[v", rather than "[v x]".

		V7.20 SP1 corrects this parsing problem.

	----> HP60 and HP63 Statements Cannot Be Compiled

		Report Number:  39910 (MC-3274)
		Resolved:	Feb 01 2007
		Application:    MET/CAL Editor

		In V7.20, the MET/CAL Editor can no longer compile HP60 and
		HP63 statements.

		This prevents using V7.20 to write or modify HP60-based or
		HP63-based procedures.

		This error was introduced after V7.11 SP1.

		V7.20 SP1 corrects this problem.

	----> 5320 FSC Voltage Cal Incorrectly Accepts Negative DCV Values

		Report Number:  39873 (MC-3273)
		Resolved:	Jan 31 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the procedure compiler incorrectly accepts
		statements which specify a negative DC voltage.

		For example, the statement:

			5320 +Voltage = -10 V

		is accepted as valid.  When executed, the following run time
		error is generated:

        		E2075: Fluke 5320A: -220,Invalid parameter

		V7.20 SP1 corrects this problem.

	----> N5531S, PSA-Based, HP 8657B Verification Causes GPF Due to dBc/Hz

		Report Number:  39188 (MC-3250)
		Resolved:	Jan 05 2007
		Application:    MET/CAL Editor & Run Time

		In MET/CAL V7.20 a problem exists in N5531 and/or PSA-based
		procedures which specify the units symbol "dBc/Hz".

		For example, the following procedure generates a run time
		crash when the MEMC statement executes:

			INSTRUMENT:	       dBc/Hz Test
			CONFIGURATION:         Agilent PSA (6.7 GHz,226)
			1.001  MATH    @FreqMHz = 10
			1.002  MATH    @dBc_Hz = 5
			1.003  LABEL   PHASE_NOISE
			1.004  TSET    TDESC = [V @FreqMHz] MHz
			1.005  TARGET  -p
			1.006  IEEE    [SDC]FR[V @FreqMHz]MZAP0DMR3
			1.007  TARGET  -m
			1.008  PSA     Mode = PhaseNoiseLogPlot
			1.008  PSA     ExtRefFreq = 10 MHz; TimebaseAccOff
			1.008  PSA     CenterFreq = [V @FreqMHz] MHz;
			1.008  PSA     FreqSpan = 50 kHz
  			1.008  PSA     FreqOffset = 20 kHz; RFCoupling = DC
  			1.008  PSA     +PhaseNoise = [V @dBc_Hz] dBc/Hz
  			1.009  MATH    MEM1 = @dBc_Hz
  			1.010  MEMC    dBc/Hz         -0U +1000%

		V7.20 SP1 corrects the problem.

	----> VSET "UFMT" Parameter Not Documented in On-Line Help

		Report Number:  39431 (MC-3263)
		Resolved:	Dec 14 2006
		Application:    MET/CAL Documentation

		In MET/CAL V7.20 the on-line help for the VSET FSC failed
		to include a description of the "UFMT" parameter.

		The "UFMT" parameter, which controls the formatting of
		measurement uncertainty-related result values, first became
		available in MET/CAL V7.20.

		V7.20 SP1 includes an updated help file, "vset.hlp",
		containing a description of the "UFMT" parameter.

		Place "vset.hlp" in your MET/CAL help directory.  (You can
		find the location of the MET/CAL help directory by looking
		at the value of the "helpdir" parameter in the [Startup]
		section of the MET/CAL initialization file, "metcal.ini".)

	----> VSET CORREQ=EXACT Causes Instrument FSC Reset Statements
	      to Require Correction

		Report Number:  39428 (MC-3262)
		Resolved:	Dec 14 2006
		Application:    MET/CAL Editor & Run Time

		In MET/CAL V7.20, when corrections are enabled, and the VSET
		"CORREQ" parameter is used to specify that all corrections
		must be "exact", an error occurs when an instrument FSC
		reset statement is executed.

		The "CORREQ" parameter, which controls run time warnings
		associated with automatic corrections applied to the reference
		value in a test, first became available in MET/CAL V7.20.

		For example, the following procedure:

			1.001  VSET         CORREQ = EXACT
			1.002  ASK+                                  C
			1.003  5520         *                        S

		generates the error message:

			E2758: The test step just completed requires that a
			correction be performed.  However, the correction
			file does not contain data required to perform
			the correction.

		V7.20 SP1 includes updated Editor and Run Time executables
		which correct this problem.

	----> MET/CAL Editor GPF While Generating TUR Report on 9640-Based
	      Procedure

		Report Number:  39280 (MC-3256)
		Resolved:	Dec 12 2006
		Application:    MET/CAL Editor

		In V7.20 the MET/CAL Editor crashes in some cases when
		generating a T.U.R. report for a 9640-based procedure.

		The problem occurs only when the procedure contains 9640
		statements in which the evaluation quantity is Modulation
		Frequency.

		An example of a 9640 statement which causes the problem is:

			1.001 9640 Freq = 100 MHz; Level = -16 dBm;
			1.001 9640 OutputImp = 50 Ohms; Mode = AM;
			1.001 9640 AMDepth = 70 %; ModWav = Triangle
			1.001 9640 +ModFreq = 200 Hz

		V7.20 SP1 corrects the problem.

-------------------------------------------------------------------------------
Section 4:  Enhancements ------------------------------------------------------
-------------------------------------------------------------------------------

	----> 5320 FSC Modified to Support Rescan

		Report Number:  MC-3430 (1/3)
		Resolved:       Jan 02 2008
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC does not support Rescan in
		loop/line source mode.

		Rescan is used to force the 5320 to re-measure the mains
		impedance.  (Note that there is a time limit that prevents
		Rescan from being used too frequently.	This is determined
		internally by the 5320A.)

		V7.20 SP1 support Rescan.  Refer to on-line help for the
		5320 FSC for additional information.

	----> 5320 FSC Modified to Support Transfer Ground Bond Resistance Mode

		Report Number:  MC-3430 (2/3)
		Resolved:       Jan 02 2008
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC does not support Transfer
		Ground Bond Resistance mode.

		In V7.20 SP1 the 5320 FSC supports Transfer Ground Bond
		Resistance mode.  There are six new resistance values,
		each with its own accuracy, dependent upon UUT current
		stimulus level.

		Refer to on-line help for the 5320 FSC for additional
		information.

	----> 5320 FSC Modified to Support Serial Resistance

		Report Number:  MC-3430 (3/3)
		Resolved:       Jan 02 2008
		Application:    MET/CAL

		In MET/CAL V7.20, when setting up a 5320 test in loop or line
		impedance mode, the 5320 FSC does not allow the resistance of
		the leads used to connect the 5320A to the UUT to be specified.

		In V7.20 SP1 there's a new parameter, "SerialResistance",
		used to specify the line or loop impedance serial resistance.
		The specified value must be between 0 and 2 ohms.

		There is no accuracy value per se.  It is up to the user to
		enter an appropriate value for the measurement uncertainty
		calculation.

	----> Unpack Dialog Modified to Allow Resizing and Direct File
	      Name Entry

		Report Number:  45279
		Resolved:       Dec 13 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the dialog that appears when a user
		chooses "File" : "Unpack" to allow choosing the file to be
		unpacked has been enhanced so that the window can be resized,
		and also allows direct text entry of the file name.

		Requires V7.20x or later.

	----> File I/O Utility Functions

		Report Number:  45276
		Resolved:       Dec 13 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes the following general purpose
		line-oriented file I/O utility functions:

			APPEND  - append line to file
			DELETE  - delete line from file
			INSERT  - insert line in file before specified line
			READ    - read specified line from file
			REPLACE - replace line in file
			WRITE   - write line to file after specified line

		Refer to the MATH FSC on-line help for details.

	----> Support for "Leakage Current Active" Added to 5320 FSC

		Report Number:  MC-3408
		Resolved:       Nov 20 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the 5320 FSC has been enhanced to support
		a new mode "LeakageCurrentActive" (or, equivalently, "IDA").
		Refer to on-line help for the 5320 FSC for details.

		Requires V7.20w or later.

	----> Function to Get Reference Accuracy from Last Setup

		Report Number:  20525
		Resolved:       Nov 16 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a new MATH FSC function to
		retrieve the reference accuracy from the last instrument
		setup in the same test.

		The name of the function is "RefAcc".

		"RefAcc" returns the reference accuracy in base units (for
		example, volts, not millivolts).

		Calls to "RefAcc" must be placed after a setup statement,
		but before the corresponding evaluation (MEMC or MEMCX).

		In order to use "RefAcc" T.U.R. checking (ASK+ U) must
		be enabled.

		Example:

			5700 1.000V S 2W
			MATH Acc = RefAcc()

			The call to "RefAcc" in this example will returns the
			reference accuracy determined by the MET/CAL 5700A FSC
			(driver) when the 5700 setup statement was executed.

		Refer to on-line help for the MATH FSC for details.

		Requires V7.20w or later.

	----> MATH Function To Indicate Whether MET/CAL Is In Demo Mode

		Report Number:  44562
		Resolved:       Oct 25 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a new MATH function that indicates
		whether or not MET/CAL is running in demo mode.

		The function name is "DEMO".

		Refer to the on-line help for the MATH FSC for details.

		Requires V7.20v or later.

	----> Asset Number Added to Run Time Header Information

		Report Number:  25794
		Resolved:       Oct 15 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the main window of the Run Time
		application shows the asset number of the UUT.	The asset
		number is shown below the procedure name.

	----> Second Line for HEAD Messages

		Report Number:  11411
		Resolved:       Oct 15 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the Run Time and Test Run main windows
		have been modified to make space for a second HEAD message.

		To access the second HEAD message line use a HEAD  procedure
		statement where the body of the statement begins with "-2".

		To clear the line use "HEAD -2".

		Example:

			HEAD DC Voltage Tests
			HEAD -2 1 V Test
			...
			HEAD -2 10 V Test
			...
			HEAD -2 100 V Test
			HEAD AC Voltage Tests
			HEAD -2 1 V @ 1 kHz Test
			...

		Rules for a "HEAD -2" lines are the same as for a regular HEAD
		statement.  See the on-line help for the HEAD FSC for details.

	----> Modify RESET FSC To Not Mark Instrument As "Used" (By Default)

		Report Number:  42782
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 a change has been made to the way
		MET/CAL handles commands specified in RESET statements.
		By default, the execution of a RESET-specified command no
		longer causes the Run Time application to mark the instrument
		as having been used by the procedure.  This means that if the
		execution of the RESET-specified command is the only use of
		the instrument in a procedure, the instrument will no longer
		appear in the "standards used" list in the database results
		associated with the calibration record.

		Example:

			RESET [@UDEV1]xyz
			5700 1.00V 1%
			END

		Before this change (V7.20q and previous) MET/CAL would
		report the instrument referred to by the alias "UDEV1" in the
		"standards used" table.  After the change it no longer
		appears in the table (by default).

		Of course, changing the example to:

			RESET [@UDEV1]xyz
			5700 1.00V 1%
			IEEE [@UDEV1]abc
			END

		causes MET/CAL to continue to include the instrument referred
		to by the alias as one of the standards used.

		This behavior can be configured on a per-workstation basis
		using the "ResetStandardUsed" optional initialization file
		parameter.

		The default is "No".  Setting "ResetStandardUsed = Yes"
		causes MET/CAL to continue to operate in the old mode -- i.e.,
		execution of a RESET FSC-specified command is sufficient to
		cause an instrument to appear in the "standards used" table.

		V7.20r or later is required.

	----> Allow Required Instruments To Be Connected After Procedure Starts

		Report Number:  42789
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		In V7.20, and previous versions, MET/CAL's design is to scan
		a procedure just before execution to determine the list
		of required instruments.  ("Required", here, really means
		"might be required" -- MET/CAL cannot determine the actual
		flow of a procedure based on an up front static analysis,
		and therefore does not know whether particular statements
		will or will not be executed.)

		After constructing the list of required instruments,
		each "system" instrument is tested and cleared by calling
		FSC-specific test and clear functions.	This happens prior
		to the start of procedure execution.

		If, when an instrument's test function is called, the
		instrument is not there, or not responding properly, MET/CAL
		displays a dialog with 3 choices:  Abort, Retry, Ignore.

		"Abort" terminates the procedure execution (before it
		really starts).

		"Retry" allows the user to hook up the instrument and re-test,
		but it does not allow procedure execution to commence until
		the test function succeeds.

		"Ignore" removes the instrument from an internal table of
		configured instruments.  Once "Ignore" has been chosen,
		thereafter, it's not possible to access the instrument
		without either (a) manually reconfiguring the instrument,
		or (b) closing and restarting the application.

		In MET/CAL V7.20 SP1 there's a new initialization file
		parameter named "InstrTest" that can be used to configure
		the operation of MET/CAL with respect to the execution of
		the built-in test and clear functions for required system
		instruments.

		There are now 3 modes of operation:

		(1) InstrTest = Legacy

			In this mode MET/CAL operates as in V7.20 and prior
			versions.  The description above explains this mode
			in detail.

		(2) InstrTest = Standard

			In this mode MET/CAL continues to test required system
			instrument before commencing procedure execution but,
			when a test function fails (because the instrument is
			not there, or turned off, or not operating correctly),
			choosing "Ignore" does not cause the instrument to
			be removed from the internal table of configured
			instruments.

			If and when the procedure reaches a statement
			that requires the instrument, the test function
			is re-executed.  If, by that time, the instrument
			is properly connected and operating properly,
			the test function will succeed and procedure
			execution continues normally.  Or if, at that time,
			the instrument is not yet connected and operating
			properly, the user may connect the instrument and
			choose "Retry".  The process may be repeated as
			needed until the instrument test function succeeds.
			The procedure continue normally from that point.

			This mode is the default mode (beginning with
			V7.20 SP1).

		(3) InstrTest = Deferred

			In this mode MET/CAL defers execution of the instrument
			test functions entirely until the procedure requires
			the use of the instrument.

			If the instrument is never used, the test function
			will never be executed.

			If and when the procedure reaches a statement
			that requires the instrument, the test function
			is re-executed.  If, by that time, the instrument
			is properly connected and operating properly,
			the test function will succeed and procedure
			execution continues normally.  Or if, at that time,
			the instrument is not yet connected and operating
			properly, the user may connect the instrument and
			choose "Retry".  The process may be repeated as
			needed until the instrument test function succeeds.
			The procedure continue normally from that point.

		Users should be aware that none of these modes change the
		requirement that reference instruments referred to by the
		procedure must be configured.

		Proper operation of the traceability and accuracy lookup
		functions require that the instruments referred to by the
		procedure be configured on the workstation using the Config
		Editor (F12).

	----> MATH Function for Linear Interpolation

		Report Number:  43067
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a new MATH function for linear
		interpolation and extrapolation.

		The name of the function is "INTERP".

		INTERP linearly interpolates between 2 specified points at
		a specified x-value.

		The formula for linear interpolation is:

			y = y1 + (x-x1) * ((y2-y1) / (x2-x1))

		INTERP may also be used to extrapolate values on the line
		defined by (x1,y1) and (x2,y2).

		Refer to MATH FSC on-line help for details.

		Requires V7.20t or later.

	----> Function to Round to Nearest Multiple of Specified Increment

		Report Number:  42760
		Resolved:       Oct 11 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a new MATH FSC function that
		rounds a specified numeric value to the nearest multiple of
		a specified increment.

		There's an existing function, "FRND", that can be used to
		round to a specified number of significant digits, but that
		is not the same thing as rounding to the closest multiple
		of a specified increment.

		The name of the new function is "CRND".

		The following example shows the difference between FRND
		and CRND:

			FRND( 1.234, 3)    generates  1.23
			FRND(12.345, 3)    generates 12.3

			CRND( 1.234, 0.01) generates  1.23
			CRND(12.345, 0.01) generates 12.34

		Both results generated by FRND have 3 significant digits,
		but they do not have the same number of digits to the right
		of the decimal point.

		On the other hand, the results generated by CRND both have
		the same number of digits to the right of the decimal point.

		Refer to MATH FSC on-line help for details.

		Requires V7.20r or later.

	----> Allow Configuring the Setting of RQS in the SRE Register with
	      IEEE & SCPI FSCs

		Report Number:  44187
		Resolved:	Oct 10 2007
		Application:    MET/CAL

		It has been found that some instruments regard setting RQS
		in the SRE register as an error condition.

		This prevents using the IEEE2 and SCPI FSCs to control
		those instruments.

		Technically such instruments are not in compliance with
		the IEEE-488.2 standard, because the standard requires that
		instruments ignore the state of the RQS bit (bit 6) in the
		SRE register.

		Nevertheless, since there is no particular reason for MET/CAL
		to set the RQS bit in the first place, in V7.20 SP1 MET/CAL
		has been modified so that, by default, it does not set RQS in
		the SRE register when an IEEE2 or SCPI statement is executed.

		A new VSET / TSET parameter named "IEEE2_SRE_RQS" has been
		implemented.  The default is "No", but procedure writers may
		now specify "IEEE2_SRE_RQS = Yes" to force RQS to be set in
		the SRE register prior to commands and queries initiated by
		the IEEE2 and SCPI FSCs.

		See on-line help for the VSET FSC for details.

		Requires V7.20v or later.

	----> Accuracy Files for Guildline Instruments

		Report Numbers: 44058, 44059, 44060, 44061, 44062, 44063,
				44064, 44065, 44066, 44067, 44025
		Resolved:	Oct 04 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes accuracy files for the following
		Guildline instruments:

			Guildline Instruments Limited / Model 9211A
			Guildline Instruments Limited / Model 9336-100G
			Guildline Instruments Limited / Model 9336-100M
			Guildline Instruments Limited / Model 9336-100T
			Guildline Instruments Limited / Model 9336-10G
			Guildline Instruments Limited / Model 9336-10M
			Guildline Instruments Limited / Model 9336-10P
			Guildline Instruments Limited / Model 9336-10T
			Guildline Instruments Limited / Model 9336-1G
			Guildline Instruments Limited / Model 9336-1P
			Guildline Instruments Limited / Model 9336-1T

		The 9211A is a current shunt.

		The 9336 series are resistance standards.

	----> Allow the Guardband Table Name To Be Specified with VSET/TSET

		Report Number:  44033
		Resolved:	Oct 03 2007
		Application:    MET/CAL

		In MET/CAL V7.20, and previous versions that support
		guardbanding, the guardband table name (parameter "gb_table")
		can be specified in the MET/CAL initialization file, or the
		guardbanding initialization file, but not in a procedure
		(using a VSET or TSET statement).

		In some cases it may be convenient to specify the table name
		in the procedure.

		In V7.20 SP1 the VSET and TSET FSCs support the "gb_table"
		parameter used to specify the name of the guardband table.

	----> Dropping Licenses Difficult Due To Short Refresh Rate of List

		Report Number:  MC-3249
		Resolved:	Oct 03 2007
		Application:    MET/TRACK

		In MET/CAL V7.20, using MET/TRACK build #434, dropping licenses
		can be difficult to the short refresh rate of the list.

		When you login to MET/TRACK as the MT user and choose
		"Setup/Licenses", then select the "Connections" tab, a list
		of connected applications is presented.

		The list is refreshed every 2 to 3 seconds. If the list is
		long, there may be insufficient time to locate and select
		the connection to be dropped before the list is refreshed.
		When the list is refreshed, the cursor moves to the top of
		the list.  This can lead the user to drop the wrong connection.

		V7.20 SP1 resolves this problem.  The list refresh rate
		has been slowed down to allow sufficient time to drop the
		desired connection.

	----> MET/TRACK Modified to Reread MET/CAL Default Procedure Directory
	      on Each Access

		Report Number:  MC-3258
		Resolved:	Oct 03 2007
		Application:    MET/TRACK

		In the MET/CAL V7.20 release (MET/TRACK build #434), MET/TRACK
		MET/TRACK reads the value of the MET/CAL default procedure
		directory once when MET/TRACK starts. If the directory is
		changed (using the MET/CAL Run Time or Editor applications)
		while MET/TRACK is running, it is necessary to close and
		restart MET/TRACK in order for it to know about the new value.

		In V7.20 SP1, MET/TRAK has been modified so that it rereads
		the MET/CAL initialization file parameter value specifying
		the default procedure directory prior to each use of the value.

	----> MET/CAL Changed To Ignore ASK+ P For MEMC & MEMCX Statements

		Report Number:  43955
		Resolved:	Sep 28 2007
		Application:    MET/CAL

		In V7.20 (and prior) it's too easy to fall into a procedure
		coding trap by forgetting to set ASK- P before executing a
		MEMC or MEMCX statement.

		Up to and including V7.20u MET/CAL always rigidly followed
		the definition of the ASK 'P' flag, regardless of the type
		of the evaluation statement.

		The problem with this approach is that because MEMC and MEMCX
		always just compare two numeric values, there's never any
		utility in repeating the comparison without having had an
		opportunity to modify one or both of the values being compared.

		Another complication of the this approach is the fact that by
		not re-establishing the reference output, MET/CAL resets it's
		internal memory of the reference accuracy.  This has the effect
		of disabling the TSR and measurement uncertainty calculations.

		In MET/CAL V7.20 SP1 the default operation of Post Test
		"Repeat" and "Cancel" have been altered so that when ASK+
		P is set and the evaluation statement is MEMC or MEMCX,
		MET/CAL ignores the ASK+ P setting and behaves as if ASK-
		P is set.  In other words, procedure control jumps back to
		the first line of the test (X.001) or to a TARGET or TARGET
		-p statement (if any) in the test.

		As an override, users may set "ask_p_memc_memcx = yes" in
		their initialization file to cause MET/CAL to revert to the
		old method.

		V7.20v or later is required.

	----> Functions To Generate SI Prefix / Engineering Units Format
	      from Dimensioned Value

		Report Number:  43951
		Resolved:	Sep 28 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 there are two new MATH functions that
		may be used to format dimensioned values in SI prefix /
		engineering units format:

		(1) ENGR - reformat dimensioned quantity to SI prefix /
		    engineering units format.

		    Example:

			ENGR("12345.6 kV") generates "12.3456 MV".

		(2) ENGR_NSD - format number, units, NSD, to dimensioned
		    quantity in SI prefix / engineering units format.

		    Example:
	
			ENGR_NSD(1234.5, "mV", 4) generates "1.234 V".

		Refer to on-line help for the MATH FSC for details.

		V7.20v or later is required.

	----> Functions To Extract Numeric Values From Strings

		Report Number:  43904
		Resolved:	Sep 26 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes two new MATH FSC functions used
		to extract embedded numeric values from strings:

			NUM  - extract 1st numeric value from string

			NUMN - extract n-th numeric value from string,
			       or count numeric values in string

		Refer to the MATH FSC help file for additional information.

		V7.20u or later is required.

	----> Functions to Strip Leading And/Or Trailing Spaces From Strings

		Report Number:  43903
		Resolved:	Sep 26 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes 3 new MATH functions to strip
		spaces from strings:

			STRIP  - strip leading and trailing white space
			         from string

			STRIPL - strip leading white space from string

			STRIPT - strip trailing white space from string

		Refer to the MATH FSC help file for additional information.

		V7.20u or later is required.

	----> Beep Enhanced to Support Trip On Operator Response

		Report Number:  43872
		Resolved:	Sep 25 2007
		Application:    MET/CAL

		In V7.20 (and previous versions) there's an optional "beep"
		parameter that may be used to cause MET/CAL to beep when
		certain operator prompts appear.

		The beep parameter covers many of the standard prompts:

			DISP FSC
			EVAL FSC
			OPBR FSC
			SET FSC
			connection message prompts
			prompt for UUT value
			range message prompt
			Editor prompt on file save operation
			Editor overwrite prompt
			... and several others

		The beep is controlled by an initialization file parameter
		with this format:

			beep = off | none | <delay>[,<count>]

		Setting "beep" to "off" or "none", or setting the count to
		zero, disables the beep.

		<delay> specifies the inter-beep delay, in seconds.  (It is
		also the delay before the initial beep.)

		<count> is optional and defaults to 1.

		When the beep parameter was first supported, it was
		anticipated that most users would set the count to 1 (or
		perhaps a small number like 2 or 3).  The idea was to set
		the delay to a relatively large number (like 10 seconds),
		so as not to annoy the user.

		This use is valid, and is probably preferred by some users.

		However, in noisy environments, or where operators are
		multi-tasking, one might want a more or less continuous beep.

		One can achieve something like a continuous beep in the
		current implementation by specifying a large <count>, but
		there's a problem with this.  The problem is that MET/CAL
		completes the beep sequence regardless of when the user
		responds to the prompt.

		In V7.20 SP1 the "beep" initialization file parameter has
		been enhanced.	The new syntax is:

			beep = off | none | <delay>[,<count>][, trip]

		This is the same as before except that you can now include
		"trip".

		For example:

			beep = 0.5, 50, trip

		indicates that there should be an inter-beep delay of 0.5
		seconds, there should be at most 50 beeps, and the beep
		sequence should be terminated when the user responds to
		the prompt.

		Specifying "trip" without a count indicates that beeping
		should continue until the user responds to the prompt,
		without any maximum number of beeps.

	----> New MATH Function to Get Name of Accuracy File

		Report Number:  43817
		Resolved:	Sep 24 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a new function, "AccName", that
		can be used to find the name of an accuracy file.

		For example:

			MATH InstrName = "Fluke 5700A"
			MATH AccFileName = AccName(InstrName)

		The name returned is the name of the accuracy file that
		will be used in calls to "ACCV", "ACCV2", etc. when the
		same instrument name is specified.  It is also the same as
		the file that will be used by built-in FSCs, as long as the
		accuracy file name has not been overridden using ACCF.

	----> 8560, 8566, and 8590 FSCs Modified To Support Delta Marker
	      Measurement

		Report Number:  MC-3384, MC-3385, MC-3386
		Resolved:	Sep 18 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the FSCs for the HP 856x and 859x
		spectrums analyzers have been updated to support delta
		marker measurement.

		Refer to on-line help for the 8560, 8566, and 8590 FSCs
		for details.

	----> Guardbanded Tolerance Error Calculation Enhanced

		Report Number:  43702
		Resolved:	Sep 18 2007
		Application:    MET/CAL

		MET/CAL V7.20, and earlier versions that support guardbanding,
		calculate the Tolerance Error based on the guardbanded
		pass limits.  (In other words, if the UUT value in a test is
		exactly at the crossover point between a "pass" and a "pass
		indeterminate", the Tolerance Error will be reported as 100 %.)

		A number of users have indicated that they would prefer to
		base the calculation on the UUT's specified limits.

		MET/CAL V7.20 SP1 supports a new guardbanding parameter
		"gb_tol_err" that allows the procedure writer to configure
		how the Tolerance Error calculation is performed.

		If "gb_tol_err = spec" the Tolerance Error calculation is
		based on the UUT's specified limits.  (With this setting the
		calculation is the same as the non-guardbanded calculation.)

		If "gb_tol_err = gb_pass" the Tolerance Error calculation
		is based on the guardbanded pass limits.  This setting is
		compatible with MET/CAL V7.20.

		The default "gb_tol_err" parameter value is "spec".

		Refer to the VSET help file and the guardbanding manual
		("Guardbanding.pdf") for additional information.

		MET/CAL V7.20t or later is required.

	----> New MATH FSC Function To Determine If File Is Positioned At EOF

		Report Number:  43518
		Resolved:	Sep 07 2007
		Application:    MET/CAL

		In V7.20 SP1 there's a new MATH FSC function named "EOF".
		"EOF" determines if a specified file is currently positioned
		at end of file (EOF).

		(This function requires V7.20t or later.)

		Refer to on-line help for the MATH FSC for details.

	----> New MATH FSC Function to Count Lines of File

		Report Number:  43517
		Resolved:	Sep 07 2007
		Application:    MET/CAL

		In V7.20 SP1 there's a new MATH FSC function named "LineCount".
		"LineCount" counts the lines in a specified file.

		(This function requires V7.20t or later.)

		Refer to on-line help for the MATH FSC for details.

	----> 5320 FSC Modified To Support New HIPOT Timer Function

		Report Number:  MC-3320
		Resolved:	Aug 30 2007
		Application:    MET/CAL

		At the time of the MET/CAL V7.20 release the 5320A did
		not support the HIPOT timer function.  Subsequent hardware
		and/or firmware updates to the 5320A added this capability.
		In HIPOT timer mode the 5320A calibrator can now measure
		the time interval for which a HIPOT tester delivers the
		output voltage.  The 5320A senses the voltage presented on
		(V - COM) and displays the time interval in seconds.

		In V7.20 SP1 the 5320 FSC supports the HIPOT timer function.

	----> 5320 FSC Modified To Support New HIPOT Leakage Current Function

		Report Number:  MC-3319
		Resolved:	Aug 30 2007
		Application:    MET/CAL

		When the submenu "HIPOT LC" is chosen, the 5320A calibrator
		can simultaneously measure the output voltage and leakage
		current of HIPOT testers.  Option 5320A LOAD is necessary
		for leakage current calibrations.

		In V7.20 SP1 the 5320 FSC supports the HIPOT leakage current
		function.

	----> Support For Voltage Calibrator Load Current Measurement Added
	      to 5320 FSC

		Report Number:  MC-3374
		Resolved:	Aug 15 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC did not support voltage
		calibrator load current measurement.

		For example, the following PORT statement that communicates
		directly with the 5320A on the serial interface has no
		equivalent in V7.20 using the 5320 FSC:

			PORT  SAF:VOLT:CURR?;:Outp:Stat On [13])

		In MET/CAL V7.20 SP1 the 5320 FSC has been enhanced to
		support this measurement function.

	----> Fluke (Datron) 9100 Accuracy File Updated

		Report Number:  42246
		Resolved:	Jun 28 2007
		Application:    MET/CAL

		V7.20 SP1 includes an updated version of the 9100 accuracy
		file ("9100.acc").

		The floor spec on two ranges in the DC power, where aux
		output is voltage, has been increased.

		The change was made because the floor spec on Aux DCV O/P
		was incorrectly listed in the published specifications as
		tighter than main DCV O/P.

		The accuracy file section to be modified is:

			# DC Power (auxiliary output is voltage)
			# Scale Factor >= 1mV/A

			Mode: Amps AX >=1mV/A

			# NOMINAL                 MOD1       Tol.   Floor   Res.
			# ----------------------  ---------  -----  ------  ----
			-32.00        32.00       NA    NA   0.012  0.003   0.01
			-320.0        320.0       NA    NA   0.006  0.005   0.1
			-3.200e+3     3.200e+3    NA    NA   0.006  0.042   1

		After the change this section is:

			# DC Power (auxiliary output is voltage)
			# Scale Factor >= 1mV/A

			Mode: Amps AX >=1mV/A

			# NOMINAL                 MOD1       Tol.   Floor   Res.
			# ----------------------  ---------  -----  ------  ----
			-32.00        32.00       NA    NA   0.012  0.006   0.01
			-320.0        320.0       NA    NA   0.006  0.006   0.1
			-3.200e+3     3.200e+3    NA    NA   0.006  0.042   1

	----> Support Improved for Test Uncertainty Ratio and Measurement
	      Uncertainty Calculations with Non-Linear Units

		Report Number:  21334
		Resolved:	Jun 21 2007
		Application:    MET/CAL

		In MET/CAL V7.20 SP1 the test uncertainty ratio and measurement
		uncertainty calculations have been modified to implement
		linearization of logarithmic units for all logarithmic units
		known to MET/CAL.  Previously linearization was performed only
		for dBm, and then only when a built-in instrument driver was
		used (i.e., not when an ACC statement was used to specify the
		reference accuracy in dBm for a user-configured instrument).

		In cases where MET/CAL has no built-in knowledge about how
		to linearize a logarithmic value, it may be necessary for
		the procedure writer to use the ACC and/or VSET FSCs to
		specify how the linearization is to be done.

	----> List Box Capability Added to MET/CAL Procedure Language

		Report Number:  42096
		Resolved:	Jun 20 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 includes a suite of new MATH functions
		to allow the procedure writer to construct and display list
		box windows to present choices to the operator.

		A list box window has 4 major components:

			(1) a read-only text area
			(2) a list box
			(3) a text-entry area
			(4) buttons

		The first 3 components are optional.

		Features provided include:

			(a) specifying window title
			(b) adding text to read-only text area
			(c) including MESS message in text area
			(d) adding items to list box
			(e) choosing multi-selection list box
			(f) controlling initial highlight
			(g) resizing window
			(h) customizing buttons
			(i) determining user's list box selection
			(j) re-using list box windows
			(k) sorting list box items
			(l) searching list box items

		The new MATH functions are:

			lbAdd      - add item to list box
			lbAddList  - add list of items to list box
			lbButton   - add button to list box window
			lbClose    - close list box window
			lbConf     - list box window attribute configuration
			lbGetSel   - get name of selected item from list box
			lbGetSelX  - get index of selected item from list box
			lbNew      - create new list box window
			lbResp     - get user's response
			lbSel      - select item in list box (by name)
			lbSelCount - get count of selected items in list box
			lbSelX     - select item in list box (by index)
			lbShow     - display list box window
			lbText     - add line to multiline edit control
			lbUnSel    - remove selection of item (by name)
			lbUnSelX   - remove selection of item (by index)

		Refer to on-line help for the MATH FSC for additional
		information.

	----> VSET Parameters to Specify Linearization Method and Impedance

		Report Number:  40956
		Resolved:	Jun 20 2007
		Application:    MET/CAL

		For all versions of MET/CAL up to and including V7.20,
		automatic linearization of values with logarithmic units in
		an ACC statement for purposes of the test specification ratio
		and measurement uncertainty calculations was not performed.

		However, with the addition of support for linearization
		of log units in ACC statements (e.g., dB, dBm, dBuV, ...),
		a method to allow the procedure writer to indicate how the
		linearization should be done, would be useful.

		For example, in the case of dBm, the system has know way of
		knowing if linearization should be to watts or to volts.

		When dBm are linearized to volts it is also necessary to
		know the impedance value.

		V7.20 SP1 includes two new VSET parameters to allow the
		specification of the linearization method and the impedance
		value.

		The new parameters are:

			(1) "LogLin" specifies the linearization method.
			    Choices are:

				DV - delta voltage
				DW - delta power
				V  - voltage
				W  - power

			(2) "Imped" specifies the impedance.  The impedance
			    is required for dBm to V linearization only.

		Refer to on-line help for the VSET FSC for details.

	----> MATH Functions to Convert Percentage Deltas to dB
	      Deltas & Vice Versa

		Report Number:  40366
		Resolved:	Jun 20 2007
		Application:    MET/CAL

		MET/CAL V7.20 already includes functions which convert back and
		forth between percentages and decibels.  These functions are:

			PCTTODBV - % to dB (voltage)
			DBTOPCTV - dB to % (voltage)
			PCTTODBW - % to dB (power)
			DBTOPCTW - dB to % (power)

		In some cases, however, it is necessary to work with
		percentages which represent deltas relative to a starting
		value.	A percentage delta can be converted to a corresponding
		gain or loss in decibels.  Therefore, MET/CAL V7.20 SP1
		provides 4 new functions: MET/CAL provided 4 new functions:

			DBTOPCTV_D - dB to % (voltage ratio delta)
			DBTOPCTW_D - dB to % (power ratio delta)
			PCTTODBV_D - % to dB (voltage ratio delta)
			PCTTODBW_D - % to dB (power ratio delta)

		Refer to on-line help for the MATH FSC for details.

	----> Modify ACC FSC to Allow Specification of Linearization Flag
	      and Impedance

		Report Number:  40954
		Resolved:	Jun 20 2007
		Application:    MET/CAL

		In V7.20, and prior versions, MET/CAL does not automatically
		linearize logarithmic units that appear in ACC statements
		in order to perform test specification ratio and measurement
		uncertainty calculations.

		However, with the addition of support for linearization
		of log units in ACC statements (e.g., dB, dBm, dBuV, ...),
		a method to allow the procedure writer to indicate how the
		linearization should be done was required.

		Without this capability, in the case of dBm, for example,
		MET/CAL would have no way of knowing if linearization should
		be to watts or to volts.

		When dBm are linearized to volts it is also necessary to
		know the impedance value.

		In V7.20 SP1 the ACC FSC has been enhanced to allow a
		linearization method to be specified in the CON field, and, if
		required, an impedance value to be specified in the MOD1 field.

		Refer to on-line help for the ACC FSC for details.

		MET/CAL also allows the linearization method and impedance
		to be specified using VSET parameters.	See report number
		40956 above.  The two method, ACC and VSET, are alternate
		methods.  For each test only one method should be used.
		The advantage of ACC is that it allows the compile time
		T.U.R. calculation to be performed.  The advantage of VSET
		is that it allows the values to be dynamiclly determined
		under procedure control.  Procedure writers must choose the
		best method based on procedure requirements.

		The virtue of supporting the specification of the linearization
		method and the impedance value in an ACC statement is that
		the method is static.  Static data may be used at compile
		time in the generation of a T.U.R. report.

	----> Support Added for 5320A-LOAD

		Report Number:  MC-3306
		Resolved:	Mar 28 2007
		Application:    MET/CAL

		MET/CAL V7.20 does not support the 5320A-LOAD.

		Support is included in V7.20 SP1.

		Note that the 5320A-LOAD is a manual standard.	It is not
		directly supported by the 5320 FSC.  A procedure writer
		must use the STD and ACCV FSCs to establish traceability
		and accuracy for 5320A-LOAD resistance values.	V7.20 SP1
		includes an accuracy file for the 5320A-LOAD.

	----> Add Support for Selecting Series Resistance of RCD Function
	      in 5320 FSC

		Report Number:  MC-3304
		Resolved:	Mar 19 2007
		Application:    MET/CAL

		In MET/CAL V7.20 the 5320 FSC does not allow series resistance
		to be selected in RCD functions.

		In MET/CAL V7.20 SP1 "SeriesResistance" has been added as
		a legal parameter for the RCDC and RCDT modes.	Legal and
		default values are listed in the updated 5320 FSC help file
		("5320.hlp").

	----> Add Support for 5320A HV ADAPTER /R MULTIPLIER

		Report Number:  39912 (MC-3275)
		Resolved:	Feb 28 2007
		Application:    MET/CAL

		MET/CAL V7.20 SP1 supports the Fluke 5320A HV ADAPTER /R
		MULTIPLIER.

		The multiplier was unavailable at the time of the V7.20
		release and therefore was not included in V7.20.

	----> 5320 FSC High Resistance Multiplier Enabled

		Report Number:  39024 (MC-3242)
		Resolved:	Feb 28 2007
		Application:    MET/CAL

		Due to lack of hardware availability, the 5320A high
		resistance multiplier was not support by the 5320 FSC in
		the V7.20 release.

		In V7.20 SP1 the high resistance multiplier is now supported.

		Refer to on-line help for the 5320 FSC for details.

	----> Provide Option to Disable Post Test "Repeat" Button

		Report Number:  22557 (MC-2396)
		Resolved:	Jan 08 2007
		Application:    MET/CAL

		In V7.20 SP1 there's new ASK 'Z' flag which controls the
		Post Test "Repeat" button.

		Specifying "ASK+ Z" causes the Post Test "Repeat" button to
		be enabled.

		Specifying "ASK- Z" causes the Post Test "Repeat" button to
		be disabled (grayed out).

		The default is controlled by the optional initialization file
		parameter "ask_z_default".  For compatibility with previous
		versions of MET/CAL, "ask_z_default", if not specified,
		defaults to "yes".

	----> Construction to Allow Specification of Binary Values in Hex

		Report Number:  39369 (MC-3260)
		Resolved:	Dec 12 2006
		Application:    MET/CAL

		MET/CAL V7.20 SP1 supports a new special construction, 'X',
		used to cause the output of binary values specified in ASCII
		hex format.

		The 'X' construction is intended primarily to assist in
		controlling instruments which must be programmed by sending
		binary values, and that document their remote commands in
		hexadecimal format.

		The format of the construction is:

			[X<hex list>]

		where <hex list> is a sequence of one or more hex bytes in
		ASCII format.

		Example 1:

			IEEE [XFF]

			This is equivalent to "IEEE [255]" (using the existing
			construction that specifies output values in ASCII
			decimal format.)

		Example 2:

			PORT [@COM1][X0D0A]

			This causes MET/CAL to write two characters, a
			Carriage Return and a Linefeed, to COM1.

		Rules for the 'X' construction:

		(1) ASCII hex specifications are case-insensitive.

		(2) One or more hex bytes may be specified in the list.
		    Each byte requires 2 ASCII hex characters.

		(3) Spaces are allowed between hex bytes, but not between
		    the 2 ASCII hex digits which represent a single byte.

		Although the 'X' construction is designed primarily for use
		with the IEEE, IEEE2, SCPI, PORT, and RESET FSCs, all of
		the following FSCs support the 'X' construction:

			DISP
			EVAL
			HEAD
			IEEE
			IEEE2
			MEM2
			MEMI
			MESS
			NVI FSCs (5320, 6100, 9640, N5531, PSA)
			OPBR
			PORT
			RESET
			RSLT
			SCPI
			SET
			VSET
			WAIT

-------------------------------------------------------------------------------
Section 5:  Beta Features -----------------------------------------------------
-------------------------------------------------------------------------------

	MET/CAL V7.20 SP1 includes a preliminary implementation of a new
	instrument control FSC named "VISA".

	The VISA FSC provides direct access to instruments using the National
	Instruments VISA library (NI-VISA).

	To enable the "VISA" FSC in MET/CAL V7.20 SP1 it is necessary to
	add the following line to the [Startup] section of the MET/CAL
	initialization file ("metcal.ini"):

		NI-VISA = Yes

	The "VISA" FSC may currently be used with instruments on the following
	interface types:

		Ethernet
		IEEE-488
		RS232
		USB

	The primary benefit of using the VISA FSC is that it provides access
	to USB and Ethernet UUTs.

	The VISA FSC is usable with IEEE-488 and RS232 instruments, but
	existing FSCs (IEEE, IEEE2, SCPI, and PORT) already support those
	interfaces.

	Restrictions:

		In V7.20 SP1 there are a number of VISA FSC restriction.
		These will be addressed in a future service pack or release:

		(a) VISA is restricted to use with the UUT.  That is, it cannot
		    be used to control a user-configured reference instrument.
		    (This is primarily because the MET/CAL Config Editor does
		    not yet support the other interface types.)

		(b) The RESET FSC cannot be used to reset a USB or Ethernet
		    UUT.

		(c) The are a number of instrument interfaces (such as VXI,
		    PXI, and Firewire) that are supported by NI-VISA, but
		    are not yet supported by the VISA FSC.

		(d) Fluke has done limited testing of the VISA FSC using
		    Ethernet and USB instruments.

		    For Ethernet instruments, VISA works best with instruments
		    that comply with the VXI-11 standard.  (Note:  The
		    "VXI-11" standard does not imply that the instrument is
		    a VXI instrument.)	We have tested the VISA FSC using an
		    Anritsu spectrum analyzer with an Ethernet (LAN) interface.

		    For USB instruments, VISA works best with USBTMC
		    instruments.  (USBTMC stands for "USB Test & Measurement
		    Class".)  We have used the VISA FSC with Agilent and
		    Keithley USB instruments.

	Licensing:

		MET/CAL users must comply with National Instruments' NI-VISA
		licensing requirements.

		There are two types of National Instruments NI-VISA licenses,
		a "Deployment License" and a "Development License.

		To use the VISA FSC in MET/CAL you must have a Development
		License.

		If you own a National Instruments IEEE-488 interface,
		you automatically have the right to use NI-VISA at no
		additional cost.  There are other National Instruments
		hardware and software products as well that include an
		NI-VISA Development License.

		Go to "http://www.ni.com/visa" to for complete information
		regarding NI-VISA licensing requirements.

	Installation:

		Before using a MET/CAL procedure that contains VISA statements
		it is necessary to install the NI-VISA library.

		The library is not distributed with MET/CAL.  You must obtain
		the library from National Instruments and follow National
		Instruments' instructions.

		If you have not already installed NI-VISA, go to
		"http://www.ni.com/visa" to download the library.  The NI-VISA
		library is also distributed on CD when you purchase a National
		Instruments IEEE-488 interface.  If you have a fairly recent
		interface you may be able to install NI-VISA from the CD
		rather than downloading from the National Instruments website.
		In general, Fluke recommends downloading the latest version
		of NI-VISA from the National Instruments website.

		If you are running and/or developing only procedures that
		do not contain VISA statements, the NI-VISA library does
		not have to be installed on your MET/CAL workstation.

	If you have questions about using NI-VISA with MET/CAL please contact
	Fluke MET/SUPPORT.

-------------------------------------------------------------------------------
End "readme720sp1.txt"
-------------------------------------------------------------------------------
