| |
|
|
The DCAM-API Internal Structure
|
|

- All Modules are DLL's in Windows. In Mac, they are framework libraries.
- The application's communication with all the installed cameras in the system is done through one entry point - The DCAM-API Library.
- The DCAM-API Library contains all the defined exported functions of the API.
- DCAM-API is responsible for connecting all registered DCAM-API Modules to the host application.
- Basic flow
- Application layer (host) initializes the DCAM-API Library.
- DCAM-API initializes each module and queries how many devices are found.
- Total count is returned back to the host.
Host can open a connection to any of the devices by index.
- Once opened, all communication and data acquisition to that device through its connected interface are handled with the link.
- There is no theoretical limit to how many devices or how many links are opened.
- Allows for simultaneous control/acquisition of multiple devices.
- Dynamic property and image data type querying. Common memory management.
- When done, the connection is closed to each module/device, then the API is cleaned up and closed.
|
 |
|
|
 |
|
|
© Hamamatsu Corporation. Customer privacy is important, please read our
privacy statement.
Send comments/questions about this page
to the webmaster.
|
|