gray banner Diffraction International logo Durango logo

Durango Hardware Interface Modules

Hardware Independence

Durango is fully hardware independent in that hardware specific code is contained in separate dynamic link libraries. We can add support for additional hardware without modifying the application code.

Durango hardware interface modules must be present in the Durango installation directory at startup. Durango first checks for a hardware key to determine if this is a commercial license (hardware capable) installation. If so, Durango attempts to start the hardware driver associated with each installed interface module and reports results to the file durango.log. Modules that are started successfully will be available in the hardware configuration dialog boxes.

In general, it is necessary to first install and configure the appropriate drivers as supplied by the hardware manufacturer. These drivers will typically be located in the system directories or in a hardware specific directory. If Durango fails to recognize or initialize supported hardware that you have installed, first try running the manufacturer’s supplied configuration and diagnostic software or demo software to verify that the manufacturer’s driver is installed, configured and working properly. If the problem persists, examine the text file durango.log for diagnostic information. This file is located in the Durango installation directory and is rewritten every time you start Durango. If you need to contact Diffraction International about a hardware problem, please include a copy of durango.log.

Hardware Interface Modules

Diffraction International has developed several Durango hardware interface modules to date. The currently available modules are listed in the following tables. We recommend the National Instruments IMAQ boards for use on a desktop machine, and the ImperX VCE for video on a laptop. For driving our Fizeau Phase Shifter, our PZT Linear Stage or your own phase shifter, we recommend any of the National Instruments DAQ devices that support at least one analog out channel. If your required drive voltage exceeds 10 V, a voltage amplifier must be added between the NIDAQ board and the PZT.

Hardware Interface Modules
Module 98 NT 2K XP Supported Hardware Interface Connects to:
4D Technology PhaseCam Yes Yes Yes Yes PhaseCam Software PhaseCam
Electrim/Fisba µPhase Yes N/A N/A N/A EDC-1000 ISA EDC-1000, Fisba µPhase
EPIX Yes Yes N/A   PixCI-D PCI Digital RS-422
PixCI-SV4 PCI Video RS-170 and CCIR
Imaging Technologies N/A Yes N/A   IC-PCI w/ AMDIG-8D-HS PCI Digital RS-422
ImperX VCE Yes Yes Yes Yes ImperX VCE PCMCIA Video RS-170 and CCIR
iREZ USB Live Yes N/A Yes Yes USB Live! USB-1 Video RS-170 and CCIR
Matrox Meteor II N/A Yes Yes   Meteor-II PCI Video RS-170 and CCIR
National Instruments IMAQ Yes Yes Yes Yes IMAQ PCI-1409/1408 PCI Video RS-170 and CCIR
IMAQ PCI-1407 PCI Video RS-170 and CCIR
IMAQ PCI-1422 PCI Digital RS-422 OR LVDS
IMAQ PCI-1428 PCI Digital Camera Link
National Instruments NI-DAQ Yes Yes Yes Yes PCI-6024E PCI  
DAQCard-6024E PCMCIA
AT-MIO-16E-10 ISA
Lab-PC+ ISA
DAQCard-AO-2DC PCMCIA
Promet International FiBO N/A N/A Yes Yes FiBO Interferometer USB 2.0  
Serial Port Yes Yes Yes Yes   RS-232  

Custom Hardware Interface Modules

If you require a Durango interface module for hardware that is not listed, please let us know. In general, we can develop Durango modules for any hardware for which the manufacturer provides a Windows driver and SDK. We may ask to borrow your hardware for testing. If your hardware is standard equipment with a commercial interferometer, there will be no charge for developing the custom module.

We can also modify our current Durango hardware interface modules to support additional features of the hardware. Let us review your requirements.