Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

MeshCore 1.18.0 – RAK4631 / RAK19007 poweroff draws 0.8 mA and blue LED stays on

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
embedded-iot

调研方向

Start at the firmware code for the shutdown and poweroff CLI commands, then trace the RAK4631 power-down path and the Bluetooth LED GPIO handling. Reproduce the reported 0.8 mA draw and illuminated blue LED after poweroff; done means the LED turns off and the board reaches a lower current state, with measurements confirming the change.

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

描述

Hardware:

  • RAK4631 on RAK19007 WisBlock Base Board (USB-C)

  • Battery powered via JST-PHR-2 connector

  • Official MeshCore Companion firmware 1.18.0

Observation:

I tested the new shutdown and poweroff CLI commands introduced with firmware 1.18.0.

Both commands disconnect Bluetooth and put the device into a low-power state. The device can be restarted using the hardware RESET button.

However, the blue Bluetooth LED remains continuously illuminated after shutdown.

Current measurements:

Measured directly in series with the battery at the JST connector:

Operating state | Current -- | -- Normal operation, BLE disconnected | 7.0 mA Normal operation, BLE connected | 6.3–7.0 mA After poweroff | 0.8 mA

Expected behavior:

After poweroff, I would expect the blue LED to turn off and the device to enter the lowest possible power-consumption state.

Could the LED GPIO state or another peripheral be responsible for the remaining 0.8 mA?

The new poweroff feature is very useful for portable battery-powered Companion devices. Reducing the remaining current consumption would make it even better.

Thank you for your work on MeshCore!

主要语言
C
星标
3.9k
派生
1.5k
平均合并
18 小时 59 分钟
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

meshcore-dev/MeshCore 的其他 Issue

查看 meshcore-dev/MeshCore 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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