Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Dynamic packet power

Abierto
  • ¿Algo no está bien?
#3,621 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
embedded-iot, networking

Línea de trabajo

Start by locating the packet forwarding and radio transmit paths in the C code, then trace how destination or next-hop routing information and recorded SNR are available when a packet is repeated. Compare a static per-node power table with SNR-based scaling and check how either interacts with the global TX setting. Done means repeated packets use appropriately scaled power for the intended link while wider-mesh packets retain the configured maximum; the proposal names no files or tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Proposal Draft
Title: [Feature Request] Dynamic Per-Packet TX Power Scaling for Asymmetric Link Budgets
The Problem
Off-grid, solar-powered repeaters deployed to bridge a specific shadowed node (e.g., a user located in an RF depression) waste critical battery capacity and solar budget due to a single global TX power setting. A repeater is currently forced to transmit at maximum power (e.g., 1W / 30 dBm) to reach a companion node that is only a short distance away, simply because that maximum power is required for the repeater to reach the wider mesh network.
The Use Case
Hardware: A 1W-capable repeater (e.g., RAK19007 + RAK13302) powered by dual 2W solar panels, servicing a local companion node located nearby but in a terrain hole.
Current Limitation: A global set tx 22 command forces the repeater to transmit at maximum power for every packet it repeats. This drains the battery bank faster than small solar panels can replenish it during low-sun conditions, especially when repeating heavy traffic.
The Inefficiency: The link budget required to hit the nearby companion node is small, but the link budget required to reach the broader mesh is large. The repeater cannot scale its output down when it only needs to throw a packet a short distance to the known companion node.
Proposed Behavior & Ideal API
Implement dynamic TX power scaling based on the packet's destination or next-hop routing path.
Behavior: When repeating a packet where the destination is a known local node with a high Signal-to-Noise Ratio (SNR), the radio dynamically drops the TX register (e.g., to 10-15 dBm) for that specific transmission. When repeating a packet out to the wider mesh, it utilizes the maximum configured global TX setting.
Implementation Options: This could be achieved via a user-defined static power routing table linking specific Node IDs to specific TX power limits, or by automatically scaling the output power based on the last recorded SNR of the target node.
Outcome: Drastically reduces peak current draw on solar-constrained repeaters and minimizes unnecessary RF noise on the local airwaves.

Lenguaje dominante
C
Estrellas
3.9k
Forks
1.5k
Merge medio
1 d 1 h
PR fusionados (30 d)
26

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de meshcore-dev/MeshCore

Todos los issues de meshcore-dev/MeshCore

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.