Difference between revisions of "Troubleshooting"

From sdk-wiki
Jump to: navigation, search
(Still Stuck?)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=Troubleshooting=
+
<span style="font-size:120%;">'''The purpose of this section is to provide tools for troubleshooting hardware, software, and networking issues with Baxter.'''</span>
<span style="font-size:120%;">'''The purpose of this section is to provide some tools for you to use when troubleshooting when things aren't working the way you expect with Baxter.'''</span>
+
  
  
Line 6: Line 5:
  
  
[[File:Troubleshooting Workflow.png|800px]]
+
[[File:Troubleshooting Workflow.png|700px|Support]]
  
  
In many cases, an issue will fall within one of the three categories listed below.
+
In a majority of cases, an issue will fall within one of the three categories listed below.
  
 
*Hardware
 
*Hardware
Line 17: Line 16:
  
 
To troubleshoot an issue, start by browsing the debugging strategies section below or search the wiki for documentation concerning the problem.
 
To troubleshoot an issue, start by browsing the debugging strategies section below or search the wiki for documentation concerning the problem.
 +
  
 
==Debugging Strategies==
 
==Debugging Strategies==
[[Debugging Strategies]] - Start here to get help!
+
'''What to do when something is just not right?  Here are some starter steps you can take when debugging Baxter, or just for when you want to inspect what's going on.'''
  
== Commonly Reported Baxter Issues ==
+
<span id="The Basic System Checks">&nbsp;</span>
 +
== Start Here! - The Basic System Checks ==
 +
Often times, an issue that a user is having may simply be from the robot software and/or the SDK software being either out of date or incompatible with each other.  Follow the three steps below to make sure that your systems are compatible with each other.
 +
 
 +
Is the robot running the same version of software as your SDK workstation?
 +
