diff --git a/10-systems/hardware/3d-printers.md b/10-systems/hardware/3d-printers.md index 76a4d9a..9924cb5 100644 --- a/10-systems/hardware/3d-printers.md +++ b/10-systems/hardware/3d-printers.md @@ -1,50 +1,49 @@ --- owner: gmikcon status: active -last_reviewed: 2026-05-10 +last_reviewed: 2026-10-11 review_interval: 180d -confidence: medium +confidence: high source_of_truth: owner-described-and-network-observed --- # 3D Printers -This document records the known 3D-printing devices in the home infrastructure. It is intentionally high-level until exact IP addresses, management UIs, and operational workflows are confirmed. +This document records the known 3D-printing devices in the home infrastructure. Both printers are networked devices with local management surfaces and physical side effects. ## Inventory -### Modified Creality Ender 2 V3 +### Modified Creality Ender 3 V2 (Klipper) - Inventory id: `klipper-3d-printer`. -- Base model: Creality Ender 2 V3. +- Base model: Creality Ender 3 V2 (owner-corrected 2026-10-11; previously misrecorded as Ender 2 V3). - Modification level: deep. -- Controller: Raspberry Pi. -- Firmware/control stack: Klipper. +- Controller: Raspberry Pi 3 Model B Rev 1.2, hostname `ender`, user `gmikcon`. +- Firmware/control stack: Klipper `v0.13.0-562-g7a4472649`. - Network: `home-lan`. - Address: `192.168.1.102`. - Management UI: Mainsail at `http://192.168.1.102/`. -- API: Moonraker at `http://192.168.1.102:7125/`. +- API: Moonraker `v0.10.0-9-g3fbe6ee` (API 1.5.0) at `http://192.168.1.102:7125/`, no authorization required on LAN. - SSH: `192.168.1.102:22`, credentials not documented. +- Webcam: crowsnest installed. +- Config: `printer.cfg` in Moonraker `config` root; gcodes root holds ~35 gcode files (recent: hatch controller box, cover_ABS, single relay cover top v1.1). -Observed Moonraker status: +Observed Moonraker status (2026-10-11): -- `klippy_connected`: `true`. -- `klippy_state`: `ready`. -- Moonraker version: `v0.10.0-9-g3fbe6ee`. -- API version: `1.5.0`. -- Registered directories: `config`, `logs`, `gcodes`, `config_examples`, `docs`. +- `klippy_connected`: `true`, `klippy_state`: `ready`. +- Printer state: `standby`, bed 23.0 C, extruder 22.9 C. ### Bambu Lab A1 - Inventory id: `bambulab-a1-3d-printer`. -- Vendor/model: Bambu Lab A1. -- Type: 3D printer. -- Network: local network, exact address not yet documented. -- Management UI/API: not yet documented. - -The Bambu Lab A1 should be treated as a closed appliance, not as a normal Linux host. SSH access is not expected. Local control, when enabled, is normally based on Bambu's LAN/access-code flow and Bambu Studio-compatible tooling rather than direct shell access. - -There are community reports of FTPS support on some Bambu Lab printer series using the printer access code, but this must be verified against this specific A1 before documenting it as active. +- Vendor/model: Bambu Lab A1 (model code BBL-P003), serial `03919D581204930` (from TLS certificate CN). +- Network: `home-lan`, address `192.168.1.251`. +- Mode: LAN-only confirmed (cloud ports 21/1883/2025/60000 closed; RTSP 554/322 closed — no RTSP camera stream). +- Local control (verified 2026-10-11): + - MQTT over TLS on port `8883`, login `bblp` + LAN access code. Publish `device/{serial}/request`, subscribe `device/{serial}/report`. Self-signed BBL CA certificate — client must skip verification. + - Implicit FTPS on port `990`, login `bblp` + LAN access code. Roots: `model` (factory 3MF samples), `cache` (sliced gcodes and owner projects), `timelapse`, `image`, `logger`, `recorder`, `ipcam`. +- Access code: stored in gnexus-creds, secret title `Bambu Lab A1 (LAN)`. Do not copy the code into this repository. +- Capabilities via MQTT: live status (temperatures, progress, layer), pause/stop/resume, print speed, G-code lines. Starting a new print in LAN mode is done from the printer screen or Bambu Studio; file upload via FTPS. ## Documentation Policy @@ -63,10 +62,5 @@ ## Open Questions -- Which network each printer uses: `home-lan` or `home-iot-lan`. -- Whether either printer has a static DHCP lease. -- Exact IP addresses and hostnames. -- Klipper UI stack: Mainsail, Fluidd, OctoPrint, or another interface. -- Whether Bambu Lab A1 is used only locally or through Bambu cloud features. -- Bambu Lab A1 IP address. -- Whether Bambu Lab A1 exposes LAN-only or FTPS endpoints in the current firmware. +- Whether either printer has a static DHCP lease (both currently observed on DHCP). +- Monitoring/alerting integration (print failed/finished) — planned, not yet configured. diff --git a/90-maintenance/pending-changes/20261011134412-87ee1837.json b/90-maintenance/pending-changes/20261011134412-87ee1837.json new file mode 100644 index 0000000..d2840e0 --- /dev/null +++ b/90-maintenance/pending-changes/20261011134412-87ee1837.json @@ -0,0 +1,19 @@ +{ + "id": "20261011134412-87ee1837", + "kind": "doc", + "target": "10-systems/hardware/3d-printers.md", + "summary": "Исправлена модель Klipper-принтера на Ender 3 V2; зафиксированы проверенные сетевые факты A1 (IP, порты, LAN-only) и Ender 3 V2", + "reason": "Владелец уточнил модель Klipper-принтера (Ender 3 V2); сетевые факты обоих принтеров проверены сканированием и живыми подключениями 2026-10-11", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-10-11\nreview_interval: 180d\nconfidence: high\nsource_of_truth: owner-described-and-network-observed\n---\n\n# 3D Printers\n\nThis document records the known 3D-printing devices in the home infrastructure. Both printers are networked devices with local management surfaces and physical side effects.\n\n## Inventory\n\n### Modified Creality Ender 3 V2 (Klipper)\n\n- Inventory id: `klipper-3d-printer`.\n- Base model: Creality Ender 3 V2 (owner-corrected 2026-10-11; previously misrecorded as Ender 2 V3).\n- Modification level: deep.\n- Controller: Raspberry Pi 3 Model B Rev 1.2, hostname `ender`, user `gmikcon`.\n- Firmware/control stack: Klipper `v0.13.0-562-g7a4472649`.\n- Network: `home-lan`.\n- Address: `192.168.1.102`.\n- Management UI: Mainsail at `http://192.168.1.102/`.\n- API: Moonraker `v0.10.0-9-g3fbe6ee` (API 1.5.0) at `http://192.168.1.102:7125/`, no authorization required on LAN.\n- SSH: `192.168.1.102:22`, credentials not documented.\n- Webcam: crowsnest installed.\n- Config: `printer.cfg` in Moonraker `config` root; gcodes root holds ~35 gcode files (recent: hatch controller box, cover_ABS, single relay cover top v1.1).\n\nObserved Moonraker status (2026-10-11):\n\n- `klippy_connected`: `true`, `klippy_state`: `ready`.\n- Printer state: `standby`, bed 23.0 C, extruder 22.9 C.\n\n### Bambu Lab A1\n\n- Inventory id: `bambulab-a1-3d-printer`.\n- Vendor/model: Bambu Lab A1 (model code BBL-P003), serial `03919D581204930` (from TLS certificate CN).\n- Network: `home-lan`, address `192.168.1.251`.\n- Mode: LAN-only confirmed (cloud ports 21/1883/2025/60000 closed; RTSP 554/322 closed — no RTSP camera stream).\n- Local control (verified 2026-10-11):\n - MQTT over TLS on port `8883`, login `bblp` + LAN access code. Publish `device/{serial}/request`, subscribe `device/{serial}/report`. Self-signed BBL CA certificate — client must skip verification.\n - Implicit FTPS on port `990`, login `bblp` + LAN access code. Roots: `model` (factory 3MF samples), `cache` (sliced gcodes and owner projects), `timelapse`, `image`, `logger`, `recorder`, `ipcam`.\n- Access code: stored in gnexus-creds, secret title `Bambu Lab A1 (LAN)`. Do not copy the code into this repository.\n- Capabilities via MQTT: live status (temperatures, progress, layer), pause/stop/resume, print speed, G-code lines. Starting a new print in LAN mode is done from the printer screen or Bambu Studio; file upload via FTPS.\n\n## Documentation Policy\n\n3D printers are infrastructure-relevant because they are networked devices with local management surfaces and physical side effects.\n\nDocument:\n\n- static or reserved IP addresses;\n- management UI/API endpoints;\n- controller host details for the Klipper printer;\n- update and backup procedures for printer configuration;\n- whether the device requires internet/cloud access;\n- firewall or network-isolation constraints.\n\nDo not document account passwords, API tokens, cloud credentials, or printer access secrets.\n\n## Open Questions\n\n- Whether either printer has a static DHCP lease (both currently observed on DHCP).\n- Monitoring/alerting integration (print failed/finished) — planned, not yet configured." + }, + "status": "applied", + "created_at": "2026-10-11T13:44:12Z", + "updated_at": "2026-10-11T13:44:14Z", + "applied_at": "2026-10-11T13:44:14Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}