-
Notifications
You must be signed in to change notification settings - Fork 40
Caveats
Whenever a sufficiently high current draw is induced, typically through
injecting a power fault, the value of the telemetry
/power_system_node/remaining_useful_life will drop to 0 within a few readings.
A fix for this problem is in the works at the time of this writing.
Occasionally, the invocation of a lander operation, i.e. its ROS action, results in the following message and the operation is aborted or ends in failure. This is an intermittent problem whose cause has not yet been identified. The failed operation usually succeeds on the next try.
[ WARN]: Fail: ABORTED: No motion plan found. No execution attempted.
Occasionally, a Guarded Move operation fails with one of the following results. These are intermittent problems whose cause has not yet been identified. The failed operation usually succeeds on the next try.
[INFO] [1662588335.979580, 1916525073.690000]: Guarded move activity started
[INFO] [1662588363.379669, 1916525101.015000]: Ground Detected ? True
[ERROR] [1662588363.758741, 1916525101.452500]: Received comm state PREEMPTING when in simple state DONE with SimpleActionClient in NS /arm_controller/follow_joint_trajectory
[INFO] [1662588364.138530, 1916525101.822500]: GuardedMove: Failed
or
[ WARN] [1662997380.189337090, 1916525067.187500000]: Fail: ABORTED: No motion plan found. No execution attempted.
[INFO] [1662997390.173686, 1916525076.817500]: Ground Detected ? False
[INFO] [1662997390.174705, 1916525076.817500]: GuardedMove: Failed
Arm faults that are injected during any arm operation should immediately stop
the arm's motion. During execution of the DigLinear action, if the scoop yaw
joint is locked just before the scoop rotates to face the direction of the dig,
the arm may not stop, and the scoop will plow into the terrain sideways. A
solution is being sought at the time of this writing.
The following kind of error occasionally appears in the executive terminal during pan/tilt operations. Pan/tilt are planned to be reworked.
[ERROR] [1637092964.828277383, 1916524887.799999952]: PanAntenna timed out
[ERROR] [1637092964.828318296, 1916524887.799999952]: PanAntenna failed. Ended at 69.477832 degrees, goal was 70.000000.
Warnings like the following might appear soon after the executive node is started. They are spurious and have to do with initialization order.
[ WARN] [1637249546.320531960, 1916524870.472500086]: PLEXIL: Battery charge is low!
[ WARN] [1637249546.320597956, 1916524870.474999905]: PLEXIL: Battery too hot!
The following errors and warnings (listed in arbitrary order) typically occur when the simulator is starting. They may be safely ignored unless they occur excessively.
[ WARN]: Skipping virtual joint 'fixed_base' because its child frame 'base_link' does not match the URDF frame 'world'
[ERROR] [1600978208.628103326]: Failed to find 3D sensor plugin parameters for octomap generation
[ERROR] [1562963343.559613217]: Could not find the planner configuration 'None' on the param server
[ERROR] [1562963345.732187182]: Got low value for ros::Time::now() in the solar frame publisher: 0.000000000
[Err] [msgs.cc:2883] Unrecognized geometry type
[Err] [CameraSimVisualPlugin.cpp:46] Camera is null. CameraSimVisualPlugin won't load.
Error [Element.cc:702] Missing element description for [param]
[Err] [Scene.cc:2949] Light [lander::lander_lights_link::lander_light_light1] already exists. Use topic ~/light/modify to modify it.
[ERROR] [1562963346.929316708, 1631761200.000999928]: CelestialBodyPlugin::OnUpdate - "site" passed to lookupTransform argument target_frame does not exist.
[ERROR] [1600978213.758398746, 1916524801.982500076]: CelestialBodyPlugin::OnUpdate - "sun" passed to lookupTransform argument source_frame does not exist.
[ERROR] [1600978213.763400607, 1916524801.987499952]: CelestialBodyPlugin::OnUpdate - "jupiter" passed to lookupTransform argument source_frame does not exist.
ERROR 1: TIFFFieldWithTag:Internal error, unknown tag 0x829a
```ODE Message 3: LCP internal error, s <= 0```
(This one is henceforth suppressed because it can occur throughout the
simulation whenever there is a collision).
The following errors and warnings (listed in arbitrary order) sometimes occur during lander operations. They may be safely ignored unless they occur excessively.
RRTstar: problem definition is not set, deferring setup completion...
RRTstar: Started planning with 1 states. Seeking a solution better than 0.00000.
RRTstar: Initial k-nearest value of 310
[ERROR]: Got a callback on a goalHandle that we're not tracking. This is an internal
SimpleActionClient/ActionClient bug. This could also be a GoalID collision.
When first built, the following warning occurs. It can be safely ignored, and
if desired, suppressed with catkin build --cmake-args -Wno-dev.
CMake Warning (dev) at /usr/share/cmake-3.10/Modules/FindBoost.cmake:911 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.
Quoted variables like "chrono" will no longer be dereferenced when the
policy is set to NEW. Since the policy is not set the OLD behavior will be
used.
Call Stack (most recent call first):
/usr/share/cmake-3.10/Modules/FindBoost.cmake:1558 (_Boost_MISSING_DEPENDENCIES)
/usr/share/OGRE/cmake/modules/FindOGRE.cmake:318 (find_package)
/usr/lib/x86_64-linux-gnu/cmake/gazebo/gazebo-config.cmake:175 (find_package)
CMakeLists.txt:14 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.