Skip to content

[FEATURE] Beacon Contact Support#721

Open
mjonuschat wants to merge 3 commits intoFrix-x:developfrom
mjonuschat:feature/beacon-contact
Open

[FEATURE] Beacon Contact Support#721
mjonuschat wants to merge 3 commits intoFrix-x:developfrom
mjonuschat:feature/beacon-contact

Conversation

@mjonuschat
Copy link
Collaborator

Implement support for Beacon Contact

This work is based on #637, incorporating the requested changes and implementing some bugfixes like reducing the probing temperature.

At the moment this PR expects the user to (manually) add the Beacon MCU to their overrides

@cdedwards
Copy link

This works well. I needed to remove some entries in my overrides.cfg but otherwise it seems to work very well.

@cdedwards
Copy link

maybe I spoke too soon. I had to remove alot from the beacon_contact.cfg file. home_xy_position can't be used.

@mjonuschat
Copy link
Collaborator Author

maybe I spoke too soon. I had to remove alot from the beacon_contact.cfg file. home_xy_position can't be used.

Can you provide some more details? What did you have to remov? My overrides since creating the PR are pretty short and home_xy_position seems to work:

[beacon]
serial: /dev/serial/by-id/usb-Beacon_Beacon_RevH_BACE57925154364134202020FF141921-if00
home_xy_position: 150, 150
home_y_before_x: True
x_offset: -23.8

@cdedwards
Copy link

This is my beacon_contact.cfg in config/hardware/probes

[gcode_macro _USER_VARIABLES]

We can declare an "inductive_virtual" probe type as it's pretty close to the Beacon way of working and should just work!

variable_probe_type_enabled: "beacon_contact"
variable_startprint_actions: "bed_soak", "extruder_preheating", "chamber_soak", "clean", "beacon_calib", "tilt_calib", "bedmesh", "z_offset", "extruder_heating", "purge", "clean"

gcode:

Beacon probe definition also include the probe management macros directly from here

[include ../../../macros/base/probing/generic_probe.cfg]
[include ../../../macros/base/homing/homing_beacon_contact.cfg]

[stepper_z]
endstop_pin: probe:z_virtual_endstop
homing_retract_dist: 0

[beacon]
#home_z_hop: 5
#home_z_hop_speed: 30
#home_xy_move_speed: 350
#home_method: contact
#home_method_when_homed: proximity
#home_autocalibrate: unhomed
#home_gcode_pre_x: _HOME_PRE_AXIS AXIS=X
#home_gcode_post_x: _HOME_POST_AXIS AXIS=X
#home_gcode_pre_y: _HOME_PRE_AXIS AXIS=Y
#home_gcode_post_y: _HOME_POST_AXIS AXIS=Y
#home_gcode_pre_xy: _HOME_XY STAGE=pre
#home_gcode_post_xy: _HOME_XY STAGE=post
contact_activate_gcode: ACTIVATE_PROBE
contact_deactivate_gcode: DEACTIVATE_PROBE
contact_max_hotend_temperature: 180

without removing all the home_'s as well as the adding max_hotend_temperature, my printer will not start.

@mjonuschat
Copy link
Collaborator Author

That seems very weird, not sure why none of the beacon config settings would work for you. What is the exact error message when they are enabled, can you upload a fresh klipper.log that includes the error?

@cdedwards
Copy link

image [klippy.log](https://github.com/user-attachments/files/23291241/klippy.log)

@mjonuschat
Copy link
Collaborator Author

Just to confirm, you're on Beacon Firmware 2.0 or newer - because those config options all got added in that firmware version.

@mjonuschat
Copy link
Collaborator Author

And it looks like the log didn't upload properly

@cdedwards
Copy link

klippy.log

@cdedwards
Copy link

and yes I'm updated to latest on beacon firmware.

@smweil
Copy link

smweil commented Nov 26, 2025

Having the exact same issue. Firmware up to date on the beacon and klipper on the latest...

@mjonuschat
Copy link
Collaborator Author

Having the exact same issue. Firmware up to date on the beacon and klipper on the latest...

Do you mind uploading a Klipper.log that show the error? The last log was inconclusive.
Also just to make sure, you're on the develop branch?

@smweil
Copy link

smweil commented Nov 26, 2025

I fixed the issue, you must include in [beacon]
home_xy_position: 150, 150

for the module to load properly.

@mjonuschat
Copy link
Collaborator Author

Sweet, I'll see how to incorporate it into the PR or set a safe default value

@mjonuschat
Copy link
Collaborator Author

Beacon config will be checked on startup to make sure home_xy_position has been defined:

Screenshot 2025-12-02 at 19 42 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants