OmniBus PCI/cPCI USER`S MANUAL
Contents
1. Level Designator A B4 B32 Level Number used in 1 2 3 4 5 Number of Simultaneous Terminals 1 4 32 32 32 Configurable Response Time v v v v v Monitor v v v v v Filtering for terminal address v v v v v Filtering for subaddress v v v v Concurrent terminal monitoring v v Protocol Error Injection v v Variable Transmit Amplitude v Zero Crossing Distortion v 5 2 1 Software Selectable Bus Termination Each databus on all OmniBus MIL STD 1553 modules has a 75 ohm termination resistor that can be switched across the direct coupled terminals under software control When transformer coupling is used the direct coupled termination resis tance must be off and external couplers and terminators are required See Ap pendix A for more information about bus termination and transformer versus direct coupling 5 2 2 Configurable RT Response Time The RT response time of MIL STD 1553 OmniBus modules may be individually set in software for each 1553 channel The response time is measured from the mid bit zero crossing of the parity bit to the mid bit zero crossing of the status word The RT response time may be set through software using the BTI1553 RTResponseTimeSet function The response time value is an integer that represents the response time in hundreds of nanoseconds up to 25 5 micro seconds The minimum response time 1s affected by the error checking process and is about 3 7 microseconds for 1553A2. LFH Pin Name Pair LFH Pin Name BUS2N BUSION 13 CDOUT0A 43 BDOUTO I 13 CDOUTOA CGND NCSVA GND 18 48 GND CDOUT2A GND CDINIA CDIN2A N BUS7P BUSI5P BUS7N BUSISN BUSSP BUSI3P BUSSN BUSI3N BUS3P BUS11P BUS3N 57 BUSIIN BUSIP 58 BUS9P BUSIN BUS9N D GND 0 1 depending on core A or B Table 6 1 General pin designations 6 3 Module Specific Wiring The meaning and use of the databus signals on the LFH connector depends on the protocol and functionality of the associated module This section provides chan nel definitions and connector pinouts for the more common OmniBus modules Listings for the 716036 Pin give the connector and pin number for the signal when a Ballard 16036 cable is used See Section 6 4 for more information on ca bles 6 2 OmniBus User s Manual PINOUTS 6 3 1 MIL STD 1553 The pin assignments for the MIL STD 1553 modules are listed in Table 6 2 be low Be sure to follow the coupling and termination guidelines provided in Ap pendix A 5x0 5x1to 5 5 Name Description Pair Pin Pin Name U U U U U U U U a U B B B B 6 BUS8P 8 8 CHIBX BUS transformer coupled BUS11P 57 CHIBXR BUS B transformer coupled 2 P3 17 BUSIIN CHIAX S A transformer coupled 1 Table 6 2 Pinouts for MIL STD 1553
3. 3 1 Figure A 1 Transformer coupling to a dual redundant databus A 2 Figure A 2 Direct connection to dual redundant databus 3 LIST OF TABLES Table 4 1 IRIG formats used by 5 4 2 Table 4 2 Electrical characteristics of OmniBus IRIG signals 4 2 Table 4 3 Hardware versus software designation of core discretes 4 3 Table 4 4 Designators for board 4 3 Table 6 1 General pin 6 2 Table 6 2 Pinouts for MIL STD 1553 modules serene 6 3 Table 6 3 Pinouts for ARINC 429 modules eese 6 4 Table 6 4 Pinouts for ARINC 708 modules 6 5 Table 6 5 Pinouts for ARINC 717 modules eene 6 6 Table 6 6 Wiring chart for 16036 cable assembly 6 8 Table 6 7 MIL STD 1553 cable assembly configurations 6 8 Table 6 8 Twinax wiring on MIL STD 1553 cable assemblies 6 9 Table 6 9 D sub connector pinout for cable assemblies 16037 and 16039 6 9 OmniBus PCI cPCI User s Manual iii TABLE OF CONTENTS This page intentionally blank OmniBus PCI c PCI User s Manual 1 INTRODUCTION This manual
4. Q eus 27 2912 9 Table 6 3 Pinouts for ARINC 429 modules LFH Polar ity LFH jb p ops h 2 P245 BU 9 2 14 Lb es 2 ja _ 2 16 Ls pes pm P247 Lp pgs B P248 BU Ls ees 2 s P2 19 BU P js P220 BU P221 Bu a 16 32 15 BU 2 9 59 P3 14 BU p s 3 4 7 3 16 Bu Lm es N ps 57 P3 17 BU Ls p fo 36 P3 18 BU Lg pps 0 55 P319 BU e peo 9 P3 20 BU 52 10 26 53 21 OmniBus User s Manual 16036 LFH Pair Pin Pin Name SOP ON IP IN 2P 2N 3P 3N 4P 4N 5P 5N 6P 6N 7P 7N 8P 8N 9P 9N S10P S10N S11P S11N S12P S12N S13P S13N S14P S14N S15P S15N o CO C C Q n PINOUTS 6 3 3 ARINC 708 The pin assignments for ARINC 708 modules are listed in Table 6 4 below Each channel can use either of two buses which are shared between adjacent receive and transmit channels Thus receive channel 0 can listen to either bus one of which could have the transmissions from channel 1 Be sure to follow the cou pling and termination guidelines provided in A
5. modular architecture of the OmniBus OmniBus PCI cPCI User s Manual 1 1 INTRODUCTION Avionics Avionics Databus Databus P1 P2 Protocol Protocol Module Module DSP Core A DSP Core B PowerPC Memory Processor SDRAM Flash Host Interface Host Computer Figure 1 2 The two core architecture of OmniBus PCI 3U cPCI products OmniBus products can be purchased with or without the capability to run user code on the PowerPC processor to offload the host computer An IRIG circuit allows channels boards and computers to be synchronized in time to each other and to external devices The easiest way to operate the OmniBus is with CoPilot amp Ballard Technology s graphical interface software Alternately software developers can write their own software applications using the included BTIDriver API Application Program Interface 1 2 OmniBus Configurations The OmniBus family includes products with many different host platform proto col and channel count combinations A given OmniBus part number is produced in the factory by mounting protocol specific modules on the required host plat form and loading module specific firmware for the DSPs Note OmniBus products are not user configurable Do not attempt to swap one module type for another one with a different part number If a module is exchanged it must be with an i
6. through a wrist strap Each circuit card is shipped in an anti static bag and should be stored in a similar container when not installed in the computer 2 4 Step 1 Review the Driver Installation Procedure The driver installation procedure varies depending on the type of board and your computer s operating system These procedures are kept on disk so they can be easily updated as operating systems evolve Before proceeding with the installa tion find print and review the driver installation procedure for your operating system Having a printed copy will facihtate the driver installation when you get to that step The driver installation instructions are in a README TXT file on the distribution disk in a folder specific to your board and operating system Follow these steps to locate and print the instructions 1 Insert the disk in your drive and browse to the folder for your product e g OMNICPCI for an OmniBus cPCI product 2 Open DRIVERS subfolder e g OMNICPCIDRIVERS OmniBus PCI cPCI User s Manual 2 1 INSTALLATION 3 Open the subfolder for your operating system e g OMNICPCI DRIVERS WIN2K 4 Printthe README TXT file in the operating system subfolder Because your system may automatically detect the newly inserted OmniBus card and initiate driver installation it 15 a good idea to have the distribution disk in your disk drive and a printed copy of the driver installation procedures in hand before you p
7. BCD values in days hours minutes seconds etc and can be synchronized to date and time of day This allows timing data from all cores and external devices to be easily correlated When IRIG time is enabled on a core all time tags associated with the core are 64 bit IRIG values that specify days down to microseconds In time tag fields the 32 bit binary timer value is re placed by the low 32 bits of IRIG time and an additional 32 bit field is allocated for the high 32 bits of IRIG time Each OmniBus core has its own IRIG timer circuit that generates the 64 bit IRIG time value IRIG timers are free running and individually keep time until either set by software or synchronized to an IRIG signal To synchronize to an IRIG signal the IRIG timer must be configured in software as a slave The source of the IRIG signal 15 the master which can be an IRIG timer in another core or an external device There can be only one master in the system The IRIG signal from the master resynchronizes the IRIG slaves from one to ten times per second Note that since the 64 bit IRIG time value has a resolution down to one micro second and the clocks in the master and slave can vary in accuracy there can be a slight underflow or overflow in the least significant digits of the IRIG value each time it is resynchronized OmniBus PCI cPCI User s Manual 4 1 OMNIBUS FEATURES The IRIG circuit in each OmniBus core can be configured as either a master or a slave An i
8. You may reach us by telephone at 800 829 1553 or 425 339 0281 by fax at 425 339 0915 on the Web at www ballardtech com or through e mail at support a ballardtech com 1 6 Updates At Ballard Technology we take pride in high quality reliable products that meet the needs of our customers Because we are continually improving our products periodic updates to documentation and software may be issued Please fill out and return the product registration card included in the front of this manual so that we can keep you informed of updates customer services and new product information 1 4 OmniBus User s Manual 2 INSTALLATION This chapter explains procedures for installing your PCI OmniBus product There are five steps to installation 1 Print and review the driver installation procedure from the software distribu tion disk Insert the OmniBus into an empty slot in your computer Install the appropriate software driver Test installation of card and drivers by running BTITST32 EXE Connect the OmniBus to the databus es ot After the Installation steps are completed the OmniBus is ready to communicate on the databus es using either CoPilot or a custom software application see Chapter 3 WARNING Static Discharge As with most electronic devices static discharge may damage or degrade components on a circuit card When handling a circuit card the user should be grounded e g
9. a local area network LAN interconnects computers in an office Data from one device is passed over the network to other devices that need it There are a number of military and commercial avionics databus standards The OmniBus supports the most common protocols which are briefly described below MIL STD 1553 is the protocol for military aircraft and other military and commercial applications It is a digital command response time division multiplexing databus protocol ARINC 429 one of the most prevalent ARINC Aeronautical Radio INCor porated standards defines the transfer of digital data between commercial avionics systems It uses broadcast bus topology and a label identification method for data words ARINC 575 is the specification for a Digital Air Data System DADS ARINC 575 includes a databus protocol almost iden tical to ARINC 429 ARINC 708 defines an airborne pulse Doppler weather radar system for commercial aircraft The Transmitter Receiver unit sends data over the 708 display databus to the Control Display Unit Data consists of 1600 bit words that are preceded and followed by a sync The display databus 1s an adapta tion of the proposed but never approved ARINC 453 databus e ARINC 717 includes the databus protocol for interconnecting the Digital Flight Data Acquisition Unit DFDAU and the Digital Flight Data Recorder DFDR Data words are 12 bits long and are nominally transmitted at 64 or 256 words per
10. and 7 7 microseconds for 1553B the default protocol in 11553 RTConfig Any value below the minimum yields the minimum The default RT response time for OmniBus modules is approxi mately 9 microseconds a value of 90 The exact response time depends on sev eral factors such as where on the bus it 1s measured analog and digital delays in the on board circuits and uncertainty due to the 100 nanosecond sampling time 5 2 8 Variable Transmit Amplitude For OmniBus 1553 level D channels the amplitude of the transmitted databus signal can be varied under software control The 12 bit amplitude has a resolu tion of 8 bits so the least significant 4 bits are don t cares The full scale value of FFOh is the default setting Since the actual amplitude and linearity depend on both the line driver and load the user must calibrate with the conditions in use for the degree of accuracy desired Some line drivers are not capable of putting 5 2 OmniBus User s Manual MODULE CONFIGURATIONS out very low voltages be sure to verify the output under your operating condi tions 5 2 4 Zero Crossing Distortion On level D channels a zero crossing of the transmitted signal can be shifted from its normal position under software control This feature allows a specific zero crossing to be shifted up to plus or minus 250 nanoseconds in increments of 5 ns zero crossing shift can be generated on the leading or mid bit zero crossing
11. can host up to two modules one per core OmniBus PCI and cPCI carrier boards are listed in the table below Part No Description 111 PCI w 1 core 112 PCI w 2 cores 121 3U cPCI w 1 core 122 3U cPCI w 2 cores 5 2 MIL STD 1553 Modules MIL STD 1553 modules can have one or two dual redundant databuses chan nels The part numbers for 1553 modules start with 5 e g 511 The second digit identifies the level of 1553 channel 0 and the third digit identifies the level of 1553 channel 1 a zero indicates no second bus The table below illustrates standard single and dual channel 1553 modules In addition any mix of levels may be ordered on a dual channel module Part No Level Level 510 A 520 B4 530 B32 540 C 550 511 522 B4 B4 533 B32 B32 544 C C 555 D D Each MIL STD 1553 channel is available in five levels of functionality summa rized in the table below levels provide at least single terminal Bus Control OmniBus PCI cPCI User s Manual 5 1 MODULE CONFIGURATIONS ler Remote Terminal and Monitor operation and user configurable R T response time Advanced features include multi terminal simulation up to 32 with con current monitoring and protocol error injection word gap and message errors Level D MIL STD 1553 modules provide variable transmit amplitude and zero crossing distortion
12. coupler that 1solates the stub from the main databus and reduces signal reflections The signal level on the main bus is the same for both direct and transformer coupling Though it is rarely done systems can mix the use of direct and transformer coupling A terminal must be properly configured for either direct or transformer coupling There is a difference between the terminal s internal interface circuit for direct and transformer coupling The transformer coupled terminal has a lower turns ratio and no isolation re sistors but this 15 made up for in the external coupler which has a step up transformer and isolation resistors see Figure A 1 direct coupled terminal has a higher turns ratio and has isolation resis tors that are connected directly to the main databus Direct coupled stubs should be kept as short as possible see Figure A 2 OmniBus PCI cPCI User s Manual A 1 COUPLING AND TERMINATION SHIELDED TWISTED PAIR CABLE Bus B F gt C 14 7 3 E SINGLE STUB TRANSFORMER COUPLERS TRANSFORMER BT P N 17011 COUPLERS TERMINATORS OR DIRECT BT P N 17001 CONNECTIONS Bus A A k lt c TERMINAL TERMINAL i e TWINAX CABLE STUB 16013 Terminol Figure A 1 Transformer coupling to a dual redundant databus A 2 OmniBus PCI cPCI User s Manual COUPLING AND TERM
13. is the user s guide for PCI and cPCI models of Ballard Tech nology s OmniBus family of products This guide introduces the OmniBus discusses special OmniBus features describes the installation process and refer ences programming alternatives 1 4 OmniBus Overview OmniBus is a family of products that enable computer systems to communicate with avionics databuses for the purpose of testing simulation and or operation Each OmniBus unit can support more than one protocol and a large number of channels They are available as an interface card for popular computer standards PCI cPCI PXI VME etc and as a stand alone bridge to other communications protocols USB Ethernet All common avionics databus protocols are sup ported including MIL STD 1553 ARINC 429 ARINC 708 and ARINC 717 Other protocols such as ARINC 575 ARINC 573 ARINC 453 etc are also supported Custom protocols are implemented upon request Figure 1 1 cPCI and PCI boards The high density modular design of the OmniBus family provides flexibility that enables the user to select from many protocol platform and channel count com binations Each OmniBus product can have at least two modules and each mod ule has its own DSP to handle the channels and protocols attached to it see Figure 1 2 The high channel count and mixed protocol capabilities can be fully exploited without the risk of overloading the DSP Figure 1 2 illustrates the
14. modules 6 3 2 ARINC 429 The pin assignments for OmniBus ARINC 429 modules are listed in Table 6 3 below Note Module 435 in the table below also includes ARINC 717 chan nels See Table 6 5 for pinouts of the 717 channels on this module ARINC 717 bipolar receive channels 4 through 7 and ARINC 429 re ceive channels 0 through 3 share the same four bipolar receivers so each ARINC 429 receive channel is only available when the corre sponding 717 receive channel is configured for biphase OmniBus PCI cPCI User s Manual 6 3 PINOUTS Channel Configurations by Part Number s 427 434 424 I2R AT 8R 8T 4R I2T OR 16T 16R 0T R R R R R R R R TI TI TI TI TI Te Te TT R receive and T 4 4 4 4 transmit 426 428 8 0 4R 4T OR 8T See Table 6 5 for ARINC 717 pinouts on 435 Chan nel Q X N Q Q M Name 512 gt o0 92 Z Vl Zz Z Sale Cy 1 Zi 1 1 2 72 OA TT 9 Crepe SE EE 15 15
15. Data can also be entered and viewed as virtual instruments knobs dials gauges etc that can be created by the user or automatically gener ated by dragging and dropping an item into the Control View window Because CoPilot can host multiple channels and databus protocols in the same project it is the ideal tool for operating OmniBus products CoPilot can be pur chased separately or with an OmniBus product For more information or a free evaluation copy call Ballard at 800 829 1553 In addition you can learn more about the latest version of CoPilot at www ballardtech com gt Example CoPilot Plus File View Project Window Help 011818 8 5 gt a 880 BUSBox1 CDV BUSBox Card 1 2 ARINC 708 0 1 Receive 0 BS Recorded Weather 4449 Msg 4 Receiver Channel 4 ARINC 423 gt Receiving Air Data System 706 C Altitude 1013 25 mB 203 True Airspeed 210 EB Simulating Attitude and Heading Re Wind Speed 015 Track Angle Magnetic 053 5 Transmitter Channel 7 ARINC 429 Sequential Monitor 1156 items 89 BUSBox2 CDV BUSBox Card 0 52 4 MILSTD 1553 Channel D Version 5 28 Bus Controller BC BD BC Messages 5 38 ATs i i RT01 INS Navige SAO Hea True Heading 014 Track Ang 03 221 Eel RT01 SA02 RX 563 knots Wind Speed 03 64 Atitude 01 01 15 351 Track n
16. INATION m TERMINATORS BTP N 17001 BTP N 17002 TEADAPTRS UNIT UNDER Figure 2 connection to a dual redundant databus OmniBus PCI cPCI User s Manual A 3 COUPLING AND TERMINATION This page intentionally blank A 4 OmniBus PCI cPCI User s Manual APPENDIX REVISION HISTORY The following revisions have been made to this manual Preliminary Version 1 Date January 31 2003 Preliminary release of this manual covering only ARINC 429 and 708 modules Date June 12 2003 Initial release of this manual OmniBus PCI cPCI User s Manual B 1 REVISION HISTORY This page intentionally blank B 2 OmniBus PCI cPCI User s Manual
17. OmniBus PCI cPCI USER S MANUAL INTERFACE CARD to AVIONICS DATABUSES June 12 2003 Rev A Copyright 2003 by Technology 3229A Pine Street Everett WA 98201 USA Phone 800 829 1553 425 339 0281 Fax 425 339 0915 E mail support ballardtech com Web www ballardtech com MA141 061203 Copyright 2003 by Ballard Technology Inc Ballard Technology s permission to copy and distribute this manual is for the purchaser s private use only and is conditioned upon purchaser s use and application with the OmniBus hardware that was shipped with this manual No commercial resale or outside distribution rights are allowed by this notice This material remains the property of Ballard Technology All other rights reserved by Ballard Technology Inc SAFETY WARNING Ballard products are of commercial grade and therefore are neither designed manufactured nor tested to standards required for use in critical applications where a failure or deficiency of the product may lead to injury death or dam age to property Without prior specific approval in writing by the president of Ballard Technology Inc Ballard prod ucts are not authorized for use in such critical applications INTERFERENCE This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the instructions manual may cause interference to radio communications Opera
18. PLING AND TERMINATION Coupling and termination only apply to OmniBus modules for MIL STD 1553 and ARINC 708 Electrically these databuses have similar characteristics Ex cept where a protocol 15 specified the following discussion applies to both A 1 Bus Termination The main databus consists of a pair of twisted shielded wires with a characteris tic impedance in the range of 70 to 85 ohms The databus must be terminated at both ends with a resistor to provide proper loading and to minimize signal reflec tion and degradation on the bus The resistor value should be close to the charac teristic impedance of the databus The resulting total load on the databus is the two terminating resistors in parallel about 39 ohms Even with a very short da tabus the load from the terminating resistors 15 still required Notice how the re sistors terminate the databuses in Figure and Figure A 2 Note that some Ballard products have on board termination resistors that can be switched in manually or under software control Note The most common problem in a new system is an improperly terminated databus A 2 Transformer versus Direct Coupling MIL STD 1553 can be either direct or transformer coupled Most military 1553 systems are transformer coupled ARINC 708 however is normally direct cou pled Both protocols have a transformer as part of the terminal s interface but 1553 transformer coupling has an additional external transformer
19. Section 6 4 If you are using MIL STD 1553 or ARINC 708 be sure to follow the coupling and ter mination guidelines discussed in Appendix A OmniBus PCI cPCI User s Manual 2 3 INSTALLATION 2 4 This page intentionally blank OmniBus PCI cPCI User s Manual 3 OPERATION Software 1s used to control the OmniBus and to manipulate data Whether you use Ballard s CoPilot amp software or develop your own applications using Bal lard s BTIDriver API library it is easy to operate the OmniBus and utilize its powerful interface 3 1 CoPilot A PC with CoPilot and Ballard s OmniBus makes a powerful low cost databus analyzer simulator CoPilot interfaces directly with the OmniBus eliminating the need to write custom software CoPilot greatly simplifies such tasks as defining and scheduling bus messages and capturing and analyzing data CoPilot is a Win dows based program that features a user friendly GUI Graphical User Interface and many timesaving features For example bus messages can be automatically detected posted in the hardware tree and associated with the appropriate attributes from the database of equipment message and engineering unit specifications CoPilot users can quickly configure run and display the activity of multiple da tabuses in a unified view Data can be observed and changed in engineering units while the bus is running The Strip View graphically illustrates the history of the selected data values
20. ady be installed you can run the test pro gram described in Section 2 4 If the OmniBus passes the test program the driv ers are properly installed Once you have installed the drivers you can usually remove and reinsert the OmniBus without having to reinstall them 2 4 Step 4 Test the Installation You can test the installation and functionality of your OmniBus by running the BTITST32 EXE program provided on the installation disk This program ana lyzes the OmniBus within several seconds If the program does not detect any faults with the interface or the OmniBus hardware it displays a passed test message BTITST32 EXE also displays important information about your card such as the assembly part number configuration and card number If you have multiple 2 2 OmniBus PCI cPCI User s Manual INSTALLATION cards installed you can differentiate them by turning the LED on and off through the LED option in BTITST32 EXE right click on the Device icon in the tree Card numbers are used by application software to uniquely identify each Omni Bus card They are assigned automatically by the host when the cards are in stalled The card numbers may change depending on the position and number of cards used Changing slots or removing cards when multiple cards are installed may change the card number assigned to a particular OmniBus card As long as the number of cards 15 constant and the cards are not moved the associated card numbers r
21. are available for single or dual channel modules and with or without a D sub connector of them provide a twinax cable from the LFH connector to a PL 75 for each of the transformer coupled MIL STD 1553 buses All channels are dual redundant so there are either two or four twinax cables with PL 75s on each assembly Twinax cables are wired as shown in Table 6 8 6 8 OmniBus User s Manual PINOUTS CHO BUSOP BUS A CHOAXR BUSON CHO BUS3P BUS BUS3N CHI CHIAX BUSSP BUS A CHIAXR BUS8N CHI BUS B Braids connected between the LFH shell and the PL 75 shell Table 6 8 Twinax wiring on MIL STD 1553 cable assemblies The 25 pin female D subminiature connector provides IRIG and discrete signals as shown in Table 6 9 Consequently the recommended cable assemblies are 16037 for dual channel and 16039 for single channel MIL STD 1553 OmniBus modules From To Pair Name LFH Pin DB25S Pin 1 como 254 1 Es EX EN 5 ES ir Braids connected shell to shell Table 6 9 D sub connector pinout for cable assemblies 16037 and 16039 z gt Q Q le lel lelg 5 12 S 9 2 5 n Q G 5 lt 19 OmniBus PCI cPCI User s Manual 6 9 PINOUTS This page intentionally blank 6 10 OmniBus PCI cPCI User s Manual APPENDIX COU
22. c capability the transmit am plitude can be individually set in software for each channel The user specifies the channel and a 12 bit amplitude The full scale value of FFOh 15 the default setting The 12 bit amplitude has a resolution of 8 bits so the least significant 4 OmniBus PCI cPCI User s Manual 5 8 MODULE CONFIGURATIONS bits are don t cares Since the actual amplitude and linearity depend on both the line driver and load the user must calibrate with the conditions in use for the de gree of accuracy desired Some line drivers are not capable of putting out very low voltages be sure to verify the output under your operating conditions 5 8 2 Configurable Frequency Parametric ARINC 429 modules can be operated at non standard speeds This configurable frequency can be set in software for each transmit and receive chan nel Thus 429 channels may be used with equipment that varies from the ARINC 429 standard such as some implementations of ARINC 575 Use a bit rate configuration function to get a non standard frequency Contact Ballard Technology for the appropriate parameters for your module part number and desired frequency 5 4 ARINC 708 Modules The table below lists the I O modules available with ARINC 708 channels Part No 708 Channels Parametrics 810 1R 1T 811 2R 2T 820 R IT Amplitude 822 2R 2T Amplitude R receive and T transmit ARINC 708 modules are available wit
23. dard and others such as are optional If you need more information than 15 pre sented here please contact Customer Support at Ballard Technology for assis tance see Section 1 5 41 OmniBus products be ordered with the capability to run user code on IBM 405GP PowerPC coprocessor The BTIDriver API functions used in program ming the host can also be used by the PowerPC Thus a program can be devel oped to run on the host and later ported to run on the PowerPC One useful application for the PowerPC is to offload the host by performing computationally intensive manipulations on databus information such as would occur in a simula tor Code for the PowerPC can be either loaded and run each time the host applica tion runs or it can be saved in non volatile memory so that it runs automatically at power A special family of PowerPC BTIDriver API functions is used to load and configure the PowerPC Code 15 developed with user provided software and hardware tools Please consult Customer Support for a list of recommended compilers and debuggers 4 2 IRIG Time By default each OmniBus core creates a 32 bit time tag from a binary timer in the DSP Each OmniBus core has an IRIG timer circuit that can be used in place of the binary timer When a core is configured to use IRIG time all time records are in IRIG time The advantage of IRIG time is that it is human readable in bi nary coded decimal
24. dentical module OmniBus products may be upgraded with additional channels or protocols but this must be done at the factory The assembly part number characterizes the configuration of an OmniBus prod uct The assembly part number is designated by groups of characters separated by dashes The first group of characters in the assembly part number 15 the part number of the main PCI or cPCI card the second group is the part number of the 1 2 OmniBus PCI cPCI User s Manual INTRODUCTION module in the Core position and the third group is the part number of the module in the Core B position more detailed description of the individual part numbers may be found in Chapter 5 The complete assembly part number is printed on the main OmniBus board If the modules are visible each group of numbers in the assembly configuration that represent modules should match the part numbers printed on the correspond ing modules The configuration of an installed OmniBus product may be deter mined by running the test program described in Section 2 4 For future reference we encourage you to record the assembly part number and serial number of your OmniBus product You may wish to use the space provided below Assembly PN Board PN Core A PN Core B PN Serial No 1 3 Avionics Databus Protocols Avionics databuses interconnect various electronic equipment navigation con trols displays sensors etc on an aircraft much as
25. e transmit amplitude available for all 717 channels the user specifies the channel and a relative 12 bit amplitude The full scale value of FF0h is the default setting The 12 bit amplitude has a resolution of 8 bits so the least significant 4 bits are don t cares Since the actual amplitude and linearity depend on both the line driver and load the user must calibrate with the condi tions in use for the degree of accuracy desired Some line drivers are not capable of putting out very low voltages be sure to verify the output under your operat ing conditions OmniBus PCI cPCI User s Manual 5 5 MODULE CONFIGURATIONS This page intentionally blank 5 6 OmniBus User s Manual 6 PINOUTS The standard connector OmniBus products is 60 Molex LFH tacle Each OmniBus module core has connector dedicated to it Sig nals on the LFH connector are either general purpose or module specific General purpose signals including triggers syncs discretes and IRIG are common to most modules and protocols The databus signals are module specific in that their use and meaning depend on the protocol and functionality of the as sociated OmniBus module This chapter provides the information needed to con nect to the individual modules through the LFH connector Should your OmniBus product have a different connector or a module not listed here please consult other docume
26. emain constant for all cards Note At any time you may use BTITST32 EXE or the Windows De vice Manager to determine and or reassign the card numbers If BTITST32 test detects a fault it displays relevant fault information When the fault message displays follow the instructions on screen If you need further as sistance call Ballard Technology at 800 829 1553 A customer support engi neer will interpret the fault and guide you through corrective steps 2 5 Step 5 Connect the Databus es OmniBus connections to the databus es depend on the module type and the spe cial requirements for each protocol To find the connector pinout first determine the part number of the associated module core and then look in the appropriate table in Chapter 6 as described in the following paragraphs Look at the labels on your OmniBus card to find its assembly part number If you can see the individual modules compare the numbers on each module with the corresponding numbers in the OmniBus assembly number If there is a mismatch proper operation cannot be expected See Section 1 2 and Chapter 5 for more in formation on the meaning of OmniBus assembly part numbers Each core module has a 60 pin LFH connector dedicated to it they are desig nated P1 for Core A and P2 for Core B In Chapter 6 look up the pin assign ments in the table associated with each module Connect the databuses accordingly Connectors and standard cables are described in
27. gl 03 64 RT01 SA03 Tx Pres 215 Latitude 01 01 16 Longitude 02011 201 49 TrueHeadng 0 BB Broadcast 4750 deg Latitude 0 Bus Monitor A2242deg Longitude 0 7Ti2knots WindSpeed C NCoPilot Projects Example Project Example Running 01 24 Figure 3 1 Sample CoPilot screen OmniBus PCI cPCI User s Manual 3 1 3 2 User Developed Software Software developers can use the bundled BTIDriver API to create custom appli cations With only a few function calls a program can operate the OmniBus and process messages to and from the avionics databus Functions include routines for transmitting receiving scheduling recording data manipulation and time tagging bus messages Although most tasks require only a few API calls the comprehensive library includes a broad range of functions for specialized needs Sample programs and utility programs are included with the API on the software distribution disk Detailed information about each API function and instructions on programming for the OmniBus is found in the separate manuals for each pro tocol e g ARINC 429 Programming Manual for BTIDriver Compliant De vices 3 2 OmniBus User s Manual 4 OMNIBUS FEATURES This section describes special capabilities and interface signals available on many OmniBus products Some of these features such as IRIG time are stan
28. h one receiver and one transmitter or two receivers and two transmitters ARINC 708 channels communicate on the air borne pulse Doppler weather radar display databus Each channel can be inde pendently switched to operate on either of two buses All channels can be configured for variable bit length Parametric versions of ARINC 708 modules have variable transmit amplitude 5 4 1 Software Selectable Bus Termination Each databus on all OmniBus ARINC 708 modules has a 75 ohm termination re sistor that can be switched across the direct coupled terminals under software control Though direct coupling is standard for ARINC 708 transformer coupling may be used When transformer coupled the direct coupled termination resis tance must be off and external couplers and terminators are required See Ap pendix A for more information about bus termination and transformer versus direct coupling 5 4 2 Variable Bit Length All OmniBus ARINC 708 modules can support messages with user defined number of bits Variable bit length mode is software selected at the channel level Special functions are provided in the BTIDriver API to read and write messages with a bit count of 1 to 1865 116 x 16 This allows ARINC 708 channels to be 5 4 OmniBus User s Manual MODULE CONFIGURATIONS used with other transfer protocols that vary from the standard 1600 bit word display databus 5 4 8 Variable Transmit Amplitude On ARINC 708 modules with
29. iBus IRIG signals 4 3 Discretes OmniBus PCI cPCI products have both input and output discretes There are six discretes per core module and four board discretes discrete inputs and out puts for both board and cores are TTL level The discrete output driver is a 5 volt 74HCT244 the discrete input receiver is 5 volt tolerant device with a high in put impedance 10 leakage current Core discretes and board discretes de scribed briefly in the following sections 4 3 1 Core Discretes Syncs Triggers Core discretes can be used as general purpose I O or as trigger inputs and sync outputs for processes running on the core module Each core has three input and three output discretes all wired to the core s associated LFH connector Core discretes can be accessed through software running either on the host processor or on the PowerPC Ballard s BTIDriver API provides functions to read and write the core discretes The parameter dionum in the API functions BTICard ExtDIORd and BTI Card ExtDIOWT specifies which discrete to read or write When DIOn where n 420 2 00 00 OmniBus User s Manual OMNIBUS FEATURES is a number is described in other functions it is synonymous with dionum 1 n dionum A specific sync or trigger can use one or more of the core discretes After a core discrete has been allocated as a trigger or sync using the enable and mask pa rameters in a
30. iniature connectors P2 and P3 Because of the size and popularity of D sub connectors some users may find it easier to interface to them than to the OmniBus LFH connectors As can be seen from Table 6 1 there is symmetry between the upper and lower halves of the LFH connector On the 16036 cable assembly the upper half of the LFH connector is wired to one D sub and the lower half is wired to the other D sub thus giving similar signals on the corresponding pins of both D subs The wire pairs on the 16036 are different from those on the 16035 Wiring for the 16036 cable is shown in Table 6 6 below OmniBus PCI cPCI User s Manual 6 7 PINOUTS 28 2 BU BU BU BU BU BU 6 18 24 s m BU BU E EEN 11 CDIN0 GND m 19 24 mo U 0 or 1 depending on core A or B Braids connected shell to shell Table 6 6 Wiring chart for 16036 cable assembly 6 4 3 MIL STD 1553 cable assemblies Ballard offers four standard cable assemblies for MIL STD 1553 see Table 6 7 below The standard length is three feet Cable Assy No No of Ch D Sub 16037 2 v v v 16038 2 v v 16039 1 v v 16041 1 v Table 6 7 MIL STD 1553 cable assembly configurations These four cables
31. ion Procedure 2 1 2 2 Step 2 Insert the Card secedere edi te feet 2 2 2 3 Step 3 Install the 2 2 2 4 Step 4 Test the Installation 2 2 2 5 Step 5 Connect the 2 3 OPERATION SF SCOP Obs EE 3 1 3 2 User Developed Software 3 2 4 OMNIBUS FEATURES 4 1 PowerBQ iiec teet n er ere e Hee 4 1 4 IRIG Time etti tetendit te e teer 4 1 4231 nDISCIeteS eee 4 2 4 3 1 Core Discretes Syncs and Triggers seen 4 2 432 Board Discretes s a s U Spa EUR EOS 4 3 5 MODULE CONFIGURATIONS 5 1 5 11 OmniBus PCI and cPCI 5 1 52 MIE STD 1553 Modules 5 iecit nett 5 1 5 2 1 Software Selectable Bus Termination 5 2 5 2 2 Configurable RT Response 5 2 5 2 3 Variable Transmit Amplitude 5 2 5 24 Zero Crossing Distortion HERE ee ETE sisa 5 3 53 ARING 429 Modules uu erret tree tne 5 3 5 3 1 Variable Transmit Amplitude 5 3 5 3 2 Configurable 5 4 5 4 ARINC 708 Modules 5 4 5 4 1 Software Selectable Bus Termination 2 5 4 5 4 2 Variable Bit Length 5 4 5 4 3 Variable Transmit Amplitude 5 5 Om
32. lar HE P2 15 BUSON bipolar bipolar P2 14 BUSIN sien e 9 a s penus bipolar bipolar awe Ses P2 16 BUS2N eie C Pa s roa bipolar P2 17 BUS3N mn TUM 2 bipolar bipolar EHESE3 P3 18 BUS12N biphase biphase bipolar bipolar P3 19 BUSI3N biphase biphase CH14 bipolar bipolar P3 20 BUSI4N biphase biphase CHI5 bipolar bipolar 53 P3 21 BUSISN R receive and T transmit See Table 6 3 for the ARINC 429 pinouts for PN 435 Table 6 5 Pinouts for ARINC 717 modules OmniBus User s Manual PINOUTS 6 4 Standard Cables Ballard sells a number of different cables that are useful for wiring to OmniBus products Each cable has a standard length Non standard lengths may be speci fied by adding a xx suffix after the part number where xx is the length in feet For example a 16035 10 is a ten foot long 16035 6 4 1 PN 16035 cable assembly LFH to LFH This is a three foot long straight through cable with 60 pin male LFH plugs on both ends It is wired pin for pin and pair for pair as shown in Table 6 1 The 16035 is useful for connecting an OmniBus product to a user provided panel or other assembly 6 4 2 PN 16036 cable assembly LFH to two 25 pin D subs This is a three foot long Y cable that adapts a 60 pin male LFH plug labeled P1 to two 25 pin male D subm
33. niBus PCI cPCI User s Manual i TABLE OF CONTENTS 5 5 ARING 717 Sau uuu ohh Suman ROI S RR IR Dd retta 5 5 5 5 1 Variable Transmit Amplitude essere 5 5 6 CONNECTOR PINOUTS 6 1 6 1 Interface Connector issued He e ege eR ie 6 1 62 dat deett demque 6 1 6 3 Module Specific Wiring 6 2 6 27 MILES D215 53 5 5 6 3 632 pire ut u Ep Ela 6 3 633 085 eoe et Re a re eU RE AR td 6 5 63 ARINGC Io u m REO len Fe UR 6 6 6 4 Standard Cables n s te eta iban eri uyak 6 7 6 4 1 PN 16035 cable assembly to LFH seen 6 7 6 4 2 PN 16036 cable assembly to two 25 pin D subs 6 7 6 4 3 MIL STD 1553 cable assemblies 6 8 APPENDIX A COUPLING AND TERMINATION 1 Termination Hep ee ecd ed 1 A 2 Transformer versus Direct A 1 APPENDIX B REVISION HISTORY B 1 OmniBus PCI cPCI User s Manual 5 LIST OF FIGURES Figure 1 1 OmmiBus cPCI and PCI boards 1 1 Figure 1 2 The two core architecture of OmniBus PCI and 30 cPCI products 1 2 Figure 3 1 Sample CoPilot 8
34. ntation provided with the product or call Customer Support at Ballard Technology Ballard offers a number of special cable assemblies to facilitate the use of their OmniBus product line 6 1 Interface Connector The user interface connector on OmniBus products is a Molex 60 pin LFH recep tacle Molex PN 70928 2000 The recommended mating connector is a cable plug assembly consisting of a frame subassembly Molex PN 70929 2000 and four terminal strips Molex PN 51 24 2022 For more information consult www molex com Appropriate shields strain reliefs and backshells are also re quired The LFH is a high density connector about the size of a 15 pin D subminiature connector For proper clearance from adjacent connectors the overall length of each LFH connector including any backshell molding must not exceed 1 64 inches 6 2 General Pinout OmniBus products have the basic pin designations shown in Table 6 1 Note that wiring is done in pairs 30 pairs total Especially on databus signals labeled BUSxx in Table 6 1 be sure to use twisted pairs to avoid cross talk The suffix on the designations for databus signals in Table 6 1 represents the polarity P for positive and N for negative The use and meaning of databus signals depends on the protocol and functionality of the associated OmniBus module as indicated in Section 6 3 OmniBus PCI cPCI User s Manual 6 1 PINOUTS
35. nternal IRIG bus connects all the cores within an OmniBus product This internal IRIG bus goes to a bidirectional buffer that 15 wired to all the IRIG pins on the LFH connectors Note that all these external IRIG signals are com mon i e electrically connected together across all LFH connectors on the Om niBus product The IRIG pins on the LFH connectors are driven by the bi directional buffer only when one of the IRIG core circuits is configured as a master An IRIG core that is configured as an external slave will expect the IRIG signal to come from an external device 1 on the IRIG pin of one of the connectors Otherwise if the IRIG core is an internal master or internal slave it uses the internal bus There are a number of formats for IRIG time OmniBus products use the formats indicated in Table 4 1 The characteristics of the external electrical interface to the IRIG pins are as shown in Table 4 2 A 1000 pps F t arse B 100 pps Modulation Frequency 0 Pulse width coded Frequency Resolution 0 No carrier index count interval 2 Master output E Coded Expressions 0 1 2 3 Slave Uses only BCD field input Table 4 I IRIG formats used by OmniBus Input impedance min 12 Input level 0 to 5 volts Input level threshold 1 5 volts Output level 0 to 3 volts Output drive capability 40 Table 4 2 Electrical characteristics of Omn
36. of a specified bit position in a specified word 5 3 ARINC 429 Modules The table below lists the I O modules available with ARINC 429 channels Part No 429 Channels Parametrics 421 16R 0T 422 12R 4T _ 423 8R 8T _ 424 4R 12T _ 425 OR 16T 426 8R 0T _ 427 4R 4T _ 428 OR 8T _ 434 4R 4T Amp Freq 435 4R 4T Amp Freq 438 8R 8T Amp Freq R receive and T transmit 435 also includes ARINC 717 channels Module 435 includes ARINC 717 channels as described in Section 5 5 Note that each ARINC 429 receive channel on the 435 module is only available when the corresponding 717 receive channel is configured for biphase see the wiring information in Section 6 3 for more details ARINC 429 modules are available in many combinations of receive transmit channels and features All ARINC 429 receive channels feature automatic speed detection and independent label and SDI filtering Each transmit channel auto matically maintains accurate label repetition rates To support data transfer pro tocols aperiodic words may be transmitted without altering the timing of periodic words Both receive and transmit channels may be independently set for standard low or high speed 12 5 or 100 Kbps OmniBus ARINC 429 channels with parametric capability have variable transmit amplitude and user configurable frequency 5 8 1 Variable Transmit Amplitude On OmniBus ARINC 429 modules with parametri
37. ower up your computer Aborting the automatic driver installation process before completion can necessitate manual installation of the driver 2 2 Step 2 Insert the Card OmniBus PCI and cPCI products are plug and play devices so no jumpers or switches are used to configure them Be sure to follow good ESD electrostatic discharge procedures see the static discharge warning at the beginning of this chapter To insert the card do the following e Shut down your computer e For PCI cards Insert the card s into an empty PCI slot and with a screw secure it to the case of your computer For cPCI cards With the injector handle in the down position insert the card s into an empty peripheral slot marked with a circle in your Com pactPCI or PXI system While pressing the bottom of the handle against the horizontal rail of the subrack move the injector handle up to lock the card in place Secure the screw located at the top of the front panel e Restart your computer 2 3 Step 3 Install the Driver To install the driver software follow the instructions printed from the README TXT file in Step 1 Section 2 1 The installation procedure copies several files into the host computer system and modifies the system registry If you encounter problems have installation questions or cannot find a folder for your operating system contact Ballard Technology Customer Support at 800 829 1553 If you think that the drivers may alre
38. parametric capability the amplitude of the transmit ted databus signal can be varied under software control The full scale value of FFOh is the default setting The 12 bit amplitude has a resolution of 8 bits so the least significant 4 bits are don t cares Since the actual amplitude and linearity depend on both the line driver and load the user must calibrate with the conditions in use for the degree of accuracy desired Some line drivers are not capable of put ting out very low voltages be sure to verify the output under your operating condi tions 5 5 ARINC 717 Modules The table below lists the I O modules available with ARINC 717 channels Part No 717 Channels 717 Parametrics 431 4R 4T Amplitude 435 4R 4T Amplitude R receive and T transmit 435 also includes ARINC 429 channels Module 435 includes ARINC 429 channels as described in Section 5 3 Note that each ARINC 429 receive channel on the 435 module is only available when the corresponding 717 receive channel is configured for biphase see the wiring information in Section 6 3 for more details Both the 431 and 435 modules have four receivers and four transmitters All OmniBus ARINC 717 channels are capable of operating at 64 128 256 512 1024 2048 4096 and 8192 wps and may be software configured as biphase or bipolar All transmit channels have variable amplitude capability 5 5 1 Variable Transmit Amplitude To use variabl
39. ppendix A Direct coupling is standard for ARINC 708 but transformer coupling is possible Used on Modules CHO R R CHI T CHI T n a CH2 R CH3 T LFH LFH 16036 LFH 810 820 811 822 Description Pair f Pin Pin Name m m m m m m m m m m m BU m m m m m m m m BU m m m m m m m au m US B transformer coupled BUS B transformer coupled 28 57 P3 17 BU SIP Table 6 4 Pinouts for ARINC 708 modules OmniBus PCI cPCI User s Manual PINOUTS 6 3 4 717 The pin assignments for the ARINC 717 modules are listed in Table 6 5 below All ARINC 717 channels can be either biphase or bipolar but note that 717 re channels have different pin assignments for biphase and bipolar ARINC 717 transmit channels use the same pin assignments for both biphase and bipolar Note Module 435 in the table below also includes ARINC 429 chan nels See Table 6 3 for pinouts of the 429 channels on this module Bi polar ARINC 717 channels 4 through 7 and ARINC 429 receive channels 0 through 3 share the same four bipolar receivers so each ARINC 429 receive channel is only available when the corresponding 717 receive channel is configured for biphase 431 435 LFH LFH 16036 LFH 4R 4T 4R 4T Channel E 7 P2 6 6 BUSAP deus CM P2 18 BUSAN R R P2 3 BUSOP bipolar bipo
40. s may be used only as general purpose I O and are only accessible through software running on the PowerPC Each OmniBus has two input and two output board discretes one each per LFH connector Table 4 4 below shows how the board discretes are distributed between the two core LFH connectors The names for board discretes are prefixed by BD e g BDOUTI Hardware LFH Core Reference Pin number BDINO P1 41 A 0 BDINI 2 41 B 1 BDOUTO P1 43 A 0 BDOUTI P1 43 B 1 Table 4 4 Designators for board discretes OmniBus PCI cPCI User s Manual 4 3 OMNIBUS FEATURES This page intentionally blank OmniBus User s Manual 5 MODULE CONFIGURATIONS OmniBus modules are available for many different protocols including MIL STD 1553 ARINC 429 575 ARINC 708 453 and ARINC 717 573 Other stan dard and custom modules are available This appendix lists the part numbers for PCI cPCI boards and for MIL STD 1553 ARINC 429 717 and ARINC 708 I O modules and describes the features and functionality of each Note OmniBus products are not user configurable Do not attempt to swap one module type for another one with a different part number If a module is exchanged it must be with an identical module OmniBus products may be upgraded with additional channels or protocols but this must be done at the factory 5 1 OmniBus PCI and cPCI Boards The PCI short and cPCI 3U OmniBus products
41. second in subframes frames and sometimes superframes ARINC 573 an older equipment specification for flight data recorders uses a databus similar to 717 These and other standards are not limited to use in aircraft They are used in many other military and industrial applications such as surface and space vehi cles process control nuclear research and oil exploration OmniBus PCI cPCI User s Manual 1 3 INTRODUCTION 1 4 Other Documentation Besides this manual Ballard provides other documentation to facilitate operation of the OmniBus interface These include protocol manuals information on the software distribution disk and CoPilot documentation Separate BTIDriver API programming manuals are available for each avionics protocol These manuals provide information on the specific protocol and include basic and advanced programming instructions for users who intend to write their own software They also contain a comprehensive reference for each function The software distribution disk accompanying the OmniBus has example pro grams drivers and driver installation instructions for various operating systems and other information files and resources 1 5 Support and Service Ballard Technology offers technical support before and after purchase Our hours are 9 00 AM to 5 00 PM Pacific Time though support and sales engineers are often available outside those hours We invite your questions and comments on any of our products
42. sync or trigger define API function the line may no longer be used to as a discrete output or input More than one core discrete each with an indi vidually specified polarity may be used in combination to define a sync or trig ger state For instance a trigger may be defined as a particular state of only one input or it may be defined as a particular combination of two or three inputs Other triggers and syncs may use the same or different combinations of these lines Refer to the BTIDriver software manuals for more information on pro gramming these discretes and their use as syncs and triggers Table 4 3 below shows the correlation between dionum the output pin and its hardware reference designator The last column shows how these discretes are used as trigger inputs and sync outputs in the BTIDriver API functions The names for core discretes are prefixed by CD e g CDIN2 Hardware LFH Pin API API Reference or P2 dionum usage CDINO 11 1 Trigger CDINI 21 2 Trigger B CDIN2 51 3 Trigger C CDOUTO 13 5 Sync A CDOUTI 19 6 Sync B CDOUT2 49 7 Sync C Table 4 3 Hardware versus software designation of core discretes Processes that are configured to be triggered by an external trigger can be trig gered through software using the BTICard CardTriggerEx function This is use ful for software testing and does not require external trigger equipment 4 3 2 Board Discretes Board discrete
43. tion of this equipment in a resi dential area is likely to cause interference in which case the user at their own expense will be responsible for taking whatever measures may be required to correct the interference TRADEMARKS CompactPCI is a registered trademark of PCI Industrial Computer Manufacturers Group Inc PICMG Power is a registered trademark of International Business Machines Corporation Molex amp LFH M is a trademark of Molex Inc Windows is a registered trademark of Microsoft Corporation OmniBus and CoPilot are registered trademarks of Ballard Technology Inc BTIDriver is a trademark of Ballard Technology Inc All other product names or trademarks are property of their respective owners Ballard Technology 29 Pine Street Everett WA 98201 USA Phone 1 800 829 1553 425 339 0281 Fax 425 339 0915 E mail support ballardtech com Web www ballardtech com TABLE OF CONTENTS AINIRODUCTION 1 1 OmniBus 1 1 1 2 OmniBus 8 1 0 2412040412441 40600000000000000000000 1 2 1 3 Avionics Databus Protocols 1 3 1 4 Other Documentation u nene e RR ERR 1 4 1 5 Supportand Service eie eei e 1 4 1 6 Updates aq n A hil a 1 4 2 INSTALLATION 2 1 Step 1 Review the Driver Installat
Download Pdf Manuals
Related Search