Here are several recommendations to help ensure stable FTP streaming with a CR1000X / CR1000-series logger:
Ensure reliable communication link: Use a robust modem (cellular or wired) with good signal strength and a stable IP connection. Connection drops are often caused by weak network links.
Stream table size & frequency: Reduce the table-write size or interval if uploads are failing. Smaller tables every 5-10 min often work more reliably.
FTP settings:
Use the FTPStreamTable() instruction in CRBasic (or equivalent) rather than plain TableSend().
Ensure the server login and path are correct, and set Retry parameters so the logger re-attempts connection on failure.
Enable passive FTP mode if your server/network requires it.
File naming & path stability: Use simple filenames and avoid overly long paths or special characters. Some FTP servers time out or reject unusual paths.
Time synchronisation: Make sure the logger’s clock is accurate (via GPS or NTP) so that scheduled streams do not overlap or conflict.
Logging and diagnostics: Enable detailed logger debug logs (via DebugMask or similar) and review message logs (CommWatch) for SSL/FTP errors or “connection reset” messages.
Firmware/OS updates: Ensure the logger is running the latest OS version that supports FTP streaming features and bug fixes.
Server side tolerance: Check the remote FTP server doesn’t impose quotas or disconnections for repeated connections in short intervals.
Power & environment: For logger sites in harsh conditions, ensure power is stable; dropouts may abort or corrupt FTP uploads.
Alternative protocols: If FTP is still unstable, consider using secure HTTP or MQTT streams supported by Campbell’s newer loggers depending on your infrastructure.
If you post your CRBasic snippet, OS version, logger model, FTP server type, and exact error messages from the CommWatch log, other forum members can help pinpoint the issue more precisely.