mirror of
https://github.com/BotChain-Robots/firmware.git
synced 2026-07-08 17:47:21 +02:00
updates to topology with flatbuffers
This commit is contained in:
@@ -12,6 +12,8 @@ To run the sample code, add the compiler variable `RMT_TEST=1` when compiling: `
|
||||
|
||||
With `main_rmt_test.cpp`, flash one or more boards, ensuring that `BOARD_ID` are unique and `RECEIVER_BOARD_ID` is a board that exists and is connected on the same network.
|
||||
|
||||
Please note that `SRC_BOARD` and `RECEIVER_BOARD` should be an 8 bit value (that is not 0x0 or 0xFF).
|
||||
|
||||
### Example Usage:
|
||||
|
||||
Board A: `idf.py -B ./build_A build -D SRC_BOARD=1 -D RECEIVER_BOARD=69 -D RMT_TEST=1 flash monitor -p COM3`
|
||||
@@ -32,6 +34,14 @@ When monitoring both boards, you should see `Received message '%.*s' on channel
|
||||
|
||||
The specific message being sent can vary depending on the setup (determined at compile time). Simply changing the `snprintf` on the `send_buf` and/or `FrameType` argument of `send()` will change the message/frames being sent (from the perspective of the user).
|
||||
|
||||
# Preprogrammed Movements Sample Code
|
||||
|
||||
See `main_preprogrammed_test.cpp`.
|
||||
|
||||
To run the sample code, add the compiler variable `PP_MOVE=1` when compiling.
|
||||
|
||||
You can use the `SRC_BOARD` compiler variable to set a custom board id.
|
||||
|
||||
# cat
|
||||
|
||||
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣴⣿⣿⡷⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
|
||||
|
||||
Reference in New Issue
Block a user