An engineer can specify a script file name for a sequence. Script files provide a way of sending data to a printer. The engineer creates the script and then if a test unit passes all the tests NaTKiT executes the commands contained in the script file. The issue disc contains the example file SCRIPTS\scriptdem.txt. The current script file syntax follows.
1/ Any line with "." in the first column is interpreted as a remark.
2/ Any line with ".." in the first two columns is interpreted as a command.
Script File Commands
The command ..CR XX sends XX line feed and carriage return combinations to the active output device.
The command ..DATE sends to the active output device the current date in d mmmm yyyy format. The d is the day of the month as a numeral, the mmmm is the full name of the month, and the yyyy is the year as four numerals. The date format can be altered by adding a format specification to the ..DATE command. For example ..DATE d mmmm yyyy is equivalent to the default and would give 7 December 1958, ..DATE d-mmmm-yy would give 7-December-58, ..DATE m/d/yy gives 12/7/58.
Please be warned that NaTKiT cannot recover if it encounters an invalid format specification.
d Display the day as a number without leading zeros (1-31)
dd Display the day as a number with leading zeros (01-31)
ddd Display the day as an abbreviation (Sun-Sat)
dddd Display the day as a full name (Sunday-Saturday)
ddddd Display a serial date number as a complete date
(including day, month, and year)
m Display the month as a number without leading zeros (1-12)
if used immediately following h or hh, the minute rather than the month is displayed
mm Display the month as a number with leading zeros (01-12);
if used immediately following h or hh, the minute rather than the month is displayed
mmm Display the month as an abbreviation (Jan-Dec)
mmmm Display the month as a full name (January-December)
y Display the year as a two-digit number (00-99)
yyyy Display the year as a four-digit number (1900-2040)
The command ..ID sends the NaTKiT's serial number to the active output device.
The command ..LPTX sets printer port X as the active device.
The command ..MODEL sends the current model to the active output device.
The command ..OPERATOR sends the current operator's name to the active output device.
The command ..PARTNER returns the next number below the current serial if the current serial number is even. If the current serial is odd then PARTNER returns the next number above. For example, if the current serial is 1245 then PARTNER returns 1246.
The command ..PLOT type yFramePos yPos sends the current test unit's frequency response to the active output device. This command only functions if the active output device is a laser printer configured to support Hewlett Packard PCL and HP-GL/2.
The argument type can be Comp, Diff or Target.
Comp specifies the compensated curve is sent to the output device.
Diff specifies the difference curve is sent to the output device.
Target sends the target frequency response to the active output device. The target is specified by data contained in the file specified by the sequence parameter Compensation file.
The argument yFramePos specifies the y axis position of the bottom left hand corner of the plot frame on the output device.
The argument yPos is an optional argument. It only applies to Comp and Target. It adjusts the plot's y axis position within the plot frame. It can be a signed number, typically in the range -3.0-3.0dB.
The command ..SERIAL sends the current test unit's serial number to the active output device.
The command ..SPACE XX sends XX spaces to the active output device. The maximum permitted value for XX is 255. If XX equals zero, or is missing, then NaTKiT ignores the SPACE command.
The command ..TIME sends the current time in "hh:mm" 24 hour format to the active output device.
The command ... sends "." to the active output device.
The command ..@ XX XX the space separated numbers are sent to the active output device as the appropriate ASCII control code. For example "..@ 12" would normally cause a printer to form feed.
Any other string, except spaces or nulls, is sent unprocessed to the active output device.
NaTKiT1 keeps a production record in the file nk_prod.dbf. This is a dBase III format file with a 1337 byte header. Each record is 243 bytes and contains 42 fields in the following format.
Modelis the product tested during the session.
Operator is the name of the operator for the session.
Test_statn is the station from which the data has come.
Start_code is the encoded session start date and time.
End_code is the encoded session end date and time.
Dead_code is the total time during the session that the Fault Finding option was active; ie no production testing occurred.
The number for all three codes is in Microsoft Visual Basic format. The Dattimecode section in Appendix C contains an explanation of the format.
Total_test gives the total number of units tested during the session.
Total_fail gives the total that failed during the session.
Failcode1 .. 32 are not in use but are intended to return a failure mode analysis.
Expansion1 and Expansion2 are, not surprisingly, for future expansion.
The data file nk_crv.dbf contains test unit response curves in dBase format. The dBase header is 3553 bytes. Each record is 187 bytes and contains 110 fields in the following format.
Model_nameis the product name tested.
Serial_num is the serial number of the unit if applicable.
Dattimecode is an encoded number representing the date and time the unit was tested. The code is in Microsoft Visual Basic format. The integer part of the number represents the date and is in the range -53688 to 65380 representing 1 January 1753 and 31 December 2078 respectively. The decimal part of the number is the time scaled so that 24 hours equals 1, eg 0.5 represents 12:00 pm.
Stat_name is the test station name where the unit was tested.
Op_name is the person who tested the unit or, to be more precise, the name the operator selected from the list. If there is no operator name list then the entry will be Unknown.
Swpstrtfrq is the Sweep start frequency in hertz, ie the frequency the response sweep started at.
Swpendfrq is the Sweep end frequency in hertz, ie the frequency the response sweep ended at.
Swpptnum is the Sweep point number, ie the number of points in the sweep. The frequency for each point can be calculated from the expression
freq = (10(inc * (n-1))) * fLo
where inc = log10(fHi / fLo) / (ptNum - 1)
n is the point of interest
fLo is the sweep start frequency, ie Swpstrtfrq
fHi is the sweep end frequency, ie Swpendfrq, and
ptNum is the number of points in the sweep, ie Swpptnum
Future_exp is for future expansion. (We have plans!)
Fail flags if the unit failed the test. This isn't as daft as it sounds because an engineer may want review the failures only - we all know engineers like to have a nice long think before they say it's all right really. The field is a single character flagging a failure if the ASCII value of the character is greater than zero.
At present, it isn't possible to set disc logging on fail.
Curve001 .. 100 the relevant number of fields will contain for each point the difference in dB from the standard. By storing the difference from the standard rather than the actual response, future environment changes are accommodated. Each field is a single character and has the difference encoded into the ASCII value of the character. The value can be simply decoded by the simple expression
difference = (n - 128) / 10
where n is the ASCII value of the character.
Please note that if importing this data into a Windows application the ASCII value returned will depend on the relevant font. The correct font is Terminal and this should be active at the point of importation.
NNNN_cal.datis the calibration file for the NaTKiT1 board serial number NNNN. The programme actually looks for the file nk_cal.dat. By keeping a duplicate of nk_cal.dat under a file name that indicates the serial number life is made a little simpler. The file is plain text.
nk_amp.dat contains the calibration data for the power amplifier. It is plain text.
nk_cal.dat - see NNNN_cal.dat above.
nk_crv.dbf contains the responses for the models the Engineer has selected for disc logging. See "APPENDIX C - The Disc Logging File nk_crv.dbf Format" for more information.
nk_prod.dbf contains the production performance data. See "APPENDIX B - Production Reporting In NaTKiT" for more information.
nk_seq.dbf contains the test sequence parameters for the models you have created at the test station. If you want to copy the test sequences to another test station then this is the file, along with nk_tst.dbf, to copy.
nk_sys.dat contains the system parameters, ie the test station name, the operator time out, etc.
nk_tname.dat contains the name of the sequence name used to create the "Typical". It is only used NK1 Xtra.
nk_tst.dbf contains the test parameters referred to in nk_seq.dbf. If you want to copy the test sequences to another test station then this is the file, along with nk_seq.dbf, to copy.
nk1.exe is the NaTKiT1 test programme that needs all these data files!
nk1_sim.exe is NaTKiT1 test programme but in simulation. It will run without the NaTKiT1 board present.
nk1_xtra.dat may not be present. It contains the system parameters set by the Engineer for the optional support programme NK1 Xtra.
nk1_xtra.exe may not be present. NK1 Xtra is an optional support programme that identifies the median of a batch and pair matches.
pricelst.txt contains the current prices when the issue disc was made and is intended as a guide only.
readme.txt lists any late information or known bugs.
whatsnew.txt contains what features and fixes are new since the last version.