------------------------------------------------------------------------------- ------------------------------------------------------------------------------- MET/CAL V.710 Dec 09, 2004 File name "readme710.txt" ------------------------------------------------------------------------------- Section 1: Table of Contents ------------------------------------------------- ------------------------------------------------------------------------------- 1. Table of Contents 2. Introduction 3. Installation Instructions 4. What's New in V7.10 Description of significant new features in V7.10. 5. On Time Support Products On Time Support products which work with the MET/CAL database. 6. Crystal Reports Reports provided with MET/CAL V7.10. 7. Minor Enhancements in V7.10 Reports on minor improvements in V7.10. These improvements are not covered in section 4. 8. Documentation Overview of product documentation. 9. Accuracy and Help File Information 10. V7.10 Problem Reports 11. V7.01 SP2 Problem Reports 12. V7.01 SP1 Problem Reports 13. Contacting Fluke How to contact Fluke with MET/CAL questions, problems, or suggestions. 14. Bonus CD ------------------------------------------------------------------------------- Section 2: Introduction ------------------------------------------------------ ------------------------------------------------------------------------------- MET/CAL V7.10 includes a variety of new features not present in V7.01. In addition, MET/CAL V7.10 incorporates all maintenance updates released in the two V7.01 service packs (SP1 and SP2). Please contact MET/SUPPORT (metsupport@fluke.com) if you have questions about MET/CAL V7.10. The reports in sections 10, 11 and 12 describe all changes made between V7.01 and V7.10. Section 10 includes reports which describe changes in V7.10, after the release of V7.01 SP1. Section 11 includes reports which describe changes in V7.01 SP2, after the release of V7.01 SP1. Section 12 includes reports which describe changes in V7.01 SP1, after the release of V7.01. The reports in sections 10, 11, and 12 are in Report Number order, beginning with the most recent. ------------------------------------------------------------------------------- Section 3: Installation Instructions ----------------------------------------- ------------------------------------------------------------------------------- The basic procedure for installing MET/CAL V7.10 is to insert the MET/BASE V7.10 CD and follow the instructions. The MET/CAL Install Manual has been updated for the V7.10 release. If you are upgrading, you should run "dbupdate.exe" after the installation. Run "dbupdate.exe" before using the applications (Run Time, Editor, MET/TRACK). ------------------------------------------------------------------------------- Section 4: What's New in V7.10? ---------------------------------------------- ------------------------------------------------------------------------------- ----> Add Guardbanding Techniques Report Number: 3111 Application: MET/CAL MET/CAL V7.10 supports guardbanding. Refer to the document "Guardbanding.pdf". Guardbanding-related parameters are also documented in the VSET on-line help file, which may be viewed using the MET/CAL Editor. ----> Special Constructions Embedded in Brace Data Not Evaluated in Results Table Report Number: 7735 Application: MET/CAL MET/CAL V7.10 modifies the handling of "special constructions" embedded in result brace data. MET/CAL special constructions are procedure language constructs enclosed in brackets, and supported by some FSCs. An example of a special construction is "[MEM]". When embedded in a text string in a procedure statement this construction indicates that the value of memory register MEM should be inserted in the string in place of the literal text "[MEM]". For example, consider the two procedure lines: MATH MEM = 20.1 HEAD Temperature = [MEM] degC When the HEAD statement is executed the user will see text containing the evaluated construction, namely: Temperature = 20.1 degC Enclosing text in braces ('{' ... '}') is a concise MET/CAL directive which indicates that the enclosed text should be included in the saved result data. Thus, for example: MATH MEM = 20.1 HEAD {Temperature = [MEM] degC} indicates that not only should the user be shown: Temperature = 20.1 degC on the Run Time display during procedure execution, but also indicates that the text should be included in the generated results. The deficiency addressed in this report is that prior to V7.10 MET/CAL did not evaluate special constructions enclosed in braces for purposes of result generation. Thus, using the example above, one would find that the result data contained: Temperature = [MEM] degC rather than the text which was most likely desired: Temperature = 20.1 degC MET/CAL V7.10 corrects this problem. The "Remark" field in the Results Table now contains brace data in which embedded special constructions have been evaluated, rather than simply written literally. It is important to realize that this change applies to the Results Table only. It does not apply to legacy results (i.e., to the CalResults Table). This change appeared initially in V7.01 SP2. ----> Support Clarke-Hess 6000 Phase Meter Report Number: 8165 Application: Editor, Run Time MET/CAL V7.10 includes a new FSC, "6000", to support the Clarke-Hess 6000 phase meter. The FSC supports phase from -180 to +180 degrees, or from 0 to 360 degrees, frequency from 5 Hz to 500 kHz, and amplitude from 10 mV to 350 V RMS. Specifically, a driver for the Clarke-Hess should be able to select phase ranges of 0-360 and +/- 180 degrees. The ability to select offsets for the Clarke-Hess is probably not required within the driver itself. The Clarke-Hess 6000 has an IEEE-488 interface only. Refer to the Editor's on-line help for the 6000 FSC for additional information. ----> Support Fluke PM 6304, 6304C, & 6306 RCL Meters Report Number: 8166 Application: Editor, Run Time The following FSCs have been implemented: 6304 M6304 6304C M6304C 6306 M6306 The PM 630x driver supports IEEE-488 and RS-232. Therefore, these FSCs are supported in 5500/CAL as well as MET/CAL. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> FSC for the Agilent/HP 53100 Series Universal Counters Report Number: 8713 Application: MET/CAL MET/CAL V7.10 includes new FSCs: 53131 M53131 53132 M53132 53181 M53181 Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Add RSLT and Brace Data to Test Results Window Report Number: 11578 Application: MET/CAL In V7.10 RSLT FSC data, and brace data, now appear in the Test Results window. The color used is cyan, to distinguish from red, green, yellow evaluation data. ----> Add Special Function 26 (Set Ref) to M8902 TOLERANCE Field Report Number: 13726 Application: Editor, Run Time Added support for MOD3 "RS" (Reference Set) to 8902 FSC. Added support for units "dB" to 8902 FSC Nominal field. Added support for special function 26 (relative mode) to M8902 FSC. Examples: 1.004 DISP Set the attenuator to 0 dB. 1.005 6060 0D 1GH -D S L 1.006 8902 0D 1GH RS N # Specify relative mode. 1.007 M8902 26.1SP H0 L0 1.008 HEAD 10 dB 1.009 DISP Set the attenuator to 10 dB. 1.010 6060 0D 1GH -D S L 1.011 8902 -10.0dB 0.1U 1GH TL 2.001 DISP Set the attenuator to 20 dB. 2.002 6060 0D 1GH -D S L 2.003 8902 -20.0dB 0.1U 1GH TL ----> MATH FSC: New Functions for dBm to watts and watts to dBm Report Number: 14986 In V7.10 two new functions, "dbmtow" and "wtodbm", have been implemented. Refer to the Editor's on-line help for the MATH FSC, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Add Argument to DOS/DOSE to Suppress Use of "user_prog_dir" Report Number: 15090 Application: Editor, Run Time In some cases it is convenient to be able to override the normal use of the initialization file parameter "user_prog_dir" when executing a DOS or DOSE statement. This situation may arise, for example, when executing a Windows utility program (like the media player) rather than a MET/CAL-specific user program. This capability exists in V7.01, but only if the full path name is specified in the procedure. Moreover, the procedure line length limitation may make it difficult to include a full path specification in the DOS/DOSE procedure statement. This forces the use of string registers, which in turn makes it more difficult to indicate to MET/CAL that a full path name is being specified. For example, the following procedure illustrates what has to be done to execute a user program not in the directory specified by "user_prog_dir": 1.001 DISP Invoke Microsoft Word 1.001 DISP with a specified document. # Set up the full path to ".doc" file to be opened. 1.002 MATH s[2] = "D:/metcal/help/mydoc.doc" # Specify the full path of the application. 1.003 MATH s[1] = "/Program Files" 1.004 MATH s[2] = "/Microsoft Office" 1.005 MATH s[3] = "/Office10" 1.006 MATH s[1] = s[1] & s[2] & s[3] & "/WinWord.exe" # Invoke the application (Word) with the specified # file ("mydoc.doc"). 1.007 DOS -x C:[S1] [S2] Notice that in the example above it was necessary to specify the beginning of the full path to Word, "C:", in the DOS procedure statement. Including "C:" in string register S[1] would have prevented MET/CAL from realizing that the specification was a full path specification, which would then have caused the value of "user_prog_dir" to be prepended to the user program specified in the DOS statement. If a "user_prog_dir" override capability were available, users could rely on the Window PATH specification to define the directories to be searched, which would allow the procedure to be written without a full path specification of the program to be executed. V7.10 solves the problem described above by added a new "-u" argument for use with the DOS and DOSE FSCs. Specifying "-u" causes MET/CAL to ignore the "user_prog_dir" specification (but only for the particular DOS or DOSE statement containing the "-u"). Using "-u", the example above can be simplified to: 1.001 DISP Invoke Microsoft Word 1.001 DISP with a specified document. # Set up the full path to ".doc" file to be opened. 1.002 MATH s[2] = "D:/metcal/help/mydoc.doc" # Specify the base name only of the application. 1.004 MATH s[1] = "WinWord.exe" # Invoke the application (Word) with the specified file # ("mydoc.doc"). 1.005 DOS -u -x [S1] [S2] ----> Support Wavetek 195 Function Generator Report Number: 19009 Application: Editor, Run Time The 195 FSC programs the Wavetek 195 Universal Waveform Generator to output DC voltage, or sine, square, triangle, positive ramp, negative ramp, and pulse waveforms. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Support Wavetek 39A Function Generator Report Number: 19010 Application: Editor, Run Time The 39A FSC programs the Wavetek 39A Universal Waveform Generator to output DC voltage, or sine, square, triangle, positive ramp, negative ramp, and pulse waveforms. The 39A FSC can also program Channel 1 of the Wavetek 195 Universal Waveform Generator. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Modify Accuracy File Header to Support a Cal Interval Range Report Number: 19205 Application: MET/CAL To better support customers who routinely extend cal intervals for standards MET/CAL V7.10 allows the cal interval in an accuracy file header to specify a range, rather than a specific interval. Example: The stock header of the Fluke 5700A 90-day accuracy file looks like this: Begin Header instrument = Fluke 5700A interval = 90 days confidence = 2.58 sigma End Header To change it so that the file is valid for any cal interval from 90 to 120 days write it like this: Begin Header instrument = Fluke 5700A interval = 90 - 120 days confidence = 2.58 sigma End Header There's also a new, associated, initialization file parameter, "acc_conflict". This parameter controls how to resolve conflicting accuracy files. A conflict occurs when two or more accuracy files for the same interval have overlapping cal interval ranges. "acc_conflict" has 3 legal values: Error Shortest Longest "Error" instructs MET/CAL to handle a conflict by generating an error message. "Shortest" instructs MET/CAL to resolve conflicts by choosing the accuracy file for which the lower end of the range is the smallest number. For example, if file 1 has an interval range of 90-120, and file 2 has an interval range of 100-130, file 1 will be chosen if "acc_conflict = shortest". "Longest" instructs MET/CAL to resolve conflicts by choosing the accuracy file for which the upper end of the range is the larest number. For example, if file 1 has an interval range of 90-120, and file 2 has an interval range of 100-130, file 2 will be chosen if "acc_conflict = longest". The default is "Error". ----> New IEEE2 and SCPI FSCs Report Number: 19213 Application: Editor, Run Time MET/CAL V7.10 includes two new FSCs, IEEE2 and SCPI. Both FSCs are similar to the existing IEEE FSC, except that IEEE2 is tailored specifically for IEEE-488.2 instruments, and SCPI is tailored specifically for SCPI instruments. The "tailoring" consists in the fact that these FSCs include built-in error checking based on requirements defined by the IEEE-488.2 and SCPI standards, respectively. The new FSCs support both commands and queries, although there are some restrictions on how commands and queries can be intermixed in a single IEEE2 or SCPI statement. Users should be aware that some instruments claim to be IEEE-488.2-compliant, or SCPI-compliant, but do not, in fact, correctly implement those remote communication standards. For such instruments it may be necessary to continue to use the IEEE FSC. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> FSC for Fluke 6100A ELectrical Power Standard Report Number: 19214 Application: MET/CAL MET/CAL V7.10 supports the Fluke 6100A Electrical Power Standard. Refer to the Editor's on-line help for the "6100" FSC, or to the on-line reference manual ("ReferenceManualV71.pdf"). ----> New Math FSC Function to Return Serial Number of Specified Asset Report Number: 19608 Application: Editor, Run Time V7.10 includes a new function in the MATH FSC, "SN", which returns the serial number of a specified asset. The serial number returned is the value of database Inventory Table field 4206. ----> Add Local Numeric Registers to the MATH FSC Report Number: 19706 Application: Editor, Run Time MET/CAL V7.10 supports a new group of 32 numeric registers, called the "L" registers. "L" registers function like the existing "M" registers, except that they are local to each procedure invocation. The MATH FSC has been updated to support the "L" registers. All FSCs which allow use of the [M] construction now also support the equivalent [L] construction. The Editor's Test Run "N-Reg" window shows "L" register values after the "M" register values. The TOL FSC has been updated to allow a tolerance value to be taken from an "L" register. This is true also for the TOLERANCE field in an instrument FSC. New MATH functions "avg_l", "min_l", "max_l", "rss_l", and "sdev_l", which are equivalent to "avg", "min", "max", "rss", and "sdev", respectively, have been added. The new functions use the "L" registers rather than the "M" registers. The Editor's on-line help files have been updated to include information on the "L" registers. The only restriction, compared to the "M" registers, is that the "L" registers cannot be directly written or read by the DOS and DOSE FSCs. The key thing about the L registers is that they are entirely local to each subprocedure invocation. For example, suppose Main calls SubA, which then calls SubB. Main will have 32 L registers. SubA will have it's own L registers (different from Main's), and SubB will have a separate set of L registers as well. Example: Write 3 procedures as follows: Instrument: Main MATH L[1] = 5 CALL SubA DISP Main: L1 = [L1] Instrument: SubA MATH L[1] = 10 Call SubB DISP SubA: L1 = [L1] Instrument: SubB MATH L[1] = 15 DISP SubB: L1 = [L1] When you run this procedure you will see, in order: SubB: L1 = 15 SubA: L1 = 10 Main: L1 = 5 Notice that each procedure has it's own, independent set of "L" registers, and that those registers are unaffected by subprocedure calls. The purpose of the "L" registers is to provide each procedure with some non-global variables which may be used within that particular procedure, and without having to worry about collisions with some other subprocedure making use of the same registers. ----> MATH Function to Convert HH:MM:SS to Seconds Report Number: 20121 Applications: Editor, Run Time V7.10 includes a new function in the MATH FSC, CTIME, which converts a time string formatted as HH:MM:SS to seconds. DD:HH:MM:SS is also supported, where DD is a number of days. All time components are optional. For example, "1::" means 1 hour. Example: MATH MEM = CTIME("1:2:3") causes the value 3723 to be assigned to MEM. (3723 = 1 * 60 * 60 + 2 * 60 + 3) Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> New MATH Function to Convert from Radians to Degrees Report Number: 20287 Application: Editor, Run Time In V7.01 there's an existing MATH function RAD to convert from degrees to radians. However, there's no function to convert from radians to degrees. In V7.10 a new MATH function, DEG, has been added to convert from radians to degrees. ----> Allow 6680-Based Procedure to Run with Configured 6681 Report Number: 20363 Application: Editor, Run Time Since the 6680 is a subset (in terms of function and accuracy) of the 6681, it would be convenient for procedure writers if MET/CAL allowed 6680-based procedures to run "as is" with a configured 6681. ----> New MATH FSC Function to Fetch Inventory Table Values Report Number: 20386 Application: Editor, Run Time V7.10 includes a new function in the MATH FSC, "INV", which returns the value of a specified database Inventory Table field for a specified asset. Refer to the Editor's on-line help for the MATH FSC for details. ----> New MATH FSC Functions to Convert Seconds Since 1970 to Formatted Date and Time Report Number: 20478 Application: Editor, Run Time V7.10 includes two new MATH FSC functions which convert values representing seconds since Jan 01, 1970 UTC to equivalent formatted date and time strings. "UGDT" converts to Universal Coordinated Time (UTC). Note that UTC was previously known as Greenwich Mean Time (GMT). "ULDT" is similar to "UGDT", but with the difference that it converts to local time, as defined by the timezone setting on the PC on which the procedure is executing. These functions allow a numeric time value returned by function "UTIME" to be converted back to a formatted date and time string. The date formatting control is the same as provided by the existing "DATE" function. Refer to on-line help for the MATH FSC for a more complete description. ----> IF, ELSE, ELSEIF, and ENDIF FSCs Would Facilitate Procedure Writing Report Number: 20778 Application: MET/CAL MET/CAL V7.10 includes new FSCs which support conditional execution. The new FSCs are: IF ELSE ELSEIF ENDIF Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Add Logical AND and Logical OR Operators to MATH FSC Report Number: 20924 Application: MET/CAL V7.10 adds logical AND and OR operators to the MATH FSC. The AND operator is "&&". The OR operator is "||". Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Allow Users to Colorize Procedure Statements in Editor Procedure Windows Report Number: 20928 Application: MET/CAL MET/CAL V7.10 improves procedure readability by allowing the procedure writer to specify display colors on a per-statement type basis. This enhancement addresses only the on-line display of procedures in the MET/CAL Editor. It does not address any run time display contexts, either in the Run Time application or in Editor Test Run. It also does not address printed copies of MET/CAL procedures. Type Ctrl+K in the MET/CAL Editor to invoke the "Configure Colors" window. ----> No Spanish Translations for Most MET/TRACK Text Strings Report Number: 21026 Application: MET/TRACK V7.10 improves support for the Spanish language in the MET/TRACK application. ----> Add Looping Constructs to MET/CAL Procedure Language Report Number: 21080 Application: MET/CAL MET/CAL V7.10 includes new FSC: WHILE ENDW DO UNTIL Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Expand Accreditation Flag to Allow Values Other than 0 and 1 Report Number: 21106 Application: MET/CAL In V7.10 legal Accreditation Flag values have been expanded to allow any integer between 0 and 32767 as a legal value. In addition, "yes" and "no" remain legal. ("Yes" is equivalent to 1 and "no" is equivalent to 0). Arbitrary string values are not allowed. This is an integer field in the database. ----> 2nd, 3rd, 4th... MDI Windows Should Default to Size of 1st MDI Window Report Number: 21287 Application: MET/CAL In V7.10 the Editor has been modified so that the size and position of the 2nd, 3rd, 4th, and 5th MDI child windows are remembered in the same way that size and position are remembered for the 1st MDI child window. The help window is not treated specially. Its size and position are remembered only insofar as it happens to be the 2nd, 3rd, 4th, or 5th child window. The size and position memory is based only on the window number. For example: open window A (#1) open window B (#2) open window C (#3) close window B open window D (#3) The point here is that when window D is opened it will be sized and positioned as the 3rd window because, at the time it's opened, there are 2 windows open already. Thus, in this example, C and D will (initially) have the same position and size, because they are both opened as the 3rd window (at the time). When the user resizes or repositions a window, the updated size and position information is associated with the window number which that window happened to have. If more than 5 child windows are open at once, MET/CAL reverts to default sizing and positioning for MDI child windows, and does not remember the size and position information. ----> Add support for other RTDs in Keithly 2002 FSC Report Number: 21562 Application: MET/CAL In V7.01 SP1 and earlier the Keithley 2002 FSC supports only the RTD: Type Standard Alpha Beta Delta PT385 IPTS-68 0.003850 0.11100 1.50700 In V7.01 SP2 the 2002 FSC has been improved to support the following additional RTDs: Type Standard Alpha Beta Delta PT100 ITS-90 0.003850 0.10863 1.49990 D100 ITS-90 0.003920 0.10630 1.49710 F100 ITS-90 0.003900 0.11000 1.49589 PT3916 IPTS-68 0.003916 0.11600 1.50594 The following table shows the MOD2 codes required in the procedure statement: FUNCTION NOMINAL MOD2 ----------------------------------------- D100 RTD -200degC to 630degC RD F100 RTD -200degC to 630degC R0 Pt100 RTD -200degC to 630degC RP Pt385 RTD -200degC to 630degC R1 Pt3916 RTD -200degC to 630degC R7 ----> Add Support for Other RTDs in Keithly 2001 FSC Report Number: 21673 Application: MET/CAL In V7.01 SP1 and earlier the Keithley 2001 FSC supports only the RTD: Type Standard Alpha Beta Delta PT385 IPTS-68 0.003850 0.11100 1.50700 In V7.01 SP2 the 2001 FSC has been improved to support the following additional RTDs: Type Standard Alpha Beta Delta PT100 ITS-90 0.003850 0.10863 1.49990 D100 ITS-90 0.003920 0.10630 1.49710 F100 ITS-90 0.003900 0.11000 1.49589 PT3916 IPTS-68 0.003916 0.11600 1.50594 The following table shows the MOD2 codes required in the procedure statement: FUNCTION NOMINAL MOD2 ----------------------------------------- D100 RTD -200degC to 630degC RD F100 RTD -200degC to 630degC R0 Pt100 RTD -200degC to 630degC RP Pt385 RTD -200degC to 630degC R1 Pt3916 RTD -200degC to 630degC R7 ----> Add Command-Line Argument to Generate Debug Output for IEEE-488 I/O Report Number: 21761 Application: MET/CAL To assist users in troubleshooting problems with IEEE-488 I/O, it would be helpful if MET/CAL supported an optional method of enabling debug output to show all data messages read from and written to IEEE-488 instruments. V7.10 includes this feature. Invoke Editor or Run Time with "-df -trace" specified on the command line and all IEEE-488 I/O from MET/CAL will be written to a file named "mcdebug.txt". "mcdebug.txt" will be located in the directory specified by the initialization file parameter "workdir". If you make multiple procedure runs within the application, successive data will be appended to "mcdebug.txt". If you restart the Editor or Run Time application, "mcdebug.txt" will be re-initialized (zeroed). Here's an example of the IEEE I/O trace output: dpr_open : 24-Jul-03 17:09:09 ib_wrt : 5 bytes ib_wrt : *IDN? ib_wrt : 15 bytes ib_wrt : *CLS;*RST;*OPT? ib_wrt : 16 bytes ib_wrt : *CLS;*RST;*SRE8 ib_wrt : 21 bytes ib_wrt : *SRE8;*CLS;STBY;OUT? ib_wrt : 6 bytes ib_wrt : FAULT? ib_wrt : 21 bytes ib_wrt : *SRE8;*CLS;STBY;OUT? ib_wrt : 6 bytes ib_wrt : FAULT? ib_wrt : 16 bytes ib_wrt : *CLS;*RST;*SRE8 ----> Add Support for Fluke 525A-P04 Pressure Module Report Number: 22101 Application: MET/CAL The Fluke 525A-P04 was added to the list of Fluke pressure modules after the initial list was created. V7.10 includes support for the Fluke 525A-P04. ----> Support Crystal Reports V10 Report Number: 23444 Application: MET/CAL The MET/CAL V7.10 release supports Crystal Reports V10. Full V10 support is available under Win2K and WinXP. Under WinNT reports may be executed (printed and preview using MET/TRACK and Run Time), but it is not possible to install the full Crystal Reports V10 distribution and write reports under WinNT. ----> Enhance 9500 Driver to Reduce Active Head Relay Transitions Report Number: 23787 Application: MET/CAL In V7.10 the 9500 FSC has been optimized to greatly reduce active head relay transitions. This change helps to extend the active head service interval. ----> New FSC "WAIT" to Specify Programmed Delays with Countdown Timer Report Number: 23886 Application: MET/CAL V7.10 includes a new FSC named "WAIT". The WAIT FSC is used to specify a programmed delay. There are three ways to use a WAIT statement: (1) To display a pop-up window which includes a procedure-specified message and a count-down timer showing hours, minutes, and seconds. (2) To generate a pop-up window which remains displayed for a specified number of milliseconds. (3) To delay procedure execution for a specified number of milliseconds, but without a pop-up message window. Refer to the Editor's on-line help for the WAIT FSC, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> New MATH FSC Functions for General Initialization File Access Report Number: 24379 Application: MET/CAL For some MET/CAL applications it is convenient to have general purpose MATH FSC functions to read and write values in standard initialization file-format files. Version 7.10 includes new MATH FSC functions, RIF and WIF, to read and write initialization files. Refer to the on-line help for the MATH FSC. Here is a brief summary of initialization file format: An initialization file is an ordinary text file. The file extension is usually ".ini", but this is only a convention, not a requirement. The file is divided into sections. Each section label is enclosed in brackets. For example, "[Temperature Values]" is a valid section label. Within each section there is a list of parameters. Each parameter has a name and value, separated by an equals sign. Rules for reading a value from an intialization file: (1) The file must exist. (2) The section label must exist in the file. (3) The parameter name must exist in the specified section. (4) The parameter must have a value. If any of conditions (1) to (4) are not satisfied, a empty string results from an attempt to read a parameter value. Rules for writing a value to an initialization file: (1) The drive on which the file resides must be writable. (2) The file must be writable. (3) If the file does not exist, it will be created. (4) If the section label does not exist, it will be created. (5) If the parameter name does not exist, it will be created. (6) The specified value will be written to the specific section of the specified file as the value of the specified parameter. Example 1 - Read Initialization File (RIF): MATH S[1] = "c:\\metcal\\test.ini" MATH MEM2 = RIF(S[1], "Sensor 1", "c1") Example 2 - Write Initialization File (WIF): MATH S[1] = "c:\\metcal\\test.ini" MATH MEM2 = WIF(S[1], "Sensor 1", "c1", "23.24 degC") ----> Support for Hart 1620 "dewK" Temperature / Humidity Recorder Report Number: N/A Application: MET/CAL The use of MET/CAL's existing support for relative humidity / temperature loggers with the Hart 1620 (and Fluke 5020A) is described in the manual "Hart1620.pdf". ----> Internationalized Install Program Report Number: N/A Application: MET/CAL Install Program With the V7.10 release MET/CAL now better supports international customers by including an internationalized installation program. The Install Program automatically detects local language settings and displays user information as appropriate in Chinese, Russian, and other languages (in addition to English). ------------------------------------------------------------------------------- Section 5: On Time Support Products ------------------------------------------ ------------------------------------------------------------------------------- On Time Support, Inc. provides software products to enhance or augment the functioning of your MET/CAL and MET/TRACK software. The following On Time Support programs may be purchased directly from Fluke. Contact your local Fluke representative for specific details, options, and prices. Additional information is also provided on Fluke's WEB site: http://www.fluke.com Metrology/Xplorer Metrology/Xplorer is a web-based query tool used to retrieve MET/CAL and MET/TRACK data with your browser, over the internet or your company's intranet. Barcode Magician Barcode Magician (BCM) is a product from On Time Support Inc. which allows you to automate repetitive database entry tasks such as checking in/out equipment, or changing equipment status simply and consistently for quantities of assets using a simple barcode tool or keyboard. BCM provides a simple, easy to use interface that allows your calibration technicians and instrument custodians a way to update your Fluke MET/BASE database quickly and efficiently while at the same time drastically reducing data entry errors and substantially increasing productivity. By using a barcode scanner in conjunction with this software, you can automate such tasks as: (1) Checking in/out equipment from a tool crib or instrument impound area. (2) Updating in-process status descriptors. (3) Changing location and association of assets. (4) Accepting instrumentation for repair work. (5) Virtually any database function other than calibration data entry, repair record creation, or addition of instruments. There are two versions of Barcode Magician: BCM Basic and BCM Plus. BCM Plus provides additional functionality beyond BCM Basic. Contact On Time Support for details. Barcode Magician Plus Barcode Magician Plus incorporates the standard features of Barcode Magician, but adds a few additional features: (1) New Calibration record with options to include (2) Standards Used and the New Full Cal Results. (3) New Maintenance record. (4) New Location record. (5) Comment field of your choice into any major table. The above functions are interactively entered per asset to allow processing different categories of instruments in the same transaction. You can process one asset at a time or a batch. The new record forms (default workstation only)include all the unsuppressed fields and look and function very similar to MET/TRACK 7.x. Only required fields need to be entered. Includes copy forwards, defaults, validated lists, pick lists, and calculated Due Date. Here are some more features: (1) New Instruments can be added while executing an Action Code. Each Action Code can be configured to allow/not allow new instruments. (2) This product allows manually entering CAL Results into the NEW Results table. New Batch Calibration Feature (BCM Plus): We added a new feature for creating calibration records quickly with two new variables, System Variable $INSERTCALRECORD$ and Custom Mod Variable @STDSUSED, that do not use up dialog boxes and allows entering an unlimited number of standards used per transaction. The prompt will occur right after the Dialog box prompts. Great for creating calibration records without the actual measurement results. One of the most requested functions has been batch calibration. Many labs calibrate several of the same type of instrument at the same time, for example thread gages. Another example is the calibration of radiation dosimeters that do not require actual instrument data, just Pass/Fail. Or, the lab manager may want to enter calibration records for instruments that were calibrated by an outside lab. This method will allow these instruments to be processed in a fraction of the time that it would normally take. EMail Notification EMail Notification is a product from On Time Support which allows you to schedule the automated delivery of EMail to your customers or other personnel. Messages may include notifications of various metrology activities such as the notification that instruments are due for calibration, escalation reports, instruments significantly out of tolerance, instruments due for pickup, or customer feedback surveys. These messages are automatically sent via a schedule which you determine using a simple web-based interface. Change/Log On Time Support has created a plug-in for the MET/TRACK database (version 6.x, 7.x) that keeps track of changes to the Inventory, Calibration, Location, Maintenance, Customer, and Standards tables. No front end program is required to configure the Change/Log option. Change/Log tracks database changes regardless of the application which makes the change. You can update your database using MET/TRACK Manual Entry, MET/CAL Run Time, Barcode Magician, ISQL, or any other application and Change/Log will maintain a full record of the change history. Change/Log is particularly useful for customers who may be subject to FDA regulatory requirements. An archive function is included. On Time Support has developed additional programs which enhance the benefits of MET/CAL Plus. The following applications may be obtained directly from On Time Support. Please see "http://www.ontimesupport.com" for full information, or contact On Time Support at: ON TIME SUPPORT Inc. Voice - 281.296.6066; Fax - 281.465.9478; E-mail - inquiries@ontimesupport.com; U.S. Mail - 25132 Oakhurst Drive, Suite 185 Spring, Texas 77386-1443 Process/Track Process/Track allows users to create, download, and upload procedures and data from Fluke 702, 743B, and 744 documenting calibrators, using the MET/CAL-Plus database. The software is fully automated. Process/Track will combine metrology and process calibrations into one system with complete forward and reverse traceability. (1) Data from every calibrator is stored in one database, providing complete traceability. (2) Calibration records are created automatically in your existing Fluke MET/BASE system expediting calibration record recording and eliminating data entry errors. (3) Calibration data is immediately accessible in the Fluke MET/BASE system after upload. (4) Existing calibration reports and test result certificates may be used with newly created calibration data. Remote Pipeline Remote Pipeline allows calibration lab supervisors/technicians to operate multiple workstations in remote locations where a continuous connection to a master server is difficult or impossible - and operate using the same database at every site. Remote Pipeline is a conduit that enables each remote system to share or replicate data with a master, consolidated Fluke MET/CAL database. Fluke MET/CAL customers can simultaneously operate many MET/CAL, 5500/CAL, MET/TRACK, Barcode Magician, and Process/Track workstations to calibrate instrumentation, perform process calibrations, or inventory instrument locations. ------------------------------------------------------------------------------- Section 6: Crystal Reports --------------------------------------------------- ------------------------------------------------------------------------------- MET/CAL V7.10 includes the following reports: ( 1) basic_inventory.rpt ( 2) basic_report_template.rpt ( 3) cal_due_by_asset_for_xxx_days.rpt ( 4) cal_due_by_asset_through_date.rpt ( 5) cal_due_by_dept_by_status_for_xxx_days.rpt ( 6) cal_due_by_location_by_status_thru_date.rpt ( 7) cal_due_by_tech_by_status_for_xxx_days.rpt ( 8) cal_due_by_tech_by_status_thru_date.rpt ( 9) cal_procedures_and_revs_for_eqpt.rpt (10) cal_summary_for_asset_number.rpt (11) cal_summary_for_work_order.rpt (12) field_customization.rpt (13) field_properties.rpt (14) license.rpt (15) master_inventory_for_asset_number.rpt (16) rt_certificate_of_cal_or_failed_cal.rpt (17) rt_report_of_cal_ver_7.rpt (18) rt_report_of_cal_ver_7_color_coded.rpt (19) rt_report_of_cal_ver_7_failures.rpt (20) rt_report_of_cal_with_exp_uncert.rpt (21) screen_customizing.rpt (22) trace.rpt The list above shows the report file names. To install reports use MET/TRACK. Login as "MT", and choose first "Install Reports", then "Configure Reports" in the top-level "Set-Up" menu. Additional reports are included on the MET/CAL Bonus Disk. A brief description of each report on the MET/CAL 7.10 CD (not the Bonus Disk) is provided below: basic_inventory.rpt A basic report that shows just inventory data. This report can be used as a template for other reports. basic_report_template.rpt A basic report that shows inventory data. Specifically designed to be used as a template. Has the joins set to left outer. cal_due_by_asset_for_xxx_days.rpt Prompts the operator for the number of days from today and shows assets with calibration due and overdue. cal_due_by_asset_through_date.rpt Prompts the operator for the date and shows assets with calibration due and overdue. cal_due_by_dept_by_status_for_xxx_days.rpt Prompts the operator for the number of days from today and groups the calibration due data by department and by status. cal_due_by_location_by_status_thru_date.rpt Prompts the operator for a date and groups the calibration due data by status and location. cal_due_by_tech_by_status_for_xxx_days.rpt Prompts the operator for number of days from today and groups the calibration due data by technician and status. cal_due_by_tech_by_status_thru_date.rpt Prompts the operator for a date and groups the calibration due data by status and technician. cal_procedures_and_revs_for_eqpt.rpt Lists all calibration procedures listed in field C2320 and shows the revisions. cal_summary_for_asset_number.rpt Prompts the operator for an asset number and gives the summary data for the asset. cal_summary_for_work_order.rpt Prompts the operator for a work order number and gives the summary data for the asset. field_customization.rpt Shows the current customization of the database fields. field_properties.rpt Shows the current customization of the properties for the database fields. license.rpt Lists all of the licenses assigned to the database and shows the version and serial numbers. master_inventory_for_asset_number.rpt Provides all inventory information for a specified asset number. rt_certificate_of_cal_or_failed_cal.rpt Generates a calibration certificate. Usually invoked from the Run Time application after a calibration has completed. Covers both PASS and FAIL calibrations. rt_report_of_cal_ver_7.rpt This is the basic report used to show full results generated by the MET/CAL Run Time application. This report uses result data from the new V7.00 Results Table. It is not a legacy report, so the "rslt_db.frm" file has no effect on the information presented by this report. rt_report_of_cal_ver_7_color_coded.rpt Similar to "report_of_calibration_ver_7.rpt", but shows failures with a red background and marginal passes with a yellow background. (The color coding is similar to MET/CAL's Test Results window.) rt_report_of_cal_ver_7_failures.rpt Similar to "report_of_calibration_ver_7.rpt", but shows only tests which failed. rt_report_of_cal_with_exp_uncert.rpt Similar to "report_of_calibration_ver_7.rpt" but shows expanded measurement uncertainty rather than test uncertainty ratio. screen_customizing.rpt This report shows the current customization of the screens. trace.rpt This report is used with the forward trace and reverse trace functions of the MET/TRACK. ------------------------------------------------------------------------------- Section 7: Minor Enhancements in V7.10 --------------------------------------- ------------------------------------------------------------------------------- ----> Allow MATH FSC Implicit Numeric-to-String Conversion Precision to be Settable Report Number: 26363 Application: MET/CAL The MATH FSC performs implicit numeric to string conversions whenever the expression evaluator encounters a situation in which a string value is expected but the value on the top of the run time stack is a numeric value. Prior to V7.10, these implicit conversions were done in such a way as to preserve at most 6 significant digits. In certain contexts conversions therefore entail a loss of precision. For example: MATH mem = 1.00000000001 MATH mem2 = put("x", mem) MATH mem1 = get("x") MATH s[2] = fmt(mem1, "%16.12f") DISP s2 = [s2] If you execute this procedure fragment you will observe that when register s[2] is displayed the value is shown as "1.000000000000". I.e., the '1' in the 11th digit to the right of the decimal point in "1.00000000001" has been lost. V7.10 supports a new, optional initialization file parameter "MathConvPrecision". Legal values for "MathConvPrecision" are 4 to 15. The default is 13. Set "MathConvPrecision" to 6 to cause the expression evaluator to behave as it did prior to V7.01C with respect to implicit numeric-to-string conversions. ----> Allow ACV (Peak) and DCV Danger Thresholds to be Settable Report Number: 26352 Application: MET/CAL V7.10 supports the following new optional initialization file parameters: Parameter Name Default Limits -------------- ------- ------ MaxSafeDCV 60.0 10.0 - 60.0 MaxSafePeakACV 42.4 10.0 - 42.4 These parameters affect the pop-up warning window generated by the MET/CAL Run Time and MET/CAL Editor Test Run applications when a potentially dangerous voltage is present. ----> Post Test Remark to Test Results Window Report Number: 26156 Application: MET/CAL In V7.10 operator messages entered using the Post Test "Remark" button appear in the Test Results window. ----> MATH FSC Function to Return Current Adjustment Threshold Value Report Number: 25685 Application: MET/CAL In V7.10 there's now a new MATH FSC function called "ADJTHR". It returns the adjustment threshold as a percentage. It is always the value from the main procedure, never from a subprocedure, regardless of whether the subprocedure is currently executing when "ADJTHR" is called. Refer to the Editor's on-line help for the MATH FSC for complete information. ----> Add ".txt" As Supported Extension in Editor's Open File Dialog Report Number: 25550 Application: Editor The filter list in the Editor Open Text File dialog has been expanded to include "*.txt". ----> Add support for Special Function 32.9 to M8902 FSC Report Number: 25434 Application: MET/CAL A customer at NCSL requested support for 8902A Special Function 32.9 (Tuned RF Level using Track-Mode Tuning) in the M8902 FSC. V7.10 implements this request. Refer to the Editor's on-line help for the 8902 and M8902 FSCs. Example: INSTRUMENT: Report Number #25434 1.001 ASK- N P F V 1.002 DISP Connect 11722A Sensor Module to 1000 MHz/ 0dBm 1.002 DISP signal source. 1.003 M8902 32.9SP H0 L0 1.004 8902 1000MH 0D FA N 1.005 MATH S[1] = "Track Mode Enabled" 1.006 EVAL -s S[1] : Is TRACK MODE button annunciator on? 2.001 M8902 * 2.002 8902 1000MH 0D FA N 2.003 MATH S[1] = "Track Mode Disabled" 2.004 EVAL -s S[1] : Is TRACK MODE button annunciator off? ----> Add Rows for DF=200 & DF=1000 to Students T Table Report Number: 25176 Application: MET/CAL In V7.01 and prior the Students T table used by MET/CAL to calculate the coverage factor given a degrees of freedom value and a confidence value has values for degrees of freedom from 1 to 100, and for infinity. Therefore, if the calculated degrees of freedom value is greater than 100, MET/CAL simply uses the values for 100, because it's not possible to linearly interpolate between 100 and infinity. The accuracy of the calculation would be improved if the table contained additional rows for degrees of freedom values of 200 and 1000. This would allow the software to interpolate linearly between 100 and 200, and between 200 and 1000. Only when the number of degrees of freedom exceeds 1000 would it then be necessary to simply use the values for DF = 1000 (i.e., no linear interpolation beyond 1000). In V7.10 Two new rows have been added to the internal Students T table: // DF, 1 S, 90%, 95%, 2 S, 99%, 3 S 1, 1.84, 6.31, 12.71, 13.97, 63.66, 235.8, 2, 1.32, 2.92, 4.30, 4.53, 9.92, 19.21, 3, 1.20, 2.35, 3.18, 3.31, 5.84, 9.22, 4, 1.14, 2.13, 2.78, 2.87, 4.60, 6.62, 5, 1.11, 2.02, 2.57, 2.65, 4.03, 5.51, 6, 1.09, 1.94, 2.45, 2.52, 3.71, 4.90, 7, 1.08, 1.89, 2.36, 2.43, 3.50, 4.53, 8, 1.07, 1.86, 2.31, 2.37, 3.36, 4.28, 9, 1.06, 1.83, 2.26, 2.32, 3.25, 4.09, 10, 1.05, 1.81, 2.23, 2.28, 3.17, 3.96, 11, 1.05, 1.80, 2.20, 2.25, 3.11, 3.85, 12, 1.04, 1.78, 2.18, 2.23, 3.05, 3.76, 13, 1.04, 1.77, 2.16, 2.21, 3.01, 3.69, 14, 1.04, 1.76, 2.14, 2.20, 2.98, 3.64, 15, 1.03, 1.75, 2.13, 2.18, 2.95, 3.59, 16, 1.03, 1.75, 2.12, 2.17, 2.92, 3.54, 17, 1.03, 1.74, 2.11, 2.16, 2.90, 3.51, 18, 1.03, 1.73, 2.10, 2.15, 2.88, 3.48, 19, 1.03, 1.73, 2.09, 2.14, 2.86, 3.45, 20, 1.03, 1.72, 2.09, 2.13, 2.85, 3.42, 25, 1.02, 1.71, 2.06, 2.11, 2.79, 3.33, 30, 1.02, 1.70, 2.04, 2.09, 2.75, 3.27, 35, 1.01, 1.70, 2.03, 2.07, 2.72, 3.23, 40, 1.01, 1.68, 2.02, 2.06, 2.70, 3.20, 45, 1.01, 1.68, 2.01, 2.06, 2.69, 3.18, 50, 1.01, 1.68, 2.01, 2.05, 2.68, 3.16, 100, 1.005, 1.660, 1.984, 2.025, 2.626, 3.077, 200, 1.00, 1.65, 1.97, 2.01, 2.60, 3.04, 1000, 1.00, 1.646, 1.96, 2.00, 2.58, 3.01, 0, 1.000, 1.645, 1.960, 2.000, 2.576, 3.000 ----> Empty Brace Construction Does Not Generate Results Table Line Report Number: 24855 Application: MET/CAL In MET/CAL V7.10 the processing of empty brace constructions has been changed to cause a Result Table line to be generated. In V7.00 through V7.01 SP1 empty brace constructions were ignored for purposes Results Table result generation. Legacy results processing, however, did generate, and continues to generate, an empty CalResults Table line when an empty brace construction is processed. For example, the procedure statement: HEAD {} now causes a Results Table row, with a blank Remark field, to be generated. This change appeared first in V7.01 SP2. All of the following FSCs process brace constructions, and so all are affected by this change: DISP DOS EVAL HEAS IEEE MEM2 MEMI MESS OPBR PORT RESET RSLT SET WAIT ----> Add Flag to Warn User When Saving Cal Record for Inactive or Deleted Instrument Report Number: 24445 Application: MET/TRACK In V7.10 a warning dialog has been added when adding or altering records for an inactive or deleted asset. The check is performed when the operator attempts to save the changes. ----> New MATH Functions to Add Values in Contiguous Registers Report Number: 24377 Application: MET/CAL V7.10 includes new MATH FSC functions to add values in a contiguous set of numeric registers. SUM - add values in a sequence of global numeric registers SUM_L - add values in a sequence of local numeric registers Example: Run the following procedure lines: MATH M[1] = 9.8 MATH M[2] = 3.5 MATH M[3] = 6.5 MATH M[4] = 8.4 MATH MEM = SUM(1, 4) The Value of MEM will be 28.2. ----> Revise TUR Calculation When UI Same As SA & Tolerance Asymmetrical Report Number: 24316 Application: MET/CAL In V7.01 and prior a zero TUR occurs in the Run Time TUR calculation when: (1) UUT Indicated and System Actual are the same, and (2) the upper test tolerance is zero. The Run Time TUR calculation has always been to choose the upper tolerance if the System Actual is greater than the UUT Indicated, and choose the lower tolerance if the System Actual is less than the UUT Indicated. When the System Actual and UUT Indicated happen to be the same, the upper tolerance is chosen, because there is no reason to prefer the upper or the lower in this case. In the case of an asymmetrical tolerance in which one side is zero, there is thus a 50% chance that the zero tolerance will be chosen when System Actual and UUT Indicated are the same. In V7.10 MET/CAL has now been changed to use the widest tolerance in this case, rather than to arbitrarily prefer the upper tolerance. There's also a new initialization file parameter which may be used, if desired, to cause MET/CAL to revert to the old algorithm: "UI_Eq_SA_LargestTol" is an optional initialization file parameter added to MET/CAL Dec 03, 2003. Legal values are { Yes, 1, No, 0 }. "Yes" and "1" are equivalent. "No" and "0" are equivalent. The default is "Yes" (i.e., "1"). The purpose of this parameter is to provide an optional flag which, if set, instructs MET/CAL to use the widest tolerance, whether lower or upper, when SA and UI happen to be exactly the same. Of course, for a symmetrical tolerance specification this parameter has no effect, because, in that case, the lower and upper tolerance values are the same. V7.01l or later is required in order to have a version which implements the "UI_Eq_SA_LargestTol" parameter. Prior to the existence of this parameter, the approach was to prefer the upper tolerance when System Actual and UUT Indicated were identical. Now, with the addition of the parameter "UI_Eq_SA_LargestTol", this approach is used only if "UI_Eq_SA_LargestTol = 0", and that is _not_ the default. ----> 180-Day, 99% Accuracy File for 5720A Report Number: 24207 Application: MET/CAL V7.10 includes a 180-day, 99% accuracy file for the Fluke 5720A. ----> 180-Day, 99% Accuracy File for 5700A Report Number: 24206 Application: MET/CAL V7.10 includes a 180-day, 99% accuracy file for the Fluke 5700A. ----> ELAPSED_TIME$ Cannot Be Directed to Inventory Field 2324 Report Number: 23986 Application: MET/CAL Prior to V7.10, the value of the Run Time variable ELAPSED_TIME$ cannot be directed to Inventory Table field 2324. 2324 is the "C-Time" field, typically used to store the elapsed time for a calibration event. The problem is that 2324 is a numeric-only field in the database, but the value of ELAPSED_TIME$ is not numeric-only. ELAPSED_TIME$ has a value formatted like this: [ Hours ] Minutes Examples are: 2 Hours 27 Minutes 35 Minutes 1 Minute One direct solution to this problem is to not use ELAPSED_TIME$ in the pass and/or file prompt files. Instead, the variable ELAPSED_TIME_MIN$ may be used. ELAPSED_TIME_MIN$ reports the time elapsed time in minutes, and it is numeric-only. Another possibility is to use ELAPSED_TIME_HR$. ELAPSED_TIME_HR$ reports the elapsed time in hours and tenths of hours. It is also numeric only. However, it is easy to fall into the trap of trying to direct ELAPSED_TIME$ to 2324, and the error is fatal, because it prevents the calibration results from being saved. It would be an improvement to the Run Time application if it detected the fact that an attempt was being made to direct an invalid value to 2324, and automatically replaced it with a valid value. The reason this problem was not noticed in V7.00 and V7.01 is that due to a separate problem, those versions did not take the value of ELAPSED_TIME$, or any other Run Time-generated value, as the value of field 2324. Correcting that problem uncovered the additional difficulty covered by this report. V7.10 resolves this issue. The Run Time now substitutes the value of ELAPSED_TIME_MIN$ for the value directed to Inventory Table field 2324 if it detects non-numeric characters in that value. This change appeared first in Run Time V7.01s. ----> Add Support for WM_MOUSEWHEEL Messages Report Number: 23461 Application: MET/CAL Most Windows mouse drivers send WM_VKSCROLL messages to an application when the user moves the scroll wheel. However, some drivers send WM_MOUSEWHEEL messages instead. Some drivers (like the Microsoft Intellimouse driver) allow the behavior of the driver to be configured in this respect. In V7.01 the MET/CAL Editor responded only to WM_VKSCROLL messages, not to WM_MOUSEWHEEL messages. In V7.10 the MET/CAL Editor has been updated to respond to WM_MOUSEWHEEL messages. V7.01q, or later, of the MET/CAL Editor is required. (In case unexpected side-effects arise on certain systems, adding "MouseWheel = NO" to the MET/CAL initialization file will disable processing of WM_MOUSEWHEEL messages.) ----> Add Support for Epsilon Factor in MATH FSC Relational Operators Report Number: 23459 Application: MET/CAL In V7.01 and prior, certain MATH FSC operations involving relational operators may produce unexpected results. The relational operators are "==", ">=", "<=", ">", "<", and "!=". The cause is that floating-point arithmetic on binary computers does not have the ability to exactly represent all numbers. In fact, the great majority of numbers cannot be exactly represented. Example: Because one or more of the numbers 0.1, 9.7, and 10.0 cannot be exactly represented, this leads to the situation in which: (9.7 + 0.1 + 0.1 + 0.1) is not equal to 10. Of course, in real mathematics the sum should be 10 exactly. However, in a binary computer what you will find is that: sum = 9.999999999999998 In V7.10 The MATH FSC has been updated so that the comparisons involved in using the relational operators ("==", > ">=", "<=", ">", "<", and "!=") now make use of an "epsilon factor". The default epsilon factor value is 1.0E-13. The value may be changed using the VSET or TSET FSCs. The parameter name is "MATH_EPSILON". The value must be between 1E-15 and 1E-5, except that, as a special case, setting the epsilon factor to zero disables the use of the epsilon factor (which causes MATH FSC execution to use exact double-precision floating-point comparisons). ----> Allow Disabling Peak Search Amplitude Measurement in Spectrum Analyzer FSCs Report Number: 23216 Application: MET/CAL In V7.01 all spectrum analyzer FSCs (8560, 8566, 8568, 8590) perform a 'peak search' when measuring either amplitude or frequency, i.e., detecting the highest peak signal displayed within the defined frequency domain. During signal generator verification, however, it is desirable to specify the particular frequency of interest, e.g., the measurement of spurious signals, at which the amplitude measurement is made. In order to accomplish this, MET/CAL should be able to disable its inherent peak search mentality on command, measuring (amplitude only) at a given frequency. Resolved in V7.10. MOD3 = "AF" (Amplitude at Frequency) is now allowed for the 8560, 8566, 8568, and 8590 FSCs. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Facilitate External Audio Level Measurement with 8902A Report Number: 22969 Application: MET/CAL In V7.10 the 8902 FSC has been updated to allow the 8902 FSC to measure level on external audio signals via the front panel "AUDIO INPUT" (not currently supported). Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Support 8902A External Input for Audio Distortion and Frequency Report Number: 22968 Application: MET/CAL In V7.10 the 8902 FSC has been enhanced to allow measuring distortion and frequency on external audio signals via the front panel "AUDIO INPUT", in addition to measuring the same parameters (via internal path) on demodulated audio signals (currently supported). Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Editor Requires Level 5 for Copy With Overwrite -- Should Be Same as Edit Level Report Number: 22809 Application: MET/CAL In V7.01 MET/CAL does not allow overwrite when copying a procedure unless the user is logged in at level 5. In V7.10 the design has been changed so that any user who has permission to edit procedures, as configured using the MET/TRACK administrative functions, will have permission to overwrite an existing procedure as part of a copy operation. ----> Allow Specifying Start and Stop Frequencies in M856x FSCs Report Number: 22534 Application: MET/CAL In V7.01 and prior the M8560, M8566, M8568, and M8590 FSCs do not allow the procedure writer to specify the start and stop frequencies as an alternative to specifying center frequency and span. Changed in V7.10. ----> Allow Specification of RF Attenuation in M856x FSCs Report Number: 22524 Application: MET/CAL In V7.01 the M8560, M8566, M8568, and M8590 FSCs do not allow the procedure writer to specify the RF attenuation level. Resolved in V7.10. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Add Ini File Parameters (4) to Disable Near- & Past-Due 9500 & 9100 Warnings Report Number: 22363 Application: MET/CAL As reported by MET/SUPPORT: There is a problem with the 9100 FSC that is not the fault of MET/CAL but rather that the 9100 (trying to be helpful to customers) generates a Warning message accompanied by an SRQ when it is approaching its Cal Due date. This 'warning period' can be set to 30, 14, and 7 days (You may need to check). This means that a known working procedure will generate an error during this 'warning period'. The 9100 displays the message onscreen and over the bus when it first enters DC Voltage and then AC Voltage. It is causing our customers some frustration, as the only solution at the moment is to change the system date of the 9100 to be before the warning period. Is there anything you can do to the FSC that would alleviate this issue? I can appreciate the amount of work that was done. This facility of the 9100 firmware is helpful when operating the calibrator in manual mode, but a pain when trying to handle it automatically. I guess the issue is that the _9100_near_cal_due_is_error and _9500_near_cal_due_is_error are NOT errors they are warnings. The problem is that when the customer tries to run the procedure MetCal generates the error and the procedure stops even though the calibrator is not out of calibration. The bit about the DC and AC volts is that the 9100 itself generates/displays the Cal due warning message when you first enter DC Voltage function and again when you enter AC Voltage. Resolved in V7.10. "9100_ShowNearCalDue", "9100_ShowPastCalDue", "9500_ShowNearCalDue", and "9500_ShowPastCalDue" are optional initialization file parameters which control whether or not the MET/CAL 9100 and 9500 drivers display instrument-generated "Near Cal Due" and "Past Cal Due" service requests. Legal values are { Yes, 1, No, 0 }. "Yes" and "1" are equivalent. "No" and "0" are equivalent. The default is for all parameters "No" (i.e., "0"). Prior to the addition of this parameter (Nov 12, 2003) the intended design was to not ignore the warning but rather to prompt the operator the first time it occurred in each procedure, presenting the option to continue or abort the procedure. Due to a bug (discovered Nov 12, 2003) the intended design was not correctly implemented. Instead, a step-terminating error was displayed every time the instrument generated a "Near Cal Due" or "Past Cal Due" service request. (It was only because the instruments themselves did not generate these errors except on first use of AC or DC functions after power-up, or on transitions from AC to DC, or vice versa, that the bug did not terminate every 9100 or 9500 procedure statement (when the near or past due cal conditions were present). After the above-mentioned bug has been corrected, if one or more of these parameters are set to 1, the corresponding warning will be displayed once per procedure (regardless of how many times the instrument generates the service request). ----> Provide 1-Year Accuracy File for 8508A Report Number: 22274 Application: MET/CAL V7.10 includes a 1-year accuracy file for the Fluke 8508A. ----> Add Modes to 9100 Accuracy File to Allow Correct Computation of Phase Accuracy Report Number: 22169 Application: MET/CAL A 9100 evaluation statement with phase in the Nominal field has frequency in the MOD1 field. The standard accuracy lookup and computation match Nominal and MOD1 to ranges in the accuracy file and compute the accuracy as x% of Nominal plus a floor. In the case of 9100 phase, the accuracy is based on voltage or current and frequency. V7.01 is limited because it does not include modes in the 9100 accuracy file which represent this relationship. If such modes were added it would then be possible to use the ACCV2 MATH FSC function to retrieve the phase accuracy. Resolved in V7.10. The following information has been added to the 9100 accuracy file: # The following mode strings are not directly # accessed by the 9100 FSC. Procedure writers # must use "ACCV2" math function to retrieve # values. Then the MATH FSC can be used to # calculate the actual phase accuracy (see # 7.19.10 Calculating Power Uncertainty in # the Model 9100 User's Handbook. # # Example: # # Compute phase accuracy dual voltage output of 5 V, # 30 mV, 60 Hz # # M9100 HX1 0.03V 5V SI MX # 9100 0deg 60H SI MN S 2W # MATH L[1] = ACCV2("Datron 9100", "Phase SI V", 5, 60) # MATH L[2]=ACCV2("Datron 9100", "Phase SI V AUX", 0.03, 60) # MATH M[1] = L[1] + L[2] # ACC 0deg M1U # MEMI Enter UUT reading in degrees. # MEMCX 0deg 2U Mode: Phase SI V # VOLTAGE (HI & LO) FREQUENCY Tol. Floor Res. # ----------------------- --------------- ----- ------ ----- 0.3 105 10 65 0 0.07 NA 0.3 105 65 1e3 NA NA NA 105 750 10 65 0 0.16 NA 105 750 65 1e3 NA NA NA Mode: Phase SI V AUX # VOLTAGE (I+ & I-) FREQUENCY Tol. Floor Res. # ----------------------- --------------- ----- ------ ----- 0.32e-3 7.5 10 65 0 0.07 NA 0.32e-3 7.5 65 1e3 NA NA NA Mode: Phase SI A # CURRENT (I+ & I-) FREQUENCY Tol. Floor Res. # ----------------------- --------------- ----- ------ ----- 0 20 10 65 0 0.08 NA 0 20 65 1e3 NA NA NA # Option 200 10- and 50-Turn Current Coils. Mode: Phase SI A T10 # CURRENT (10-Turn Coil) FREQUENCY Tol. Floor Res. # ----------------------- --------------- ----- ------ ----- 3.2 200 10 65 0 0.23 NA 3.2 200 65 1e3 NA NA NA Mode: Phase SI A T50 # CURRENT (50-Turn Coil) FREQUENCY Tol. Floor Res. # ----------------------- --------------- ----- ------ ----- 3.2 1000 10 65 0 0.23 NA 3.2 1000 65 1e3 NA NA NA The individual components of the phase accuracy can now be retrieved from the 9100 accuracy file using the MATH FSC ACCV2 function. The components can then be combined according to the example in section 7.19.10 Calculating Power Uncertainty in the Model 9100 User's Handbook. Example: MATH L[1] = ACCV2("Datron 9100", "Phase SI V", 100, 60) MATH S[32] = "Phase SI V AUX" MATH L[2] = ACCV2("Datron 9100", S[32], 0.15, 60) MATH M[1] = L[1] + L[2] M9100 150A 1mV/A 100V SI AX TARGET 9100 157deg 60H SI PR S 2W ACC 157deg M1U MEMI Enter UUT reading in degrees. MEMCX 157deg 2U ----> Add Duty Cycle Specs to 5520A Accuracy Files Report Number: 22080 Application: MET/CAL Basic 5520A Duty Cycle accuracy is +-(0.8% of period + 100 ns). However, in V7.01 and prior, MET/CAL computes system accuracy as a percent of the Nominal value + a floor. So a 5520 FSC statement where Nominal value is duty cycle cannot possibly compute the correct accuracy. In V7.10 a new mode has been added to the 5520A accuracy files to support the correct computation of duty cycle accuracy. This new mode can be accessed using the ACCV2 FSC. The value returned by ACCV2 can be used in a subsequent ACC FSC to establish the system accuracy for the test. ----> FSCs for SCPI Instruments Should Send SDC Only For Error SRQs Report Number: 22029 Application: MET/CAL When function "scpi_srq" is called it sends Selected Device Clear (SDC) to the device which asserted the SRQ, reguardless of whether the SRQ was expected or not. An example of an expected SRQ is "Message Available". Errors, on the other hand, are typically unexpected SRQs. Sending SDC typically puts the instrument in a power-up state, causing all information about the reading just taken to be lost. The following instrument drivers in MET/CAL call "scpi_srq" when the instrument generates an SRQ: Keithley 2000 Keithley 2001/2002 HP 34401A HP 34420A Agilent E4418B/E4419B Fluke PM 6680/PM 6681 Fluke PM 6685 To address this issue, in V7.10 the following parameters are now supported in the [Startup] section of the MET/CAL initialization file: K2000_SDC = Yes/1/No/0 K200x_SDC = Yes/1/No/0 HP34401_SDC = Yes/1/No/0 HP34420_SDC = Yes/1/No/0 HP441x_SDC = Yes/1/No/0 PM668x_SDC = Yes/1/No/0 If the parameter does not exist in the initialization file, the default is "No", i.e., DO NOT send SDC after processing an SRQ. ----> Allow 'Arrive Date' (I4224) in the Future Report Number: 21877 Application: MET/TRACK In V7.01 SP1 and prior MET/TRACK does not allow a date in the future to be assigned as an "Arrive Date" for an instrument. The "Arrive Date" in this context is field 4224 in the Inventory Table. Some organizations manage work flow in a manner which makes it convenient to assign a future arrive date in some cases. MET/TRACK V6 allowed such a future date specification for the "Arrive Date". V7.01 SP2 includes an updated version of MET/TRACK which allows the "Arrive Date" for an instrument to be a future date. ----> MATH Function to Round a Number to a Specified Number of Signficant Digits Report Number: 21788 Application: MET/CAL In some cases it is convenient to directly round a floating-point value to a specified number of significant digits. The FMT function can be used for this purpose, but it's less obvious than a more specialized function would be. V7.10 includes a new function, "FRND". Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Instrument Configuration Should Not list GPIB-USB-A Report Number: 21763 Application: MET/CAL GPIB-USB-B is the preferred National Instruments USB card. The Config Editor has been updated in V7.10 to list the GPIB-USB-B, rather than the GPIB-USB-A. ----> 34401 FSC Help File Does Not State That the 34401A Language Must Be Set to SCPI Report Number: 21756 Application: MET/CAL In V7.01 the following text has been added near the top of the 34401 FSC help file: The 34401A remote language must be set to SCPI when the 34401A is to be controlled using the 34401 FSC. To set or verify that the 34401A language is set to SCPI, perform the following steps via the 34401A front panel: 1. Press "Shift" then MENU On/Off. 2. Press ">" arrow key until "E: I/O MENU" is displayed. 3. Press "v" arrow key to enter I/O MENU. 4. Press ">" arrow key until "5: LANGUAGE" is displayed. 5. Press "v" arrow key to enter LANGUAGE. 6. Press ">" arrow key until "SCPI" is displayed. ----> Allow selection of AC coupling for 2001 ACV <= 200 Hz Report Number: 21643 Application: MET/CAL In MET/CAL version 7.01 and earlier, Keithley 2001 AC Voltage Measurement coupling is selected as follows: <= 200 Hz AC+DC Coupling > 200 Hz AC Coupling In V7.10 the 2001 FSC MOD2 "O" (Override) is now legal for AC voltage in addition to resistance and conductance modes. In AC voltage mode when the frequency is <= 200 Hz and MOD2 is "O", the default selection of AC+DC coupling is overrode and AC coupling is selected. Above 200 Hz MOD2 "O" has no effect. ----> Allow Selection of AC Coupling in Keithley 2002 FSC for ACV <= 200 Hz Report Number: 21621 Application: MET/CAL In V7.01 SP2 the 2002 FSC (for the Keithley 2002) has been improved to allow the selection of AC coupling for ACV <= 200 Hz. In MET/CAL version 7.01 SP1 and earlier, Keithley 2001/2002 AC Voltage Measurement coupling is selected as follows: <= 200 Hz AC+DC Coupling > 200 Hz AC Coupling In V7.10 (actual V7.01 SP2) 2002 FSC MOD2 "O" (Override) is now legal for AC voltage in addition to resistance and conductance modes. In AC voltage mode when the frequency is <= 200 Hz and MOD2 is "O", the default selection of AC+DC coupling is overridden and AC coupling is selected. Above 200 Hz MOD2 "O" has no effect. ----> "Add Customer" Screen Should Show Customer Number Report Number: 21611 Application: MET/TRACK In V7.01 there's a problem when choosing a customer under the Add Asset tab. Users wish to have control over what information is shown. There may be several customers with the same name and same city. It would be helpful to add the "Customer Number" column to the list, to eliminate the confusion between similar customers. V7.10 has be enhanced to resolve this issue. ----> Add MATH FSC Function to Determine if Last Evaluation Passed Report Number: 21150 Application: MET/CAL The request is for the opposite of the existing "fail" function. This is a minor enhancement, but it will improve procedure readability in some cases. In V7.10 Function "pass" has been added. However, it should be used with the awareness that it is identical to "not fail". This means that: (a) If no evaluations have been performed, "pass" returns 1 (TRUE). (b) If the last evaluation failed, but the setup for the following evaluation has already been done, "pass" will return 1 (TRUE) when called at that point in the procedure. ----> IEEE FSC Help File Does Not Describe Scope of [TERM ...] Special Construction Report Number: 21085 Application: MET/CAL In V7.01 and prior the IEEE FSC help file fails to state that the input terminator ([TERM...]) special construction affects all subsequent IEEE statements, with or without an alias, for both GPIB0 and GPIB1. In V7.10 text has been added to the IEEE FSC help file to clarify the scope of the TERM construction. ----> Lower 8508A ACV Measurement Bound From 0.002 V to 0 V Report Number: 21083 Application: MET/CAL In V7.10 the 8508 FSC has been changed to lower the ACV bound from 0.002 V to 0 V. This allows measuring 800 microvolts peak-to-peak (316 microvolts rms) during 9500B CAL ADJ. In V7.01 the following error occurs: E9716: FSC 8508: NOMINAL AC voltage out of range (0.002 V to 0.1999999 V) ----> Test Run ASK Flags Window Should be Wider Report Number: 20476 Application: MET/CAL In V7.10 the Editor Test Run ASK Flags Window is slightly wider. This makes it easier to click on the title bar in order to move the window. ----> Math Functions to Count Occurrences of a Substring in a String Report Number: 20072 Application: MET/CAL In V7.01 MATH functions "FIND" and "FINDI" have been modified to return the count of occurrences of a specified substring in a specified string when the third argument (the occurrence number) is set to zero. For example: MATH MEM = FIND("a,b,c,d,e", ",", 0) In this example the value of MEM will be set to 4, because there are 4 commas in "a,b,c,d,e". Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> Add Support for Query Operation to the SCPI and IEEE2 FSCs Report Number: 19740 Application: MET/CAL The first implementation of the SCPI and IEEE2 FSCs did not support queries. V7.10 includes versions of the SCPI and IEEE2 FSCs which support queries. Refer to the Editor's on-line help, or the on-line Reference Manual ("ReferenceManualV71.pdf") for complete information. ----> IEEE FSC [SPL ] Special Construction Should Return in Demo Mode Report Number: 19550 Application: MET/CAL In V7.01 and prior, in demo mode, the IEEE FSC [SPL ] always returns zero. Therefore procedures using the serial poll special construction cannot be successfully executed in demo mode. It should be noted that the IEEE FSC [SRQ ,] does return the mask value in demo mode. In V7.10 the [SPL ] construction has been modified so that in Demo Mode it always returns the specified . (In earlier versions it returns zero in Demo Mode.) ----> UUT Indicated in Test Results Window for Go-NoGo Tests Report Number: 18295 Application: MET/CAL In V7.01 and prior when a Go-NoGo test is executed, the UUT Indicated column in the Test Results window shows "OPER-EVAL". In V7.10 a new, optional initialization file parameter, "GoNoGo", has been added to allow the "OPER-EVAL" string to be overidden. Maximum string length is 13 characters. If a longer string is specified, it's ignored, and the default ("OPER-EVAL") is used. This change affects both the Test Results window and the Post Test window. (This change may affect "legacy results" as well.) ----> One-Year Accuracy File for the HP 6063B Report Number: 14483 Application: MET/CAL Upon investigation, it turned out that the specifications in the existing accuracy file for the HP 6063B ("hp63.acc") were actually one-year specs, not 90-day as stated in the file header. The interval has been changed to 365 days. ----> One-Year Accuracy File for the HP 6060B Report Number: 14482 Application: MET/CAL Upon investigation, it turned out that the specifications in the existing accuracy file for the HP 6060B ("hp60.acc") were actually one-year specs, not 90-day as stated in the file header. The interval has been changed to 365 days. ------------------------------------------------------------------------------- Section 8: Documentation ----------------------------------------------------- ------------------------------------------------------------------------------- Printed manuals have been updated for MET/CAL V7.10. The V7.10 distribution contains the following documentation files: GettingStartedV71.pdf This is the MET/CAL and 5500/CAL Getting Started Guide, Version 7.1. Available in printed form as well as on-line. Guardbanding.pdf Describes MET/CAL V7.10's support for guardbanding. ImportToolV7.pdf Describes the MET/CAL V7 Import Tool. InstallV71.pdf This is the V7.1 Install Manual. Available in printed form as well as on-line. PIItoMCTranslator.pdf This is the User's Guide for the Portocal II to MET/CAL results translator. Available on-line only. QuickReferenceV7.pdf This is the one-page hot keys sheet which shows the hot keys used by MET/TRACK and the MET/CAL Editor. Available in printed form as well as on-line. ReferenceManualV71.pdf This is the MET/CAL V7.1 Reference Manual. Includes all new FSCs. Available on-line only. ResultsTable7.pdf This document lists the MET/CAL V7 Result quantities, and shows the new database Results Table column names. Has not been updated for V7.10. Available on-line only. RHT.pdf This document explains how to use the Fluke 5000A RH/T Precision Humidity and Temperature Data Logger with MET/CAL V6.11 and later (including MET/CAL V7.00, V7.01, and V7.10). Available on-line only. UsersManualV71.pdf This is the MET/CAL Users Manual (Version 7.1). Available in printed form as well as on-line. The following "readme" files are provided. These are available on-line only. "readme700.txt" (this file) is the primary "readme" file for V7.00. "readme6.pdf", "readme601.pdf", "readme610.pdf", "readme611.txt", and "readme611A.txt" are supplied for upgrade customers who wish to the understand the full sequence of software updates. readme6.pdf This is the readme file for the V6.00 release. readme601.pdf This is the readme file for the V6.01 release. readme610.pdf This is the readme file for the V6.10 release. readme611.txt This is the readme file for the V6.11 release. readme611A.txt This is the readme file for the V6.11A release. readme700.txt This is the readme file for the V7.00 release. readme701.txt This is the readme file for the V7.01 release. readme710.txt This is the readme file for the V7.10 release. [ This is the file you are currently reading! ] ------------------------------------------------------------------------------- Section 9: Accuracy and Help Files ------------------------------------------- ------------------------------------------------------------------------------- V7.10 includes many updated and new accuracy files. All updates included in V7.01 SP1 and V7.01 SP2 are included in V7.10. In many cases the updates provide corrected specifications but do not affect the ability of the MET/CAL Editor to compile instrument FSC statements in the procedure editor. However, in a number of cases, including the 9500B and other FSCs, the accuracy file updates were made in parallel with updates to the built-in instrument driver used by MET/CAL, and the updated driver must have the corresponding updated accuracy file to operate correctly when the MET/CAL Editor compiles a procedure statement, or when the Run Time calculates a Test Uncertainty Ratio. Therefore, please install the updated versions of all accuracy files included in V7.10. If you have customized accuracy files on your system please backup your accuracy files before installing V7.10. On-line help files for all new FSCs are included in V7.10. In addition, many help files for FSCs which existed in V7.01 have been updated. ------------------------------------------------------------------------------- Section 10: V7.10 Problem Reports -------------------------------------------- ------------------------------------------------------------------------------- This section contains problem reports which describe all corrections made from V7.01 SP2 to V7.10. ----> "Run Time" Reports Do Not Appear in MET/CAL Run Time As Available to Add Report Number: 27046 Application: MET/TRACK When a report is added and configured to be a run time report (a check in RUN), it does not cause the report to appear in MET/CAL Run Time as available to be added. This problem is present in MET/TRACK build #361. A design change in MET/TRACK caused the library "metgendb.dll" to operate incorrectly. Resolved in V7.10. "metgendb.dll" has now been updated. ----> Repeatedly Running Same Report from Run Time Causes Slowdown Report Number: 27011 Application: Run Time In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, running consecutive calibrations from Run Time and previewing the same report, after every calibration the report generation gets slower and slower. For example, the first time a report is previewed it may take about 4 seconds. After consecutively previewing the same report 20 times, the preview time will have increased to about 40 seconds. (The time varies. It depends on the PC and depends on the particular report.) It may be, although this is unclear, that this slowdown leads to more serious problems on some networked systems, due to network timeouts. Resolved in V7.10. ----> V7.01 SP2 MET/TRACK Maintenance Table Problem Report Number: 26793 Application: MET/TRACK In MET/TRACK V7.01 SP2 there is a problem with the Maintenance Table which occurs with some customer databases. With certain databases the problem occurs when the user takes an Inventory Table record and sets the Recall Interval to '0' and the Interval type to 'N', then saves the record. Next, add (or Edit) a Maintenance Table record and the Interval Type will copy the Recall Interval from the Inventory Table even though no customization is set to do that. It only seems to occur with databases that have been upgraded from earlier versions, such as V4. Resolved in V7.10. ----> Cannot Print Landscape on Browse Screens (Using MET/TRACK) Report Number: 26785 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, there is a printing problem. Portrait mode is used even when landscape mode is selected. Resolved in V7.10. ----> Attempting to Slew 9500 LS from 909.10 ps to 909.09 ps Corrupts Slew Screen Report Number: 26694 Application: MET/CAL In MET/CAL V7.01, V7.01 SP1 and V7.01 SP2 a slew screen problem appears when slewing the 9500 scope calibrator from 909.10 ps to 909.09 ps. Using the Editor in "Demo mode" causes the Test Results window to display "9500 statement terminated by floating point exception". In real mode the procedure works. Resolved in V7.10. ----> Executing (Particular) M681/6681 Statements Locks Up App in Demo Mode Report Number: 26351 Application: MET/CAL In MET/CAL V7.01, V7.01 SP1 and V7.01 SP2 executing the following procedure in demo mode locks up the application (Editor Test Run or Run Time): INSTRUMENT: Report Number #26351 1.001 ASK- V 1.002 M681 COM 320nT 0.2V 0.4V DC ++ X1 1.003 6681 200nT 0.6Vpp TI S Resolved in V7.10. ----> Import Tool Allows Only Two Characters in Field 4229 Report Number: 26237 Application: Import In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the external Import Tool ("imp.exe") allows only two characters in field 4229. If the imported data are set up for 364 days the following error is generated: Field 4229 data exceeds maximum allowed length (2 characters). One or more fields exceed data length limits. 06523,Fluke,8600A,Digital Multimeter,2086221,,AGOURA,Out Of Service,D,364,MFG ^^^^^ However, this is a valid entry and it should be possible to successfully import the data. Resolved in V7.10. ----> Temperature and Humidity in Installed "variable.dat" File Should Be Blank Report Number: 26194 Application: Install Resolved in V7.10. ----> Users In Segregates Other Than MT Cannot Add or Change Calresults Report Number: 26176 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 users in segregates other than "MT" cannot add or change data in the Cal Results table. The test was done using MET/TRACK build #333. However, the problem was reported by a customer in Italy who does not have build #333. The problem probably exists in V7.01, if not earlier versions. To demonstrate the problem: 1. Create a new segregate (e.g., TEST). 2. Create a new level 5 user and assign them to this segregate. 3. Login as the new user. 4. Create an asset and a cal record. 5. After saving the cal record attempt to enter information into cal results. You will get an error: The following internal error has occured -2147217911 [Sybase][ODBC Driver][Adaptive Server Anywhere]Syntax error or access violation. Permission denied you do not have permission to select from "calresults" Resolved in V7.10. ----> Invalid Information Can Be Saved In Field 4217 (Accessory Asset) Report Number: 26171 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 MET/TRACK does not prevent invalid information from being saved in field 4217. Field 4217 is a special purpose field for use with sub-assets to a main asset. If you enter invalid information in this field and attempt to save the record you will get a message: Asset Number XXXXX does not exist. If, at this point, you click on the "X" button in the top right corner of the form you will get the message: Save Changes (yes - no - cancel). If you choose "Yes" the invalid information will be saved to field 4217. Resolved in V7.10. ----> Advanced Global Changes Logic Reversed Report Number: 26142 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 certain operations specified using "advanced global changes" are reversed. To demonstrate the problem: (1) Login to MET/TRACK as the administrator. (2) Select "Database/Global Changes". (3) Click on "Advanced". (4) Select a field (e.g., 4203) as the field to change. (5) When selecting the Operater "Begins with" and a secondary field (e.g., 4202) and an existing value (e.g., FLU) the value put into SQL command display is: "I4203 LIKE '%FLU"' -- the wild card is in front of the value indicating "Ends with" (6) "Ends with" works the same way (backward) in that it puts the data in as 'I4203 like FLU%' which would be correct for "begins with". Resolved in V7.10. ----> ACI Measurement Example in 5790 Help File is Incorrect Report Number: 26132 Application: Documentation In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 there's a mistake in the 5790 help file. The following example from the 5790 help file demonstrating ACI measurement is incorrect: 1.001 ASK- R N W 1.002 ACMS F 1.003 HEAD AC CURRENT: {22mA Range} 1.004 DISP Connect the 5700A Output terminals to the 5790A 1.004 DISP Input 1 using Pomona cable #1368-A-18, A40-20mA 1.004 DISP current shunt, & 792A-7004 current shunt adapter. 1.005 MEMI Enter the AC-DC difference of the shunt at 100Hz. 1.006 MATH M[20] = MEM 1.007 5790 20.00000mA I1 E N 2W 1.008 IEEE OUT 20mA;OPER 1.009 5790 20.00000mA I1 E N 2W 1.010 MATH M[1] = MEM + M[20] 1.011 5700 OUT -20mA;OPER 1.012 5790 -20.00000mA I1 E N 2W 1.013 MATH M[3] = (M[1] - (MEM + M[20])) / 2 1.014 IEEE OUT 20mA,100Hz;OPER 1.015 5790 20.00000mA 100H I1 E N 2W 1.016 MATH MEM1=200E-6-(200E-6*(1-((MEM+M[20])/M[1]))) 1.017 IEEE STBY 1.018 MEMC 20.00000mA 140P% 0.0004U 100H Replace it, using the following suggestion: 1.001 ASK- R N W 1.002 ACMS F 1.003 HEAD AC CURRENT: {22 mA Range} 1.004 DISP Connect the 5700A Output terminals to the 5790A 1.004 DISP INPUT 1 using a Pomona cable #1368-A-18, A40-20mA 1.004 DISP current shunt, & a 792A-7004 curr. shunt adapter. # Enter A40-20 mA AC-DC difference (in percent). 1.005 MEMI Enter A40-20mA shunt AC-DC diff. at 100 Hz (%): # L[32] contains A40-20 mA AC-DC difference, converted to # proper decimal. 1.006 MATH L[32] = MEM / 100 # Apply +DC. 1.007 IEEE OUT 20mA;OPER # Take +DC reading with 5790A. 1.008 5790 20.00000mA I1 E N 2W # Store +DC reading in L[1]. 1.009 MATH L[1] = MEM # Apply -DC. 1.010 IEEE OUT -20mA;OPER # Take -DC reading with 5790A. 1.011 5790 -20.00000mA I1 E N 2W # Compute mean DC from ¿DC readings. 1.012 MATH L[2] = (L[1] + ABS(MEM)) / 2 # Apply AC. 1.013 IEEE OUT 20mA,100Hz;OPER # Take AC reading with 5790A. 1.014 5790 20.00000mA 100H I1 E N 2W # Set source to standby. 1.015 IEEE STBY # Apply A40-20 mA shunt AC-DC difference to measured AC value. 1.016 MATH L[3] = MEM - (MEM * L[32]) # Compute AC value based on nominal & difference between # DC and corrected AC. 1.017 MATH MEM = (20E-3-(20E-3*(1-(L[3]/L[2]))))/1E-3 1.018 MEMC 20.00000mA 140P% 0.0004U 100H The help file has been updated for the V7.10 release. ----> Adding a User-Configured Serial Device Defaults to COM0 Report Number: 26097 Application: Config Editor In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 when adding a user-configured instrument, if "Remote Interface:" is set to "Serial", no "Serial Port:" radio button is selected. At this point if "OK" is selected, the following error is displayed: COM0 does not exist or islocked by another device. Do you wish to continue? If "Yes" is selected a subsequent error is displayed: E2948: Illegal serial address for SCF update. Resolved in V7.10. ----> MET/TRACK Validation Problem Report Number: 26062 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if field 4210 is set up with "req list" validation and an asset is then saved asset without first selecting a value from the list, the current user name will populate field 4210. If the user then saves and selects that field, it is populated alternately with the user name. When there is Required Validation it should supersedes the default values. Resolved in V7.10. ----> .XLS, BMP, or .CSV Link in I4260 Causes Error in MET/CAL Run Time Report Number: 26002 Application: METGENDB.DLL In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 when a spread sheet or bitmap link is created in field I4260 (Inventory Notes) MET/CAL Run Time generates the error: "(132gid)SQL Error::Data truncated", followed by: "E5452: Can't determine if asset "XXXX" exists. Query error." This is a difficult one to reproduce. It appears that, for example, if Excel is installed on the computer, it tries to translate and display the spreadsheet (at least it does in MET/TRACK). Without Excel it will dispay just the ICON for the file. It was causing this problem with .CSV files until I removed the association with Excel - then it works fine in Run Time. The error has been duplicated as follows: (1) Login to MET/TRACK as a level 5 user. (2) Edit the Inventory form for an existing asset. (Make sure that field 4260 is shown on the Inventory form. If it's not, login as the MET/TRACK administrator and add it.) (3) Open the Windows Explorer, and find an Excel spreadsheet (.xls file.) (4) Drag the spreadsheet from the Explorer to the I4260 multiline edit control. (5) Save the changes. (6) Close MET/TRACK. (7) Start the Run Time. (8) Attempt to run any procedure. You will see the "data truncated" error, followed by E5452, as stated in the initial report. Additional note: It does not appear that this problem is strictly connected to whether or not there's a Windows association with the particular file extension on the PC being used. This problem can be duplicated using ".bmp" and ".xls" files, but not using ".doc" or ".jpg" files. However, in the case of ".jpg" files there's a separate problem (logged in a different report) -- namely, MET/TRACK locks up when the record is saved. Partially resolved in V7.10. The exchange size limit has been increased to 15 MB. ----> Full Results Grid Out Of Sync with Radio Buttons Report Number: 25901 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the full results grid viewer may get out of sync with the radio buttons. When the problem occurs the grid "view" is not in sync with the radio buttons. When the form is first loaded the radio buttons correctly reflect the previous view, but the grid is not refreshed to reflect it. The grid always seems to open in the Full-Data view. Clicking the view buttons correctly allows the selection of the desired view. The problem appears to be specific to switching between "Classic" and "Full Data". Resolved in V7.10. ----> Quick Reports Print / Print Preview Font Size Incorrect Report Number: 25897 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the Quick Reports "Print Preview" font size is incorrect. Resolved in V7.10. ----> Cannot Delete Cal Record for an Asset Used as a Standard Report Number: 25825 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if a customer accidently enters a cal record for a standard and then tries to delete the cal record, an error message is generated: "This asset as been used as a standard and cannot be deleted". Resolved in V7.10. The solution is to allow a level 4 or level 5 operator to delete a cal record for a standard, but only if the cal record to be deleted was not the cal record which was "in effect" at the time the standard was used to calibrate a UUT. ----> Edit Inventory Screen Not Repainted Correctly After Closing Validation Editor Report Number: 25778 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 MET/TRACK does not repaint the "Edit Inventory..." correctly after closing the validation editor when a validation list was displayed at the time the validation editor was invoked. Resolved in V7.10. ----> Unable to Create Calibration Record with Italian Standard Regional Setting Report Number: 25755 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when using the regional setting "Italian (Standard)" MET/TRACK disconnects from the database when an attempt is made to create a calibration record. To duplicate the problem: 1. Configure the regional setting of the test PC by choosing "Italian (Standard)" in the "Regional Settings" tab of the Windows "Regional Settings Properties" window. 2. Start MET/TRACK, logging in as a normal user (with permission to add a calibration record). 3. Type F3. 4. When the "New Calibration Record..." window appears enter the asset number of an existing asset. 5. When the "New Calibration Record..." appears (same name, but different window from step (4)) enter values for all required fields. 6. Click the "Save Record" button. 7. The error message: Connection to database has been lost. ... MET/TRACK must terminate... will now be generated. This test was done on a WinNT system, using MET/TRACK build #333. However, the same problem was present in V7.01. Resolved in V7.10. ----> Unique Tag Fields Cause Errors When Used in Search Functions Report Number: 25746 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, if unique tag fields are added to the search form, then, when they are used in a search, an error is generated by MET/TRACK. To demonstrate the problem: 1. Login to MET/TRACK as the administrator ("MT"). 2. Choose "Lay-out". 3. Choose "Search Engine Screen". 4. Click on the "Restore a field..." button. 5. Scroll to the bottom of the list in the "Field Restore" window. 6. Restore one or more of the fields: CCTAG CMTAG IMTAG KKTAG LLTAG LMTAG RMTAG RRTAG 7. Close MET/TRACK. 8. Login to MET/TRACK as a normal user. 9. Type Ctrl+F. 10. Click on the dropdown arrow associated with the edit control of one of the fields restored in step 6. 11. Select at item from the dropdown list. 12. Click on the "Begin Search..." button. 13. The following Sybase error will now be displayed: ... Syntax error or access violation: Syntax error near ')' on line 1 ... FUNCTION/SUB:frmDataBrowser, NewSearchRefresh In V7.10 the unique tag fields are no longer searchable. ----> MET/TRACK Error After Key Following Failed Asset Search Report Number: 25738 Application: MET/TRACK In V7.01, V7.01 SP1 and V7.01 SP2 MET/TRACK incorrectly generates an error message when the user types the key after a failed search. This report is based on MET/TRACK build #332. To demonstrate the problem: 1. Login to MET/TRACK at level 5. 2. Choose "Search". 3. Choose "Search Engine". 4. Enter any non-existent asset number. 5. Click on the binoculars to start the search. 6. The "Instrument Browser..." window will indicate "no record". 7. Press 8. You will now see the error: 91 Object variable or With block variable not set Resolved in V7.10. ----> Arrive Date & Status Are Cleared When a Calibration Fails Report Number: 25719 Application: METGENDB.DLL In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when an asset fails calibration in Run Time the arrive date and status are blanked, on the inventory screen, even though the database setup is set to blank only when the calibration passes. This continues to cause problems because failed assets may seem to "disappear" from our reports. The problem has been duplicated with MET/TRACK builds #329 and #333. I've been able to duplicate this problem with MET/TRACK build #329. Build #329 is the V7.01 SP2 build. This problem was casued by a trigger reading a Boolean as 1 or 0, versus "Y" or "N". Resolved in V7.10. ----> Cal Table Interval and Interval Units Defaults Ignored When Fields Suppressed Report Number: 25704 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when Calibration Table fields 2302 (Interval) and 2331 (Interval Units) are suppressed the default values for those fields should be used when a new Calibration Table record is added. However, if the default for 2302 is set to "12" and the default for 2331 is set to "M", then when a new calibration record is added the values which appear in the saved record are "0" for 2302 and "D" for 2331. This problem appeared while using MET/TRACK build #332 to verify that bug #20377 was resolved. It is not known if this problem is present in V7.01. It has been concluded that when fields 2302 and 2331 are suppressed, then the values are taken from field 4229 (for 2302 the interval) and field 4228 (for 2331 the interval units). These two fields are in the inventory table. Resolved in V7.10. Now MET/TRACK always copies the Interval and Interval Unit from Inventory to Calibration when these two fields are suppressed. I4229 is copied to C2302 and I4228 is copied to C2331. ----> Time Truncated in MET/TRACK Location Dialog Report Number: 25686 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if the user enters the maximum number of characters in field L2801 (User Name), then selects Edit, then Location, and then picks an asset, the time will be shifted over so far in the dialog that the displayed time is chopped off. Note: field L2801 can accept up to 20 characters. Resolved in V7.10. The list view has been expanded to show the date and time first, then the user name. ----> "Check" Button in Forward Trace Dialog Incorrectly Disabled Report Number: 25684 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if a user: (1) Opens Forward Trace, (2) selects an asset, (3) selects Reverse Trace, (4) selects Forward Trace again, then the "Check" button will be disabled. If the user then goes back to Reverse Trace, that button will be ok, but the Forward Trace button will never again be enabled. Easy work-around: Double-click on the calibration date. This has the same effect as the "Check" button. Resolved in V7.10. ----> On MET/TRACK Date Entry Forms Does Not Follow Tab Order Report Number: 25681 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when entering data, e.g., on the Calibration Form, typing repeatedly follows the designated tab order, but typing skips some fields. For example, in some cases on the Calibration Form will skip over "Temp" (C2311) and "Found-Left" (C2308). The design is that and should be the same, except on engineering notes-type fields. Engineering notes-type fields are, in effect, multi-line edit controls, and typing should cause an advance to the next line. Resolved in V7.10. ----> Quick Reports Goes Into Endless Loop When No Date Found Report Number: 25666 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if no data are found as a result of a Quick Reports query MET/TRACK enters an endless loop and the user must use "End Task" to close the application. A statement saying something like "No Data Found" would be a better solution. Resolved in V7.10. ----> Field 4203 Data Length Controls Val Editor Lengths for Field 2326 Report Number: 25656 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 field 4203 data length incorrectly controls the Validation Editor lengths for field 2326. Other fields are affected as well. To demonstrate the problem: 1. Set field 2326 to its maximum length (44). 2. Create a validation file for this field with entries of various lengths between 23 and 29 characters (inclusive). 3. Set the entry length of field 4203 to 22. 4. Login as a normal user, open a cal form for editing, place the cursor in field 2326, and press F7. Attempt to save the validaton. The error "Entry #X 'XXXXXXXXXXXXXXX': Items in the validation list exceed the maximum allowable length in customization" will appear. 5. Login as MT and change the entry length of 4203 to its maxumum value (30). 6. Repeat step 4. 7. Observe that the error message is no longer displayed. Resolved in V7.10. ----> MET/TRACK Allows Invalid Entries in Validated Fields Report Number: 25655 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 invalid entries are allowed in validated fields. To demonstrate the problem: Select a validated field and type the first character of a validation entry. All of the entry will be highlighted except the first character. Press delete, then save the entry. It will accept the partial entry. This problem does not depend on the level of the user. As long as you have permission to edit the field this problem can appear. Resolved in V7.10. ----> Level 1 and 2 Users Can Modify Restricted Fields Report Number: 25654 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if a field has validation and is configured to prevent level 1 and 2 users from adding or modifying the field data, they can still enter or change (and save) data by using validation entries by typing in the first character of a val entry. A level 1 or 2 user cannot simply enter a value, and cannot cause the dropdown list of valid values to be displayed, but can type a valid prefix of a validation value and then using the built in auto-completion successfully save the value. Resolved in V7.10. ----> DB Update Should Detect Mismatch Between Customization and Merge Report Number: 25642 Application: DB Update In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the current version of the file "patch1.sql" includes code to cross-check the customization against "sys.systable" for a few fields looking for merge information. However, the cross-checking should be expanded to include all fields for which merge is allowed. If the condition exists where customization is marked "Y" for merge, but no table exists, one cannot turn this off using the normal customization editor, nor can one create a merge table for this field. ISQL must be used and this may cause problems with cloning. Note: Field 4206 should be set to "X" for merge on all fforms. This field should never have a merge table. Resolved in V7.10. ----> Modifying or Adding a Maintenance/Location Record in Databrowser Causes an Error Report Number: 25640 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 adding or deleting a maintenance or location record from the browser form may cause an error. Resolved in V7.10. ----> Unable to Clone Asset Report Number: 25638 Application: MET/TRACK In MET/TRACK V7.01 SP2 when an attempt to clonse an asset is made an SQL error may be generated. The error is: The following internal error has occured: 438 Object doesn't support this property or method. ... FUNCTION/SUB: frmDataBrowswer, Clone, Click The problem is not as general as suggested by the statement above. It is not the case that every attempt to clone an asset fails. The problem arises when a field is marked for linked validation, but there are no actual linkage data provided. The situation probably arose as a side-effect of upgrading from an earlier version of MET/TRACK where the linkage data were external. (In the current version all linkage data are internal -- i.e., inside the database.) Resolved in V7.10. ----> Delete Location Fails if L2801 is Numeric Report Number: 25600 Application: MET/TRACK In MET/TRACK V7.01 SP2 if L2801 is numeric, the Delete Location Record function fails. L2801 is a string field, but it is used as a date field currently. However, with older databases the field was used for other purposes. If the value happened to be non-numeric, the conversion to a data would fail. Resolved in V7.10. ----> MET/TRACK Stops Responding When Internal Import with Incorrect Asset Number Assempted Report Number: 25432 Application: MET/TRACK In MET/TRACK V7.01 SP1 and SP2 there is a problem when importing records which specify an incorrect asset number (Inventory Table field 4201). Resolved in V7.10. ----> Incorrectly Repeated Error When Editing Asset in Segregate Without Permission Report Number: 25352 Application: MET/TRACK In MET/TRACK V7.01 SP2, and earlier versions, attempting to edit an asset in a segregate for which edit permission is not available leads to the error: "The asset is in a segregate you do not have permission to use." This error message is valid. The problem, however, is that when the error message window is closed, it immediately reappears, and then continues to reappear everytime it's closed, forcing the user to use the Windows Task Manager to close MET/TRACK. The problem has been resolved in V7.10. ----> Forcecase Fails Except for Engineering Notes Fields Report Number: 25323 Application: MET/TRACK In MET/TRACK V7.01 SP2 the "forcecase" initialization file parameter has no effect. The problem occurs with all text fields other than the engineering notes (RTF) fields. (The "forcecase" parameter does not apply to numeric and date fields.) This problem was not present in V7.01 SP1 and ealier versions -- it was introduced in SP2. V7.10 corrects the problem. ----> For Validated Fields MET/TRACK Does Not Properly Restrict Entered Values Report Number: 25322 Application: MET/TRACK In MET/TRACK V7.01 SP2 in a required, validated field, e.g., 4202, you can enter any information. The problem applies to other fields as well. It also applies to linked validation. For example, link field 4202 to 4203, 4204 and then enter data for each field. Next, login as a non-MT user and add or edit an inventory record. Note that you can enter anything into field 4202 and save the record. The underlying problem is that validation does not work. MET/TRACK fails to restrict directly entered values to the values on the validation list. Problems with linked validation are a side-effect of this basic problem. Resolved in V7.10. ----> PM 668x driver reports "-113, Header error" on 166 MHz PC Report Number: 25321 Application: MET/CAL In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, in some cases, the PM 668x driver reports "-113,Header error" when the 6680 FSC specifies a time interval measurement. V7.10 corrects the problem by inserting a 50 ms or greater delay between the IEEE-488 write that sets up the SRQ mask and the IEEE-488 write that sends the measurement setup commmand string. Since the problem was not universal it was decided to add a MET/CAL initialization file parameter to control whether the delay is inserted and to specify the duration of the delay. If a customer reports a "-113,Header error" when attempting to use the 6680, 6681, or 6685 FSCs, they should be instructed to add the following parameter to the [Startup] section of the MET/CAL initialization file ("metcal.ini") with a value of 50 or greater. Parameter Name: PM668x_SRQ_delay Parameter Value: 0 to 5000 ms Example: PM668x_SRQ_delay = 50 The MET/CAL 7.10 default is no parameter/no delay. ----> MET/CAL Can't Read RHT.INI When Numbers Use Comma as Decimal Symbol Report Number: 25171 Application: MET/CAL Run Time In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when using LogWare III on a workstation configured so that the decimal symbol is a comma, temperature and humidity values written by LogWare III to the RHT data file are written using the comma as the decimal symbol. However, MET/CAL fails to correctly read these values from the RHT data file. The problem is caused by the fact that MET/CAL expects the decimal symbol to be a period ('.'). Here's an example of an RHT data file which cannot be read by MET/CAL: [A43240] temperature=26,01 C humidity=40,15 RH timestamp=1087487175 In V7.10 MET/CAL has been modified so that it reads and converts humidity and temperature values in the RHT initialization file when those values use a comma as the decimal symbol. (MET/CAL does not currently display those values in the Run Time prompt screen using the configured decimal symbol. A separate change would be required for that.) ----> Slew Window Message Length Limitation Report Number: 25154 Application: MET/CAL In V7.01 SP2, and earlier versions, the slew window used by the MET/CAL Editor and Run Time applications does not support sufficiently long text strings to properly support localization of messages in languages other than English. The immediate problem was a German translation of the message: Adjust stimulus for a UUT horizontal reading of markers/division. In German this message became: Stimulus für eine horizontale Prülings Anzeige von: Marke/Teilstrich nachregeln. which was too long for the slew window code. In V7.10 longer messages are allowed. (The messages may not be fully displayed in the window, but, if too long, will simply be truncated. An internal error which aborts the procedure step will no longer occur.) ----> User-Entered Value for Field C2324 Containing Comma Not Accepted Report Number: 25153 Application: MET/CAL Run Time In V7.01 SP2, using the MET/CAL Run Time application, when a prompt appears after procedure execution to prompt for a value to be written to C2324 ("C-Time"), the user has the option of overriding the automatically generated value and directly specifying the elapsed time. There's a problem in V7.01 SP2 in that if the user-entered value contains a comma (as the decimal separator) MET/CAL incorrectly concludes that the value is non-numeric and automatically substitutes the value of ELAPSED_TIME_MIN$ for the user-entered value. This problem was inadvertently introduced as a side-effect of a change which appeared first in V7.01 SP2, and is therefore not present in versions prior to V7.01 SP2. (To be more precise, this problem is present in versions V7.01s through V7.01v.) V7.10 corrects this problem. ----> 9500B/1100 Radio Button in 9500 Configuration Dialog Selects 9500B/3200 Report Number: 25080 Application: MET/CAL In V7.01 SP2, and prior versions, using the MET/CAL Configuration Editor (F12 in Editor or Run Time) to configure a 9500B with a 1.1 GHz option fails because when the chosen configuration is saved the software incorrectly changes the selected option to the 3.2 GHz option. V7.10 corrects this problem. ----> Error Attempting to Create User Table Report Number: 25058 Application: MET/TRACK In MET/TRACK V7.01 SP1 and SP2 a problem occurs in some cases when attempting to create a user table. If you enter the table name, a field name, and a field type, then choose Add Table, an error message indicating that the table requires two fields appear. After you respond to the error message, an additional error message is generated. Resolved in V7.10. ----> Pick/Val List Limits Number of Entries Report Number: 25032 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the validation list is limited to the number of entries that can be displayed during the editing of the list. The limitation appears to be 65535 characters. This is also a limitation on the pull down list. To demonstrate: (1) Login to MET/TRACK as the administrator ("MT"). (2) Set field I4247 to a pick list. (3) Edit the pick list. (4) Add entries until the limit is reached. (ISQL could be used to prepopulate the data). (5) Notice that only 65535 characters can be entered. Resolved in V7.10. ----> Type-Ahead Does Not Work With Field C2355 in V7.01 SP2 Report Number: 25030 Application: MET/TRACK In MET/TRACK V7.01 SP2 type-ahead does not work correctly with field C2355 when editing a calibration record. Resolved in V7.10. ----> Time Not Shown When Deleting Location Record Report Number: 25029 Application: MET/TRACK In MET/TRACK versions V7.01 through V7.01 SP2 Location Table fields L2809 (date), User Name (L2801) and L2810 (time) are not shown when deleting a location record. The missing fields are important to customers who use MET/TRACK in the tool crib to sign equipment in and out. V7.10 corrects the problem. The window now shows Date (L2809), User Name (L2801) and Time (L2810). ----> MET/TRACK Type-Ahead Fails for Inventory Table Fields I4225 and I4245 Report Number: 25028 Application: MET/TRACK In MET/TRACK V7.01 SP2 type-ahead does not work correctly with fields I4225 and I4245 when editing an inventory record. Resolved in V7.10. ----> Enter Key Fails in MET/TRACK RTF Fields Report Number: 25027 Application: MET/TRACK In MET/TRACK V7.01 SP2 when entering data in the Inventory Notes field (I4260), if the key is used the cursor will not "linefeed down" to the next line, but instead the cursor ends up in the Calibration Notes field (I4244). A work-around is to use Ctrl+Enter instead of Enter. Resolved in V7.10. Now the key inserts a line break in the Notes field in all the tables that have notes fields. Use the key to move from a notes field to the next field. ----> MET/TRACK Quick Reports "Report Title" Font Size Incorrect Report Number: 25024 Application: MET/TRACK Resolved in V7.10. ----> No Drill Down for Validated Fields in Inventory Form Report Number: 25023 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 there is a problem with the "drilldown" on validated fields in the Inventory Form. Resolved in V7.10. ----> MET/TRACK Browser Screen Buttons Misaligned Report Number: 25022 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 buttons are misaligned on some browse forms: Calibration Tab - buttons 3 & 4 are overlapped Location Tab - buttons 2 & 3 have unwanted extra space Maintenance Tab - buttons 2 & 3 have unwanted extra space Cosmetic problem. Resolved in V7.10. ----> Selecting "break" During 856x Reset Causes Incorrect Driver Operation Report Number: 25017 Application: MET/CAL In V7.01 SP2 there's a problem in the driver (FSC) for the HP 8560A/B/E, HP 8566B, HP 8568B and HP 8590 E/L spectrum analyzers. If the operator presses "Break" during the operation of resetting the spectrum analyzer, incorrect looping occurs. Resolved in V7.10. ----> MET/CAL User Manual Refers to Nonexistent Report Report Number: 25016 Application: Documentation In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 the MET/CAL User's Manual refers to a non-existent report named "TBLDEFS.RPT". Resolved in V7.10. The manual has been updated. ----> MET/TRACK Clone Functions Allows Cloning Only One New Asset Report Number: 25013 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if an asset is selected and the clone function started, a new asset is created. After saving the asset, if the clone function is called again, it appears that the second asset is saved, but it is not. This problem applies to any additional assets that are created as well. Resolved in V7.10. (First resolved in MET/TRACK build #329.) ----> Linked Fields Remain Linked After Dropping Validation from Root Field Report Number: 25012 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 linked fields may remain linked after validation is dropped from the root field. To demonstrate the problem: (1) Set up linked validation with 2801 as the root and 2902, 2803 and 2804 as linked fields. (2) When validation is removed from 2801, 2803 and 2804 still appear as linked fields. The "me2_customization" table still shows them as linked and the "customiz" table still shows the root and all links. Data are removed from the "vallink" and "vallinkdata" tables. Resolved in V7.10. ----> 8560 FSC Causes Unexpected SRQ at Onset of Procedure Execution Report Number: 25011 Application: MET/CAL In MET/CAL V7.01 SPW there's a problem with the 8560 FSC. When a procedure contains an 8560 FSC, the following error message is generated once at the onset of procedure execution: The device at address xx on IEEE-488 port 0 has asserted SRQ. Do you wish to continue? In SP2 "take sweep" and "wait for end-of-sweep SRQ" operations were added to the 856x "clear" function. This was done to prevent procedure execution from proceeding while an 856x Spectrum Analyzer was performing the "Instrument Preset" invoked by the clear function. For some reason the older 8560A spectrum analyzer holds the SRQ line high after the end-of-sweep serial poll. In V7.10 an additional serial poll has been added to the clear function to alleviate the problem. ----> Update Fluke 5820A Leveled Sine Frequency Floor Spec Report Number: 25010 Application: MET/CAL In V7.10 the MET/CAL 5820 accuracy file has been updated per a spec change initiated by the engineering group responsible for the Fluke 5820A. The leveled sine frequency specs have been changed from: .33 ppm + 0.0 Hz to: .33 ppm + 0.4 Hz However, the MET/CAL accuracy file states the spec as: .33 ppm + 0.5 Hz Therefore, to bring the MET/CAL accuracy file into line with the planned change to the published specs the leveled sine floor spec has been changed from 0.5 Hz to 0.4 Hz. This change will very slightly improve the reference accuracy used by MET/CAL for TUR and measurement uncertainty calculations involving the 5820A when the NOMINAL value is a frequency value and the waveform type is leveled sine (MOD2 is "LS"). To verify that the defect has been fixed, perform the following steps: 1. Open the Editor. 2. Configure a 5820A with the 2.4 GHz option. 3. Type Ctrl+N or select File->New. 4. Cut and paste the following procedure statements in to the MDI window: INSTRUMENT: Report ID #25010 5820 50kH 0.33P% 4e-4U 5.00mVpp LS S6 L 5820 999kH 0.33P% 4e-4U 5.5Vpp LS S6 L 5820 1.00MH 0.33P% 4e-7U 5.5Vpp LS S6 L 5820 599.99MH 0.33P% 4e-7U 5.5Vpp LS S6 L 5820 600.0MH 0.33P% 4e-7U 5.5Vpp LS S6 L 5820 2100.0MH 0.33P% 4e-7U 3.5Vpp LS S6 L 5. Press F9 repeatedly and verify that each 5820 statement generates a 1:1 TUR warning. ----> Displaying Raw Measurement Data When There Are None Generates Error Report Number: 25006 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when looking at data in the "Results" table, there is a "Measurement" button on the form. When a user chooses that button, there is never any data in the "Measurements" form. If the users selects a column title an error message is generated. The raw measurement data are present only when measurement uncertainty is enabled. The reason it appears that there are never any data values in the form is that the procedure which was run to generate the result data did not enable the measurement uncertainty calculation. Clicking on the "name" column causes the following error message to appear: The following internal error has occured: 6149 Invalid bookmark. ... Function/SUB: frmFullResults, gridRaw, HeadClick Corrected in MET/TRACK build #254. Resolved in V7.10. ----> Quick Reports Fails When There's More Than One Unused Date Field Report Number: 24992 Application: MET/TRACK In MET/TRACK V7.01 SP1 and SP2, if a user has more then one unused date field (4250 ... 4253) in Quick Reports, an error is displayed and there is no preview. Resolved in V7.10. ----> Field 2335 Has Non-Configurable Permissions, But Supports Only Levels 4 & 5 Report Number: 24979 Application: MET/TRACK In V7.01 SP2, and previous versions, MET/TRACK does not allow permissions to be configured for field 2335. However, the field is "filled in" only when the user is logged in at level 4 or level 5. Since the permissions are non-configurable, the field should be updated regardless of the level of the logged-in user. V7.10 corrects this problem. ----> Interval Units / Interval Conflict Generates Error on Save, But Saves Anyway Report Number: 24971 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, using MET/TRACK, if "Interval Units" is defaulted to "N" and "Interval" is defaulted to a number other than "0", a message is displayed on "Save" indicating that Interval Type "N" must have an Interval of zero. However, choosing "OK" causes the save operation to complete normally. The pop-up message has been removed in V7.10. ----> Second Save of New History Record Fails Report Number: 24968 Application: MET/TRACK In MET/TRACK V7.01 SP1 and V7.01 SP2 when an initial attempt to save a history record fails (for a valid reason like leaving a required field blank), then, even after the problem has been corrected, the record cannot be saved. Resolved in V7.10. ----> MET/TRACK Validation Value Lengths Not Restricted to Field Entry Length Report Number: 24883 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 MET/TRACK does not limit the length of a validation value to the maximum entry length for the field to which the validation value applies. This causes problems for the MET/CAL Run Time application because when the Run Time queries the database to obtain the validation values for a required Inventory Table field the interface DLL ("metgendb.dll") generates an error code (as it should) indicating that the value has been truncated. Resolved in V7.10. ----> Error Encountered when Adding Maintenance Record Report Number: 24963 Application: MET/TRACK In MET/TRACK V7.01 SP2 an error may occurs when adding a maintenance record. The error was caused by an incorrectly constructed SQL query. Resolved in V7.10. ----> Error Generated When Field 2384 On Cal Form But Level 3 User Lacks Access Report Number: 23947 Application: MET/TRACK In MET/TRACK V7.01 SP1 and V7.01 SP2 an error is generated for a level 3 user if field 2384 is shown on the cal form, but the user does not have have access. When an attempt is made to create a new cal record, the following error message appears: The folling internal error has occured 438 Object doesn't support this property or method. ... FUNCTION/SUB: Table,Set_Customiz_Properties If level 3 users are given access to this field, the error does not occur. Resetting tabs, etc., has no effect. Resolved in V7.10. ----> Inventory Data Not Saved When Customer Selected Report Number: 24939 Application: MET/TRACK In MET/TRACK V7.01 SP2 problems occur in some cases when saving an Inventory Table record. To demonstrate the problem: 1) Add --> Inventory Record (or F2) 2) Select Customer from list 3) Fill in inventory information (manufacturer, model, etc.) 4) Click on Save The form closes, appearing to save properly, but, in fact, the record has not been saved. Editing an inventory record exhibits the same problem. A work-around it to save the inventory item without assigning a customer, then go to the search screen find the asset, then add a customer record for the asset. Resolved in V7.10. ----> MET/TRACK Truncates Displayed MET/CAL Procedure Names Report Number: 24921 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, when displaying the MET/CAL procedure directory to allow associating a MET/CAL procedure name with an inventory item MET/TRACK truncates procedure names longer than about 42 characters, making it difficult to choose the correct procedure. Resolved in V7.10. ----> Cloning An Asset More Than Twice Closes Inventory Window Report Number: 24854 Application: MET/TRACK In V7.01 SP2, and earlier versions, using the clone feature in the inventory window more than once fails. The sequence of steps which fails is as follows: (1) Create a new asset. (2) Clone the asset. (3) Attempt to clone another asset. When the second clone attempt is made the inventory window closes, and the clone operation is not completed. V7.10 corrects this problem. ----> Paste into Calibration Results Using Ctrl+V Produces Double Copy Report Number: 24720 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 there's a problem when using the keyboard to paste information into the Cal Results table. To demonstrate the problem: (1) Choose a calibration record to be edited. (2) Click on the "Enter Calibration Results" icon. (3) Attempt to copy and paste data using Ctrl+C and Ctrl+V. (4) Observe that the input into the results is doubled. For example, the copied line: Hello There becomes: Hello ThereHello There The paste operation works correctly if you click on the right mouse button and select "Paste". Resolved in V7.10. ----> Internal Import Missing Listings for Maintenance Report Number: 24705 Application: MET/TRACK In MET/TRACK V7.01 SP1 and V7.01 SP2 internal import is missing all references to the maintenance form and fields. Resolved in V7.10. ----> Clone from Edit/Inventory Produces Bad Record Report Number: 24095 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if an asset is cloned, using the Edit/Inventory form, from an asset that has a customer assigned, the customer Ktag is copied to the cloned record. When saving the cloned inventory record the error "subscript out of range" occurs. If, at that time, you add a cal record, then go back and edit the cal record you will get a series of errors and have to shut down MET/TRACK with the task manager. As a work-around, clone works from the browse form. Resolved in V7.10. ----> Linked Validation Fails On Upgrade from V5 to V7.01 (or V7.01 SP1) Report Number: 24018 Application: DB Update The upgrade from V5 to V7.01 fails in some cases. Version 5.XX allowed 'Comment' as a string entry in the "vallink" table. Version 7.XX does not allow this. This results in an error being generated when the linked validation list is edited. The following script has been added to the patch files to correct the problem: UPDATE "mt"."vallink" SET link2 = NULL where link2 = 'Comment'; UPDATE "mt"."vallink" SET link3 = NULL where link3 = 'Comment'; UPDATE "mt"."vallink" SET link4 = NULL where link4 = 'Comment'; UPDATE "mt"."vallink" SET link5 = NULL where link5 = 'Comment'; UPDATE "mt"."vallink" SET link6 = NULL where link6 = 'Comment'; UPDATE "mt"."vallink" SET link7 = NULL where link7 = 'Comment'; UPDATE "mt"."vallink" SET link8 = NULL where link8 = 'Comment'; UPDATE "mt"."vallink" SET link9 = NULL where link9 = 'Comment'; UPDATE "mt"."vallink" SET link10 = NULL where link10 = 'Comment'; Resolved in V7.10. Run DB Update to apply the patch. ----> Printer Selection Changes Windows Default Printer Report Number: 23608 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the printer selection changes the Windows Default Printer. If a user selects a different printer it initially prints to it OK. If the user selects a different printer the second time, it still goes to the first printer selected. Selecting it a 3rd time solves the problem. If the user then selects the first printer again, it initially comes out on the second printer and so on. This was related to Crystal Reports V8. It's resolved with the MET/CAL V7.1 release because Crystal Reports V10 is now being used. ----> Merge Data Not Displayed on Browse Forms Report Number: 23384 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if a merge table is created on a field (e.g., 3240 - repair action) the field title is highlighted on the core, browse and edit forms. The merge data can only be displayed on the core and edit forms. The browse form will give you a message: "No merge data exists for "Repair action"" - or whatever the title of the field is. Normal merge data are displayed on the core and edit forms. Resolved in V7.10. ----> Linked Validation Accepts Only 8 Columns (Should Be 10) Report Number: 23227 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if a linked validation is set up on a field (for example, 4203) with the desire to add 9 other fields, then when attempting to add the 9th field this error appears: "The following internal error has occured -2147217865[Sybase][ODBC][Adaptive Server Anywhere]Column not found: Column 'link11' not found. This warning - ... FUNCTION/SUB: Module1,Get_Column The problem is occurs on field with linked validation that has more than 8 linked fields. Resolved in V7.10. (Resolved in MET/TRACK build #329.) ----> Calibration Record Not Saved When It Should Be Report Number: 23048 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 there is a problem which occurs in some cases when saving a calibration record. The following description explains the problem: When a user enters in a new calibration record and forgets to click on the due date window to get it to auto fill, and then clicks on the "X" button in the upper right of the window, an error message appears message asking if the record is to be saved. Next, clicking on the "Yes" button yields a warning indicating that a due date is required. Clicking "OK" causes the due date to be auto-filled. Up to this point this all is "normal" and as one would expect. If the user then clicks on the "X" button again, the window closes, giving the user the impression the record has been saved, when in fact it has not been saved. If the user takes the proper action and clicks on the floppy disk/save button, thinking the record is being saved, it still does not save. As you know the floppy disk turns green when a record has been saved. In the scenario mentioned above the button "depresses" but does not turn green and once again the record has not been saved. Resolved in V7.10. ----> Report "Ver_7_Certificates" View Fails in Some Cases Report Number: 23023 Application: Reports In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if the user name (C2307) in the Calibration Table does not have a corresponding entry in the Userlist Table, then the View does not return any values. This can only happen if the results were imported with no validation on the user names. Resolved in V7.10. An update to "patch1.sql" was required. Run DB Update to apply the patch. ----> METGENDB.DLL Reports Default Values Too Long For Fields C2393 and C2394. Report Number: 23021 Application: METGENDB.DLL At the request of a customer, the Run Time application was recently updated to allow fields C2386 to C2396 to be included in the Run Time pre- and/or post-run prompt screens. However, in MET/CAL V7.01, V7.01 SP1 and V7.01 SP2 it is not possible to prompt for C2393 or C2394 after the Run Time update, because the interface library ("metgendb.dll") reports default values for these fields greater than the maximum field length. Resolved in V7.10. An update to "patch1.sql" was required. Run DB Update to apply the patch. ----> Inappropriate Dropdown Lists Under Field Properties Default Report Number: 23020 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 incorrect dropdown lists appear under field properties. To demonstrate the problem: Consider Calibration Table field 2393: (1) Start MET/TRACK, login as the administrator. (2) Choose "Lay-out" : "Entry Screens" : "Calibration Screen". (3) If field 2393 is not shown on the Calibration Screen, add it. (4) Double-click on 2393 to bring up the Field Properties window. (5) Click the down arrow in the Default Value control. (6) Observe the choices: Current Date User's Login Name ... Desktop Name (7) None of these values are appropriate for C2393 ("Use Dominance Test"). Note: 2393 is not the only field which exhibits this problem. Resolved in V7.10. (The list is now empty.) ----> Update From V6 to V7 May Cause Errors Due to Missing Ktags Report Number: 23007 Application: DB Update In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 there is a problem with the DB Update application in some cases when upgrading from V6 to V7. MET/TRACK V6 allowed a customer to be deleted even when the "customer" was in use. This left "orphaned" Ktags in the inventory, and then generated errors when "patch1.sql" was applied as part of the V7 upgrade. Resolved in V7.10. After upgrading to V7.10 run DB Update to apply the SQL patches. ----> MET/TRACK Fails When Date Separator and Time Separator are Same Char Report Number: 23005 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 an error occurs when the date separator and the time separator (as specified in the Windows regional settings) are the same character. To demonstrate the problem: (1) Set the regional setting to Italian (Standard). (2) Set the date separator to '.' (dot). (3) Start MET/TRACK. The following error message will be generated: ... 13 Type Mismatch ... ... Check_Expired_Password (4) Choose "OK" to close the error message window. (5) Choose "Add" : "Calibration Record". (6) Enter the asset number of an existing asset. The following error message will be generated: ... 380 Invalid property value ... ... Table, Set_Customiz_Properties (7) Choose "OK" to close the error message window. (8) Fill in required calibration data as needed. (9) Attempt to save the data. The following error message will be generated: Connection to database has been lost. ... MET/TRACK must terminate... The application crashes at this point. (MET/TRACK build #301 was used to execute the sequence of steps given above.) This problem has been resolved in V7.10. ----> SQL Error When 2nd Procedure is Run (Due to Copies) Report Number: 22992 Application: METGENDB.DLL In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 an SQL error occurs in some cases at the end of the Run Time application when results are being saved. The error occurs when the database is configured so that Calibration Table field 2361 gets its value by copying from Maintenance Table field 3217. Neither field is required or validated. When the first procedure is executed all is normal. When a second procedure is run, immediately after the operator enters an asset number the following error is generated: (232e)SQL error::invalid cursor state::2361:: It's possible to then continue and complete the procedure execution, but the copy from 3217 to 2361 does not take place. MET/CAL V7.10 includes a new version of "metgendb.dll" which corrects this problem. ----> MET/TRACK Fails When Editing an Asset with More Than 500 Maintenance Records Report Number: 22910 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 an error occurs when editing an asset with more then 500 maintenance records. The error message is: Error number 9: subscript out of range Resolved in V7.10. ----> Standard Windows Resizing Functionality for Listed MET/TRACK Windows Report Number: 22867 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 various MET/TRACK windows fail to correctly implement the standard Microsoft Windows resizing functionality. There should be minimize and maximize buttons on the window title just to the left of the 'X' in the upper-right corner of the window. The maximize graphic should change to a graphic indicating "restore to normal" when the window is maximized. The problem is present in at least the following MET/TRACK windows: 1. Edit --> Inventory Screen 2. ADD --> Inventory Screen 3. Edit --> Calibration Screen 4. ADD --> Calibration Screen 5. ADD --> Location Screen 6. EDIT --> Location Screen 7. ADD --> Maintance Screen 8. EDIT --> Maintance Screen 9. ADD --> Customer Screen 10. EDIT --> Customer Screen 11. EDIT --> Assign Asset to Customer 12. Search --> Search Engine Screen 13. Reports --> Run Installed Report Screen 14. Reports --> Run Any Report Screen Resolved in V7.10 for the Add/Edit records screens (for Inventory, Calibration, Location, Maintanence and Customer), Search Engin screen, Run Install Report screen and Run Any Report Screen. ----> Unabled to Save Validation Data for Field C2341 Report Number: 22442 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if you change the field C2341 property to "Req Val" or "Picklist", you will be able to refresh, edit and save the validation data as MT user. If you try to "Refresh and Save" or "Edit and Save" the validation data as a normal user, it is not possible to save the validation data. The error message generated is: Items in the validation list exceed the maximum allowable length in customization. Resolved in V7.10. ----> Leading Spaces Stripped When Data Pasted Into Legacy Results Report Number: 22362 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 when data are pasted into the Cal Results table leading spaces, if any, are stripped off. Resolved in V7.10. ----> Add/Edit Allowd with Incorrect User Level Report Number: 22340 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 there is a problem with MET/TRACK's permission checks. It is possible to set up the configuration so that a level 3 user should be able to add and/or update certain fields, but MET/TRACK nevertheless disallows the operation. Resolved in V7.10. ----> Error Pasting Result Data into MET/TRACK Cal Results Table Form Report Number: 22312 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 if the user edits or adds data in the Cal Results Table (using a right mouse click to paste) and then does not type or click on any other character, the pasted data are not saved. It is necessar to click another character before the results are saved. An extra LF is added to the end of the results when the data are saved. Resolved in V7.10. (This may actually have been resolved in V7.01 SP2.) ----> Combine Cal Function Doesn't Prompt for Deleting of Old Records Report Number: 21999 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2 the Combine Calibration function should prompt to delete the old calibrations after they are combined successfully. This worked in version 7.00 SP4, but does not work in V7.01. Resolved in V7.10. ----> Dropdown List Not Present on Pre/Post Run Prompt if Pick List on Field Report Number: 21981 Application: METGENDB.DLL In MET/CAL V7.00, V7.01, V7.01 SP1, and V7.01 SP2 if a field in a pre- or post-run prompt is set up as a pick list, the dropdown arrow is missing and it will accept typed in data. If the same field is set up as a simple validation the dropdown arrow is present and it works as expected. The work-arounds are to simply enter the desired value, without the benefit of the dropdown list, or use "simple" validation, which forces all legal values to be in the list. Resolved in V7.10. ----> Client Install Error on Win XP from NT 4 server Report Number: 21875 Application: Install In the MET/CAL V7.01 Install Program an error occurs in some cases at the end of the splash screen of the installation for the Client Install. The problem occurs on a WinXP client with an WinNT 4.0 server network. Resolved in V7.10. The V7.10 Install Program is written using a new version of InstallShield and this problem is no longer present. ----> C2307 Uppercase Versus Lowercase Stored in Database Report Number: 21654 Application: METGENDB.DLL In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 there's a problem with handling uppercase vs lowercase letters in the user's name in Calibration Table field C2307. The login name, rather than the full user name, are written to the field. Resolved in V7.10. ----> Upgrade Install Deletes Tools Menu Customization Report Number: 21636 Application: Install In MET/CAL V7.01 the Install Program deletes the user-customizable Tools Menu items when an upgrade is performed. Resolved in V7.10. The Tools Menu is now left exactly as it was when an upgrade is done. Note that in some cases this means there will be obsolete items in the user's Tools Menu. For example, there may be references to the 16-bit versions of MET/CAL and MET/TRACK. In such cases it is the user's responsibility to update the Tools Menu manually by editing the relevant section of the MET/CAL initialization file. ----> Documentation on Backing Up Databases is Incorrect Report Number: 21596 Application: Documentation In the Version 7 Users Manual on Page 2-6 the following line is incorrect: Target: C:\sqlany80\win32\dbbackup.exe -x -y "-cuid=mt; pwd=mt; dbf=c:\metdata\mtrack.db" c:\backup The backup will fail if the user follows the stated instructions. The text should be: "C:\Sybase\SQL Anywhere 8\win32\dbbackup.exe" -x -y "-cuid=mt; pwd=mt; dbf=c:\metdata\mtrack.db" c:\backup Resolved in V7.10. ----> Required Date Format Not Specified, Can Lose Calibration Data When Saving Report Number: 21588 Application: METGENDB.DLL In MET/CAL V7.01, V7.01 SP1, and V7.01 SP2 when a customer makes a date field in the cal form "required" and does not set a default date, the cal technician is required to type in a date when adding an asset in the Run Time application. The expected date format is yyyy/mm/dd. If this format is not followed exactly, the user receives an error message and cannot save the calibration. At the end of a very complex cal procedure this is a serious problem. This only affects customers who are adding assets into the database at Run Time. Resolved in V7.10. An error message is now displayed when the user enters an illegal date format. The error occurs when the user tries to close the dialog by clicking "OK". The user then has the opportunity to correct the date entry. ----> MET/TRACK Error When Reliability Greater Than 99 Report Number: 21445 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 a problem occurs when the reliability value exceeds 99. Resolved in V7.10. ----> Clone Does Not Function After Saving a Calibration Record Report Number: 21378 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 there's a problem with the clone function after saving a calibration record. To demonstrate the problem: 1. Add a new asset. 2. Add a calibration record for the asset added in step 1. 3. Close the calibration record. 4. The inventory record remains displayed. Select the Clone button. Right now it does nothing. It should go into the "Clone mode". Resolved in V7.10. ----> After Save, Field Properties Don't Follow Customization Report Number: 21347 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 a problem occurs if the user sets up a description for 'require on insert', but not for 'require on update'. The Description field will still have the required color. If the same asset is opened through the Edit Menu selection the color and use are correct. Resolved in V7.10. ----> Apostrophe in Idefault Causes Serialization Error at End of Run Time Report Number: 21310 Application: METGENDB.DLL In MET/CAL V7.00, V7.01, V7.01 SP1, and V7.01 SP2 an apostrophe in the Idefault value causes a serialization error at end of the Run Time application. The user had "Manufacturer's Spec" as a default for field 2355. (This is a V6.11 upgraded database). With V7.00 Run Time, when trying to save the results, a 232 serialization error occured. To demonstrate: ( 1) Start MET/TRACK. ( 2) Login in as "MT". ( 3) Go to "Lay-out" : "Entry Screens" : "Calibration Screen" ( 4) If field 2355 is not already on the screen, choose the button which has the tooltip "Restore a field...", then select field 2355 and click the button which has the tooltip "Restore a field..." in the "Field Restore" window. ( 5) Double-click the field 2355 edit control in the "Calibration Entry/Edit Screen..." window. ( 6) Check the "Required" check box. ( 7) Enter "Manufacturer's Spec" as the default value. ( 8) Click the 'X' in the upper right hand corner of the "Field Properties" window to close, and, one hopes, save the changes. ( 9) Type Alt+F4 to close MET/TRACK. (10) Start the Run Time and, in demo mode, run any procedure. (11) Before results are saved observe the following error message: (232icc)SQL Error::Syntax error or access violation Resolved in V7.10. This has been corrected by a change to the MET/TRACK customization screen which causes single quotes to be transformed to double quotes as they are stored in the default value of "mt.customization". ----> Quick Reports Label "Alternate Row Colors" is Truncated Report Number: 21161 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 the Label "Alternate Row Colors" under Options is wrapped around and truncates the text in English (unknown for the other languages). Resolved in V7.10. ----> Problem with Cal Time and Due Time Fields Report Number: 20946 Application: MET/TRACK In MET/TRACK V7.01, V7.01 SP1 and V7.01 SP2, only the first character of the Cal Time and Due Time fields is shown if the user invokes the search by dropping down the value edit control, rather than using Ctrl+F or the "Search" menu item. The problem occurs only on the initial search. Resolved in V7.10. ----> Company Name Does Not Appear in Reports When Run From MET/TRACK Report Number: 20820 Application: MET/TRACK In MET/TRACK V7.00 the Company Name does not show up in the reports when run from Met/Track. However, it does show up at the end of Run Time when the same report is run. What appears is: "Company Name from dbconfig" A customer reports that this worked with V7.00 and broke after installing V7.00 SP4. Resolved in V7.10. (Actually, this was resolved with the V7.01 release, but the corresponding report did not make it into the V7.01 readme file, and therefore is being included here in the V7.10 readme file.) ----> MET/TRACK Allows Entries of Validation Values Longer than Max Field Length Report Number: 20723 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 it's possible to enter validation values which exceed the field length of the field to which the validation list applies. To demonstrate the problem: 1. Login as MT. 2. Choose "Inventory Screen" in the "Entry Screen" submenu under the top-level "Lay-out" menu. 3. Double-click on the "Description" field to bring up the "Field Properties" window for that field. (If "Description" is not shown in the Inventory Form, you will have to first re-configure the form so that "Description" is displayed.) 4. Choose the "Validation/Merge" tab. 5. Choose the "Reg Val" radio button. 6. Choose "Edit". 7. In the "Field Validation" window enter a 61 character value. 8. Choose "Save". 9. Close the "Field Properties" window. 10. Close the "Inventory Entry/Edit Screen..." window. 11. Close the MET/TRACK main window. The issue illustrated above is that even though the maximum allowed length for a "Description" field value is 60, MET/TRACK's validation editor allows longer values to be entered. A side-effect of this problem is that when the Run Time prompts for required inventory data, a "truncation error" (E5399) occurs, which prevents the addition of inventory data for the new asset. This problem likely exists for all fields in all tables for which the user may specify validation in the form of a drop-down list or a "pick list". Resolved in V7.10. ----> Install Program Option for Choosing Applications to Install is Confusing Report Number: 20643 Application: Install In MET/CAL V7.00 and V7.01 a number of user have commented that the Install Program function where the user chooses which application to install is confusing. Resolved in V7.10. The user no longer has the option of selecting functional groups. Run Time, Editor, and MET/TRACK are selected by default. Other applications are available. Applications are selected for installation by a check box method familiar to most Windows users. ----> Incorrect Tool Tip for "OK" Button in MET/TRACK Forward Trace Window Report Number: 20572 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 on the Forward Trace dialog box the tool tip on the OK button says "&OK". Resolved in V7.10. ----> MET/TRACK Quick Reports Form Uses English Table Names in Treeview Report Number: 20495 Application: MET/TRACK In MET/TRACK V7.00, V7.01, V7.01 SP1 and V7.01 SP2 the Quick Reports form shows a treeview containing: Inventory Calibration Location Maintenance Customers in the left panel (when the leftmost tab is selected). These table names should appear in French when the selected language is "French". Resolved in V7.10. ----> Mismatch Between Maxlen and Field Data for Some Inventory Table Fields Report Number: 20414 Application: METGENDB.DLL In MET/CAL V7.00, V7.01, V7.01 SP1, and V7.01 SP2 a problem occurs for certain Inventory Table fields when an attempt is made to fetch the field value, for a particular asset, and the provided buffer is one byte larger than the claimed maximum field length. This problem occurs for fields for the following fields: 4236 4238 4254 4255 5256 4257 Note that the for the last 4 fields (4254 to 4257) this error occurs even though ISQL lists the field values as "(NULL)". Resolved in V7.10. The database (and "patch1.sql") have been modified to maximum length and data length 26 for fields of type "timestamp". Also, "metgendb.dll" has been modified so that for fields of type "double" it passes back a field length of 32 characters. ----> Misspelled Words in Users Manual Report Number: 20360 Application: Documentation In MET/CAL V7.00 and V7.01 the following errors exist in the User's Manual: (1) On page 7-14 of the users manual, the Picture Directory is specified as "pidir". It should be "picdir". (2) On page 7-17 of the users manual, the Procedure Directory is specified as "pocdir = picture_directory". It should say "procdir = procedure_directory". Resolved in V7.10. ----> Contact Numbers for Europe Are Incorrect Report Number: 20351 Application: Documentation In the MET/CAL V7.00 User's Manual (also shipped with V7.01) the contact number for Europe are incorrect. Resolved in V7.10. ----> Crystal Reports Preview from Run Time Doesn't Support Double-Click to Maximize Report Number: 19875 Application: MET/TRACK In MET/CAL V7.00, V7.01, V7.01 SP1, and V7.01 SP2 when a report is previewed from MET/TRACK you can maximize it by double-clicking on the caption. However, when the report is previewed from the Run Time, the same capability is not provided. Resolved in V7.10. This was solved by the upgrade from Crystal Reports V8 to Crystal Reports V10. ----> Getting Started Guide on V7.00 CD Incorrectly Has "Version 6" Page Header Report Number: 19606 Application: Documentation In MET/CAL V7.00 and V7.01 the file "GettingStartedV7.pdf" on the MET/CAL CD incorrectly states that it is "Version 6" on the title page and on the page header which appears on alternate pages. An updated electronic copy of "GettingStartedV7.pdf" was shipped with V7.01. Resolved in V7.10. ----> Report Error with Multiple Workstations Report Number: 13209 Application: MET/CAL In MET/CAL V7.00, V7.01, V7.01 SP1, and V7.01 SP2 some users have reported problems with the Crystal Reports report preview window being "locked up" when the same report is previewed on multiple workstations at the end of the Run Time application. Resolved in V7.10. ------------------------------------------------------------------------------- Section 11: V7.01 SP2 Problem Reports ---------------------------------------- ------------------------------------------------------------------------------- This section contains problem reports which describe all corrections made from V7.01 SP1 to V7.01 SP2. ----> Non-Standard Behavior When Tabbing Between Controls in MET/TRACK Forms Report Number: 24915 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier V7 versions of MET/TRACK, errors and inefficiencies in the keyboard handler cause non-standard behavior in various forms when tabbing between controls, using Ctrl+S to save, and using Ctrl+F4 to close. V7.01 SP2 corrects this problem. ----> Table Form Focus Error Causes Disconnect Report Number: 24914 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier V7 versions of MET/TRACK, the application may crash when adding or editing calibration, location, inventory, customer, or repair records in cases where the current Windows focus is set to a non-visible control in the form. V7.01 SP2 corrects this problem. ----> 3458 FSC Help Incorrectly Documents Offset Compensation Selection Criterion Report Number: 24913 Application: Editor (Documentation) In MET/CAL V7.01 SP1, and earlier versions, the 3458 FSC on-line help file incorrectly documents the upper resistance limit at which the driver selects offset compensation. The documented limit is 10 kOhm, but should be 12 kOhm. V7.01 SP2 includes an updated help file for the 3458 FSC. To install the help file copy it into the help directory, replacing the existing help file. (The location of the MET/CAL help directory may be determined by looking at the value of the "helpdir" parameter in the [Startup] section of the MET/CAL initialization file ("metcal.ini"). ----> Windows Resource Problem (CreateSolidBrush) Report Number: 24907 Application: Editor In MET/CAL V7.01 SP1 Editor, and earlier Editor versions, a Windows resource problem involving the Win32 function "CreateSolidBrush" may occur in situations where a procedure runs continuously in a loop, with the Test Results window and the edit child window (containing the procedure) both open. The problem is not seen frequently, but may occur when MET/CAL is used for factory test or monitoring applications. The specific error, when it occurs, is E2241: Internal Error: "CreateSolidBrush" failed ... V7.01 SP2 corrects this problem. ----> Quick Reports Fails with Dutch Regional Settings When Limits Specified Report Number: 24889 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier versions, there's an error in Quick Reports when the regional settings on the PC cause different numeric or date formats to be used, and when numeric or date limits are specified to define the report. The error that occurs involves a dropped database connection. V7.01 SP2 resolves this problem. ----> MET/TRACK Crash After Double Save in "Add Calibration" Report Number: 24881 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier V7 versions of MET/TRACK, an application crash can be induced by typing Ctrl+S to save changes in an edit form whenever the Windows focus is on any of certain non-text edit controls. In V7.01 SP2 MET/TRACK has been changed. Ctrl+S now saves the changes, but does not close the form. After a Ctrl+S is typed focus is set to the first text box in the form. At that point Ctrl+F4 may be used to close the form. A related change is that if the focus is on a non-text control when Ctrl+F4 is typed, focus is moved to the first text control on the form, but the form is not closed. A second Ctrl+F4 may be used to close the form. ----> MET/TRACK Allows Deleting "mt.results" Rows, But "Combine Cal" Then Fails Report Number: 24851 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions of MET/TRACK, if you delete rows from the Results Table prior to performing a "combine cal" operation, the combination fails. V7.01 SP2 corrects the problem. ----> Adder Errors in 1000 VDC Range Sections of 8508A Accuracy Files Report Number: 24848 Application: MET/CAL In MET/CAL V7.01 SP1, and earlier versions, there are floor specification errors in the 1000 V range sections of the 8508A accuracy files ("8508.acc" and "8508_95pct_1degC_1yr.acc"). For example, in the "Mode: 1000V D8" section of "8508.acc" the line: -1050 1050 NA NA 0.00033 500E-6 10E-6 has been changed to: -1050 1050 NA NA 0.00033 1E-3 10E-6 V7.01 SP2 corrects the errors. In each of the two accuracy files there are 37 lines where the adder has been increased to correctly reflect the 8508A specifications. ----> PM668x Meas Time Incorrect for 2nd, 3rd... NMEAS Loop when MEASURE_ONLY=YES Report Number: 24700 Application: MET/CAL In MET/CAL V7.01 SP1 and prior the PM 668x driver calculates an incorrect OPC timeout in some cases. The FSCs affected are 6680, 6681, and 6685. The OPC timeout is the timeout in effect when the driver is waiting for a measurement to complete. The problem occurs only when: (a) Measurement uncertainty is enabled, and (b) the number of measurements per test ("NMEAS") is greater than one, and (c) the "MEASURE_ONLY" parameter is set to "Yes". This problem was found by code inspection. No actual run time problem has been observed. However, in principal, when all of the above conditions are true, there may be tests which timeout prematurely (i.e., before the measurement has completed). The problem has been corrected in V7.01 SP2. ----> Trace Report Does Not Show Correct Selected Dates in Page Footer Report Number: 24651 Application: Reports In MET/CAL V7.01 SP1 and prior the Trace Report does not correctly show the selected dates in the page footer section. Instead, it shows the last cal date and the due date of the last instrument calibrated. The problem has been corrected. V7.01 SP2 includes an updated Trace Report ("trace.rpt"). ----> Numeric Fields in Database Not Updated Correctly in V5 to V7.01 Upgrade Report Number: 24646 Application: MET/TRACK In V7.01 there's an upgrade problem which occurs when upgrading from V5 to V7.01. The problem is present in the SQL script "patch2.sql", which is applied to the database when "dbupdate.exe" is executed. (This is part of the upgrade process.) The specific problem is that the maximum length for certain numeric database fields is not correctly updated to the V7 value. The maximum therefore remains set to the V5 value, which is less than the V7 value. The problem has been corrected in V7.01 SP2. An updated copy of "patch2.sql" is included in the service pack. To apply the patch install "patch2.sql" in the proper directory, then run "dbupdate.exe". ----> 4805 99% 1yr Accuracy File Has Non-Contiguous Frequency Band for 1000V Range Report Number: 24640 Application: MET/CAL In V7.01 SP1 and prior there's an error in the 1000V range section of the Datron 4805 99% 1-year accuracy file. In the accuracy file lines: 200.00 1100.00 10 330 570e-4 120e-3 10e-3 200.00 1100.00 3e3 10e3 440e-4 100e-3 10e-3 200.00 1100.00 10e3 33e3 680e-4 160e-3 10e-3 there is a gap between 330 Hz and 3000 Hz which is not represented. The error causes an accuracy lookup error for procedure statements like: 4805 1000V 1% 1kH 2W The problem has been corrected in V7.01 SP2. The service pack includes and updated accuracy file ("4805_99.1yr"). ----> Procedure Compiler Generates Incorrect TUR for 8508 MEMC test Report Number: 24639 Application: Editor In MET/CAL V7.01 SP1 and prior there's a problem with the compile time TUR calculation for the 8508 FSC. The problem does not always occur. It depends on the sequence of compile time operations (F8, , F9), and on the particular statements in the procedure. The evaluation step must be a MEMC or MEMCX statement. The problem is not present in the TUR Report, or in the run time TUR calculation. The problem occurs when the software associates the wrong M8508 statement with an 8508 statement. Here's an example procedure which demonstates the problem: INSTRUMENT: Incorrect 8508 TUR 1.001 M8508 RNGLK 200mV 1.002 8508 100.00mV D5 N 2W 1.003 MEMC 125 100.00mV 0.02% 0.01U 2.001 M8508 RNGLK 20V 2.002 8508 2.500V D5 N 2W 2.003 MEMC 12.5 2.500V 0.02% 0.001U If you load this procedure into the Editor, in text mode, then switch to procedure mode and type F9, an incorrect TUR warning will be generated. What happens is that the second M8508 statement ("M8508 RNGLK 20V") is incorrectly associated with the first 8508 statement, producing an invalid TUR. The problem has been corrected in V7.01 SP2. ----> Validation Does Not Work for Inventory Field 4229 Report Number: 24616 Application: MET/TRACK In MET/TRACK V7.01 SP1 and prior, Inventory Table field 4229 ("Recall Interval") does not correctly support field validation using the "Req Val" and "Pick List" methods. If you login as the MET/TRACK administrator you can configure the field to be validated by one of these methods, but the proper dropdown list of legal values is not available when you are logged in as a normal user attempting to edit I4229 in the Inventory Table screen. Resolved in V7.10 SP2. ----> Repair Table Does Not Assign Archive Bits to Each Repair Type (R3251) Report Number: 24606 Application: MET/TRACK In V7.01 SP1, and earlier, the Repair Table should differentiate repairs by type and assign an archive bit to each unique repair type for a UUT. However, it does not operate that way. Rather, on insert, it assigns a single archive bit for a UUT for the entire tablet, but, on update, it works as desired. This can result in unwanted query results for report generation. The problem was found by code inspection. No problem reports from customers have been received. V7.01 SP2 includes and updated patch file ("patch3.sql") which, when executed, updates a number of database triggers to correct the problem. To apply the patch it is necessary to install "patch3.sql" in the proper directory, then run "dbupdate.exe". ----> Recursion in Location Trigger Causes Delays With Large Database Report Number: 24593 Application: MET/TRACK In V7.01 SP1, and earlier versions, certain database operations are non-optimal because database triggers are not implemented efficiently. This slows down database operations unnecessarily. The problem may become acute when working with a very large database on which the On Time Support "Change Log" program is installed. V7.01 SP2 includes updated database triggers which operate more efficiently. The updates are implemented by applying the database patch "patch3.sql". To apply the patch install "patch3.sql" in the proper directory, then execute "dbupdate.exe". ----> Default for Field 4212 Not Applied Correctly Report Number: 24541 Application: MET/TRACK In V7.01 SP1 and prior, if the default value for field 4212 ("Note Date") is set to "Current Date" for both Add and Update, the date will not change to the current date when the form is edited or saved. However, if you clear the previous date from the field, then save the record, it will show the current date. The problem has been corrected in V7.01 SP2. ----> Error When Copying from C2371 to an Inventory Date Field Report Number: 24536 Application: MET/TRACK In V7.01 SP1 and prior, if the software is configured to copy from field 2371 (user date field, defaulted to current date) to an Inventory Table date field (e.g., 4251) an error occurs at the end of the Run Time application. V7.01 SP2 corrects this problem. Note: The MET/TRACK part of this problem was resolved in V7.01 SP2. The Run Time part of the problem is resolved in V7.10. ----> Unstable Operation After Aborting Creation of New Cal Record Report Number: 24497 Application: MET/TRACK In MET/TRACK V7.01 SP1 unstable operation of the application occurs after aborting the creation of a new cal record. The sequence of steps required to demonstrate the problem is: (1) Select an asset from the Browser. Choose an asset which has at least 1 cal record. Then choose the "Calibration" tab. (2) Click on the "+" button. (3) Abort this operation by clicking on the "X". (4) Select "No" on save changes. (5) Next select the pencil (edit this calibration record). The cursor will change to a "flashing" hour glass and you can't do anything. If you attempt to close the application the login screen will appear. If you try to close it you will get a series of error messages and the login form will keep re-appearing. At this point it is necessary to use the Windows Task Manager to close the application. V7.01 SP2 corrects this problem. ----> 8590 FSC with NMEAS > 1 Causes Invalid System Actual Value in Post Test Report Number: 24493 Application: MET/CAL In V7.01 SP1 and prior, when an 8590 statement is executed, with NMEAS greater than 1, and NOMINAL field units are "D" (dBm), an invalid System Actual value is calculated. Here's an example procedure fragment which shows a case where the problem occurs: 1.001 ASK- R Q N P F V 1.002 VSET NMEAS = 2 1.003 8590 -20.00D 1.00U 100MH This problem was caused by a missing statement to assign an impedance value for the 8590. The missing impedance value, in turn, caused the V to dBm conversion to fail, which resulted in an invalid average value in the measurement uncertainty module, and the invalid average was then assigned as the System Actual value. The problem has been corrected in V7.01 SP2. ----> Misspelling "RNGLK" in M8508 Statement May Crash Editor Report Number: 24486 Application: Editor In MET/CAL V7.01 and prior, if if a procedure writer misspells the word "RNGLK" in an M8508 statement the Editor may crash. The misspelling must be such that the misspelled word ends with a 'K', and the next to last character is not an 'L'. The problem has been corrected in V7.01 SP2. ----> 856x Driver (856x & 859x FSCs) Performs Unnecessary Sweeps Report Number: 24472 Application: MET/CAL In V7.01 SP1, and earlier versions, the 856x driver, used by the 8560, 8566, 8568, and 8590 FSCs, performs one or more unnecessary sweeps. For long sweep times or a large "NMEAS" setting, this can add a substantial time penalty to procedure execution. The low-level measurement function in the 856x driver uses the following algorithm: 1. Perform a sweep. 2. If MOD3 not AF... 2.1 Perform a peak search. 2.2 Set marker to center frequency. 3. Perform a sweep. 4. Query marker amplitude. 5. If MOD3 not AF... 5.1 Query marker frequency. The low level measurement function is invoked from a higher level function that actually performs the test (Setup, Nominal Setup, Evaluation, or Comparison). Currently with measurement uncertainty disabled (default or NMEAS = 0), the 856x driver performs four sweeps for each 856x statement. This is because the high level function invokes the low level function twice. The first call is to throw away a reading which causes two sweeps to be performed. The second call is to obtain the saved reading which causes another two sweeps to be performed. The second call to the low level measurement function should take only one sweep. The time penalty is worse when measurement uncertainty is enabled. For example if NTHROW = 2 and NMEAS = 2, the 856x driver will perform 8 sweeps when five sweeps would be sufficient. MET/CAL V7.01 SP2 includes an updated 856x driver which eliminates the unnecessary sweeps. ----> Field 3250 Has Incorrect Selections for Default Report Number: 24433 Application: MET/TRACK In V7.01 SP1, and earlier V7 versions, Maintenance Table field 3250 has incorrect selections for the default value. If you view the default list, the displayed selections are: Current Date User's Login Name User's Full Name User's Segregate User's Workstation Desktop Name These are not valid values for the "Default Value" dropdown list. V7.01 SP2 corrects this problem. The "Default Value" dropdown list now shows: D W M U N ----> RESET FSC for UUT with [SDC] at Beginning Not Executed Correctly Report Number: 24423 Application: MET/CAL In MET/CAL V6.10 through V7.01 SP1 a RESET statement for the UUT which begins with a non-address construction (for example, "[SDC]") is not evaluated correctly. (Prior to V6.10 the RESET statement could not be used to reset the UUT, unless the UUT address (IEEE-488 or serial) was directly or indirectly specified. Therefore, the issue described in this problem report does not apply to versions prior to V6.10.) The problem has been corrected in V7.01 SP2. ----> Date Search from Toolbar (Field/Value) Causes Database Disconnect Report Number: 24388 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions, the database connection may be dropped after a date search from the toolbar. Here's an example which shows how to cause the problem to occur: (1) In configuration select a date field from the search form (e.g., 2303). (2) Login as a normal user and select Field 2303. (3) Select a value from the "Value" listing. (4) Click on the field glasses. (5) The error message: Connection to the database has been lost ... etc. MET/TRACK must terminate. will be generated. V7.01 SP2 corrects the problem. ----> 5520 Thermocouple Measurement with MEASURE_ONLY = YES Causes GPF Report Number: 24384 Application: MET/CAL In MET/CAL V7.01 SP1, and earlier versions, a problem occurs when executing a 5500, 5520, 5800, or 5820 statement if all of the following are true: (1) Measurement uncertainty is enabled and the number of measurements ("NMEAS") is greater than 1. (2) The "MEASURE_ONLY" parameter is set to "Yes". (Note that the default for this parameter is "No".) (3) A measurement function of the instrument is being used: MOD3 Measurement ------ -------------------------------- HM Humidity OM 50 Ohm Input Overload Protection TM, TN Thermocouple VM Voltage ZM Input Impedance Executing a 5500, 5520, 5800, or 5820 statement with the above conditions all true causes an application crash (GPF) in Run Time or Editor Test Run. Here's an example procedure fragment which can be used to demonstrate the problem: VSET nmeas = 2; MEASURE_ONLY = yes DISP Connect a Source of 25°C to TC-Input of 5520A TARGET -m 5520 25.0degC 0.5U _K TM 2W The problem occurs in both real mode and demo mode. V7.01 SP2 corrects the problem. ----> Duplicate Instrument Name, Manually Entered, Not Detected Properly Report Number: 24361 Application: Configuration Utilit In V7.01 SP1, and some prior versions, it is possible, using the Configuration Editor (F12 in Editor or Run Time), to configure two instruments with the same name. However, MET/CAL does not support multiple configured instruments with identical instrument names, so the Configuration Editor should not allow this situation to occur in the first place. This problem was introduced when the Configuration Editor was updated (for a previous release) to show the instrument address in the "Current Configuration" window. V7.01 SP2 corrects the problem. ----> 3325 Accuracy File Interval Incorrect Report Number: 24237 Application: MET/CAL In V7.01 SP1, and earlier versions, the header of the 3325 accuracy file ("3325.acc") incorrectly states that the calibration interval is 90 days. However, the specifications in the accuracy file are 1-year specs. V7.01 SP2 includes an updated 3325 accuracy file which corrects the interval specification. ----> Customer Information Not Updated After Search Report Number: 24235 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions of MET/TRACK, customer information is not always displayed correctly after a search. Here's a detailed description of how to demonstrate this problem: (1) Start MET/TRACK, then choose "I4201 - Asset Number" in the "Field:" edit control on the MET/TRACK tool bar. (2) Choose an asset number in the "Value:" dropdown list on the MET/TRACK tool bar. In this step you must choose an asset which has customer information associated with it. (3) Click on the "Begin Search..." icon on the MET/TRACK tool bar. (4) Click on the "Customer" tab. You are now looking at asset information for the asset specified in step (2) on the left portion of the MET/TRACK screen, and the associated customer information on the right portion of the screen. (5) Now choose a different asset number in the "Value:" dropdown list on the MET/TRACK tool bar. In this step you must choose an asset which has customer information associated with it, and which has customer information different from the customer information associated with the asset chosen in step (2). (6) Click on the "Begin Search..." icon on the MET/TRACK tool bar. Observe the problem: You are now looking at asset information for the asset specified in step (5) on the left portion of the MET/TRACK screen, and the customer information for the asset chosen in step (2) on the right portion of the screen. The problem has been corrected in V7.01 SP2. ----> Maintenance Table Uses Default Calibration Interval Type From Inventory Table Report Number: 24176 Application: MET/TRACK In V7.01 SP1, and earlier versions, the Maintenance Table uses the default calibration interval type from the Inventory Table. It should use the default specified for the Maintenance Table calibration interval. To duplicate the problem: (1) Start MET/TRACK, logging in as the administrator. (2) Confirm that the default value for the Inventory Table "Interval Units" field (I4228) is "M". If it's otherwise, change it to "M". (3) Choose "Lay-out" : "Entry Screens" : "Maintenance". (4) Customize R3250 ("Interval Units") so that the default value is "N". (5) Close MET/TRACK. (6) Start MET/TRACK, logging in as a normal user. (7) Choose "Add" : "Maintenance Record". (8) Specify any existing asset. (9) When the "New Maintenance Record..." window appears, observe that the value in the "Interval Units" field is "M". The default value should be "N". V7.01 SP2 resolves the problem. ----> C2311 Trailing Zeroes Not Shown On Calibration Browse Form Report Number: 24175 Application: MET/TRACK In V7.01 SP1, and earlier versions, Calibration Table field C2311 (temperature) is not displayed correctly in the MET/TRACK browse screen when the digits to the right of the decimal point are zero. For example, given a temperature value of "23.0", the MET/TRACK edit screen correctly displays "23.0", but the browse screen incorrectly shows just "23". The problem is the same when the decimal symbol is a comma. The browse screen shows just "23", but the edit screen shows "23,0". V7.01 SP2 corrects this problem. The browse screen now displays one digit to the right of the decimal point. ----> Maintenance Calculates Due Date When Interval Type Is "N" Report Number: 24173 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier V7 versions, there's a problem in the Maintenance Form which sometimes occurs. The problem is that the Maintenance Form calculates and displays a due date even when the interval type is "N" (i.e., "never needs cal") and the calibration interval is zero. V7.01 SP2 corrects this problem. ----> Level 3 User With "Add" But Not "Update" Access Can Modify Inventory Data Report Number: 24171 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior versions, a level 3 user is incorrectly allowed, in some cases, to modify Inventory Table data. The problem occurs when a particular Inventory Table field is configured to: (1) allow level 3 to add, and (2) not allow level 3 to update. When a field is configured this way, a level 3 user is allowed to modify the field value in the MET/TRACK edit inventory screen. V7.01 SP2 corrects the problem. A level 3 user is no longer allowed to modify an inventory table field value when the field is configured as described above. ----> Update Hertz Leveled Sine Specs in Fluke 5820A Accuracy File Report Number: 24118 Application: MET/CAL In V7.01 SP2 leveled sine specifications for the Fluke 5820A have been updated in the MET/CAL accuracy file. This change was necessary because there was a corresponding update to the leveled sine specifications in the 5820A operator and service manuals: For the Operator Manual, change table 1-5 (Leveled Sine Wave Specifications) frequency characteristics, 1-year absolute uncertainty, from 0.33 ppm to 0.33 ppm +/- 0.5 Hz. In the Service Manual, change table 1-11 (Leveled Sine Wave Specifications) frequency characteristics, 1-year absolute uncertainty, from 0.33 ppm to 0.33 ppm +/- 0.5 Hz, as well. V7.01 SP2 includes an updated accuracy file ("5820.acc"). ----> 5700A & 5720A 180-Day Accuracy Files Have Incorrect Frequency Ranges Report Number: 24116 Application: MET/CAL V7.01 SP2 includes updated accuracy files for the Fluke 5700A and Fluke 5720A. Previous versions of the accuracy files contained errors in some of the AC voltage and AC current frequency range upper limits. The errors occur only in certain very narrow frequency ranges. For example, above 99,999 Hz, but less than 100,000 Hz. Another example is above 299,990 Hz, but less than 300,000 Hz. This change affects the following files: 5700.acc 5700_95pct_180dy.acc 5700_99.1yr 5720.acc 5720_95pct_180dy.acc 5720_99.1yr ----> Error During PM 6680 Measurements Report Number: 24109 Application: MET/CAL In MET/CAL V7.01 SP1, and prior versions, some 6680 statement may cause the error: E2075: PM 6680: -113,"Undefined header" to be generated. An example of a test which may generate this error is: M680 ChA 100kH 6680 100000.00nT 0.5U 0.99Vpp +A PA However, it is not always the case that the error occurs when the above test is executed. It depends procedure timing, which is affected by preceding procedure statements and other factors. The problem has been resolved. In V7.01 SP2 a 50 ms delay was added between the last setup command to the counter and the first initiate command. ----> Source Copy of Fields to Inventory Table Fields Can't Be Viewed or Removed Report Number: 24089 Application: MET/TRACK In MET/TRACK V7.01 SP1 there's a problem viewing or removing the "source copy" of fields. The following sequence of steps shows how to cause the problem: 1. Log into MET/TRACK as the administrator ("MT"). 2. Select layout/inventory entry/edit. 3. Select a date field on the Inventory Form (e.g., 4251). 4. Select C2301 as the source. 5. Close the "Field Properties" window. 6. Reopen the "Field Properties" window. 7. Observe that the source copy is blank. ISQL shows that 4251 has "Scopy" set to 2301. 8. Select C2303 as the source. 9. Close the "Field Properties" window. 10. Reopen the "Field Properties" window. 11. At this point note that there is no way to remove the entry. V7.01 SP2 corrects this problem. ----> Units Reported for S1, S2, U1, ..., U10 Should Be V when NOM Units Are dBm Report Number: 24053 Application: Run Time In V7.01 SP1, and prior V7 versions, units reported in the Results Table for the result quantities S1, S2, U1, U2, ..., U10 are incorrect when the Nominal units are dBm. The reported units should be "V", not "dBm". MET/CAL linearizes the UUT Resolution, Nominal, and other values by converting from dBm to rms voltage. The various parts of the uncertainty calculation (the calculation of S2, the standard deviation, the top-level RSS, etc.) are then performed in linearized units, not directly in dBm. The Standard Uncertainty, after being calculated in volts, is then converted back to dBm before being reported in the Results Table in the database. In V7.01 SP2 the problem has been corrected. In cases where the evaluation units are dBm, and MET/CAL therefore does the uncertainty calculation in linearized units (namely rms voltage), MET/CAL now reports appropriate linearized units (rms voltage) in the Results Table. This change affects the following result quantities: Standard Deviation S1 S2 System Accuracy U1 U2 U3 U4 U5 U6 U7 U8 U9 U10 Other result quantities are reported in dBm (in the database Results Table). These include: UUT Resolution Standard Uncertainty Expanded Uncertainty Average Measurement Individual Measurements (NMEAS values) V7.01s or later of the Run Time application is required to obtain this change. It is important to bear in mind that MET/CAL only linearizes dBm values in cases where it knows the impedance of the reference. This means that linearization will happen in cases like: (1) 5520 -50.00D 1kH 0.85U SI 2W (2) 5520 -50.00D 1kH SI S 2W ... MEMCX -50.00D 0.85U but will not happen in a case like: (3) IEEE ... MEMCX -50.00D 0.85U In other words, the test has to be either a standard instrument evaluation step, or has to be a MEMC / MEMCX test with a preceding associated instrument setup statement. In either case, the reference must be an instrument for which MET/CAL includes a built-in driver (and, therfore, for which the impedance is known to the software). Also remember that, as stated in the VSET on-line help file, if one or more optional uncertainty components (U3 to U10) are specified MET/CAL assumes that the optional components are entered as RMS voltage values, not dBm values, when the test is one for which MET/CAL is automatically linearizing for purposes of the uncertainty calculation. ----> Total Passes Greater Than 99 (2 Digits) Generates Error 380 Report Number: 24012 Application: MET/TRACK In V7.01 SP1, and prior V7 versions, if the "Total Passes" field (C2344) is greater than 99 (2 digits), a MET/TRACK error is generated (Error 380) when a calibration record is added or edited. The data type of field C2344 is 'integer'. MET/TRACK currently limits the value of this field to 99, but there should be no such limit. V7.01 SP2 corrects this problem. The value if C2344 is now limited only by the maxium integer value. ----> Value of Reliability Field (C2362) Cannot Exceed 99 Report Number: 24011 Application: MET/TRACK In V7.01 SP1, and prior V7 versions, if the value of the reliability field (C2362) is greater than 99, MET/TRACK generates "error 380" when a calibration record is added or edited. The data type of C2362 is integer. MET/TRACK should not limit the value to 99. V7.01 SP2 corrects this problem. ----> Database Disconnect Caused By Date-Based Search Report Number: 24005 Application: MET/TRACK In V7.01 SP1, and prior V7 versions, when attempting to search on a date field using the toolbar MET/TRACK may disconnect from the database. To demonstrate: Select a date field from the "Field" drop down list (e.g., C2301). Select a date from the "Value" drop down list. Click on the "Begin Search" icon. When the problem arises the following message is generated: Your connection to the database has been lost. You may have been disconnected by the system administrator or ... MET/TRACK must terminate. The same operation works from the "Search" form, however. The problem affects all date fields and numeric fields when the search is done on the main screen with the following condition(s): 1. The date field does not have the format "YYYY-MM-DD". 2. The regional settings for the numeric field are not in "US Standard". (When the regional settings change it may change the default date field format.) In V7.01 SP2 the problem has been resolved. Now the search is checked against the field type and covers the following date and numeric fields: Date Fields: C2301, C2303, C2306, C2316, C2342, C2371 TO C2374, C2380, K4621 TO K4624, I4212, I4221, I4224,, I4250 TO I4253, L2806, L2807, L2809, L2822 TO L2825, R3230, R3247, R3261 TO R3264 Numeric Fields: C2309, C2310, C2311, C2312, C2315, C2317, C2324, C2328, C2375 TO C2379, C2386 TO C2392, K4625 TO K4628, I4219, I4254 TO I4257, L2818 TO L2821, R3209, R3212, R3215, R3218, R3221, R3224, R3227, R3229, R3231, R3232, R3235, R3239, R3252, R3265 TO , R3269 ----> Editing Sequence Generates Incorrect Active Head List in 9500-Based Procedure Report Number: 23964 Application: Editor In MET/CAL V7.01 SP1, and earlier versions, in some cases when compiling a 9500-based procedure the MET/CAL Editor generates a procedure header containing an invalid list of required active heads in the instrument configuration section. Here's an example which shows how to cause this problem to occur: First, configure a 9500B/3200 with 9530 heads on channels 1 and 2. Then use the Editor to enter and compile the following procedure: Instrument: Test M9500 * 9500 3.2GH 100mVpp LS S L M9500 CH12 9500 1.1GH 100mVpp LS S L This generates procedure header configuration lines as follows: CONFIGURATION: Datron 9500 (G5, C3) CONFIGURATION: Datron 9530 on channel 1 CONFIGURATION: Datron 9510 on channel 2 However, if you: (1) Comment out the 1.001 line. (2) Type F9. (3) Position the cursor at the beginning of line 1.003. (4) Type a space. (5) Type F9. the procedure header configuration lines now become: CONFIGURATION: Datron 9500 (G5, C3) CONFIGURATION: Datron 9560 on channel 1 CONFIGURATION: Datron 9560 on channel 2 However, the procedure header configuration lines should have remained unchanged. V7.01 SP2 corrects this Editor problem. ----> 9500 Active Head Requirement Not Computed Correctly When Period Specified Report Number: 23950 Application: MET/CAL In MET/CAL V7.01 SP1, and earlier versions, the 9500 active head requirements are not always computed correctly by the compiler when the 9500 statement specifies period (seconds) in the NOMINAL field. Problems may arise at the end points of a range. For example, 9510 and 9520 heads can output a 909.09 ps leveled sine wave. However, the MET/CAL compiler computes period limits by using the inverse of frequency limits. Therefore, in this example, MET/CAL computes the period limit as 1 / 1.1 GHz, which is not exactly equal to 909.09 ps. V7.01 SP2 corrects this problem. MET/CAL now uses directly specified period limits (in seconds), rather than calculating the period limits by inverting the corresponding frequency limits. ----> Combine Cal Causes Disconnect When Regional Settings Are Spanish Report Number: 23810 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions, the Combine Calibration operation fails when the decimal symbol in effect at the time the records to be combined are created is different from the decimal symbol in effect at the time the records are combined. For example, if you create two records with the regional setting on your PC set to "English (United States)", then change the regional setting to "German (Standard)", then perform a combine calibration operation using MET/TRACK, the operation will fail because the decimal symbol used for numeric field values when the two calibration records were created is '.', but the decimal symbol used when the records are combined is ','. This affects all numeric fields in the Calibration Table: C2309 C2310 C2311 C2312 C2315 C2317 C2324 C2328 C2375 to C2379 C2386 to C2392 V7.01 SP2 corrects this problem. ----> 8562E Error 111 Generates Incorrect MET/CAL Error Message Report Number: 23807 Application: MET/CAL In MET/CAL V7.01 SP1, and earlier versions, incorrect error messages are generated when an error occurs with the 8560 or 8590 series spectrum analyzer, and the error code is less than 400. For example, when the error code is 111, MET/CAL generates the error message: E5983: HP8562E: LO or RF hardware/firmware failure. However, the error message should be: E5854: HP8562E: Command does not have enough arguments. V7.01 SP2 corrects this problem. ----> 8560 FSC Causes Error When Used With 8560E Report Number: 23802 Application: MET/CAL MET/CAL V7.01 SP1 introduced a problem when using the 8560 FSC to control an 8560E. The problem was introduced when bug report #22535 ("8568/M8568 Statements Cause IEEE-488 Timeout") was addressed in the V7.01 SP1 release. The underlying problem is that the 8560 family of instruments are not consistent with regard to their handling of the "TS" command. It turns out (and this has been confirmed by Agilent) that for some instruments the Take Sweep command must be invoked by sending "TS" (no terminator). For others, it must be invoked by sending "TS;" (terminator required). In V7.01 SP2 the MET/CAL driver for this instrument family now distinguishes between different instruments and sends a Take Sweep command appropriate to each. ----> IEEE-488 Read Greater Than 4096 Bytes May Fail Due To Readdressing Instrument Report Number: 23371 Application: MET/CAL In V7.01 SP1, and prior versions, when MET/CAL performs a read operation to fetch a single data message which exceeds 4096 bytes, the read may fail because MET/CAL readdresses the sending instrument prior to each part of the read operation. This failure has been observed in testing a Wavetek 195. The data message returned by the 195 should be 8047 bytes. However, since MET/CAL buffers the I/O using a 4096-byte buffer, reading 8047 bytes requires two separate read operations. The first read retrieves 4096 bytes. The second read retrieves 3950 bytes, but should retrieve 3951. This issue affects only input operations done using the IEEE, IEEE2, and SCPI FSCs, and only when the data message read from the instrument is directed to a file. (This is because it is not possible to read more than 4096 bytes when the data message is not directed to a file, because the MEM2 string register is limited to 4096 bytes.) It's not clear whether the behavior of the Wavetek 195 is typical in this respect. It apparently discards a byte when it is readdressed before the complete data message has been read. Here's an example of a procedure which demonstrates the problem: Fluke Corp. MET/CAL Procedure =============================================================== INSTRUMENT: 195 learn crash DATE: January 30, 2004 AUTHOR: Fluke Corp. REVISION: ADJUSTMENT THRESHOLD: 70% NUMBER OF TESTS: 1 NUMBER OF LINES: 18 =============================================================== STEP FSC RANGE NOMINAL TOLERANCE MOD1 MOD2 3 4 CON 1.001 DISP pause 1.002 IEEE *LRN?[I > 195_LRN.txt] 1.003 DISP Use front panel to reset the 195... 1.004 IEEE [O < 195_LRN.txt] 1.005 DISP pause at end of procedure In V7.01 SP2 MET/CAL has been changed so that it does not readdress the sending instrument on the second and subsequent read operations required to retrieve a single data message. ----> MET/TRACK Handles Subreport Parameter Fields Incorrectly Report Number: 23358 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions, parameter fields in subreports are not handled correctly. To demonstrate the problem create a subreport that uses "Asset_ctag" as a parameter field, and print all cal certificates for a customer between two specified dates. V7.01 SP2 corrects this problem. ----> "Sdefaults" Set On Updated Databases Report Number: 23234 Application: DBUpdate In MET/CAL V5 and V6 updated databases may have update/edit ("sdefaults") set. In MET/CAL V7 the MET/TRACK administator has no way to disable these defaults. This situation can leads to errors (e.g., "Error 380"). The problem has been corrected in V7.01 SP2. An updated copy of "patch1.sql" is included in the service pack. To apply the patch install "patch1.sql" in the proper directory, then run "dbupdate.exe". ----> 8902 and 8903 FSCs Incorrectly Use "D" (dBm) for Audio Distortion Units Report Number: 22983 Application: MET/CAL In V7.01 SP1, and earlier versions, the 8902 and 8903 FSCs use "D" as the units code for Audio Distortion. This is incorrect because "D" is the MET/CAL units code for dBm. dBm represents an absolute power magnitude, not a ratio. Therefore the correct units symbol is "dB". V7.01 SP2 corrects the problem by allowing "dB" as the audio distortion units. For backward compatibility the 8902 and 8903 FSCs will continue to allow "D" as well. ----> Date Recalculated Incorrectly in MET/TRACK Edit Calibration Screen Report Number: 22914 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior versions, dates are re-calculated incorrectly in the Edit Calibration screen in some cases. The sequence of steps required to cause the problem to occur is: (1) Start MET/TRACK. (2) Choose "Add" : "Calibration". (3) Tab through the due date and due time fields. (4) Enter all required data. (5) Change the calibration interval. (6) Save the record. (7) Reopen the record just created in edit mode. (8) Tab through the due date field. At this point an incorrect due date will be shown. V7.01 SP2 corrects the problem. ----> Import Reports Successful Import of Cal History for Non-Existent Asset Report Number: 22674 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier versions, when using the built-in Import function, if you use an external text file and mark fields for import as calibration histories before importing (or manually entering) the inventory data, the import function reports " records sucessfully imported", but, actually, no records have been imported. V7.01 SP2 corrects this problem. ----> Cal Histories Can Be Deleted for an In-Use Standard Report Number: 22650 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions, a normal user is allowed to delete calibration records for an asset used as a standard. It should not be possible to delete calibration records for a standard, because doing so destroys the traceability chain. V7.01 SP2 corrects this problem. ----> 5520 FSC Accuracy Look-Up Incorrect When Nominal is Volts and MOD3 is TC Report Number: 22591 Application: MET/CAL In MET/CAL V7.01 SP1 and prior, when specifying volts in the NOMINAL field and "TC" in MOD3 of a 5520 statement, MET/CAL derives its accuracy from the 320 mV DC voltage range. This is likely because, originally, the TC output was specified identically to the NORMAL output when sourcing DC voltage. For some unknown length of time, however, the TC Simulate output has been specified differently, making the accuracy look-up in MET/CAL incorrect. V7.01 SP2 corrects the problem. The 5520 FSC now generates the mode string "Volts TC" when 5520 FSC Nominal units are volts and MOD3 = "TC". A new mode block has been added to 5520 accuracy files. For the 5520A the "Volts TC" accuracy now agrees with the specifications in the current 5520A Operators Manual PN 688739, August 1998 Rev. 6, 1/03. For the 5500A the "Volts TC" accuracy is identical to the 330 mV DC range specifications. However, because the accuracy file look-up used by MET/CAL is shared between the 5500 and 5520 FSCs, the mode string change described above applies to the 5500 FSC as well. V7.01 SP2 therefore includes updated 5500 accuracy files as well. ----> Quotes Not Allowed in Import Source Files Report Number: 21964 Application: MET/TRACK MET/TRACK V7.01 SP1 does not handle quotes correctly in import source files. (This report refers to the built-in data importation tool in MET/TRACK, not to the external Import Tool.) V7.01 SP2 corrects the problem. ----> Global Change Dialog Box Shows Only 21 Characters Report Number: 21864 Application: MET/TRACK In V7.01 SP1 and earlier the calibration description field in MET/TRACK's global change dialog shows only the first 21 characters of the description. This makes it difficult to select the proper record when two or more records have descriptions which are the same out to at least the first 21 characters. V7.01 SP2 includes a version of MET/TRACK which corrects this problem. ----> Incorrect Ohms CW Floor Values in Fluke 5720A 180-Day, 95% Accuracy File Report Number: 21601 Application: MET/CAL In V7.01 SP1 and prior the "Ohms CW" floor values in the Fluke 5720A 180-day, 95% accuracy file are incorrect. The incorrect values are 1.00E+00, 1.00E+00, 5.00E+00, 1.00+e01. They should be 10E-3, 10E-3, 50E-3, and 100E-3. V7.01 SP2 includes an updated accuracy file which corrects the problem. ----> Date Fields Not Updated When Date Value Already Exists Report Number: 21479 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior versions, if a date field (such as 4212) is set to "current date" (for both initial and update), the field will not be updated to the current date when a record which already has a date value in the field is changed. MET/TRACK V6 worked differently in this regard, and a number of customers have requested that the V6 behavior be restored. This problem has been addressed in V7.01 SP2. ----> Field 2311 (Temperature) Generates Error 380 with German Regional Settings Report Number: 21227 Application: MET/TRACK In MET/TRACK V7.01 SP1, and earlier V7 versions of MET/TRACK, a problem occurs when the default value for a numeric field uses a decimal symbol different from the decimal symbol indicated by the regional setting of the PC. For example, if customization is set up to use "23.5" as the default value for Calibration Table field 2311 (temperature), but the regional setting on the PC is "German Standard" (which makes the decimal symbol a comma), then an "Error 380" error message is generated when a new calibration record is created. This problem applies to the following numeric fields: Calibration Table: C2309, C2310, C2311, C2312, C2315, C2317, C2324, C2328, C2375, C2376, C2377, C2378, C2386, C2387, C2388, C2389, C2390, C2391, C2392 Inventory Table: I4219, I4254, I4255, I4256, I4257 Customer Table: K4625, K4626, K4627, K4628 Location Table: L2818, L2819, L2820, L2821 Repair Table: R3209, R3212, R3215, R3218, R3221, R3224, R3227, R3229, R3231, R3232, R3235, R3239, R3252, R3265, R3266, R3267, R3268, R3269 V7.01 SP2 corrects this problem. ----> New Linked Validation Data Cannot Be Used w/o 1st Exiting from the Form Report Number: 20636 Application: MET/TRACK In V7.01 SP1, and earlier V7 versions, when new new data are entered into the linked validation table, one must first leave the form where the new validation data were created before being able able to use them for the record. To demonstrate this problem add a user-defined field that includes validation, then login as a normal user with permission to enter data. Go to the user-defined field and type F7 to edit validation. Add new validation entries, and save them. Notice that when you return to the Inventory Form the new validation entries are not on the list. However, if you first close, then re-open, the form you will see the new entries. V7.01 SP2 corrects this problem. ----> Numeric Fields Not Validated By MET/TRACK Report Number: 20337 Application: MET/TRACK In MET/TRACK V7.01 SP1, and prior V7 versions, when the "Interval" is set up for validation in the inventory form there is no validation when entering the interval for a new asset. The same problem is present for other numeric fields in the Inventory Table. V7.01 SP2 corrects the problem. Now, when a numeric field is set up as a validated field, MET/TRACK correctly restricts the entered value to a valid value when the information for a new asset is being entered. ----> 4800 99% 1-Year Accuracy File Has Non-Contiguous Frequency Band for 1000V Range Report Number: 14968 Application: MET/CAL In V7.01 SP1 and prior there's an error in the 1000V range section of the Datron 4800 99% 1-year accuracy file. In the accuracy file lines: 90.000 1100.000 10 330 250e-4 60e-3 1e-3 90.000 1100.000 3e3 10e3 210e-4 40e-3 1e-3 there is a gap between 330 Hz and 3000 Hz which is not represented. The error causes an accuracy lookup error for procedure statements like: 4800 1000V 1% 1kH 2W The problem has been corrected in V7.01 SP2. The service pack includes an updated accuracy file ("4800_99.1yr"). ------------------------------------------------------------------------------- Section 12: V7.01 SP1 Problem Reports ---------------------------------------- ------------------------------------------------------------------------------- This section contains problem reports which describe all corrections made from V7.01 to V7.01 SP1. ----> 4950 ACV Measurement Causes Intermittent 4950 Error Report Number: 23411 Application: Run Time, Editor In V7.01 there's an intermittent problem related to SRQ handling in the 4950, 1271, 1281, and 8508 FSCs. The problem has been observed with the 4950 FSC only but, in principle, could also affect the 1271, 1281, and 8508 FSCs. When the problem occurs the error: E2071: Error Sending Command to 4950 is generated. Corrected in V7.01 SP1. ----> MET/TRACK Import Fails When Commas Inside Quotes Are Present Report Number: 23354 Application: MET/TRACK In V7.01 the Import Tool built into MET/TRACK does not work correctly if the comma-separated values include double-quoted items. For example: Asset #, Mfr , Model, Description , Serial # 123 , Fluke, 5520A, "Calibrator, Multifunction", 45678 will be imported with: Description as - "Calibrator Serial # as - Multifunction" Corrected in V7.01 SP1. ----> IEEE FSC Read From File, With Slow Construction, Should Not Readdress Instrument Report Number: 23327 Application: MET/CAL In V7.01 when the IEEE FSC "slow" construction ([S]) is used in conjunction with the [O < ] construction (read from file, write to current address), MET/CAL readdresses the IEEE-488 instrument being written to when the first byte of each buffer is written. Output using the [O < ] construction is buffered, with a 256 byte buffer size. For binary transfers, the IEEE-488 instrument should not be re-addressed when the first byte of the second and subsequent buffers is sent. Thus, for example, writing an 8046 byte buffer to the Wavetek 195 fails because when the first byte of the 2nd 256-byte buffer is written MET/CAL readdresses the 195 which interrupts the binary data transfer in a manner which the 195 does not accept: Instrument: Test 1.001 DISP Pause... 1.002 IEEE [TERM NONE]*LRN?[I > 195_LRN.txt] 1.003 DISP Reset Wavetek 195... 1.004 IEEE [S5][O < 195_LRN_A.txt] The error generated when the transfer fails is E_NI_EARG (#2744). Situations which generate this error condition are uncommon because it is unusual to use the [O < ] in conjunction with the [S] construction. Corrected in V7.01 SP1. ----> Accuracy File Interval For Marconi 2024 RF Signal Generator Is Incorrect Report Number: 23264 Application: MET/CAL The V7.01 accuracy file for the Marconi 2024 RF Signal Generator has a 90 day interval. According to the manufacturer the correct interval is 2 years. The updated accuracy file is not included in V7.01 SP1. The file may be downloaded from the MET/CAL website. ----> Interval Incorrect in 8648A/B/C/D Accuracy File ("8648.acc") Report Number: 23217 Application: MET/CAL The 8648A/B/C/D Signal Generator specifications are 2 year, not 90 day as stated in the V7.01 8648 accuracy file ("8648.acc"). The interval has been changed to 730 days in "8648.acc". The updated accuracy file is not included in V7.01 SP1. The file may be downloaded from the MET/CAL website. ----> Calibration Add Screen Closes After Save, Not Allowing Results To Be Entered Report Number: 23194 Application: MET/TRACK In V7.01 the MET/TRACK "Add Calibration" screen closes when you save the calibration summary data, but you must save the cal summary data before you can add the cal results data. This means that a level 3 user cannot add any results to a calibration (because a level 3 user cannot edit calibrations). Corrected in V7.01 SP1. ----> L2809 May Be Marked "Not Required", But Remains Always Required Report Number: 23192 Application: MET/TRACK L2809 is able to be marked "not required", but it is always required. L2809 is part of what makes up the LTAG and, by definition, must be present with the current date. Currently, users can make this field NOT REQUIRED. In V7.01 this is an issue in the respect that it will not allow you to save the location record if the value is not populated. It gives you a warning, then closes, but does not save. It is the same with field L2810. L2809 is the date field and L2810 is the time field that makes up part of the LTAG. The defect has been resolved. Now the fields L2809 and L2810 are required when added to the form. When the fields are removed from the form the default values are set to the current date and current time, respectively. Corrected in V7.01 SP1. ----> HP RF Product Default Accuracy Files Have Incorrect Interval Report Number: 23063 Application: MET/CAL In V7.01 default accuracy files for the following HP/Agilent instruments have 90 day cal intervals specified. They should be 1 year. 8560 FSC: 8560A, 8562A, 8563A, 8561B, 8562B, and 8560 E-Series Spectrum Analyzers 8566 FSC: 8566B Spectrum Analyzer 8568 FSC: 8568B Spectrum Analyzer 8590 FSC: 8590L, 8591E, 8592L, 8563E, 8564E, 8565E, and 8596E Spectrum Analyzers 8901 FSC: 8901A and 8901B Modulation Analyzers 8902 FSC: 8902A Measuring Receiver and 8902S Microwave Measurement System 8903 FSC: 8903B Audio Analyzer and 8903E Distortion Analyzer Except for "9500.acc", V7.01 SP1 does not include updated accuracy files. The latest accuracy files may be downloaded from the MET/CAL website. ----> Config Editor Doesn't Allow 5720A To Be Configured With 5725A And 5220A Report Number: 23058 Application: MET/CAL A customer would like the Instrument Configuration Editor to support configuring the 5720A with a 5725A and a 5220A. In V7.01 the procedure and the System Configuration File ("config.dat") both support this, but the Instrument Configuration Editor does not. This affects the 5700A as well. Corrected in V7.01 SP1. ----> Problem Running Procedure With Selection By Asset Number Report Number: 23014 Application: Run Time Using V7.01, two customers report problems executing procedures using the Run Time application when the procedure selection method is "By Asset". Information attached to the problem report indicates that the error is a low-level crash (page fault in "KERNEL32.DLL"). The crash apparently occurs immediately after entering the asset number in response to the prompt displayed by the Run Time application. The customer states also that when the Run Time is launched from MET/TRACK (using "Calibrate" : "Asset with MET/CAL Run Time...") the problem does not occur. The problem appears only when the Run Time is using procedure selection by asset, and only when MET/TRACK has prepended an invalid prefix (i.e., "MET/CAL: ") to the beginning of the procedure name. The problem does not appear when MET/CAL is invoked from MET/TRACK because, in that mode, MET/TRACK strips off the prefix before invoking the MET/CAL Run Time. The problem may be intermittent. It depends on the memory layout of the particular PC when the application is invoked. Corrected in V7.01 SP1. ----> VSET WS = NO and VSET WS = 0 Do Not Work Within Procedure Report Number: 23002 Application: Editor In V7.01 the VSET FSC does not allow the Welch-Satterthwaite flag ("WS") to be turned off. A work-around is to leave "WS" unset in the MET/CAL initialization file, and use "VSET WS = *" in the procedure. This will cause WS to revert to the default, which is "NO". Corrected in V7.01 SP1. It is now possible to specify: VSET WS = No or, equivalently: VSET WS = 0 ----> Print Button In User Table Window Covered Up When Active Window Border >> 1 Report Number: 23001 Application: MET/TRACK In V7.01 the height of the grid in the "usergrid" form should be adjusted because, in some cases, it overlaps the print button at the bottom of the screen. To bring up the window referred to: (1) Choose "Tools" in the top-level MET/TRACK menu. (2) Choose "Edit User Tables" in the dropdown menu. (3) Choose any of the user tables. Note: You must have previously created at least one user table in order to be able to do this. (4) Resize the table as needed to make it narrower so that the horizontal scroll bar at the bottom of the table appears. Note: There's a minimum width, so you may have to add fields to the user table to be able to force the scroll bar to appear. It looks like you need at least about 4 fields in the user table. This problem is manifested only when the "Active Window Border" setting under "Display Properties" in the Control Panel is significantly larger than one. If you set the active window border to 15, for example, most of the "Print" button is covered up. MET/TRACK should be changed so that the grid height is calculated in such a way as to take into account the active window border. Corrected in V7.01 SP1. ----> MET/TRACK "Search Engine..." Field Title Background Color Incorrect Report Number: 23000 Application: MET/TRACK In V7.01 the label background color on the search screen is incorrect. The problem is that the MET/TRACK sets the background color for the field labels to be the color selected under the "Menu" setting in the "Display Properties" dialog in the Control Panel. The correct setting is "Button Face". Corrected in V7.01 SP1. ----> Run Time Unable to Prompt for Calibration Table Fields 2386 to 2396 Report Number: 22997 Application: Run Time In V7.01 the Run Time application does not allow Calibration Table fields greater than 2384 to be prompted for. (2384 used to be the maximum field number in the Calibration Table, and the Run Time was not updated when the Calibration Table was expanded.) Excluding 2385 ("OLE Doc"), the Run Time should allow Calibration Table fields 2386 to 2396 (inclusive) to be prompted for (via "promptdb.txt"). Corrected in V7.01 SP1. The Run Time application has been updated to allow fields from 2386 to 2396 in the Calibration Table to be prompted for in the Run Time pre- and/or post-run prompt screens. However, due to a separate problem, it remains not possible to prompt for 2393 and 2394. (This problem has been reported in a separate report.) ----> Default IEEE-488 Address Incorrect for 34401A in Instrument Configuration Report Number: 22984 Application: Config Editor The default IEEE-488 address for the Agilent/HP 34401A in the instrument configuration utility should be 22 not 21. Corrected in V7.01 SP1. ----> When Units Are Ohms Some Result Table Quantities Have "Ohms" Instead of "Ohm" Report Number: 22972 Application: Run Time Since the Windows character set does not include a character for the Greek letter omega, it's not possible to store the correct SI symbol for ohms in the database Results Table. MET/CAL therefore uses "Ohm" as a stand-in for the omega. In V7.01 the problem is that some result quantities incorrectly use "Ohms" instead of "Ohm" as the units symbol. This inconsistency occurs with Cardinal Point, UUT Resolution, and Test Description (unless directly specified using VSET). MET/CAL should be changed to store "Ohm" instead of "Ohms" in the Results Table units field for these result quantities. Corrected in V7.01 SP1. ----> Maintenance Type (Field R3251) Default Value Does Not Work (Build #298) Report Number: 22928 Application: MET/TRACK In V7.01, in MET/TRACK build #298, on the Maintenance/Repair data entry form, the Maintenance Type R3251 field default value no longer works. You can select the value by hand. Corrected in V7.01 SP1. ----> Problem Editing Maintenance Records When More Than 500 Records Present Report Number: 22910 Application: MET/TRACK In V7.01, when editing an asset that has more than 500 maintenance records, the following error may be generated: error number 9: subscript out of range Corrected in V7.01 SP1. ----> RESET FSC Disallows Non-Address Construction at Beginning of Statement Report Number: 22898 Application: Editor In V7.01, the RESET FSC supports special constructions like [Dxxx], [SDC], & [GTL] however they are not allowed at the beginning of the RESET FSC command string. Example: 1.001 RESET *RST[SDC][GTL] is accepted by the compiler, however 1.001 RESET [SDC]*RST[GTL] is not. Corrected in V7.01 SP1. Prior to the change the compiler enforced the rule that if the statement began with a special construction, it had to be an address construction. The design has now been changed to allow other constructions at the beginning as well. However, if an address construction is specified in the statement, it has to be at the beginning, and there can't be more than one. The presence or absence of the address construction is still used to distinguish between RESET statements intended to reset a user- configured system instrument and RESET statements intended to reset the UUT. ----> M8902 Nominal field Limits Incorrect for 8902S Lo Frequency Report Number: 22873 Application: MET/CAL In V7.01 the M8902 FSC will not allow all legal values for the 8902S Local Oscillator frequency. Corrected in V7.01 SP1. ----> 8508 FSC Reset Function Should Send SDC Report Number: 22869 Application: MET/CAL In V7.01, if a measurement in progress is interrupted by the operator, using the Run Time "Break" menu item or the Editor Test Run "Stop" button, the instrument is left in a state such that a subsequent attempt to communicate with the instrument will result in an IEEE-488 timeout. This applies to the 1281, 1271, and 4950 as well. Corrected in V7.01 SP1. ----> 9100 & 9500 FSC Near and Past Due Cal Warnings Not Functioning As Designed Report Number: 22821 Application: MET/CAL In V7.01 when using the MET/CAL "9100" and "9500" FSCs, the "Near Cal Due" and "Past Cal Due" service requests generated by the 9100 and 9500 instruments are intended to cause a once-per-procedure operator prompt giving the operator the choice of either aborting the procedure or ignoring the warning an continuing. However, due to a bug in the implementation, these service requests cause the FSC (driver) to generate a step-terminating error each time they occur. Corrected in V7.01 SP1. ----> Problem Entering New Assets with MET/TRACK (Build #301) Report Number: 22820 Application: MET/TRACK The Fluke service center reports that, in some cases, when creating a new asset, after entering the new number, the inventory form appears with no asset in field 4201. The record cannot be saved. The problem appears to be related to configuring 4201 as the last item in the tab order. This problem appears in builds 300 and 301, but is not present in earlier versions. This problem was not present in the last official MET/TRACK release (V7.01). Corrected in V7.01 SP1. ----> 8902S Tuned RF Level Measurement Fails at Low Amplitudes Report Number: 22769 Application: MET/CAL In V7.01 there are problems using the M8902 and 8902 FSCs when using the down converter below -90 dBm (8902S). A "No input detected" error will be generated in some cases. Corrected in V7.01 SP1. ----> I4219 Not Shown Correctly When It Is A Whole Number Report Number: 22687 Application: MET/TRACK In V7.01, if the field I4219 has a value that is a whole number (e.g., 35.00, 42.00, 2.00, ...) the two decimal places to the right do not appear on the browse screen. On the edit screen they are shown correctly. Corrected in V7.01 SP1. ----> Currency Symbol Does Not Show Up In Field 4219 In Browse Screen Report Number: 22685 Application: MET/TRACK In V7.01, the currency symbol does not show up in field 4219 in the MET/TRACK Browse Screen. In the edit screen the currency symbol is shown correctly. Corrected in V7.01 SP1. ----> Source Copy Status Not Displayed On Inventory Form Report Number: 22630 Application: MET/TRACK In V7.01 MET/TRACK the source copy status is not shown on the Inventory Form. Corrected in V7.01 SP1. ----> 8902 FSC Problem - 75 us Sent Instead of 750 us in FM De-Emphasis Mode Report Number: 22629 Application: MET/CAL In V7.01 when the M8902 FSC is used to set up 750 microsecond FM de-emphasis, the MET/CAL 8902 driver incorrectly sets up 75 microsecond FM de-emphasis. Corrected in V7.01 SP1. ----> Copy Forward from Inventory to Location Does Not Work Report Number: 22597 Application: MET/TRACK In V7.01, copy forward from Inventory to Location does not work. This is a legal customization and should work. A customer reported that he would like the asset number and serial number fields to be copied forward from the Inventory form to the Location form. It has been confirmed that this does not work in MET/TRACK builds 295 and 297. Corrected in V7.01 SP1. ----> Source Copy Does Not Work for Fields Report Number: 22596 Application: MET/TRACK In V7.01, customizing a field so that Source Copy is set to "On" does not function correctly. This situation arises when a user sets up a form to initialize a field value based on the value entered for the same field in the previous record. To duplicate the problem: 1. Login as MT. 2. Choose Lay-Out->Entry Screens->Calibration Screen 3. Restore field C2341 4. Set Source Copy to ON. 5. Close the field property form and the customization form. 6. Re-login as a level 4, or higher, user. 7. Add a new calibration record and enter a string value into field C2341. 8. Save the record. 9. Add another calibration record for the same asset. 10. Observe that field C2341 is initially empty. Corrected in V7.01 SP1. ----> Maintenance Records Cannot Be Deleted From Search Screen Report Number: 22551 Application: MET/TRACK To demonstrate the problem: Search for an Asset that has a Maintenance Record. Create one if necessary. Select the Maintenance tab. Click on the 'X' to delete the record. Resolved in V7.01 SP1. The "X" Button has been removed from the Maintenance and Location Tabs of Instrument Browser screen. ----> 8568/M8568 Statements Cause IEEE-488 Timeout Report Number: 22535 Application: Run Time In V7.01 executing the following procedure statements results in a IEEE-488 timeout: 1.001 ASK- N V 1.002 DISP Connect 8568B CAL OUTPUT to 8568B SIGNAL INPUT 2. 1.003 M8568 SPAN 450H 1.004 M8568 30T -10D 1.005 8568 100.000000MH -10D I2 N E2746: IEEE-488: (NI EABO) Timeout. I/O operation aborted. The problem is that the 856x driver was sending a semicolon after the take sweep ("TS") command. This caused the IEEE-488 timeout due to the following (from HP 8568B Programming Manual): "When the analyzer receives a TS command, it is not ready to receive any more data via HP-IB until one full sweep had been completed." Thus, receipt of the semicolon was being held off until the TS command was completed. Corrected in V7.01 SP1. ----> 8568 FSC Automatic Connection Message Incorrect When MOD2 is "I2" Report Number: 22519 Application: Run Time In V7.01, if an 8568 FSC MOD2 field is "I2" the automatic connection message is incorrect. Corrected in V7.01 SP1. ----> Pressing F7 in Inventory Screen Causes Internal Error "subscript out of range" Report Number: 22481 Application: MET/TRACK To demonstrate the problem using MET/TRACK V7.01 follow these steps: 1. Press F2 "Add->Inventory Record" 2. Enter an Asset Number 3. Enter data for all required fields 4. Save Record 5. Press F7 At this point an internal error message is displayed. Corrected in V7.01 SP1. ----> 6680 and 6681 FSCs May Not Operate Correctly in V7.00 and V7.01 Report Number: 22447 Application: MET/CAL The problem was introduced when a design change was made for the V7.00 release in the 6680/6681 FSC. The problem was not consistently present in V7.00. There may have been a firmware dependency, but we were unable to determine precisely when the problem would occur. The Pendulum engineers (designers of the 6680 and 6681) looked at the commands the MET/CAL V7.00 driver was sending to the instrument, and agreed that the commands were valid. Nevertheless, it was determined that the problem could be alleviated by changing the MET/CAL driver so that it did not send an SDC (Selected Device Clear) to the instrument after a non-error SRQ. Even though it should have worked, it was superfluous. Corrected in V7.01 SP1. (All Run Time and Editor versions V7.01f or later correct this problem.) ----> Field 2341 Generates An Error If Validated Report Number: 22446, 22442 Application: MET/TRACK In Version 7.01, if you edit field 2341 property to 'Req Val' or 'Picklist' you will be able to refresh, edit and save the validation data as the MT user. However, if you try to 'Refresh and save' or 'edit and save' the validation data as a normal fluke user, e.g., level 5, it is not possible to save the validation data. The error message is: Items in the validation list exceed the maximum allowable length in customization. Corrected in V7.01 SP1. ----> Not Able To Enter Special German Characters into C2341 Report Number: 22443 Application: MET/TRACK In V7.01, when entering data into C2341 (Comment Field) with PICKLIST enabled, it is not possible to enter German characters like 'äöüß' directly into the field. Only standard ASCII characters are displayed correctly. Editing the PickList/Validation List (F7) is possible; here German characters are accepted, but still you can't save it as normal user. Corrected in V7.01 SP1. ----> Restoring and Moving a Field in the Search Form Causes an Error Report Number: 22414 Application: MET/TRACK In MET/TRACK V7.01 an error will occur if you first restore, then move, a field on the Search Form. Follow these steps to demonstrate the problem: 1. Login as MT 2. Choose Layout->Search Engine Screen 3. Click on the restore button 4. Select a field to restore 5. Select the restored field move it 6. This error will now appear: ... 340 Control array element does not exist ... Corrected in V7.01 SP1. ----> Error in 1271/1281 Accuracy Files Report Number: 22351 Application: MET/CAL As reported by a MET/CAL user: I've just been writing a procedure using the Datron 1281 and have come across a bit of a problem with the 1271/1281 accuracy files dated 11/09/2001. The Tolerance values for Frequency with 'FAST OFF' are currently 0.01. I believe these should be 0.001. Here's the relevant section of "1281.acc": Mode: Hertz # Nominal MOD1 Tolerance Floor Res. # --------------------- ----------- --------- -------- -------- 10.00000 19.99999 2E-06 1100 0.01 20e-6 10e-6 20.0000 199.9999 2E-06 1100 0.01 200e-6 100e-6 0.200000e3 1.999999e3 2E-06 1100 0.01 2e-03 1e-3 2.00000e3 19.99999e3 2E-06 1100 0.01 20e-3 10e-3 20.0000e3 199.9999e3 2E-06 1100 0.01 200e-3 100e-3 0.200000e6 1.000000e6 2E-06 1100 0.01 2 1 The same issue applies also to "1281_95.1yr", "1271.acc", "1271_95.1yr". Corrected versions of the accuracy files referred to above are available on the MET/CAL website. ----> Searching for Asset Number Containing Field Number (I42XX, C23XX, etc.) Fails Report Number: 22344 Application: MET/TRACK To demonstrate the problem: Create an asset # ML28X (where 'X' is any number). Create one or more location records for the same asset. Perform a search for 'ML28%'. Click on the location tab. A fatal error will now occur. Corrected in V7.01 SP1. ----> MET/TRACK Handling of Record Editing Conflicts Report Number: 22334 Application: MET/TRACK When two or more users open the same record for editing, MET/TRACK generates an Abnormal Termination error, causing MET/TRACK to terminate. V7.01 SP1 modifies this behavior. Now, when two or more people edit the same record at the same time, the last one to save changes prevails, but no Abnormal Termination error is generated. ----> Improper French Translation on Edit Maintenance window. Report Number: 22331 Application: MET/TRACK As reported by a customer: I used M/T V7.01 in French and when I click on the "Edit repair" icon, M/T opens a small window in which to enter the asset number. The title of the window is "Supprimer une Maintenance". It should be "Editer une maintenance". Corrected in V7.01 SP1. ----> Cannot Tab to the Interval field in the Calibration Screen Report Number: 22326 Application: MET/TRACK In V7.01 it is not possible to tab to the Interval field in the Calibration Screen. The tab order is set to allow it to be tabbed to, but the tab key skips over the field. Corrected in V7.01 SP1. ----> Forcecase = 1 Does Not Work for Some Fields Report Number: 22322 Application: MET/TRACK In V7.01 the "forcecase" initialization file parameter does not operate correctly in MET/TRACK for some fields. Corrected in V7.01 SP1. Note that, by design, there are some fields for which case is preserved regardless of the "forcecase" setting. For example, case is preserved in user-entered notes and remarks. ----> Report Does Not Print to Specified Printer Report Number: 22319 Application: MET/TRACK When a report is written to print to a specified printer, it works within Crystal, but does not work in MET/TRACK. Corrected in V7.01 SP1. ----> Print Command When No Physical Printer Present Causes Crash Report Number: 22307 Application: MET/TRACK To demonstrate the problem: Go to MET/TRACK search engine and find a particular Asset. Now try to print that record. Have the Printer Driver configured without a physical printer. Windows crashes. Corrected in V7.01 SP1. You will now receive an error message. ----> Run Time Prompted-For C2324 Value Overwritten by METGENDB.DLL Report Number: 22300 Application: MET/TRACK In V6.11A and prior one could include a specification like: Time to Calibrate UUT :: ELAPSED_TIME_HR$ 2324 or Time to Calibrate UUT :: ELAPSED_TIME_MIN$ 2324 in one or both of the post-run prompt files (i.e., the pass and fail prompt files). This would cause the elapsed time calculated by the MET/CAL Run Time application to be automatically written to field 2324 in the database Calibration Table. The user could optionally override the calculated elapsed time by simply entering a different value, and the user-entered value would then be written to field 2324. In V7.00 and V7.01, the user override capability no longer functions correctly. The user-entered value is ignored, and the interface DLL "metgendb.dll" simply always re-calculates the elapsed time. Corrected in V7.01 SP1. ----> Maintenance Edit from Search Screen Allows Only Current Record to be Edited Report Number: 22293 Application: MET/TRACK This was happening since the global variable which contains the record definition was not getting updated for every record Using V7.01, a customer reports that he is not able to edit maintenance records when performing a search using the "search engine". When he pulls up an asset record and then chooses the maintenance tab, if the arrow keys are used to move to an older record, and "Edit" is then selected, he always gets the most current record. Corrected in V7.01 SP1. ----> Dimensioned Uncertainty Results Have No Units When Units Are Non-Standard Report Number: 22290 Application: Run Time In V7.01 MET/CAL recognizes certain units symbols (like "V" for volts, etc.) The MEMC and MEMCX FSCs allow the procedure writer to specify any string as the units symbol. If the string happens to be a units symbol not recognized by MET/CAL, then units are blank for dimensioned, uncertainty-related result quantities the database Results Table. In an example reported by a customer, the units symbol was "LBS". This is not recognized by MET/CAL (because no instrument FSC supported by MET/CAL uses units of pounds). Changed in V7.01 SP1. Units not recognized by MET/CAL, but specified in MEMC or MEMCX statements, are now associated with uncertainty-related result quantities. ----> M5720 with C3 in CON Field Does Not Cause Procedure to Require a 5725A Report Number: 22155 Application: MET/CAL "MMFC C3" causes a 5725A to be required. However, "M5720 C3" does not. This allows a (somewhat obscure) problem to occur in a procedure which routes unboosted current out the 5725A output ports, and never uses any boosted current. The problem is that when the procedure is compiled the configuration lines at the top of the procedure do not list the 5725A as a required instrument. If, then, the procedure is executed and no 5725A is configured, a run time error will occur when the 5720 run time driver attempts to control the 5725A. The reason this issue doesn't arise often is that there's little reason to route unboosted current out the 5725A output ports, since it degrades accuracy without adding capability. The problem has been corrected. M5720 now works like MMFC in this regard. I.e., an M5720 statement with "C3" in the CON field will cause a 5725A to be a required instrument. It's not completely clear that this change is an improvement, because the 5725A will be required even if the procedure never routes unboosted current out the 5725A output ports. Moreover, the 5725A will be required even when the procedure requires a different boost amp (not the 5725A). However, after internal discussion, we concluded that 5720/M5720 should be consistent with 5700/MMFC. Furthermore, it can be argued that it's a procedure writing error to specify C3 in M5720 CON when you are using a boost amp other than the 5725A, or have no intention of routing unboosted current out the 5725A output ports. ----> 9100 Accuracy File Has Incorrect Floor for Mode: Volts SI AX, 3.2-7.5 range Report Number: 22152 Application: MET/CAL In V7.01 the 9100 accuracy file has an incorrect floor value for the Option 9100-PWR specification of voltage from the current terminals (Mode: Volts SI AX). The floor value is 400 uV, not 400 mV. An updated accuracy file is available on the MET/CAL website. ----> 8508 FSC Timing Problem After User Interrupts Procedure Using "Break" Report Number: 22095 Application: MET/CAL In V7.01 an IEEE-488 timeout problem may occur with the 8508 when the following sequence is loosely adhered to: 1) Start a MET/CAL procedures using the 8508. 2) When the 8508 is taking a reading, as indicated by "8508A taking a reading", press BREAK on the Run Time menu bar. 3) Press TERMINATE and terminate the executing procedure. 4) Start up any procedure that uses the 8508, you'll get an error message saying "8508 IEEE timeout...." The 8508 is in remote and sometimes can't be taken out of remote by pressing the LOCAL button. The only way to clear the 8508 is to turn it off and back on. Corrected in V7.01 SP1. A 0.5 s delay has been added after SDC is sent in the internal "clear" function. ----> Not Able to Set C2307 to Default "User's Login Name" Report Number: 22091 Application: MET/TRACK Problem with MET/TRACK V7.01 reported by user: I use field C2307 as the Cal-Tech and want to have it default to the logged-in users name. Using the field properties pop-up I have selected the default value as "User's Login Name". As long as the MET/TRACK application is open the information is retained on the layout screen, however when MET/TRACK is closed and then reopened the Default Value property for C2307 is blank and running MET/TRACK does not apply the default value as expected. Some additional notes: A work-around is to edit the Customiz_Me_2 table directly. Once the value is saved in the table it is retained. Even with the value saved in the table the layout tool field properties (default value) for C2307 is still blank. The behaver is the same with both pick-list validation and no validation on the field. Corrected in V7.01 SP1. ----> Russian Windows Causes Form Error Report Number: 22062 Application: MET/TRACK Problem reported by Fluke personnel in Europe: I have installed Met/Cal 7.01 on Russian Win2KSP1 and have found some problems. Logging into MET/TRACK as MT works correctly but, as a normal operator, adding a new asset (inventory record) you'll get the error: 380 Invalid property value FUNCTION/SUB: Table, CreateForm When you press Yes, you'll get: 5 Invalid procedure call or argument FUNCTION/SUB: Table, InsertRecord And then the Inventory Form is shown, but not all the fields are on the screen. Actually it stops after Acquisition date. Can it be something with the date setting (the Russian system setting is dd.MM.yyyy or d MMMM yyyy'r.')? Do you have any idea what is going wrong here? Corrected in V7.01 SP1. This problem was caused by a currency symbol which contains a '.'. In the case of the Russian Ruble, the displayed symbol will now be "RUR" and for all other symbols containing a "." will be replaced with a space. ----> Errors Controlling Pressure Modules Using P525 and P700 FSCs Report Number: 22053 Application: MET/CAL In V7.01 a number of timing-related problems have been reported using the P525 and P700 FSCs. Specifically, switching between voltage and pressure modes showed timing problems. Corrected in V7.01 SP1. Changes to MET/CAL have been made to work around the 525A firmware problems related to controlling the pressure modules. ----> Corrections and/or Additions to 9500 Accuracy File to Accommodate 9500B Specs Report Number: 22039 Application: MET/CAL V7.01 SP1 includes an updated accuracy file which correctly represents current 9500B specifications. The accuracy file is also available on the MET/CAL website. ----> Level 1, 2, or 3 Cannot Save Cal Records Without Standards Report Number: 22030 Application: MET/TRACK In V7.01 if the cal form is set up with limited permissions for levels 1, 2, or 3 where the user cannot access the Standards field (C2340) (field is not required), then, after filling out other fields and clicking on the save icon, the message is generated: "One or more standard must be entered and checked." However, the field is greyed out and it is not possible to enter the requested data.. Corrected in V7.01 SP1. Now users with levels 1, 2, or 3 are able enter new cal records and save them in the situation described above. ----> 6680/6681/6685 Vp and Vpp Statements Cause TUR Report Error Report Number: 22023 Application: MET/CAL In V7.01 a 6680, 6681, or 6685 FSC statement with PP (volts peak-to-peak) in the MOD3 field causes the following error when a TUR report is run: 1.001 6680 1Vp 1% 1kH MX #! T.U.R. calc. not implemented for FSC (no 'mode' string). 2.001 6680 1Vpp 1% 1kH PP #! T.U.R. calc. not implemented for FSC (no 'mode' string). Corrected in V7.01 SP1. ----> Cannot Use Run Time with Long Procedure Name Using MET/TRACK-Specified Name Report Number: 22018 Application: Run Time In V7.01 when MET/TRACK associates a procedure name with an asset, it should not include a prefix with the name, as if it is part of the name. MET/TRACK uses the prefixes "MET/CAL: " and "External: ", however these prefixes are not part of the procedure name. The proper solution for this problem would be to correct the problem in MET/TRACK. A change to MET/CAL has already been made (previously) to provide an interim work-around for this problem. This change appeared first in V7.00d, and was available in V7.00 SP4. The interim solution involved stripping off the illegal prefix, if present, before attempting to open the procedure. Unfortunately, this work-around did not address the case where the procedure name, plus the illegal prefix, were, taken together, longer than the maximum legal procedure name. Corrected in V7.01 SP1. A modification to the interim solution has been made to allow the string passed from MET/TRACK to MET/CAL to be as long as needed, including the prefix. The change appeared first in Run Time V7.01e. ----> Validation for Field 4229 Does Not Appear on Data Entry Form Report Number: 22010 Application: MET/TRACK In V7.01 if field 4229 is set up as a validated field the select arrow does not appear on the data entry form when logged in as a normal user. It appears correctly when logged in as "MT". Corrected in V7.01 SP1. ----> Dropdown List Not Present on Pre/Post Run Prompt if Pick List on Field Report Number: 21981 Application: Run Time Problem in V7.00 SP4 reported by a MET/CAL user: I confirmed that if a field in a pre- or post-run prompt is set up as a pick list, the dropdown arrow is missing and it will accept typed in data. If the same field is set up as a simple validation the dropdown arrow is present and it works as expected. Corrected in V7.01 SP1. ----> Sensitivity Coefficient C2 Calculated as Zero/Zero when S1 and S2 are Both Zero Report Number: 21956 Application: MET/CAL In V7.01 in some situations MET/CAL calculates sensitivity coefficient C2 as: C2 = sqrt((cS1 * CS1 * S1 * S1 + cS2 * cS2 * S2 * S2) / (S1 * S1 + S2 * S2)); Notice that if S1 and S2 are both zero, this formula becomes: C2 = sqrt(0/0) This results in C2 being set to a special value indicating "indeterminate", per the IEEE floating-point standard. When C2 is indeterminate, subsequent calculations which use C2 will also result in indeterminate values. S1 is usually calculated as: S1 = (standard deviation) / (sqrt(NMEAS)) so S1 will be zero if the standard deviation is zero. S2 is, by default, calculated as: S2 = (UUT_RES * 0.5) / (3 ^ 0.5) so, by default, S2 will be zero only if the UUT resolution is zero. (This is not a typical or realistic case, because a UUT resolution of zero implies an infinitely accurate UUT.) Although this problem should be unlikely in V7, because there's no good reason to set S2 or UUT_RES to zero (and it's certainly not realistic), MET/CAL should be updated to preclude this zero/zero division from happening. One easy work-around, useful before the code is updated to prevent the problem, is to directly set C2 to 1 in the procedure. This overrides the calculation of C2 and thus precludes the 0/0 division. Other work-arounds are to set U2M to "SINGLE" and to directly assign a value to U2. Also note that this problem can occur only when Welch-Satterthwaite is enabled (WS = YES). Corrected in V7.01 SP1. The MET/CAL measurement uncertainty module has been modified so that in cases where S1 and S2 are both zero, and where it is necessary to calculate the value of C2, the default value (1.0) is now used for C2, rather than the normal calculation: C2 = SQRT((CS1 * CS1 * S1 * S1 + CS2 * CS2 * S2 * S2) / (S1 * S1 + S2 * S2)) ----> Users Cannot Edit Validation Report Number: 21942 Application: MET/TRACK In V7.01 if a validation file is created by the administrator (MT) on a field (e.g. 4231, 32 characters) with only 5 characters entered then, when a user attempts to edit the list and save, the message "Items in the validation list exceed the maximum allowable length in customization" appears, and the changes cannot be saved. Corrected in V7.01 SP1. ----> Selecting a Printer Font Causes an Internal MET/TRACK Error Report Number: 21890 Application: MET/TRACK To duplicate the problem in V7.01: ( 1) Start MET/TRACK and login as the administrator. ( 2) Choose "Set-Up". ( 3) Choose "Desktops". ( 4) Enable the "Default" checkbox under "Allowed Desktops". ( 5) Choose the "Font" button under "Title". ( 6) Select any printer-type font. For example, "Helvetica-Narrow". (The printer-type fonts have a printer icon to the left in the font list shown under "Font:" in the "Font" window.) ( 7) Choose "OK". ( 8) Close the "Desktop..." window. ( 9) Choose "Set-Up". (10) Choose "Desktops". (11) You will now see an error message: The following internal error has occurred: 380 Invalid property value ... FUNCTION/SUB: frmDesktops, Form, Load This is not a fatal error because you can simply go back and select a non-printer-type font. The best solution will be to modify MET/TRACK so that the printer-type fonts do not appear in the list from which to select. (I'm assuming there's a good reason for not allowing printer-type fonts to be chosen. If there is not a good reason, then a different solution would be to fix the code to allow such a font to be selected without causing an internal error message to be generated.) An odd side-effect of this problem is that the "Desktops..." window will show two grayed-out buttons at the bottom: Restore Factory Settings to Selected Desk Clear All - Restore Factory Settings Corrected in V7.01 SP1. The printer fonts have neen removed from the application. ----> Search Screen with Two Or More Fields, Over a Network, Crashes Report Number: 21870 Application: MET/TRACK To demonstrate the problem in V7.01: 1) Configure a client/server system on a network. 2) Start MET/TRACK on the client machine. 3) Login as a normal user. 4) Choose "Search" on the top-level menu. 5) Click on the down arrow of the asset, and also choose one for the Pass/Fail field as quickly as possible (1 second or less) 6) This usually causes an error. Corrected in V7.01 SP1. ----> R4228 (Interval Units) Will Not Change to Default Value Report Number: 21800 Application: MET/TRACK In V7.01, on some systems, if you set the default value for R4228 (interval units) to 'N' and enter a new record, the default value shows up as 'M'. ----> 9100 Duty Function with M9100 Nominal Field in hertz has Incorrect Limits Report Number: 21747 Application: Editor In V7.01, attempting to compile the following statements 2.001 M9100 PER 110H 2.002 9100 98 98.0pct 0.5% 0.1U 15Vp PU 2W generates: E8856: FSC 9100: In % Duty mode, for voltage 15 Vp and offset 0 Voff, pulse width limits are 1e-005 s to 1.99999 s. Corrected in V7.01 SP1. Compile time limits checking has been corrected to support % duty mode with frequency in the M9100 NOMINAL field. ----> Calibration Table Field 2362 Limited to 2 Digits Report Number: 21707 Application: MET/TRACK In V7.01 Calibration Table field 2362 is limited to 2 digits. Corrected in V7.01 SP1. ----> Fields 2809 and 2810 are Set to "Required" and Cannot be Changed Report Number: 21700 Application: MET/TRACK In V6.11A and before, on the location form, L2809 and L2810 were shipped as required by default, but the customer had the option to make them non-required. In V7.01 you can no longer turn the requirement off. The required box is check and greyed out, so you cannot access it. Nor can you turn the requirement off by accessing the "me2_customiz" table in ISQL. This is a problem especially when customers want to import data. There is currently no work around except to populate these fields with a date and a time respectively. Corrected in V7.01 SP1. The required fields are now enabled and the MT user will have the option of determining whether the fields L2809 (Loan Date) and L2810 (Loan Time) are required or not. ----> When Copying a Procedure Created on 6.11A M437 MOD1 Changes State Report Number: 21687 Application: Editor Copy a procedure created using V6.11A that uses the M437 and 437 FSCs. Open it in the MET/CAL Editor and observe that MOD1 has been changed to NULL. Here's an example: Calibration Training MET/CAL Procedure =============================================================== INSTRUMENT: 437 DATE: 2003-06-10 AUTHOR: Real name for user "fluke". REVISION: ADJUSTMENT THRESHOLD: 70% NUMBER OF TESTS: 1 NUMBER OF LINES: 16 CONFIGURATION: HP 437B =============================================================== STEP FSC RANGE NOMINAL TOLERANCE MOD MOD2 3 4 CON 1.001 M437 pct (null) T5 1.002 DISP Connect sensor to 1mW/50MHz PWR REF Output 1.003 437 1mW 50MH CP N Corrected in V7.01 SP1. The problem introduced in V7.00 has been fixed. The problem was that the sensor codes in M437 MOD1 were renumbered. This affected compiled procedures. Compiled procedures with a sensor code in M437 MOD1, compiled with V6.11A and earlier, did not run or print correctly in V7.00 or V7.01. This has been corrected by supporting both old and new codes. V7.01a or later of Editor and Run Time is required to obtain this correction to the M437 FSC. ----> Incorrect MOD1 Description in 8903 FSC Help File Report Number: 21680 Application: MET/CAL From 8903 FSC help file as shipped with V7.01: MOD1 This field specifies the frequency. o Frequency entered as [][]H. o Distortion entered as: [][]pct or D. o Source Frequency entered as: [][]H. o not applicable Distortion has been removed from the list of legal MOD1 quantities. Contact MET/SUPPORT if you would like an updated 8903 help file prior to the next factory release of MET/CAL. ----> 9000/9100 ACI Nominal/ MOD1 Interfield Check Not Performed Report Number: 21660 Application: Editor In V7.01 the following statement does not generate an error: 9100 1A 1A S Corrected in V7.01 SP1. The missing compile time error check has been added. ----> 9000/9100 ACV Nominal/ MOD1 Interfield Check Not Performed Report Number: 21659 Application: Editor In V7.01 the following statement does not generate an error: 9100 1V 1V S Corrected in V7.01 SP1. The missing compile time error check has been added. ----> 9000/9100 ACI MOD1 Not Restricted to H, T, A, and Ap Report Number: 21658 Application: Editor From the 9100 help file: 9100 FSC NOMINAL, MOD1, MOD2, MOD3, and CON Rules 9100 9100 9100 9100 9100 9100 Mode (function) NOMINAL MOD1 MOD2 (1) MOD3 (2) CON (3) =============================================================== DC Voltage V 2W --------------------------------------------------------------- AC Voltage V|Vpp H|T SI|SQ|IP|TI|TZ 2W H|T V|Vpp SI|SQ|IP|TI|TZ 2W --------------------------------------------------------------- DC Current A 2W|T1|T5 --------------------------------------------------------------- AC Current A|App H|T SI|SQ|IP|TI|TZ 2W|T1|T5 H|T A|App SI|SQ|IP|TI|TZ 2W|T1|T5 Note that for AC Current, MOD1 can only be H, T, A, and App. However the following statement generates no error: 9100 1A 1V S Corrected in V7.01 SP1. The missing compile time error check has been added. ----> 9000/9100 FSCs Do Not Recognize "A" (autorange) As RANGE Field Entry Report Number: 21655 Application: Editor In V7.01 the 9000 and 9100 FSCs will not recognize "A" (autorange) as a RANGE field entry. For example, 9100 A 1V 1% Pressing F8 or F9 in the Editor compiles the line as: 2.001 9100 A 1% 1V SI 2W Also, entering the following line: 9100 A 390.0nF 2% 1.0U 4W causes: E2428: FSC 9100: Illegal units in MOD1 field. The correct behavior should be like the 5500 FSC: 1.001 5500 A 1V 1% 2W 2.001 5500 A 390.0nF 2% 1.0U 4W Corrected in V7.01 SP1. Initial field identification for the 9000 and 9100 FSCs has been modified to address this issue. ----> Field 4218 Truncated Report Number: 21642 Application: MET/TRACK In V7.01 the 4th character of field 4218 (Owning Dept.) is truncated. Corrected in V7.01 SP1. ----> MET/TRACK Search Screen Not Properly Displayed Report Number: 21632 Application: MET/TRACK In V7.01, for some customizations, the search screen is not properly displayed. Corrected in V7.01 SP1. ----> Extended Characters in Results Table Not Displayed Correctly in Japanese Windows Report Number: 21624 Application: Run Time MET/CAL V7.00 (and later) attempts to use extended characters where appropriate in units prefixes and units symbols. Specifically: "°C" represents degrees Celsius "°F" represents degrees Fahrenheit "°" represents degrees (phase, etc.) "g/cm²" represents grams per centimeter squared "µ" represents the units prefix for micro However, when the Japanese codepage is used, under Japanese Windows, the extended characters are not displayed correctly in MET/TRACK or in reports generated using Crystal Reports. Corrected in V7.01 SP1. The Run Time application has been modified to support a new initialization file parameter named "ExtendedUnits". Legal values are "yes", "no", "1", and "0". Values are case-insensitive. "yes" is equivalent to "1". "no" is equivalent to "0". The default value is "yes". Since the parameter is optional, omitting it from the initialization file ("metcal.ini") means that MET/CAL will continue to use extended characters in units prefixes and units symbols. If "ExtendedUnits = no" or "ExtendedUnits = 0" in the initialization file MET/CAL will use "deg" as the degrees symbol, "u" as the micro symbol, and "2" as the "power of 2" representation. Thus, within Japan, or any other locale where the codepage is such that these extended characters are not displayed correctly, users should make the appropriate specification in the initialization file to turn off the use of extended characters in this context. ----> The "Sort by:" List Box Font is Not Localized Report Number: 21622 Application: MET/TRACK Using V7.01, in Japanese Windows, in the search form the "Sort by:" list box is not localized. Corrected in V7.01 SP1. ----> The Field label "Find" on the Tool Bar in the MET/TRACK Main Window is Cut off Report Number: 21620 Application: MET/TRACK Under Japanese windows, the field labeled "Find" on the Tool Bar in the Main window is chopped off. Corrected in V7.01 SP1. ----> Error When Using F12 Key To Assign Customer Report Number: 21612 Application: MET/TRACK In V7.01 an error may occur when assigning an asset to a customer using the F12 function key. It remains possible to assign the asset by clicking on the "Customer" tab after looking up the asset, then clicking on the '+' sign. Corrected in V7.01 SP1. ----> MET/TRACK Customer Tab Not Updated Correctly Report Number: 21610 Application: MET/TRACK In V7.01, if you are looking at the "Customer" tab and then do a search for a different asset, the customer is not updated. You have to click another tab, then return to the "Customer" tab. Corrected in V7.01 SP1. ----> Customer Number Field Not Available When Assigning Customer Report Number: 21609 Application: MET/TRACK As reported by a customer: Under the Customer Assignment Window (F12) we have no way of viewing our customer number field. We use that same number between our accounting software and Fluke MET/CAL. It would be a tremendous help if we could add it to that screen. Corrected in V7.01 SP1. ----> Pressing Enter Twice Creates Error On Search Screen Report Number: 21608 Application: MET/TRACK In V7.01, when searching for an asset, if you hit twice, instead of once, there is an error: FUNCTION/SUB.frmDataBrowser, cmdNext, Click Corrected in V7.01 SP1. ----> Inventory/Calibration Record Editing Requires Re-searching for Asset After Save Report Number: 21605 Application: MET/TRACK In V7.01, after editing an Inventory Record or Calibration Record, you are dropped from the browser when you save. The program forces you to search again to get back to the asset(s) you are editing. Corrected in V7.01 SP1. The Search Engine Screen will now remain open... However, the user must manually refresh the screen to view the updated records ----> No Prompt for Required Fields at the End of Run Time Report Number: 21571 Application: MET/CAL In V7.01, if calibration fields are set to required with no default there is no prompt at the end of Run Time. A Sybase "232" error is displayed and "cannot commit". Results are lost. Corrected in V7.01 SP1. ----> MET/TRACK Status Line Can't Handle Courier New Report Number: 21453 Application: MET/TRACK For MET/TRACK V7.01, a reported by a customer: The font used for the (bottom) status line in the MET/TRACK application seems to depend on the desktop setting for the datafont. If a fixed font, e.g., "Courier New", is selected, the variable- sized fields of the status line are too small to hold the information, so the text is truncated. This will show up next time MET/TRACK is launched. Maybe you can change this to use the same font/fontsize as for the menu items? The report has been confirmed. When the data font for the default desktop is changed to Courier New one sees, for example: Source: calibrati (should be "calibration") User: nich (should be "nicholas") Level: (level number should be shown) Destop: def (should be "default") Corrected in V7.01 SP1. This was resolved by choosing a fixed font and point size for the status bar. ----> Standards "required" Causes Error at End of Run Time Report Number: 21451 Application: Run Time As reported by a customer: V5.X would allow field 2340 (Standards) to be set to required. At the end of Run Time it would prompt for standards. V6.X would not allow standards to be set to required. An upgraded V5 database caused errors at the end of Run Time and the table "customiz" had to be modified using ISQL. V7.00 again allows the field to be set to required, but at the end of Run Time an error is generated (E5483: cannot commit cal summary data. Function error) and it is not possible to save the results. It works as expected in MET/TRACK. This is a problem in the database interface library "metgendb.dll". The Run Time automatically generates a list of standards used by the procedure which just completed. The Run Time should not prompt for a value for field C2340, whether or not that field is designated as "required". However, it's certainly true that it should be possible to make C2340 required for the purposes of MET/TRACK, and doing so should not cause the Run Time to be unable to save the results data from the calibration. Corrected in V7.01 SP1. ----> Selecting Printer Icon Twice Causes an Error Report Number: 21448 Application: MET/TRACK To demonstrate the error using V7.01: 1. Open MET/TRACK as a non-MT user. 2. Select "Search". 3. Select any asset and press enter to begin the search. 4. The instrument browser will appear. Now select the printer icon. 5. Select the printer icon again. An error is now displayed. After the error is acknowledged, the every time the printer is selected again, an error is generated. Corrected in V7.01 SP1. ----> Reliability Greater Than 99 Causes An Error Report Number: 21445 Application: MET/TRACK In V7.01, attempting to save a calibration which would force the reliability to 100 or more confuses the database. Corrected in V7.01 SP1. The problem is a missing error check. The reliability factor is now limited to a maximum value of 99. ----> Security Bug Level 1 User Access Report Number: 21443 Application: MET/TRACK In V7.01, for tables other than Calibration, if field access is set to blank, then level 1 users have complete access for that field. Access should be read-only. Corrected in V7.01 SP1. The field now has complete access only for Level 4 and Level 5 users. ----> MET/TRACK Quick Reports Fails on Field C2340 (Standards used) Report Number: 21416 Application: MET/TRACK To demonstrate the problem using V7.01: 1. Open MET/TRACK as a non-MT user. 2. Select "Reports", then "Quick Reports". 3. Select "Calibration", then "2340". 4. Select "Print Preview". An error will be displayed. Corrected in V7.01 SP1. ----> 54-Character Procedure Name in Field 4241 Causes an Error Report Number: 21412 Application: MET/TRACK To demonstrate the problem: Create a procedure with a 54-character procedure name. Compile and save the procedure. Create a test asset and set the procedure you created up as the default procedure (in field 4241). Start Run Time, select "calibrate by asset number". Choose your test asset number. You will see a "procedure name too long" error. This is related to reports #20279 and #20030. The basic issue here is that when the Run Time queries the MET/TRACK database to find out the name of the procedure associated with a specified asset, an invalid procedure name is returned to the the Run Time. The name is invalid because it includes "MET/CAL:" prepended to the valid name. Corrected in V7.01 SP1. ----> Erroneous Message after Saving Full Results Changes Report Number: 21401 Application: MET/TRACK To demonstrate the problem: 1. Open MET/TRACK as a non-MT user. 2. Select Edit, then Calibration. 3. Select an asset that has a calibration record with full results. 4. Open the full results viewer. 5. Select the Data Columns radio button. 6. Select Edit. 7. Double click on a field to edit. Change something in that field. 8. Close the window. 9. Verify that a message "Do you want to save?" is displayed. 10. Select Yes. A message "Changes not Executed" is displayed. However, when viewed again the changes to the field in step 7 did in fact occur. Corrected in V7.01 SP1. ----> Linked Validation with "extra" Columns Causes Error Report Number: 21351 Application: MET/TRACK In V7.01, if an older DB is updated (V6 and before), and the linked validation has a comment column, then MET/TRACK will generate an error when editing the validation. V7 has no provision for a comment column. Further explanation: In V6 when a linked validation is set up two tables are affected, "vallink" and "vallinkdata". If a linked validation is set up with 4202 as the root and 4203 and 4204 linked and a comment field added, the "vallink" table will look like this: ROOT LINK1 LINK2 LINK3 LINK4 LINK5 ETC 4202 4203 4204 COMMENT (NULL) (NULL) ETC The "vallinkdata" table will look like this: ROOT ROOTDATA DATA1 DATA2 DATA3 DATA4 4202 FLUKE 77 METER HELLO! where "HELLO!" is the comment. These tables are brought forward "as is" during DBupdate. When the validation is opened for edit in V7 the following message appears: "The following internal error has occurred: 13 Type mismatch This warning ... FUNCTION/SUB:frmValidation_Linked,PopulateDataGrid" The form will open, but it includes the comment field as "data3": Manufacture Model Description data3 Fluke 77 meter HELLO! Corrected in V7.01 SP1. This was tested using MET/TRACK build #301 and an upgraded V6 DB with linked validation that included a comment. Tested logged in as both MT and as normal user. No errors were detected. ----> Add Field Numbers to the Customization Form Report Number: 21330 Application: MET/TRACK MET/TRACK V7.00 and V7.01 do not show field numbers in the customization form. Corrected in V7.01 SP1. Now, when editing customization for all forms the field numbers are shown in the edit boxes. ----> Standards Used Field Not in Correct Position after V5.1 to V7.00 Upgrade Report Number: 21315 Application: DB Update The "standards" used field ends up in the upper left corner of the form after a V5.1 to V7.01 upgrade. The problem can easily be fixed as an MT user, but it's ugly. All sorts of fields are on top of it. Corrected in V7.01 SP1. When you upgrade from V5.1 to V7.01, you will see the field "Standards Used" in the appropriate place. ----> Field I4218 with Validation Shows Only 3 Characters, Not All 4 Characters Report Number: 21309 Application: MET/TRACK In V7.01, when using validation with Inventory Table field 4218, only the first 3 characters of the field are shown. Corrected in V7.01 SP1. ----> Trace Report Does Not Show Vendor When Used as a Standard Report Number: 21244 Application: MET/TRACK As reported: I noticed that forward traceability on a lab standard that was calibrated by a vendor (Std = "Vendor") does not show "Vendor" as the standard. The standard field on the report is blank. Of course I know that it was done by the vendor, but since "vendor" is a valid asset, I thought it would show up. The forward report did work for instruments calibrated by other than the vendor. Set up an asset called "Vendor" with 0 interval and 'N' as type. Use this asset as a standard. It will not be shown on the trace report. Corrected in V7.01 SP1. ----> Trace Report Does Not Show Last Standard Used Report Number: 21228 Application: MET/TRACK When running a forward trace report that has FLUKE CORPORATION as the highest level, the standard will not be shown. Corrected in V7.01 SP1. ----> Import Tool Allows Level 0 User to Enter Data into Database Report Number: 21051 Application: MET/TRACK V7.01 does not prevent a level 0 user from importing data. Corrected in V7.01 SP1. When logged in as a level 0 user the option to import is no longer available in MET/TRACK build #290 or later. ----> Desktop Table Error Generated on Bold and Italic Style Settings Report Number: 20950 Application: MET/TRACK This problem appear with German regional settings. Sometimes when configuring the title and display fonts and style settings for the desktops (Set-Up, Desktops), errors related to the font selection are generated when trying to design the browse and entry forms. Investigation revealed that MET/TRACK was using the German words for "true" and "false", namely "Wahr" and "Falsch", for certain field values. The word "Falsch" was too long (by one character). Corrected in V7.01 SP1. MET/TRACK has been updated so that only the words "TRUE" and "FALSE" are used as database values. Localization settings no longer cause no-English values to be used for these Boolean fields. ----> Save and Cancel Button Needed for User Permissions/Levels Screen Report Number: 20949 Application: MET/TRACK When changing user permissions or levels, Save and Cancel buttons are needed. Corrected in V7.01 SP1. ----> Configured Users Can Be Deleted Report Number: 20947 Application: MET/TRACK In V7.01, all configured users can be deleted, even if data are tagged to a user being deleted. Configured users with associated data (cal results) should not be able to be deleted. Corrected in V7.01 SP1. ----> MET/TRACK Screen Shows Incorrect Customer ID Report Number: 20882 Application: MET/TRACK In V7.01, if you Change a Customer ID (for example, from "123" to "ABC"), then save it, the old value remains displayed. Corrected in V7.01 SP1. ----> Field Properties Report and Documentation Not Clear Report Number: 20834 Application: Reports Problem Statement: In the User's Manual, Appendix C1, it is stated that a report with information about all the fields can be run. Some customers have asked for information about what the abbreviation under Field Type is, e.g., SPVAL, RO, INT... The report should be updated to clean up 'Field types'. When the report was looked at it had 'Field Type' listed on it. Reviewing this, it was determined that this column on the report was redundant with another column, 'Data Type'. Redundant and non-user friendly (cryptic) abbreviations used in the 'field type' column were removed. V7.01 SP1 does not include updated reports. Contact MET/SUPPORT if you would like an updated field properties report. The updated report is also on the MET/CAL website. ----> Maintenance Interval (3249) is Set from Inventory (4229), Ignores default Report Number: 20795 Application: MET/TRACK In V7.01 the Maintenance Interval (3249) is automatically set from Inventory (4229), and ignores any default. Maintenance interval records are independent of calibration and should not be copied from Inventory. Corrected in V7.01 SP1. ----> Need to be Able to Change the Interval Type on an Existing Cal Record Report Number: 20698 Application: MET/TRACK As reported by a customer: I need to change the interval type on an existing calibration record but MET/TRACK ghosts that field and won't allow entry. Currently there is 'D' for the type and I want to change to 'M' for months. I know this field comes from the Inventory Screen for new cals, but is there anyway I can make that change on an existing record? Corrected in V7.01 SP1. The entry can now be changed. "Type over" is not implemented. It's necessary to delete the existing type (for example, "D"), and then enter the new type (for example, "M"). ----> Clone Function for Assets Uses 'M' (Months) for Interval Regardless of Setting Report Number: 20674 Application: MET/TRACK In V7.01 the "clone" function for assets uses 'M' (months) as the interval regardless of what it is set to. Additional information: This problem appears only when Edit/Inventory/Clone is selected. From the Instrument Browser it works fine. It appears to follow the default for this field. Corrected in V7.01 SP1. ----> Edit Location Record Generates Invalid "Save Changes" Prompt Report Number: 20669 Application: MET/TRACK To demonstrate the problem using MET/TRACK V7.01: Choose "Edit Location". When the "Edit Location..." dialog appears, immediately choose (click on) the 'X' in the upper right corner of the window. Even though no changes have been made, you will now receive a "Save the Changes?" prompt. There are no changes to be saved, so the prompt is not valid. Corrected in V7.01 SP1. ----> Customize Selection for "Destination" Contains the Selection "ON" Report Number: 20647, 20648 Application: MET/TRACK When customizing a field the drop-down for destination contains the list: OFF ON 4201 4202 etc. When "ON" is selected an error is generated: (Sybase)(ODBC Driver)(Adaptive Server Anywhere)Column not 'IOn' not found. The selection for "ON" should not be in the list. There is no field "ON". 4201 should not be there either. Corrected in V7.01 SP1. ----> MET/TRACK Can't Search for Model Numbers Containing a Slash ("/") Report Number: 20595 Application: MET/TRACK As reported by a customer: On the Search Form, if the model number (4203) has a slash "/" in the model number the search fails to find any matches. The model does appear in the drop down list. This may affect other fields, I have not checked. I did find that the dash "-" works OK, in fact I have not found any other characters that cause problems, however, I have not made an exhaustive check. I can work around the problem by changing how the model number is entered if I have to, however we do have equipment that actually does have a slash in the model number. Corrected in V7.01 SP1. ----> Global Change Errors Occur when Field 2340 is Selected Report Number: 20433 Application: MET/TRACK Using MET/TRACK V7.01, if you login as MT, select Database, then Global Changes, then Calibration Table, then field 2340 (Standards), an unending sequence of error messages is generated. The application must be terminated using the Windows Task Manager. Corrected in V7.01 SP1. ----> V5 to V7 Upgrade: C2331 and C2302 Cannot Be Suppressed Report Number: 20377 Application: DB Update If C2331 or C2302 are suppressed, errors occur when attempting to save calibrations in MET/TRACK. MET/CAL is not affected. V7.0O SP4 included a temporary work-around in the form of an SQL patch which unsuppressed C2303 and C2331. The problem has been corrected in V7.01 SP1. It is now possible to leave C2331 and C2302 suppressed. ----> Procedure Parameter Report Locks Up Report Number: 20244 Application: Reports The report "procpram.rpt", designed to provide information to the user developing new reports, locks up and never returns any information when running with V7 DB. A new procedure parameter report, compatible with V7, is available. The name of the report is "V7ProcParm.rpt". This report has been available since V7.00 SP4 but, due to an oversight, is not included in the V7.01 release. V7.01 SP1 does not include updated reports. Contact MET/SUPPORT if you would like an updated procedure parameter report. The updated report is also on the MET/CAL website. Reopened----> 5520A Accuracy File Update Report Number: 20239 Application: MET/CAL An updated accuracy file for the Fluke 5520A is available on the MET/CAL website. The date of the updated file is 2003-10-27. ----> Forced Re-Search of Assets Report Number: 19874 Application: MET/TRACK Here's an example which demonstrates this problem: Create 6 assets, Pressure_Std_1 through Pressure_Std_6, in the Inventory Form. Close Inventory Screen Search for "Pressure_Std%" The search produces 1 of 6 records (this is correct). Now go to the Calibration Form on first Asset (Pressure_Std_1). Choose "Add Record". Choose "Save Record". Close the New Calibration Record Form. The problem is that you now have to choose "Search" again, even though you have already searched and found the 6 records you want to edit. The problem occurs when in editing records as well. Corrected in V7.01 SP1. The Search Engine Screen now remains open. However, the user must manually refresh the screen to view the updated records. ----> Large Number in Coverage Factor Creates Error Report Number: 19855 Application: MET/TRACK In V7.01 MET/TRACK entering an unreasonably large Coverage Factor value causes the database connection to be dropped. (Coverage Factor is a measurement uncertainty parameter. Reasonable values are in the neighborhood of 2.) Corrected in V7.01 SP1. The maximum allowed value is 999. ----> Regional Settings Do Not Apply in Add Windows for Field Title Report Number: 19683 Application: MET/TRACK In V7.01, regional language support does not work for the field title when adding Instrument, Calibration, Customer, etc. Corrected in V7.01 SP1. ----> Adding Merge Tables Does Not Support Languages Other Than English Report Number: 19682 Application: MET/TRACK In V7.01 adding Merge tables does not support languages other than English. For example, change the Title set to #5 (Spanish) and the language to Spanish when adding a merge table, and observe that all the messages are in English. Corrected in V7.01 SP1. ----> Manual Standards Not Included in Self-Cal Check Report Number: 13231 Application: Run Time This report was originally filed for V6.01. It was then suspended as a low-priority issue. It was re-opened for V7.10 based on customer input. An instrument required by a procedure because it is referred to in an STD statement, and not otherwise required by way of instrument FSC reference or IEEE/PORT/RESET alias reference, is not subject to the normal "self calibration" check which can prevent, or warn about, the situation where the required standard has the same asset number as the UUT. Example: (1) Make sure the "self_cal" initialization file parameter is: (a) not specified at all, or (b) set to "no", or (c) set to "warn" in the [startup] section of "metcal.ini". (2) Use the Config Editor to configure "Manual Standard #1", and assign to it the asset number "ms1xyz". (3) Write, compile, and save a procedure containing the line: STD Manual Standard #1 (4) Start the Run Time and execute the procedure written in step (3). (5) When the prompt for the asset number of the UUT appears enter: ms1xyz (6) You will now see that the procedure begins execution without any warning or error message about the fact that the standard ("Manual Standard #1") and the UUT have the same asset number. Corrected in V7.01 SP1. ------------------------------------------------------------------------------- Section 13: Contacting Fluke ------------------------------------------------- ------------------------------------------------------------------------------- For assistance and questions regarding Fluke Metrology Software please contact MET/SUPPORT at: phone: 1 (800) 825-7411 email: MetSupport@fluke.com European customers may contact the MET/SUPPORT group in Europe via email at: MetSupport@fluke.nl To directly contact the MET/CAL software development team you may send email to: Matt.Nicholas@fluke.com ------------------------------------------------------------------------------- Section 14: Bonus CD --------------------------------------------------------- ------------------------------------------------------------------------------- The MET/CAL V7.10 Bonus CD includes: (1) application notes (2) example reports (3) picture files (4) user-contributed procedures (5) utility programs The application notes are: access7.doc access_excel7.doc app note format.doc backing up version 7 database from an icon.doc cable_sm.doc calpurg7.doc dual database.doc fluke 18x calibration accessories.txt fluke 53&54-ii calibration accessories.txt fluke 8x-iv calibration accessories.txt impapp6.doc leads.zip local_to_euro.doc purge7.doc send2met.doc storproc revised.doc turndays.doc uncertainty in metcal.doc user_table.doc using a digital camera in metcal.doc Updates and additional app notes may be available on the MET/CAL web site. Contact MET/SUPPORT for additional help. The example reports are: basic calibration.rpt basic_inventory.rpt calmonth.rpt cmonth.rpt coastal.rpt inventory report - grouped by location.rpt inventory report - grouped by user.rpt main_sub.rpt maintenance_due_by_asset_for_xx_days.rpt master_inventory_for_asset_number.rpt screen_customizing.rpt turntime.rpt v7 - basic inventory.rpt v7 - basic report template.rpt v7 - screen customizing.rpt v7 - table definitions report.rpt v7 asset count by manufacturer.rpt v7 average cal time by mfg - model.rpt v7 cal standard useage.rpt v7 cal standard utilization.rpt v7 cal standards due-dates.rpt v7 cal workload graph.rpt v7 cal workload history.rpt v7 inventory report.rpt v7 location report.rpt Updates and additional reports may be available on the MET/CAL web site. Contact MET/SUPPORT for additional help. Picture Files: There are many ".bmp" and ".jpg" files on the bonus CD. Refer to the CD. There are too many to list here. User-Contributed Procedures: The bonus CD contains a variety of user-contributed procedures. No warranty as to the quality or adequacy of these procedures is stated or implied by Fluke. However, in many cases these procedures may provide examples of MET/CAL functionality, and may be a useful starting point for creating new or modified procedures. Please do not assume that the latest MET/CAL features are utilized in these procedures. Refer to the CD to see the list of procedures. Utility Programs: This section of the bonus CD includes the latest versions of Autopro, Quick Sort, Thumb Nails, Ask Helper and several other utilities. These applications are not directly supported by the Fluke MET/CAL engineering group, but are supported to some extent by Fluke. ------------------------------------------------------------------------------- End "readme710.txt" -------------------------------------------------------------------------------