emScope is part of the World Wide Laboratory Project being undertaken by the Beckman Institute Imaging Technology Group. Through this project we are providing specifications for the remote control of an electron microscope over the Internet. We are also providing a sample implementation for the Philips CM200 Transmission Electron Microscope..

We are currently distributing the core libraries and some sample applications for controlling a Philips CM200 Transmission Electron Microscope. There is currently a severe lack of documentation and the routines for filling in the instrumental calibration tables are missing. See the INSTALL.README file for notes.

This is a snapshot of the core libraries of emscope and some sample applications. Over time I hope to increase the number of applications and amount of documentation available. The problem is a lot of our projects are a work in progress so it is difficult to find time to prepare them even for snapshot releases.


INSTALL.README for b2 software - Installation notes for the B2 emscope distributions

INSTALL.README for b6 software - Installation notes for the B6 emscope distributions

DM-RemoteScripter.sea - MacOS (PowerPC) Digital Micrograph "Remote Scripter" Plugin

emscope-1.0b3-src.tar (fixed b2 release, source only) - Source code distribution of emScope

emscope-1.0b6-src.tar.Z (b6 release, source only) - Source code distribution of emScope

jpegsrc.v6a.tar - Source distribution of IJG JPEG library

emc-api.doc - Microsoft Word Document. Documentation for libemCM200.a library

emc-concepts.doc - Microsoft Word Document. General concepts behind emScope project

Note that the documentation does not precisely match the libraries implemented here. The documentation is a version or two *ahead* of what has actually been implemented. The most trivial difference is that all functions in the documentation begin with "emc" while the actual functions begin with "em". Also all emcCamera functions don't have a camera ID parameter yet. So one really needs to look at the source code to know what's happening. A future release will update the libraries to more closely match the documentation.