RoboFlowHelp.1.20

!!! warning "Legacy Documentation" This page contains documentation for the original RoboFlow application. Some features described here may not exist in the new Damtoolkit WAP interface.

Syncfolder-synchronize-with-FTP (Synchronize files from folder with FTP site)

The SyncFolder workflow compares the local files and folders in a local folder to a remote folder via FTP.

Depending on the Master (local or FTP) and Slave (FTP or local) the files and folders are synchronized from the Master to the Slave:

• New or modified master files and folders are uploaded/downloaded to the slave

• By default no Master-files are ever deleted unless you choose the hot folder-option in Master-Slave. In that case only new master-files are processed and deleted afterwards

• If you rename files on the Master, the same files on the Slave will be renamed

• If you rename files on the Slave, they will be put back to the original name from the Master

• If you move files on the Master, the same files on the Slave will be moved

• If you move files on the Slave, they will be put back to the original location on the Master

• If you rename and move files at the same time, then the workflow no longer recognizes this files and will treat them as new files

Parameters

Name	Description	Example
FTPserver	IP-address or DNS name of FTP server	e.g. 192.168.2.100
FTPuser	FTP user name	e.g. roboflow
FTPpassword	Password of FTP user name
FTPport	Portnumber of FTP-server default: 21	e.g. 21
FTProot	Root folder on FTP-site where the files to synchronize are stored	e.g. /datafiles
WaitForRemoteFile	number of milliseconds to wait for a stable FTP file, if file-size and file-date does not change in this wait-period, the file is considered stable (=ready to process)	e.g. 4000
Master-Slave	Choose the master and slave (local or FTP) and choose if it's a "hotfolder" or not (hotfolder-option means that the Master-files are moved to the Slave and then deleted on the Master. In that case you should also set New-Slave-File to "do nothing".)
New-Slave-Files	If a new file is found at the slave-side (so not present at master-side) the workflow can "do nothing" or can "delete" the new-slave-file