Lima-camera-pilatus issueshttps://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues2023-11-10T11:00:36+01:00https://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues/20pilatus 100k acquisition cannot be stopped when running at a high frame rate ...2023-11-10T11:00:36+01:00Laurent Claustrepilatus 100k acquisition cannot be stopped when running at a high frame rate in exttrigmultWhen running at a high frame rate and with extntrigger mode the camserver K command (kill acquisition) is ignore and the acquisition cannot be stopped.
This is due to the expperiod camserver parameter set by Lima always to the latency_ti...When running at a high frame rate and with extntrigger mode the camserver K command (kill acquisition) is ignore and the acquisition cannot be stopped.
This is due to the expperiod camserver parameter set by Lima always to the latency_time, minimum is the detector readoutime 950us.
Setting a period when using external trigger modes is useless and to fix this issue we just need to set the period to a value greater to 100ms.
This issue does not append with the bigger detector models.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues/17Limited number of frames to 2^162023-11-10T17:37:56+01:00Samuel DebionneLimited number of frames to 2^16On Dectris Pilatus2, the frame counter is hold in a 16 bits register, so the limit of nb of frames is 65536.
We should add a check to the prepareAcq() accordingly.
cc @sebastien.petitdemangeOn Dectris Pilatus2, the frame counter is hold in a 16 bits register, so the limit of nb of frames is 65536.
We should add a check to the prepareAcq() accordingly.
cc @sebastien.petitdemangehttps://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues/13camserver and NFS ramdisk - Insufficient Disk Space2022-03-09T14:11:17+01:00Laurent Claustrecamserver and NFS ramdisk - Insufficient Disk SpaceWith old pilatus like on ESRF-ID10 , we run the lima server on a remote computer and NFS mount a ramdisk on the pilatus computer. So camserver check the disk space when the saving path is not detected as a ramdisk (in our case a NFS) and...With old pilatus like on ESRF-ID10 , we run the lima server on a remote computer and NFS mount a ramdisk on the pilatus computer. So camserver check the disk space when the saving path is not detected as a ramdisk (in our case a NFS) and return an error to tell there is not enough space to store the requested images:
```
Insufficient Disk Space
```Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues/11for long exposure time latency time is too short in external trigger mode2021-11-15T15:24:54+01:00Laurent Claustrefor long exposure time latency time is too short in external trigger modewhen starting an acquisition with long exposure (>10s ??) camserver fails and complains about a too short period.
For Pilatus 2, the latency_time must be increase to 13ms, for Pilatus3 is has to be tested.when starting an acquisition with long exposure (>10s ??) camserver fails and complains about a too short period.
For Pilatus 2, the latency_time must be increase to 13ms, for Pilatus3 is has to be tested.Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/Lima-camera-pilatus/-/issues/4Pilatus says ready when it is not : missing first external trigger2022-05-17T12:11:06+02:00Matias GuijarroPilatus says ready when it is not : missing first external triggerI had to add 3 milliseconds sleep after 'startAcq' to make sure trigger was not missed.I had to add 3 milliseconds sleep after 'startAcq' to make sure trigger was not missed.