Lima-camera-basler issueshttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues2024-01-29T09:33:46+01:00https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/38lima-core 1.9.242024-01-29T09:33:46+01:00Laurent Claustrelima-core 1.9.24this version of lima-core 1.9.24 fixes issue with _calcStatus for the infinite acquisition + openssl no depsthis version of lima-core 1.9.24 fixes issue with _calcStatus for the infinite acquisition + openssl no depsLaurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/37HwInterface::acqStatus does not manage well mult trigger and detector status2024-01-29T08:56:58+01:00Laurent ClaustreHwInterface::acqStatus does not manage well mult trigger and detector statusWhen trigger mode is set to Ext/InTrigtMulti or ExtGate, the global status does not stay Running but change to Ready when waiting for the next trigger.
There is no management of the status.det version status.acq. To be done.When trigger mode is set to Ext/InTrigtMulti or ExtGate, the global status does not stay Running but change to Ready when waiting for the next trigger.
There is no management of the status.det version status.acq. To be done.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/36scout camera does not support reading of the frame rate range if not enable f...2024-01-19T08:07:56+01:00Laurent Claustrescout camera does not support reading of the frame rate range if not enable firstObserved by Alexander Kessler (Helmholtz Institut Jena) with a Scout scA640-70gm, issue on github (https://github.com/esrf-bliss/Lima-camera-basler/issues/37)Observed by Alexander Kessler (Helmholtz Institut Jena) with a Scout scA640-70gm, issue on github (https://github.com/esrf-bliss/Lima-camera-basler/issues/37)Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/35add tango attribute for reading the effective frame rate2023-10-31T16:31:39+01:00Laurent Claustreadd tango attribute for reading the effective frame rateLaurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/34hw roi does not work for camera with increment >1 on X offset/width2023-10-31T16:31:22+01:00Laurent Claustrehw roi does not work for camera with increment >1 on X offset/widthWith camera model acA1920-50gm the HW ROI increment on X and Width is not 1 bur about 4. checkRoi() seems to manage that feature but the code is has bug and checkRoi does not return the correct HW roi to lima.With camera model acA1920-50gm the HW ROI increment on X and Width is not 1 bur about 4. checkRoi() seems to manage that feature but the code is has bug and checkRoi does not return the correct HW roi to lima.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/33set latency time for changing frame rate is broken2023-09-06T14:52:00+02:00Laurent Claustreset latency time for changing frame rate is brokensince pylon6 port and according to the camera model, the latency_time change break the change of a frame rate in Camera::setExpTime()since pylon6 port and according to the camera model, the latency_time change break the change of a frame rate in Camera::setExpTime()Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/31The "packet_size" parameter is equal to 1000.2023-04-26T10:21:31+02:00Olivier NeveuThe "packet_size" parameter is equal to 1000.Hi,
I think there is a problem with the `packet_size` parameter.
Indeed, after having executed and killed the device server, we can see in `pylonviewer` that the value of this parameter is equal to 1000.
It is consistent with the cont...Hi,
I think there is a problem with the `packet_size` parameter.
Indeed, after having executed and killed the device server, we can see in `pylonviewer` that the value of this parameter is equal to 1000.
It is consistent with the contents of the `Camera` class constructor in the [BaslerCamera.cpp](https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/blob/master/src/BaslerCamera.cpp#L198) file. The parameter `packet_size` is not used in the constructor.
Best regards.https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/29basler get_bpm_result fails with AttributeError from numpy2022-12-21T09:55:39+01:00Marie Claire Lagierbasler get_bpm_result fails with AttributeError from numpyAttributeError: module 'numpy' has no attribute 'int'
Numpy 1.24 : The deprecation for the aliases np.object, np.bool, np.float, np.complex, np.str, and np.int is expired (introduces NumPy 1.20).
np.int is used by :
- /users/blissadm/c...AttributeError: module 'numpy' has no attribute 'int'
Numpy 1.24 : The deprecation for the aliases np.object, np.bool, np.float, np.complex, np.str, and np.int is expired (introduces NumPy 1.20).
np.int is used by :
- /users/blissadm/conda/miniconda/envs/basler/lib/python3.9/site-packages/Lima/Server/plugins/Bpm.py
- /users/blissadm/conda/miniconda/envs/basler/lib/python3.9/site-packages/Lima/Server/plugins/RoiCollection.pyhttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/28Allow setting latency_time > 02023-10-31T11:29:13+01:00Stuart FisherAllow setting latency_time > 0Some of the scientists would like to use the bpm viewer where they can decouple exposure time and acquisition frequency. I've enabled this option in the bpm viewer now, but it seems the camera doesn't actually support this functionality....Some of the scientists would like to use the bpm viewer where they can decouple exposure time and acquisition frequency. I've enabled this option in the bpm viewer now, but it seems the camera doesn't actually support this functionality.
If you set a `latency_time` != 0, and run `prepareAcq` you get:
```
DevFailed[
DevError[
desc = limacore.Exception: Hardware: setBin(/opt/conda/conda-bld/lima-camera-basler_1658736749318/work/src/BaslerCamera.cpp, 1298): Error: Cont
rol channel not open.
origin = Traceback (most recent call last):
File "/users/blissadm/conda/miniconda/envs/basler/lib/python3.9/site-packages/Lima/Core/Debug.py", line 64, in real_fn
return new_fn(*arg, **kw)
File "/users/blissadm/conda/miniconda/envs/basler/lib/python3.9/site-packages/Lima/Server/LimaCCDs.py", line 1850, in prepareAcq
self.__control.prepareAcq()
limacore.Exception: Hardware: setBin(/opt/conda/conda-bld/lima-camera-basler_1658736749318/work/src/BaslerCamera.cpp, 1298): Error: Control channel
not open.
reason = PyDs_PythonError
severity = ERR]
```
I spoke to @debionne and he tells me there is an option somewhere in the api to change the latency time. I have not dug into the cpp to check whether this is exposed, any help would be much appreciated!https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/26segfault since lima-core and processlib compiled in RelWithDebInfo2022-09-23T09:09:32+02:00Laurent Claustresegfault since lima-core and processlib compiled in RelWithDebInfoLaurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/25add support for camera model ACE22022-07-22T15:54:20+02:00Laurent Claustreadd support for camera model ACE2ACE generation 2 are coming, the current lima plugin did not well manage if some features are really supported by the camera, Pylon provides some nice helper functions like IsAvailable to check this.
We will make some code cleaning to r...ACE generation 2 are coming, the current lima plugin did not well manage if some features are really supported by the camera, Pylon provides some nice helper functions like IsAvailable to check this.
We will make some code cleaning to remove test on "is_usb" and remove exception when the acquisition is stopped. We also optimize the threadFunction() funct to not check the image video format at each new frame for instance.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/24add temperature reading2022-07-22T15:54:41+02:00Laurent Claustreadd temperature readingcheck if available for any camera model.check if available for any camera model.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/23add support for py38 and py392022-03-30T18:17:37+02:00Laurent Claustreadd support for py38 and py39need to move to the latest sip 4.19* (probably 4.19.25) API v12.7need to move to the latest sip 4.19* (probably 4.19.25) API v12.7https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/22Default gain incorrectly calculated on device start2022-03-25T16:57:50+01:00Stuart FisherDefault gain incorrectly calculated on device startI updated the conda environment on id13eh22 (conda env basler) to the latest basler / lima packages. The gain is constrained between [0,1] but on startup the gain is calculated to be 1023. This breaks the device as as soon as you start a...I updated the conda environment on id13eh22 (conda env basler) to the latest basler / lima packages. The gain is constrained between [0,1] but on startup the gain is calculated to be 1023. This breaks the device as as soon as you start a scan you get an out of range error for the camera (gain must be within 0,1).
```
EH2 [25]: uvlm1._proxy
Out [25]: DeviceProxy(id13/limaccds/uvlm1,139763629686944)
EH2 [21]: uvlm1._proxy.video_gain
Out [21]: 1023.0
```
I dont seem to be able to override this in the config either:
```
default :
{
Video :
{
gain = 1;
};
};
```
seems to have no effect (but i could have the wrong config key)
cc @cyril.guilloudhttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/21camera model acA1300-60gmNIR failed with pylon6 and balser plugin 1.102022-03-25T16:56:35+01:00Laurent Claustrecamera model acA1300-60gmNIR failed with pylon6 and balser plugin 1.10observed on ID09 computer lid09bas1, camera plugged on eth4, serial number 21637317
```
[2022/01/14 08:59:29.763887] 7fa747f85700 *Camera*Basler::Camera::setExpTime (/opt/conda/conda-bld/lima-camera-basler_1638524240538/work/src/Basl...observed on ID09 computer lid09bas1, camera plugged on eth4, serial number 21637317
```
[2022/01/14 08:59:29.763887] 7fa747f85700 *Camera*Basler::Camera::setExpTime (/opt/conda/conda-bld/lima-camera-basler_1638524240538/work/src/BaslerCamera.cpp:945)
-Error: Exception(Error): Value 1000000.000000 must be smaller than or equal 916000.000000. [thrown]
basler camera_id: uname://id09-bpm1
-
```Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/20in internal trigger framerate is always enabled2021-11-29T15:13:51+01:00Laurent Claustrein internal trigger framerate is always enabledwhen setting trigger mode to IntTrig the camera setTrigger() method enable the FrameRate, if a previous frame rate, aka a latency time greater than 1us, has been set you will get an acquisition not running at maximum frame rate you expec...when setting trigger mode to IntTrig the camera setTrigger() method enable the FrameRate, if a previous frame rate, aka a latency time greater than 1us, has been set you will get an acquisition not running at maximum frame rate you expect.
The issue is Lima CtAcquisition will first set the exposure then the trigger mode, so basler plugin must not reenable FrameRate if latency_time is ~0. .Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/19Latency time with video live is not working2021-11-10T13:10:52+01:00Valentin VallsLatency time with video live is not workingTrying to play with a RGB basler at ID24
It sounds like the latency time is not working.
```
BERRU [96]: bas_uscope_us.proxy.camera_model
Out [96]: 'acA3088-16gc'
```
```
BERRU [88]: bas_uscope_us.stop_live()
BERRU [89]: bas_uscope...Trying to play with a RGB basler at ID24
It sounds like the latency time is not working.
```
BERRU [96]: bas_uscope_us.proxy.camera_model
Out [96]: 'acA3088-16gc'
```
```
BERRU [88]: bas_uscope_us.stop_live()
BERRU [89]: bas_uscope_us.proxy.image_roi = [0, 0, 100,100]
BERRU [90]: bas_uscope_us.start_live(0.01)
BERRU [91]: bas_uscope_us.proxy.latency_time = 1
BERRU [92]: bas_uscope_us.stop_live()
BERRU [93]: bas_uscope_us.start_live(0.01)
BERRU [94]: bas_uscope_us.proxy.latency_time
Out [94]: 1.0
```
The camera was still taking about 20 frames/s
```
BERRU [97]: prdef(bas_uscope_us.start_live)
'start_live' is defined in:
/home/blissadm/local/bliss.git/bliss/controllers/lima/lima_base.py:1106
def start_live(self, acq_time: typing.Optional[float] = 0.1):
"""Start live video of a Lima detector.
This will also be displayed inside Flint.
"""
flint = plot_module.get_flint()
proxy = self.proxy
flint.start_image_monitoring(self.image.fullname, proxy.name())
if proxy.video_live:
proxy.video_live = False
proxy.acq_time = acq_time
proxy.video_source = "BASE_IMAGE"
proxy.video_exposure = acq_time
proxy.video_live = True
BERRU [98]: prdef(bas_uscope_us.stop_live)
'stop_live' is defined in:
/home/blissadm/local/bliss.git/bliss/controllers/lima/lima_base.py:1121
def stop_live(self):
"""Stop live video of a Lima detector
This will also be stopped inside Flint.
"""
proxy = self.proxy
proxy.video_live = False
flint = plot_module.get_flint(creation_allowed=False, mandatory=False)
if flint is not None:
flint.stop_image_monitoring(self.image.fullname)
```
Any idea why? @claustre @berruyerhttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/18BPM viewer with USB color camera2021-10-27T14:28:56+02:00Michal GandorBPM viewer with USB color cameraUsing the newest pylon6 branch code - all the acquisition, both image and params working fine under jive LiveViewer. When BPM is used, the image is acquired in LiveViewer but does not propagate to BPM web app.Using the newest pylon6 branch code - all the acquisition, both image and params working fine under jive LiveViewer. When BPM is used, the image is acquired in LiveViewer but does not propagate to BPM web app.https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/17Gain parameter not available2021-11-29T15:12:52+01:00Michal GandorGain parameter not availableUsing the newest pylon6 branch and GigE colour camera the `Gain parameter not available` occurs when trying to acquire an image. The gain param can be changed, but during acquisition, the error appears anyway.Using the newest pylon6 branch and GigE colour camera the `Gain parameter not available` occurs when trying to acquire an image. The gain param can be changed, but during acquisition, the error appears anyway.https://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/16pylon6 fix acq thread synchro2021-11-29T15:12:36+01:00Laurent Claustrepylon6 fix acq thread synchrothe acquisition thread function does not work well with some issues when stopping a continuous acquisition or when using a color camerathe acquisition thread function does not work well with some issues when stopping a continuous acquisition or when using a color cameraLaurent ClaustreLaurent Claustre