Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
unmigratedcomposition-wiki-markupsetup

Ephus and ScanImage interface to a growing range of hardware devices. Frequently, custom software interfaces to these devices must be developed, allowing their capabilities to be accessed via scripting in Matlab.

Such device interfaces are developed as part of a growing Matlab package of devices classes called Dabs. (See list below.) The current version of this package is included with all recent and planned releases of ScanImage.

Some users may find some of these device interfaces useful in and of themselves – i.e. as a Matlab object-oriented scripting interface for these devices. Note that the interfaces are provided as-is and their distribution/maintenance is not presently a primary aim of the ScanImage/Ephus projects. (Any issues affecting ScanImage/Ephus operation, however, should be brought to the developers' attention (mailto:iyerv@janelia.hhmi.org?subject=\[ScanImage/Ephus Feedback\]).)

Tip
titleHelp Wanted!

User-contributions to the Dabs package are encouraged and welcomed, as they may be of general benefit to the community. In some cases, abstract superclasses are included in the Dabs package to facilitate the development of device interfaces to a common standard. For instance a Linear Stage Controller superclass has been developed. Users can create custom subclasses for their particular stage controllers, allowing ScanImage to operate with these devices.

Please let us know (mailto:iyerv@janelia.hhmi.org?subject=\[ScanImage/Ephus Feedback\]) if you develop a device interface class, or package of classes, so we may include it in a future release.

Note that Ephus makes use of two earlier-style Matlab device interfaces: NiMex and QCamMex.

Toggle Cloak
idDabsList
List of Current Dabs Classes (& Packages)
Cloak
idDabsList
  • dabs.andor.AndorCamera
  • dabs.coherent.Chameleon
  • dabs.coolled.PE
  • dabs.newport.XPS
  • dabs.ni.daqmx (package)
  • dabs.pi.(E517/E712/E753/E816)
  • dabs.piezojena.DDrive
  • dabs.prior.PriorStage
  • dabs.qimaging.QCam
  • dabs.scientifica.LinearStageController
  • dabs.sutter.(MPC200/MP285)
  • dabs.thorlabs.LSM
{toc:type=flat|maxLevel=2} h2. QCamMex QCamMex is a C-language interface to QCam drivers that are exposed for users to control all QImaging CCD cameras. This provides an alternative to the QCapture Suite provided by the QIMAGING. The preferred method of acquiring QCAM (in binary form) is as a part of Ephus, but it can also be downloaded independently below. The runtime requires [SvobodaLab:QCam SDK|ScanImage, Ephus, and other DAQ software, EPHUS r^QCamSDK2005.exe] and [SvobodaLab:QCam Driver|ScanImage, Ephus, and other DAQ software, EPHUS r^QCamDriver2005.exe]. h5. Release History || Release Notes \\ || Release Date \\ || Installer \\ || Source/Dev Kit \\ || SVN URL || Summary \\ || | [QCamMex R0.2 - beta|Release note for qcammex_R0.2_Beta.zip] \\ | 05/15/2008 | [SvobodaLab:qcammex_R0.2_Beta.zip |ScanImage, Ephus, and other DAQ software, EPHUS r^qcammex_R0.2_Beta.zip] \\ | [ScanImage, Ephus, and other DAQ software, EPHUS r^QCamMex_R0.2_SRC_Beta.zip] \\ | [Copy Me|https://svn.janelia.org/svobodalab/software/distribution/branches/jinyang_main/svobodalab/Programs/Qcam] \\ | Beta release of QCAM R0.2 \\ | h5. How to Install: # Download qcammex_R0.2_Beta.zip (from table above) and dependencies QCam_SDK and QCam Driver. # Install QCam SDK (The password to the SDK is 'easy imaging' without quotes) and QCam Driver. # Create a new folder, QCam, in ...\svobodalab\Programs and unzip qcammex_R0.2_Beta.zip to the folder ...\svobodalab\Programs\QCam,  # Run startQCam in Matlab. h5. Documentation *  [QCam Documentation] h2. NIMEX NIMEX is a C-language interface to National Instruments NIDAQmx data acquisition drivers that are exposed for use as objects in MATLAB (@nimex/@daqjob). This provides an alternative to the objects provided by the Matlab Data Acquisition toolbox, which have several functional limitations. The preferred method of acquiring Nimex (in binary form) is as a part of Ephus, but it can also be downloaded independently below. The runtime requires [NIDAQmx 8.5(.0f5 or better)|http://www.ni.com/dataacquisition/nidaqmx.htm] and the [GTK Runtime|http://gladewin32.sourceforge.net/modules/wfdownloads/visit.php?lid=111]. h5. Release History {report-table} {content-reporter:scope=Home> children|type=page} {text-filter:content:title|include=.*NIMEX r.*} {text-sort:content:title|mode=exact|order=descending} {content-reporter} {report-column:title=Release Notes} {report-info:content:title|link=true}{report-column} {report-column:title=Release Date} {report-info:data:ReleaseDate|format= dd MMM yyyy} {report-column} {report-column:title=Installer}{report-info:data:Installer|link=true}{report-column} {report-column:title=Source/Dev Kit}{report-info:data:SourceInstaller|link=true}{report-column} {report-column:title=SVN URL} {report-link:data:SVNURL}Copy Me{report-link} {report-column} {report-column:title=Summary|width=500px}{report-info:data:ReleaseSummary} {report-column} {report-table} (Developers: Submit a {create-page:boilerplate=ReleaseNotes|parent=@self|prompt=Enter Release Number (e.g. 1.0.0)|prefix=NIMEX r|addspace=false|target=editscaffold}new release {create-page}) h5. Documentation *  [Legacy Documentation|(DOC) NIMEX Legacy Documentation]