gevent.exceptions.InvalidThreadUseError

[Baokangwen]

@beenje @olofsvensson @pkeller @tbn @AKastner
Dear everyone,

I have the following problem in the process of configuring MXCUBE, I have tried many methods, I don't know how to do it, have you ever encountered this situation, what changes should I make to the program?

Thank you for your reply.

Best regards,
kven

[beteva]

Dear @Baokangwen, the error message you report is not explicit enough to understand your problem. One can only see that you are using the exporter protocol for your device and that the device is still busy. As the error says cannot read image, this leads to think that you are using the exporter protocol to read you OAV image, but I can only speculate on this. Please, be more explicit and show not only all the trace, but also what device you have the error with and the xml configuration of this device.

[marcus-oscarsson]

Hi @Baokangwen, could you give us some more context, what are you trying to do when this happens ? What version of mxcubecore are you using ? It seems to be some sort of gevent issue.

[Baokangwen]

Dear @beteva @marcus-oscarsson,

Attached is my run log file.I am using the latest MXCUBE version.

mxcube3.log

Best regard,
kven

[Baokangwen]

Dear @marcus-oscarsson @beteva,
As shown in the image below, the Beamline attri (id) of MotorAdapter is shown as none, I found that the name of the HO filename is also wrong, I don't have the xml file tox, my file is called dtox.xml.

Thanking you for your reply.

[marcus-oscarsson]

You perhaps have a typo in your beamline.yml or detector.xml file, look for tox in those files ?

[Baokangwen]

You perhaps have a typo in your beamline.yml or detector.xml file, look for tox in those files ?

Thank you marcus,this problem was successfully resolved.

[Baokangwen]

Dear @Baokangwen, the error message you report is not explicit enough to understand your problem. One can only see that you are using the exporter protocol for your device and that the device is still busy. As the error says cannot read image, this leads to think that you are using the exporter protocol to read you OAV image, but I can only speculate on this. Please, be more explicit and show not only all the trace, but also what device you have the error with and the xml configuration of this device.

@ Dear betava
I had this issue when I was getting a video stream from the MD2 camera.
Just like the image below.

If the data is obtained correctly, it should look like this.

Do you know how to solve this problem?

[marcus-oscarsson]

Sorry for taking sometime to answer, we have all been on Christmas holidays :). I assume that you are using Tango to communicate with the camera is that correct ?. Is this in a hardware object or in the mxcube-video-streamer project ?

The numbers in the last screenshot somehow looks correct, its binary data. What would you like to do with this data ?