diff --git a/10-systems/hardware/3d-printers.md b/10-systems/hardware/3d-printers.md index 9924cb5..626eb7f 100644 --- a/10-systems/hardware/3d-printers.md +++ b/10-systems/hardware/3d-printers.md @@ -13,10 +13,10 @@ ## Inventory -### Modified Creality Ender 3 V2 (Klipper) +### Modified Creality Ender 2 V3 (Klipper) - Inventory id: `klipper-3d-printer`. -- Base model: Creality Ender 3 V2 (owner-corrected 2026-10-11; previously misrecorded as Ender 2 V3). +- Base model: Creality Ender 2 V3 (owner-confirmed 2026-10-11; briefly misrecorded as Ender 3 V2 earlier the same day). - Modification level: deep. - Controller: Raspberry Pi 3 Model B Rev 1.2, hostname `ender`, user `gmikcon`. - Firmware/control stack: Klipper `v0.13.0-562-g7a4472649`. diff --git a/90-maintenance/pending-changes/20261011134508-9f7034ce.json b/90-maintenance/pending-changes/20261011134508-9f7034ce.json new file mode 100644 index 0000000..47730f5 --- /dev/null +++ b/90-maintenance/pending-changes/20261011134508-9f7034ce.json @@ -0,0 +1,19 @@ +{ + "id": "20261011134508-9f7034ce", + "kind": "doc", + "target": "10-systems/hardware/3d-printers.md", + "summary": "Возврат модели Klipper-принтера: Ender 2 V3 (правка на Ender 3 V2 была ошибкой)", + "reason": "Владелец подтвердил: правильная база — Ender 2 V3, правка на Ender 3 V2 была его ошибкой", + "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 2 V3 (Klipper)\n\n- Inventory id: `klipper-3d-printer`.\n- Base model: Creality Ender 2 V3 (owner-confirmed 2026-10-11; briefly misrecorded as Ender 3 V2 earlier the same day).\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:45:08Z", + "updated_at": "2026-10-11T13:45:10Z", + "applied_at": "2026-10-11T13:45:10Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}