[docs](trx-rs): show multi-server topology in README diagram
Replace single-server Mermaid diagram with two trx-servers: one with two SDRs, the other with an SDR and FT-817, both feeding a single trx-client. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Stan Grams <sjg@haxx.space>
This commit is contained in:
@@ -84,17 +84,22 @@ Build without SDR support: `cargo build --release --no-default-features`
|
|||||||
|
|
||||||
```mermaid
|
```mermaid
|
||||||
graph TD
|
graph TD
|
||||||
Radio["Radio / SDR Hardware"] <-->|"serial or USB"| Server["trx-server<br/>rig control, DSP, decoders, audio capture"]
|
SDR1["SDR #1"] & SDR2["SDR #2"] <-->|USB| S1["trx-server A"]
|
||||||
Server <-->|"JSON-TCP :4530"| Client["trx-client<br/>remote connection, audio relay"]
|
SDR3["SDR #3"] & FT817["FT-817"] <-->|USB / serial| S2["trx-server B"]
|
||||||
Server -->|"Opus-TCP :4531"| Client
|
|
||||||
Client <-->|internal channels| F1["Web UI :8080"]
|
S1 <-->|"JSON-TCP :4530"| C1["trx-client"]
|
||||||
Client <-->|internal channels| F2["rigctl :4532"]
|
S1 -->|"Opus-TCP :4531"| C1
|
||||||
Client <-->|internal channels| F3["JSON-TCP"]
|
S2 <-->|"JSON-TCP :4530"| C1
|
||||||
|
S2 -->|"Opus-TCP :4531"| C1
|
||||||
|
|
||||||
|
C1 <-->|internal channels| F1["Web UI :8080"]
|
||||||
|
C1 <-->|internal channels| F2["rigctl :4532"]
|
||||||
|
C1 <-->|internal channels| F3["JSON-TCP"]
|
||||||
```
|
```
|
||||||
|
|
||||||
`trx-server` owns hardware access and runs the DSP pipeline.
|
Each `trx-server` owns one or more rigs and runs DSP, decoding, and audio capture locally.
|
||||||
`trx-client` connects over TCP and exposes user-facing frontends.
|
A `trx-client` connects to any number of servers over TCP and exposes them through
|
||||||
This keeps hardware local to one host while making control available over the network.
|
a unified set of frontends.
|
||||||
|
|
||||||
## Documentation
|
## Documentation
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user