IL3 User’s Guide
page 70
11S-3002B
NIC Parameters
•
Set Transmit/Receive buffers to maximum (these may also be referred to as descriptors)
•
Jumbo Frames/Packets set to maximum size (usually 9K). Experiment with these settings as
results to vary from system to system.
•
Enable interrupt moderation / throttling (set to adaptive if available)
•
Enable Checksum offloads
Camera Connection
•
Point to point connection without any routers or switches between the camera and the computer
is best. If you do need to use a Router or Switch, confirm that it supports and is configured for
Gigabit Ethernet, UDP, and Jumbo Packets. Many Switches Some Routers have built-in firewalls-
these will need to be disabled.
•
Use Cat 5e or Cat 6 cables only. (Cat 5 cables do not support Gigabit Ethernet and may cause the
system to run at 100Mb.)
Fas
M
otion Parameters
There are several parameters to be set to optimize performance. FasMotion Default Parameters are
set conservatively so the application will run on an average un-optimized system. If your system
is excessively slow or busy, you may need to change to more conservative settings. If you have
optimized your system for image transfer performance, you will wish to change to more aggressive
settings in order to get faster transfers.
UDP Transfers
The camera system, while controlled
by Fas
M
otion, uses UDP protocol for
all video streaming (Live and Playback)
and for all file transfers.
If the camera is allowed to send image
data and metadata as fast as it is able,
it will easily swamp most systems and
will cause the UDP connection to fail.
The system introduces an inter-packet
delay to slow the camera down to a
level where the PC can keep up.
Setting Packet Delay
The camera is The Packet Delay setting
is found in the Find Cameras menu.
This is a edit box/spinner that sets the
inter-packet delay in
m
sec.
The default setting is 200. Very fast
systems will be able to keep up with a
delay of 10 to 20, while slow systems
may need the setting bumped up to 300 or 400. For transfers of very large numbers of very small
frames (tens of thousands of JPGs, for example, or possibly large numbers of low-resolution stacks of
uncompressed images) the delay will also need to be increased in order to accommodate file-system
overheads.
Transfer performance can be monitored by simply watching the progress bar during a Save or Copy. If
you notice the progress stopping often or if the system needs to retrieve missing frames at the end of
a transfer, that is a good indication that the PC is not keeping up and that the Packet delay needs to
be increased.
A better way to assess transfer performance is by setting the -s command-line switch and reviewing
the stats.txt file after a transfer (see the next section).
Figure 7-9: Packet Delay Spinner