beautypg.com

Notes, Error description – Yaskawa MotionWorks IEC Toolboxes User Manual

Page 189

background image

Communications Toolbox: Function Blocks

MotionWorks IEC61131-3 Toolboxes: 2013-09-13

176

Notes

This block utilizes FTP, not SFTP as SSL is not currently supported in the firmware. As a result, all FTP
traffic sent and received (e.g. username, password, file data) is sent unencyrpted in plain text and is
therefore visible to anyone with access to your internal network. However, this should not be a problem
so long as the data you are sending is not of a sensitive matter and your FTP server account is
CHROOT'd properly (talk to your IT professional about using FTP).

It is suggested that your FTP server either have a internal/external domain name OR use a static IP
address as a change in address will prevent the block from transferring files. See "Setup" for more
details.

Your FTP user account for this block must have "Write" privileges to be able to write files to the server.
Optionally, your account may also have "Append" privileges. Note that if your destination files already
exists and your user only has "Write" then the file will be overwritten. If the file exists and your user
has "Append" then the file contents transferred will be appended to the existing file.

Error Description

ErrorID

Meaning

0

No error

8705

The maximum number of concurrently open user IO devices (sockets/files) has been
reached.

8706

The socket handle was invalid.

8707

The IP address string was not in a valid format.

8708

The socket could not be created.

8709

The specified address or port is already in use on the local network.

8710

The specified address or port is not available for use.

8711

Unable to accept new socket connection.

8712

Unable to bind to the specified address.

8713

The socket type argument was invalid.

8714

The local address or port was not valid.

8715

The socket could not be connected.

8716

There is no network routing path to the specified address.

8717

The socket is already connected to another endpoint.

8718

The socket connection attempt was actively refused by the remote peer.

8719

The socket was not connected to a remote endpoint. Call Y_ConnectSocket prior to
Y_ReadDevice or Y_WriteDevice.

8720

An error occurred trying to get or set the device option.

8721

The communication device could not be read.

8722

The communication device could not be written.

8723

The Buffer argument to WriteDevice and ReadDevice is required.