25-03-2021

Download Carnegie Mellon University 1394 Driver

In the tabs below, select your interferometer camera interface type. In the Filter Options at left, mark checkboxes to select only those expansion slots and/or ports that are open and available on your computer. For help in identifying a slot or port, click on its checkbox label.

When installation is finished, verify in the driver tab that the provider is 'Carnegie Mellon University' and that the version is '6.4.0.108'. Also verify that your camera is now listed in the device manager as 'CMU 1394 Digital Camera Device'. Find Carnegie Mellon University software downloads at CNET Download.com, the most comprehensive source for safe, trusted, and spyware-free downloads on the Web.

At the bottom of this page is additional information about device drivers.

Carnegie Mellon University Majors

UniversityAnalog1394a1394bUSB 2.0CameraLinkGigE

National Instruments PCI-8252

The PCI-8252 ships with National Instruments Vision Acquisition Software.

Rosewill RC-504

The Rosewill RC-504 PCIe adapter card adds 2 external Firewire 1394a (400 Mbps) ports to your computer. Requires an open PCI Express 1-lane(x1) port. No drivers to install.

StarTech PCI Express 1394 FireWire Adapter Card

The StarTech PEX1394B3 adds two IEEE 1394b FireWire 800 ports and one IEEE 1394a FireWire 400 port. Works without any additional drivers.

FireWire 400 to FireWire 400

To connect a FireWire 400 (1394a) camera to a FireWire 400 port, you will typically need a 6-pin FireWire cable.

Laptop FireWire ports are typically 4-pin and do not provide power to the camera. This is resolved with a 6-pin to 4-pin Y-cable and power supply.

You will also need camera device driver software. Durango supports the National Instruments Vision Acquisition Software and the Carnegie Mellon University CMU 1394 drivers.

FireWire 400 to FireWire 800

To connect a FireWire 400 (1394a) camera to a FireWire 800 (1394B) port, you will need a 6-pin to 9-pin FireWire cable.

You will also need camera device driver software. For FireWire cameras, Durango supports the National Instruments Vision Acquisition Software and the Carnegie Mellon University CMU 1394 drivers.

1394

Device Drivers

Carnegie Mellon Library

National Instruments Vision Acquisition Software

For many camera interface options, Durango requires National Instruments Vision Acquisition Software (NI-VAS). NI-VAS may be downloaded for a trial evaluation.

CMU 1394 Drivers

The free CMU 1394 drivers from Carnegie Mellon University are supported by Durango and are compatible with a wide range of digital cameras under Windows XP. We look forward to these drivers being someday available for Windows 7.

Imaging Source IC Capture

This software is included free of charge with all cameras, converters and grabbers manufactured by The Imaging Source.

Basler Pylon Driver / SDK

Operates with all Basler cameras that have an IEEE 1394a, IEEE 1994b or GigE Vision interface. Internal architecture is based on GenICam. Durango does not yet support the Pylon drivers.

The current official release of the driver is 6.4.6, released on September 26, 2011 by Christopher R. Bakercbaker+iwan1394@cs.cmu.edu.
After more than a year of wrestling with the nuances of Microsoft's 64-bit operating systems, and with no small quantity of assistance from a few brave testers (you know who you are!), I am proud to officially release this next version of the CMU 1394 Digital Camera Driver, which includes:

Carnegie Mellon University Andrew Carnegie

Home
  • Support for all present 64-bit versions of Microsoft Windows XP, Vista and 7, allowing both native (64-bit) and emulated (32-bit) applications to access camera data via a single driver interface.
  • A completely new demo application, written from the ground up to support both 32-bit and 64-bit Windows.
  • A litany of bugfixes, many of which were contributed by individual users (for which I am grateful!), including:
    • Squashment of the nefarious BSOD on resume-from-suspend bug
    • A closer-to-correct implementation of the Serial I/O functionality described in the IIDC 1.31 standard (closer = still a little quirky, but the quirks may be in the camera I am testing with)
    • Verified Strobe and Parallel I/O functionality (Strobe controls are also now integrated into the same dialog as Gain, Zoom, Focus, etc.)
    • .. and many others
  • New since the public beta:
    • Fully automated driver installation on 64-bit systems
    • Several minor bugfixes and documentation updates, but nothing that alters the API/ABI

Update: digital signatures for all kernel-mode software

All 64-bit versions of windows require a digital signature via an AuthentiCode certificate in order to run kernel-mode software. I would like to thank MathWorks for providing the funding for this certificate and allowing this driver set to continue to be published freely to the general public. MathWorks provides an adapter to the CMU 1394 Digital Camera driver as part of their Image Acquisition Toolkit to allow developers quick and easy access to images from firewire cameras within the MATLAB environment.

Carnegie Mellon Football

Known issues and limitations

Download Carnegie Mellon University 1394 Driver License

  • Large-block asynchronous transfers. I have received several requests and offerance of patches that restore the ability to issue large asychronous I/O (i.e., larger than a single quadlet/register) requests to cameras. I am evaluating these and trying to fold them into the driver in a manner that supports 64-bit platforms.
  • Mysterious BSOD when using multiple 1394b cameras on the same bus under Windows 7. In experimenting with various configurations of cameras, 1394b host controllers, and driver settings, I have occasionally triggered inexplicable kernel panics while performing comparatively simple operations. Whether this is a quirk of the new Microsoft 1394 bus driver, of some particular host controller, of the 1394 camera driver's innards, or, most likely, of some combination thereof, remains to be seen. Using a single 1394b camera on a single bus is quite stable, however, and the circumstances where multiple cameras trigger this problem seem rare.
  • The usual assortment of bugs and quirks. Much of the frame-handling logic had to be altered to accommodate the curious limitations of DMA transfers on 64-bit systems. Although I have been unit-testing this code to the greatest extent possible, my experience is that no new code is completely bug-free. My thanks go out to the many beta testers who have helped me to this point, and further comments/questions/bug reports/etc. are especially welcome on this front.