The DNP File Control feature set is intended to be used as a mechanism for transferring log and configuration files between DNP masters and slaves. KEPServerEX version 5.6's DNP Master Ethernet and Serial Drivers support file transfer to and from a DNP slave. When specifying the Remote File Identifier, users should be aware that KEPServerEX has no way of verifying that the specified remote file path and name are valid: it only verifies that the length is within the 256 characters limitation. As a result, unintended file transfers may occur when the remote path is specified incorrectly. For example, a user may set the remote file identifier to a folder or directory on the DNP slave before performing an upload. Although this transfer may complete successfully, the file most likely cannot be used by the DNP Master.
Local File Identifiers (which include a Path and Name) are verified for syntactic correctness at configuration. The file path must exist in order for a file to be uploaded or downloaded successfully at Runtime. Furthermore, the KEPServerEX Runtime must have Read/Write permission to the file. If the Local File Identifier uses a UNC path that exists on a network resource, KEPServerEX may require domain user credentials. To configure these credentials when KEPServerEX is running as a service (which is the default setting), first locate the KEPServerEX Runtime service in the Service Control Manager. Then open the Log On tab, and specify both the required domain user account and password.
Note 1: Because the KEPServerEX Runtime service may not have access to mapped network drives, UNC paths should be used for Local File Identifiers.
Note 2: When KEPServerEX is configured to run in Interactive Mode, the user that invokes the Runtime process will require Read/Write permissions to the specified Local File Identifiers.