You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The service for AlliedVision cameras written #133 is ready uses the Vimba driver. Allied Vision recently released a new driver, called VimbaX.
Eventually, and probably not in the foreseeable future, we will want to test the service compatibility with the VimbaX driver and the respective new Python package, VmbPy: https://github.com/alliedvision/VmbPy/
(as opposed to the Python package used for Vimba, which is VimbaPython: https://github.com/alliedvision/VimbaPython)
So, the main goal of this issue is to rewrite the AlliedVisionCamera service to use VmbPy with VimbaX.
The service for AlliedVision cameras written #133 is ready uses the Vimba driver. Allied Vision recently released a new driver, called VimbaX.
Eventually, and probably not in the foreseeable future, we will want to test the service compatibility with the VimbaX driver and the respective new Python package, VmbPy: https://github.com/alliedvision/VmbPy/
(as opposed to the Python package used for Vimba, which is VimbaPython: https://github.com/alliedvision/VimbaPython)
So, the main goal of this issue is to rewrite the AlliedVisionCamera service to use VmbPy with VimbaX.
The Python API seems to be exactly the same, so it could just mean having the hardware service check which driver is installed and using the correct package accordingly. In particular:
https://github.com/alliedvision/VmbPy#differences-to-vimbapython
Full Python API manual:
https://docs.alliedvision.com/Vimba_X/Vimba_X_DeveloperGuide/pythonAPIManual.html
There's also a migration guide:
https://docs.alliedvision.com/Vimba_X/Vimba_X_DeveloperGuide/migrationGuide.html#migration-from-vimba
Python examples with Vimba X:
https://docs.alliedvision.com/Vimba_X/Vimba_X_DeveloperGuide/examplesOverview.html#vmbpy-examples
All info about VimbaX and Vimba:
https://docs.alliedvision.com/
The text was updated successfully, but these errors were encountered: