ProPak6 FTP

1. Overview

This application note provides direction on utilizing the integrated FTP functionality of the ProPak6 for convenient data extraction from the internal memory. Both the ProPak6 and OEM638 contain 4 GB of internal logging memory. Once configured as an FTP server, data can be transferred via Ethernet or Wi-Fi. This allows the ProPak6 to be used in remote environments as a monitoring station. Within this document, the means to add the ProPak6 to an established network through static IP are also explained.
The later portion of this Application Notes details the process involved to transfer data from the ProPak6 to a smart phone. Within this section both iOS and Android examples are provided including configuring either device for static IP to connect to a ProPak6 Access Point Wi-Fi network and configuring third party FTP client applications for connection.

2. Networking Features

2.1 Port Information 

Since the ProPak6 is the first NovAtel receiver that contains both Cellular and WiFi, there has been a change made to the standard port configuration. There are now 4 ICOM ports that are shared between all network connections (Cellular, WiFi, and Ethernet), while COM4 is received for Bluetooth.

2.2 Default IP Configuration

The ProPak6 is not preconfigured with an IP address (like the SPAN-SE was). Instead, the user must define a unique IP address. This is achieved through the IPCONFIG command. Once an address has been defined, it can be saved to the receiver via SAVETHERNETDATA ETHA. This command overrides the SAVECONFIG command, ensuring preservation of networking settings should the unit be installed at a remote location where the only access available is through a network; after factory reset, or firmware change, network communication will still be possible.

2.3 Configuring for Static connection on an Existing Network

In order to configure your receiver with a Static IP address, without having to remove your PC from your existing network framework, you must set an acceptable address with a common network part and unique machine part.

Example 1:
The network portion of your PC IP address can be obtained by opening Command Prompt and sending IPCONFIG.

Windows IP Configuration
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : 
   IPv4 Address. . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
Tunnel adapter 6TO4 Adapter:
   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 
   Default Gateway . . . . . . . . . :

Figure 1: IPCONFIG from PC
The receiver must be set with the same Subnet Mask and Default Gateway as the PC:
Subnet mask:
Default Gateway:
From the highlighted line of the figure above, the IP address can broke down into its two parts:
Network Part:
Machine Part:
The ProPak6 must be set with the identical network part and an acceptable machine part value (normally 2 – 254, and not already taken by a different device).
Acceptable Configuration:

2.3.1 Setup for Windows FTP Client

Using the settings above, it is then possible to configure the receiver to accept Windows FTP Client access. First active the FTP Server on the ProPak6:
Now you will need to know the username and password. By default, the ProPak6 account is set to:
Username: admin
Password: Enclosure PSN (found on the bottom of the receiver)

Figure 2: ProPak6 Enclosure PSN
This is also a good time to set your own unique password, especially if connecting the ProPak6 to a publically accessible network. This is possible through:
è Replace OLDPASSWORD with your Enclosure PSN
è Replace NEWPASSWORD with your own unique password

Once connected, the FTP service will use standard DOS commands to manipulate the data on the ProPak6. These messages can be found below:

! delete literal prompt send
? debug ls put status
append dir mdelete pwd trace
ascii disconnect mdir quit type
bell get mget quote user
binary glob mkdir recv verbose
bye hash mls remotehelp  
cd help mput rename  
close lcd open rmdir  

Figure 3: DOS FTP Commands

Example Connection and Data Transfer:

