branding och namechange
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
# Decoder, IP, and AMMC configuration
|
||||
|
||||
This guide explains how physical MyLaps/AMB decoders connect to JMK RB RaceController. It uses this example network:
|
||||
This guide explains how physical MyLaps/AMB decoders connect to RC RaceCore. It uses this example network:
|
||||
|
||||
| Device | Example address | Purpose |
|
||||
|---|---:|---|
|
||||
| RaceController/backend | `192.168.1.100` | Runs Node.js, AMMC processes, web UI, and API |
|
||||
| RC RaceCore/backend | `192.168.1.100` | Runs Node.js, AMMC processes, web UI, and API |
|
||||
| Operator laptop | `192.168.1.50` | Opens the web UI; does not run AMMC |
|
||||
| Main decoder | `192.168.1.10` | Start/finish and lap counting |
|
||||
| Split decoder | `192.168.1.11` | Optional intermediate timing |
|
||||
@@ -28,7 +28,7 @@ Replace these addresses with addresses from your own LAN.
|
||||
```text
|
||||
car transponder -> physical loop -> physical decoder with its own IP
|
||||
-> AMMC process on backend -> unique backend WebSocket port
|
||||
-> browser/RaceController -> active session, results, statistics
|
||||
-> browser/RC RaceCore -> active session, results, statistics
|
||||
```
|
||||
|
||||
Complete example:
|
||||
|
||||
Reference in New Issue
Block a user