Closed Assume-Zhan closed 1 year ago
Like the issue happened before, but hardware is PhidgetSpatial Precision 3/3/3 MOT0110_0
What issue?
I've also installed the latest libphidget22, and run the helloworld example in here
Could you try the helloworld example with libphidget22-1.7.20210816
instead of the latest one? This version is what we're using, and it should already have support for the MOT0110_0. If the helloworld example doesn't work with our version of libphidget22, then maybe upgrading to the latest version will solve your problem.
Like this timeout issue #105; however, the IMU version is 0109.
I've tried to use the latest version of libphidget, and it got well for HelloWorld example.
Later on, I tried to use libphidget22-1.7.20210816
, it can't detect any attach and detach signal.
So that I try to upgrade the libphidget
to the latest version, and it works well and finally get connected.
It seems that the MOT0110_0 is not supported for old version of libphidget
@mintar Thank you very much !!!
I am facing the same issue. I have MOT0110_0 and the HelloWorld example from libphidget22-1.13 works. But the phidigets_drivers package uses the 1.7 version of libphidget. How should I upgrade the version of libphidget of the phidgets_drivers package to make it run. I am new to all this so a little help would be really appreciated, thanks.
In short, you need to update https://github.com/ros-drivers/phidgets_drivers/blob/noetic/libphidget22/CMakeLists.txt to point to the new version, and make any patches necessary to make it compile without warnings. You can see an example PR (on the rolling
branch) here: https://github.com/ros-drivers/phidgets_drivers/commit/9b679fa5ad2d91832de163398d239ffa74dceaea
Thanks @clalancette for your answer, After changing the libphidget version to the appropriate one in the CMakeLists.txt file and using the patch file for the mentioned PR the package finally worked.
Thanks @clalancette for your answer, After changing the libphidget version to the appropriate one in the CMakeLists.txt file and using the patch file for the mentioned PR the package finally worked.
If you'd like to submit a PR to update noetic to that, it would be much appreciated.
I'm looking at #160 myself right now and will submit a PR to backport it to noetic afterwards, so no need to do anything on your side, @kunal-mod .
I have merged the update to libphidget into the noetic
, rolling
and humble
branches and released them on the ROS buildfarm. They should be part of the next binary release (in a few weeks time). Until then, you have to build from source.
I have the same issue. I just bought a PhidgetSpatial Precision 3/3/3 MOT0110_0. Ubuntu 20 and ROS noetic.
I've tried to use the latest version of libphidget, libphidget22-1.18.2024123
, and it worked well for the HelloWorld example and the example.py
script to print the IMU measurements.
Later on, I tried to use the current library you are using for the noetic branch, libphidget22-1.13.20230224
, and it can't detect any attach and detach signal.
I wanted to try to replicate the steps in for ex #161 but I am not sure where to get the URL_MD5
value. I just change the library version, try to compile and I get a Each Download failed!
.
Could you instruct me how to do that so I can try to update the libphidget library my driver uses?
I have the same issue. I just bought a PhidgetSpatial Precision 3/3/3 MOT0110_0. Ubuntu 20 and ROS noetic.
I've tried to use the latest version of libphidget,
libphidget22-1.18.2024123
, and it worked well for the HelloWorld example and theexample.py
script to print the IMU measurements. Later on, I tried to use the current library you are using for the noetic branch,libphidget22-1.13.20230224
, and it can't detect any attach and detach signal.I wanted to try to replicate the steps in for ex #161 but I am not sure where to get the
URL_MD5
value. I just change the library version, try to compile and I get aEach Download failed!
.Could you instruct me how to do that so I can try to update the libphidget library my driver uses?
I managed to get it using md5sum path/to/libphidget22-1.18.2024123.tar.gz
. However, when compiling libphidget22
with catkin build
it never compiles, it just runs forever (>40 min), so I have not yet been able to use the new version of the library. I am using the same path file for 1.13
The patch file needs to be recreated as well. It probably hangs because:
patch
command doesn't succeed because you switched the library, so the libphidget22-*.patch
doesn't match the files it is trying to patch.patch
command fails, it goes into interactive mode and asks the user how to proceed.catkin
, so you don't see it and it just hangs forever.You need to compile it without the patch file, then you'll get a lot of warnings from libphidget
. You have to fix those warnings and create a new patch file for those fixes.
Thanks @mintar. TLDR: I got it working.
In case you are interested, after compiling without the patch file, I ran the spatial launch file again but I got the same MOT0110_0: Spatial: Failed to open device: Timed Out
error. I tried many things; one was re-downloading the same library from the "User Guide" in the sensor website, then tried to run the "Example Code" with Python, which did not run so I installed the python library with pip install --force-reinstall -v "Phidget22==1.18.20240123"
. After all that, I managed to get it working with the ros driver (although I am not sure exactly what made it work).
Thanks again.
@andrespulido8 Just FYI: I've updated the libphidget to 1.19 in PR #175. Seems you got it working without me, but that PR should fix it for everyone.
Like the issue happened before, but hardware is PhidgetSpatial Precision 3/3/3 MOT0110_0
\ Phidgets Device
\ Host Machine
\ Issue Description
Time out Everytime I run
roslaunch phidgets_spatial spatial.launch
it always get a timeout issueAdditional info When I run
lsusb
, it has shown upI've run the command in README to setup udev rules.
I've also installed the latest libphidget22, and run the helloworld example in here And it always output 5 times even I have plugin and unplugin once.
Did I miss any required steps?