"set_only_check_type" seems not working about xarm-python-sdk

[vimior]

@tma-qst
Sorry, yes, there is a problem with this feature in 1.11.x, we will release a new one soon, I will let you know when it is released

[tma-qst]

@vimior Thank you so much for the prompt reply! Following to your answer, I'd like to know the followings. Please let me know if you have answers!

• Is there any combinations of the Python SDK and firmware where set_only_check_type works?
• Is that problem only for the Python SDK? I mean, does set_only_check_type work in the C++ SDK?
• Is there an expectation when the fixed version will be released? (in weeks, or months, or...?)

[vimior]

@tma-qst

• Not sure yet
• This problem is in the firmware, so both Python and C++ will have this problem, and both Python and C++ will support this function
• A new version is expected to be released within this week (or next week later)

[tma-qst]

@vimior Got it, thanks!!

[vimior]

@tma-qst
We have updated the firmware and Studio to v1.12.0, you should get the update within a few days.
We recommend updating the firmware of v1.12.0 and Studio together, and updating the SDK (v1.11.5)

[vimior]

@tma-qst
For the motion interface after set_only_check_type(x) (x>0), it is recommended to judge the return value. If the return value is 1, the value of only_check_result is the corresponding error code. If the previous one has failed, the subsequent result may not be correct

[tma-qst]

@vimior Thank you so much!! Since I need do the update by offline, I will be waiting for the latest firmware uploaded on the google drive directory. I will check whether my script works as soon as I have downloaded the updated firmware!

[tma-qst]

Now I've installed the updated firmware, and my script works - successfully detects self-collisions!!
I'm closing this issue. Thank you so much for your efforts!