Home

National Instruments 370551A-01 Network Card User Manual

1. O HL t nud 5 8 rr 0 gee f Lu gs x ERIT IM Ts 5 pu 8 2 onm E g i 8 6 11 58 in M il E Ei e R174 a 33 3 pu E 5 y ce m 3 m 3 WU _ us 3 Q Sji 9 mire z 8 rum B IT muU og e O de w58 B g mer e E 8 ao 8 F 4 3 m Bu 8 m 2 9 U24 26 qe i gf n z B o 0 Be 5 2 0 2 OJE 173 wg 3 s E s 3 pa 3 2 5 Bu i p o 5 a 3 OU 2 n 5 3 5 8 cT in huo 8 d ig co T E 8 Sic 68 C65 MEL E Ey ws Fu Z FA Eg i bd EB E ae BE 5 gt i B 25 mom el 51 18 2 5 85 aum E leo 89 g X ig gs a 0 a w g d 9 BF wA 2 B 8 amp 3 Z 18 CM 06 Los st o g zs m g uod 2g 8 D x g SG u a m gt Coe Be 1 8 B 5 al ehg R cmn 2088 Ulp Ye SIMM SIZE 4 Y 32 AND LARGER m m Ye pig REZ ite ABC o ro UE VeL S gt lt uw o 8 ab 3 z a P Zo o Zo g Te
2. eeeeeeeeeeeeeeeeneneenen eene 5 2 Using the NI VXI NI VISA Software eese en eene eee eren 5 2 Completing the Software Installation esee eene 5 3 Chapter 6 NI VXI Configuration Utility Running the VXIedit Configuration Utility esee 6 1 PCI MXI 2 Configuration Editor essere enne 6 3 Update Current Configuration sseseeeeeeeeeeeee ee nn 6 4 Record Configuration to 6 4 Load Configuration from File eene eee 6 4 Revert to Current Configuration nenne 6 4 Logical Address Configuration Editor sese 6 4 D iceiSet ngs iae eate ER ees 6 5 Logical Address et eee 6 5 Device Type t ihe 6 6 Address Space t pe epe e 6 6 PCI MXI 2 for Linux viii ni com Contents VXI VME Shared Memory eese 6 6 VXI VME Shared RAM Size eee 6 7 Shared RAM Po0l 6 7 Advanced Shared RAM Settings 6 8 R source Manager Del y nr ete et 6 10 Resource Manager Delay eee 6 10 Default Controller LA 1 6 11 System 6 12 Servant Area S126 iv ota e tease pen eds 6 12 Number of Handlers tei eerie ertet 6 12 Number of Interrupters esses 6 13 Protocol Reglster epe eee ie ee idei
3. S5 MXIbus CLK10 Signal 57 Receive CLK10 from MXIbus MXlIbus Termination Automatic MXIbus termination U35 switches 1 and 2 switch 2 set to YES switch 1 ignored Configuration EEPROM User modifiable factory settings U35 switches 3 and 4 protected both switches set to NO DRAM SIMMs Installed Per customer order SIMM Size Configuration S6 OFF if SIMMS are 4 M x 32 or larger ON if smaller than 4M x 32 PCI MXI 2 for Linux 1 12 ni com Chapter 1 Table 1 6 VME MXI 2 Hardware Default Settings Hardware Component Default Setting A16 Base Address U20 Hex C040 VME MXI 2 Intermodule Signaling W2 No user defined pin selected MXlIbus Termination U21 switches 3 and 4 Automatic MXIbus termination switch 3 OFF switch 4 ignored Configuration EEPROM U21 switches 1 and 2 User modifiable factory settings protected both switches OFF DRAM SIMMs Installed Per customer order SIMM Size Configuration S2 OFF if SIMMS are 4 M x 32 or larger ON if smaller than 4 M x 32 Table 1 7 VXI VME MXI 2 Configuration Editor Default Settings Editor Field Default Setting Logical Address 1 set by hardware switch LA Selection Set by hardware switch Address Space A24 Requested Memory 16 KB A16 Write Posting Disabled A24 A32 Write Posting Disabled Interlocked Mode Disabled VXI VME System Controller Auto V
4. Transfer Limit Unlimited 2 VXImove uses Synchronous v Enable 2 Auto Retry Enable 24 A32 Write Posting PCI Bus Settings r User Window Size 64KB bed wv Driver Window Size 32KB m f Pes si wv IV Enable expansion ROM Cancel Default Figure 6 6 PCI MXI 2 Bus Configuration Editor MXI Bus The following sections describe the options for the MXI Bus portion of this editor MXI System Controller You can use the MXI System Controller control to determine whether the PCI MXI 2 acts as the MXIbus System Controller The three options are Auto Yes and No When the Auto setting is active the default setting the PCI MXI 2 automatically can sense from the MXIbus cable whether it should be the controller This setting requires that the cable is attached properly before making any NI VXI function calls or attempting to use the VXI VME MXI 2 Configuration Editor Refer to the Connect the MXIbus Cable section of Chapter 3 VME MXI 2 Configuration and Installation or the Connect the MXIbus Cable section of Chapter 4 VME MXI 2 Configuration and Installation 6 14 ni com Chapter 6 NI VXI Configuration Utility You can select the Yes or No options to manually determine whether the PCI MXI 2 should be the MXIbus System Controller You must still be certain to cable the MXIbus system appropriately when you make either of these selec
5. 2 Cable 4 Connection to Other Mainframes Figure 4 7 MXI 2 Cable Configuration Using a PCI MXI 2 and a VME MXI 2 When you have properly connected the MXI 2 cable power on the VMEbus mainframe and then the computer Note Always turn on the mainframe first Doing so makes it possible for your external computer to access the VME boards in the mainframe upon startup PCI MXI 2 for Linux 4 12 ni com NI VXI NI VISA Software Installation This chapter describes how to install and uninstall the NI VXI NI VISA software for Linux Installing the NI VXI NI VISA Software for Linux Before you begin you may need to install Linux on your computer Refer to the Linux documentation for instructions After your computer is booted into Linux you are ready to install the NI VXI NI VISA software To install NI VXI NI VISA for the PCI MXI 2 for Linux perform the following steps Insert the NI VXI NI VISA for Linux CD 2 Login to your system as root 3 Mount the CD ROM 4 change the current directory to the mounted CD ROM type the following command cd mnt cdrom 5 the installation script type the following command INSTALL The INSTALL places NI VXI and NI VISA in their default locations The script uses rpm to install the packages on systems that support it or extracts the files directly on other systems The script also optionally installs support for NI VXI in LabVIEW You also can install
6. 2002 National Instruments Corporation rights reserved Important Information Warranty The National Instruments MXIbus boards and accessories are warranted against defects in materials and workmanship for a period of one year from the date of shipment as evidenced by receipts or other documentation National Instruments will at its option repair or replace equipment that proves to be defective during the warranty period This warranty includes parts and labor The media on which you receive National Instruments software are warranted not to fail to execute programming instructions due to defects in materials and workmanship for a period of 90 days from date of shipment as evidenced by receipts or other documentation National Instruments will at its option repair or replace software media that do not execute programming instructions if National Instruments receives notice of such defects during the warranty period National Instruments does not warrant that the operation of the software shall be uninterrupted or error free A Return Material Authorization RMA number must be obtained from the factory and clearly marked on the outside of the package before any equipment will be accepted for warranty work National Instruments will pay the shipping costs of returning to the owner parts which are covered by warranty National Instruments believes that the information in this document is accurate The document has been carefully r
7. c Do Not Terminate MXIbus Off Figure 3 9 MXIbus Termination Configuration EEPROM PCI MXI 2 for Linux The VXI MXI 2 has an onboard EEPROM which stores default register values that are loaded at power on The EEPROM is divided into two halves a factory configuration half and a user configuration half Both halves were factory configured with the same configuration values so you can modify the user configurable half while the factory configured half stores a back up of the default user settings 3 14 ni com Chapter 3 VXI MXI 2 Configuration and Installation Use switches 3 and 4 of the four position switch at location U35 to control the operation of the EEPROM The Restore Factory Configuration switch switch 4 causes the VXI MXI 2 to boot off the factory configured half instead of the user modified settings This is useful in the event that the user configured half of the EEPROM becomes corrupted in such a way that the VXI MXI 2 boots to an unusable state The Change Factory Configuration switch switch 3 of U35 lets you change the factory default configuration settings by permitting writes to the factory settings section of the EEPROM This switch serves as a safety measure and should not be needed under normal circumstances When this switch is off its default setting the factory configuration of the EEPROM is protected so any writes to the factory area will be ignored The factory area is protected regardles
8. Interrupt Handlers Default Value 0 to 7 1 6 12 ni com Chapter 6 NI VXI Configuration Utility Number of Interrupters This field gives the number of interrupters that the PCI MXI 2 supports Interrupters Default Value 0to7 0 Protocol Register This field specifies the contents of the Protocol register indicating which protocols the device supports This field is meaningful only when the PCI MXI 2 is configured as a message based device The default value is OxOffO Commander Signal Register Master Read Protocol Response This field specifies the response value to a Read Protocol command received by the PCI MXI 2 from the Resource Manager if the PCI MXI 2 is not the Resource Manager in your system This field is meaningful only when the PCI MXI 2 is configured as a message based device The default value is 0x8448 Response Generation Event Generation Programmable Handler Word Serial Trigger Instrument Extended Longword Serial Longword Serial National Instruments Corporation 6 13 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Bus Configuration Editor PCI MXI 2 for Linux Figure 6 6 shows the Bus Configuration Editor The following sections describe the options you can select for each of the fields 3 Bus Configuration E ditor Bus Settings MI Bus Timeout Auto 1 ms bud MXI CLK10 Drive Receive
9. The more you increase the size of the user window the larger the window you can map in MapVXIAddress You also can disable this option Disabling the user window causes the PCI MXI 2 to request the minimum amount of address space on the PCI bus With the window disabled you will be unable to perform any low level function calls such as VXIpeek VXIpoke and MapVXIAddress Itis recommended to have a user window of at least 64 KB and the default setting for the user window is set at this value If you are going to be initiating transfers to a wide variety of addresses in both A24 and A32 you should increase the size of the user window Any change you make to the size of the user window requires that you reboot your computer The size of the driver window however is system defined and is not user configurable Note Neither the user window nor the driver window can be placed below 1 MB with the Linux NI VXI driver Therefore the Place below 1 MB option and the Window Base option will always be disabled Expansion ROM Use the Enable expansion ROM control to enable or disable the PCI expansion ROM The expansion ROM is enabled by default It is recommended to retain the default setting This option is included in vxiedit in case future versions of the PCI MXI 2 do not implement a PCI expansion ROM PCI MXI 2 for Linux 6 18 ni com Chapter 6 NI VXI Configuration Utility VXIANME MXI 2 Configuration Editor Before
10. figure 3 11 VXIbus local bus 3 7 VXIbus logical address 3 3 selection figure 3 5 VXIbus Slot 0 non Slot 0 3 5 connecting MXIbus cable 3 19 default settings Configuration Editor settings table 1 13 hardware settings table 1 12 National Instruments Corporation l 9 Index hardware description 1 4 installation 3 18 quick start installation 1 6 onboard DRAM 3 17 specifications electrical A 7 environmental A 6 MX Ibus capability descriptions 4 performance A 7 physical A 6 requirements A 6 VMEbus capability codes A 4 VXIbus local bus 3 7 VXIbus logical address 3 3 VXIpeek function 7 3 VXIpoke function 7 3 vxitedit utility interacting with VXI VME devices 1 8 VME device configuration information 1 8 W Web professional services E 1 technical support E 1 window mapping option VXI shared RAM 6 9 window size 6 18 worldwide technical support E 1 write posting A16 write posting VME VXI MXI 2 6 21 A24 32 write posting PXI MXI 2 6 17 2 6 21 2 for Linux
11. 16 amp 1 VMEbus slave A32 A24 and 16 addressing D32 D16 DOS EO master VMEbus master D32 D16 and D08 data sizes A 4 ni com D32 D16 DO8 EO slave BLT MBLT master BLT MBLT slave RMW master RMW slave Appendix A D32 D16 D08 O Interrupt Handler D32 D16 D08 O Interrupter ROAK National Instruments Corporation RORA 5 Specifications for VXI MXI 2 VMEbus slave D32 D16 and 08 data sizes VMEbus master block and D64 transfers VMEbus slave block and D64 transfers VMEbus master read modify write transfers VMEbus slave read modify write transfers VMEbus master retry support VMEbus slave retry support First slot detector VMEbus System Controller Prioritized or Round Robin Select arbiter Release on Request and FAIR bus requester Interrupt handler for levels 7 1 Interrupt requester for levels 7 1 VMEbus D32 D16 D08 O interrupt handler VMEbus D32 D16 D08 O interrupter Release on Acknowledge or Register Access interrupter VMEbus bus timer programmable limit PCI MXI 2 for Linux Appendix A Specifications for VXI MXI 2 Requirements Environmental Physical PCI MXI 2 for Linux VXIbus Configuration Space 64 B A24 or A32 16 KB minimum programmable Temperature Operating 0 to 55 Stora
12. 7 4 configuration See also PCI MXI 2 Configuration Editor VXI VME MXI 2 Configuration Editor default settings 1 9 PCI MXI 2 board 2 1 configuration EEPROM 2 3 default settings Bus Configuration Editor table 1 11 Device Configuration Editor table 1 11 hardware settings table 1 9 Logical Address Configuration Editor table 1 10 quick start 1 6 VME MXI 2 module 4 1 configuration EEPROM 4 6 default settings Configuration Editor settings table 1 13 hardware settings table 1 13 front panel features 4 3 MXlIbus termination 4 5 onboard DRAM 4 8 DRAM configurations table 4 9 SIMM size configuration figure 4 9 PCI MXI 2 for Linux Index parts locator diagram figure 4 2 VMEbus A16 base address 4 3 VME MXI 2 intermodule signaling 4 4 VXI MXI 2 module configuration EEPROM 3 14 front panel features 3 3 MXlIbus termination 3 13 onboard DRAM 3 17 removing metal enclosure 3 3 right side cover figure 3 2 trigger input termination 3 12 VXIbus CLK10 routing 3 8 VXIbus Slot 0 non Slot 0 3 5 configuration EEPROM C 1 controlling EEPROM operation C 1 fixing invalid EEPROM configuration C 2 PCI MXI 2 board 2 3 VME MXI 2 module 4 6 VXI MXI 2 module 3 14 configuration settings PCI MXI 2 loading from file 6 4 reverting to current settings 6 4 saving to file 6 4 updating current configuration 6 4 contacting National Instruments E 1 controller default controller LA 1 6 11 MXI s
13. Logical Address This parameter sets the MXI logical address of the PCI MXI 2 The following table shows the allowable range of values and the default value Logical Address Range Default Value 0 to 254 0 National Instruments Corporation 6 5 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility PCI MXI 2 for Linux Device Type This field indicates the classification of the PCI MXI 2 The default value is MBD designating a message based device The following table shows the available options Classification Setting Extended Device EXT Message Based Device MBD Register Based Device RBD The device type affects only the contents of the Device Class field in the Device Type register The functionality of the other registers does not change Address Space This field indicates the addressing mode s of the device s operational registers The PCI MXI 2 can be configured in one of three ways The default addressing mode is for A16 space only Your other options are A16 A24 and A16 A32 Notice that several other controls on the configuration editor panel are disabled when the addressing mode is A16 as shown in Figure 6 3 Only if you select A16 A24 or A16 A32 are the following controls relevant e VXI Shared RAM Size e Shared RAM Pool e Advanced Byte Swapping Memory Select Mapping VXI VME Shared Memory The VXI Shared Memory group contains the controls to s
14. cte teet reet eg e ee ees 6 27 MXI Bus System Controller sese 6 27 MXI Bus Timeout Value eeeeeseeeeeeeeen eene 6 27 National Instruments Corporation ix PCI MXI 2 for Linux Contents Advanced MXI Settings 6 28 MX Alito Retry isu eee ge ettet Ree 6 28 Tr nster Limit ceret tte tele ie etes 6 29 Parity Checking enia 6 29 MXI Bair Requestet 22 Erro tete 6 29 MXI CLK1O Signal teet eer recentes 6 29 Chapter 7 Using the NI VXI NI VISA Software Interactive Control of NI VXI NI VISA eese enne emeret 7 2 Example Programs ioi ertt eR E Ee eden 7 2 Programming Considerations wes ne ra er uses bbc ERE e 7 2 Multiple Applications Using the NI VXI and VISA Libraries 7 2 Low Level Access EUnCons ree rete e rt et etes 7 3 Local Resource Access Functions eseeseseeeseeeereeenen enne 7 3 System Configuration Functions esee 7 4 Compiling Your C Program for NI VXI NI VISA seseeeeeeee 7 4 Symbols 2 22 eee rete e rette te t ttn 7 4 Appendix A Specifications Appendix B NI VXI NI VISA Software Overview Appendix C EEPROM Configuration Appendix D Common Questions Appendix E Technical Support and Professional Services Glossary Index PCI MXI 2 for Linux X ni com About This Manual This manual contains instructions for
15. 3 PCI MXI 2 Device Configuration Editor Default Settings Editor Field Default Setting Default Controller LA 1 First Remote Controller System IRQ Level 1 Servant Area Size 0 Number of Handlers 1 Number of Interrupters 0 Protocol Register OxFFO Read Protocol Response 0x8448 Table 1 4 PCI MXI 2 Bus Configuration Editor Default Settings Editor Field Default Setting MXI System Controller Auto MXI Bus Timeout Value ms MXI CLK10 Receive MXI Transfer Limit Unlimited VXImove uses Synchronous MXI Enabled MXI 2 Auto Retry Enabled A24 A32 Write Posting Disabled User Window Size 64 KB Driver Window Size 32 KB Expansion ROM Enabled PCI MXI 2 for Linux National Instruments Corporation 1 11 Chapter 1 Introduction and Quick Start VXIAME MXI 2 This section summarizes the hardware and software default settings for the VXI MXI 2 and VME MXI 2 Table 1 5 VXI MXI 2 Hardware Default Settings Hardware Component Default Setting Logical Address U43 1 VXIbus Slot 0 Non Slot 0 W2 Automatic detection VXIbus Local Bus S8 S9 Both OFF Single VXI MXI 2 VXIbus CLK10 Routing W3 From onboard oscillator External Trigger Termination 52 OFF Unterminated SMB CLK10 Direction S3 OUT Drive CLK10 signal SMB CLK10 Termination S4 Ignored effective only when S3 is set to IN Polarity of External SMB CLK10 Inverted
16. A MXIbus device responds at Logical Address 255 during a priority select cycle The Resource Manager subsequently assigns it a new logical address which the device responds to until powered down A method of automatically assigning logical addresses to V XIbus devices at system startup or other configuration times Emitter Coupled Logic Electronically Erasable Programmable Read Only Memory An intelligent CPU controller interface plugged directly into the VXI backplane giving it direct access to the VXIbus It must have all of its required VXI interface capabilities built in Electromechanical Compliance G 4 ni com EMI expansion ROM external controller F fair requester hex 1 interrupt interrupt handler interrupt level IRQ National Instruments Corporation G 5 Glossary Electromagnetic Interference An onboard EEPROM that may contain device specific initialization and system boot functionality In this configuration a plug in interface board in a computer is connected to the VXI mainframe via one or more V XIbus extended controllers The computer then exerts overall control over V XIbus system operations A MXIbus master that will not arbitrate for the MXIbus after releasing it until it detects the bus request signal inactive This ensures that all requesting devices will be granted use of the bus Hexadecimal the numbering system with base 16 using the digits
17. CLK10 Signal Switch determines signal direction C Drive Receive Cancel Default Figure 6 10 Advanced MXI Settings MXI Auto Retry The VXI VME MXI 2 has an automatic retry feature for cycles that map from the MXIbus to the VXI VMEbus This feature works in the same manner as the Auto Retry control described in the VX VME Bus Options section By default this option is disabled Normally when a cycle maps from the MXIbus to the VXI VMEbus any retry response received on the VXI VMEbus is passed to the MXIbus If you enable the Auto Retry feature the VXI VME MXI 2 automatically retries any VXI VME cycle that receives retry response instead of passing a retry response on to the MXIbus The VXI VME MXI 2 automatically continues to retry the VXI VME cycle until it receives either a DTACK or BERR response which it then passes to the MXIbus Note The VXI VME MXI 2 has a limit on the number of automatic retries it will perform on any one cycle If the limit is exceeded and the VXI VME MXI 2 receives another retry it will pass a retry back to the MXIbus even though Auto Retry is enabled PCI MXI 2 for Linux 6 28 ni com Chapter 6 NI VXI Configuration Utility Transfer Limit You can use this feature to control how many data transfers the VXI VME MXI 2 will perform on the MXIbus before releasing it to another master device that is requesting use of the bus The default setting holds the MXIbus for an u
18. I have installed Run the NI VXI utility program vic Under the Text tab type ver in the command field and the utility will display the versions of vic and NI VXI and the latest PCI MXI 2 board revision that this NI VXI driver supports How can I determine the revision of the PCI MXI 2 board that my NI VXI software supports Running the NI VXI utility program vic as described above will display the versions of vic and NI VXI and the hardware revision of the PCI MXI 2 that the NI VXI software supports How can I determine the serial number and hardware revision of the PCI MXI 2 board Run the NI VXI utility program vxiedit Choose the PCI MXI 2 Configuration Editor The editor window displays the serial number and hardware revision of the PCI MXI 2 board How can I determine the serial number and hardware revision of the VXI MXI 2 or VME MXI 2 Run the NI VXI utility program vxiedit Choose the VXI VME MXI 2 Configuration Editor The opening screen displays the serial number and hardware revision of the VXI MXI 2 or VME MXI 2 Which NI VXI utility program must I use to configure the PCI MXI 2 Use the VXI Resource Editor program vxiedit or its text mode counterpart vxitedit to configure the PCI MXI 2 The Resource Editor program is located in the NIVXI bin directory usr local nivxi bin by default National Instruments Corporation D 1 PCI MXI 2 for Linux Appendix D Common Questions PCI MXI 2 for Linux Which NI
19. I receive a message that it could not find a particular file even though the file does exist What is wrong When a NI VXI utility cannot find a file that it needs it usually means that one of the environment variables is set incorrectly Check the environment variable NIVXIPATH and your etc 1d so conf file NIVXIPATH should be set only to the directory where you installed NI VXI usr local nivxi by default etc 1d so conf should include the directory where you installed the NI VXI library usr local nivxi lib by default Run ldconfig to reread this file You can also receive this error message if you do not have full permissions to some of the NI VXI files and directories Users who will be using NI VXI should have full permissions to the tb1 and examp1es directories They should also have read write permissions for all the files contained in those directories Whenever I try to run resman without the MXI 2 cable plugged into my PCI MXI 2 it hangs This also happens if I have the wrong end of my cable plugged into the PCI MXI 2 Why The PCI MXI 2 uses the MXI 2 cable to find out if it is the MXIbus System Controller If the correct end of the cable is not securely attached to the PCI MXI 2 Resman and other NI VXI applications can hang The MXI 2 cable has a label indicating which end should be plugged into the system controller If you need to run Resman with the MXI 2 cable unattached you can force the PCI MXI 2 to be system contr
20. MXI 2 defines synchronous MXI block data transfers which surpass previous block data throughput benchmarks The new synchronous MXI block protocol increases MXI 2 throughput to a maximum of 33 MB s between two MXI 2 devices All National Instruments MXI 2 boards can initiate and respond to synchronous MXI block cycles hy Note In the remainder of this manual the term MXIbus refers to MXI 2 Hardware Description The PCI MXI 2 is a half size PCI compatible plug in circuit board that plugs into one of the expansion slots in your PCI based computer It links your PCI based computer directly to the MXIbus and vice versa Because the PCI MXI 2 uses the same communication register set that other VXIbus message based devices use other MXIbus devices view the PCI MXI 2 as a VXIbus device The PCI MXI 2 can also function as the MXlIbus System Controller and can terminate the MXIbus signals directly on the PCI MXI 2 In addition you can have onboard DRAM on the PCI MXI 2 that can be shared with the MXIbus and VXI VMEbus and used as a dedicated data buffer The VXI MXI 2 module is an extended class register based V XIbus device with optional V XIbus Slot 0 capability so that it can reside in any slot in a C size or D size chassis 3 Note D size VXI mainframes have connections for a P3 connector The VXI MXI 2 however does not have this connector and if configured as a Slot 0 controller cannot provide the necessary control for VXI devices tha
21. O to 9 and letters A to F Hertz cycles per second Input output the techniques media and devices used to achieve communication between machines and users Integrated Circuit Institute of Electrical and Electronics Engineers Inches A means for a device to request service from another device A VMEbus functional module that detects interrupt requests generated by Interrupters and responds to those requests by requesting status and identify information The relative priority at which a device can interrupt Interrupt signal PCI MXI 2 for Linux Glossary KB L LED logical address m master master mode operation MB MBLT message based device MITE MODID MTBF MXI 2 PCI MXI 2 for Linux Kilobytes of memory Light Emitting Diode An 8 bit number that uniquely identifies each VXIbus device in a system It defines the A16 register address of a device and indicates Commander and Servant relationships Meters A functional part ofa MXI VME V XIbus device that initiates data transfers on the backplane A transfer can be either a read or a write A device is in master mode if it is performing a bus cycle which it initiated Megabytes of memory Eight byte block transfers in which both the Address bus and the Data bus are used to transfer data An intelligent device that implements the defined V XIbus registers and communication protocols These devices are able to use Word Serial Pr
22. Timeout Value The VXI VMEbus Bus Timeout BTO is a watchdog timer for transfers on the VMEbus Data Transfer bus After the specified amount of time has elapsed the BTO circuitry terminates a VMEbus cycle if no slave has responded The VXI VME MXI 2 must provide the VXI VMEbus for proper operation because when a MXIbus cycle is involved the VXI VMEbus timeout must be disabled and the MXIbus enabled You should disable the BTO of any other BTO module residing in the mainframe If this is not possible set its VXI Bus Timeout control to its maximum setting to give the MXIbus cycles as much time as possible to complete The lowest value in the allowable range is 15 us and the highest value is 256 ms The default value is 125 us Advanced VXI Settings Click the Advanced button to reach additional configuration options for the VXI VME Bus portion of this editor as shown in Figure 6 9 These options are intended for more advanced users 6 24 ni com Chapter 6 NI VXI Configuration Utility PETIT VXI Settings x These settings control the operation of the Vx bus Exercise caution when changing these options M Bus Protocols Transfer Limit 256 mBus Arbitration Settings Arbiter Type 3 Priority Request Level Fl Round Robin Operate as Fair Requester v Enable Arbiter Timeout Cancel Default Figure 6 9 Advanced VXI Settings VXI VME Auto
23. VMEbus specification VXIAME Fair Requester The VXI VME MXI 2 is always a Release On Request requester However you can configure whether the VXI VME MXI 2 acts as either a fair or unfair requester on the VXI VMEbus By default the Operate as Fair Requester checkbox is enabled signifying a fair requester For more information on the different types of requesters refer to the VMEbus specification 6 26 ni com Chapter 6 NI VXI Configuration Utility Arbiter Timeout An arbitration timeout feature is available on the VXI VME MXI 2 when it is acting as the VMEbus arbiter This feature applies only to a VXI Slot 0 VMEbus System Controller VXI VME MXI 2 By default this option is enabled The timer begins when the arbiter circuit on the VXI VME MXI 2 drives one of the BGOUT lines on the backplane If no device takes over the bus within the timeout limit the BGOUT is removed and the bus is either idle or granted to another requester MXI Bus Options Use the options in this group to control features of the MXIbus interface on the VXI VME MXI 2 module MXI Bus System Controller You can use the System Controller control to determine whether the VXI VME MXI 2 acts as the MXI Bus System Controller When the Auto setting the default setting is active the VXI VME MXI 2 automatically can sense from the MXIbus cable whether it should be the controller You can select either Yes or No to manually determine if the VXI VME MXI 2 shou
24. VXI NI VISA Software Installation When used with a VXI MXI 2 Resman identifies and configures the VXI devices including the VXI MXI 2 When used with a VME MXI 2 Resman configures the VME MXI2 to allow the PCI MXI 2 to access devices in the VME chassis Resman does not configure VME devices The VME specification does not specify the initialization and configuration procedures that the V XI specification requires It is recommended that you enter the information about your VME devices into the vxitedit utility Resman can then properly configure the various device specific VME address spaces and VME interrupt lines For more information on configuring non VXI devices in your VXI system refer to Chapter 3 VXI Text Resource Editor of the NI VXI Text Utilities Reference Manual For more details about installing the NI VXI software refer to Chapter 5 NI VXI NI VISA Software Installation in this manual After Resman has detected and configured all VXI VME devices you can view specific information on each device in your system by using the vxiedit utility or its text mode counterpart vxitedit These utilities include a Resource Manager Display which contains a description for each device including each VXI device s logical address You can interact with your VXI VME devices by using the vic and victext utilities for NI VXI These utilities let you interactively control your VXI VME devices without using a conventional programming languag
25. VXT utility program must I use to perform startup Resource Manager operations Use the Resman program to perform startup Resource Manager operations It is located in the NIVXI bin directory usr local nivxi bin by default Resman uses the settings in the Configuration Editor of vxitedit It initializes your VXI VMEbus system and stores the information that it collects to the resman tb1 file in the tb1 subdirectory of the NIVXI directory What can I do to make sure that my system is up and running The fastest method for testing the system is to run Resman This program attempts to access memory in the upper A16 address space of each device in the system If resman does not report any problems the VXI MXI communication system is operational To test individual devices you can use the vic program or it text mode counterpart victext to interactively issue NI VXI functions You can use the VXTin and VXIout functions or the VXTinReg and VXIoutReg functions to test register based devices by programming their registers If you have any message based devices you can send and receive messages with the WSwrt and WSrd functions Notice that VXIinReg and VXIoutReg for VXI devices only Finally if you are using LabVIEW or LabWindows CVI and you have instrument drivers for the devices in your chassis you can use the interactive features of these programs to quickly test the functionality of the devices What do the
26. be lower than in normal operating mode In a VXI VMEbus MXlIbus system you can configure some VXI VME MXI 2 modules for normal operating mode and others for interlocked arbitration mode The VXI VMEbus mainframes configured in interlocked arbitration mode will be interlocked with each other and the mainframes configured for normal operating mode can perform transfers in parallel 6 22 ni com Chapter 6 NI VXI Configuration Utility This type of system configuration is recommended if you have one of the following situations e A VXI VMEbus mainframe with only slave devices and no masters Without bus masters there is no chance for deadlock You can configure the VXI VME MXI 2 devices in this mainframe for normal operating mode VXI VMEbus mainframe with both masters and slaves but the masters communicate only with the slaves in their mainframe The masters never attempt transfers across the MXIbus so there is no chance for deadlock when a MXIbus master attempts a transfer into the VXI VMEbus mainframe You can configure the VXI VME MXI 2 devices in this mainframe for normal operating mode e A VXI VMEbus mainframe in which all masters that perform cycles across the MXIbus support the VME64 RETRY protocol You can configure the VXI VME MXI 2 devices in this mainframe for normal operating mode because all masters that could cause a deadlock will automatically retry the operation VXI VME Bus Options Use the options in this gr
27. can increase performance with its capability to post write cycles from both the MXIbus and the VXI VMEbus Write cycles should be posted only to devices that cannot return a BERR signal because the BERR will not be reported to the originating master Click on the checkbox control s if you want to use either A16 or A24 A32 write posting By default both options are disabled The A16 write posting control affects only write cycles that map through the A16 window from the VXI VMEbus to the MXIbus and vice versa A16 write cycles in VXI configuration space are never posted regardless of the setting of this control The A24 A32 write posting control affects write cycles that map through the A24 window and A32 window from the VXI VMEbus to the MXIbus and vice versa This control also affects write cycles to the VXI VME MXI itself via its requested memory space from both the VXI VMEbus and the MXIbus For more information on the A16 A24 and A32 windows refer to VXI 6 the VXIbus Mainframe Extender Specification National Instruments Corporation 6 21 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Interlocked Mode PCI MXI 2 for Linux Interlocked arbitration mode is an optional mode of operation in which at any given moment the system can perform as if it were one large VXI VMEbus mainframe with only one master of the entire system V XI VMEbus MXIbus This mode of operation prevents deadlocks by interlocking all
28. descriptions indicate whether they apply to VXI only or both VXI and VME The following function classes apply only to VXI e Commander Word Serial Protocol functions e Servant Word Serial Protocol functions e VXI Signal functions e VXI Trigger functions Refer to the NI VISA User Manual to learn about VISA and how to use it in your system The NI VISA online help describes the attributes events and operations you can use in NI VISA The user manual is available in the VXrpnp linux NIvisa Manuals directory Use the Acrobat Reader program to open and navigate through this manual National Instruments Corporation 7 1 PCI MXI 2 for Linux Chapter 7 Using the NI VXI NI VISA Software Interactive Control of NI VXI NI VISA The easiest way to learn how to communicate with your instruments is by controlling them interactively Use the VXI VME interactive control utility vic or its text mode counterpart victext to write to and read from your instruments This utility displays the status of your VXI VME transactions and informs you of any errors that occur Refer to the online help for instructions on how to use victext and to learn about the features of each Example Programs The NIVXI examples subdirectory contains various example programs along with a makefile that show how to use various functions in the NI VXI software and how to develop application programs using these functions Make certain that the environment variable N
29. for Linux 3 6 Chapter 3 VXI MXI 2 Configuration and Installation VXIbus Local Bus If you will be installing more than one VXI MXI 2 in a single V XIbus mainframe you must configure the boards to use the local bus The VXI MXI 2 uses the local bus to pass a signal to the other VXI MXI 2 modules in the mainframe to disable the VMEbus bus timeout unit BTO during cycles that map to the MXIbus Because the local bus is used you need to install all VXI MXI 2 modules for a single mainframe in adjacent slots You will use two switches on the VXI MXI 2 to select its position in relation to any other VXI MXI 2 module in the mainframe Use switch S9 when there is a VXI MXI 2 to the right higher numbered slot Use S8 when there is a VXI MXI 2 to the left lower numbered slot Figure 3 4 shows four configuration settings for a VXI MXI 2 Figure 3 4a illustrates the default setting which is for a single VXI MXI 2 in a mainframe Use the setting in Figure 3 4b for the VXI MXI 2 located to the left of all others Figure 3 4c shows the setting to use if the VXI MXI 2 is between two others Use the setting of Figure 3 4d for the VXI MXI 2 located to the right of all others National Instruments Corporation 3 7 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation x nom Eum 2S ss Yes No Yes VXI MXI to left VXI MXI to left VXI MXI to right VXI MXI to right a Single VXI MXI 2 in Mainframe Defa
30. interface e visa his the main header file containing the C prototypes for the NI VISA functions e visatype hcontains VXIplug amp play data type specifications vpptype h contains useful definitions for instrument drivers PCI MXI 2 for Linux B 2 ni com EEPROM Configuration This appendix describes how to control the operation of the PCI MXI 2 onboard EEPROM and how to fix an invalid EEPROM setting The EEPROM stores default registers values that are loaded at power on The EEPROM is divided into two halves so that you can modify one half while the factory configured half retains a back up of the default user settings Controlling the EEPROM Operation Use switch 1 FOV of the four position switch at location U17 to control the operation of the EEPROM Switch 1 determines whether the PCI MXI 2 boots off the factory configured half or the user configurable half In its default setting the PCI MXI 2 boots off the user configurable half This switch is useful in the event that the configuration becomes corrupted in such a way that the PCI MXI 2 boots to an unusable state The TST switch switch 2 of U17 lets you change the factory default configuration settings by permitting writes to the factory settings section of the EEPROM This switch serves as a safety measure and should not be needed under normal circumstances When this switch is off its default setting the factory configuration of the EEPROM is protected so an
31. more call your local NI office or visit ni com alliance If you searched ni com and could not find the answers you need contact your local office or NI corporate headquarters Phone numbers for our worldwide offices are listed at the front of this manual You also can visit the Worldwide Offices section of ni com niglobal to access the branch office Web sites which provide up to date contact information support phone numbers email addresses and current events National Instruments Corporation E 1 PCI MXI 2 for Linux Glossary Prefix Meanings Value p pico 10 12 n nano 107 u micro 10 6 m milli 10 3 k kilo 10 M mega 106 G giga 10 t tera 10 Symbols Degrees Q Ohms 9 Percent A A Amperes A16 space VXIbus address space equivalent to VME 64 KB short address space In VXI the upper 16 KB of A16 space is allocated for use by VXI devices configuration registers This 16 KB region is referred to as VXI configuration space A24 space VXIbus address space equivalent to the VME 16 MB standard address space A32 space V XIbus address space equivalent to VME 4 GB extended address space National Instruments Corporation G 1 PCI MXI 2 for Linux Glossary ACFAIL address address modifier address space address window ANSI arbitration asynchronous B B backplane BERR binary BIOS PCI MXI 2 for Linux
32. settings of any switches shown with this pattern 2 have no bearing on the configuration described in any of the following figures PCI MXI 2 for Linux 3 10 ni com Chapter 3 VXI MXI 2 Configuration and Installation 222 On 500 Termination for External Trigger Input o EE o In SMB CLK10 Direction 22220 On 500 Termination for SMB CLK10 Effective only when S3 is set to IN ib 5 SMB CLK10 Output Polarity Effective only when S3 is set to OUT INVERTED N NON INVERTED a Drive Inverted External CLK SMB Default On 500 Termination for External Trigger Input A 5 In SMB CLK10 Direction 84 Of 22222 500 Termination for SMB CLK10 Effective only when S3 is set to IN S5 a SMB CLK10 Output Polarity Effective only when S3 is set to OUT INVERTED N NON INVERTED b Drive Non Inverted External CLK SMB 222 On 500 Termination for External Trigger Input T 29 In SMB CLK10 Direction SA Off 5 On 500 Termination for SMB CLK10 Effective only when S3 is set to IN 2220 SMB CLK10 Output Polarity Effective only when S3 is set to OUT INVERTED N NON INVERTED c Receive External CLK SMB 222 On 500 Termination for External Trigger Input secu ISS In SMB CLK10 Direction 84 Of mmn On 50Q Termination for SMB CLK10 Effective only when S3 is set to IN 2222 SMB CLK10 Output Polarity Effe
33. the RPM files without going through the INSTALL script by using rpm glint or gnorpm on RedHat or other RPM based systems For example to install NI VXI in opt on a RedHat 5 x system type the following command rpm prefix opt nivxi Uvh nivxi pcimxi 1 6 1 1386 rpm National Instruments Corporation 5 1 PCI MXI 2 for Linux Chapter 5 NI VXI NI VISA Software Installation where 1 6 1isthe version you are installing Note that this version number will be different if you are installing a newer version hy Note If you use rpm rather than the INSTALL script you must repeat this step for each package you want to install If you install the software to a location other than the default set the appropriate environment variable NIVXIPATH for NI V XI or VXIPNPPATH for NI VISA See your manual for details Refer to the README file on the CD ROM for additional important information and instructions Removing the NI VXI Driver for Linux To uninstall the driver you must meet the following requirements e You must have superuser privileges e The driver must not be in use Typing rpm e nivxi pcimxi nivisa removes the NI VXI NI VISA software Using the NI VXI NI VISA Software PCI MXI 2 for Linux The NI VXI software is configured to be loaded in the usr local nivxi directory If you have installed the software in another directory set the NIVXIPATH environment variable to your directory For example if you have install
34. transfer limit 6 16 MXI 2 auto retry 6 16 limit on note 6 17 synchronous MXI 6 16 user window and driver window 6 17 window size 6 18 PCI MXI 2 Configuration Editor default settings table 1 11 illustration 6 3 load configuration from file 6 4 record configuration to file 6 4 revert to current configuration 6 4 saving changes 6 3 update current configuration 6 4 PCI MXI 2 Device Configuration Editor default controller LA 1 6 11 default settings table 1 11 illustration 6 11 number of handlers 6 12 number of interrupters 6 13 protocol register 6 13 read protocol response 6 13 servant area size 6 12 system IRQ level 6 12 PCI MXI 2 Logical Address Configuration Editor address space 6 6 controls 6 6 default settings table 1 10 device settings group 6 5 device type classification setting 6 6 illustration 6 5 logical address parameter range default value 6 5 resource manager delay 6 10 PCI MXI 2 for Linux Index VXI shared RAM options 6 6 advanced shared RAM settings 6 8 illustration 6 8 enable byte swapping 6 9 memory select 6 9 shared RAM pool 6 7 lower half window and upper half window 6 7 VXI VME shared RAM size 6 7 window mapping 6 9 performance specifications PCI MXI 2 board A 3 VME MXI 2 module A 11 VXI MXI 2 module A 7 phone technical support E 1 physical specifications PCI MXI 2 board 3 VME VXI 2 module A 10 VXI MXI 2 module A 6 prob
35. want to update the PCI MXI 2 configuration settings use the Update Current Configuration option instead Load Configuration from File You can use this option to load your configuration settings from a file This action only updates the configuration settings in your editor This does not write the configuration settings to the PCI MXI 2 configuration EEPROM To update the configuration use the Update Current Configuration option for the changes to take effect Revert to Current Configuration If you made changes to the configuration settings without committing those changes writing to configuration EEPROM you can revert the configuration settings to the values they had before you made the changes 3 Note You can successfully revert only if you have not yet selected the Update Current Configuration option Logical Address Configuration Editor PCI MXI 2 for Linux Figure 6 3 shows the Logical Address Configuration Editor Notice that the options are arranged into three groups Device Settings VXI Shared Memory and Resource Manager The following sections describe the options you can select for each of the fields 6 4 ni com Chapter G Configuration Utility Logical Address Configuration E ditor Figure 6 3 PCI MXI 2 or PXI MXI 2B Logical Address Configuration Editor Device Settings The Device Settings group contains the controls to set the logical address device type and address space of the PCI MXI 2
36. will be executed on the first VXI VME MXI 2 in the MXI 2 chain If you select the Local controller option the NI VXI functions execute on the PCI MXI 2 National Instruments Corporation 6 11 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility System IRQ Level The remote controllers in this case the VXI VME MXI 2 can report events such as triggers and DMA to the PCI MXI 2 through a VXI IRQ line This field selects which VXI IRQ level the remote controllers should use to report events to the PCI MXI 2 Interrupt Request Levels Default Value 1to7 1 Servant Area Size This field designates the servant area size which is supplied to the Resource Manager in response to the Read Servant Area command if the PCI MXI 2 is not the Resource Manager in your system The servant area size is an 8 bit value 0 through 255 that indicates the servant area The servant area begins at the logical address following the PCI MXI 2 logical address and includes N contiguous logical addresses where N is the value of the servant area size This field is meaningful only when the PCI MXI 2 18 configured as a message based device Servant Area Range Default Value 0 to 255 0 3 Note If the PCI MXI 2 is the Resource Manager Logical Address 0 this setting is irrelevant PCI MXI 2 for Linux Number of Handlers This field gives the number of interrupt handlers that the PCI MXI 2 supports
37. wy L 2835 93 ex in I 3 TON amp ui R40 RA 7 3 3 B L ag om os grec 8 NUS eme E E om E Eu B Bus wv g g n E NOE x wa i 3 D as bom D E m m pg mm g 8 P e mus oss E ls om ms 9 BES eos er C25 o tia ese mie 8 E 2 go m m EI PT ME Bes 1 i mom Jio EE Ae Eee neo 7 E m E fme amp R55 Jt zl 5 Dreo E x gt RES ae F Eme res lt a R63 RET X Ea 865 Res d s OCOPYRIGHT 1995 VME MXI 2 o O ASSY183105A 01 c 30 S N i lo 1 52 2 021 2 4 020 DRAM Bank 1 DRAM Bank 0 PCI MXI 2 for Linux Figure 4 1 VME MXI 2 Parts Locator Diagram ni com Chapter 4 VME MXI 2 Configuration and Installation Front Panel Features The VME MXI 2 has the following front panel features e Three front panel LEDs SYSFAIL LED indicates that the VMEbus SYSFAIL line is asserted MXILED indicates when the VME MXI 2 is accessed from the MXIbus VME LED indicates when the VME MXI 2 is accessed from the VMEbus e MXlIbus connector e System reset pushbutton VMEbus A16 Base Address The VME MXI 2 requires 64 bytes of A16 space for its configuration registers It uses the logical address sch
38. A VMEbus backplane signal that is asserted when a power failure has occurred either AC line source or power supply malfunction or if it is necessary to disable the power supply such as for a high temperature condition Character code that identifies a specific location or series of locations in memory One of six signals in the VMEbus specification used by VMEbus masters to indicate the address space in which a data transfer is to take place A set of 2 memory locations differentiated from other such sets in VXI VMEBbus systems by six addressing lines known as address modifiers nis the number of address lines required to uniquely specify a byte location in a given space Valid numbers for n are 16 24 and 32 In VME VXI because there are six address modifiers there are 64 possible address spaces A portion of address space that can be accessed from the application program American National Standards Institute A process in which a potential bus master gains control over a particular bus Not synchronized not controlled by time signals Bytes An assembly typically a printed circuit board with 96 pin connectors and signal paths that bus the connector pins A C size V XIbus system will have two sets of bused connectors called J1 and J2 A D size V XIbus system will have three sets of bused connectors called J1 J2 and J3 Bus error signal A numbering system with a base of 2 Basic Input Output System BIOS funct
39. BLE FOR VERIFYING AND VALIDATING THE SUITABILITY OF NATIONAL INSTRUMENTS PRODUCTS WHENEVER NATIONAL INSTRUMENTS PRODUCTS INCORPORATED IN A SYSTEM OR APPLICATION INCLUDING WITHOUT LIMITATION THE APPROPRIATE DESIGN PROCESS AND SAFETY LEVEL OF SUCH SYSTEM OR APPLICATION Compliance FCC Canada Radio Frequency Interference Compliance Determining FCC Class The Federal Communications Commission FCC has rules to protect wireless communications from interference The FCC places digital electronics into two classes These classes are known as Class A for use in industrial commercial locations only or Class B for use in residential or commercial locations Depending on where it is operated this product could be subject to restrictions in the FCC rules In Canada the Department of Communications DOC of Industry Canada regulates wireless interference in much the same way Digital electronics emit weak signals during normal operation that can affect radio television or other wireless products By examining the product you purchased you can determine the FCC Class and therefore which of the two FCC DOC Warnings apply in the following sections Some products may not be labeled at all for FCC if so the reader should then assume these are Class A devices FCC Class A products only display a simple warning statement of one paragraph in length regarding interference and undesired operation Most of our products are FCC Class A The F
40. CC rules have restrictions regarding the locations where FCC Class A products can be operated FCC Class B products display either a FCC ID code starting with the letters EXN Trade Name Number or the FCC Class B compliance mark that appears as shown here on the right Fe Tested to Comply with FCC Standards Consult the FCC Web site at http www cc gov for more information FCC DOC Warnings This equipment generates and uses radio frequency energy and if not installed and used in strict accordance with the instructions in this manual and the CE Mark Declaration of Conformity may cause interference to radio and television reception Classification requirements are the same for the Federal Communications Commission FCC and the Canadian Department of Communications DOC FOR HOME OR OFFICE USE Changes or modifications not expressly approved by National Instruments could void the user s authority to operate the equipment under the FCC Rules Class A Federal Communications Commission This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to part 15 of the FCC Rules These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the instruction manual may cause harmful i
41. Configuration i Record Configuration to File i Load Configuration from File i Revert to Current Configuration iz Return to Main Menu Figure 6 2 PCI MXI 2 Configuration Editor The first three options under the PCI MXI 2 Configuration Editor are as follows Logical Address Configuration Editor e Device Configuration Editor e Bus Configuration Editor When making changes to the PCI MXI 2 through these editors remember that the changes do not take effect until you commit them by selecting the Update Current Configuration option Before proceeding to a description of each field in these editors review the remaining four options of the PCI MXI 2 Configuration Editor These options directly relate to how you can use the changes you make using the configuration editors which are described after the options National Instruments Corporation 6 3 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Update Current Configuration Use this option to write the configuration settings to the PCI MXI 2 EEPROM and files used by NI VXI Notice that some of the configuration settings cannot take effect until you reset the machine either by using the reset button or by turning the power off and on again Record Configuration to File With this option you can save your configuration settings to a file Notice that this option does not write the configuration settings to the PCI MXI 2 configuration EEPROM If you
42. Figure 3 1 VXI MXI 2 Right Side Cover 3 2 ni com Chapter 3 VXI MXI 2 Configuration and Installation Front Panel Features The VXI MXI 2 has the following front panel features e Three front panel LEDs SYSFAIL LED indicates that the VMEbus SYSFAIL line is asserted MXILED indicates when the VXI MXI 2 is accessed from the MXlIbus VXI LED indicates when the VXI MXI 2 is accessed from the VXlIbus e MXlIbus connector e Three SMB connectors External clock Trigger output Trigger input e System reset pushbutton Removing the Metal Enclosure The VXI MXI 2 is housed in a metal enclosure to improve EMC performance and to provide easy handling Because the enclosure includes cutouts to facilitate changes to the switch and jumper settings it should not be necessary to remove it under normal circumstances However it is necessary to remove the enclosure if you want to change the amount of DRAM installed on VXI MXI 2 Switch S6 which is directly related to the amount of DRAM you want to install is also accessible only by removing the enclosure If you will be making this change remove the four screws on the top the four screws on the bottom and the five screws on the right side cover of the enclosure Refer to the Onboard DRAM section for details about changing DRAM VXIbus Logical Address Each device in a VXIbus MXIbus system is assigned a unique number between 0 and 254 This 8 bit numbe
43. IVXIPATH is set correctly as described in Chapter 5 NI VXI NI VISA Software Installation Also refer to your software utilities reference manual for additional examples For NI VISA programming examples look in VXIpnp linux NIvisa Examples Programming Considerations The following sections contain information for you to consider when developing Linux applications that use the NI VXI VISA bus interface software Multiple Applications Using the NI VXI and VISA Libraries PCI MXI 2 for Linux Multiple application support is another feature in the NI VXI NI VISA libraries You can have several applications that use the NI VXI and or NI VISA libraries running simultaneously In addition you can have multiple instances of the same application running simultaneously The NI VXI NI VISA functions perform in the same manner whether you have only one application or several applications or several instances of a single application all using the NI VXI VISA libraries However you do need to be careful in certain cases as described in the Low Level Access Functions section 7 2 ni com Chapter 7 Using the NI VXI NI VISA Software Low Level Access Functions The memory windows used to access the VXI VMEbus are a limited resource You should follow the protocol of calling the viMapAddress or MapVXIAddress function with Access Only mode first before attempting to perform low level VXI VMEbus access with viPeekx viPokeX or VXI
44. LEDs on the front of the VXI MXI 2 or VME MXI 2 mean The SYSFAIL LED shows the state of the VXIbus VMEbus SYSFAIL line This line is asserted whenever any device in the chassis has not yet passed its self test if it has failed its self test or if it has detected a failure after originally passing its self test The MXI LED indicates that the VXI MXI 2 or VME MXI 2 is acting as a slave to another device on the MXlIbus such as when the PCI MXI 2 communicates with either the VXI MXI 2 or VME MXI 2 or with another device in the chassis The VXI VME LED when lit indicates that the VXI MXI 2 or VME MXI 2 is acting as a slave to another device in the VXI VME chassis such as when a bus master inside the chassis wants to talk to either the VXI MXI 2 or VME MXI 2 or another device outside the chassis D 2 ni com Appendix D Common Questions Are the PCI MXI 2 and the VXI MXI 2 two devices or one with respect to the VXIbus Both the PCI MXI 2 and the VXI MXI 2 are unique VXIbus devices with their own logical addresses However the MXIbus allows the computer to behave as if it is inside the chassis with the VXI MXI 2 by transparently converting PCI bus cycles to MXIbus cycles to V XIbus cycles and vice versa I have a system that requires rugged chassis and bulkhead cables Can I still use MXIbus Yes National Instruments sells MXIbus bulkhead cables Contact National Instruments for further information What kind of signal is CLK10
45. LUDING THE ABOVE RELIABILITY OF OPERATION OF THE SOFTWARE PRODUCTS CAN BE IMPAIRED BY ADVERSE FACTORS INCLUDING BUT NOT LIMITED TO FLUCTUATIONS IN ELECTRICAL POWER SUPPLY COMPUTER HARDWARE MALFUNCTIONS COMPUTER OPERATING SYSTEM SOFTWARE FITNESS FITNESS OF COMPILERS AND DEVELOPMENT SOFTWARE USED TO DEVELOP AN APPLICATION INSTALLATION ERRORS SOFTWARE AND HARDWARE COMPATIBILITY PROBLEMS MALFUNCTIONS OR FAILURES OF ELECTRONIC MONITORING OR CONTROL DEVICES TRANSIENT FAILURES OF ELECTRONIC SYSTEMS HARDWARE AND OR SOFTWARE UNANTICIPATED USES OR MISUSES OR ERRORS ON THE PART OF THE USER OR APPLICATIONS DESIGNER ADVERSE FACTORS SUCH AS THESE ARE HEREAFTER COLLECTIVELY TERMED SYSTEM FAILURES ANY APPLICATION WHERE A SYSTEM FAILURE WOULD CREATE A RISK OF HARM TO PROPERTY OR PERSONS INCLUDING THE RISK OF BODILY INJURY AND DEATH SHOULD NOT BE RELIANT SOLELY UPON ONE FORM OF ELECTRONIC SYSTEM DUE TO THE RISK OF SYSTEM FAILURE TO AVOID DAMAGE INJURY OR DEATH THE USER OR APPLICATION DESIGNER MUST TAKE REASONABLY PRUDENT STEPS TO PROTECT AGAINST SYSTEM FAILURES INCLUDING BUT NOT LIMITED TO BACK UP OR SHUT DOWN MECHANISMS BECAUSE EACH END USER SYSTEM IS CUSTOMIZED AND DIFFERS FROM NATIONAL INSTRUMENTS TESTING PLATFORMS AND BECAUSE A USER OR APPLICATION DESIGNER MAY USE NATIONAL INSTRUMENTS PRODUCTS IN COMBINATION WITH OTHER PRODUCTS IN A MANNER NOT EVALUATED OR CONTEMPLATED BY NATIONAL INSTRUMENTS THE USER OR APPLICATION DESIGNER IS ULTIMATELY RESPONSI
46. Linux Index L LA selection and logical address option 6 20 LabVIEW software 1 6 LEDs on VXI VME MXI 2 D 2 local bus VXIbus 3 7 local resource access functions 7 3 logical address configuration PCI MXI 2 board 6 5 VXI VME MIXI 2 6 20 VXI MXI 2 module 3 3 definition 3 3 Logical Address Configuration Editor See PCI MXI 2 Logical Address Configuration Editor low level access functions 7 3 manual See documentation MapV XIAddress function 7 3 memory setting with Requested Memory control 6 20 user and driver window configuration 6 17 memory requirement specifications PCI MXI 2 A 2 VME VXI MXI 2 A 10 2 6 memory select option VXI shared RAM 6 9 multiple application support with NI VXI and VISA libraries 7 2 MXI CLK 10 signal controlling 6 15 MXI system controller 6 14 MXI transfer limit setting 6 16 MXI 2 1 3 MXI 2 automatic retry feature 6 16 limit on note 6 17 MXlIbus Bus Timeout value setting 6 15 PCI MXI 2 for Linux 1 4 MXIbus cable connections VME MXI 2 module 4 11 VXI MXI 2 module 3 19 MXlIbus capability descriptions PCI MXI 2 board A 1 VME MXI 2 module A 8 VXI MXI 2 module A 4 National Instruments customer education E 1 professional services E 1 system integration services E 1 technical support E 1 worldwide offices E 1 NI VXI NI VISA software common questions D 1 compiling C programs 7 4 symbols 7 4 description 1 5 example progr
47. MEbus capability codes 4 support technical E 1 symbols in C programs 7 4 synchronous MXI protocol 6 16 system configuration functions 7 4 system controller MXI system controller 6 14 MXlIbus system controller 6 27 VMEbus system controller 6 23 system integration services E 1 system IRQ level 6 12 T technical support E 1 telephone technical support E 1 termination MXlIbus termination VME MXI 2 module 4 5 VXI MXI 2 module 3 13 trigger input termination VXI MXI 2 module 3 12 training customer E 1 transfer limit setting MXlIbus 6 16 6 29 VXI VME MXI 2 6 25 trigger input termination VXI MXI 2 module 3 12 troubleshooting resources E 1 National Instruments Corporation I 7 Index U uninstalling NI V XI driver for Linux 5 2 UnMapVXIAddress function 7 3 user and driver window configuration 6 17 window size 6 18 V viClose function 7 4 victext utility interactive control of NI VXI NI VISA 7 2 overview B 1 viMapAddress function 7 3 viMemAlloc function caution 7 3 viOpenDefaultRM function 7 4 viPeekX function 7 3 viPokeX function 7 3 viUnmapAddress function 7 3 VME devices configuring 1 8 VMEbus system controller VXI Slot 0 caution 6 24 VMEbus capability codes VME MXI 2 module A 8 VXI MXI 2 module 4 VME MXI 2 Configuration Editor See VXI VME MXI 2 Configuration Editor VME MXI 2 module 1 13 common questions D 1 configuration 4 1 configuration EEPROM 4 6
48. MXE Getting Started with Your PCI MXI 2 and the NI VXI NI VISA Software for Linux Q7 NATIONAL _ May 2002 Edition y INSTRUMENTS Part Number 370551A 01 Worldwide Technical Support and Product Information ni com National Instruments Corporate Headquarters 11500 North Mopac Expressway Austin Texas 78759 3504 USA Tel 512 683 0100 Worldwide Offices Australia 03 9879 5166 Austria 0662 45 79 90 0 Belgium 02 757 00 20 Brazil 011 3262 3599 Canada Calgary 403 274 9391 Canada Montreal 514 288 5722 Canada Ottawa 613 233 5949 Canada Qu bec 514 694 8521 Canada Toronto 905 785 0085 China Shanghai 021 6555 7838 China ShenZhen 0755 3904939 Czech Republic 02 2423 5774 Denmark 45 76 26 00 Finland 09 725 725 11 France 01 48 14 24 24 Germany 089 741 31 30 Greece 30 1 42 96 427 Hong Kong 2645 3186 India 91 80 4190000 Israel 03 6393737 Italy 02 413091 Japan 03 5472 2970 Korea 02 3451 3400 Malaysia 603 9596711 Mexico 001 800 010 0793 Netherlands 0348 433466 New Zealand 09 914 0488 Norway 32 27 73 00 Poland 0 22 3390 150 Portugal 351 210 311 210 Russia 095 238 7139 Singapore 6 2265886 Slovenia 386 3 425 4200 South Africa 11 805 8197 Spain 91 640 0085 Sweden 08 587 895 00 Switzerland 056 200 51 51 Taiwan 02 2528 7227 United Kingdom 01635 523545 For further support information see the Technical Support and Professional Services appendix To comment on the documentation send email to techpubs ni com
49. Retry The VXI VME MXI 2 has an automatic retry feature for cycles that map from the VXI VMEbus to the MXIbus By default this option is disabled Normally when a cycle maps from the VXI VMEbus to the MXIbus any retry response received on the MXIbus is passed to the VXI VMEbus If you enable the Auto Retry feature the VXI VME MXI 2 automatically retries any MXI cycle that receives a retry response instead of passing a retry response back to the VXI VMEbus The VXI VME MXI 2 automatically continues to retry the MXI cycle until it receives either a DTACK or BERR response which it then passes to the VXI VMEbus Notice that the VXI VME MXI 2 has a limit on the number of automatic retries it will perform on any one cycle If the limit is exceeded and the VXI VME MXI 2 receives another retry it will pass retry back to the VXI VMEbus even though Auto Retry is enabled Transfer Limit You can use this feature to control how many data transfers the VXI VME MXI 2 will perform on the VXI VMEbus before releasing it to another master device that is requesting use of the bus The available options you can choose from are 16 64 and 256 transfers If you do not want the VXI VME MXI 2 to hold the VXI VMEbus long National Instruments Corporation 6 25 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility PCI MXI 2 for Linux enough to perform 256 transfers the default value you can use this control to select a smaller value Arh
50. Se accuse ppt deed 40 to 85 C Relative humidity Noncondensing operating 0 to 95 Noncondensing storage 0 to 9596 EMD ttt eg up ete FCC Class A verified Board dimensions eene Fully enclosed shielded VXI C size board 233 35 by 340 mm 9 187 by 13 386 in deret Single fully implemented MXI 2 bus connector and three SMB connectors Slot requirements esses Single VXI C size slot Compatibility eee Fully compatible with VXI specification VXI keying 1 Class 1 TTL MTBE ettet trt Contact factory Weight eire tete rettet 1 027 kg 2 26 Ib typical no DRAM installed A 6 ni com Appendix A Specifications for VXI MXI 2 Electrical 5 VDC Typical DC current rating 2 5 Maximum DC current rating 3 5 A 5 2 VDC Typical DC current rating 180 mA Maximum DC current rating 225 mA 2 VDC Typical DC current rating 80 mA Maximum DC current rating 100 mA Performance nier 33 MB s SUSTAIN see iie 23 MB s National Instruments Corporation A 7 PCI MXI 2 for Linux Appendix A Specifications for VME MXI 2 VME MXI 2 The following sections list the specifications for the VME MXI 2 module MXIbus Capability Descriptions Master mode A32 A24 and A16 addressing e Mast
51. VME MXI 2 module Similarly the term VXI VME MXI 2 means that information applies to either the VXI MXI 2 or the VME MXI 2 The following flowchart shows where to turn in this manual for more information about configuring and using the hardware and software National Instruments Corporation 1 1 PCI MXI 2 for Linux Chapter 1 Introduction and Quick Start How to Use This Manual Gather What You Need to Get Started Chapter 1 Configure and Install the Chane PCI MXI 2 Chapter 3 Configure and Install the Chapter 4 Configure and Install the VXI MXI 2 VME MXI 2 Chapter 5 Install the NI VXI VISA Software Run the Software Chapter 6 P Configuration Utility vxitedit Review Programming Chapter 7 Considerations Software and Utilities Reference Write Application Program PCI MXI 2 for Linux 1 2 ni com Chapter 1 Introduction and Quick Start PCI MXI 2 Kit Overview The PCI MXI 2 kits link any computer with a PCI bus hereafter referred to as a PCI based computer directly to the VXIbus or VMEbus using the high speed Multisystem eXtension Interface bus MXI 2 A PCI based computer equipped with a VXI MXI 2 kit can function as a VXI Commander and Resource Manager A PCI based computer equipped with a VME MXI 2 kit can function as a VMEbus master and or slave device The PCI MXI 2 kit makes your PCI based computer behave as if it were plugged directly into the VXI
52. VME backplane as an embedded CPU VXI VME module The software included with the kits is for Intel x86 based computers What You Need to Get Started A PCI based computer running Linux kernel 2 2 x or 2 4 x VXIbus or VMEbus mainframe PCI MXI 2 interface board VXI MXI 2 or VME MXI 2 interface module MXI 2 cable Oovovovo wo NI VXI NI VISA software media for the PCI MXI 2 MXI 2 Description MXI 2 is the second generation of the National Instruments MXIbus product line The MXIbus is a general purpose 32 bit multimaster system bus on a cable MXI 2 expands the number of signals on a standard MXI cable by including VXI triggers all VXI interrupts CLK 10 and all of the utility bus signals SYSFAIL SYSRESET and ACFAIL Because MXI 2 incorporates all of these new signals into a single connector the triggers interrupts and utility signals can be extended not only to other mainframes but also to the local CPU in all MXI 2 products using a single cable Thus MXI 2 lets CPU interface boards such as the PCI MXI 2 perform as if they were plugged directly into the VXI VME backplane National Instruments Corporation 1 8 PCI MXI 2 for Linux Chapter 1 Introduction and Quick Start In addition MXI 2 boosts data throughput performance past previous generation MXIbus products by defining new high performance protocols MXI 2 is a superset of MXI All accesses initiated by MXI devices will work with MXI 2 devices However
53. XI 2 Electrical 5 VDC Typical DC current rating 2 2A Maximum DC current rating 3 2A Performance Peaks sn 33 MB s SUSTAINED et ree 23 MB s National Instruments Corporation A 11 PCI MXI 2 for Linux NI VXI NI VISA Software Overview This appendix lists and describes the main programs and files that make up the NI VXI NI VISA software Main Programs and Files This section lists the main programs and files that you can use for controlling your VXI VME interface Note executable not listed in this section is used by the driver and should not be executed by the user directly National Instruments Corporation Resman is the National Instruments multiple mainframe Resource Manager vic is a graphical interactive control program This program is described in detail in the NI VXI Graphical Utilities Reference Manual victext is a text based interactive control program with all the power of vic This program is described in detail in the NI VXI Text Utilities Reference Manual vxiedit is a graphical VXI resource editor program This program is described in detail in the NI VXI Graphical Utilities Reference Manual vxitedit is the text based VXI resource editor program This program is described in detail in the NI VXI Text Utilities Reference Manual vxiinit is the driver initialization program Depending on the version of the driver insta
54. XI 2 boots to an unusable state The Change Factory Configuration switch switch 2 of U21 lets you change the factory default configuration settings by permitting writes to the factory settings section of the EEPROM This switch serves as a safety measure and should not be needed under normal circumstances When this switch is off its default setting the factory configuration of the EEPROM is protected so any writes to the factory area will be ignored The factory area is protected regardless of the setting of switch 1 of U21 Figure 4 5 shows the configuration settings for EEPROM operation The settings of switches 3 and 4 have no effect on EEPROM configuration National Instruments Corporation 4 7 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation Onboard DRAM PCI MXI 2 for Linux U21 a Boot from User Configuration Factory Configuration Protected Default EIE L WU b Boot from Factory Configuration Factory Configuration Protected SAG c Boot from User Configuration Factory Configuration Unprotected NFL i WI d Boot from Factory Configuration Factory Configuration Unprotected U21 U21 Figure 4 5 EEPROM Operation The VME MXI 2 can accommodate up to two 1 35 in DRAM SIMMs Table 4 1 lists the SIMMs you can use You can use 32 or 36 bit SIMMs since DRAM parity is not required Because the VME MXI 2 supports only one organization at a time a
55. XI VME Bus Timeout Value 125 us VXI VME Auto Retry Disabled VXI VME Transfer Limit 256 VXI VME Arbiter Type Priority VXI VME Request Level 3 VXI VME Fair Request Enabled National Instruments Corporation 1 13 PCI MXI 2 for Linux Introduction and Quick Start Chapter 1 Introduction and Quick Start Table 1 7 VXI VME MXI 2 Configuration Editor Default Settings Continued Editor Field Default Setting VXI VME Arbiter Timeout Enabled MXI System Controller Auto MXI Bus Timeout Value ms MXI Auto Retry Disabled MXI Transfer Limit Unlimited MXI Parity Checking Enabled MXI Fair Requester Disabled MXI CLK10 Set by hardware switch VXI MXI 2 only Assumes no DRAM is installed If DRAM is installed the Address Space would be A32 and Requested Memory would match the amount of DRAM PCI MXI 2 for Linux 1 14 ni com PCI MXI 2 Configuration and Installation This chapter contains the instructions to configure and install the PCI MXI 2 module Caution Electrostatic discharge damage several components on your PCI MXI 2 module To avoid such damage in handling the module touch the antistatic plastic package to a metal part of your computer chassis before removing the PCI MXI 2 from the package Configure the PCI MXI 2 This section describes how to configure the configuration EEPROM on the PCI MXI 2 Figure 2 1 shows the PCI MXI 2 The drawing shows
56. XIbus cable to terminate the MXIbus You can manually control MXIbus termination by defeating the automatic circuitry Use switches 1 and 2 of the four position switch at location U35 to control whether MXIbus termination is automatic Figure 3 9a on Figure 3 9b or off Figure 3 9c The settings of switches 3 and 4 have no effect on MXIbus termination National Instruments Corporation 3 13 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation Use switch 2 of U35 to select whether you want the VXI MXI 2 to automatically control termination of the MXIbus Switch 1 of U35 lets you manually control whether to terminate the MXIbus when automatic termination is turned off Switch 1 has no effect when switch 2 is set for automatic MXIbus termination you must turn off automatic termination if you want to manually control termination Restore Factory Configuration No Yes Change Factory Configuration No Yes Automatic MXIbus Termination Yes No Terminate MXIbus Yes No a Automatic MXIbus Termination Default Restore Factory Configuration No Yes Change Factory Configuration No Yes Automatic MXIbus Termination Yes No Terminate MXIbus Yes No b Terminate MXIbus On 035 Restore Factory Configuration Yes Change Factory Configuration No o Yes Automatic MXIbus Termination Yes No Terminate MXlbus Yes No
57. ams 7 2 installing 5 1 for Linux 1 8 5 1 interactive control 7 2 overview 7 1 programming considerations 7 2 local resource access functions 7 3 low level access functions 7 3 multiple applications support 7 2 system configuration functions 7 4 programs and files header files B 2 main programs and files B 1 removing NI VXI driver for Linux 5 2 setting up for use 5 2 NIVXIPATH environment variable 5 2 0 online technical support E 1 ni com P parity checking MXlIbus 6 29 PATH environment variable 6 1 PCI Bus options 6 17 expansion ROM 6 18 user window and driver window 6 17 window size 6 18 PCI MXI 2 board common questions D 1 configuration See also PCI MXI 2 Configuration Editor configuration EEPROM 2 3 default settings Bus Configuration Editor table 1 11 Device Configuration Editor table 1 11 hardware settings table 1 9 Logical Address Configuration Editor table 1 10 hardware description 1 4 installation 2 3 quick start installation 1 6 specifications electrical A 3 environmental A 2 functionality A 2 MXlIbus capability descriptions 1 performance A 3 physical A 3 requirements A 2 PCI MXI 2 Bus Configuration Editor default settings table 1 11 expansion ROM 6 18 illustration 6 14 National Instruments Corporation 1 5 MXI bus A24 A32 write posting 6 17 MXI Bus Time Out BTO 6 15 MXI CLK10 signal 6 15 MXI system controller 6 14 MXI
58. and what kind of signal do I need for an external CLK10 CLK10 is a differential ECL signal on the V XIbus backplane However the oscillator for the VXI MXI 2 and the EXTCLK input from the front panel use TTL Therefore you need to supply a TTL level signal for EXTCLK and our voltage converters will convert the signal to differential ECL CLK10 is not applicable to VME What is the accuracy of the CLK10 signal The CLK10 generated by the VXI MXI 2 is 100 ppm 0 01 as per the VXIbus specification If you need a more accurate CLK10 signal you can use the EXTCLK input at the front of VXI MXI 2 CLK10 is not applicable to VME Whenever I try to execute any of the NI VXI utilities I receive a message similar to this one error in loading shared libraries libnivxi so cannot open shared object file no such file or directory What does this error message mean This usually means that the application could not load the NI VXI library Check the environment variable NIVXIPATH and your etc ld so conf file NIVXIPATH should be set only to the directory where you installed NI VXI usr local nivxi by default etc 1d so contf should include the directory where you installed the NI VXI library usr local nivxi 1ib by default Run ldconfig to reread this file National Instruments Corporation D 3 PCI MXI 2 for Linux Appendix D Common Questions PCI MXI 2 for Linux Whenever I try to execute any of the NI VXI utilities
59. anel Features tet ve dene eer re de 3 3 Removing the Metal Enclosure 3 3 VX Ib s Logical Addr6ss eet to et e 3 3 VXIbus Slot O Non Slot nnne enne 3 5 VXlIb s Local B s 3 8 ine abi eu 3 7 National Instruments Corporation Vii PCI MXI 2 for Linux Contents VXIbus CEKI1O Routing 5 3 8 Trigger Input Termination eese nene en rennen 3 12 MXlIbus Terminatioh rte ehe estis 3 13 Configuration EEPROM sss eene n eem EES 3 14 Onboard tiec tto pe eet 3 17 Install the uoa he n D eget eel pee ee de 3 18 Connect the MXTb s Cable eis cies eee teet rt pete cese eet s 3 19 Chapter 4 VME MXI 2 Configuration and Installation Configure the VME MXL2 iecit tet ihe te itte ree de Re ee tene 4 1 Front Panel F at res eee pee RR eem 4 3 VMEbus A16 Base Address aaa r emere 4 3 VME MXI 2 Intermodule Signaling eee 4 4 MXlIbus Termination uie ea die rs 4 5 Configuration EEPROM cq ie 4 6 Onboard DRAM 3s eee a ie deseleteta eee 4 8 Install the V ME MXE2 s eed eH e ee tat 4 10 Connectthe MX I bus Cables teet teta eoe 4 11 Chapter 5 NI VXI NI VISA Software Installation Installing the NI VXI NI VISA Software for Linux eene 5 1 Removing the NI VXI Driver for Linux
60. arbitration in the VXI VMEbus MXIbus system By default this option is disabled which puts the VXI VME MXI 2 in normal operating mode In normal operating mode non interlocked multiple masters can operate simultaneously in the VXI VMEbus MXlIbus system A deadlock occurs when a MXIbus master requests use of a VXI VMEbus resource in another VXI VMEbus mainframe while a VXI VMEbus master in that mainframe is in the process of requesting a resource across the MXIbus When this situation occurs the VXI VMEbus master must give up its bus ownership to resolve the conflict The RETRY signal is used to terminate the transfer on the VMEbus however devices in the VXI VMEbus mainframe must be able to detect a RETRY caused by a deadlock condition so that they can retry the operation Any master device that cannot detect the retry protocol will interpret the response as a BERR signal instead The VXI VME MXI 2 is shipped from the factory configured for normal operating mode non interlocked If MXIbus transfers will be occurring both into and out of the mainframe and the VXI VMEbus modules in your system do not have the capability for handling retry conditions you may want to configure the VXI VME MXI for interlocked arbitration mode by clicking on the Enable checkbox In this mode no software provisions for deadlock conditions are required However parallel accesses in separate VXI VMEbus mainframes are no longer possible and system performance may
61. ation 6 28 MXI auto retry 6 28 MXI bus system controller 6 27 MXI bus timeout value BTO 6 27 MXI CLK10 signal 6 29 caution statement 6 29 MXI fair requester 6 29 parity checking 6 29 transfer limit 6 29 VXI VME bus options 6 23 advanced VXI settings 6 24 illustration 6 25 VXI VME bus timeout value BTO 6 24 arbiter timeout 6 27 arbiter type 6 26 request level 6 26 transfer limit 6 25 VXI VME auto retry 6 25 VXI VME fair requester 6 26 VXI VME MXI 2 selection dialog box figure 6 19 VXI VME MXI 2 note 6 19 VXIbus CLK10 routing 3 8 CLK10 generation figure 3 9 SMB CLK 10 settings figure 3 9 3 11 VXIbus local bus 3 7 VXIbus logical address 3 3 See also logical address VXIbus logical address See logical address VXIbus Slot 0 non Slot 0 3 5 ni com VXIedit configuration utility VME device configuration information 1 8 VXIEDIT software utility illustration 6 2 running 6 1 text based equivalent utility note 6 1 VXILINUX symbol defining 7 4 VXImemaAlloc function caution 7 3 VXI MXI 2 module 3 1 common questions D 1 configuration 3 1 CLK10 routing 3 8 configuration EEPROM 3 14 front panel features 3 3 MXlIbus termination 3 13 onboard DRAM DRAM configurations table 3 17 SIMM size configuration figure 3 18 removing metal enclosure 3 3 right side cover figure 3 2 trigger input termination 3 12 VXIbus CLK10 routing CLK10 generation figure 3 9 SMB CLK10 settings
62. ation by defeating the automatic detection circuitry Use the three position jumper W2 to select automatic Slot 0 detection Slot 0 or Non Slot 0 operation Figure 3 3 shows these three settings Caution Do not install a device configured for Slot 0 into another slot without first reconfiguring it to either Non Slot 0 or automatic configuration Neglecting to do this could damage the device the V XIbus backplane or both National Instruments Corporation 3 5 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation W2 Slot 0 Auto Nonslot a Automatic Slot 0 Detection Default W2 Nonslot b Manual Slot 0 Configuration W2 Nonslot c Manual Nonslot 0 Configuration When the VXI MXI 2 is installed in Slot 0 it becomes the VMEbus System Controller In this role it has VMEbus Data Transfer Bus Arbiter circuitry that accepts bus requests on all four VMEbus request levels prioritizes the requests and grants the bus to the highest priority requester As VMEbus System Controller the VXI MXI 2 also drives the 16 MHz Figure 3 3 VXIbus Slot Configuration VMEbus system clock by an onboard 16 MHz oscillator As required by the V XIbus specification the VXI MXI 2 drives the 10 MHz signal CLK10 on a differential ECL output when installed in Slot 0 When not installed in Slot 0 the VXI MXI 2 only receives the CLK10 signal PCI MXI 2
63. ational Instruments LabVIEW to ease your programming task This standardized program matches the modular virtual instrument capability of VXI and can reduce your VXI VMEbus software development time LabVIEW is a complete programming environment that departs from the sequential nature of traditional programming languages and features a graphical programming environment PCI MXI 2 for Linux You can use this section as a guide to quickly configure and operate your VXIor VME system using the PCI MXI 2 and the VXI MXI 2 or 2 This section assumes that you intend to perform a basic configuration as follows e You have one PCI MXI 2 interface module which you will install in your PCI based computer as the Resource Manager logical address e You have either one C size VXI MXI 2 or 60 B size 2 which you will install in a VXI or VME chassis respectively and connect to the PCI MXI 2 You will be using the NI VXI NI VISA software for initialization configuration and device interaction e You will use the default hardware and software settings The PCI MXI 2 is the main controller the VXI VME Resource Manager and a message based device Your system contains only one VXI or VME chassis There is no shared memory used on the PCI based computer the PCI MXI 2 or the VXI VME MXI 2 Refer to the Default Settings section for a complete listing of the hardware and software default se
64. ce Manager The simplest required communication protocol supported by message based devices in a VXIbus system It utilizes the A16 communication registers to transfer data using a simple polling handshake method A mechanism that signifies that a device will immediately give a successful acknowledge to a write transfer and place the transfer in a local buffer The device can then independently complete the write cycle to the destination G 10 ni com Index A A16 base address VMEbus 4 3 A16 write posting VXI VME MXI 2 6 21 A24 A32 write posting PCI MXI 2 6 17 VXI VME MXI2 6 21 address space configuration PCI MXI 2 6 18 VXI VME MXI 2 6 20 arbiter type setting 6 26 arbitration mode interlocked 6 22 automatic retry feature setting MXI 2 6 16 limit on note 6 17 MXlIbus 6 28 VXI VME 6 25 BTO See Bus Time Out BTO value setting bulkhead cables D 3 Bus Time Out BTO value setting MxXlIbus 6 15 6 27 VXI VME 6 24 C C programs compiling 7 4 sample programs 7 4 symbols 7 4 cables connecting MXIbus cable VME MXI 2 module 4 11 VXI MXI 2 module 3 19 CLK10 routing VXIbus 3 8 SMB CLK 10 settings figure 3 11 National Instruments Corporation VXIbus CLK10 routing figure 3 9 CLK10 signal MXIbus common questions D 3 controlling direction of 6 15 setting 6 15 Close VXIlibrary function 7 4 common questions about NI VXI NI VISA software D 1 compiling C programs 7 4 symbols
65. ch 1 FOV on U17 to the ON position as shown in Figure C 2 to restore the factory configuration U17 FOV TST POS fo L er Figure C 2 Restoring the Factory Configuration C 2 ni com Appendix C EEPROM Configuration B Note If you have to remove the PCI MXI 2 module to access switch 1 follow the installation instructions given in Chapter 2 PCI MXI 2 Configuration and Installation to reinstall the PCI MXI 2 module Replace the computer cover 5 Turnonthe computer The computer should boot this time because the factory default configuration is being used to initialize the PCI MXI 2 module 6 Run vxiedit to readjust the PCI MXI 2 configuration Refer to Chapter 6 NI VXI Configuration Utility for instructions on using this utility 7 After saving the configuration reboot the computer Remove the top cover or access port to the PCI bus 9 Change switch 1 FOV on U17 to the OFF position 10 Replace the computer cover 11 Turn on the computer If the computer does not boot with this configuration you will have to repeat these steps modifying your configuration until a final configuration is reached National Instruments Corporation C 3 PCI MXI 2 for Linux Common Questions This appendix addresses common questions you may have about using the NI VXI bus interface software on the PCI MXI 2 platform How can I determine which version of the NI VXI software
66. ctive only when S3 is set to OUT INVERTED NON INVERTED d Receive External CLK SMB with 500 Termination Figure 3 6 SMB CLK10 Settings National Instruments Corporation 3 11 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation The VXI MXI 2 can also drive or receive the MXIbus CLK10 signal Switch S7 controls whether the VXI MXI 2 drives MXIbus CLK10 from the VXIbus CLK10 or receives MXIbus CLK10 As shown in Figure 3 5c if W3 is configured to use the MXIbus CLK10 to generate the VXIbus CLK10 signal switch S7 must be configured to receive MXIbus CLK10 This is shown again in Figure 3 7a If you change the 57 setting to drive CLK10 out the MXIbus do not set the W3 jumper to receive the MXIbus CLK10 instead use the settings shown in Figure 3 5a or Figure 3 5b as appropriate UN Caution Do not configure more than one MXIbus device to drive the MXIbus CLK10 Having a second device driving MXIbus CLK10 could damage the device Figure 3 7 shows the configuration settings for receiving and driving MXlIbus CLK10 respectively Drive CLK10 out MXIbus Drive CLK10 out MXIbus Receive CLK10 from MXIbus Receive CLK10 from MXIbus a Receive CLK10 from MXIbus Default b Drive MXIbus CLK10 from VXIbus CLK10 Figure 3 7 Receiving or Driving MXIbus CLK10 Trigger Input Termination You can use switch S2 to terminate the external trigger input SMB with 50 Fig
67. d useful source of information for writing compiling and debugging C programs National Instruments Corporation 7 5 PCI MXI 2 for Linux Specifications This appendix lists various module specifications of the PCI MXI 2 VXI MXI 2 and VME MXI 2 such as physical dimensions and power requirements PCI MXI 2 The following sections list the specifications for the PCI MXI 2 module MXIbus Capability Descriptions National Instruments Corporation Master mode A32 A24 and A16 addressing Master mode block transfers and synchronous block transfers Slave mode A32 A24 and A16 addressing Slave mode block transfers and synchronous block transfers Master mode D32 D16 and 08 data sizes Slave mode D32 D16 and 08 data sizes Optional MXIbus System Controller Can be a fair MXIbus requester Can lock the MXIbus for indivisible transfers Can terminate the MXIbus MXlIbus master retry support MXlIbus slave retry support Interrupt handler for levels 7 to 1 Interrupt requester for levels 7 to 1 MXIbus D32 D16 D08 O interrupt handler MXIbus D32 D16 D08 O interrupter Release on Acknowledge or Register Access interrupter MXlIbus bus timer programmable limit Automatic MXIbus System Controller detection A 1 PCI MXI 2 for Linux Appendix A PCI Functionality Requirements Environmental PCI MXI 2 for Linux Specifications for PCI MXI 2 PCI Initiator master capability PCI Target
68. d bottom edges of the front panel PCI MXI 2 for Linux 4 10 ni com Chapter 4 VME MXI 2 Configuration and Installation 5 Check the installation 6 Connect the cables as described in the following section before restoring power 7 Replace or close any doors or covers to the mainframe Connect the MXIbus Cable There are two basic types of MXI 2 cables MXI 2 cables can have either a single connector on each end or a single connector on one end and a double connector on the other end Connect the labeled end of the cable to the MXI 2 device that will be the MXlIbus System Controller Connect the other end of the cable to the other device Be sure to tighten the screw locks to ensure proper pin connection Figure 4 7 shows the correct cabling for a VME system containing a PCI MXI 2 board in a PCI based computer cabled to a VME MXI 2 module residing in Slot 1 of a VMEbus mainframe Notice that you can expand your system to include other devices by using an additional MXI 2 cable However in such a case the first cable needs to have a double connector on one end You can then use a cable with a single connector on each end to connect the last device on the MXIbus National Instruments Corporation 4 11 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation 1 VME Chassis 5 Connection to External Computer 2 VME MXI 2 Module 6 2 Interface Module 3 Additional MXI 2 Cable 7
69. d by the PCI MXI 2 for use via the NI VXI low level function calls MapVXIAddress uses this address space to allocate regions for use by the VXIpeek and VXIpoke macros Volts Volts direct current VXI Interactive Control Program a part of the NI VXI bus interface software package Used to program VXI devices and develop and debug VXI application programs Versa Module Eurocard or IEEE 1014 A device configured for installation in Slot 0 of a VXIbus mainframe or Slot 1 of a VMEbus chassis This device is unique in the VMEbus system in that it performs the VMEbus System Controller functions including clock sourcing and arbitration for data transfers across the backplane Installing such a device into any other slot can damage the device the VMEbus V XIbus backplane or both VMEbus Extensions for Instrumentation A program in the NI VXI bus interface software package that initializes the board interrupts shared RAM VXI register configurations and bus configurations PCI MXI 2 for Linux Glossary VXItedit W Word Serial Protocol write posting PCI MXI 2 for Linux VXI Resource Editor program a part of the NI VXI bus interface software package Used to configure the system edit the manufacturer name and ID numbers edit the model names of VXI and non VXI devices in the system as well as the system interrupt configuration information and display the system configuration information generated by the Resour
70. e When driving the MXIbus CLK10 the VXIbus CLK10 is used as the source In this case change the jumper setting so that it does not use the MXIbus CLK10 as the source for the VXIbus CLK10 UN Caution Do not configure more than one MXIbus device to drive MXI CLK 10 Setting up a second device to drive MXI CLK10 could damage the device National Instruments Corporation 6 29 PCI MXI 2 for Linux Using the NI VXI NI VISA Software This chapter discusses programming information for you to consider when developing applications that use the NI VXI NI VISA driver After installing the driver software you can begin to develop your VXI VME application software Be sure to check the README file for the latest application development notes You must run Resman each time the computer or chassis power is cycled so that your application can access devices in the VXI or VME chassis The NI VXI software was designed for use in VXI systems Because VXI is a superset of VME you can also use the NI VXI functions as a comprehensive set of programming tools for VME systems Refer to the NI VXI User Manual and the NI VXI online help for overviews of NI VXI and detailed descriptions of the NI VXI functions The user manual is available in the NIVXI manuals directory where NIVXI refers to the actual location where you have installed the NI VXI software Use the Acrobat Reader program to open and navigate through this manual Notice that the function
71. e LabVIEW or LabWindows CVI Try the following in vic 1 Click the Bus Access tab at the top of the window and select InReg as the Operation along the left side of the window 2 Select the VXI MXI 2 or VME MXI 2 as the Device Name under Input Parameters and the Id Logical Address register under Input Parameters 3 Click Go If the CMPL light along the right side of the window is green and the output value ends in an FF6 you have successfully read the manufacturer ID for National Instruments 1 8 ni com Chapter 1 Introduction and Quick Start The same functionality is available in victext with the vxiinreg command You can use help vxiinreg for the command s parameter description You may now want to read the configuration registers from other VXI devices in your system using the same procedure The InReg operation accesses only the upper 16 KB of A16 space Try reading the registers from one of the devices listed in the Resource Manager Display of vxiedit In this way you can verify that your PCI MXI 2 can access each device in your VXI system successfully You can also access VXI and VME defines that are configured in A16 A24 and A32 address spaces by using the In and Out operations in vic or the vxiinor vxiout commands in victext Default Settings This section summarizes the hardware and software default settings for the PCI MXI 2 kit If you need more information about a particular setting or if you want to try a di
72. e and install the VME MXI 2 module This chapter applies only if you ordered the VME 2 kit If you ordered VXI MXI 2 kit you should refer to Chapter 3 VXI MXI 2 Configuration and Installation UN Caution Electrostatic discharge can damage several components on your VME MXI 2 module To avoid such damage in handling the module touch the antistatic plastic package to a metal part of your VMEbus chassis before removing the VME MXI 2 from the package Configure the VME MXI 2 This section describes how to configure the following options on the VME MXI 2 e VMEbus A16 base address e VME MXI intermodule signaling e MXlIbus termination e Configuration EEPROM e Onboard DRAM The VME MXI 2 automatically detects if it is located in the first slot of the chassis to perform the VMEbus System Controller functions It is not necessary to configure the VME MXI 2 System Controller option The module can be installed in any slot of a VMEbus chassis Figure 4 1 shows the VME MXI 2 The drawing shows the location and factory default settings of the configuration switches and jumpers on the module National Instruments Corporation 4 1 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation
73. e boards in D size mainframes The VXI MXI 2 has no P3 connector and cannot provide P3 Slot 0 control to VXI devices requiring this capability N Caution If the VXI MXI 2 is not configured for automatic Slot 0 detection be certain that the slot you select in your VXIbus mainframe matches the VXI MXI 2 configuration as either a Slot 0 device or a Non Slot 0 device If you install your VXI MXI 2 into a slot that does not correspond with the jumper setting you risk damage to the VXI MXI 2 the VXIbus backplane or both 4 Insert the VXI MXI in the slot you have selected by aligning the top and bottom of the board with the card edge guides inside the mainframe Slowly push the VXI MXI 2 straight into the slot until its plug connectors are resting on the backplane receptacle connectors Using slow evenly distributed pressure press the VXI MXI 2 straight in until it seats in the expansion slot The front panel of the VXI MXI 2 should be even with the front panel of the mainframe 5 Tighten the retaining screws on the top and bottom edges of the front panel 6 Check the installation 7 Connect the cables as described in the following section before restoring power 8 Replace or close any doors or covers to the mainframe Connect the MXIbus Cable There are two basic types of MXI 2 cables MXI 2 cables can have either a single connector on each end or a single connector on one end and a double connector on the other end Connect th
74. e labeled end of the cable to the MXI 2 device that will be the MXIbus System Controller Connect the other end of the cable to the other device Be sure to tighten the screw locks to ensure proper pin connection Figure 3 12 shows the correct cabling for a VXI system containing a PCI MXI 2 board in a PCI based computer cabled to a VXI MXI 2 module residing in Slot 0 of a VXIbus mainframe Notice that you can expand your system to include other devices by using an additional MXI 2 cable However in such a case the first cable needs to have a double connector on one end You can use a cable with a single connector on each end to connect the last device on the MXIbus National Instruments Corporation 3 19 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation 1 VXI Mainframe 5 Connection to External Computer 2 VXI MXI 2 Slot 0 Module 6 2 Interface Module 3 Additional MXI 2 Cable 7 2 Cable 4 Connection to Other Mainframes Figure 3 12 MXI 2 Cable Configuration Using a PCI MXI 2 and a VXI MXI 2 When you have properly connected the MXI 2 cable power on the V XIbus mainframe and then the computer hy Note Always turn on the mainframe first Doing so makes it possible for your external computer to access the VXI boards in the mainframe upon startup PCI MXI 2 for Linux 3 20 ni com VME MXI 2 Configuration and Installation This chapter contains the instructions to configur
75. ed NI VXI in usr2 nivxi type the following command in csh setenv NIVXIPATH usr2 nivxi in bash or ksh export NIVXIPATH usr2 nivxi The NI VISA software is configured to be loaded in the usr local vxipnp directory If you have installed the software in another directory set the VXIPNPPATH environment variable to your directory For example if you have installed NI VXI in usr2 vpp type the following command in csh setenv VXIPNPPATH usr2 vpp in bash or ksh export VXIPNPPATH usr2 vpp 5 2 ni com Chapter 5 NI VXI NI VISA Software Installation Place these lines in your cshrc or login C shell or profile Bourne or Korn shells so they will execute automatically the next time you log in Completing the Software Installation After the software is installed run Resman the National Instruments Resource Manager You must run Resman every time the computer or chassis power is cycled so that your application can access devices in the VXI VME chassis After you run Resman you are ready to use the NI VXI Resource Editor program vxiedit to interactively configure the hardware in your system Refer to Chapter 6 NI VXI Configuration Utility for instructions on using the configuration editors in vxiedit National Instruments Corporation 5 3 PCI MXI 2 for Linux NI VXI Configuration Utility Ej This chapter contains instructions for using the VXI Resource Editor utility of the NI VXI software to configure
76. eme of the VXIbus specification in which each device is assigned an 8 bit value called the logical address This logical address allocates 64 bytes of space to the device within the upper quarter of A16 space The VME MXI 2 cannot be configured to locate its registers in the lower three quarters of A16 space The A16 base address of the VME MXI 2 will be address lines 15 and 14 high with address lines 13 through 6 matching the logical address of the 2 and address lines 5 through 0 low In other words the 16 base address of the VME MXI 2 module s 64 byte register set is as calculated below base address C000 hex logical address x 40 hex The factory default logical address for the VME MXI 2 is 1 which locates the registers in the range C040 hex to CO7F hex You can change the logical address of the VME MXI 2 by changing the setting of the 8 bit DIP switch at location designator U20 The ON position of the DIP switch corresponds to a logic value of 0 and the OFF position corresponds to a logic value of 1 Allowable logical addresses for the VME MXI 2 range from 1 to 254 hex FE Verify that no other devices in your system use the A16 address space for the 2 If possible configure all other VMEbus A16 devices to be located within the lower three quarters of A16 space Also when setting base addresses keep in mind the grouping requirements set by the system hierarchy Refer to VXI 6 VXIbus Mainframe Extende
77. emory on the motherboard or into onboard memory on the PCI MXI 2 Because each half is independent of the other you can choose from any of the following mapping options e Halfthe VXI VME shared RAM mapped to system memory the other half mapped to PCI MXI 2 onboard memory e Both halves mapped to PCI MXI 2 onboard memory e Both halves mapped to system memory PCI MXI 2 for Linux 6 8 ni com Chapter 6 NI VXI Configuration Utility Enable Byte Swapping This checkbox indicates whether byte swapping should be performed for slave accesses to this half of the VXI VME shared RAM space For example if the native byte order of the shared RAM is Motorola Big Endian and you want to present data to the VXI VMEbus in Intel Little Endian byte order you will need to enable byte swapping The default value is non swapped Click on the checkbox if you want to enable byte swapping This field is ignored if the Memory Select field is set to Onboard memory Memory Select This option determines where this half of the VXI VME shared RAM is mapped By default the shared RAM is mapped to System memory If you want to use the RAM on the 2 choose the Onboard memory option Window Mapping You can click on the checkbox at the bottom of the screen if you want to map both halves of the inward window to the same address When both halves of the inward window are mapped to the same destination with the same byte order the windows e
78. er mode block transfers and synchronous block transfers Slave mode A32 24 and A16 addressing e Slave mode block transfers and synchronous block transfers e Master mode D32 D16 and DO8 data sizes e Slave mode 032 D16 and DOS data sizes e Optional MXIbus System Controller e Can be a fair MXIbus requester e Can lock the MXIbus for indivisible transfers e Can terminate the MXIbus e MXlIbus master retry support e MXlIbus slave retry support e Interrupt handler for levels 7 to 1 e Interrupt requester for levels 7 to 1 e MXIbus D32 D16 D08 O interrupt handler e MXIbus D32 D16 D08 O interrupter e Release on Acknowledge or Register Access interrupter e MXlIbus bus timer programmable limit e Automatic MXIbus System Controller detection Automatic MXIbus termination detection VMEbus Capability Codes PCI MXI 2 for Linux A32 24 A16 master VMEbus master A32 A24 and 16 addressing A32 24 16 amp 1 VMEbus slave A32 A24 and 16 addressing D32 D16 DOS EO master VMEbus master D32 D16 and D08 data sizes A 8 ni com D32 D16 DO8 EO slave BLT MBLT master BLT MBLT slave RMW master RMW slave Appendix A D32 D16 D08 O Interrupt Handler D32 D16 D08 O Interrupter ROAK National Instruments Corporation RORA 9 Specifications for VME MXI 2 VMEbus s
79. es for VXI VME MXI and PCI By using MITE DMA to transfer data and commands to and from devices the MITE frees up a computer s microprocessor to perform other tasks such as data analysis and presentation In addition to DMA the MITE incorporates both the new Synchronous MXI protocol and VME64 MBLT 8 byte block transfers in which both the address bus and data bus are used to transfer data directly into the ASIC to perform the fastest transfer operation to instruments Software Description The NI VXI NI VISA bus interface software for the PCI MXI 2 and Linux includes a Resource Manager graphical and text based interactive VXI resource editor programs a comprehensive library of software routines for VXI VME programming and graphical and text based interactive control programs for interacting with VXI VME or VISA You can use this software to seamlessly program multiple mainframe configurations and have software compatibility across a variety of VXI VME controller platforms NI VISA has a comprehensive library of software routines not only for VXI VME programming but also for GPIB GPIB VXI and serial You can use this software to program instruments connected via different types of interfaces National Instruments Corporation 1 5 PCI MXI 2 for Linux Chapter 1 Introduction and Quick Start Optional Software Quick Start Your 2 kit includes the NI V XI NI VISA bus interface software In addition you can use N
80. ess used in making chips A message based device which is also a bus master and can control one or more Servants A set of registers through which the system can identify a module device type model manufacturer address space and memory requirements In order to support automatic system and memory configuration the VXIbus specification requires that all VXIbus devices have a set of such registers National Instruments Corporation G 3 PCI MXI 2 for Linux Glossary D daisy chain Data Transfer Bus DIP DMA DRAM driver window DTACK DTB dynamically configured device dynamic configuration E ECL EEPROM embedded controller EMC PCI MXI 2 for Linux A method of propagating signals along a bus in which the devices are prioritized on the basis of their position on the bus DTB one of four buses on the VMEbus backplane The DTB is used by a bus master to transfer binary data between itself and a slave device Dual Inline Package Direct Memory Access a method by which data is transferred between devices and internal memory without intervention of the central processing unit Dynamic RAM A region of PCI address space that is decoded by the PCI MXI 2 for use by the NI VXI software Data Acknowledge signal See Data Transfer Bus A device that has its logical address assigned by the Resource Manager A VXI device initially responds at Logical Address 255 when its MODID line is asserted
81. et the VXI and VME shared RAM size and the shared RAM pool The Advanced button leads to additional options that configure the upper and lower half of the shared RAM area 6 6 ni com Chapter 6 NI VXI Configuration Utility VXI VME Shared RAM Size This field indicates the amount of RAM in bytes that is shared in either A24 or A32 space This determines the total shared RAM size which is then divided into two equal halves that you can set up independently of one another 5 Note When the Address Space field is in the default setting of 16 only this field is ignored Shared RAM Pool This field indicates the size of memory in kilobytes that is allocated at startup This memory is used by the lower upper half window when the Memory Select control accessible through the Advanced popup field is set to System memory Memory Range Default Value 0 to 65 535 KB 0 KB The following table indicates how the Shared RAM Pool relates to the VXI Shared RAM Size depending on the setting of the Memory Select control for the upper and lower half windows Lower Half Upper Half Shared RAM Pool Window Window Window System memory System memory Equal to VXI VME Shared RAM Size System memory Onboard memory Half the VXI VME Shared RAM Size Onboard memory System memory Half the VXI VME Shared RAM Size Onboard memory Onboard memory 0 The shared RAM pool is used by VXImemAl11oc func
82. eviewed for technical accuracy In the event that technical or typographical errors exist National Instruments reserves the right to make changes to subsequent editions of this document without prior notice to holders of this edition The reader should consult National Instruments if errors are suspected In no event shall National Instruments be liable for any damages arising out of or related to this document or the information contained in it EXCEPT AS SPECIFIED HEREIN NATIONAL INSTRUMENTS MAKES NO WARRANTIES EXPRESS OR IMPLIED AND SPECIFICALLY DISCLAIMS ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE CUSTOMER S RIGHT TO RECOVER DAMAGES CAUSED BY FAULT OR NEGLIGENCE ON THE PART OF NATIONAL INSTRUMENTS SHALL BE LIMITED TO THE AMOUNT THERETOFORE PAID BY THE CUSTOMER NATIONAL INSTRUMENTS WILL NOT BE LIABLE FOR DAMAGES RESULTING FROM LOSS OF DATA PROFITS USE OF PRODUCTS OR INCIDENTAL OR CONSEQUENTIAL DAMAGES EVEN IF ADVISED OF THE POSSIBILITY THEREOF This limitation of the liability of National Instruments will apply regardless of the form of action whether in contract or tort including negligence Any action against National Instruments must be brought within one year after the cause of action accrues National Instruments shall not be liable for any delay in performance due to causes beyond its reasonable control The warranty provided herein does not cover damages defects malfunctions or service failures caused by owner s fa
83. ews on the bottom and the five screws on the right side cover of the metal enclosure If the SIMMs are 4 M x 32 or larger S6 should be in the OFF setting as shown in Figure 3 11a For SIMMs smaller than 4 M x 32 use the ON setting as shown in Figure 3 11b SIMM Size SIMM Size 4M x 32 e 4M x 32 and Larger and Larger gomm S6 J S6 ANNE EF peor m a 4M x 32 and Larger b Smaller than 4 M x 32 Figure 3 11 SIMM Size Configuration Refer to Table 3 1 for how to adjust the switch ON or OFF for all supported DRAM configurations Many of the DRAM options are available from National Instruments Install the VXI MXI 2 PCI MXI 2 for Linux This section contains general installation instructions for the VXI MXI 2 Refer to your VXIbus mainframe user manual or technical reference manual for specific instructions and warnings 1 Plugin your mainframe before installing the VXI MXI 2 The power cord grounds the mainframe and protects it from electrical damage while you are installing the module Caution protect both yourself and the mainframe from electrical hazards the mainframe should remain off until you are finished installing the VXI MXI 2 module 2 Remove or open any doors or covers blocking access to the mainframe slots 3 18 ni com Chapter 3 VXI MXI 2 Configuration and Installation 3 If you are installing the VXI MXI 2 into a D size mainframe install a support designed for installing C siz
84. f a MXI VME V XIbus device that detects data transfer cycles initiated by a VMEbus master and responds to the transfers when the address specifies one of the device s registers A device is in slave mode it if is responding to a bus cycle A device configured for installation in Slot 0 of a VXIbus mainframe This device is unique in the VXIbus system in that it performs the VMEbus System Controller functions including clock sourcing and arbitration for data transfers across the backplane Installing such a device into any other slot can damage the device the V XIbus backplane or both A device whose logical address cannot be set through software that is it is not dynamically configurable A VMEbus signal that is used by a device to indicate an internal failure A failed device asserts this line In VXI a device that fails also clears its PASSed bit in its Status register A VMEbus signal that is used by a device to indicate a system reset or power up condition RAM installed on your personal computer and used by the operating system as contrasted with onboard RAM which is installed on the PCI MXI 2 or VXI VME MXI 2 G 8 ni com T trigger TTL U user window V V VDC VICtext VME VMEbus System Controller VXIbus VXiinit National Instruments Corporation G 9 Glossary Either TTL or ECL lines used for intermodule communication Transistor Transistor Logic A region of PCI address space reserve
85. fferent configuration please refer to the appropriate hardware or software chapters in this manual The manual flowchart at the beginning of this chapter directs you to where to find the information you need PCI MXI 2 This section summarizes the hardware and software default settings for the PCI MXI 2 Table 1 1 PCI MXI 2 Hardware Default Settings Hardware Component Default Setting U17 Switch 1 FOV OFF PCI MXI 2 boots off the user configured half of the EEPROM U17 Switch 2 TST OFF Factory configuration of the EEPROM is protected U17 Switch 3 POS OFF Do not alter this setting U17 Switch 4 CT ON Do not alter this setting DRAM SIMM Installed Per customer order National Instruments Corporation 1 9 PCI MXI 2 for Linux Chapter 1 Introduction and Quick Start PCI MXI 2 for Linux Table 1 2 PCI MXI 2 Logical Address Configuration Editor Default Settings Editor Field Default Setting Logical Address 0 Device Type MBD Address Space A16 VXI Shared RAM Size 0 KB Shared RAM Pool 0 KB Lower Half Window Byte Swapping Disabled non swapped Lower Half Window Memory Select System Memory Upper Half Window Byte Swapping Disabled non swapped Upper Half Window Memory Select System Memory Resource Manager Delay 5s Map Upper Lower Halves to Same Address Disabled ni com Chapter 1 Introduction and Quick Start Table 1
86. front panel features 4 3 MXlIbus termination 4 5 onboard DRAM 4 8 DRAM configurations table 4 9 SIMM size configuration figure 4 9 PCI MXI 2 for Linux Index parts locator diagram figure 4 2 VMEbus A16 base address 4 3 2 intermodule signaling 4 4 connecting MXlIbus cable 4 11 default settings Configuration Editor settings table 1 13 hardware description 1 4 installation 4 10 quick start installation 1 7 specifications electrical A 11 environmental A 10 MXIbus capability descriptions 8 performance A 11 physical A 10 requirements A 10 VMEbus capability codes A 8 VXI shared RAM options 6 6 advanced shared RAM settings 6 8 illustration 6 8 caution 6 10 enable byte swapping 6 9 lower half window and upper half window 6 7 memory select 6 9 shared RAM pool 6 7 VXI VME shared RAM size 6 7 window mapping 6 9 VXI VME automatic retry feature 6 25 VXI VME extender kit hardware description 1 4 introduction 1 1 MXI 2 description 1 3 overview 1 3 requirements for getting started 1 3 software description 1 5 VXI VME MXI Configuration Editor 16 write post and A24 A32 write post 6 21 PCI MXI 2 for Linux 1 8 address space and requested memory 6 20 and RESMAN 6 19 default settings table 1 13 illustration 6 20 interlocked mode 6 22 LA selection and logical address 6 20 MXI bus configuration options advanced MXI settings 6 28 illustr
87. ifications PCI MXI 2 A 2 VME MXI 2 module A 10 VXI MXI 2 module A 6 example code E 1 example programs 7 4 expansion ROM enabling 6 18 F fair requester MXI 6 29 VXI VME 6 26 files for NI VXI header files B 2 main programs and files B 1 frequently asked questions D 1 E 1 functions local resource access functions 7 3 low level access functions 7 3 system configuration functions 7 4 G GetDevInfo function 7 3 H handlers selecting number of 6 12 hardware See also PCI MXI 2 board VME MXI 2 module VXI MXI 2 module default settings table National Instruments Corporation I 3 Index PCI MXI 2 board 1 9 VME MXI 2 module 1 13 VXI MXI 2 module 1 12 description 1 4 quick start installation 1 6 settings table 1 13 header files B 2 help professional services E 1 technical support E 1 InitVXIlibrary function 7 4 installation electrostatic discharge caution 2 1 hardware installation 1 7 NI VXI NI VISA software for Linux 1 8 5 1 completing installation 5 3 procedure 5 1 removing 5 2 using 5 2 PCI MXI 2 board 2 3 VME MXI 2 module 4 10 connecting MXIbus cable 4 11 VXI MXI 2 module 3 18 connecting MXIbus cable 3 19 instrument drivers E 1 interlocked arbitration mode 6 22 intermodule signaling VME MXI 2 4 4 interrupt handlers selecting number of 6 12 interrupters selecting number of 6 13 IRQ level selecting 6 12 K KnowledgeBase E 1 PCI MXI 2 for
88. ilure to follow the National Instruments installation operation or maintenance instructions owner s modification of the product owner s abuse misuse or negligent acts and power failure or surges fire flood accident actions of third parties or other events outside reasonable control Copyright Under the copyright laws this publication may not be reproduced or transmitted in any form electronic or mechanical including photocopying recording storing in an information retrieval system or translating in whole or in part without the prior written consent of National Instruments Corporation Trademarks LabVIEW MITE MXI National Instruments NI ni com NI VISA and NI VXI are trademarks of National Instruments Corporation Product and company names mentioned herein are trademarks or trade names of their respective companies Patents For patents covering National Instruments products refer to the appropriate location Help Patents in your software the patents txt file on your CD or ni com patents WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS 1 NATIONAL INSTRUMENTS PRODUCTS ARE NOT DESIGNED WITH COMPONENTS AND TESTING FOR A LEVEL OF RELIABILITY SUITABLE FOR USE IN OR IN CONNECTION WITH SURGICAL IMPLANTS OR AS CRITICAL COMPONENTS IN ANY LIFE SUPPORT SYSTEMS WHOSE FAILURE TO PERFORM CAN REASONABLY BE EXPECTED TO CAUSE SIGNIFICANT INJURY TO A HUMAN 2 IN ANY APPLICATION INC
89. installing and configuring the National Instruments PCI MXI 2 kits for Linux The VXI MXI 2 kit includes a VXI MXI 2 module that plugs into a VXI mainframe and links your PCI based computer to the VXIbus The VME MXI 2 kit includes a VME MXI that plugs into a VME chassis and links your PCI based computer to the VMEbus Both kits include the PCI MXI 2 interface board which links your computer to the MXIbus and the NI VXI bus interface software The VXI MXI 2 and VME MXI 2 kits are fully VXIplug amp play compliant This manual uses the term PCI MXI 2 kit when information applies to either kit and the term VXI VME MXI 2 when information applies to either the VXI MXI 2 or the VME MXI 2 How To Use the Manual Set Getting Started Installation and Manual Configuration NY Online Online NI VXI Use Online NI VISA User Manual Utilities User Manual NI VXI and NI VISA NI VXI Function Help NI VISA Reference victext Reference National Instruments Corporation Xi PCI MXI 2 for Linux About This Manual Conventions bold PCI MXI 2 for Linux Begin by reading this getting started manual to guide you through the installation and configuration of the hardware and software You should install and configure the components of the PCI MXI 2 kit in the order in which this manual describes them Be sure to review the Quick Start and Defa
90. ions are the fundamental level of any PC or compatible computer BIOS functions embody the basic operations needed for successful use of the computer s hardware resources G 2 ni com block mode transfer BTO unit bus master CLK10 CMOS Commander configuration registers Glossary An uninterrupted transfer of data elements in which the master sources only the first address at the beginning of the cycle The slave is then responsible for incrementing the address on subsequent transfers so that the next element is transferred to or from the proper storage location In VME the data transfer may have no more than 256 elements MXI does not have this restriction Bus Timeout Unit a functional module that times the duration of each data transfer and terminates the cycle if the duration is excessive Without the termination capability of this module a bus master attempt to access a nonexistent slave could result in an indefinitely long wait for a slave response A device that is capable of requesting the Data Transfer Bus DTB for the purpose of accessing a slave device Celsius A 10 MHz 100 ppm individually buffered to each module slot differential ECL system clock that is sourced from Slot 0 of a VXIbus mainframe and distributed to Slots 1 through 12 on P2 It is distributed to each slot as a single source single destination signal with a matched delay of under 8 ns Complementary Metal Oxide Semiconductor a proc
91. ircuit different from that to which the receiver is connected Consult the dealer or an experienced radio TV technician for help Canadian Department of Communications This Class B digital apparatus meets all requirements of the Canadian Interference Causing Equipment Regulations Cet appareil num rique de la classe B respecte toutes les exigences du R glement sur le mat riel brouilleur du Canada Compliance to EU Directives Readers in the European Union EU must refer to the Manufacturer s Declaration of Conformity DoC for information pertaining to the CE Mark compliance scheme The Manufacturer includes a DoC for most every hardware product except for those bought for OEMs if also available from an original manufacturer that also markets in the EU or where compliance is not required as for electrically benign apparatus or cables To obtain the DoC for this product click Declaration of Conformity at ni com hardref nsf This Web site lists the DoCs by product family Select the appropriate product family followed by your product and a link to the DoC appears in Adobe Acrobat format Click the Acrobat icon to download or read the DoC Certain exemptions may apply in the USA see FCC Rules 815 103 Exempted devices and 15 105 c Also available in sections of CFR 47 The CE Mark Declaration of Conformity will contain important supplementary information and instructions for the user or installer Contents About This Man
92. is field determines whether to enable write posting for incoming slave accesses to A24 A32 VXI VME shared RAM By default this option is disabled the Enable A24 A32 Write Posting checkbox is cleared Enabling write posting will increase the throughput of your inward cycles However you should not enable write posting unless the destination of your inward A24 A32 cycles is onboard RAM because cycles to onboard RAM will always complete successfully PCI Bus The following sections describe the options for the PCI Bus portion of this editor User Window and Driver Window The PCI MXI 2 driver requires the use of two PCI windows a user window and a driver window Calling the MapvxIAddress function allocates regions of the user window to your application and VXIpoke accesses are performed through this window NI V XI uses the driver window to perform high level functions such as VXIin and VXIout and to access registers on the PCI MXI 2 and VXI VME MXI The windows are mapped to PCI base address registers and determine the amount of PCI memory space the PCI MXI 2 requests from the PCI system during initialization National Instruments Corporation 6 17 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Window Size The amount of space you can allocate for the user window is system dependent You can use the Size control to select the size of the user window minimum of 4 KB maximum of 2 GB
93. it should be the VXI VMEbus system controller The VXI VMEbus system controllers operate certain VXI VMEbus lines as required for VXI VME systems Verify that any other VXI VME devices with system controller capability that are located in the same chassis are not configured as system controller Having more than one device configured as system controller will damage the VXI VME system For VXI systems that include VME devices ensure that the VME devices are not configured in the upper 16 KB starting from 0xC000 of the A16 address space This region is reserved for VXI device configuration registers which are used for initializing configuring and interacting with VXI devices The PCI MXI 2 and 2 also use this region for this purpose Also ensure that no VXI devices in your system are configured for either logical addresses 0 or 1 These are the default configurations for the PCI MXI 2 and the VXI MXI 2 respectively For more information about the VXI MXI 2 or VME MXI 2 hardware refer to either Chapter 3 VXI MXI 2 Configuration and Installation or Chapter 4 VME MXI 2 Configuration and Installation National Instruments Corporation 1 7 PCI MXI 2 for Linux Chapter 1 Introduction and Quick Start Installing and Loading the NI VXI NI VISA Software for Linux VME Users Device Interaction PCI MXI 2 for Linux For information on installing uninstalling or using the NI VXI NI VISA software refer to Chapter 5 NI
94. iter Type You can use the Arbiter Type feature to configure the VXI VME MXI 2 as either a Priority or Round Robin VMEbus arbiter This control is applicable only if the VXI VME MXI 2 you are configuring is a VMEbus System Controller VXI Slot 0 device The default value is Priority When configured for Priority arbitration the VXI VME MXI 2 grants the bus to the highest pending bus request level In Round Robin arbitration mode the VXI VME MXI 2 grants the bus to the next highest bus request level after the level of the previous bus owner This effectively gives the same priority to each bus request level Refer to the VMEbus specification for more information on the different types of arbiters Request Level The VXI VME MXI 2 uses one of the four VMEbus request levels 0 to 3 to request use of the VME Data Transfer Bus DTB The VXI VME MXI requests use of the DTB whenever an external MXIbus device such as a PCI based computer with a PCI MXI 2 interface attempts a transfer that maps into the VXI VMEbus mainframe The VXI VME MXI 2 uses VMEbus request level 3 by default as required by the VXIbus specification This is suitable for most V XIbus systems However you can change the VXI VME MXI 2 to use any of the other three request levels 0 1 or 2 by changing the setting of the Request Level control You may want to change request levels to change the priority of the VXI VME MXI 2 request signal For more information refer to the
95. lave D32 D16 and 08 data sizes VMEbus master block and D64 transfers VMEbus slave block and D64 transfers VMEbus master read modify write transfers VMEbus slave read modify write transfers VMEbus master retry support VMEbus slave retry support First slot detector VMEbus System Controller Prioritized or Round Robin Select arbiter Release on Request and FAIR bus requester Interrupt handler for levels 7 1 Interrupt requester for levels 7 1 VMEbus D32 D16 D08 O interrupt handler VMEbus D32 D16 D08 O interrupter Release on Acknowledge or Register Access interrupter VMEbus bus timer programmable limit PCI MXI 2 for Linux Appendix A Requirements Environmental Physical PCI MXI 2 for Linux Specifications for VME MXI 2 16 5 A24 or A32 Temperature Operating Stora Se accuse ppt deed Relative humidity Noncondensing operating Noncondensing storage 16 KB minimum programmable to 55 C 40 to 85 C 0 to 95 0 to 95 FCC Class A verified VMEbus double height board 233 36 by 160 mm 9 187 by 6 2999 in Single fully implemented MXI 2 bus connector Single VMEbus double height slot Fully compatible with VMEbus specification Contact factory 0 33 kg 0 73 1b typical no DRAM installed ni com Appendix A Specifications for VME M
96. ld be the MXI Bus System Controller You must still be certain to cable the MXIbus system appropriately when you make either of these selections MXI Bus Timeout Value The MXI Bus Timeout BTO is a watchdog timer for transfers on the MXIbus The MXIbus BTO unit operates only when the VXI VME MXI2 is acting as the MXI Bus System Controller The functionality of this control is similar to that of the VXI Bus Timeout control described in the VXI VME Bus Options section The options range from 8 us to 128 ms with a default value of 1 ms After the specified amount of time has elapsed the BTO circuitry terminates a MXIbus cycle if no slave has responded The BTO circuitry is automatically deactivated when the VXI VME MXI 2 is not acting as the MXI Bus System Controller The BTO is also disabled when the current MXIbus cycle maps to the VXI VMEbus through a VXI VME MXI 2 National Instruments Corporation 6 27 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Advanced MXI Settings Click the Advanced button to reach additional configuration options for the MXI Bus portion of this editor as shown in Figure 6 10 These options are intended for more advanced users 3 Advanced MXI Settings LX These settings control the operation of the MXI 2 bus Exercise caution when changing these options M Bus Protocols Transfer Limit Unlimited Y Enable Parity Checking Operate as Fair Requester Mm MXI
97. le Auto ace C Yes always be the system controller V Bus Timeout No never be the system controller Enable A16 Write Posting Enable 424 432 Write Posting Enable Interlocked Mode MX Bus Timeout M Shared Memory MX Bus Address Space A24 System Controller Auto SS Yes always be the system controller Requested Memory 16 KB m No never be the system controller im o Cancel Default Figure 6 8 VXI VME MXI 2 Configuration Editor LA Selection and Logical Address You can set or modify the logical address of the VXI VME MXI 2 either within the VXI VME MXI 2 Configuration Editor itself or with the onboard 8 position DIP switch To select the configuration method you prefer use the LA Selection controls The default selection is the Switch option Notice that the Logical Address control is inaccessible because it would have no effect In this option you need to change the hardware switch setting on the VXI VME MXI 2 itself if you want to change the logical address If you select Software for this option you can then use the Logical Address control to select a logical address within the range of 1 to 254 If you use this option the hardware switch setting has no effect and you must use the VXI VME MXI 2 Configuration Editor to change the logical address Address Space and Requested Memory PCI MXI 2 for Linux The VXI VME MXI requires at
98. least 16 KB of address space in A24 space or at least 64 KB in A32 space Use the Address Space control to select whether you want to use A24 space or A32 space Use the ni com Chapter 6 NI VXI Configuration Utility Requested Memory control to set the amount of memory space that the VXI VME MXI 2 will request You can select up to 8 MB in A24 space and up to 2 GB in A32 space The default setting uses the minimum requirement of 16 KB in A24 space These controls are necessary if you change the amount of DRAM installed on the VXI VME MXI 2 The amount of memory you set with the Requested Memory control should match the amount of DRAM installed on the VXI VME MXI 2 If no DRAM is installed keep the default setting of 16 KB Notice that the smallest valid amount in A32 space is 64 KB N Caution If you install DRAM into the VXI VME MXI 2 do not attempt to use the first 4 KB of memory space This 4 KB space maps to the registers on the VXI VME MXI 2 and does not access onboard DRAM Accessing this region will cause your VXI VME MXI 2 to behave incorrectly If you do not want to lose 4 KB of DRAM you can get around this limitation by setting the Requested Memory control to double the amount that is installed on the VXI VME MXI 2 because the DRAM is aliased throughout the remainder of the requested memory space The DRAM should then be accessed in the upper half of the requested memory space A16 and A24 A32 Write Posting The VXI VME MXI 2
99. lems and solutions D 1 professional services E 1 programming considerations See NI VXI NI VISA software programming examples E 1 protocol register contents specifying 6 13 Q questions about NI VXI NI VISA software D 1 quick start configuration 1 6 default settings 1 9 device interactions 1 8 hardware installation 1 7 VME users 1 8 R read protocol response 6 13 removing NI VXI driver for Linux 5 2 PCI MXI 2 for Linux 1 6 request level for Data Transfer Bus setting 6 26 Requested Memory control 6 21 requester See fair requester resman utility fixing system hangups D 4 overview B 1 performing startup Resource Manager operations D 2 testing your system D 2 VME device configuration 1 8 resource manager delay setting 6 10 rugged cables D 3 S servant area size setting 6 12 Slot 0 non Slot 0 configuration 3 5 software drivers E 1 software NI VXI See NI VXI NI VISA software software optional 1 6 specifications PCI MXI 2 electrical A 3 environmental A 2 MXIbus capability descriptions A 1 PCI functionality A 2 performance A 3 physical A 3 requirements 2 VME MXI 2 electrical A 11 environmental A 10 MXIbus capability descriptions 8 performance A 11 physical A 10 requirements A 10 VMEbus capability codes 8 ni com VXI MXI 2 electrical A 7 environmental A 6 MXIbus capability descriptions 4 performance A 7 physical A 6 requirements A 6 V
100. ll SIMMs installed must be of the same type Use Bank 0 first when installing SIMMs This allows you to install up to 64 MB The VME MXI 2 supports DRAM speeds of 80 ns or faster 4 8 ni com VME MXI 2 Configuration and Installation Switch S2 is used to select the size of each SIMM If the SIMMs are 4 M x 32 or larger S2 should be in the OFF setting as shown in Figure 4 6a For SIMMs smaller than 4 M x 32 use the ON setting as shown in Figure 4 6b 52 4 32 and Larger 52 b Smaller than 4 M x 32 Figure 4 6 SIMM Size Configuration Refer to Table 4 1 for how to adjust the switch ON or OFF for all supported DRAM configurations Many of the DRAM options are available from National Instruments Table 4 1 VME MXI 2 DRAM Configurations National Instruments Switch Setting Bank 0 Bank 1 Total DRAM Option of S6 E 0 _ 256 K x 32 or 1 MB ON 256 K x 36 256 K x 32 or 256 K x 32 or 2MB ON 256 K x 36 256 K x 36 512K x 32 or 2MB ON 512 K x 36 512K x 32 512 K x 32 or 4 ON 512 K x 36 512K x36 1M 32 4MB YES ON 1Mx36 1 320 1 320 8 ON 1M x 36 1M x 36 2M x 32 or 8 MB YES ON 2M x 36 National Instruments Corporation 4 9 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation Table 4 1 VME MXI 2 DRAM Configurations Continued National Instrume
101. ll it into Slot 0 To install the VXI MXI 2 refer to the Install the VXI MXI 2 section Figure 3 1 shows the VXI MXI 2 as it would appear when facing the right side cover The drawing shows the location and factory default settings of most of the configuration switches and jumpers on the module Notice that switch S6 is accessible only by removing the front cover National Instruments Corporation 3 1 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation 93 o ioisuoN M VXI MXI 2 INSTRUMENTS NATIONAL H E s A 5 H 3 Fi TEE ds 22 ig i iz E snap uos oro oneooy 5 8 oe saxi ine ono enia Fe g a 55 cmm lt 5 m 85 3 mm 28 i2 Ej SE 3 mm 52 gf 632 m Push up for logic 1 Push down for logic 0 Turnoff power to instruments and cables before installing or removing any modules WARNING LII ILI X oes si es ueuw enpoejia indino BWS ss NL si cs uou OITO BWS 0 S u es jeu euep yuu P zs Toyo or Lt 1 035 2 W2 7 U43 9 S5 11 S3 8 S6 10 S4 12 S2 PCI MXI 2 for Linux
102. lled on your system it may or may not be present The README file contains the latest updates and corrections to the manual when appropriate B 1 PCI MXI 2 for Linux Appendix B NI VXI NI VISA Software Overview Header Files for NI VXI The NIVXI include directory where NIVXIis the actual location where you installed the NI VXI software package contains the following include files for the C language interface e nivxi his the main header file containing the C prototypes for the NI VXI functions datasize h contains data size specifications busacc h contains parameter and return values for the bus access functions e devinfo h contains parameter and return values for the device information and system configuration functions e vxiint h contains parameter and return values for the interrupt and signal functions sysint h contains parameter and return values for the system interrupt functions trig hcontains parameter and return values for the trigger functions This file is useful in VXI systems but is not applicable for VME systems ws hcontains parameter and return values for the Commander and Servant Word Serial functions This file is useful in VXI systems but is not applicable for VME systems Header Files for NI VISA The VXIpnp linux include directory where VXIpnp is the actual location where you installed the NI VISA software package contains the following include files for the C language
103. n 6 13 Read Protocol Response seen 6 13 Bus Configuration Editor seen emen 6 14 MXI Bis ur AGI BUR EAM RDUM SI 6 14 MXI System Controller eene 6 14 MXI Bus Timeout eee essere eene 6 15 MX CEK1O i e classed tete edendis 6 15 Transfer Lait ete teeth 6 16 Synchronous M XL ee eni erts 6 16 MXI 2 Auto Retry ne e e deed 6 16 A24 A32 Write Posting 6 17 Bus eo een FUR EH YR 6 17 User Window and Driver Window ees 6 17 Expansion ROM 4 eset eta e tete eee tee 6 18 VXI VME MXI 2 Configuration Editor 6 19 LA Selection and Logical 6 20 Address Space and Requested Memory see 6 20 A16 and A24 A32 Write Posting sese 6 21 Interlocked Mode 2 ne ete egere trees ten 6 22 VXI VMEB Bus Options nitentem tette titer RE Y Hp eden 6 23 VMEbus System Controller eene 6 23 VXI VME Bus Timeout Value eere 6 24 Advanced V XI S ttings uttter eget 6 24 VXI VME Auto Retry cecer 6 25 Transfer Lt uec det ete 6 25 Arbiter Types 2a gn e ete Rn Hd 6 26 Request Level uisi teet 6 26 VXI VME Fair Requester eseeeeeeeeeee 6 26 Arbiter Timeout eitge ene the 6 27 MXT Bus Options
104. nlimited period of time The other options you can choose from are 16 64 and 256 transfers If you do not want the VXI VME MXI 2 to hold the MXIbus for an unlimited period of time you can use this control to select one of these values Parity Checking By default MXIbus parity checking is enabled and should not be disabled under normal circumstances MXIbus parity is always generated regardless if checking is enabled or disabled MXI Fair Requester You can use the Operate as Fair Requester checkbox control to configure the VXI VME MXI 2 as either a fair or unfair requester on the MXIbus In its default setting disabled the VXI VME MXI 2 will request the bus at any time If you enable this option the VXI VME MXI 2 will request the MXIbus only when there are no requests pending from other MXIbus masters This prevents other MXIbus masters from being starved of bandwidth MXI CLK10 Signal The VXI MXI 2 can either receive or drive the MXIbus CLK10 signal In its default setting the VXI MXI 2 uses the switch setting of S7 to determine the signal direction VME users This option is not applicable to the VME MXI 2 You can use the Drive or Receive options to override the setting of S7 and control the direction of the MXIbus CLK10 signal When receiving the MXlIbus 10 signal configure the W3 jumper setting to use the MXIbus as the source for generating the VXIbus CLK10 applicable only if the VXI MXI 2 is a Slot 0 devic
105. ntain information that you may find helpful as you read this manual e ANSI IEEE Standard 1014 1987 IEEE Standard for a Versatile Backplane Bus VMEbus e ANSI IEEE Standard 1155 1993 IEEE VMEbus Extensions for Instrumentation VXIbus e ANSI VITA 1 1994 VME64 e Multisystem Extension Interface Bus Specification Version 2 0 National Instruments Corporation e PCI Local Bus Specification Revision 2 0 PCI Special Interest Group e VXI MXI 2 User Manual National Instruments Corporation e VME MXI 2 User Manual National Instruments Corporation e VXI 6 VXIbus Mainframe Extender Specification Rev 2 0 VXIbus Consortium National Instruments Corporation PCI MXI 2 for Linux Introduction and Quick Start This chapter describes the PCI MXI 2 kits lists what you need to get started introduces the concepts of MXI 2 and includes a brief description of the hardware and software This chapter also contains a Quick Start section which has the basic information you need to install the PCI MXI 2 kit with a simple configuration and a Default Settings section which lists the hardware and software default settings for easy reference You may find that these sections contain as much information as you need to get started with your PCI MXI 2 kit This manual uses the term PCI MXI 2 kit when information applies to either the VXI 2 kit which contains a VXI MXI 2 module or the VME 2 kit which contains a
106. nterference to radio communications Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense Canadian Department of Communications This Class A digital apparatus meets all requirements of the Canadian Interference Causing Equipment Regulations Cet appareil num rique de la classe A respecte toutes les exigences du R glement sur le mat riel brouilleur du Canada Class B Federal Communications Commission This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to part 15 of the FCC Rules These limits are designed to provide reasonable protection against harmful interference in a residential installation This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the instructions may cause harmful interference to radio communications However there is no guarantee that interference will not occur in a particular installation If this equipment does cause harmful interference to radio or television reception which can be determined by turning the equipment off and on the user is encouraged to try to correct the interference by one or more of the following measures Reorient or relocate the receiving antenna Increase the separation between the equipment and receiver Connect the equipment into an outlet on a c
107. nts Switch Setting Bank 0 Bank 1 Total DRAM Option of S6 2M x 32 or 2M x 32 16 MB ON 2M x 36 2M x 36 4M x 32 or 16 MB YES OFF 4M x 36 4M x 32 or 4M x 32 or 32 MB OFF 4M x 36 4M x 36 8M x 32 or 32 MB YES OFF 8M x36 8M x 32 or 8 M x 32 or 64 MB YES OFF 8M x 36 8M x 36 Install the VME MXI 2 This section contains general installation instructions for the VME MXI 2 Consult your VMEbus mainframe user manual or technical reference manual for specific instructions and warnings Plugin your mainframe before installing the VME MXI 2 The power cord grounds the mainframe and protects it from electrical damage while you are installing the module JN Caution To protect both yourself and the mainframe from electrical hazards the mainframe should remain off until you are finished installing the VME MXI 2 module 2 Remove or open any doors or covers blocking access to the mainframe slots 3 Insertthe VME MXI 2 in the slot you have selected by aligning the top and bottom of the board with the card edge guides inside the mainframe Slowly push the VME MXI 2 straight into the slot until its plug connectors are resting on the backplane receptacle connectors Using slow evenly distributed pressure press the VME MXI 2 straight in until it seats in the expansion slot The front panel of the VME MXI 2 should be even with the front panel of mainframe 4 Tighten the retaining screws on the top an
108. o terminate the MXIbus when automatic termination is turned off National Instruments Corporation 4 5 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation Switch 4 has no effect when switch 3 is set for automatic MXIbus termination you must turn off automatic termination if you want to manually control termination TIT a Automatic MXIbus Termination Default ANG b Terminate MXIbus On DAA VIN T U21 U21 OFF c Do Not Terminate MXIbus Off Figure 4 4 MXIbus Termination Configuration EEPROM PCI MXI 2 for Linux The VME MXI 2 has an onboard EEPROM which stores default register values that are loaded at power on The EEPROM is divided into two halves a factory configuration half and a user configuration half Both halves were factory configured with the same configuration values so you can modify the user configurable half while the factory configured half stores a back up of the default user settings Use switches 1 and 2 of the four position switch at location U21 to control the operation of the EEPROM The Restore Factory Configuration switch switch 1 causes the VME MXI 2 to boot off the factory configured half instead of the user modified settings This is useful in the event that the 4 6 ni com Chapter 4 VME MXI 2 Configuration and Installation user configured half of the EEPROM becomes corrupted in such a way that the VME M
109. of 0 and the up position corresponds to a logic value of 1 Verify that the VXI MXI 2 does not have the same logical address as any other statically configured V XIbus device in your system Remember that logical addresses hex 0 and FF are not allowed for the VXI MXI 2 Also when setting logical addresses keep in mind the grouping requirements set by the system hierarchy Refer to VXI 6 VXIbus Mainframe Extender Specification for more information about setting logical addresses on a multimainframe hierarchy 3 4 ni com Chapter 3 VXI MXI 2 Configuration and Installation Figure 3 2 shows switch settings for logical address hex 1 and CO Push up for logic 1 LOGICAL ADDRESS SWITCH Shown at default setting of Logical Address 1 Push down for logic 0 Push up for logic 1 Push down for logic 0 a Switch Set to Logical Address 1 Default LOGICAL ADDRESS 12345678 U43 SWITCH b Switch Set to Logical Address Hex CO 12345678 U43 Figure 3 2 Logical Address Selection VXIbus Slot 0 Non Slot 0 The VXI MXI 2 is configured at the factory to automatically detect if it is installed in Slot 0 of a VXIbus mainframe With automatic Slot 0 detection you can install the VXI MXI 2 into any V XIbus slot AN You can manually configure the VXI MXI 2 for either Slot 0 or Non Slot 0 oper
110. oller by setting the MXI System Controller field to yes in vxitedit D 4 ni com Technical Support and Professional Services Visit the following sections of the National Instruments Web site at ni com for technical support and professional services e Support Online technical support resources include the following Self Help Resources For immediate answers and solutions visit our extensive library of technical support resources available in English Japanese and Spanish at ni com support These resources are available for most products at no cost to registered users and include software drivers and updates a KnowledgeBase product manuals step by step troubleshooting wizards hardware schematics and conformity documentation example code tutorials and application notes instrument drivers discussion forums a measurement glossary and so on Assisted Support Options Contact NI engineers and other measurement and automation professionals by visiting ni com ask Our online system helps you define your question and connects you to the experts by phone discussion forum or email e Training Visitni com custed for self paced tutorials videos and interactive CDs You also can register for instructor led hands on courses at locations around the world e System Integration lf you have time constraints limited in house technical resources or other project challenges NI Alliance Program members can help To learn
111. on half so you can modify the user configurable half while the factory configured half stores a back up of the default user settings The factory configuration is a minimal configuration that allows you to boot your PCI MXI 2 regardless of the changes made to the user configuration For information on configuring the onboard EEPROM refer to Appendix C EEPROM Configuration Install the PCI MXI 2 This section contains general installation instructions for the PCI MXI 2 Consult your computer user manual or technical reference manual for specific instructions and warnings 1 Plugin your PCI based computer before installing the PCI MXI 2 The power cord grounds the computer and protects it from electrical damage while you are installing the module UN Caution protect both yourself and the computer from electrical hazards the computer should remain off until you are finished installing the PCI MXI 2 module 2 Remove the top cover or access port to the PCI bus Select any available PCI expansion slot 4 Touch the metal part of the power supply case inside the computer to discharge any static electricity that might be on your clothes or body 5 Lineup the PCI MXI 2 with the MXI 2 connector near the cut out on the back panel Slowly push down on the top of the PCI MXI 2 until its card edge connector is resting on the expansion slot receptacle Using slow evenly distributed pressure press the PCI MXI 2 straight down until it
112. otocol to communicate with one another through communication registers A National Instruments custom ASIC a sophisticated dual channel DMA controller that incorporates the Synchronous MXI and VME64 protocols to achieve high performance block transfer rates Module Identification lines Mean Time Between Failure The second generation of the National Instruments MXIbus product line MXI 2 expands the number of signals on a standard MXIbus cable by including VXI triggers all VXI interrupts CLK10 SYSFAIL SYSRESET and ACFAIL G 6 ni com MXlIbus MXlIbus System Controller NI VXI Non Slot 0 device 0 Onboard RAM PCI propagation R register based device Resman Resource Manager National Instruments Corporation G 7 Glossary Multisystem eXtension Interface Bus a high performance communication link that interconnects devices using round flexible cables A functional module that has arbiter daisy chain driver and MXIbus cycle timeout responsibility Always the first device in the MXIbus daisy chain The National Instruments bus interface software for VME V XIbus systems A device configured for installation in any slot in a VXIbus mainframe other than Slot 0 Installing such a device into Slot 0 can damage the device the VXIbus backplane or both The optional RAM installed into the SIMM slots of the PCI MXI 2 board or VXI VME MXI 2 module Peripheral Component Interconnect The PCI bus i
113. oup to control features of the VXI VMEbus interface on the VXI VME MXI 2 VMEhus System Controller You can use the System Controller control to override the jumper setting on the VXI MXI 2 The VME MXI 2 does not have an onboard jumper setting for this option When the Auto setting the default setting is active the onboard jumper setting determines if the VXI MXI 2 is the VXI Slot 0 device For more information refer to the VXIbus Slot 0 Non Slot 0 section of Chapter 3 VXI MXI 2 Configuration and Installation Otherwise choose either the Yes or No option Notice that selecting either of these options overrides the onboard jumper setting on the VXI MXI 2 so it will not matter how the jumper is set You would need to run the VXI VME MXI 2 Configuration Editor again if you decide to change the VMEbus System Controller VXI Slot 0 setting at a later time National Instruments Corporation 6 23 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility AN Caution Do not install a VXI VME MXI 2 configured for VMEbus System Controller VXI Slot 0 into another slot without first reconfiguring it to either Non Slot 0 or automatic configuration Neglecting to do this could damage the VXI VME MXI 2 the VXI VMEbus backplane or both This means that you should use either the No option or the Auto option of this control For the VXI MXI 2 you also have the option of changing the hardware jumper setting PCI MXI 2 for Linux VXI VME Bus
114. peek VXIpoke Your application should always call the viUnmapAddress or UnMapVXIAddress function immediately after the accesses are complete so that you free up the memory window for other applications The functions viMapAddress and MapVXIAddress return a pointer for use with low level access functions It is strongly recommended that you use the functions to access the memory instead of directly dereferencing the pointer Using these functions makes the NI VXI VISA software more portable between platforms Refer to the Compiling Your C Program for NI VXI NI VISA section for more information on portability issues and to your NI VXI or NI VISA software reference manual for more information on low level VXIbus or VMEbus access functions Local Resource Access Functions By using vxiedit you can set up the PCI MXI 2 to share either the system memory on the motherboard or the onboard memory on the PCI MXI 2 with the VXI VME system Refer to the NI VXI Graphical Utilities Reference Manual for more information on setting these parameters Notice that sharing the system memory with the VXI VME system does not mean that the entire range of shared system memory is available to be used for VXI VME transfers You need to be cautious in specifying the portion of memory you want to share as some areas are already used for other purposes UN Caution Use viMemAlloc or VXImemAlloc to allocate a buffer in the system memory that is re
115. pplication that does not disable SYNC MXI programmatically you can deselect the checkbox to force your application to not use SYNC MXI if necessary MXI 2 Auto Retry The PCI MXI 2 has an automatic retry feature for cycles that map from the MXI bus to the PCI bus By default this option is enabled the Enable MXI 2 Auto Retry checkbox is checked Normally when a cycle maps from the MXI bus to the PCI bus any retry response received on the PCI bus is passed to the MXI bus When the MXI 2 auto retry feature is enabled the PCI MXI 2 automatically retries any PCIcycle when the PCI host responds to a cycle with a retry The PCI MXI 2 automatically continues to retry the PCI cycle until it receives either a DTACK or BERR response which it then passes to the MXI bus This is the default situation because many external masters do not support VXI MXI retries If the external master does support retries it may be 6 16 ni com Chapter 6 NI VXI Configuration Utility beneficial to disable the MXI 2 auto retry feature With this feature disabled you can lower the MXI Bus Timeout because there will be no delay due to the inward cycles being retried 5 Note The PCI MXI 2 has a limit on the number of automatic retries they will perform on any one cycle If the limit is exceeded and the PCI MXI 2 receives another retry it will pass a retry back to the MXIbus even though the Enable MXI 2 Auto Retry checkbox is checked A24 A32 Write Posting Th
116. r Specification for more information on setting base addresses on a multimainframe hierarchy National Instruments Corporation 4 3 PCI MXI 2 for Linux Chapter 4 VME MXI 2 Configuration and Installation Figure 4 2 shows switch settings for A16 base address hex C040 and F000 U20 3 a Switch Set to A16 Base Address Hex C040 Default b Switch Set to A16 Base Address F000 Figure 4 2 Base Address Selection VME MXI 2 Intermodule Signaling PCI MXI 2 for Linux If you will be installing more than one VME MXI 2 in a single VMEbus chassis you must select a user defined pin for use by the VME MXI 2 The VME MXI 2 modules use this signal to disable the bus timeout unit s on the other VME MXI 2 modules during VMEbus accesses that map to the MxXiIbus This is done because the MXIbus bus timeout unit should be the sole timer of any MXIbus access Since bus timeout units on other VMEbus modules cannot monitor this signal they should be permanently disabled If it is not possible to disable a module s bus timeout unit it should be configured to the highest setting to give MXIbus accesses as much time as possible You can choose from three user defined pins on J2 P2 The pin you select must be bused on the VMEbus backplane between all slots that will have a VME MXI 2 installed Use jumper W2 to select pin A5 C5 or C30 of J2 P2 as shown in Figure 4 3 Notice that a fourth po
117. r called the logical address defines the base address for the V XI configuration registers located on the device With unique logical addresses each VXIbus device in the system is assigned 64 bytes of configuration space in the upper 16 KB of A16 space National Instruments Corporation 3 3 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation PCI MXI 2 for Linux Logical address 0 is reserved for the Resource Manager in the VXIbus system Because the VXI MXI 2 cannot act as a Resource Manager do not configure the VXI MXI 2 with a logical address of 0 Some VXIbus devices have dynamically configurable logical addresses These devices have an initial logical address of hex FF or 255 which indicates that they can be dynamically configured While the VXI MXI 2 does support dynamic configuration of VXI devices within its mainframe it is itself a statically configured device and is preset at the factory with a VXI logical address of 1 Ensure that no other statically configurable V XIbus devices have a logical address of 1 If they do change the logical address setting of either the VXI MXI 2 or the other device so that every device in the system has a unique associated logical address You can change the logical address of the VXI MXI 2 by changing the setting of the 8 bit DIP switch labeled LOGICAL ADDRESS SWITCH location designator U43 on the panel The down position of the DIP switch corresponds to a logic value
118. running the VXI VME MXI 2 Configuration Editor you must run Resman hy Note Throughout this section the term VXI VME MXI 2 denotes that the information applies to both the VXI MXI 2 and the VME MXI 2 Upon entering the VXI VME MXI 2 Configuration Editor the program displays a list of VXI VME MXI 2 boards that Resman detected in your system as shown in Figure 6 7 Select XI ME MXI 2 Ea LA 1 Frame 1 Slot 0 Figure 6 7 VXI AVME MXI 2 Selection Dialog Box Select the device you want to configure from the Detected Boards pull down list or you can select User LA and type in the board s logical address in the Logical Address field Click OK to enter the editor or Cancel to return to the main menu After finding a VXI VME MXI 2 the VXI VME MXI 2 Configuration Editor displays a panel as shown in Figure 6 8 that you can use to modify its configuration settings The panel displays the current settings of the module Notice that it also shows the hardware revision and serial number of the VXI VME MXI The title of the screen will reflect the model of the device you have For instance if you have a 2 the title will read VXI MXI 2 Configuration Editor as shown in Figure 6 8 National Instruments Corporation 6 19 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility 3 VXI MXI 2 Configuration E ditor Serial Number 708 ore Bus Hardware Revision B System Control
119. s 0 18 kg 0 4 Ib typical no DRAM installed Electrical 5 VDC Typical ner 22 Direct Current 3 5 Performance Peak use ROBES 33 MB s Sustained eee 23 MB s National Instruments Corporation 3 PCI MXI 2 for Linux Appendix A Specifications for VXI MXI 2 VXI MXI 2 The following sections list the specifications for the VXI MXI 2 module MXIbus Capability Descriptions e Master mode A32 A24 and A16 addressing e Master mode block transfers and synchronous block transfers e Slave mode A32 24 and A16 addressing Slave mode block transfers and synchronous block transfers e Master mode D32 D16 and DO8 data sizes e Slave mode 032 D16 and DOS data sizes e Optional MXIbus System Controller e Can be a fair MXIbus requester e Can lock the MXIbus for indivisible transfers e Can terminate the MXIbus e MXlIbus master retry support e MXlIbus slave retry support e Interrupt handler for levels 7 to 1 e Interrupt requester for levels 7 to 1 e MXIbus D32 D16 D08 O interrupt handler e MXIbus D32 D16 D08 O interrupter e Release on Acknowledge or Register Access interrupter e MXlIbus bus timer programmable limit e Automatic MXIbus System Controller detection Automatic MXIbus termination detection VMEbus Capability Codes PCI MXI 2 for Linux A32 24 A16 master VMEbus master A32 A24 and 16 addressing A32 24
120. s Corporation 6 1 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility Figure 6 1 shows the main menu of the vxiedit resource editor PCI MXI 2 for Linux VXI Resource Editor e NATIONAL INSTRUMENTS Copyright 1996 RII Rights Reserved j VXLAVME MXI 2 Configuration E ditor B i Manufacturer Name Config E ditor i Model Name Configuration E ditor f i Device Name Configuration Editor E i Non VXl Device Configuration Editor i Interrupt Configuration E ditor H i Trigger Configuration E ditor Utility Bus Configuration E ditor ua Figure 6 1 VXledit Main Screen The rest of this chapter describes only the features of the PCI MXI 2 Configuration Editor and the VXI VME MXI 2 Configuration Editor For instructions on using the other editors refer to your software utility reference manual either the NI VXI Graphical Utilities Reference Manual or the NI VXI Text Utilities Reference Manual 6 2 ni com Chapter 6 NI VXI Configuration Utility PCI MXI 2 Configuration Editor Figure 6 2 shows the opening screen of the PCI MXI 2 Configuration Editor Notice that the screen displays the serial number and hardware revision of the PCI MXI 2 board in addition to several configuration options PCI MXI 2 Configuration E ditor Serial Number 9858 Revision B f Log nfiquration E ditor i Device Configuration E ditor i Bus Configuration Editor i Update Current
121. s a high performance 32 bit or 64 bit bus with multiplexed address and data lines The transmission of signal through a computer system A Servant only device that supports VXIbus configuration registers Register based devices are typically controlled by message based devices via device dependent register reads and writes The name of the National Instruments Resource Manager in NI VXI bus interface software See Resource Manager A message based Commander located at Logical Address 0 which provides configuration management services such as address map configuration Commander and Servant mappings and self test and diagnostic management PCI MXI 2 for Linux Glossary retry RPM S S Servant Shared Memory Protocol SIMM slave slave mode operation Slot 0 device statically configured device SYSFAIL SYSRESET System RAM PCI MXI 2 for Linux An acknowledge by a destination that signifies that the cycle did not complete and should be repeated RPM Package Manager a widely used software distribution tool that you can use to install upgrade or remove software from your system Seconds A device controlled by a Commander there are message based and register based Servants A communication protocol that uses a block of memory that is accessible to both a client and a server The memory block operates as a message buffer for communications Single In line Memory Module A functional part o
122. s device to drive MXIbus CLK10 Having a second device driving MXIbus CLK10 could damage the device National Instruments Corporation 6 15 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility PCI MXI 2 for Linux MXI Transfer Limit Use this feature to control how many data transfers the PCI MXI 2 will perform on the MXIbus before releasing it to another master device that is requesting use of the bus The default setting holds the MXIbus for an unlimited period of time The other options you can choose from are 256 64 and 16 transfers If you do not want the PCI MXI 2 to hold the MXIbus for an unlimited period of time you can use this control to select one of these values Synchronous MXI The MXIbus has a special high speed block protocol for transferring large blocks of data This protocol SYNC MXI locks the MXIbus during the transfer which prevents anyone else from using the bus vxImove uses this protocol to transfer data If a VXI interrupt or signal comes in while a synchronous MXI move is underway there can be a problem Using the SYNC MXI protocol will prohibit access to the MXI bus which will prevent you from responding to an interrupt and prevent bus monitoring devices from accessing the bus at regular intervals By default this option is enabled the VXImove uses Synchronous MXI checkbox is checked You can also disable S YNC MXI programmatically in VXImove However if you have an older NI VXI a
123. s of the setting of switch 4 of U35 National Instruments Corporation 3 15 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation PCI MXI 2 for Linux Figure 3 10 shows the configuration settings for EEPROM operation The settings of switches 1 and 2 have no effect on EEPROM configuration Restore Factory Configuration No Change Factory Configuration No Automatic MXIbus Termination Yes Terminate Yes U35 Restore Factory Configuration No Yes Change Factory Configuration No WIN n Yes Automatic MXIbus Termination Yes 222 No Terminate MXIbus Yes Z b Boot from Factory Configuration Factory Configuration Protected Restore Factory Configuration No Change Factory Configuration No Automatic MXIbus Termination Yes Terminate MXIbus Yes c Boot from User Configuration Factory Configuration Unprotected U35 Restore Factory Configuration No Yes Change Factory Configuration No Yes Automatic MXIbus Termination 2222 lt Terminate MXIbus Yes EZA No d Boot from Factory Configuration Factory Configuration Unprotected Figure 3 10 EEPROM Operation 3 16 ni com Onboard DRAM Chapter 3 VXI MXI 2 Configuration and Installation The VXI MXI 2 can accommodate up to
124. seats in the expansion slot 6 Check the installation Ensure that the PCI MXI 2 is secure in its slot 7 Replace the computer cover National Instruments Corporation 2 3 PCI MXI 2 for Linux Chapter 2 PCI MXI 2 Configuration and Installation Figure 2 2 shows how to install the PCI MXI 2 1 PCI Bus Slot 4 MXI 2 Connector 2 Cutouts 5 PCI MXI 2 Board 3 PCI Bus Card Edge Connector Figure 2 2 PCI MXI 2 Installed in a Computer PCI MXI 2 for Linux 2 4 ni com VXI MXI 2 Configuration and Installation This chapter contains the instructions to configure and install the VXI MXI 2 module This chapter applies only if you ordered the VXI MXI 2 kit If you ordered the VME MXI 2 kit skip this chapter and refer to Chapter 4 VME MXI 2 Configuration and Installation Caution Electrostatic discharge can damage several components on your VXI MXI 2 module To avoid such damage in handling the module touch the antistatic plastic package to a metal part of your VXI chassis before removing the VXI MXI 2 from the package Configure the VXI MXI 2 This section describes how to configure the following options on the VXI MXI 2 VXIbus logical address VXIbus Slot 0 Non Slot 0 VXIbus local bus VXIbus CLK10 routing Trigger input termination MXlIbus termination Configuration EEPROM Onboard DRAM hy Note If you have only one VXI chassis in your system you should leave the VXI MXI 2 at Logical Address 1 and insta
125. served for your use only Using any range of addresses that was not returned from viMemAlloc or VXImemAlloc to receive data may cause your computer to crash or behave incorrectly The onboard memory on your PCI MXI 2 on the other hand is entirely available to you You can obtain the VXI address of your onboard memory using the Get DevInfo function When you have the VXI VME address you can access that memory using high level or low level VXI VMEbus access functions National Instruments Corporation 7 3 PCI MXI 2 for Linux Chapter 7 Using the NI VXI NI VISA Software System Configuration Functions The System Configuration functions provide the lowest level initialization of your VXI controller For NI VXI use the InitVXIlibrary function at the start of each application and the 1 1 function at the end of each application For NI VISA use viOpenDefaultRM at the start of each application and the viClose function at the end of each application Compiling Your C Program for NI VXI NI VISA Symbols PCI MXI 2 for Linux You can use the sample programs included with the NI VXI software as a starting point to develop your own C program that uses NI VXI functions First look over and compile the sample programs using the makefile provided to get familiar with how the functions operate The example programs are broken into multiple files and each one shows how to use different groups of f
126. sition is also available on the jumper This is the factory default setting which does not connect the VME MXI 2 to any user defined pin You would use this option only if you are installing a single VME MXI 2 in a chassis 4 4 ni com Chapter 4 VME MXI 2 Configuration and Installation Figure 4 3 shows the four intermodule signaling settings W2 Wwe A5 5 C5 C5 C30 C30 NC NC a User Defined Pin A5 Selected b User Defined Pin C5 Selected w2 we A5 A5 C5 C5 C30 C30 NC NC c User Defined Pin C30 Selected d No User Defined Pin Selected Default Figure 4 3 VME MXI 2 Intermodule Signaling Settings MXIbus Termination The first and last MXIbus devices connected to the MXIbus whether it is a single MXI 2 cable or daisy chained MXI 2 cables must terminate the MXIbus Any MXIbus devices in the middle of a MXIbus daisy chain must not terminate the MXIbus The VME MXI 2 automatically senses if it is at either end of the MXIbus cable to terminate the MXIbus You can manually control MXIbus termination by defeating the automatic circuitry Use switches 3 and 4 of the four position switch at location U21 to control whether MXIbus termination is automatic Figure 4 4a on Figure 4 4b or off Figure 4 4c The settings of switches 1 and 2 have no effect on MXIbus termination Use switch 3 to select whether you want the VME MXI 2 to automatically control termination of the MXIbus Switch 4 lets you manually control whether t
127. slave capability Data pathz i ates Card voltage type sss Parity generation checking error reporting Target decode speed Target fast back to back capability Resource locking PCI interrupts auiii iiis Base Address Registers Expansion ROM eee PCI master performance ideal maximum eese PCI slave performance ideal maximum eese Memory spa c Temperature Operating o cete tne Storages e i deed A 2 Supported Supported 32 bits 5 V only 32 bit half size card Supported Medium 1 clock Supported Supported as a master and slave Interrupts passed on INTA signal dedicated to local registers size configurable from 256 B to 4 GB 8 KB 132 MB s 16 Dwords max 33 MB s to local registers 32 KB minimum programmable to 55 C 40 to 85 C ni com Appendix A Specifications for PCI MXI 2 Relative humidity Noncondensing operating 0 to 9596 Noncondensing storage 0 to 9596 EMI tt e det FCC Class A verified Physical Board dimensions 174 63 by 106 68 mm 6 875 by 4 2 in Connectors ati dee Single fully implemented MXI 2 connector Slot requirements esee Single PCI slot Aid etre ttes Contact factory Weight esae tri bii
128. so be configured to drive the external CLK SMB signal from the VXIbus CLK10 signal Switch S3 controls whether the VXI MXI 2 drives or receives the external CLK SMB signal If you change the S3 setting to drive CLK10 out the external CLK10 SMB connector do not set the W3 jumper to receive the SMB CLK10 signal instead use the settings shown in either Figure 3 5a or Figure 3 5c as appropriate National Instruments Corporation 3 9 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation When switch S3 is set so that the VXI MXI 2 receives the SMB CLK10 signal you have the option to add a 50 termination to the signal by setting switch S4 S4 is unused its setting does not matter when 53 is configured to drive the external CLK SMB signal You can use an additional switch S5 to control the polarity of the external CLK SMB signal when S3 is configured to drive it S5 is unused its setting does not matter when S3 is configured to receive the external CLK SMB signal Figure 3 6 shows four configuration settings for the VXI MXI 2 Figure 3 6a shows the default configuration which is for driving the inverted external CLK SMB Use the settings of Figure 3 6b to drive the noninverted external CLK SMB signal Figure 3 6c illustrates the setting for receiving the external CLK SMB signal Finally you can configure the switches as shown in Figure 3 6d to receive the external CLK SMB signal with a 50 Q termination 3 Note The
129. ssentially form one continuous window If the windows are mapped to different destinations the base of each inward window maps to the base of each destination If the windows both map to the shared RAM destination but the byte order is different the base of each inward window maps to the base of the shared RAM destination This results in one half of the window accessing the system RAM in Little Endian byte order and the other half accessing it in Big Endian byte order National Instruments Corporation 6 9 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility AN Caution There is a potential problem when opening up a shared memory region to point to system RAM The PCI bus may return a retry on any cycle into system RAM As a consequence an external VXI VME device accessing the system RAM may get a VXI VME retry back If the external VXI VME device does not support VXI VME retry the VXI VME device will falsely detect the retry condition as a bus error condition VXI VME devices that support retries will not have this problem because they can handle VXI VME retry conditions correctly by automatically retrying the access For example the National Instruments VXI DAQ boards handle VXI VME retry conditions properly and do not exhibit this problem Resource Manager Delay The only option under the Resource Manager portion of the Logical Address Configuration Editor is the Resource Manager Delay control Resource Manager Delay h
130. t information This icon denotes a caution which advises you of precautions to take to avoid injury data loss or a system crash Bold text denotes items that you must select or click on in the software such as menu items and dialog box options Bold text also denotes parameter names Xii ni com italic monospace monospace bold monospace italic About This Manual Italic text denotes variables emphasis a cross reference an introduction to a key concept or text as it appears on a hardware label This font also denotes text that is a placeholder for a word or value that you must supply Text in this font denotes text or characters that you should enter from the keyboard sections of code programming examples and syntax examples This font is also used for the proper names of disk drives paths directories programs subprograms subroutines device names functions operations variables filenames and extensions and code excerpts Bold text in this font denotes the messages and responses that the computer automatically prints to the screen This font also emphasizes lines of code that are different from the other examples Italic text in this font denotes text that is a placeholder for a word or value that you must supply Usually this is a variable in a directory path for example NIVXI refers to the actual location where you have installed the NI VXI software Related Documentation The following documents co
131. t need P3 support PCI MXI 2 for Linux The VXI MXI 2 uses address mapping to convert MXIbus cycles into VXIbus cycles and vice versa By connecting to the PCI MXI 2 board the VXI MXI 2 links the PCI bus to the VXIbus The VXI MXI 2 can automatically determine if it is located in VXI Slot 0 and or if it is the MXlIbus System Controller The VME MXI 2 module is a single slot double height VMEbus device with optional VMEbus System Controller functions It uses address mapping to convert MXIbus cycles into VMEbus cycles and vice versa just like the VXI MXI 2 By connecting to the PCI MXI 2 board it links the 1 4 ni com Chapter 1 Introduction and Quick Start PCI bus to the VMEbus The VME MXI 2 can automatically determine if it is located in the first slot of a VMEbus chassis and if it is the MXIbus System Controller Also the VXI MXI 2 and VME MXI 2 automatically terminate the MXlbus if installed as the first or last device in the MXIbus If installed in the middle of the MXIbus both the VXI MXI 2 and VME MXI 2 automatically disable MXIbus termination In addition you can have up to 64 MB of onboard DRAM on the VXI MXI 2 and VME MXI 2 modules that can either be shared with the VXI VMEbus and MXlIbus or used as a dedicated data buffer The PCI MXI 2 VXI MXI 2 and VME MXI 2 products achieve high performance block transfer rates by integrating the MITE custom ASIC a sophisticated dual channel DMA controller with standard interfac
132. the PCI MXI 2 and the VXI MXI 2 or VME MXI 2 vxiedit is the VXI resource editor program that you use to configure the system and to edit the manufacturer name and ID numbers the model names of VXI and non VXI devices in the system and the system interrupt configuration information This program also displays the system configuration information generated by the Resource Manager Note text based version vxitedit is also available as an alternative Although this chapter focuses only on the graphical vxiedit program the two programs are functionally equivalent For information on vxitedit refer to the NI VXI Text Utilities Reference Manual Running the VXledit Configuration Utility To run vxiedit type vxiedit at the command prompt You can run vxiedit from any directory but make sure that both the PATH and NIVXIPATH environment variables have the destination directory of the NI VXI software added to them NIVXIPATH is used by the application to find the different configuration files cfg table files tb1 and help files h1p during its execution The default pathname used by the program if NIVXIPATH is not set is usr local nivxi Most of the features on the PCI MXI 2 VXI MXI 2 and VME MXI 2 are configurable through software using vxiedit rather than through hardware switches or jumpers on the boards themselves In addition the vxiedit utility can override some of the hardware settings National Instrument
133. the location and factory default settings on the module Your PCI MXI 2 may look slightly different National Instruments Corporation 2 1 PCI MXI 2 for Linux Chapter 2 PCI MXI 2 Configuration and Installation 3862 3862 3 3 r taj 3862 3862 5852 E a nae 21 R zu Js 3 z u a 3662 3662 3662 KA 8 3662 jen c c 3 oe gt sh oraz zo c 020 g5 amp c 2j yen DN E N c gt or Ex 2 5 ge m P gla 66 S 9r 3 aSa 3 7 gt gt gt gt gt gt gt o gt Seer Q P 69 2 y93H8c en SILNOW 10MHZ q S PCI MXI 2 ma 1 NATIONAL INSTRUMENTS CORP S N 1 U17 2 DRAM Figure 2 1 PCI MXI 2 Parts Locator Diagram PCI MXI 2 for Linux 2 2 ni com Chapter 2 PCI MXI 2 Configuration and Installation Configuration EEPROM The PCI MXI 2 has an onboard EEPROM which stores default register values that are loaded at power on The EEPROM is divided into two halves a factory configuration half and a user configurati
134. tion calls For information on the VXImemAlloc function refer to the NI VXI User Manual and the NI VXI Programmer Reference Manual National Instruments Corporation 6 7 PCI MXI 2 for Linux Chapter 6 NI VXI Configuration Utility 5 Note When the Address Space field is in the default setting of A16 only this field is ignored This field is also ignored if the Memory Select fields for both the lower and upper half windows are set to Onboard memory Advanced Shared RAM Settings Clicking the Advanced button displays a dialog box to configure the destination of MXIbus cycles that map into the PCI MXI 2 through the A24 A32 shared RAM 3 Advanced Shared RAM Settings x This panel is intended for advanced users only Refer to the Getting Started manual for more information m Lower Half Window Upper Half Window Enable byte swapping Memory Select gt Memory Select f System memory fe System memory Onboard memory Onboard memory Map upper and lower halves to same address Cancel Default Figure 6 4 Advanced Shared RAM Settings Note When the Address Space field is in the default setting of A16 only these fields ignored and cannot be accessed The VXI VME shared RAM is divided into two halves or windows You can select the byte order for each half independently You can map each half of the VXI VME shared RAM independently into system m
135. tions hy Note Make sure the MXI 2 cable is connected to the PCI MXI 2 when you power on or reboot the computer This is required for the PCI MXI 2 to automatically detect whether it will be the MXIbus System Controller MXI Bus Timeout The MXIbus Bus Timeout BTO is a watchdog timer for transfers on the MXlIbus The MXIbus operates only when the PCI MXI 2 is acting as the MXIbus System Controller After the specified amount of time has elapsed the BTO circuitry terminates a MXIbus cycle if no slave has responded The BTO is also disabled when the current MXIbus cycle maps to the VXI VMEbus through a VXI VME MXI 2 The default timeout value is 1 ms If the Enable MXI 2 Auto Retry checkbox option is enabled you should use a MXI Bus Timeout of 1 ms or greater MXI CLK10 The 2 is capable of either receiving or driving the MXIbus CLK10 signal You can use the Drive or Receive options of the MXI CLK10 feature to control the direction of the MXIbus CLK10 signal By default all MXI 2 boards receive MXI CLK10 the Receive option is active therefore you must choose one board on your MXI 2 bus to drive CLK10 by changing the value of the control to Drive For most configurations it is recommended to choose the System Controller as the CLK10 source for simplicity The only exception you may want to make is if you want your triggers synchronous to the VXI 10 MHz clock N Caution Do not configure more than one MXIbu
136. ttings If you need more information or if you want to try a different configuration refer to the appropriate hardware or software chapters in this manual which describe the installation and configuration steps in greater detail 1 6 ni com Chapter 1 Introduction and Quick Start Hardware Installation To guard against electrostatic discharge touch the antistatic plastic package to a metal part of your computer before removing the PCI MXI 2 from the package Install the PCI MXI 2 in an available PCI slot in your PCI based computer By default the PCI MXI 2 automatically detects whether it should be the system controller on the MXIbus Verify that the correct cable end labeled Connect This End To Device Closest To MXIbus Controller In This Daisy Chain is attached securely to the PCI MXI 2 You must connect the cable this way so that the PCI MXI 2 can correctly detect whether it should be the system controller on the MXIbus For more information refer to Chapter 2 PCI MXI 2 Configuration and Installation You received either a VXI MXI 2 or a VME MXI 2 in your PCI MXI 2 kit To guard against electrostatic discharge touch the antistatic plastic package to a metal part of your computer before removing the VXI MXI 2 or VME MXI 2 from the package Install the VXI MXI 2 in the first slot of a VXI chassis or install the 2 in the first slot of a VME chassis The VXI VME MXI 2 default configuration automatically detects whether
137. two 1 35 in DRAM SIMMs Table 3 1 lists the SIMMs you can use Table 3 1 VXI MXI 2 DRAM Configurations National Instruments Switch Setting Bank 0 Bank 1 Total DRAM Option of S6 0 m 256 K x 32 or 1 MB ON 256 K x 36 256 K x 320r 256 K x 32 or 2MB ON 256 K x 36 256 K x 36 512K x 32 or 2MB ON 512 K x 36 512 K x 32 512 K x 32 or 4 ON 512 K x 36 512K x36 1M 32 4MB YES ON 1M x 36 1M x 320 1Mx32or 8 MB ON 1M x 36 1M x36 2M x 32 or 8 MB YES ON 2M x 36 2M x 32 or 2M x 32 16 MB ON 2M x 36 2M x 36 4M x 32 or 16 MB YES OFF 4 M x 36 4M x 32 or 4 32 or 32 MB OFF 4M x36 4M x36 8Mx320r 32 MB YES OFF 8M x 36 8 M x 32 or 8 M x 32 or 64 MB YES OFF 8M x 36 8 M x 36 National Instruments Corporation 3 17 PCI MXI 2 for Linux Chapter 3 VXI MXI 2 Configuration and Installation You can use 32 or 36 bit SIMMs because DRAM parity is not required Because the VXI MXI 2 supports only one organization at a time all SIMMs installed must be of the same type Use Bank 0 first when installing the SIMMs This allows you to install up to 64 MB The VXI MXI 2 supports DRAM speeds of 80 ns or faster Switch S6 is used to select the size of each SIMM The SIMM sockets and S6 are accessible only by removing the right side cover To access these components remove the four screws on the top the four scr
138. ual How To Use the Manual Set rn eer extet e x ee dias ERES xi CONVENTIONS suis noter e RH ERA P KE RP xii Related Documentations ise riter e e oa cou e ee Ee Leine eben be xiii Chapter 1 Introduction and Quick Start How to Use This Manual iidem P REIR EU ENSE ER 1 2 PCI MXI 2 Kit OVerViQW iocis ertt iet eoe ee a e tede re Haee 1 3 What You Need to Get Started itt e err HE RR 1 3 MXI 2 Description i dei teet eee out tuted ette pe oen ee dvi ett 1 3 Hard Ware Descriptions tue taie REDE UR CE UAR 1 4 Software Descriptio ua eio 1 5 Optional Software snars e e He e e b edere 1 6 Q ick Starto 5a nip eue i rede ites a 1 6 Hardware Installation i E e ete e e DR RE 1 7 Installing and Loading the NI VXI NI VISA Software for Linux 1 8 VME d 1 8 Device T ter ctioti e di eoo te eee t eatin eines 1 8 Default e te bep t RE deg e e t mda 1 9 PCGEMXE2 nS us ahead 1 9 VXI VME MXE 2 ie it ti ee e e eo PEE 1 12 Chapter 2 PCI MXI 2 Configuration and Installation Configure the PCI MXI 2 eee terree eere Pe GER ERROR os 2 1 Configuration EEPROM e aire e e A ener nennen 2 3 Installthe PCEMXI 2 a r ote a tratta ert ener N 2 3 Chapter 3 VXI MXI 2 Configuration and Installation Configure the V XI EMXI 2 n nece t eee tup eite etg 3 1 Front P
139. ult b Leftmost VXI MXI 2 in Mainframe No Yes No Yes 25 04 s8 mmu ALL L 22 77 59 50 VXI MXI to left VXI MXI to left VXI MXI to right VXI MXI to right c VXI MXI 2 between Two Others d Rightmost VXI MXI 2 in Mainframe Figure 3 4 VXIbus Local Bus Configuration VXIbus CLK10 Routing When the VXI MXI 2 is installed in Slot 0 of your mainframe it supplies the VXIbus CLK10 signal The VXI MXI 2 can use three different sources to generate this signal the onboard oscillator the external CLK SMB connector and the MXIbus CLK10 signal Use the three position jumper W3 to select these options as shown in Figure 3 5 Notice that Figure 3 5b and Figure 3 5c also show switches S3 and 57 respectively You must configure these switches as shown when using the corresponding CLK10 source setting of W3 PCI MXI 2 for Linux 3 8 ni com Chapter 3 VXI MXI 2 Configuration and Installation From Onboard Oscillator From SMB S3 must be set to mA From zd a CLK10 Generated from Onboard Oscillator Default From Onboard Oscillator From SMB S3 must be set to IN NS We From MXIbus X SMB CLK10 Direction 8 b CLK10 Generated from SMB From Onboard Oscillator From SMB S3 must be set to IN N W Tii CLK10 from From MXIbus WS orm Ne VEL A S7 c CLK10 Generated from MXIbus Figure 3 5 VXIbus CLK10 Routing The VXI MXI 2 can al
140. ult Settings sections in Chapter 1 Introduction and Quick Start The material in those sections may be all you need to get up and running with your PCI MXI 2 kit When you have successfully set up your system you can begin to develop applications in NI VXI and or NI VISA The NI VXI User Manual presents the concepts of VXI and prepares you for detailed explanations of the NI VXI functions Study the descriptions of each function given in the online help utility to fully understand the purpose and syntax of each function This manual is available in the NIVXI manuals directory where NIVXI refers to the actual location where you have installed the NI V XI software Use the Acrobat Reader program Version 3 or later to open this file We recommend the VISA API for new applications Refer to the NI VISA User Manual to learn about VISA and how to use it in your system The NI VISA online help describes the attributes events and operations you can use in NI VISA The user manual is available in the VXIpnp linux NIvisa manuals directory where VXIpnp refers to the actual location where you have installed the NI VISA software Use the Acrobat Reader program Version 3 or later to open this file The following conventions are used in this manual The symbol indicates that the following text applies only to a specific product a specific operating system or a specific software version This icon denotes a note which alerts you to importan
141. unctions You can then modify the sample programs to try out different aspects of the NI VXI software The sample programs for the Linux C compiler are in the usr local nivxi examples directory for NI VXI and usr local vxipnp linux NIvisa Examples directory for NI VISA The easiest way to compile the sample programs is to use the makefile included with the NI VXI NI VISA software For example go to the examples directory and type make You may need to define a symbol so that the NI VXI library can work properly with your program The VXILINUX symbolis required for NI VXI applications but not NI VISA applications VXILINUX designates the application as a Linux NI VXI application You can define this symbol using a define statements in the source code or you can use the D option in your compiler If you use a define statement you must define the symbol before including the NI VXI header file nivxi h If you use the makefiles to compile the sample program the makefile already defined the necessary symbol 7 4 ni com Chapter 7 Using the NI VXI NI VISA Software If you define this symbol in your source code your source code should look something like the following sample code define VXILINUX include lt nivxi h gt Refer to the documentation that came with your compiler package for detailed instructions about using the compiler and the various tools linker debugger and so on Your compiler documentation is an important an
142. ure 3 8a shows the default setting for a nonterminated trigger input SMB Use the setting of Figure 3 8b to terminate the trigger input SMB Switch S2 is located above switches S3 S4 and S5 which have no effect on this configuration PCI MXI 2 for Linux 3 12 ni com Chapter 3 VXI MXI 2 Configuration and Installation C Jo On 500 Termination for External Trigger Input S2 5 KZA SMB CLK10 Direction pee Edd 22222224 On 509 Termination for SMB CLK10 Effective only when S3 is set to IN p eme se SMB CLK10 Output Polarity Effective only when S3 is set to OUT NON INVERTED INVERTED a Non Terminated External Trigger Input SMB Default S2 Off A On 50Q Termination for External Trigger Input s3 our PL SMB CLK10 Direction S4 Off 22222 On 500 Termination for SMB CLK10 Effective only when 53 is set IN S5 2222222 SMB CLK10 Output Polarity Effective only when S3 is set to OUT NON INVERTED INVERTED b Terminated External Trigger Input SMB with 500 Figure 3 8 SMB Trigger Input Termination MXIbus Termination The first and last MXIbus devices connected to the MXIbus whether it is a single MXI 2 cable or daisy chained MXI 2 cables must terminate the MXlIbus Any MXIbus devices in the middle of a MXIbus daisy chain must not terminate the MXIbus The VXI MXI 2 automatically senses whether it is at either end of the M
143. y Note This field is effective only when the PCI MXI 2 is at its default logical address of 0 The PCI MXI 2 is the Resource Manager only if its logical address is 0 This field specifies the time in seconds that the Resource Manager RM waits before accessing any other VXI VMEbus device s A16 configuration registers RM Delay Range Default Value 0 to 65535 s 5 PCI MXI 2 for Linux 6 10 ni com Chapter 6 NI VXI Configuration Utility Figure 6 5 shows the Device Configuration Editor The following paragraphs describe the options you can select for each of the fields 3 Device Configuration E ditor System IRQ Level iy er Local controller troller L 1 HODIE IRR Number of Handlers Number of Interrupters E 0 a 1 a D Protocol Register Read Protocol Response z xFFO a x8448 Cancel Default Figure 6 5 PCI MXI 2 Device Configuration Default Controller LA 1 Many NI VXI functions use controller as a parameter with 1 accepted as a valid value You use this selection to determine which controller you are referring to when you use 1 in these NI VXI functions Review the descriptions of the NI VXI functions to determine which are applicable for this control By default the Default Controller LA 1 option is set to First remote controller so that any NI VXI functions that are passed the value of 1 for the controller parameter
144. y writes to the factory area will be ignored The factory area is protected regardless of the setting of switch 1 of U17 Figure C 1 shows the default settings for EEPROM operation UN Caution Do not alter the settings of switches 3 and 4 of U17 Leave these switches as shown in Figure C 1 unless specifically directed by National Instruments National Instruments Corporation C 1 PCI MXI 2 for Linux Appendix C EEPROM Configuration U17 FOV m 2 E TST o POS A Jol cr Figure C 1 EEPROM Operation Default Settings Fixing an Invalid EEPROM Configuration Certain EEPROM configurations can cause your PCI computer to lock up while in its boot process Generally only the size and location of the memory windows can cause problems with the PCI MXI 2 locking up your system For example many PCI based computers will not boot if a board in its system requests more memory space than the computer can allocate If you encounter this situation you should reduce the size of the PCI MXI 2 user window If this situation occurs after changing the configuration on the PCI MXI 2 follow these steps to reconfigure the PCI MXI 2 Turn your computer off UN Caution To protect both yourself and the computer from electrical hazards the computer should remain off while changing the settings on the PCI MXI 2 module PCI MXI 2 for Linux 2 Remove the top cover or access port to the PCI bus 3 Change swit
145. ystem controller 6 14 MXlIbus system controller 6 27 VMEbus system controller 6 23 customer education E 1 professional services E 1 technical support E 1 D Default Controller LA 1 6 11 default settings 1 9 PCI MXI 2 for Linux 1 2 hardware settings table 1 13 PCI MXI 2 board Bus Configuration Editor table 1 11 Device Configuration Editor table 1 11 hardware settings table 1 9 Logical Address Configuration Editor table 1 10 VME MXI 2 module Configuration Editor settings table 1 13 hardware settings table 1 13 VXI MXI 2 module 1 13 Configuration Editor settings table 1 13 Device Configuration Editor See PCI MXI 2 Device Configuration Editor device type for PCI MXI 2 setting 6 6 diagnostic resources E 1 documentation conventions used in manual xii how to use documentation set figure xi how to use this manual figure 1 2 online library E 1 related documentation xiii DRAM configuration VME MXI 2 module 4 8 DRAM configurations table 4 9 SIMM size configuration figure 4 9 VXI MXI 2 module 3 17 DRAM configurations table 3 17 SIMM size configuration figure 3 18 driver window See user and driver window configuration drivers instrument E 1 software E 1 ni com E EEPROM See configuration EEPROM electrical specifications PCI MXI 2 A 3 VME MXI 2 module A 11 VXI MXI 2 module A 7 enable byte swapping option VXI VME shared RAM 6 9 environmental spec

National Instruments 370551A-01 Network Card User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents