2026 remote v2: printable bottom shell, notes for the PC radio link
- Bottom shell: the brace pivot bosses stand on pillars and the lip's tie band steps out at 45 deg (both were floating overhangs); the kickstand barrel sits on the bed. Checked by slicing the STLs layer by layer: only bridges are left. STLs re-exported. - remote_v2_top_multicolor.3mf: now the owner's OrcaSlicer project (all parts on two plates); export_3mf.py regenerates the plain multi-part file. - README "Planned": a USB nRF24 stick on the PC so Unity can talk to both the robot and the remote (what to work out), plus pointers to the other notes for later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
60605209fb
commit
80270ba17e
6 files changed
+44
-11
No files matched your search
@@ -75,6 +75,32 @@ Hardware (besides the electronics of the old remote):
|
||||
|
||||
Design notes, checks and open points: [hardware/openscad/PLANNING.md](hardware/openscad/PLANNING.md).
|
||||
|
||||
## Planned
|
||||
|
||||
- **PC radio link (owner, later):** a USB nRF24L01 stick on the PC (it
|
||||
probably shows up as a serial port), on the same radio as the robot and the
|
||||
remote, so Unity on the PC can both receive data from (telemetry) and send
|
||||
data to the robot and the remote. Not designed yet. To work out:
|
||||
- what the stick's firmware does: many of these sticks are a USB-serial
|
||||
chip with a microcontroller set up by AT commands (address, channel, data
|
||||
rate) that passes raw payloads through; check that it can match
|
||||
`HXP_RADIO_*` in `shared/HexapodProtocol/HexapodProtocol.h` (channel 96,
|
||||
250 kbps, 5-byte address `HXPD1`, fixed payload of `sizeof(CmdPacket)`)
|
||||
and whether it can do auto-ack and ack payloads;
|
||||
- the radio protocol: today the remote only transmits a `CmdPacket` to the
|
||||
robot and nothing comes back. Three nodes need an address per node (or
|
||||
per pipe), a packet type byte, and telemetry back (e.g. as ack payloads
|
||||
or in time slots) so the nodes don't talk over each other; who has
|
||||
priority when the PC and the remote both send commands;
|
||||
- Unity side: a serial-port reader/writer next to the simulation (the
|
||||
2019 generation already drove the robot from Unity, through the remote
|
||||
over USB: see `../2019-teensy-nrf24/`).
|
||||
- Remote battery level and the IMU on the normal pin headers: see
|
||||
[remote/README.md](remote/README.md), "Planned".
|
||||
- Robot power: a stable 6 V supply for the 18 servos, see
|
||||
[hardware/openscad/PLANNING.md](hardware/openscad/PLANNING.md), "Notes for
|
||||
future designs".
|
||||
|
||||
## Where to go next
|
||||
|
||||
- **[robot/README.md](robot/README.md)**: placeholder geometry to measure,
|
||||
|
||||
Reference in new issue
Block a user