Curtiss-Wright FHB5-PE1MWB04-00, User Manual, Page: 13 / 72

INTRODUCTION
2-3
FibreXtreme User Guide Copyright 2017
2.1 How to Use This Manual
Purpose
This manual introduces the FibreXtreme SL240 PCI-Express (PCIe) card. It provides guidance
through the process of unpacking, setting up, and programming the cards.
NOTE : Both the FibreXtreme SL100 and SL240 hardware are referred to throughout this
manual as SL240. The software that supports both the SL100 and SL240 hardware is
referred to as SL240, including the driver and API. Anything that is exclusive to the SL100 or
the SL240 is described as such.
Scope
This manual contains the following information:
· An introduction to FibreXtreme SL240 PCIe.
· Applications and topologies for SL240 PCIe cards.
· Instructions for installing and configuring the card.
· An operational overview of the product.
·
General card specifications.
· Register set information.
· Programming information.
· Summary of the protocol used by the SL240 PCIe cards.
· Ordering information for all products mentioned in this manual.
·
A brief introduction to the Front Panel Data Port (FPDP) interface.
· Definitions of words, phrases, and terms used in this manual.
· List of key words referenced in this manual.
The information in this manual is intended for information systems personnel, system
coordinators, or highly skilled network users with at least a systems-level understanding of general
computer processing, memory, and hardware operation.
Style Conventions
· Called functions are italicized. For example, OpenConnect().
· Data types are italicized. For example, int.
·
Function parameters are bolded. For example, Action.
· Path names are italicized. For example, utility/sw/cfg.
· File names are bolded. For example, config.c.
· Path file names are italicized and bolded. For example, utility/sw/cfg/config.c.
· Hexadecimal values are written with a "0x" prefix. For example, 0x7e.
·
For signals on hardware products, an 'Active Low' is represented by prefixing the
signal name with a slash (/). For example, /SYNC.
· Code and monitor screen displays of input and output are boxed and indented on a
separate line. Text that represents user input is bolded. Text that the computer displays
on the screen is not bolded. For example:
C:\> ls
file1 file2 file3
· Large samples of code are Courier font, at least one size less than context, and are
usually on a separate page or in an appendix.