* [[Software_Update_-_v1.0.0#II._Setup_and_Check_Version|Checking s/w version]]
 +
 
 +
Are the robot and workstation running the latest available software release? (Today that would be the 1.0.0 software)
 +
*[[Software Update - v1.0.0|Instructions on accessing the latest software and updating your robot]].
 +
 
 +
Is your workstation capable of working well with Baxter?
 +
*[[System requirements|Minimum SDK requirements]].
 +
 
 +
 
 +
== Commonly Reported Issues ==
 
*[[Trouble enabling robot]]
 
*[[Trouble enabling robot]]
 
*[[Arms are pulling in Zero-G mode]]
 
*[[Arms are pulling in Zero-G mode]]
 
*[[Calibration and/or Tare is failing]]
 
*[[Calibration and/or Tare is failing]]
 
*[[Baxter arms are tucked and untuck arms example is not working]]
 
*[[Baxter arms are tucked and untuck arms example is not working]]
*[[Arms are moving in an unexpected way]]
 
 
*[[Gripper commands are failing]]
 
*[[Gripper commands are failing]]
  
 +
<span id="Understanding the Problem">&nbsp;</span>
 +
== Understanding the Problem ==
 +
As a Research SDK user you are in a more free-form environment than standard Baxter customers, and often will be dealing with hardware, software, and environment configurations all at the same time.  The first step in resolving your problem is determining what type of problem it could be.  As previously mentioned, the majority of issues can be groups into one of the below categories.  In each category we will try to help you determine what group your specific issue falls within and provide you with tools to help resolve.
 +
 +
*Hardware
 +
*Software
 +
*Networking
 +
 +
<span id="Hardware">&nbsp;</span>
 +
==== Hardware====
 +
The first step is determining if you are facing a Hardware problem.  Many hardware issues are fairly apparent that something physical is broken - if there's a crack in a screen or a ripped cable, there's little mystery left.  Other issues may be internal or electrical and need a bit of investigation to discover. 
 +
 +
Possible symptoms of a hardware failure:
 +
*Baxter will not bootup
 +
*Arms are disabling and falling slowing
 +
*[[Gripper commands are failing|Electric gripper is stuck in an "open" position]]
 +
 +
Available tools to help you troubleshoot:
 +
*[[Tools - robot monitor|Robot Monitor]] - ROS package to display robot diagnostics.
 +
*[[Field Service Menu (FSM)#Tests Menu|Field Service Menu]] - Low level hardware tests that can be run on Baxter.
 +
*[[FTP Log Files|Export Logs]] - Rethink Robotics Support will require the log files from a customer with a potential hardware failure.
 +
 +
 +
If you face a Hardware problem, you can always contact The Rethink Robotics Support team at RSDK.Support@RethinkRobotics.com and start working with them to further diagnose the issue, and possibly schedule a service call.
 +
 +
==== Software Issues ====
 +
If your problem doesn't seem to be related to a physical component of the robot, then you'll need to figure out if the issue is in the Software - and furthermore, ''which'' Software. The three major players in the software system will be ROS, the Research SDK (both on-robot and on-development machine), and of course, your own code. ROS introspection features and the Topic/Service based communication help out to easily inspect what's going on when debugging your code.  Useful tools include [[rviz]] and [http://www.ros.org/rxbag rxbag (rosbag)].
 +
 +
Possible symptoms of a software failure:
 +
*Baxter will not boot up
 +
*Baxter is shutting down
 +
*Calibration/Tare Failure
 +
*[[Trouble enabling robot|Unable to enable arms]]
 +
 +
Available tools to help you troubleshoot:
 +
* [[rviz]]
 +
* [[Tools - rxconsole|rxconsole]]
 +
* [http://www.ros.org/rxbag rxbag (rosbag)] - Record, view, and playback ROS topics ([http://www.ros.org/rxbag/Commandline Command-line reference])
 +
* [http://www.ros.org/rxplot rxplot] - Plot ROS topics data on a simple graph (Numerical and boolean data)
 +
 +
 +
If you think you're having a software problem, checkout some of the other tools on the wiki and also the ROS documentation.  If you've found a bug in the software, you can also see if it's in our GitHub tickting system, and if not, please add it! =)
 +
 +
==== Network & Environment Issues ====
 +
If your problems seem to be dipping into the area of communication issues, there's a good chance that checking into your Network configuration and Environment settings is a very worthwhile step.  ROS and various network setups sometimes take a bit of TLC.  Thankfully there is a great little checklist you can run through over at the [http://www.ros.org/ROS/NetworkSetup ROS wiki] that will help you sort out many of the possible issues!
 +
 +
Possible symptoms of Newtwork issues:
 +
*[[Networking#Baxter|Cannot ping Baxter]]
 +
*[[Trouble enabling robot|Cannot enable Baxter]]
 +
 +
Available tools to help you troubleshoot:
 +
*[[Networking]]
 +
 +
<span id="Still Stuck?">&nbsp;</span>
 +
 +
== Still Stuck? ==
 +
 +
<span style="font-size:120%;">'''[https://groups.google.com/a/rethinkrobotics.com/forum/#!forum/brr-users User Forum]</span> - The Baxter Research Robot Community Forum, hosted by Google Groups, is a great place to communicate with the Rethink Robotics Support team, as well as other Baxter Researchers.  Post your question, and you'll get an answer, either from other community members, or the folks here at Rethink.
 +
 +
 +
<span style="font-size:120%;">'''[mailto:rsdk.support@rethinkrobotics.com Rethink Robotics Support]</span> - Send a message with specific details about the problem you are experiencing as well as the troubleshooting steps that you have already taken if the wiki and forum have not resolved your issue.
  
.
+
----

Latest revision as of 14:57, 15 April 2015

The purpose of this section is to provide tools for troubleshooting hardware, software, and networking issues with Baxter.


We recommend using the workflow below when troubleshooting an issue - in many cases others have come across the same questions!


Support


In a majority of cases, an issue will fall within one of the three categories listed below.

  • Hardware
  • Software
  • Networking


To troubleshoot an issue, start by browsing the debugging strategies section below or search the wiki for documentation concerning the problem.


Debugging Strategies

What to do when something is just not right? Here are some starter steps you can take when debugging Baxter, or just for when you want to inspect what's going on.

 

Start Here! - The Basic System Checks

Often times, an issue that a user is having may simply be from the robot software and/or the SDK software being either out of date or incompatible with each other. Follow the three steps below to make sure that your systems are compatible with each other.

Is the robot running the same version of software as your SDK workstation?

Are the robot and workstation running the latest available software release? (Today that would be the 1.0.0 software)

Is your workstation capable of working well with Baxter?


Commonly Reported Issues

 

Understanding the Problem

As a Research SDK user you are in a more free-form environment than standard Baxter customers, and often will be dealing with hardware, software, and environment configurations all at the same time. The first step in resolving your problem is determining what type of problem it could be. As previously mentioned, the majority of issues can be groups into one of the below categories. In each category we will try to help you determine what group your specific issue falls within and provide you with tools to help resolve.

  • Hardware
  • Software
  • Networking

 

Hardware

The first step is determining if you are facing a Hardware problem. Many hardware issues are fairly apparent that something physical is broken - if there's a crack in a screen or a ripped cable, there's little mystery left. Other issues may be internal or electrical and need a bit of investigation to discover.

Possible symptoms of a hardware failure:

Available tools to help you troubleshoot:

  • Robot Monitor - ROS package to display robot diagnostics.
  • Field Service Menu - Low level hardware tests that can be run on Baxter.
  • Export Logs - Rethink Robotics Support will require the log files from a customer with a potential hardware failure.


If you face a Hardware problem, you can always contact The Rethink Robotics Support team at RSDK.Support@RethinkRobotics.com and start working with them to further diagnose the issue, and possibly schedule a service call.

Software Issues

If your problem doesn't seem to be related to a physical component of the robot, then you'll need to figure out if the issue is in the Software - and furthermore, which Software. The three major players in the software system will be ROS, the Research SDK (both on-robot and on-development machine), and of course, your own code. ROS introspection features and the Topic/Service based communication help out to easily inspect what's going on when debugging your code. Useful tools include rviz and rxbag (rosbag).

Possible symptoms of a software failure:

Available tools to help you troubleshoot:


If you think you're having a software problem, checkout some of the other tools on the wiki and also the ROS documentation. If you've found a bug in the software, you can also see if it's in our GitHub tickting system, and if not, please add it! =)

Network & Environment Issues

If your problems seem to be dipping into the area of communication issues, there's a good chance that checking into your Network configuration and Environment settings is a very worthwhile step. ROS and various network setups sometimes take a bit of TLC. Thankfully there is a great little checklist you can run through over at the ROS wiki that will help you sort out many of the possible issues!

Possible symptoms of Newtwork issues:

Available tools to help you troubleshoot:

 

Still Stuck?

User Forum - The Baxter Research Robot Community Forum, hosted by Google Groups, is a great place to communicate with the Rethink Robotics Support team, as well as other Baxter Researchers. Post your question, and you'll get an answer, either from other community members, or the folks here at Rethink.


Rethink Robotics Support - Send a message with specific details about the problem you are experiencing as well as the troubleshooting steps that you have already taken if the wiki and forum have not resolved your issue.