From 1d36153f01da3a4d207c4bcb62c446642d7b6b1c Mon Sep 17 00:00:00 2001 From: ted-miller Date: Thu, 14 Sep 2023 14:09:07 -0400 Subject: [PATCH 1/9] Add missing troubleshooting items --- doc/troubleshooting.md | 79 ++++++++++++++++++++++++++++++++++++++++++ src/ErrorHandling.h | 12 +++---- 2 files changed, 85 insertions(+), 6 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 6bc11f16..0ddb21bd 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -582,6 +582,33 @@ The name must not be blank. After correcting the configuration, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). +### Alarm: 8011[23 - 54] + +*Example:* + +```text +ALARM 8011 + Failed creating/adding/init *something* +[23] - [54] +``` + +*Solution:* +Ensure that the ROS2 version (Galactic, Humble, etc) is the same for MotoROS2, the micro-ROS Agent and the client PC. +Additionally, ensure that the ROS2 version is one that is [officially supported](https://github.com/Yaskawa-Global/motoros2#general-requirements) by MotoROS2. + +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). +Describe the problem and include the following items: + + - `PANELBOX.LOG` + - output from debug listener script (complete and unedited) + - version of MotoROS2 + - version of micro-ROS Agent + - version of ROS2 on client PC + - copy of the MotoROS2 yaml configuration file + - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). + + ### Alarm: 8011[55] *Example:* @@ -609,6 +636,58 @@ Refer to [FAQ: Can names of joints be changed?](faq.md#can-names-of-joints-be-ch After correcting the configuration, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). +### Alarm: 8011[56 - 58] + +*Example:* + +```text +ALARM 8011 + Failed creating/adding/init *something* +[56] - [58] +``` + +*Solution:* +Ensure that the ROS2 version (Galactic, Humble, etc) is the same for MotoROS2, the micro-ROS Agent and the client PC. +Additionally, ensure that the ROS2 version is one that is [officially supported](https://github.com/Yaskawa-Global/motoros2#general-requirements) by MotoROS2. + +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). +Describe the problem and include the following items: + + - `PANELBOX.LOG` + - output from debug listener script (complete and unedited) + - version of MotoROS2 + - version of micro-ROS Agent + - version of ROS2 on client PC + - copy of the MotoROS2 yaml configuration file + - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). + +### Alarm: 8011[60 - 62] + +*Example:* + +```text +ALARM 8011 + Must enable ETHERNET function +[60 - 61] +``` + +*Solution:* +The ETHERNET function must be enabled for one (or both) LAN interface in the robot controller. +Please contact your local Yaskawa representative to request this function. + +### Alarm: 8011[59] + +*Example:* + +```text +ALARM 8011 + Host on NIC check x +[59] +``` + +*Solution:* + ### Alarm: 8012[xx] *Example:* diff --git a/src/ErrorHandling.h b/src/ErrorHandling.h index f88731b6..f604be6e 100644 --- a/src/ErrorHandling.h +++ b/src/ErrorHandling.h @@ -91,7 +91,7 @@ typedef enum SUBCODE_EXECUTOR, SUBCODE_INCREMENTAL_MOTION, SUBCODE_ADD_TO_INC_Q, -} TASK_CREATE_FAIL_SUBCODE; +} TASK_CREATE_FAIL_SUBCODE; //8010 typedef enum { @@ -165,14 +165,14 @@ typedef enum SUBCODE_CONFIGURATION_FAIL_MP_NICDATA1, SUBCODE_FAIL_MP_NICDATA_INIT1, -} ASSERTION_SUBCODE; +} ASSERTION_SUBCODE; //8011 typedef enum { SUBCODE_ALLOCATION_MALLOC, SUBCODE_ALLOCATION_CALLOC, SUBCODE_ALLOCATION_REALLOC, -} ALLOCATION_SUBCODE; +} ALLOCATION_SUBCODE; //8012 typedef enum { @@ -193,7 +193,7 @@ typedef enum SUBCODE_CONFIGURATION_INVALID_USERLAN_MONITOR_PORT, SUBCODE_CONFIGURATION_USERLAN_MONITOR_AUTO_DETECT_FAILED, SUBCODE_CONFIGURATION_RUNTIME_USERLAN_LINKUP_ERR, -} CONFIGURATION_SUBCODE; +} CONFIGURATION_SUBCODE; //8013 typedef enum { @@ -201,7 +201,7 @@ typedef enum SUBCODE_INFORM_INVALID_JOB, SUBCODE_INFORM_FAIL_TO_CREATE_JOB, SUBCODE_INFORM_FAIL_TO_LOAD_JOB, -} INFORM_SUBCODE; +} INFORM_SUBCODE; //8014 typedef enum { @@ -210,7 +210,7 @@ typedef enum SUBCODE_DAT_FAIL_PARSE_MGROUP, SUBCODE_DAT_FAIL_PARSE_SGROUP, SUBCODE_DAT_FAIL_PARSE_SRANG -} DAT_SUBCODE; +} DAT_SUBCODE; //8015 extern void motoRosAssert(BOOL mustBeTrue, ASSERTION_SUBCODE subCodeIfFalse); extern void motoRosAssert_withMsg(BOOL mustBeTrue, ASSERTION_SUBCODE subCodeIfFalse, char* msgFmtIfFalse, ...); From 2af3598ced3f4e0d7e07aa97a6a40b395b0bbdd8 Mon Sep 17 00:00:00 2001 From: ted-miller Date: Thu, 14 Sep 2023 14:16:21 -0400 Subject: [PATCH 2/9] Satisfy linter --- doc/troubleshooting.md | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 0ddb21bd..37e0db73 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -600,14 +600,13 @@ If the behavior persists, save a copy of the [debug-listener script](#debug-log- Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). Describe the problem and include the following items: - - `PANELBOX.LOG` - - output from debug listener script (complete and unedited) - - version of MotoROS2 - - version of micro-ROS Agent - - version of ROS2 on client PC - - copy of the MotoROS2 yaml configuration file - - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). - +- `PANELBOX.LOG` +- output from debug listener script (complete and unedited) +- version of MotoROS2 +- version of micro-ROS Agent +- version of ROS2 on client PC +- copy of the MotoROS2 yaml configuration file +- verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). ### Alarm: 8011[55] @@ -654,13 +653,13 @@ If the behavior persists, save a copy of the [debug-listener script](#debug-log- Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). Describe the problem and include the following items: - - `PANELBOX.LOG` - - output from debug listener script (complete and unedited) - - version of MotoROS2 - - version of micro-ROS Agent - - version of ROS2 on client PC - - copy of the MotoROS2 yaml configuration file - - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). +- `PANELBOX.LOG` +- output from debug listener script (complete and unedited) +- version of MotoROS2 +- version of micro-ROS Agent +- version of ROS2 on client PC +- copy of the MotoROS2 yaml configuration file +- verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). ### Alarm: 8011[60 - 62] From bc8dab36526e339fbdd147cc6d76ade1eb255561 Mon Sep 17 00:00:00 2001 From: ted-miller Date: Fri, 15 Sep 2023 14:10:51 -0400 Subject: [PATCH 3/9] Edits from review --- doc/troubleshooting.md | 73 ++++++++++++++++++++++++++++-------------- 1 file changed, 49 insertions(+), 24 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 37e0db73..d6e798d1 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -459,7 +459,7 @@ ALARM 8011 *Solution:* Check the [setup instructions](../README.md#installation) to ensure that the robot controller is configured properly. -If the behavior persists, save a copy of the debug-listener script output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -588,24 +588,31 @@ After correcting the configuration, the [changes will need to be propagated to t ```text ALARM 8011 - Failed creating/adding/init *something* + MotoROS2: Fatal Error + Failed adding ... + Failed to init ... + Failed creating ... [23] - [54] ``` *Solution:* -Ensure that the ROS2 version (Galactic, Humble, etc) is the same for MotoROS2, the micro-ROS Agent and the client PC. -Additionally, ensure that the ROS2 version is one that is [officially supported](https://github.com/Yaskawa-Global/motoros2#general-requirements) by MotoROS2. +These alarms are often caused by version incompatibilities between ROS 2 (on the client PC), micro-ROS (as part of MotoROS2) and/or the micro-ROS Agent. + +Ensure only compatible versions are used. + +As an example: the *Humble* version of MotoROS2 should only be used with ROS 2 *Humble* on the client PC and with the *Humble* version of the micro-ROS Agent. +Please also verify the client PC uses a version of ROS 2 that is [supported by MotoROS2](https://github.com/Yaskawa-Global/motoros2#general-requirements). If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). Describe the problem and include the following items: - `PANELBOX.LOG` -- output from debug listener script (complete and unedited) +- output from [debug-listener script](#debug-log-client) (complete and unedited) - version of MotoROS2 - version of micro-ROS Agent -- version of ROS2 on client PC -- copy of the MotoROS2 yaml configuration file +- version of ROS 2 on client PC +- copy of `motoros2_config.yaml` copied from the robot controller - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). ### Alarm: 8011[55] @@ -641,51 +648,69 @@ After correcting the configuration, the [changes will need to be propagated to t ```text ALARM 8011 - Failed creating/adding/init *something* + MotoROS2: Fatal Error + Failed adding ... + Failed to init ... + Failed creating ... [56] - [58] ``` *Solution:* -Ensure that the ROS2 version (Galactic, Humble, etc) is the same for MotoROS2, the micro-ROS Agent and the client PC. -Additionally, ensure that the ROS2 version is one that is [officially supported](https://github.com/Yaskawa-Global/motoros2#general-requirements) by MotoROS2. +These alarms are often caused by version incompatibilities between ROS 2 (on the client PC), micro-ROS (as part of MotoROS2) and/or the micro-ROS Agent. + +Ensure only compatible versions are used. + +As an example: the *Humble* version of MotoROS2 should only be used with ROS 2 *Humble* on the client PC and with the *Humble* version of the micro-ROS Agent. +Please also verify the client PC uses a version of ROS 2 that is [supported by MotoROS2](https://github.com/Yaskawa-Global/motoros2#general-requirements). If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). Describe the problem and include the following items: - `PANELBOX.LOG` -- output from debug listener script (complete and unedited) +- output from [debug-listener script](#debug-log-client) (complete and unedited) - version of MotoROS2 - version of micro-ROS Agent -- version of ROS2 on client PC -- copy of the MotoROS2 yaml configuration file +- version of ROS 2 on client PC +- copy of `motoros2_config.yaml` copied from the robot controller - verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). -### Alarm: 8011[60 - 62] +### Alarm: 8011[59] *Example:* ```text ALARM 8011 - Must enable ETHERNET function -[60 - 61] + Host on NIC check x +[59] ``` *Solution:* -The ETHERNET function must be enabled for one (or both) LAN interface in the robot controller. -Please contact your local Yaskawa representative to request this function. -### Alarm: 8011[59] +The `agent_ip_address` key in the `motoros2_config.yaml` configuration file is an address that is not reachable by the robot controller. + +Options: + +1. Modify the `agent_ip_address` key and specify an IP address that is on the robot's subnet. + Now follow the instructions [to propagate the changes to the Yaskawa controller](../README.md#updating-the-configuration). +2. Modify the robot controller's IP so it is on the Agent's subnet. +3. Modify the robot controller's network settings to add a gateway which can reach the Agent's IP address. + +Refer to the relevant Yaskawa Motoman documentation for information on how to change the controller's network configuration. + +### Alarm: 8011[60 - 62] *Example:* ```text ALARM 8011 - Host on NIC check x -[59] + Must enable ETHERNET function +[60 - 61] ``` *Solution:* +The ETHERNET function must be enabled for one (or both) LAN interface in the robot controller. +Please contact your local Yaskawa representative to request this function. ### Alarm: 8012[xx] @@ -700,7 +725,7 @@ ALARM 8012 *Solution:* Verify there are no other MotoPlus applications (`.out` file) installed on the robot controller. -If the behavior persists, save a copy of the debug-listener script output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -926,7 +951,7 @@ If auto-detection is to be used, verify `agent_ip_address` is set to an IP that After correcting the configuration, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). -If the behavior persists, save a copy of the debug-listener script output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -949,7 +974,7 @@ If the alarm is raised again, make sure `userlan_monitor_port` is set to the cor If the configuration file has to be updated, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). -If the behavior persists, save a copy of the debug-listener script output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). From 7bd865a468922cb445ff3a3f1943927831dd8067 Mon Sep 17 00:00:00 2001 From: "G.A. vd. Hoorn" Date: Tue, 19 Sep 2023 09:16:08 +0200 Subject: [PATCH 4/9] Don't combine example alarm msgs --- doc/troubleshooting.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index d6e798d1..92bb74fd 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -590,7 +590,23 @@ After correcting the configuration, the [changes will need to be propagated to t ALARM 8011 MotoROS2: Fatal Error Failed adding ... +[23] - [54] +``` + +or: + +```text +ALARM 8011 + MotoROS2: Fatal Error Failed to init ... +[23] - [54] +``` + +or: + +```text +ALARM 8011 + MotoROS2: Fatal Error Failed creating ... [23] - [54] ``` @@ -650,7 +666,23 @@ After correcting the configuration, the [changes will need to be propagated to t ALARM 8011 MotoROS2: Fatal Error Failed adding ... +[56] - [58] +``` + +or: + +```text +ALARM 8011 + MotoROS2: Fatal Error Failed to init ... +[56] - [58] +``` + +or: + +```text +ALARM 8011 + MotoROS2: Fatal Error Failed creating ... [56] - [58] ``` From d6ae4ca992f99c86b4bd781c6e66239a4e3b5032 Mon Sep 17 00:00:00 2001 From: "G.A. vd. Hoorn" Date: Tue, 19 Sep 2023 09:22:24 +0200 Subject: [PATCH 5/9] Refer to `8011[23 - 54]` text instead of duplicating it --- doc/troubleshooting.md | 47 +----------------------------------------- 1 file changed, 1 insertion(+), 46 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 92bb74fd..d63caeef 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -660,52 +660,7 @@ After correcting the configuration, the [changes will need to be propagated to t ### Alarm: 8011[56 - 58] -*Example:* - -```text -ALARM 8011 - MotoROS2: Fatal Error - Failed adding ... -[56] - [58] -``` - -or: - -```text -ALARM 8011 - MotoROS2: Fatal Error - Failed to init ... -[56] - [58] -``` - -or: - -```text -ALARM 8011 - MotoROS2: Fatal Error - Failed creating ... -[56] - [58] -``` - -*Solution:* -These alarms are often caused by version incompatibilities between ROS 2 (on the client PC), micro-ROS (as part of MotoROS2) and/or the micro-ROS Agent. - -Ensure only compatible versions are used. - -As an example: the *Humble* version of MotoROS2 should only be used with ROS 2 *Humble* on the client PC and with the *Humble* version of the micro-ROS Agent. -Please also verify the client PC uses a version of ROS 2 that is [supported by MotoROS2](https://github.com/Yaskawa-Global/motoros2#general-requirements). - -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. -Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). -Describe the problem and include the following items: - -- `PANELBOX.LOG` -- output from [debug-listener script](#debug-log-client) (complete and unedited) -- version of MotoROS2 -- version of micro-ROS Agent -- version of ROS 2 on client PC -- copy of `motoros2_config.yaml` copied from the robot controller -- verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). +Please refer to [Alarm: 8011[23 - 54]](#alarm-801123---54). ### Alarm: 8011[59] From 7b45057a4f50c291b96aa91e9f4410926f2a965c Mon Sep 17 00:00:00 2001 From: "G.A. vd. Hoorn" Date: Tue, 19 Sep 2023 09:30:39 +0200 Subject: [PATCH 6/9] Clarify which subcodes this section applies to --- doc/troubleshooting.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index d63caeef..c9a3a800 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -590,7 +590,7 @@ After correcting the configuration, the [changes will need to be propagated to t ALARM 8011 MotoROS2: Fatal Error Failed adding ... -[23] - [54] +[xx] ``` or: @@ -599,7 +599,7 @@ or: ALARM 8011 MotoROS2: Fatal Error Failed to init ... -[23] - [54] +[xx] ``` or: @@ -608,9 +608,11 @@ or: ALARM 8011 MotoROS2: Fatal Error Failed creating ... -[23] - [54] +[xx] ``` +Where `[xx]` is a subcode in the ranges `[23 - 54]` or `[56 - 58]`. + *Solution:* These alarms are often caused by version incompatibilities between ROS 2 (on the client PC), micro-ROS (as part of MotoROS2) and/or the micro-ROS Agent. From a19b1f2423bb6c5f1d11ab677cea71be32b50b60 Mon Sep 17 00:00:00 2001 From: gavanderhoorn Date: Tue, 19 Sep 2023 09:39:27 +0200 Subject: [PATCH 7/9] Emphasise we need the output of the debug logger not the script itself. --- doc/troubleshooting.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index c9a3a800..8f71efd1 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -459,7 +459,7 @@ ALARM 8011 *Solution:* Check the [setup instructions](../README.md#installation) to ensure that the robot controller is configured properly. -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the output of the [debug-listener script](#debug-log-client) and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -621,7 +621,7 @@ Ensure only compatible versions are used. As an example: the *Humble* version of MotoROS2 should only be used with ROS 2 *Humble* on the client PC and with the *Humble* version of the micro-ROS Agent. Please also verify the client PC uses a version of ROS 2 that is [supported by MotoROS2](https://github.com/Yaskawa-Global/motoros2#general-requirements). -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the output of the [debug-listener script](#debug-log-client) and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues). Describe the problem and include the following items: @@ -714,7 +714,7 @@ ALARM 8012 *Solution:* Verify there are no other MotoPlus applications (`.out` file) installed on the robot controller. -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the output of the [debug-listener script](#debug-log-client) and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -940,7 +940,7 @@ If auto-detection is to be used, verify `agent_ip_address` is set to an IP that After correcting the configuration, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the output of the [debug-listener script](#debug-log-client) and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). @@ -963,7 +963,7 @@ If the alarm is raised again, make sure `userlan_monitor_port` is set to the cor If the configuration file has to be updated, the [changes will need to be propagated to the Yaskawa controller](../README.md#updating-the-configuration). -If the behavior persists, save a copy of the [debug-listener script](#debug-log-client) output and the `PANELBOX.LOG` from the robot's teach pendant. +If the behavior persists, save a copy of the output of the [debug-listener script](#debug-log-client) and the `PANELBOX.LOG` from the robot's teach pendant. Open a new issue on the [Issue tracker](https://github.com/yaskawa-global/motoros2/issues), describe the problem and attach `PANELBOX.LOG` and the debug log to the issue. Include a verbatim copy of the alarm text as seen on the teach pendant (alarm number and `[subcode]`). From bdb62cb0186cd3bae22a09a72517d0dd3f42d45f Mon Sep 17 00:00:00 2001 From: ted-miller Date: Tue, 19 Sep 2023 16:47:53 -0400 Subject: [PATCH 8/9] Range is [60-62] --- doc/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index 8f71efd1..c9993128 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -694,7 +694,7 @@ Refer to the relevant Yaskawa Motoman documentation for information on how to ch ```text ALARM 8011 Must enable ETHERNET function -[60 - 61] +[60 - 62] ``` *Solution:* From 1d7603b7d8b65b4f5a14a35975a2649127f11380 Mon Sep 17 00:00:00 2001 From: "G.A. vd. Hoorn" Date: Wed, 20 Sep 2023 16:23:31 +0200 Subject: [PATCH 9/9] Clarify what `x` is in the desc of `8011[59]` --- doc/troubleshooting.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/troubleshooting.md b/doc/troubleshooting.md index c9993128..2ec89880 100644 --- a/doc/troubleshooting.md +++ b/doc/troubleshooting.md @@ -674,9 +674,10 @@ ALARM 8011 [59] ``` -*Solution:* +Where `x` is either `1` or `2`. -The `agent_ip_address` key in the `motoros2_config.yaml` configuration file is an address that is not reachable by the robot controller. +*Solution:* +This problem is often caused by the `agent_ip_address` key in the `motoros2_config.yaml` configuration file set to an address that is not reachable by the robot controller. Options: