Commit Graph
5 Commits
Author SHA1 Message Date
mangavalkandClaude Opus 5.5 7761e8f803 BDP_TOUCH: one quick continuous press instead of small steps
Stepping down 0.005 mm at a time found no touch even 0.25 mm into the bed
(peak 16): the sensor sets a new baseline by itself while the force looks
steady, and the slow ramp looked steady. A quick press gave about 25 per
0.1 mm. BDP_TOUCH now lowers the nozzle in one drip-mode move (SPEED,
default 0.3 mm/s) while a timer reads the force every few ms and stops the
move at STOP; Z per reading comes from stepper_z's past position, the halt
position is recovered like homing.py does. The threshold needs 3 readings
in a row, and the curve is logged also when no touch was found.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 17:24:12 +01:00
mangavalkandClaude Opus 5.5 b16961dba3 TOUCH_COMPARE: Beacon contact vs bd_pressure touch (extras/bdp_touch.py)
bd_pressure's endstop output is not wired, so BDP_TOUCH lowers the nozzle
in small steps and reads the force after each one, up to a force limit
(default 80) or 0.4 mm below the start, then lifts back. It reports the
threshold height and the zero-force height from a line fit and logs the
curve to klippy.log. TOUCH_COMPARE heats the nozzle to 150C, homes, and
alternates Beacon's contact probe with BDP_TOUCH at one spot, reporting
mean, spread and range of each and of the difference. Refuses while the
bdp_guard is armed or the sensor is in PA mode.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 16:58:20 +01:00
mangavalkandClaude Opus 5.5 f25f348d0b Motion lights outside the G-code queue (extras/motion_lights.py)
The AM312 case light and nozzle LEDs waited for long commands (heat waits,
AFC loads, QGL) because [gcode_button] runs through the G-code queue. The
new module reads the pin itself, keeps the timeout on a reactor timer and
sets the case light with output_pin's send_async_request and the nozzle
LEDs directly on the led_effect object. CASELIGHT and _LIGHTS_ON keep
working; _STATUS_SHOW reads printer.motion_lights.near.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 00:35:26 +01:00
mangavalkandClaude Opus 5.5 e5be65834e LEDs: nozzle light follows the motion sensor, new logo status macro
The motion timeout switched the nozzle LEDs off during prints, motion
switched them off when idle or paused, the timeout counted from the first
movement, and every _status_* macro stopped the nozzle light.

- _LIGHTS sets case light and nozzle LEDs from presence, print state and
  CASELIGHT MODE=AUTO|ON|OFF; the timeout (60 s) starts at the sensor
  release
- _STATUS STATE=... replaces the _status_* macros; logo effects only
  cover the logo LEDs and use REPLACE=1
- heater gauge while heating, print progress, paused, error flash from
  _ERROR, part ready once the bed is cool, dim night mode when idle and
  nobody near, cleaning during BLOBIFIER_CLEAN
- removed unused effects and macros, 12 fps for the toolhead effects

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 19:32:42 +02:00
mangavalkandClaude Opus 5.5 eaf9c82617 Group macros by topic, add Blobifier, fix first tool change
- Split the macro files into folders by topic (print, heating, afc,
  pressure_advance, spoolman, leds, sensors); klipper-macros.cfg is the
  one file printer.cfg includes. Macros moved unchanged; the effective
  config is identical apart from the paths of the PA shell scripts.
- Add the modified Blobifier (Turtleblobifier for AFC) and define
  [save_variables] once in save_variables.cfg instead of in both
  blobifier.cfg and the PA macros (same file, bd_pa_variables.cfg).
- PRINT_WARMUP: heat to the loaded lane's temperature before the first
  tool change. AFC skips heating when the loaded lane's tool number is
  not in the print file's temperature list, and the unload then failed
  below min_extrude_temp.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 14:24:37 +02:00