The "disk full" error indicates that there are too many files exceeding the device storage capacity. Numerous combinations of factors could contribute to this issue, such as:

Excessive log files: Logs may be growing in size. You can reduce the maximum age of the files via the Host → Settings under the Log section.

Accumulated histories: F200s have limited space and therefore histories should be cleared after a certain time. Refer to the following article for steps on clearing histories: Clearing Histories.

Exceeding the point limit (5K points).

Snapshot accumulation: Ensure that the number of snapshots has not exceeded the limit. You can control the number of snapshots on the F200 controller by enabling purge settings. For instructions on setting up purge settings, see this article: Purge Settings.

Adding large files: Large images, zips or any other file types to a project can reduce space on the device. Don't go above 90% cumulative. Look at the Disk Space in the Host → Debug.

Run the following queries in Folio → Launch to help clean up some zip files to reduce space.

To delete failed snapshot zip files:

readAll(file and finFileUpload).findAll(x => x->file.toStr == "application/x-zip-compressed").finHardDelete

To delete backed zip files:

readAll(file and bak and finBackup).findAll(x => x->file.toStr == "application/zip").finHardDelete

To delete other zip files:

readAll(file and finFileUpload).findAll(x => x->file.toStr == "application/zip").finHardDelete

If there are unused or unneeded template .fst files, delete those as well. They can be found and deleted from DB Builder → Templates tree.