Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Handling of COMMAND-parameters: info-text not shown

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
lua
Domain
embedded-iot

Research direction

Start by locating the Lua handling for command-parameter responses and compare it with the COMMAND sequence diagram in the linked CRSF specification. Reproduce a device response with ready status (0x00) and an info-text such as "OK" or "Failed"; done means that text is displayed as it is in the TBS Agent.

Written by the indexing model from the issue text.

Description

If the LUA starts a command-parameter, it writes (0x2d) the parameter with status (0x01).

If the device immediate executes the command if may - according to the TBS specs - answer with status (ready: 0x00) and send an additional info-text (like "OK" or "Failed").

But this info-text isn't displayed.

Refer to the sequence diagram: https://github.com/tbs-fpv/tbs-crsf-spec/blob/main/crsf.md#command
The last arrow shows the info text in the frame (status: ready, Info: "OK").

I think this is missing in the LUA

The TBS Agent seems to work correctly in this regard.

Dominant language
Lua
Stars
13
Forks
6
Avg merge
2d 21h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExpressLRS/Lua

All issues in ExpressLRS/Lua

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.