-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: This detector doesn't manage hardware roi #9
Comments
Salut Philippe, In the meantime you can try to force "no hw roi" by adding the following line in your camera.def file: It seems you X serie model detector (maybe camserver version) does not have the command to check if hw roi is supported. |
Hi @laurent-claustre , Here is the output on the pilatus server:
We use conda 4.8.2 and the system installed is CentOS 6.5:
We installed conda package as following
Here is the list of conda packages installed in the dedicated env:
I added the
Indeed, an image was created in Thank you again for you help! |
Ok, good news. With some camserver versions and even if you are running a X model, the hwroi command id not supported and camserver returns an error code. |
Hi,
I encountered an error with our Pilatus DS.
We have a detector identified in camera_model as a 'PILATUS3 300K-W, S/N 3-xxxx-Z, X serie'.
I followed each step instructions of page https://lima1.readthedocs.io/en/latest/camera/pilatus/doc/index.html#installation
~det/p2_det/config/cam_data/camera.def
:I launched the Pilatus device server with following properties:
/home/det/p2_det/config/cam_data/camera.def
localhost
41234
/lima_data
However, when I launch the command
prepareAcq
, I got the following message:Error: This detector doesn't manage hardware roi
.Do you know how to solve this?
Note: I do not know if this is linked but when I launched ATKPanel, I got following warnings (in commandline):
However LimaCCDs
saving_format
attribute isRAW
(but this is an attribute and not an attribute property).Regards
The text was updated successfully, but these errors were encountered: