Martin Günther

Just for reference: Our scanner has firmware `V2.51-21.08.15` . I haven't personally seen the problem, but that doesn't mean I'm positive it's not there. I guess many people don't even...

@spuetz , could you have a look?

Can't test right now because compilation fails, just as @WanliJiang noticed. Some more thoughts: - Why not use `q` and `e` to yaw, like in most shooters? And some other...

Oh, just noticed that you already mentioned the select tool conflict. I'm not really happy with either solution (deactivating and reactivating it / mentioning the problem in the docu /...

Yes, firmware version > 2.5 don't support ranging output, so our driver refuses to work with it here: https://github.com/uos/sick_tim/blob/200a3e10e11adb472a6603a494c34774088ca1e7/src/sick_tim_common.cpp#L281-L285 You can disable this check, but then it probably still won't...

I'm glad you found a workaround! Indeed, it looks like the 3 values you changed manually were not correctly parsed from the datagram (especially angle_increment). I don't have time to...

What exact phidgets device are you using? What versions of this repo and libphidgets are you using in ROS2 and ROS1? What is your ROS2 version? I guess that the...

Related issues: #162, #159

One more tip: make sure that the /imu/data topic on Noetic is actually published directly by the phidgets_spatial node and not using the imu_filter_madgwick.

Your device (PhidgetSpatial 3/3/3 Basic 1042_0) doesn't support onboard orientation estimation. You can see that if you check the C API: https://www.phidgets.com/?prodid=1025#Tab_API For your device, `PhidgetSpatial_getAlgorithm()` has a constant output...