Load IPM, Run server, toggle bit to transfer the file.Īdd Tags to log, and one DI to use as FTP transfer trigger.

FileZilla - Setup user account and password the matched datalog configuration.

Tool Kit project with M2M, Datalog config, & an FTP Client Tranfer (enabled/executed via DI register).

Calculate how many days you can log data before reaching a given file sizeĮxample: 400,000 bytes ÷8554 bytes per day 46.75 days Setting up an FTP Client Transfer with IPm2m and FileZilla Overview.

Calculate the total number of bytes per dayĮxample: 144 records x 54 bytes per record x 1.10 (10%) = 8554 total bytes per day.Calculate the number of datalog records stored per dayĮxample: 1440 minutes per day ÷10 minute (logging rate) = 144 datalog records per day.The Record Content window includes a display of the total number of bytes each record.Observe the total number of bytes per datalog record.The retrieved data will be displayed in the Data Viewer main window and/or written to an ASCII text file on your hard drive.Įach TCP client transfer must have a unique IP port in the RTU configuration and the Datalog server must have the same TCP port added.Datalogging with TCP Client Transfers How much data can I log?

Data transfer options allow data to be easily read and then cleared, if desired. To make configuration easy and accurate, the available I/O points are readily accessible from within a tag listing, based on the project file.ĭatalogging will begin once the datalog configuration data is downloaded to the station. Use the datalog configuration windows in the I/O Tool Kit to define the rate and conditions (such as an event signal) by which datalogging will occur, and to define the I/O to be logged.

Citect support