Manuals

eMorpho-HP - Embedded Digital MCA

This section is devoted to the software that accompanies and supports the eMorpho. A brief performance data sheet can be found here (pdf)

Software strategy

The goal of the software we provide is to put you in the driver's seat and give you all the tools necessary to develop your own.

Getting started

You can operate the eMorpho using our graphics user interface written in IGOR. This graphical point and click interface gives you access to all of the capabilities of the eMorpho—no programming necessary.

The code for the IGOR GUI is available for free to our customers. Updates are available through a weblink. Unzip into a temporary directory and follow the instructions in the ReadMe.txt file. Note, however, that you do need an IGOR PRO license, version 4 or higher. If you don't own one you can purchase it either through us or directly from WaveMetrics.

Writing your own

We support integrating the eMorpho into your data acqusition system by providing a very simple and well-documented application programmer's interface (API), written. entirely in C. An API programmer's manual and the API source code will be available too.

Generic C-code

The API has been written without using operating system dependent methods as much as that is possible. The most notable exception is calling the USB driver dll, which is the only way to access the USB controller under Windows.

Three-layer code

1. The API uses a single function to physically move data across the USB interface. This is the only function that would need changing when implementing the code on a different operating system.
2. The basic API functions mirror the functionality found in the on-board signal processing FPGA. For every section there is a read and write function, which is all that is needed to operate the eMorpho. A few wrapper functions are provided that help with filling in the various bitfields and registers to accomplish certain tasks, such as starting data acquisition or setting the high voltage on an attached power base.
3. For convenience, we provide a unified command interface. This is a single function through which all other functions of the API can be called. This mechanism is helpful when integrating the API with user code. Only one function needs to be exported.