Local Capture Mode

If the parameter localMode.enabled in anneth.ini is set to true, then Anneth Local Capture mode is entered automatically whenever a switch closure is detected on the Local Capture switch input. In this mode, data acquisition is completely controlled by the external Remote Start and Resolution switches. A simplified full-screen display window allows the operator to monitor current system Status, Filename, Scan Number, Scan Time, Resolution, Gain, and Peak-to-Peak Signal. A File History window displays a list of collected files, and summary information for each of these files.

Note that in Local Capture mode the instrument sweep speed and retrace speed are fixed at 375000 Hz, with data acquisition in both directions. All data collected in this mode will be in the 16-bit fixed point format.

Resolution Control

In Local Capture mode, resolution is controlled by the external Resolution switch. If this switch is open, the spectral resolution will be set to the value of the parameter resolution.hi from the anneth.ini file. The default for this value is 4 cm^-1. If the Resolution switch is closed, the spectral resolution will be set to the value of the parameter resolution.lo from the anneth.ini file. The default for this value is 16 cm^-1.

Remote Start

In Local Capture mode, a switch closure on the external Remote Start switch will initiate data collection. The filename will be set according to the Edgar 8.3 file naming convention. The output path will be set to the location specified by path.local from the anneth.ini file. If path.local is not present, a default of “C:\rawdata” will be used. If the specified folder does not exist, it will be created. Data will be collected for as long as the Remote Start switch remains closed.

While data is being collected, the Status field will show “Recording”. When data is not being collected, the Status field will show “Standby”.

Note that the Edgar 8.3 file naming convention can specify a unique filename only to the nearest minute, so when using this mode your run times (or down time between runs) should be greater than 60 seconds. If you collect a short file (less than 60 seconds), then attempt to start another collection before the next minute starts, the system will wait until the new minute to start collecting, in order to avoid overwriting the previous file.