Serial Bus #1: Add Serial Bus Module to handle multiple ESPs#175
Merged
JensOgorek merged 30 commits intomainfrom Dec 18, 2025
Merged
Serial Bus #1: Add Serial Bus Module to handle multiple ESPs#175JensOgorek merged 30 commits intomainfrom
JensOgorek merged 30 commits intomainfrom
Conversation
a3248f8 to
212ae62
Compare
falkoschindler
approved these changes
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a SerialBus module so multiple ESP32-based Lizard nodes can share one UART link with a single coordinator that orchestrates traffic round-robin style.
Commands:
bus.send(receiver, payload)– enqueue a point-to-point frame (payload must fit in 256 bytes, no newlines).bus.make_coordinator(peer_ids...)– marks this node as coordinator and loads the peer poll order.How it works:
Each instance runs a background FreeRTOS task that reads
$$sender:receiver$$payloadframes from UART, parses control words (__POLL__,__DONE__,__BUS_RESPONSE__), and either executes remote commands or enqueues outbound traffic. Coordinators open transmit windows for their peers in turn and enforce timeouts; non-coordinators only transmit while polled, then reply with__DONE__once their queue is flushed.