micro-ROS / micro-ROS/system_modes

Error in node state when switching modes

未關閉
#99 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
C++
星號
45
分支
13
PR 合併指標
30 天內沒有已合併 PR

描述

Hello!

I've been working with system_modes for a few days and I'm having an error when changing my system mode.

I have several modes, which are default, alert, compromised and halt, and in this particular example when I change the mode from alert to compromised there are nodes that do not change their status from active to inactive. I leave you images of the monitor so that you can see the result together with the yaml configuration of both modes.

```
ALERT:
image_1_to_2: inactive
imu_1_to_2: active
odom_1_to_2: active
pc2_1_to_2: active
scan_1_to_2: active
tf_1_to_2: active
tf_static_1_to_2: active
twist_2_to_1: active
COMPROMISED:
image_1_to_2: inactive
imu_1_to_2: active
odom_1_to_2: active
pc2_1_to_2: inactive
scan_1_to_2: inactive
tf_1_to_2: active
tf_static_1_to_2: active
twist_2_to_1: inactive
```
System in alert mode:
![Screenshot from 2022-12-20 11-08-47](https://user-images.githubusercontent.com/44479765/208641297-4330e612-6507-4f02-9892-7e2adf2c8fac.png)

System in compromised mode:
![Screenshot from 2022-12-20 11-08-36](https://user-images.githubusercontent.com/44479765/208641324-70392290-c993-4d99-baf2-d1b1c37923e1.png)

I also show you how I have configured the modes of some of the nodes, although I am not using that parameter

```
pc2_1_to_2:
ros__parameters:
type: node
modes:
__DEFAULT__:
ros__parameters:
use_sim_time: false

scan_1_to_2:
ros__parameters:
type: node
modes:
__DEFAULT__:
ros__parameters:
use_sim_time: false
```

I do not have any type of rule configured, although I suppose that for this simple case of changing node states it would not be necessary.

Any idea what is happening?

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

報告未提供原始檔案或測試;先從 ALERT 和 COMPROMISED YAML 以及列出的節點狀態螢幕擷取畫面開始,然後在所述 ROS 2 設定中重現從警報到受損狀態的轉換。追蹤 pc2_1_to_2、scan_1_to_2 和 twist_2_to_1 持續作用的原因,並驗證每個節點都達到為 COMPROMISED 宣告的狀態。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
cpp
領域
robotics
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。