Beacon Rev H Probe randomly disconnects

General Discussion
1

Basic Information:

Printer Model: Ratrig V-Core 3.1
MCU / Printerboard: Raspberry Pi 4B (8 GB) + BTT Octopus v1.1 (F446)
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…
I recently wired up the beacon rev H sensor to my Ratrig V-Core 3.1 and initially, all the calibration worked fine. However, when I ran BED_MESH_CALIBRATE, I had too many probe points set (100, 100 instead of 10, 10), so the printer scanned the bed and then Klipper shut down. I did a klipper/firmware restart and updated the bed mesh to only probe a 10x10 grid, but ever since, the beacon sensor isn’t being detected by Klipper. When I run ls /dev/serial/by-id/*, I only see the Octopus, even though I have the beacon USB cable connected to the pi.

I have not been able to successfully reconnect with the Beacon Sensor and am not sure what I need to do to fix this issue.
klippy.log (7.0 MB)

2

The Beacon is closed source and not part of mainline Klipper. You need to reach out to the creators of the Beacon for support.

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.