FTP Push

The FTP Push feature allows logged data files to be automatically copied using FTP to a user-specified server. The logged data files are copied to the server as soon as the data file is closed.

Select Data Logging / FTP Push.

 

Server Address – Enter the address of the server in which the data is to be copied to. Enter the address either as a numeric IP address or a valid DNS address. For example, ftp.trimble.com.

FTP Server Port – Enter the port of the FTP server in which the data is to be copied it. The default port is 21.

Username – Enter the (case sensitive) username required to log into the server.

Password – Enter the (case sensitive) password required to log into the server.

Verify Password – Re-enter the password required to log into the server.

When choosing an FTP Server password, remember the following limits:

• 60 characters for the server address

• 12 characters for the user name

• 15 characters for the password

• 60 characters for the remote directory

Delay – When the file roles instead of pushing the data immediately, the push is delayed by "delay" minutes. If there are a number of receivers on the same network all FTP-pushing, each receiver should have a unique delay to avoid overloading the network by all the receivers trying to FTP-push at the same time.

Remote Directory – The remote directory is the directory structure that the FTP Push should follow to write the data.

Example: \Data_Files\Trimble\

Path Style – Select one of two directory structures for the created files:

• Flat – Files are all created at the top-level directory of the selected file system. No subdirectories are used.

  NOTE – This can result in a large number of files in a single directory, which can cause slow responses when listing directories, etc.

  NOTE – Some file systems have limitations on the number of files that can be created in a top-level directory. You should not use this path style if a large number of files will be created.

• Type/YYY/DDD/site – Files will be stored in a structure of the form /type/YYYY/DDD/site/filename.<<T02 or T04>>. The site is the station name. The date chosen corresponds to the expected start time of the session.

• RefData.YY/Month.MMM/Day.DD – Files will be stored in a structure of the form /RefData.YY/Month.MMM/Day.DD.

Rename – Select one of two options:

• No – This leaves the file name format as previously selected when using FTP Push.

• ##########YYYYMMDDhhmm: Creates a twenty-two character name consisting of:

  • The full ten-digit serial number (##########)

  • The four-digit year (YYYY)

  • A two-digit month (MM, 01 = January)

  • A two-digit day-of-month (DD, 01=first day of month)

  • A two-digit hour (00 to 23)

  • A two-digit minute (00 to 59)

  The time encoded is the theoretical start time when the file would be created. Typically, it is the start time of the session. However, if a scheduled file starts later than its scheduled time (for example, due to a power failure), then the file will be named as if it actually started on time.

Transfer Mode

• Passive with fallback to Active – This is the default setting. Trimble recommends that you select this option.

• Passive – The client sends a PASV command to the server and then receives an IP address and port number. The client uses these to open the data connection to the server. Use this option in situations where the client is behind a firewall and cannot accept incoming TCP connections.

• Active – The client sends the server, the IP address and port number on which the client will listen, and the server initiates the TCP connection.

• SFTP – The default port will automatically switch to Port 22 (user editable). After entering the connection details and clicking Test to perform a test of the connection, the algorithm and fingerprint provided by the remote server will be displayed, and the Verify check box is enabled but remains unchecked. You must select the Verify check box to enable remote host verification during transfers; otherwise the key submitted by the remote host will always be accepted.

  NOTE – You are encouraged to use HTTPS connections in combination with SFTP for secure transmission of all credentials. Also, it is strongly recommended that you enable Email Alerts on the receiver to be notified if a transfer fails due to a new fingerprint being used by the remote FTP server.

Test – When you click Test, the receiver attempts to connect to the server and publishes a test file called Hi.text to verify that the information is correctly entered. To push logged files, you must enable FTP Push on the Logging Setup page. Data files are only pushed when a data logging file is closed.