0

Correct.exe

Is there a paper, manual, or anything else on all the commands for using this correction file updater program?  Thank you.

10 comments

Date Votes
0
Avatar
Chad D.

Hello Marc, the use of correct.exe is documented in the MET/CAL User's Guide under Customizing the Run Time, then Creating Correction Files (*.COR).  There are six help topics available in this section.

-Chad

0
Avatar
Marc Devereaux

Thank you but, there is nothing on how to use the correct.exe itself.  Lots of info on the .cor file format, etc.  I am looking for details on the commands or program specifiers that can be used with the correct.exe program.  Right now we have a problem running this line in metcal:

DOS          -x correct.exe C:/Progra~2/Fluke/METCAL.ini 5720 init.  Get this error: E4243: CORRECT: Hmm... Can't seem to fine "none\5720.new" and then E1846: User program "correct.exe C:/progra~2/fluke/metcal.ini 5720 init" failed. Exit code = 1.

I can execute: DOS          -x correct.exe C:/ProgramData/Fluke/METCAL.ini 5720 check 168.  Returns the Julian date in the .cor file and I can execute DOS          -x correct.exe C:/Progra~2/Fluke/METCAL.ini 5720 reset which seems to update the Julian date in the .cor file.  So I know that the correct.exe is finding the the correction directory and .cor files for some commands. 

I would like to know what all the specifiers are and how they work.  Thank you.

 

 

0
Avatar
Dale Chaudiere

Your MET/CAL initialization file (default "metcal.ini") has:

correctdir            =none

You need a setting like the following:

correctdir            =C:\ProgramData\Fluke\METCAL\Corrections

0
Avatar
Chad D.

Marc, what Dale states is true and should correct the "none\5720.new" error you observed.

I also wanted to thank you for bringing the missing command line information to my attention!  I didn't realize that this wasn't previously included in the help system.  I will update the following information, if needed, and add it to the MET/CAL help topics:

USAGE DOS -x correct.exe <ini file> <name> exists Check to see correction file (<name>.cor) exists in the directory specified by "correctdir" in the MET/CAL initialization file. MEM1 is set to 1 if correction file exits MEM1 is set to 0 if correction file does not exists DOS -x correct <ini file> <name> init Initialize a correction file. This operation copies the empty correction file <FSC>.new from the MET/CAL working directory to the MET/CAL correction file directory. If <FSC>.cor already exists in the correction directory, it is backed up as <FSC>.bak in the correction directory. DOS -x correct <ini file> <name> reset Reset the GMT time stamp in a correction file to the current GMT. This operation does change any other data in the correction file. DOS -x correct <ini file> <name> check [<hours>] Check to see correction file is still within the time period specified (hr). If <hours> is not specified, the value of MEM is used. DOS -x correct <ini file> <name> backup Backup a correction file so it can then be modified safely. DOS -x correct <ini file> <name> restore Restore a backup version of a correction file. DOS -x correct <ini file> <name> read "<mode string>" <nominal> [<mod1>] Read a value from an existing correction file. Value is returned in MEM. DOS -x correct <ini file> <name> insert "<mode string>" <nominal> [<mod1>] [-sensor|-source] Insert a value into an existing correction file. The correction value must be stored in MEM1 prior to execution of the DOS statement. The value in MEM1 must be in the same units an the nominal value on the DOS FSC command line. For example, if nominal = "1kV" on the command line and the correction value is 1000.02V, the value in MEM1 must be 1.00002. <ini file> is the full path name of the MET/CAL initialization file. MATH S[1] = IFILE() <name> can be a recognized FSC name or the name of a user-configured device or manual standard. <mode string> uses the MET/CAL rules for accuracy/correction file mode strings. The mode string must be valid for the name specified. The <nominal> and <mod1> strings must contain a value immediately followed by a valid MET/CAL dimension. If the <mod1> string is ommitted, the correction file must contain NA in the MOD1 lower limit and upper limit fields for a successful insertion. If <mode string> contains "Ohms" and <name> is one of the following, the nominal value is taken from memory register MEM in lieu of <nominal> on the DOS FSC statement line. 4000 4000A 4700 4705 4707 4708 4800 4800A 4805 4808 5450 5700 5720 Note, for the above names, the FSC is used, not the model number. Example: For the Fluke 5720A, use "5720", not "5720A". The following statement is an example of a valid use of correct: "-sensor" or "-source" is only necessary for user-configured device or manual standards. If <name> is a recognized instrument FSC, source vs. sensor is automatically determined. DOS -x correct [S1] 5700 insert "Volts" 1V 1kH DOS -x correct [S1] 436 insert "Watts" 100mW 10kH -sensor However, the following statement is invalid because "Hz" is the MET/CAL units code for Hertz. DOS -x correct [S1] 5700 insert "Volts" 1V 1kHz

 

0
Avatar
Marc Devereaux

Thank you very much. 

My metcal.ini file has these entries:

accdir                = Z:\acc
correctdir            = Z:\Correction Files
cortemplates          = none
helpdir               = C:\ProgramData\Fluke\Help
mathfiledir           = C:\ProgramData\Fluke\METCAL\MathFiles
password_dir          = C:\ProgramData\Fluke\METCAL
picdir                = Z:\pic
procdir               =I:\MetCal Under Developement\Agilent\3458A_New
rifwifdir             = C:\ProgramData\Fluke\METCAL\IniFiles
rinfdir         = Z:\
user_cwd              = Z:\INI
user_data_dir       = C:\ProgramData\Fluke\METCAL
user_prog_dir       = Z:\USER_PROG
workdir               = C:\ProgramData\Fluke
rslt_col_template     = none

So as you can see the correctdir has an entry so that is not the problem.  I would think if it was = none, that the other correct.exe lines would not execute either but, they work.  Just the init command line that is not functioning.
 

0
Avatar
Chad D.

Yes, cortemplates needs to be set to the real directory containing your *.new template files.  The init command is trying to copy 5720.new from the cortemplates directory, but cannot find directory "none":

cortemplates          = none

0
Avatar
Marc Devereaux

OK.  Different than correctdir.  Made the change to cortemplates = and works now.

That ini file entry is not in the MetCal reference manual either and your previous description of the correct.exe INIT command says that the <fsc>..new file is pulled from the metcal working directory not the cortemplates directory.  Maybe these edits could be added to the next rewrites too.

Thank you very much for your help.  Happy Holidays.

0
Avatar
Chad D.

You are correct Marc.  I also noticed the outdated reference to the MET/CAL Working Directory as I was updating the help topics, and will ensure this is corrected in the 8.2 help topic.

Happy Holidays to you as well!

-Chad

0
Avatar
Marc Devereaux

Chad another question please.  We are now getting an error: E2506: Can't open file: "m\5720.tmp".  Looks like correct.exe is creating a copy of the .cor file in the User_prog_dir= directory labeled name.tmp?  We have that directory in a shared network folder and typically we do not want the techs messing around in that directory so we restrict their permissions.  Worried they may overwrite or delete a file needed by others.  Do we have to change their permissions and allow them to write to that directory to use correct.exe?

0
Avatar
Chad D.

Hi Marc, I am not sure if the error you are seeing is related to permissions that are preventing the file copy operation from completing successfully, or if there is still bad path somewhere.  The path reported in the error message is not valid "m\5720.tmp".  If you were working with a network drive, perhaps "M:\5720.tmp" would be a valid path, but I do not see this listed in your previous metcal.ini entries.  Please ensure that all paths are correct in metcal.ini, then check directory permissions if the error persists.

-Chad

Please sign in to leave a comment.