Robotics StackExchange | Archived questions

clearpath husky emergency stop issue

Hello,

I have a clearpath husky a200. Recently, there has been a problem where the husky will keep activating the emergency stop during operation (see attached video). The problem used to happen maybe once in a while; however, it has gotten to a point now where we are are not able to even teleoperate the robot.

Things we've tried that didn't work:

  1. charging the battery overnight to ensure full charge
  2. checked all connections on board from sensors, estop receiver...etc
  3. charged the estop pendent to ensure full charge

Please let me know if you've seen this issue before?

https://www.youtube.com/watch?v=jW91uOJ2uwI

UPDATE (May 21st): I have tried installing a new ISO for the husky, still didn't fix the problem

UPDATE 2 (May 23rd): I have found that the error seems to happen less when operating at extremely low speeds and acceleration via keyboard teleoperation (teleoptwistkeyboard: this package allows the user to increase/decrease speed). This might be why joystick operation causes the error to happen immediately (the joystick commands outputs a preset high velocity/acceleration upon user input).

  1. Could there be a corrupted file somewhere in Husky that prohibits certain user vel/accel commands which subsequently stops the husky? If so, where should I look?

  2. Also, how can I lower the speed output from the joystick operation to verify that this is indeed a speed/acceleration limit issue?

Asked by aarontan on 2018-05-20 15:45:04 UTC

Comments

Could you clarify whether you've contacted Clearpath about this already?

Asked by gvdhoorn on 2018-05-21 01:50:54 UTC

yes, I have emailed tech support at clearpath but I was hoping someone whose experienced this before may help me before clearpath responds

Asked by aarontan on 2018-05-21 07:32:23 UTC

here's a related post: https://answers.ros.org/question/292023/husky-a200-motor-driver-too-hot/

Asked by aarontan on 2018-05-23 11:00:59 UTC

Clearpath has confirmed that this is a hardware issue.

Asked by aarontan on 2018-06-06 13:22:57 UTC

Answers