Lima-camera-basler issueshttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues2022-03-25T16:57:50+01:00https://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/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/7Expo time2021-06-14T11:34:21+02:00Damien NaudetExpo timeIt seems that the exposition time is not read from the camera when starting Lima.
For example, if you set the expo time to 0.2s (with Lima or PylonViewer), quit, then start Lima, the expo time returned by Lima is 1.0, but you get 5 img/s...It seems that the exposition time is not read from the camera when starting Lima.
For example, if you set the expo time to 0.2s (with Lima or PylonViewer), quit, then start Lima, the expo time returned by Lima is 1.0, but you get 5 img/s when you start the live.
Not sure if this is a Core or Basler issue tho.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/5Manage frame error for B/W camera and continuous acq frame2019-03-20T10:14:31+01:00Laurent ClaustreManage frame error for B/W camera and continuous acq frameA bug has been introduced by not managing the soft buffers when pylon cannot a valid acquire an image (e.g due to lost packets).
The buffer is re-queued to pylon queue letting lima with an invalid image (or the previous one) in the buf...A bug has been introduced by not managing the soft buffers when pylon cannot a valid acquire an image (e.g due to lost packets).
The buffer is re-queued to pylon queue letting lima with an invalid image (or the previous one) in the buffer memory. That create a decrepency between indexes, for instance, if pylon failed at image num 1 and image 2 is ok, image 2 is available in buffer 2 but newFrameReady is fired for image 1, so a client appli requesting image 1 will get buffer 1 where there is a fake image or the previous image due to ring buffer...
We propose to add intermediate small buffer of 2 images, and let pylon only filling the small buffer, then memcopy valid image to the lima bufferv1.8.1Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-basler/-/issues/3External trigger mode is broken2021-06-14T11:33:58+02:00Samuel DebionneExternal trigger mode is brokenRarely used, but required for the next exp on ID13Rarely used, but required for the next exp on ID13Laurent ClaustreLaurent Claustre