Receiver-log compatibility and errors
Use this reference to check whether a receiver-log file is compatible, understand why a file was skipped or rejected, and interpret the timestamps, file details, transmitter counts, and record counts shown by ReceiverLogs.
Supported inputs
ReceiverLogs accepts Fathom receiver logs as individual .csv files or by scanning a directory that contains them. Extension matching is case-insensitive.
A project scan searches subfolders but ignores:
- files with unrelated extensions
- dot-prefixed files and folders
- the app-managed
ReceiverLogs.projectfolder
A file that cannot be read or parsed is reported without preventing other healthy files from being reviewed. File Manager requires filenames it can display as UTF-8.
If ReceiverLogs cannot finish scanning the folder reliably, it keeps the previous file review rather than replacing it with an incomplete list. Repair the access or path problem and run Scan files again.
Loader errors
| Problem | Meaning | What to check |
|---|---|---|
| File access failed | ReceiverLogs could not open the file or finish reading the folder. | Confirm that the file exists and your user account can read it. |
| Invalid encoding | The receiver-log text is not valid UTF-8. | Re-export or replace the file; renaming it does not repair its contents. |
| Invalid Fathom header | The file does not begin with a supported Fathom export header. | Confirm that it is an original, unmodified Fathom CSV export. |
| Invalid schema | A record declaration is duplicated or inconsistent. | Compare the reported declaration with the original export. |
| Invalid row | A row has malformed CSV quoting, an invalid record type, or unexpected populated fields. | Compare the reported row with the original export. |
| Unsupported extension | The file is not a .csv. | Use the original Fathom CSV rather than a renamed workbook or other file. |
A failed file remains outside the Dataset or shows Inspection failed / Load failed. Open its Status detail, repair or replace it, choose Scan files, and then retry Update Dataset.
Compatibility checklist
A supported Fathom CSV has:
VEMCO DATA LOGat the beginning of the first non-empty line- valid UTF-8 text
- at most one descriptor for each record type
- data rows that follow a matching descriptor
- valid one-line CSV quoting
An optional row beginning with RECORD TYPE may appear after the header and is ignored. Empty lines are allowed. ReceiverLogs accepts common CRLF line endings.
Use original Fathom exports whenever possible. Files constructed or edited by hand are more likely to contain damaged descriptors, quoting, encoding, or line endings.
Detection times
ReceiverLogs recognises detection times in these forms:
YYYY-MM-DD HH:MM:SSYYYY-MM-DDTHH:MM:SS- either form with fractional seconds
Leading and trailing whitespace is ignored when interpreting the time. The date must be real. A malformed detection timestamp does not reject the whole file, but that row is unavailable in time-based Data Explorer views.
The original Device Time (UTC) text remains part of the loaded record.
File details
File Manager displays details supplied by receiver-log content, not values inferred from the filename or filesystem date. Depending on what the export contains, these can include:
- source filename, identifier, and size
- receiver model and serial
- firmware and timezone
- initialisation and offload times
- external time, PPM/HR counts, memory, and battery information
Optional values remain blank when the export does not provide them. Scan inspection samples large files, so a detail found only in an unexamined middle section may remain blank until the file is loaded into the Dataset.
Unique transmitters
ReceiverLogs counts distinct non-empty detection Full ID values, excluding rows whose detection type ends in _SELF, such as PPM_SELF and HR_SELF.
If the export does not include a Detection Type column, ReceiverLogs cannot identify self-detections and counts every distinct non-empty Full ID. A transmitter ID found in several files is counted once in the Dataset-level total.
Record counts
Record totals include rows from successfully loaded files only. A record type with no rows is omitted, and skipped files do not contribute records.
Limitations
This reference focuses on files you can review through File Manager. For working with detections after the files have been added to a Dataset, use Data Explorer: explore detections.