Skip to content
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

MOT0109_0: Spatial: Failed to open device: Timed Out #105

Closed
DoneMan opened this issue Oct 20, 2021 · 11 comments · Fixed by #106
Closed

MOT0109_0: Spatial: Failed to open device: Timed Out #105

DoneMan opened this issue Oct 20, 2021 · 11 comments · Fixed by #106

Comments

@DoneMan
Copy link

DoneMan commented Oct 20, 2021

did anyone encounter this before?
on branch noetic.
i have the phidgets spatial 3/3/3 MOT0109_0, i'm trying to launch the spatial.launch and i get these errors:

[ INFO] [1634714179.485430556]: Loading nodelet /PhidgetsSpatialNodelet of type phidgets_spatial/PhidgetsSpatialNodelet to manager imu_manager with the following remappings:
[ INFO] [1634714179.487040471]: waitForService: Service [/imu_manager/load_nodelet] has not been advertised, waiting...
[ INFO] [1634714179.492581832]: Loading nodelet /ImuFilterNodelet of type imu_filter_madgwick/ImuFilterNodelet to manager imu_manager with the following remappings:
[ INFO] [1634714179.494079519]: waitForService: Service [/imu_manager/load_nodelet] has not been advertised, waiting...
[ INFO] [1634714179.504203262]: Initializing nodelet with 8 worker threads.
[ INFO] [1634714179.508148068]: waitForService: Service [/imu_manager/load_nodelet] is now available.
[ INFO] [1634714179.510623053]: Initializing Phidgets SPATIAL Nodelet
[ INFO] [1634714179.510687100]: Starting Phidgets SPATIAL
[ INFO] [1634714179.510703508]: Opening spatial
[ INFO] [1634714179.513058698]: Connecting to Phidgets Spatial serial 373265, hub port 0 ...
[ INFO] [1634714179.515118447]: waitForService: Service [/imu_manager/load_nodelet] is now available.
[ERROR] [1634714180.514098019]: Spatial: Failed to open device: Timed Out
[FATAL] [1634714180.515002304]: Failed to load nodelet '/PhidgetsSpatialNodeletof typephidgets_spatial/PhidgetsSpatialNodeletto managerimu_manager'
[ INFO] [1634714180.525610450]: Initializing IMU Filter Nodelet
[ INFO] [1634714180.528075648]: Starting ImuFilter
[ INFO] [1634714180.539780216]: Using dt computed from message headers
[ INFO] [1634714180.539883555]: The gravity vector is kept in the IMU message.
[ INFO] [1634714180.560925486]: Imu filter gain set to 0.100000
[ INFO] [1634714180.560996819]: Gyro drift bias set to 0.000000
[ INFO] [1634714180.561031830]: Magnetometer bias values: 0.000000 0.000000 0.000000
[PhidgetsSpatialNodelet-3] process has died [pid 6039, exit code 255, cmd /opt/ros/melodic/lib/nodelet/nodelet load phidgets_spatial/PhidgetsSpatialNodelet imu_manager __name:=PhidgetsSpatialNodelet __log:=/home/user/.ros/log/9edd08f0-3175-11ec-92fd-b05cdaa8ff51/PhidgetsSpatialNodelet-3.log].
log file: /home/user/.ros/log/9edd08f0-3175-11ec-92fd-b05cdaa8ff51/PhidgetsSpatialNodelet-3*.log
[ WARN] [1634714190.572501364]: Still waiting for data on topics /imu/data_raw and /imu/mag...

can anyone help please?

@mintar
Copy link
Contributor

mintar commented Oct 20, 2021

This is the crucial line:

[ERROR] [1634714180.514098019]: Spatial: Failed to open device: Timed Out

So it seems like the driver tried to open the USB device, but failed.

The phidgets webpage says:

Make sure you're setting all of the matching parameters correctly. You can learn more by reading our page on Addressing Phidgets. Also make sure that the channels you're trying to open aren't already opened in another program (including the Phidget Control Panel).

Some more things to check:

  • Did you set up the udev rules properly? (see README)
  • Does the device show up in lsusb?

@mintar mintar changed the title Failed to load nodelet '/PhidgetsSpatialNodelet of type phidgets_spatial/PhidgetsSpatialNodelet to manager imu_manager Spatial: Failed to open device: Timed Out Oct 20, 2021
@DoneMan
Copy link
Author

DoneMan commented Oct 20, 2021

@mintar
yes, i have set up the udev-rules as was instructed in the wiki
yes when typing lsusb the device shows up as follows:
Bus 001 Device 042: ID 06c2:008c Phidgets Inc. (formerly GLAB)

@DoneMan
Copy link
Author

DoneMan commented Oct 20, 2021

@mintar any ideas on what can cause this?

@phidgets
Copy link

MOT0109_0 requires phidget22. The module will need to be migrated from phidget21 to phidget22.

@DoneMan
Copy link
Author

DoneMan commented Oct 21, 2021

@phidgets branch noetic uses phidget22

@phidgets
Copy link

Ok, i didn’t have a look at the other branch. It looks to be pulling in a particular version of libphidget22 from 1.5 years ago. MOT0109 is a brand new device and requires version 1.7.20210816 or newer of the library.

@DoneMan
Copy link
Author

DoneMan commented Oct 21, 2021

@phidgets i see. looks like i will have to edit the source code for it to take the new package.
thank you very much for your support.
also
@mintar thank you very much.

@mintar mintar changed the title Spatial: Failed to open device: Timed Out MOT0109: Spatial: Failed to open device: Timed Out Oct 21, 2021
@mintar mintar changed the title MOT0109: Spatial: Failed to open device: Timed Out MOT0109_0: Spatial: Failed to open device: Timed Out Oct 21, 2021
@DoneMan
Copy link
Author

DoneMan commented Oct 21, 2021

@mintar how complicated do you think this is to be done? updating the libphidgets22 library?

@mintar
Copy link
Contributor

mintar commented Oct 21, 2021

@phidgets : Thanks for the hint!

@DoneMan : I've just pushed the required changes to the libphidgets22-1.7-noetic branch. Please test whether it's working and leave a comment!

@DoneMan
Copy link
Author

DoneMan commented Oct 21, 2021

@mintar great! i am checking now

mintar added a commit that referenced this issue Oct 21, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.
@DoneMan
Copy link
Author

DoneMan commented Oct 21, 2021

@mintar it works!!! you are a freaking king! thank you very much!!

@DoneMan DoneMan closed this as completed Oct 21, 2021
@DoneMan DoneMan reopened this Oct 21, 2021
mintar added a commit that referenced this issue Oct 21, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.
mintar added a commit that referenced this issue Oct 22, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.
mintar added a commit that referenced this issue Oct 22, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.

This is a forward-port of #106 to ROS2.
mintar added a commit that referenced this issue Oct 22, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.

This is a forward-port of #106 to ROS2.
clalancette pushed a commit that referenced this issue Oct 22, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.

This is a forward-port of #106 to ROS2.
clalancette pushed a commit that referenced this issue Oct 22, 2021
This is required to support new devices such as the MOT0109.

Fixes #99, fixes #105.

This is a forward-port of #106 to ROS2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants