Jack O'Quin
Jack O'Quin
Q&A page is here: http://answers.ros.org/question/61720/move_base-cannot-cancel-while-executing-recovery-behavior/
Is there some way to hack it by setting a global boolean variable for the behavior to check periodically, returning if it's set?
My naive opinion: your last option looks good.
Some cameras can get their firmware into a bad state for whatever reasons. What recovery actions have you tried? Some of these suggestions may help: http://wiki.ros.org/camera1394/Troubleshooting
> If this problem is happening, I've tried opening coriander, where I see the > same effect. However, If I stop and start reception from coriander, the > problem seems...
> Also, if I open coriander I can fix the problem by pressing "restart iso". I imagine this could be included during initialization on the ros driver. I'm not sure...
Yes, please keep it open. What you did should have worked. The version you built has several significant changes from the current Hydo release, 1.9.5. I am planning to release...
Thanks for checking. Sounds like the problem is somewhere in the relatively recent changes.
Happened again today. Different address, but same offset in `freenect_close_device`. No core dump. I forgot to set ulimit. But, it's probably reproducible.
Thanks for the report. I agree that ``addLaserCalibration()`` is broken. It was probably never tested without data for all the lasers. I believe this is a duplicate of #79.