Conversation
|
This works well. I needed to remove some entries in my overrides.cfg but otherwise it seems to work very well. |
|
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: |
|
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" gcode: Beacon probe definition also include the probe management macros directly from here[include ../../../macros/base/probing/generic_probe.cfg] [stepper_z] [beacon] without removing all the home_'s as well as the adding max_hotend_temperature, my printer will not start. |
|
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? |
|
Just to confirm, you're on Beacon Firmware 2.0 or newer - because those config options all got added in that firmware version. |
|
And it looks like the log didn't upload properly |
|
and yes I'm updated to latest on beacon firmware. |
|
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. |
|
I fixed the issue, you must include in [beacon] for the module to load properly. |
|
Sweet, I'll see how to incorporate it into the PR or set a safe default value |


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