User's Manual

Table Of Contents
Printed Documentation
152
6. The Server will ask for a username and password. Enter the username “ftp”, and the
password can be anything, even left blank if the FTP Server is set up as described
earlier.
Note: A blank anonymous password will not work on all types of FTP server, some
may require a correctly formatted email address (e.g. a@b.com) as the password.
Also, the username ftp is equivalent to typing the username anonymous.
7. Switch the transfer mode to binary, by entering the command bin;
8. Turn on “hash marking”, by entering the command “hash”. This will print “#” symbols
across the screen when the transfer is in progress.
9. Transfer a file: The command to receive a file is “recv, and to send is “send”.
Following the command you must enter the name of the file to transfer, and
optionally also the name to call the file when it has arrived.
For example, to send a file called “500K”, enter:
send 500K
And to receive a file called “2M”, and locally rename it to “2M_downloaded”, enter:
recv 2M 2M_downloaded
Note: Some FTP servers are case-sensitive, this is a common reason for a failed
download. Remember that Windows does not always display file names with their
names in the correct case. To see a list of files in the current directory of the FTP
Server, and their exact case sensitive names and file sizes, enter the command “ls l”
(short for: list directory contents, using long format). You can use this command to
make sure the files you are intending to transfer are the correct length for the test you
wish to perform.
a. Wait for the transfer to complete. You will see “#” symbols scrolling across the
screen, at a rate proportional to the file transfer speed. You can cancel the transfer
by pressing CTRL + C, although the system will take a few seconds to take action
and close down the transfer.
When the transfer is complete, the session will show you the transferred speed. An
example transcript from Airspan’s Product Applications Laboratory is shown in the
screenshot below:
Note: As the FTP Client shows the speed at which the data in the file was
transferred, it will not show you the actual data throughput over the air interface. This
is because an allowance of 3.7% must be made to include the protocol headers
encapsulating the data. A description of these overheads and the 3.7% calculation is
shown in the technical note at the end of this section, along with details of other
overheads to consider. Referring to the transfer speed in the screenshot above, the
data transfer above resulted in an Ethernet frame throughput to the FTP Client of:
110.33KBytes/sec * 1.037 = 114.4KBytes/sec, or 915.3KBits/sec.