micro-ROS / micro-ROS/micro-ROS-demos

Demo similar to multithread_publisher_subscriber from rclc but in Zephyr. Multithreading not working as espected.

未关闭
#83 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
C
星标
101
派生
35
平均合并
4 天 16 小时
30 天内合并 PR
3

描述

## Issue template

- Hardware description: Olimex STM32-E407
- RTOS: Zephyr
- Installation type: -
- Version or commit hash: -

#### Steps to reproduce the issue
Install Micro-Ros like in the Tutorial: [Tutorial Micro-ROS and Zephyr](https://micro.ros.org/docs/tutorials/core/first_application_rtos/zephyr/)

Then add this App from this Repository: [Micro-ROS and Zephyr](https://github.com/Johannes-42/microROS_Zephyr-)
If that is run It will publish 2 numbers from 2 threads. The main thread and the second created thread.
But if the publisher in the main thread is commented out. Also, the second thread will not publish anymore.
Is that wanted behavior or am I doing something wrong?

#### Expected behavior
Multithreaded Threads can publish their publishers

#### Actual behavior
Multithreaded Threads only publish if the main thread is publishing.

#### Additional information
I also tried it with a timer, then the second thread will publish only if the timer is used and in the same time interval.

I want to use Micro-ROS multithreaded to give some threads a higher priority than others. One more question to that would be if it is possible to start multiple apps in Zephyr? something like:
ros2 run micro_ros_setup configure_firmware.sh ping_pong ping_pong2 --transport serial-usb
This command would not work but is there a way to run 2 apps?

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从 Zephyr 教程和所引用的 Micro-ROS 与 Zephyr 应用开始,然后将其双线程 publisher 设置与 rclc multithread_publisher_subscriber 示例进行比较。在 Olimex STM32-E407 上复现该行为,并确定是否支持独立线程发布以及运行多个 app;记录已确认的行为以及所需的更改或限制。

由索引模型根据 Issue 内容生成。

评估

技术栈
c
领域
embedded-iot, operating-systems
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
30/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。