Please see our FAQ titled “Driver Support for Various Windows Operating
Systems - 64bit Windows and running a 32bit EXE”, at URL http://www.mil1553.com/faqs.
This document spells out the necessary changes for the hardware driver (at
the Device Manager level), and for the software drivers.
(a) Our software API supports all current modules of the same type. So, the same software tools
installation is applicable for the M4K and the M8K modules on their respective cards. M4K modules
sit on 2000 & 4000 family cards and on the first generation UNET; M8K modules sit on 8000 family
cards and on the UNET2.
(b) There is a base card dll (called Exc4000Ms.dll) which contains API functions for all the base card
families: 2000, 4000, 8000, UNET, UNET2.
There is a module level dll (called ExcProtocolMs.dll, where the word protocol is replaced with the
actual protocol name of the module). In addition, there are lower level dlls (ExcUnetMs.dll,
ftd2xx.dll, ftd3xx.dll) with calls that are used for extracting packets from the cards/modules.
A full set of dlls is required for use with all cards (even for non-UNET cards). After installing your
software tools, the set of dlls is available at folder
“C:\Excalibur\Protocol Software Tools\Source\lib\excMSVisual”. Here you will find subfolders
Win32/x64 and, for each of these, Debug/Release. Select the folder that matches your compiler
settings, and take the full set of dlls.
For 32bit Windows, copy the dlls to the folder of your EXE, or to C:\Windows\System32.
For 64bit Windows, copy the dlls to the folder of your EXE, or to C:\Windows\SysWOW64. You can
use either the 32bit set of dlls, libs & exes, or the 64bit set.
The software tools package comes with folders Manuals which contains hardware & software
manuals, and Source which contains source code for the dll, compiled dlls & libs for 32bit/64bit
(subfolders DllProtocolSource, lib), and demo programs (source code + EXEs) compiled for 32bit (in
folder Source\demos_protocol\bin) and for 64bit (in folder Source\demos_protocol\bin64).
The API for the base card level functions is found starting at folder “C:\Excalibur\4000PCI Software
Tools”.
Let us examine the times of the messages.
Each message (label) is one 32-bit word.
In addition, we have 4 bit-times between messages, so we have a total of 36 bit-times
for each label.
At low speed, each bit time is 80 usec (microsec), so the one word takes 80*36 = 2880
usec to be transmitted.
Using data rate mode, with data rate of 125 bit-times, this means that we want to
transmit the word every 80*125 = 10,000 usec.
1. The algorithm used for Data Rate mode is as follows:
• set up all the blocks & their periodicity
• transmit the first block
• then check if the period of first block has expired and needs to be
retransmitted
• if NOT, transmit next block
• then check if the period of every block from the first block on, has expired, one
at a time, and needs to be retransmitted
• if NOT, transmit the next block
Therefore, if the periods were not set up properly, it is possible that some block(s)
will be transmitted multiple times, and some blocks will not be transmitted at all. So,
after transmitting each block we check to see if the period of every block, that has so
far been transmitted, has expired. This will happen after 10,000 usec, which is eaten
up by transmitting 4 labels (each of size 2880 usec). So, at this point, instead of
transmitting label #5, we go back & transmit label #1, then label #2, then label #3,
then label #4, and then back again to label #1, ...
So, we will never transmit label #5.
If you use a larger data rate, of 250 bit-times, this translates to 20,000 usec, which
gives enough time for all 5 labels to be transmitted, then wait about 5600 usec, and
go back to transmitting the labels in sequence again. Or you could use a smaller rate,
say 180 or perhaps 200, which will cover the 14,400 usec total needed by the five
labels.
2. Alternatively, you can use Interblock mode. Its algorithm is:
• set up all blocks & their interblock gaptimes (how many bittimes to wait
between transmitting this block and the next block)
• transmit each block in sequence, waiting the appropriate time in between
transmission of one block & the next one
• NOTE that all blocks will be transmitted ONCE, and then we start a new round
of transmitting all the blocks ONCE, etc.
Install the software tools for the module. Our current software tools release contains:
API Source code and DLLs:
• a single set of source code files for the API functions – found at folders
"C:\Excalibur\ProductName Software Tools\Source\DllProductNameSource” and “include”
• one set of DLLs for use with 32bit applications - found at folder structure
"C:\Excalibur\ProductName Software Tools\Source\lib\excMSVisual\Win32” (with
subfolders Debug & Release)
• one set of DLLs for use with 64bit applications - found at folder structure
"C:\Excalibur\ProductName Software Tools\Source\lib\excMSVisual\x64” (with subfolders
Debug & Release)
Demo Programssource code and EXEs:
• a single set of source code for demo programs- found at folder structure
"C:\Excalibur\ProductName Software Tools\Source\demos_ProductName”, separate folder
for each demo program
• one set of demo program EXEs compiled for 32bits- found at folder structure
"C:\Excalibur\ProductName Software Tools\Source\demos_ProductName\bin”
• one set of demo program EXEs compiled for 64bits- found at folder structure
"C:\Excalibur\ProductName Software Tools\Source\demos_ProductName\bin64”
NOTE: You need to take a full set of DLLs as found in the appropriate subfolder (under lib) for your
compiler setting: [Win32 or x64], and [Debug or Release]. Copy the full set of DLLs to the folder
where your EXE sits, or to C:\Windows\SysWOW64 (for 64bit Windows).
The DLLs include: a module level DLL (ExcProductMs.dll), a base-board dll (Exc4000Ms.dll), and
other dlls for lower-level functions to access the registers on the module.
For 32bit applications, the DLL set contains an additional 32bit dll named frontdesk.dll.
The 8000PCIe card is our latest release of the evolution of the 4000PCI[e] card family. That is, it is
basically a 4000PCIe that supports up to 8 modules.
The M4K modules that are supported on the 4000PCI[e] family cards, have evolved into M8K
modules that are supported on the 8000PCIe family cards. The software for the M4K modules has
evolved into supporting the corresponding M8K modules.
Hence, use the latest software release for M4KProductName for use on the M8KProductName
module.
For example, for the module code Fx, M8K1553Px module, the software installation is available for
free download on our website, at URL https://www.mil-1553.com/m4k1553px, filename
m4k1553pcipx-st-win32-win64.zip.
In addition, you need the appropriate hardware driver so that the Device Manager will be able
recognize the card. This driver is available at URL https://www.mil-1553.com/kernel-drivers, file hwpci-winx64.zip for 64bit Windows (or hw-pci-w2k.zip for 32bit Windows). If your machine is 64bit
Windows 10 with Secure Boot, then you need the hardware driver filename hw-pci-winx64-SecureBoot-Win10.zip .
We first suggest that you install (on the target machine) the latest released
software tools package for each of your module types. Then, you will need a new
set of DLLs that match your compiler. You will then copy the set of DLLs to the
same folder where your EXE sits (or where it expects the DLLs), and run your EXE.
Where are the DLLs found ?
For Borland compiled EXEs: If we have support for Borland DLLs, the set can be
found at “C:\Excalibur\[protocol] Software Tools\Source\lib\excBorland”. Make
sure to the take the full set of DLLs.
For Microsoft compiled EXEs: The set of DLLs can be found at
“C:\Excalibur\[protocol] Software Tools\Source\lib\excMSVisual”. In this folder,
you will find two subfolders, Win32 (for 32bit DLLs), and x64 (for 64bit DLLs). In
each subfolder, you will find two subfolders: Debug and Release. Select the DLLs
from the desired subfolder and copy them to your target folder.
NOTE: Please also see the FAQ titled “Driver - 64bit Windows and running a 32bit EXE.pdf”
We have seen this problem. It is important to verify that the compiler options are set
the same on the 64bit Windows machine as on the 32bit Windows machine. The
default options may be different, and very critical for successful compilation & running.
For example, if a structure has an odd number of bytes or words, the compiler may
default to a data alignment that adds extra bytes/words to the structure. This might
not be compatible with our DLL and its compilation options.
For instance, here are some changes that you should make to your Borland C++
Builder (5) Project, in order to work well with our DLLs.
Project > Options > Advanced Compiler:
- Data Alignment should be BYTE (not Quad word)
- Calling convention should be STANDARD CALL (not C)
Note that the size of an int may be different across compilers and operating systems
1. Concerning software tools packages:
We combined software for similar cards into a single software package. For
instance, "1553Px Software Tools" now covers M4K1553Px[S] module,
M8K1553Px[S] module, UNET/Px, 1553Px module on UNET2; and older
cards EXC-1553PCMCIA/Px and /EP. [ Similarly for 429RTx modules & cards. ]
In addition, we made a single combined package for 32bit and 64bit
compiled drivers (DLLs, demo programs). The package comes with a single
set of source code files for the DLLs, a single set of source code demo
programs, 32bit compiled DLLs and demo programs, and native 64bit
compiled DLLs and demo programs. We supply VS2008 project solutions
and project files for the different components of the package.
At the end of the software tools installation, we also install the associated
GUI package for this protocol. Note that the GUI packages now come
packaged with all the necessary DLLs. So, it is not necessary to install
software tools prior to running the GUI packages.
2. Concerning LabVIEW and LabWindows tools packages:
We have combined support for multiple cards using one set of tools:
LabVIEW VIs and LabWindows CVIs for various (not yet for all) cards
running the same protocol (just like the combined software tools).
Note that the newer LabVIEW and LabWindows packages come packaged
with all the necessary DLLs. So, it is not necessary to install software tools
prior to running the VI or CVI packages.
3. All Excalibur software is now installed to a folder structure starting at
C:\Excalibur. Locate the folder for your protocol; the protocol name is
generally part of the folder name. Subfolders include Manuals & Source.
Source includes subfolders DLLsource (.c), include (.h), lib (.DLLs and .LIBs),
demos_xxx (which includes folders for each demo program, and folder bin
for 32bit compiled EXEs, folder bin64 for 64bit compiled EXEs).
Utilities programs (e.g., ExcConfig), Showhex, ExcLaunchPad) are installed
to folders at C:\Excalibur\Utilities. There are also additional folders here for UNET utilities and USB drivers.
4. Please see file ReadMeFirst_XXX.txt in your root folder for more information on the folder structure.
We used to place a copy of all of Excalibur DLLs into WINSYSDIR, the Windows system folder.
One day, a number of years ago, we got "burned" because another company did
the same thing and we had a name clash. As a result, we purposely decided to
change this policy. We renamed all of our DLLs to a more consistent schema (to
reduce the possibility of a name clash), and stopped copying to WINSYSDIR.
We decided to place the DLLs in the target installation folders ONLY (under folder C:\Excalibur).
The customer will find the DLLs and copy them to wherever he needs to find them:
• in the installation folder,
• in the folder where the EXE sits,
• just be available automatically (i.e., place it in WINSYSDIR or C:\Windows\SysWOW64),
• or somewhere else.
You can run multiple applications simultaneously for any specific protocol,
using a single set of DLLs (for that protocol).
For example, for multiple 1553Px modules, you can run demo_bc_general
on module 0, demo_rt_general on module 1, demo_mon on module 2,
demo_loopback on module 3 - all at the same time, simultaneously.
You can run only one application on a specific module at a time.
You can run different applications (or even the same application) on
different modules at the same time. For example, you can run multiple
copies of MerlinPlus or Mystic on different cards (one copy can run on all the modules of a single card).
1. Pin to pin assignments are compatible.
2. The registers & memory maps are different, due to the additional (and larger)
registers for the additional features of the SerialPlus module; as listed in the User's Manual.
3. The latest software covers both the Serial module (all versions) and the SerialPlus
modules. It recognizes which module you have, and applies any API function call to
the appropriate register.
Many functions are handled internally in two flavors: 8bit for Serial, 16bit for
SerialPlus. Despite the different memory maps, the two internal implementations
(8bit and 16bit) are synchronized.
4. IF you use the latest software release (for PCI or for VME/VXI), then there is no
need to change your software application.
5. Here is a list of software API additions to support features only available on the
SerialPlus modules:
ClearRcvCountTrigFlag_SER
ClearRcvPatternTrigFlag_SER
SetModuleTimetagResolution_SER
SetRcvCountTrigger_SER
SetRcvPatternTrigger_SER
SetTransmitGap_SER
The software drivers API handles all the different models of the modules.
Assuming that you use current software tools, there is no problem mixing &
matching different generation modules on the same card.
Of course, newer features (and functions) that were added in a later module /
later firmware or hardware version may not be available on the older module(s).
For the 1553Px module, there are three generations of the M4K module:
- Px first generation (using an AMD chip)
- PxII second generation (using an Intel chip) - hence the II in the module name
- PxIII third generation (using a Nios chip)
For the 429RTx module, there are two generations of the M4K module:
- RTx first generation (using a Motorola chip)
- RTx second generation (using a Nios chip)
- Showhex Memory Display Utility: Select menu item File > Save All Modules to
File, and save the file as a .txt file. Please send us this file. It contains the
contents of memory at the moment you saved the contents.
- new demo_information program: We added / are adding a new demo
program called demo_information_xxxx to each software tools release.
It is incorporated into the installation software for the specific card, like all other
demo programs. This demo program prints to a file the types of all modules on
the card, and for each module of the specific protocol you are running, performs
a call to Init_Module_xxx, to initialize the module. For each module that passes
the initialization function, the program will print the module information (e.g.,
firmware revision, hardware revision) to a file.
- ExcLaunchPad: A general GUI program that gives information about each card
in your machine, and the modules on the card(s).
Please see our FAQ titled “Driver Support for Various Windows Operating
Systems - 64bit Windows and running a 32bit EXE”, at URL http://www.mil1553.com/faqs .
This document spells out the necessary changes for the hardware driver (at
the Device Manager level), and for the software drivers.
All Excalibur cards require (a) hardware installation disk for the given operating system (32bit or 64bit), and
(b) software tools installation for the card/module.
32bit Windows support: All of the products that we sell today have 32bit Windows software tools
drivers. All products have been tested under 32bit Windows XP, 7, etc. This applies to 4000PCI Series
boards as well as to PCMCIA cards. For these products, the filename on the webpage for the product
indicates this using a “-win” in the file name.
64bit Windows support: Most of the products that we sell today have native 64bit Windows
software tools drivers. For these products, the filename on the webpage for the product indicates
this using a “winx64” in the file name. [ In general, Legacy products are not supported under 64bit Windows. ]
64bit Windows support for 32bit software tools: The 32bit software tools for our current cards and
modules will also run under 64bit Windows. Hence, using current 32bit DLLs and a 32bit application
EXE, will run under 64bit Windows.
Hardware installation (a) is quite straightforward. When you install the card in the machine, the Add New
Hardware Wizard will ask for a disk. You need to supply the hardware installation. The necessary files can be
found at URL http://www.mil-1553.com/kernel-drivers .
File names will be hw-pci-osname.zip for PCI cards, and hw-pcmcia-osname.zip for PCMCIA cards. The
osname will be w2k for 32bit Windows (all flavors), and winx64 for 64bit flavors. For example, hw-pciw2k.zip and hw-pci-winx64.zip.
NOTE: If the card was not properly installed, then you might see a device listed in the Device Manager with a
yellow question mark ("?") icon, perhaps called "PCI Device". Right click and select Update Driver, or Install
Driver, and install the necessary driver from the appropriate hardware installation disc
In Windows 7, if the card name is listed under Excalibur PCI Cards, and there is a small question mark on the
icon, then this is OK. The card is properly recognized.
Software tools installation for the card/module (b):
Start at URL http://www.mil-1553.com/4000-family to download software tools for the M4K family of
modules for EXC-4000PCI cards. Click on the name of appropriate module to get to the webpage containing
all the installation packages available for free download for that product. Please also check URL
http://www.mil-1553.com/applications for any applications programs that may pertain to your module. If
your card is not of the M4K family, please navigate the list on the left side of the screen (under the heading
Downloads) to find your card and the list of available software downloads.
You have three options for software installation:
Option (b-1) - For 32bit Windows, you install 32bit software tools (file name on the webpage will be
product-st-win.zip). You can then run your compiled 32bit application, either from its own folder (and it will
access the DLLs from the Windows\System32 folder), or from the folder where we installed the software
tools.
Option (b-2) - Running 64bit application under 64bit Windows: For 64bit Windows, you can install native
64bit software tools (file name on the webpage will be product-st-winx64.zip). You can then run your
compiled native 64bit application, either from its own folder (and it will access the DLLs from the
Windows\System32 folder), or from the folder where we installed the software tools.
Option (b-3) - Running 32bit application under 64bit Windows: In addition, if you want to run a 32bit
application under 64bit Windows, you will need to create a folder containing the 32bit EXE, the necessary
32bit DLLs (e.g., Exc429RTxMs.dll and Exc4000Ms.dll), and the additional 32bit kernel level file frontdesk.dll
(available within the hw-pci-w2k.zip file). Depending on when we last released the software package, this
file may or may not be automatically installed to the folders excBorland and excMSVisual.
If your application opens the DLLs from a different folder, then place the 32bit frontdesk.dll in folder
C:\Windows\SysWOW64.
a) The 64-bit version of Frontdesk.dll is automatically installed (to c:\windows\system32) when you
install the 64-bit version of the Excalibur (kernel) device driver.
b) No.
c) Not the 64-bit version of Frontdesk.dll. But see the next question!
d) YES. But you only need the copy of 32-bit frontdesk.dll when you run your application under 64-
bit Windows. The 32-bit version of Frontdesk.dll should be placed in the same directory as the 32-bit
application (.exe) directory.
e) It is bundled with the 32-bit Excalibur Software Tools (kernel) device driver. It can be found at
http://www.mil-1553.com/kernel-drivers , filename hw-pci-w2k.zip.
f) Yes. In older versions of various Excalibur Software Tools, there was a problem that prevented
frontdesk.dll from being loaded for users' Unicode applications, but this bug was fixed a few years
ago.
We need to check a number of things:
Device Manager, card is listed properly; that is, the hardware driver was installed
from the hardware installation disk
Check that Showhex sees the card, and in bank 4 it sees the installed modules
(Start > Programs > Excalibur > Showhex)
If card is PCIe, verify that you have connected the SATA power cable to the
power supply; otherwise, the modules will not be recognized, since they are not
getting enough power
Note that the default device number for the card is 25; use ExcConfig to assign a
different (additional) device number to the card, e.g., number 0
Verify the device number that the application expects to use; perhaps the
application expects device number 0, or some other number, and it has not yet
been assigned in ExcConfig
If you are running a 32bit application on 64bit Windows, verify that the 32bit
frontdesk.dll is in the EXE folder along with the necessary 32bit DLLs
Additional FAQ to see: “Driver Support for Various Windows Operating Systems - 64bit
Windows and running a 32bit EXE” at URL http://www.mil-1553.com/faqs .
Yes, all of our current products are supported under Windows operating systems,
including Windows 10, Windows 8, Windows 7.
Hardware drivers – Use the same ones as for Windows XP.
Software drivers – Use the same ones as for Windows XP.
Please see our FAQ titled “Where can I find Software drivers on this website” at
www.mil-1553.com/faqs , to determine where the drivers are found.
Please see our FAQ titled “Driver Support for Various Windows Operating Systems -
64bit Windows and running a 32bit EXE”, available for download in our FAQs section of
our website, at www.mil-1553.com/faqs .
This document explains which hardware driver & which software driver combination to
install for use on your current Windows (32bit and 64bit).
Before working with EXC-4000VME/VXI boards, you must verify that there is enough
memory (user window size) on the VME/VXI machine for the board (8 MB). If there is
not enough memory, the board may not work properly.
Verifying User Window Size for Windows NT/2000/XP/Vista/7/8
1. Install NI-VXI_VISA Tools for PCI Based MXI-2 for Windows NT/2000/XP/Vista/7/8
2. Select Start | Programs | National Instruments | Measurements & Automation.
The Measurements & Automation Explorer main screen is displayed.
3. Under Configuration, double-click Devices and Interfaces. All devices and
interfaces are displayed.
4. Right-click on VXI Systems 0 (PCI-MXI-2), and select Hardware Configuration. The
Settings for PCI-MXI-2 dialog box is displayed.
5. Click the PCI tab.
6. In the User window size field, select 8 MB.
7. Click OK.
8. Reboot your Computer.
The default installation folder is “C:\ Excalibur\ProductName Software Tools” (older installations may place the files
in “C:\Program Files\Excalibur\ProductName Software Tools”).
The root folder contains all source code files (*.c, *.h) used in building the Windows DLL, including:
• file proto_xxx.h contains the prototypes for all API functions
• file flags_xxx.h contains flags used in the software tools
• file errors_xxx.h contains error codes (function return values) used in the software tools
• file RevisionHistory.txt contains a listing of the changes made to the software package, by revision number
(for older product releases, this file was named readme.rev)
Folder DemoSource contains source code of demo programs – programs that demonstrate the use of some of the
functions of the API. The name of the program gives a hint as to what it does: demo_xxx.c where “xxx” is the
descriptive name. There is usually a comment at the top of the source code describing what the program actually
does.
Folder excMSVisual (or folder bin) contains a project workspace (.dsw for VS 6) or solution (.sln for VS 2008) for the
DLL, the resultant DLL & LIB files; and project workspaces or solutions for some of the demo programs, and resultant
EXEs. The project workspaces are compiled using Microsoft Visual C++ 6; the solutions are compiled using Microsoft
Visual Studio 2008.
Folder excBorland contains a project workspace (.ide) for the DLL, the resultant DLL & LIB files, and resultant EXEs;
and project workspaces for some of the demo programs. These are compiled using Borland C++ 5. For newer
products, this folder may not exist. For 64bits, we do not supply a Borland compiled DLL.
Folder Manuals (newer installation packages) contains the manuals (software & hardware) for this card & module.
Folder Utilities (newer installation packages) contains various utility programs available for the card, including
ExcConfig and Showhex.
Older installation packages: Instead of the Utilities folder, there may be two additional files in the installation:
• ExcConfig – Excalibur Configuration utility, which is used to assign a device number to your Excalibur board,
for use in all applications (as a parameter to function Init_Module_xxx).
• Showhex – Memory Display Utility, which displays the module / board / card memory in hexadecimal.
Shortcuts to the demo programs are found at: Start | Programs | Excalibur | ProductName.
GUI programs: There may be an additional folder with a GUI program for this product.
1. For Windows 7: We have seen this error message when the operating system is not up to
date.
The solution is to install *all* Windows updates for this version of the operating system (64bit
Windows 7). In our experience, once Windows performs all of the system updates, either (a)
the driver is automatically recognized by the Device Manager, or (b) you should be able to
select the option to "Update Driver" for the card, and point it to the latest kernel driver
(hardware installation disk), as available on our software installation CD, or on our website at
URL https://www.mil-1553.com/kernel-drivers .
2. For Windows 10, the problem may be related to drivers that comply with the "Secure Boot"
requirement.
In this case, you can download the appropriate kernel driver from our website, at URL
https://www.mil-1553.com/kernel-drivers , filename hw-pci-winx64-Secure-Boot-Win10.zip
(PCI Hardware Installation for Windows 64 Bit Secure Boot).
The regular 64bit kernel driver (non-Secure Boot) is filename hw-pci-winx64.zip at this same
URL.
3. Alternatively, some websites suggest methods How to Disable Driver Signature Enforcement in Windows.
(a) assign a device number to the board
(b) call function Init_Module_XXX to get a handle to the specific module on the board
In order to access the modules on the Excalibur board (to call API functions on the
module), you must first call function Init_Module_XXX (where XXX is replaced by a
few letters that represent the protocol being used). The function Init_Module_XXX
takes two parameters: device number (a number associated with the base board),
module number (the position of the module on the board, 0,1,2,3, etc.).
• NOTE: The association of a device number is with the board, not with the modules.
For PCI[e] boards, the dip switch (SW1) setting of the board is the device number (a
number from 0-15).
• NOTE: If you have only one PCI[e] board in your computer, you may use default
device number 25.
For UNET family boards, you will need to modify the file ExcaliburDevices.ini that is
found in the root folder of your software tools.
Each section in the .ini file has a heading [DEVnumber]. Replace "number" with the
desired device number.
Follow the instructions at the top of the file, and the given examples, to set up the
parameters for your UNET family board.
This ExcaliburDevices.ini file must reside in the /etc directory. Note that this will
require root privileges.
(a) assign a device number to the board
(b) call function Init_Module_XXX to get a handle to the specific module on the board
In order to access the modules on the Excalibur board (to call API functions on the
module), you must first call function Init_Module_XXX (where XXX is replaced by a
few letters that represent the protocol being used). The function Init_Module_XXX
takes two parameters: device number (a number associated with the base board),
module number (the position of the module on the board, 0,1,2,3, etc.).
• NOTE: The association of a device number is with the board, not with the modules.
Under Windows, the device number is assigned using the ExcConfig utility. This
applies to all boards, PCI[e] based, or UNET family. Run ExcConfig to associate a
device number (0–15) with a board type and the board’s Unique ID.
Double-click on some row in the grid - corresponding to the device number (0-15)
listed in the leftmost column.
On the inner screen, click on the desired board type from the list on the left.
For PCI[e] boards, select a Unique ID which corresponds to the dip switch (SW1)
setting of the board.
• NOTE: If you have only one PCI[e] board in your computer, you may use default
device number 25, without listing the board in ExcConfig.
For UNET family boards, select the Connection Type by clicking on the radio button
that corresponds to either USB connection or Ethernet connection.
The API for the modules that sit on the UNET series cards (UNET, UNET2) is the same
as the API for modules that sit on the 4000 series cards (4000-2000-8000).
The current released software installation package for each module will work on all
the cards – 4000 series families, UNET series families.
It is necessary to replace the old dlls that you have used previously, with a full set of
new dlls that will work for both card families. The dlls are found starting at the
following paths (example is generic, for some protocol):
C:\Excalibur\Protocol Software Tools\Source\lib\excMSVisual
Then, open folder Win32 for 32bit dlls, or x64 for 64bit dlls.
Then, open folder Debug or Release, depending on the compiler option you are using.
In this folder you will find DLL and LIB files that you should use when compiling or
running your application. Copy the DLLs to the folder where your EXE sits, or to folder
C:\Windows\SysWOW64.
We now have drivers that fulfill this requirement.
They can be downloaded as filename hw-pci-winx64-Secure-BootWin10.zip at URL http://www.mil-1553.com/kernel-drivers .
This is the hardware installation disk to be used in the Device Manager, to
install a driver for the Excalibur PCI or PCIe card. In addition, you need to
install software drivers for the individual modules on the card.
Please see our FAQ titled “Driver Support for Various Windows Operating
Systems - 64bit Windows and running a 32bit EXE” at URL http://www.mil-1553.com/faqs.