2.6.10 samplesPerFile
“samplesPerFile” defines the number of data lines each file can have before a new file is created. This
tag controls the size of the data files into easily manageable lengths for later processing. This setting is
loaded as a signed 32-bit integer, which can translate into very large data files. The user should
exercise caution before setting large files and test the end-user software application for data limitations.
2.6.11 sampleRate
The “sampleRate” tag defines the data rate in Hertz, or samples per second. Valid sample rate settings
are 12, 25, 50, 100, 200, and 400 Hz. See section 4.1 for special features regarding the sample rates.
2.6.12 stopOnVusb
The “stopOnVusb” tag stops data logging operations when a 5v supply is detected on the USB
connector. Without the stopOnVusb option (default), the device switches power from the internal
battery to the USB 5v and continues to log data.
2.6.13 statusIndicators
The brightness intensity of the LED status indicators is defined using the “statusIndicators” tag and
valid settings of “normal”, “high”, and “off”.
2.6.14 wakeUpTime
The “wakeUpTime” option configures the logger to turn on at specific times and days of month.
Parameters are in order of minutes, hours, and days and are separated by spaces. Multiple parameters
are separated by commas. For example, “wakeUpTime=5,20 4,15” turns the logger on at 5 minutes
and 20 minutes past the hour of 4am and 3pm. “wakeUpTime=*” will turn the logger on with each
minute. There are three additional parameters needed to complete the wakeUpTime option and each
must be on a separate line in the config.txt file:
“secsToRecord” defines the time period of data to record in seconds. For example,
“secsToRecord=50” will record 50 seconds of data after a wake up event.
“fileAppend” will append new data to the previous available data file. The logger
will create a new file with each wake up event if fileAppend is not used.
“offOnEndRecord” turns the logger off after the completion of each wake up event.
This option saves power since the logger is not active between wake up
events. Otherwise, the logger will stay in a standby mode (blue LED blinks)
while waiting for the next wake up event.
Each time the logger completes a wake up event, the remaining portion of the memory sector is filled
with a repeating comment string (“;sectalign”). This procedure ensures that the next wake up event
starts on a new memory sector, which makes flash memory allocation easier for the logger. For the
end-user, ignore these “;sectalign” comment strings.
Gulf Coast Data Concepts
Page 14
X16-5, Rev New