Connected to
220 Service ready.
User ( admin
331 User name ok, need password.
230 User logged in.
ftp> binary
200 Command OK.
ftp> dir
200 Command OK.
150 Here it comes...
drwxrwxrwx    1     root     root        4096 Jan  1  1980 .
drwxrwxrwx    1     root     root        4096 Jan  1  1980 ..
drwxrwxrwx    1     root     root        4096 Jan  1  1970 LOST.DIR
-rwxrwxrwx    1     root     root   414784800 Jan  9  1980 BMAW14030016K_1.LOG
-rwxrwxrwx    1     root     root     2508428 Jun  6 16:36 TEST_LOGS.GPS
226 Transfer OK, Closing connection.
ftp: 348 bytes received in 0.00Seconds 87.00Kbytes/sec.
ftp> get TEST_LOGS.GPS
200 Command OK.
150 Here it comes...
226 Transfer OK, Closing connection.
ftp: 2517739 bytes received in 5.59Seconds 450.64Kbytes/sec.
ftp> bye
221 Bye.

Figure 4: Example Communication with CMD FTP

Figure 5: FTP Connection and Transfer

3. Third Party Software

It is also possible to access the ProPak6 via third party FTP services. The Host is the IP address of the ProPak6, the username is admin, using the defined password. The Port number is to be left blank as it will default to the FTP server, port 21:

Figure 6: Connection Information - FileZilla

It is also important to remember to set to the transfer type in third party software to binary. Leaving the service in default (ASCII) may result in corruption of binary logs during download process.
Figure 7: Binary Transfer Type Settings
Some users prefer this method of transfer to that of the standard FTP service built into Windows’ Command Prompt because you are able to observe transfer status and messages. An example of an established connection and file transfer in FileZilla is available below:

Figure 8: FileZilla File Transfer Example

4. Transferring Files to a Smart Phone

4.1 Wireless Access Point Configuration

To sync a smart phone with the ProPak6 for data transfer, configure the ProPak6 as an Access Point so that the cell phone can connect via Wi-Fi. This can be done via the following:
Logging IPSTATUS will provide confirmation of the adapter IP, while logging WIFIAPCONFIG will reiterate the configuration that has been sent to the receiver:
[COM1]<IPSTATUS COM1 0 86.0 UNKNOWN 0 14973.220 004c4020 7fe2 12832
<     3
<          ETHA "" "" ""
<          WIFI "" "" ""
<          CELL "" "" ""
<          1
<          ""
[COM1]<WIFIAPCONFIG COM1 4 88.0 UNKNOWN 0 1.927 004c4020 dc65 12832
<     1 AUTHENTICATION "open"
<WIFIAPCONFIG COM1 3 88.0 UNKNOWN 0 1.940 004c4020 dc65 12832
<     1 SSID "ProPak6_Network"
<WIFIAPCONFIG COM1 2 88.0 UNKNOWN 0 1.944 004c4020 dc65 12832
<     1 ENCRYPTION "none"
<WIFIAPCONFIG COM1 0 88.0 UNKNOWN 0 6251.097 004c4020 dc65 12832
<     1 IPADDR ""

4.2 Cell Phone Settings

Once Wi-Fi is enabled on the smart phone, search for the SSID assigned to the ProPak6. The cellular device must be set to a static IP address on the network, below are examples for Android and iPhone:

Figure 9: iOS Static IP Setup

Figure 10: Android Static IP Setup

Confirmation of connection can be found by logging WIFIAPSTATUS and observing that the MAC address is present on the network:

[COM1]<WIFIAPSTATUS COM1 0 87.0 UNKNOWN 0 14178.313 004c4020 a895 12832
<     ENABLED "00:21:66:00:87:8A" 1 1
<          "D8:96:95:0D:0F:DE" 54.0

4.3 FTP Client Applications

In order to use a smart phone, an FTP client application must be present. There are various available through the application stores on major platforms. Once installed, the connection settings should follow the same general requirements as a PC based FTP client:

Figure 11: iOS FTP Client Setup

Figure 12: Android FTP Client Setup

4.4 Connection and Data Transfer Examples

Below are example connections established using both iOS and Android operating systems:

Figure 13: iOS FTP Connection to Propak6

Figure 14: Android FTP Connection to ProPak6

Final Points

If you require any further information regarding the topics covered within this application, please contact:

NovAtel Customer Service
1120 – 68 Ave. N.E.
Calgary, Alberta, Canada, T2E 8S5
Phone: 1-800-NOVATEL (in Canada or the U.S.) or +1-403-295-4500
Fax: 403-295-4901