HIKROBOT · MVS
MVS acquisition, triggering, parameters, data recording and unified SDK adaptation
- Integration Prerequisites
- Camera model, SDK, interface and target system
For Equipment Manufacturers and Enterprise R&D Teams
Branded Vision Device SDK and System Integration Development
Develop image or point-cloud acquisition, parameter controls, application software, unified SDKs and system integrations using the interfaces exposed for a specific device model.
Determine development scope based on device model and open interfaces
The following manufacturers provide development documentation that can support a model-specific integration assessment. These references do not imply that JIVISION has integrated every model or holds agency, certification or partnership status.
Basler · pylon
pylon acquisition, parameters, events, data processing and device applications
- Integration Prerequisites
- Specify camera, SDK components and target system
Allied Vision · Vimba X
Vimba X collection, feature control, status notification and application packaging
- Integration Prerequisites
- Model, transport layer and version
Teledyne IIS · Spinnaker
Spinnaker acquisition, triggering, camera control and industrial applications
- Integration Prerequisites
- Supported industrial camera models; FLIR thermal imaging products are not covered by this
IDS · IDS peak
IDS peak acquisition, configuration, image processing and terminal adaptation
- Integration Prerequisites
- Model, transport layer and operating platform
LUCID · Arena
Arena acquisition, parametric, depth or polarization data and application software
- Integration Prerequisites
- Specified models and their available features
Baumer · neoAPI
neoAPI acquisition, parameter control, multi-camera and terminal adaptation
- Integration Prerequisites
- Camera, interface, operating system and SDK
JAI · eBUS SDK for JAI
eBUS SDK for JAI acquisition, control and device applications
- Integration Prerequisites
- JAI supports models and corresponding software; it is not regarded as a general eBUS authorization
Euresys · eGrabber
eGrabber buffering, events, acquisition chain and device integration
- Integration Prerequisites
- Card type, firmware, driver and camera link
Zivid · Zivid SDK
Zivid SDK acquisition, point cloud, robot coordinates and application packaging
- Integration Prerequisites
- Camera, SDK, working distance and artifact
Photoneo · PhoXi
PhoXi interface, point cloud acquisition, parameters, reconstruction and robotic applications
- Integration Prerequisites
- Sensors, control software and interface versions
Mech-Mind · Mech-Eye SDK
Mech-Eye SDK acquisition, point cloud and device application adaptation
- Integration Prerequisites
- Camera, SDK and required software licenses
Orbbec · Orbbec SDK
Orbbec SDK color depth collection, parameters and application packaging
- Integration Prerequisites
- Camera models and corresponding SDK generations
RealSense · RealSense SDK
RealSense SDK acquisition, depth, calibration and robot data interface
- Integration Prerequisites
- Camera, firmware, SDK and target system
Stereolabs · ZED SDK
ZED SDK Stereo Data, Spatial Perception and Embedded Applications
- Integration Prerequisites
- Model, computing platform, SDK and functional conditions
ifm · ifm3d
ifm3d configuration, data collection, in-depth application and robot access
- Integration Prerequisites
- Specific product and library compatibility relationship with firmware
LMI · Gocator
Corresponding to SDK’s contour collection, measurement results, tasks and industrial access
- Integration Prerequisites
- Series, firmware and corresponding SDK system
SICK · Visionary
Official samples and corresponding interfaces, image point cloud collection and application packaging
- Integration Prerequisites
- Specify Visionary model and interface version
Prophesee · Metavision
Metavision event collection, filtering, tracking and terminal applications
- Integration Prerequisites
- Sensor, SDK module and commercial deployment license
Optris · Direct SDK / OTC SDK
Thermal data, control and analysis software for Direct or OTC SDK
- Integration Prerequisites
- Product model and corresponding SDK, radiation data conditions
FLIR · Atlas SDK
Atlas SDK’s heat mapping, control, recording and temperature measurement applications
- Integration Prerequisites
- Specific models and radiation data supported by Atlas
Hamamatsu · DCAM
DCAM-API/SDK acquisition, exposure, triggering and scientific imaging software
- Integration Prerequisites
- Camera, SDK and acquisition interface
Andor · SDK
Acquisition control, data management and instrument application corresponding to SDK
- Integration Prerequisites
- Model, SDK2 or SDK3, platform and license
Thorlabs · OCT SDK
Acquisition, triggering, tomography analysis and instrument software corresponding to OCT SDK
- Integration Prerequisites
- Specify system, SDK permissions and reference samples
DAHENG IMAGING · Galaxy SDK
Galaxy SDK acquisition, triggering, parameters and embedded adaptation
- Integration Prerequisites
- Model, SDK platform package and interface
MindVision · Camera SDK
Manufacturer SDK collection, control, image recording and platform application
- Integration Prerequisites
- Model, SDK, system and interface
Cognex · In-Sight SDK
In-Sight SDK host computer, task, image and result integration
- Integration Prerequisites
- SDK supports models; does not modify the underlying firmware of the device by default
KEYENCE · CV-X
Corresponds to ActiveX or communication interface control, image result collection and host computer
- Integration Prerequisites
- Controller models, software licenses and open interfaces
Raytrix · Light Field SDK
Light Field SDK acquisition, refocusing or 3D interface and application
- Integration Prerequisites
- Camera, SDK, computing platform and licensing
HOLOEYE · SLM Display SDK
SLM Display SDK image phase data transmission and experimental system linkage
- Integration Prerequisites
- Finished SLM and customer’s existing optical machine; does not include emission optical path research and development
Compatibility Scope and Interface Verification
Maintain a compatibility matrix covering manufacturer, model, firmware, SDK, operating system and interface. Verify acquisition, control, recovery and outputs for each supported configuration. The availability of manufacturer documentation does not establish that a device integration has been completed.
| Verification link | Confirm content |
|---|---|
| Equipment and software portfolio | Brand, model, firmware, SDK, driver, operating system and interface |
| Acquisition and Parameters | Data format, trigger, exposure, depth or radiometric data and accessible parameters |
| Exceptions and deployment | Broken link recovery, caching, concurrency, installation distribution and commercial deployment license |
| deliver | Adaptation code, interface description, configuration, examples, compatibility table and test records |
Other Manufacturers and Unlisted Models
Please submit model number, official protocol or SDK, firmware version, target system and prototype conditions. For devices that do not have clear open interfaces, verify the information and authorization first, and then determine the collection, control or system integration work.
Responsibilities and Deliverables
| Development Stage | Deliverables | Items to Confirm |
|---|---|---|
| Requirements and system interfaces | Equipment tasks, inputs and outputs, interfaces and test requirements | Scope of responsibility for customer's existing systems and supplier components |
| Design and software development | Agreed circuitry, structure, firmware, algorithm or application | Actual design scope, source file rights and third-party licenses |
| Prototype and engineering joint debugging | Agreed configured prototype, parameters, construction and installation information | Number of prototypes, institutional conditions and on-site joint debugging arrangements |
| Validation and technical handover | Configuration list, test records, problem handling and usage instructions | Reference methods, judgment standards and subsequent maintenance scope |
Verification and Acceptance
Maintain a compatibility matrix covering manufacturer, model, firmware, SDK, operating system and interface. Verify acquisition, control, recovery and outputs for each supported configuration. The availability of manufacturer documentation does not establish that a device integration has been completed.
Define the samples, target configuration, reference values, operating conditions and acceptance method before testing. Retain normal results, failure cases, version information, known limitations and retest records in the delivery documentation.
Enterprise Project Questions
Can I modify the underlying firmware of any brand of device?
Firmware modification requires source access, development interfaces and permission from the manufacturer. Where only a host SDK or communication protocol is available, development is limited to the functions exposed by that interface.
Can different models of the same brand directly share the adaptation results?
Results from one model cannot be directly extended to the full range. Sensor data, firmware, SDK, interfaces and operating platforms need to be verified and the actual test combination documented in the support checklist.
How does a unified SDK handle differences between device manufacturers?
Provide common acquisition, status and result interfaces while retaining capability queries and manufacturer extensions. A software wrapper cannot add a function that the device hardware does not provide.
Project Enquiry
xuzhiyang0928@gmail.com
Provide Equipment and Sample Information to Define the Development Scope
Branded Vision Device SDK and System Integration Development
Please describe the purpose of the equipment, existing systems, cameras and interfaces, target output, reference samples, prototype quantity and design data delivery requirements.
Phone: 13910119357xuzhiyang0928@gmail.com