victor/p21-print
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Test the BEEP command #1

New issue
Closed
opened 2026-07-18 19:56:56 +00:00 by victor · 1 comment
victor commented 2026-07-18 19:56:56 +00:00
Owner
Copy link
No description provided.
victor commented 2026-07-18 20:00:00 +00:00
Author
Owner
Copy link

Fixed in 0f9c69e. Root cause: the BEEP command needs a space before the on/off byte (BEEP + 0x01/0x00), matching BATTERY?/CONFIG?; we were sending BEEP + byte with no space, so it had no effect.

Verified on hardware:

  • config round-trips: beep --off -> CONFIG? reports beep off; beep -> reports on
  • audible: the beeper sounds

Note: on the tested unit, enabling makes it beep continuously until turned off, so p21 beep / p21 beep --off act as an on/off switch. Added a unit test locking the exact byte format (BEEP \x01\r\n / BEEP \x00\r\n).

Fixed in 0f9c69e. Root cause: the BEEP command needs a space before the on/off byte (`BEEP ` + 0x01/0x00), matching BATTERY?/CONFIG?; we were sending `BEEP` + byte with no space, so it had no effect. Verified on hardware: - config round-trips: `beep --off` -> CONFIG? reports beep off; `beep` -> reports on - audible: the beeper sounds Note: on the tested unit, enabling makes it beep continuously until turned off, so `p21 beep` / `p21 beep --off` act as an on/off switch. Added a unit test locking the exact byte format (`BEEP \x01\r\n` / `BEEP \x00\r\n`).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.2.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
victor/p21-print#1
No description provided.