The Gig-cPCI-3U and Gig-cPCI-3U Switch family of network adapter cards and
switches are high-performance, cost-effective solutions for adding Gigabit Ethernet
connectivity to any embedded or real-time network appliance or network access device
which has available slots in their 3U cPCI based systems.
The GigMAC-CPCI-3U and Gig-CPCI-3U-Switch family includes optimized, highperformance driver support for VxWorks and Linux. Instructions for Linux driver
installation are included in this manual. In addition, a companion document titled
“VxWorks Users Manual and Integration Guide” is provided for technical assistance in
integrating and testing the driver in an embedded real-time VxWorks environment.
1.1 SEE ALSO
Please also see the following documents on our website at www.dssnetworks.com and
also included in the OEM developers kit CD:
Datasheets – please see product datasheets and other updated product information on
OEM developer CD and on website.
Release Notes -- where updated information is provided on new features, compatibility,
performance benchmarks, platform information and corrected problems.
VxWorks Users Manual and Integration Guide, DSS Document part no 131901.
Provides technical information on integrating and testing our controllers and drivers into
a VxWorks BSP and system board.
GIGFAQ.HTML – Also on website and included on OEM developer CD contains many
answers to commonly asked questions regarding Gigabit Ethernet and our products
including performance and system recommendations.
README.LINUX – Included on OEM developer CD contains latest driver installation
and usage instructions for Linux Operating System.
netPerformance.txt -- Included on OEM developer CD contains useful information on
tuning the VxWorks network protocol stack.
1.2 COMPATIBILITY
The GigMAC-cPCI-3U and Gig-3U CPCI Switch family is fully compliant with the
following standards:
IEEE 802.3 (all sections applicable to 1000 Base T, 1000 Base SX, 1000 Base LX)
IEEE 802.1D and IEEE 802.1Q as applicable for VLAN and priority queuing support
PCI 2.2 and PCI-X 1.0 compliant
PCI low-profile specification (as applicable for model)
IEEE 1386.1 Draft 2.2
Linux driver compatibility: Standard Linux 2.4 or 2.6 kernel level network driver
module compiled and tested on Intel and PowerPC architectures up to Linux kernel
2.4.30 and 2.6.22 (see release notes for latest updated information).
VxWorks driver compatibility: Wind River standard Tornado 2.0.2, Tornado 2.2/2.2.1,
(vxWorks 5.4/5.5/5.5.1) and Workbench (vxWorks 6.x) Enhanced Network Driver (END
driver) loadable module integrated and tested on PowerPC and Intel architectures.
2. MODEL NUMBERS
This user manual covers all Models of our Intel based GigMAC-cPCI-3U and Gig 3U
CPCI-switch cards including:
• Compatible with all 10/100/1000BaseT hubs, switches and routers
• Burst rate of up to 256 dwords (1024 bytes) over PCI bus
• Jumbo frame support for up to 9K, 802.3x full duplex flow control with automatic
pause and priority with multiple priority queues
3. SWITCH CAPABILITIES MODELS C5468
The model C5468 provides an onboard Gigabit Ethernet layer 2 switch with
management capabilities. The operating registers in the switch are accessible via a
register-level API that is provided in the host driver and described in section 10.5 of this
manual.
The switch can be programmed to support advanced features including following:
o Port rate control
o Protected ports (switch partitioning)
o Broadcast Storm Suppression
o LED control
4. OEM DEVELOPER KIT CONTENTS
An OEM developer kit is provided with the purchase of the Gigabit Ethernet controllers
which contains drivers, documentation and sample code including the following:
Driver source code for vxWorks, Linux 2.4, PowerPC, Intel platforms
Users Manual(s)
VxWorks Users Manual and Integration Guide
Datasheets for chipset controllers (Intel, National, etc.)
TCP/UDP/IP performance test programs (vxWorks, Linux, Windows versions
included)
TCP, UDP and raw driver performance tests
Driver Utilities (Linux)
High-performance frame generator (wire and bus-speed capable)
Transmit and receive callbacks (hooks) for driver-level application code
Internal and external loopback capabilities
Built-in performance instrumentation statistics
Gigabit Ethernet FAQ sheet
NetPerformance.txt protocol stack tuning guide for vxWorks
On solid green to indicate auto-negotiation complete and MAC and driver level link is
up.
Transmit and Receive Activity Indicators
Transmit and Receive LEDs are solid or blinking yellow
to indicate activity on the link (blinking shows tx and rx activity).
Model C5262-RJ dual-port or C5261-RJ single port 3U CPCI (copper)
The front panel has two onboard RJ-45 connectors that supports the connection of
Category 5e cabling with 4 LED indicators per port that provide the following as marked
with silkscreen nomenclature on front panels:
Model C5262-LC dual-port or C5261-LC single port 3U CPCI (fiber)
The front panel has two onboard fiber LC connectors that support the connection of
singlemode or multimode fiber optics with 4 LED indicators per port that provide the
following as marked with silkscreen nomenclature on front panels:
The front panel has two onboard SFP connectors that support the connection of
singlemode or multimode fiber optics or 1000-Base T transceivers with 4 LED indicators
per port that provide the following as marked with silkscreen nomenclature on front
panels:
Model C5164/C5264 quad-port 3U CPCI with RJ-45 connector(s)
The front panel has four onboard RJ-45 connectors that support the connection of
Category 5e cabling with 1 LED indicator per port that provides both a “link” and
“activity” indicator as follows:
OFF (no link)
ON (link)
BLINKING (link and activity)
Model C5468 Gig 3U CPCI Switch with 4-port RJ-45 connector(s)
The front panel has four onboard RJ-45 connectors that support the connection of
Category 5e cabling with 1 LED indicator per port that provides both a “link” and
“activity” indicator as follows:
OFF (no link)
ON (link)
BLINKING (link and activity)
The following table shows typical system level frame latencies measured during highperformance testing using frame generator including path from SDRAM to wire through
system controller across PCI bus interface:
Frame size (bytes)
60 – 100
500
1000
1500
Typical latency
(microseconds)
< 2
4
8
12
7. POWER CONSUMPTION SPECS
3U CPCI Boards Power Consumption Table
Card Model
C5261
C5262
C5263
C5164
C5264
C5468
3.3V Source
Current I (mA, A) Power (Watts)
900 2.97
1.17 3.86
1.17 3.86
2.34 7.90
2.34 (est) 7.90 (est)
1.93 6.40
8. HARDWARE INSTALLATION
Before attempting to install the card into your system, please make sure of the following:
Shut off the power to the computer and any peripherals. It is important to remove the
power cable to the computer to reduce the possibility of residual power remaining in
the power supply.
Ground yourself. Many electronic components inside computer and on the card can be
severely damaged by receiving a shock of static electricity. Before touching any
electronic components or boards, discharge any static electricity on your body by
touching the bare metal case around the power supply inside your computer. Avoid
excessive movement during the installation, such as walking across carpets, as this can
generate static. If you must leave the installation area before the installation is
complete, be sure to ground yourself again before continuing the installation.
There are many different styles and types of Embedded System platforms that utilize 3U
CPCI expansion slots. This section contains a generic installation procedure. Please
refer to your User's manual for more detailed instructions on installing the adapter in an
Embedded or CompactPCI system.
Step 1 - Shut down the power to the computer system and remove the power cord and
any peripheral cables.
Step 2 - Align the CPCI connectors and the CPCI SBC or carrier connectors and push
slide in to connectors mate. Once mated, press down firmly on the 3U CPCI card until it
is completely seated in the connectors on the CPCI backplane. Re-attach the power
cable and any other cables that were removed for the hardware installation procedure.
Connecting Fiber optic Model C5261-LC, C5262-LC, C5263-SFP
This section explains how to connect the fiber cards to the external network using
standard fiber optic cables. Typically 50 or 62.5 micron multimode fiber optic cables with
LC or SC type connectors are used depending on the connector option. For extended
distance, single-mode fiber can be used in models equipped with extended range
single-mode connectors.
Insert the fiber optic cable into the SC or LC type connector until the self-locking tab
clicks into position. Connect the opposite end in to a 1000 Base SX switch. Two types of
cables are used when connecting the fiber cards to the network. A workstation or
"straight through" cable is typically used to connect Ethernet adapters to switches. A
fiber “crossover” cable may also be used to connect controllers back-to-back. This
configuration is useful for loopback and/or diagnostic purposes or when a switch is not
available.
This section explains how to connect the adapter cards to the external network using
the standard Category 5e, 5e or 6 cables. The maximum cable length is typically 100
meters or 328 feet.
Insert the Category 5e cable into the RJ-45 connector until the self-locking tab clicks
into position. Connect the opposite end in to a 10/100 or 10/100/1000 Base T switch.
Two types of cables are used when connecting the adapter cards to the network. A
workstation or "straight through" cable is typically used to connect Ethernet adapters to
switches. A “crossover” cable may also be used to connect controllers back-to-back.
This configuration is useful for diagnostic purposes or when a hub or switch is not
available. However, it is not recommended for extended use, as it violates the IEEE
specification for 10 Mbit, 100 Mbit and 1000 Mbit Ethernet networks.
Note(1): Models C5164, C5264, C5261-RJ, C5262-RJ and C5468 support “auto-MDIX”
mode where a crossover cable is not required when directly attaching two controllers.
Note(2): Cables used for Gigabit networks must use all 8 wires. In 10 and 100 modes,
wires are dedicated for transmit or receive while in Gigabit mode, data is transmitted
and received over all 4-pairs.
The following sections explain how to install the driver software in VxWorks, and Linux
based systems.
10.1 LINUX DRIVER INSTALLATION AND USAGE
These instructions assume that you are running Red Hat Linux 7.x, 8.x, 9.x or a similar
Linux OS. You should be using at least a kernel version 2.4.18 installation for any other
Red Hat-based system will be similar. For other Linux based systems, the location of
some files may be slightly different.
Building the driver
To build the driver, copy the driver files to an appropriate directory. You will need to
make sure your CD is mounted.
$ mkdir dpm
$ cd dpm
$ cp /mnt/cdrom/linux-dpm-driver/dpm/dpm*.tar.gz .
$ gunzip dpm*.tar.gz
$ tar vxf dpm*.tar
To create a new driver object module:
$ make clean
$ make
Repeat same procedure with driver utility directory as follows:
$ mkdir util
$ cd util
$ cp /mnt/cdrom/linux-dpm-driver/util/util*.tar.gz .
$ gunzip util*.tar.gz
$ tar vxf util*.tar
To create a new utility programs:
$ make clean
$ make
Note(1): If you are installing the adapter cards in an SMP machine, you should
comment out the standard CFLAGS line in the “Makefile” and uncomment the SMP
version of CFLAGS before compiling the driver (safe to leave SMP enabled on newer
versions of Linux (2.4.18 – 2.4.26, 2.6).
Note(2): Before compiling, please also edit the Makefile and set “INCLUDEDIR” to the
path of your Linux kernel source tree. For example:
INCLUDEDIR = /usr/src/linux-2.4.25/include
Installing the driver
To install the driver object module in the file system, become root and run:
# make install
# depmod –a
# insmod dpm.o
Note(1): For loading driver with Intel 82546 based cards, use ‘ChipSelector=1’ or leave
blank (default)
Note(2): For loading driver with National DP83820 based cards, use ‘ChipSelector=0’
Note(3): ‘modprobe’ may be used in place of ‘insmod’ to resolve module dependencies.
Configure the card using your preferred configuration tool, or edit the initialization script
for the interface directly. On Red Hat, the file /etc/sysconfig/network-scripts/ifcfg-eth0
might look something like this (substituting ethernet device number, example: eth0,
eth1, etc):
Note: You should also add a line to /etc/modules.conf for each interface as shown in the
following example:
SAMPLE MODULES.CONF FILE
alias eth1 dpm
alias eth2 dpm
alias eth3 dpm
alias eth4 dpm
options dpm ChipSelector=1 IntrHoldOff=0
Note: In order to load the Intel driver, the "ChipSelector=1" option (the default) can be
set in the 'options' field of modules.conf. Please see man page for modules.conf for
additional information on module configuration.
MANUAL DRIVER INSTALLATION
insmod ./dpm.o # to insert driver module
ifconfig eth1 192.168.0.3 # if not already configured by system
Once driver is inserted you may need to run "ifconfig" command or it may be run
automatically by the system.
MANUAL DRIVER REMOVAL
ifdown eth[n] # repeat for all 'dpm' network interfaces
rmmod dpm # to remove driver module
LOADING THE DRIVER FOR INTEL BASED MODELS (C5261, C5262, C5164, etc.)
Note: In order to load the Intel driver, the "ChipSelector=1" option is not required during
the 'insmod' as it is the default option:
The following parameters are used by entering them on the command line with the
modprobe or insmod command. For example, with Intel based card model (ex. C5262,
C5164, etc.) entering:
insmod dpm [ChipSelector=1] IntrHoldOff=0
loads the dpm driver setting it for Intel chipset and setting the Interrupt Holdoff latency to
zero (disabled).
Parameter Name
SetAutoNeg
DuplexMode
PauseFlowEn
IntrHoldOff
MediaSpeed
Valid
Range/Settings
0,1 1
0,1,2
(0=half, 1=full,
2=both)
0, 1 1
0, 1 or 2 (0=off) 1
10, 100, 1000 1000
Default Description
This parameter specifies the enabling of auto
negotiation.
Defines the direction in which data is allowed to
flow. Can be either one or two-directional. If both.
1
If auto negotiation is enabled, defines modes
advertised. If auto negotiation is disabled sets
duplex to this value.
This parameter enables or disables pause frame
flow control (typically enabled).
This value delays the generation of receive
interrupts in units of 100 microseconds. Receive
interrupt reduction can improve CPU efficiency if
properly tuned for specific network traffic.
Increasing this value adds extra latency to frame
reception and if set too high could decrease the
throughput of TCP traffic.
If auto negotiation id disabled, speed forces the
line speed to the specified value in megabits per
second (Mbps). If auto negotiation is enabled,
sets the highest speed advertised.
(adapters using copper connections only)
NumBufDescs
MaxMtuSize
MaxBufferSize
AccAllUni
DSS NETWORKS, INC. DocVersion: 1.2 Page: 24
This value is the number of transmit and receive
descriptors allocated by the driver. Increasing
80 - 4096 256
1500-9600 1500
2048, 4096,
8192, 16384
0, 1 0 Setting this parameter to one instructs the driver
2048
this value allows the driver to queue more
transmit and receive buffers. Each descriptor is
16 bytes.
This value is the maximum mtu size supported in
the driver.
Sets the maximum buffer size supported in the
driver.
to receive all unicast frames (sometimes useful in
frame generator testing). Do not enable for
normal traffic.
ChipSelector
FrameGenSize
0, 1 1
60-MaxMtuSize 1500
Sets the chipset selector (0=National, 1=Intel).
Default is National chipset.
Sets the frame generator frame size for testing
end-to-end or loopback.
FUNCTIONALITY TESTING
When the driver is loaded into the system via `insmod' it probes the PCI bus to locate all
DP83820 devices, and creates control structures for each. The driver logs a couple of
messages available in `/var/log/messages' for each device with information about its
PCI geographic location, IRQ, IO address, and some basic debug information
(addresses of some important structures).
All the devices on the PCI bus can be listed by,
# cat /proc/pci
# cat /proc/interrupts
IRQ and IO address information from this can be correlated with the information
displayed by the driver in `/var/log/messages'
When the TCP/IP stack is initialized, it opens all configured ethernet devices, and
initializes them for use. At this time, the driver will perform auto negotiation and log
information about the link status. The driver can then be tested by running ping, telnet,
ftp, NFS etc.
Suggested basic verifications to be run
lsmod # lists loaded drivers
ifconfig # lists configured network interfaces
dmUtil -s eth[n] # prints low-level driver statistics for device
ping <ip addr> # ping to remote station to verify
ADDITIONAL VERIFICATION AND PERFORMANCE TESTING
Verification and performance testing can be done using the Linux "uxBlaster" and
"uxBlastee" test programs found on OEM developer kit CD. The 'dmUtil' utility program
also found on the CD can be used to obtain valuable information used for debug and
integration verification.
dmUtil -m eth0 # displays DP83820 MAC controller registers
dmUtil -p eth0 # displays gigabit (phy) transceiver registers
dmUtil -e eth0 # displays eeprom
dmUtil -a eth0 # displays mac address
dmUtil -ms eth0 # displays mac stats (Intel only)
LOOPBACK PERFORMANCE TESTING
1. Edit 'Makefile'
2. Un-comment the following define:
CFLAGS += -DNS_FRAME_TEST -DIN_FRAME_TEST
3. Save file, unload and reload driver using procedures described above.
4. Use "ifconfig" command to bring up Ethernet interface.
5. Run the following command from the 'util' directory:
./dmUtil -l eth1 # loopback eth0, eth1, etc.
6. View statistics using dmUtil command as follows:
./dmUtil -s eth1 1 # second arg=1 zeroes statistics after gathering
Note: The driver must be compiled without "-DNS_FRAME_TEST" for normal
operation.
Jumbo frames: The mtu size can be increased using the ifconfig utility, as
follows:
# ifconfig <interface-name> mtu <mtu-size>
Example: ifconfig eth0 mtu 3000
Note: Use of jumbo frames is not recommended as it is not IEEE standard and many
switches do not support the forwarding of jumbo frames. It also has to be enabled and
negotiated on both ends of the connection and in today’s faster systems, using jumbo
frames offers little performance improvement and may only be useful in closed
application-specific networks.
The “dpm driver utility” is used to capture detailed board levels statistics, controller
registers and to set loopback mode. Example usage of the “dmUtil” are as follows:
dmUtil -s eth1 # get driver statistics for interface 1
dmUtil –p eth1 # get phy (transceiver) registers for interface 1
dmUtil –m eth1 # get MAC (PCI controller) registers for interface 10
dmUtil –t eth1 # get execution debug trace for interface1
(DEBUG_FLAGS trace option must be compiled in)
dmUtil –e eth1 # get eeprom configuration settings
The dpm network driver management API is an api extension primarily used by the
‘dmUtil’ command line utility to enable various management functions or to acquire
driver status and statistics. The typical api usage sequence is as follows:
1. User enters ‘dmUtil’ command and parameters as shown in the following
example:
./dmUtil –s eth1
2. dmUtil parses command line and prepares an “ioctl” request block to send to
driver. A pointer to a application buffer to hold the text message results (for
example formatted statistics) is provided by dmUtil in the request block.
3. Driver receives ioctl request block performs action and copies result data to
applications message buffer.
The following is an API description of the management ioctl commands issued to the
driver from the ‘dmUtil’ application’s viewpoint:
/* get mac MIB statistics */
#define DM_IOCTL_GET_MAC_STATS 10
Please also see example code in dmUtil.c for additional information.
10.5 SWITCH CONFIGURATION / MANAGEMENT API
Note: This section is applicable for Model C5468 Gig 3U CPCI switch/interface cards
only.
The following functions are provide a low-level access capability for reading and writing
the configuration and management registers on the embedded switch:
Functions to reset and initialize switch:
STATUS inResetSwitchDevice(int unit, int initialReset);
Functions to read and write registers in the switch:
STATUS inReadSpiReg(int unit, int page, int offset, int bCnt, UINT8 *pData);
STATUS inWriteSpiReg8(int unit, int page, int offset, int val);
STATUS inWriteSpiReg16(int unit, int page, int offset, int val);
STATUS inWriteSpiReg32(int unit, int page, int offset, int val);
Note: The Intel device driver supporting the Model C5468 card initializes the switch by
writing a default configuration during initialization. This is performed in the Intel driver
initialization using the function “inLiInitBcm5388()”. This function may be modified to
make changes to the default configuration. Additional switch management functions
may be implemented using the low-level register access API shown. For additional
information and register programming details, please contact technical support.
There are several ways to test your adapter on vxWorks and Linux platforms. This
section provides suggestions on how you may test and verify your installation. Before
you can proceed with any of the suggested tests, you must have previously configured
your TCP/IP protocols and interfaces on your computer. Please refer to your online help
and User Manuals for your particular system on instructions on setting up your TCP/IP
environment.
ICMP Ping. Ping is a simple verification method and it very useful for verification of
cabling, adapter configuration and system configuration of the TCP/IP protocol
software. You can also specify a “fast ping” and larger message sizes in order to
more effectively test the protocols and adapter interface.
FTP File Transfer. FTP is also an available method for testing your installation. FTP
allows you to test by transferring files of different sizes. Using large file transfers is a
good way to test medium transfer rates through the protocol stack.
HTTP Web Browsing. Is a good means of testing the protocols and interface to the
adapter.
Telnet. Using Telnet you can log into another system and invoke commands to send
a receive data. You can also test multiple connections within a single window by
repetitively Telnet’ing back and forth between multiple systems.
Windows Explorer. In a Windows environment, you can also use the Windows
explorer to access files on other systems within your Workgroup or Domain.
Blaster / blastee can be used to perform TCP throughput tests between VxWorks,
Linux and Windows platforms. These test programs are included on the OEM
developer CD.
Internal loopback: The vxWorks and Linux drivers can be placed into internal
loopback for a full-speed raw driver and controller throughput test. This is very useful
for getting a baseline throughput measurement and also for verifying the robustness
of the controller and driver in your system.
Connector (Model C5261-LC, C5262-LC, C5262-SC, C5263-SFP fiber): SFP, SC or
LC connector type for 50/125 or 62.5/125 micron multimode fiber or 8/125 singlemode
fiber.
Drivers:
Linux 2.4 (2.4.18 – 2.4.26), Linux 2.6 (all versions)
Tornado 2.0.2, Tornado 2.2 and Tornado 2.2.1 (VxWorks 5.4/5.5/5.5.1)
Status Indicators (model C5164): Per port link/activity
Status Indicators (model C5468): Per port link/activity
Status Indicators (model C5261/5262): Per port link, duplex, transmit, receive
Bus Interface: PCI v2.2 bus master, 32/64-bit, 33/66 MHz
Dimensions: (3U CPCI Models C5164, C5261, C5262, C5468):
Standard 3U CPCI
PCI Power supply voltage: 5V or 3.3V (factory optioned), 5V is default
PCI signaling voltage: 5V and 3.3V
Performance Throughput (PCI 32/33): 118 Mbytes/sec (944 Mb) full or half duplex
sustained per port
Maximum frame rate: Over 850,000 frames per second sustained per port
Burst Rate: Up to 256 dwords (1024 bytes) over PCI bus
Host Offloading: IPv.4 checksum (UDP, TCP and IP) and optional statistics gathering
for RFC 1213 (MIB II), RFC 1398 (Ether-like MIB), IEEE
802.3 LME
Optional: Jumbo packets, 802.3x full duplex flow control with
automatic pause and priority with multiple priority queues
Link Quality Monitor: Continuously adapts to actual line conditions
by managing echo and crosstalk cancellation,
equalization, timing and skew compensation.
Operating Temperature: 0º to 60ºC (standard –C1 model)
Relative Humidity: 10% to 90%, non-condensing
Voltage: 5 or 3.3 volts
MTBF:
Model C5261 – 350,000 hours
Model C5262 – 300,000 hours
Model C5263 – 300,000 hours
Model C5164 – 275,000 hours
Model C5264 – 300,000 hours
Model C5468 – 250,000 hours
Environmental Standards Compliant:
FCC Part 15, Class B
EN 55022; 1998 Class B
EN 50082-1
CE Mark
Network: IEEE 802.3u Auto Negotiation and parallel detection
IEEE 802.3ab Gigabit Ethernet over 4 pairs of UTP Category 5e (1000BaseT)
Gigabit
IEEE 802.3z Gigabit Ethernet over 1000 Base SX multimode fiber
IEEE 802.1D and 802.1Q as applicable for VLAN priority queuing
IEEE 802.3 Gigabit Ethernet over 4 pairs of UTP Category 5e 1000BaseTX).
IEEE 802.3u Fast Ethernet over 2 pairs of UTP Category 5 (100BaseTX).
IEEE 802.3 Ethernet over 2 pairs of UTP Category 3 (10BaseT).
Full Duplex: Support for 10/100/1000 Mbps data rates on all copper models (fiber
models Gigabit mode only)
Telephone technical support (Mon-Fri 8AM to 6PM, MST), 24-hour support via web
email
1 year limited product warranty on controller hardware (contact support for
warrantee/RMA information)
Contacting Us
You may contact DSS Networks in one of several ways: via the Web, e-mail, fax or
telephone.
Technical Support
Send all technical support queries to support@dssnetworks.comor visit the DSS
Networks website at www.dssnetworks.com. The DSS Networks website contains
technical as well as sales literature for all of our products.
Technical Support-Worldwide
+1.949.716.9051
Technical Support-Fax
+1.949.716.9052
Main Corporate Telephone Numbers
949-716-9052
DSS NETWORKS, INC. DocVersion: 1.2 Page: 46
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.