Append is the default: new records are added to the current measurement-period file. The basic connection test checks login and folder access, not append permission. An explicit append refusal is reported in the event log; no automatic switch occurs.

Completed daily file builds one whole record-day in CPU storage after a reading from the following day confirms it is closed. All unsent records must remain available in logger storage, with enough free CPU space for the file. Upload retries replace the same dated destination file; avoid sharing these names with other writers. Retention gaps stop the export instead of silently omitting data. Delivery follows the configured schedule after the day closes.

Separate batch files send new records in bounded files named with their first record number. Retries use that same name, and the transfer checkpoint advances only on success. This permits frequent delivery without append, but produces multiple files.

Select the method in Communications, then regenerate and deploy the program and matching library. Changing methods starts a separate transfer checkpoint and may resend retained records; keep earlier downloads separate when combining data. Smaller table headers and records are required for whole-day and separate-batch modes; the generator or exporter reports limits rather than truncating data.