Why do the BusTools and Test Configuration applications fail when multiple Condor PCI, cPCI, PMC or PC/104-Plus products are installed in my computer?
Installation of Multiple Condor PCI/cPCI/PMC/PC/104-Plus Products under Windows XP/2000
When you install a Condor API product (i.e., IP-AVIONICS-SW, CEI-x20-SW or BusTools/1553-API), the installed device is assigned a device number (0-9), based on the order in which devices are installed.
For products installed under the Windows NT or 9x operating systems, this device number remains associated with the API installation value assignment throughout the lifespan of the device on that computer.
Under Windows XP/2000, the device number associated with the API installation value may change after a computer restart when multiple devices are installed. The actual device number is enumerated to the devices dynamically, based on the physical location in which devices are installed in the computer.
Installation of the Condor API and Devices
When you install a Condor API product, the first installed product is designated as Device 0; the second installed product is designated as Device 1, and so on. This should be true regardless of the physical slot in which the products are installed. They should also appear in the Windows Device Manager designated with this device number (i.e., CEI-500 (Board0) Dev0, CEI-520 (Board 0) Dev0, PCCARD-1553 (Board0) Dev1, etc.). When running the test configuration program for the second and subsequent devices installed, the device number remains as assigned when installed until the computer is restarted.
Once the computer is restarted, the device number assigned by the device driver is enumerated for each device based on the physical location of the device in the computer, whether that location is a PCI slot on the motherboard, or a cPCI slot in a PXI chassis. The device number enumeration begins with Device 0 assigned to the PCI/cPCI/PMC/PC/104-Plus device installed in the lowest slot, (usually closest to the processor). All subsequent Condor boards receive the next available device number, based on the increasing slot in which they are installed.
There is currently no easy way to positively determine what the enumerated device number is defined to be for a PCI/cPCI/PMC/PC/104-Plus device; rather, it is up to you to determine the desired device number scheme based on the placement of the PCI/cPCI/PMC/PC/104-Plus products in the computerâs PCI slot or chassisâ cPCI slot. If you plan on installing multiple Condor products in a computer, it is recommended you install the products in slots farthest from the processor to avoid IRQ resource conflicts with other devices. It is also recommended you install the products in a specific order and location. The first installed product should be installed in the lower of the slots chosen for Condor devices, (closer to the processor), the second installed product in the next higher slot, and so forth.
Condor Application and API Product Issues
Problems Encountered with BusTools/1553
In the installation of BusTools/1553, the initial definition is that Device 0 is a Condor MIL-STD-1553 device. If the 1553 product is enumerated as Device 1, you must modify the file Bustools32.ini as follows:
- Open BusTools/1553.
- Click New Topology from the toolbar.
- Set the Board Configuration to match the 1553 product type.
- Click the OK button. An error dialog appears.
- Click the OK button.
- Close BusTools/1553
- Edit the file Bustools32.ini (located in the \Windows or \WinNT folder) using a text editor such as Notepad.
- Modify the (second) line under [Setup Info0] from HARDWARE_ADDRESS=0x0 to HARDWARE_ADDRESS=0x1.
- Close and save Bustools32.ini.
- Open BusTools/1553.
- Click New Topology from the toolbar.
- The Board Configuration should show your 1553 product type. Do not modify this selection, as that causes an overwrite of the Bustools32.ini file, and the modification performed in step 8 will be lost.
- Click the OK button and the initialization of the 1553 product should be successful.
Refer to Appendix D of the "BusTools/1553 User Manual" for more information regarding hardware configuration issues.
Problems Encountered with BusTools/ARINC
The BusTools/ARINC application requires Device 0 to be an ARINC device. If you install either a CEI-520 or CEI-620 in combination with a (c)PCI-1553, you must insure the CEI-x20 device is installed first, in a lower slot, and enumerated as Device 0.
Problems Encountered with BusTools/1553-API Test Applications (non-modular 1553 products)
When you install BusTools/1553-API, batch files are created containing the device number and board type assigned during the installation. These batch files are referenced by the Test Config and One-Shot shortcuts, and are used to invoke the respective executable with the desired arguments. If a 1553 product was assigned as Device 0 during installation, but is then enumerated as Device 1 after a computer restart, the invocations of these test applications fail. To successfully test the application, double-click the executable by viewing the contents of the \Condor BusTools-1553-API\Examples\Win32 folder using the Windows Explorer. Enter the device number assigned based on the situation, and not necessarily based on what was assigned during the installation of the product. You should modify the respective batch file for both executables in this same folder, changing the device number argument(s) as necessary.
Problems Encountered with CEI-x20-SW and Condor Modular Products Test Applications
Modular products include BusTools/1553-API and IP-AVIONICS-SW. When a test program is executed for these products, you are prompted for the desired device number. The API attempts to match these device numbers to Windows registry entries defined for the respective device number assigned during installation of the product. If the device-number-referenced registry entry for PCI Manufacturer/Device ID doesn't match-up with the application because the device driver-enumerated device ID has changed, the API returns an error and the application fails. All CEI-x20 and PCI/cPCI modular products must be installed so the assigned Device ID and device driver enumerated device ID are an exact match.