Skip to content

Add EmergentCamera device adapter - #1032

Open
VolodymyrCherkas wants to merge 3 commits into
micro-manager:mainfrom
VolodymyrCherkas:add-emergent-camera
Open

VolodymyrCherkas wants to merge 3 commits into
micro-manager:mainfrom
VolodymyrCherkas:add-emergent-camera

Conversation

@VolodymyrCherkas

@VolodymyrCherkas VolodymyrCherkas commented Nov 6, 2026 •

Copy link
Copy Markdown

Adds an eSDK-based adapter for Emergent monochrome GigE cameras. It supports camera discovery, Snap/Live/sequences, hardware ROI/binning, Mono8/10/12, exposure/gain controls, trigger/GPIO configuration and PTP.

The adapter exposes camera parameters as Micro-Manager properties.

Build and dependencies

The change is confined to DeviceAdapters/EmergentCamera/: two C++ implementation files, one header, the Windows Visual Studio project/filter files and one BSD-3-Clause license. Emergent SDK headers and libraries must be installed separately from the manufacturer.

For Windows x64, use Visual Studio 2022/v143 C++ tools. From the mmCoreAndDevices root:

msbuild DeviceAdapters\EmergentCamera\EmergentCamera.vcxproj /m /p:Configuration=Release /p:Platform=x64

The configurable ESDK_ROOT property defaults to the vendor installation directory, C:\Program Files\EVT\eSDK. Repository-wide build registration is outside this adapter-only change.

Validation

  • Windows tests were performed in Windows 11 26H2, used Emergent HE-25000SBL-T-M with firmware 3.35 and eSDK 4.08.06/4.08.02. Acquisition and main camera settings were tested and are operational. PTP master lock/accuracy and physical GPIO timing remain untested.
  • Linux x86_64 source cross-compilation against Ubuntu 24.04/eSDK 4.08.05 passes. No hardware tests were performed in Linux.
  • macOS is not supported.
  • color cameras not tested.

@marktsuchida

Copy link
Copy Markdown
Member

Thanks for the PR!

Can you remove all binaries (they don't belong in the repo) and duplicate licenses, as well as CMake files (which we don't use)? Also remove the .gitattributes file; we handle newlines by using the default Git for Windows settings which work without this (LF in the repo, CRLF in worktree text files on Windows).

Why are test results saved in the tree? Are the tests testing the SDK or the adapter or both? The Windows run-tests.ps1 hard-codes various paths. This suggests that it is for your dev env, not something appropriate for this shared repo.

What are the INI files for? Are they something the camera vendor requires to operate the device? If not, it would seem like something the application layer should handle and not be part of a device adapter.

Statements like "The adapter directory was renamed from Emergent to EmergentCamera." suggest that some of the notes are leftover from previous steps and not relevant to the code as it stands.

Could you (not (just) your LLM) go through and review all the files and make sure that they are aimed at a human reader and are set up for maintenance over time and also do not include any unnecessary/excessive material? Then I'll be happy to actually review the code and build files.

@VolodymyrCherkas

Copy link
Copy Markdown
Author

Dear Mark, thank you very much for your constructive feedback!

I have cleaned it up, removed .ini configurations, recompiled and tested it is operational under Windows 11.
Original .ini idea was implemented to automate camera settings handling, as with presets it is not very intuitive how to save all camera settings and reuse them next time. Removed this feature to avoid confusion and redundant features.

I have checked it after the LLM and it looks much cleaner now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants