2026 remote v2: clamps for the 56x80 perfboard, generated inlay 3MF
- remote_v2.scad: main board is the measured 56 x 80 mm perfboard, held by 4 side clamps (M3 button head + washer into inserts), no holes in the board - export_3mf.py writes remote_v2_top_inlays.3mf (top shell + honeycomb + ON/OFF on filaments 1/2/3); remote_v2_top_multicolor.3mf stays the owner's OrcaSlicer project - STLs re-exported, README printing table and PLANNING notes updated Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
80270ba17e
commit
4aeb79dc89
6 files changed
+22
-16
No files matched your search
@@ -54,8 +54,9 @@ Regenerate them from `remote_v2.scad` with `-D 'PART="..."'`.
|
||||
|
||||
| File | Part | Notes |
|
||||
|------|------|-------|
|
||||
| `remote_v2_top_multicolor.3mf` | top shell with both inlays | One object with three parts on filaments 1/2/3: case black, honeycomb red, ON/OFF white. The inlays are the first 3 layers (0.6 mm) of the face-down shell, so the colour swaps only happen there. Made by `hardware/openscad/export_3mf.py` from the three STLs below |
|
||||
| `remote_v2_top_inlays.3mf` | top shell with both inlays | One object with three parts on filaments 1/2/3: case black, honeycomb red, ON/OFF white. The inlays are the first 3 layers (0.6 mm) of the face-down shell, so the colour swaps only happen there. Made by `hardware/openscad/export_3mf.py` from the three STLs below |
|
||||
| `remote_v2_top.stl` + `_inlay.stl` + `_text.stl` | the same, as STLs | Load the three at once and keep them as one multi-part object |
|
||||
| `remote_v2_top_multicolor.3mf` | OrcaSlicer project (owner) | all parts on two plates; after re-exporting STLs, update its parts with Orca's "Reload from disk" |
|
||||
| `remote_v2_bottom.stl` | bottom shell | flat underside on the bed |
|
||||
| `remote_v2_kickstand.stl` | table stand | |
|
||||
| `remote_v2_eyelet.stl` | neck-strap eyelet | on the top face (slots to balance it) or on the front edge |
|
||||
@@ -91,7 +92,12 @@ Design notes, checks and open points: [hardware/openscad/PLANNING.md](hardware/o
|
||||
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;
|
||||
priority when the PC and the remote both send commands. Owner's
|
||||
decisions: the remote wins, with a toggle on the remote that hands the
|
||||
robot to Unity and lets the remote's sticks control Unity instead; the
|
||||
PC is the hub while it's online, the robot is the hub when it isn't;
|
||||
goals: mirror the real robot in Unity, drive it from Unity, remote data
|
||||
to the PC, and PC data to the remote;
|
||||
- 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/`).
|
||||
|
||||
Reference in new issue
Block a user