File Naming & Folder Structure

This article explains the different folder and file naming convention used by the enDAQ sensors.

*Note Slam Stick is now enDAQ

In this Article


Folder Structure

The enDAQ internal SD memory card stores all data recordings and device information documentation. When an enDAQ sensor is initially plugged into a computer, it contains three folders on the SD card: DOCUMENTATION, SYSTEM, & SOFTWARE. A fourth (DATA) folder is created after a recording is taken on the enDAQ sensor.

Folder Name Contents
DOCUMENTATION Quick-start Guide, Datasheet, and Calibration Certificate
SOFTWARE
The latest version of enDAQ Lab software (64-bit & 32-bit versions)
SYSTEM
Information for the internal processor and the enDAQ configuration file
DATA Recordings taken on the enDAQ sensor
DATA/YYYYMMDD Folder name by date (year, month, day) of recording files
DATA/CUSTOM
Folder name can optionally be customized

Time Based File Naming

Unique recording files are generated each time the enDAQ sensor completes the operation. The files are organized by date and time of day.  The time of day is represented in “seconds after midnight” which means a file that started recording at 9:00am will be stored as SSX32400 because 9:00am is exactly 32,400 seconds after midnight.

Note

If the folders are named with the incorrect date, the clock can be set on the enDAQ to match the appropriate date and time. See the Configuration Overview article for setting the clock on an enDAQ sensor.

The enDAQ DATA folder organizes recording files by generating a folder for the date specified by the internal clock of the device and stores data recordings into the folder of the date they were recorded. The data files are organized chronologically from top to bottom inside each date folder and are labeled in the following format “SSX00000”. This naming format indicates the file is an enDAQ data file (SSX) and what time the recording was initiated (00000).

enDAQ data is accessible to a computer the same way a flash drive is accessible to a computer. enDAQ use a FAT32 file system for data storage, limiting the maximum file size for a single recording to 4GB. The use of triggers is recommended when large amounts of data are to be recorded. See the triggering article for more detail on available triggering options.

Note

enDAQ devices will not automatically initiate a new recording if the 4GB limit is reached.

If a data file becomes corrupted or does not display data (i.e. a 0 Kb file) in the enDAQ Lab, the enDAQ sensor may have stopped recording unexpectedly. The data can be retrieved or fixed by using the  chk dsk command utility using the command prompt on Microsoft computers. Here is a link with more information on how to use chk dsk on a computer.


Serialized File Naming

The current naming convention is admittedly somewhat cumbersome and not human-readable.  This convention was chosen to prevent files being generated with the same name; but many of our customers now have multiple units and they record over the course of days which can result in files with the same name. As a result, we have also implemented a scheme that generates files that are guaranteed to be unique per device

XXXXXXXX_YYY
X = user selectable
Y = user resetable

  • XXXXXXXX is configurable by the user, up to 8 characters, and defaults to the device serial number.
  • YYY starts at 000, and increments for every file that is recorded. This count is stored persistently on the device, and will remain across recording sessions
    • The most significant digit of the count is in base-36 representation, allowing for file names up through 999, A99, B99, to Z99.
    • After the count reads Z99, the count is reset to 000.
  • The count is reset by changing either the directory name or the filename prefix.
  • When a new file is selected, if the generated filename already exists, the new file will have a -2 appended. This number will be incremented as needed.
  • All recordings over multiple days will go into the same directory.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.