In the PLC user program:
CALL "FTP_PUT"
SRC_DB := DB100 // data to send
START := 0
LENGTH := 1024
FILE_NAME := 'meas_01.csv'
DEST := '/DATA/CSV_OUT/meas_01.csv'
CP_IP := '192.168.1.10'
(Check your CP’s FTP function block availability – sometimes FTP is client-only or server-only.) 10.16 1oo 244 icc ftp server
| Aspect | Implementation | |--------|----------------| | Data consistency | Use redundant DBs in PLC; FTP writes to two separate physical paths or shared network storage. | | Client connection | Connect to virtual IP (e.g., VRRP) or cycle between both IPs; or use a load balancer. | | Active FTP server | Both are active; client decides. For safety-critical – use two separate FTP sessions to both cards, compare retrieved files. | | File synchronization | Sync via PLC user program or external script (rsync, robocopy) after FTP write. | In the PLC user program: CALL "FTP_PUT" SRC_DB
ftp 10.16.100.244
When prompted:
You will see a prompt like ftp> if successful. (Check your CP’s FTP function block availability –
From a PC on same network:
ftp 192.168.1.10
User: oper
Password: ******
ftp> ls
ftp> put test.txt
ftp> get /DATA/CSV_OUT/meas_01.csv
Repeat for 192.168.1.11.