When the ATA Payload boots, it needs to determine the filename for the next data log file. I could just keep appending to the same file, but I feel that using a different one each time will keep things easier to track when it comes time to process the data.
The current algorithm is that the data files are in the root of the SD card (no directories) and follow the 8.3 file format as:
ATA00000.dat
Each time the device boots, it reads the files one by one, incrementing a counter for the filename number. Once it hits a free number, it uses that for the current logfile. It then creates the log file, writes out a header and begins operations.
The code for the filename search is already in the repo and has been tested on the SD card. Given the number space, it can reboot 99999 times before running out of filenames.
When the ATA Payload boots, it needs to determine the filename for the next data log file. I could just keep appending to the same file, but I feel that using a different one each time will keep things easier to track when it comes time to process the data.
The current algorithm is that the data files are in the root of the SD card (no directories) and follow the 8.3 file format as:
ATA00000.dat
Each time the device boots, it reads the files one by one, incrementing a counter for the filename number. Once it hits a free number, it uses that for the current logfile. It then creates the log file, writes out a header and begins operations.
The code for the filename search is already in the repo and has been tested on the SD card. Given the number space, it can reboot 99999 times before running out of filenames.