I'm going round in circles!

[TitusADuxass]

So, I found the solution for No Beacon Model Loaded.  - Home X, Home Y, move toolhead to centre of build (not really necessary) and Beacon_Calibrate -

Communication lost with O2S!

Firmware restart...

Communcation lost with MCU!

ls /dev/serail/by-id still shows them as present.

[Huminio]

Do you see any errors related to USB devices in system log? (Not klipper logs)

[TitusADuxass]

In an act of desperation, I removed the Beacon and went back to a Z stop switch.

It's working again!

So, either the Beacon is bad and is sending corrupt messages to the Pi or the Pi is bad (overloaded?).

I ruled out the USB cable earlier and I had the same errors when I ran the Beacon via the O2S.

I'm going to give it a 4 hour print job this evening and see what happens.

[NikosSprocket]

12 hours ago, mvdveer said:

There was an e-mail address in the log file that flagged the need for moderation

Thanks for finding the reason @mvdveer.

I just found it!

@TitusADuxass kernel is signed, probably the person who custom compiled the linux kernel, by not an official Debian resource.

Linux: Linux version 6.12.47+rpt-rpi-v8 (email)

vs.

Linux: Linux version 6.12.47+rpt-rpi-2712 

[NikosSprocket]

7 hours ago, TitusADuxass said:

In an act of desperation, I removed the Beacon and went back to a Z stop switch.

It's working again!

 

So, either the Beacon is bad and is sending corrupt messages to the Pi or the Pi is bad (overloaded?).

I ruled out the USB cable earlier and I had the same errors when I ran the Beacon via the O2S.

I'm going to give it a 4 hour print job this evening and see what happens.

Does the Beacon getting power separately or from the Pi?

I have found out that all these peripherals "prefer" direct power supply from a PSU as the Pi cannot handle any spikes.

I used to power the LEDs from the Pi and I had random shutdowns, especially during printing.

Since then, I have re-wired all peripheral power to PCUs, 5V and 24V and I never had another unexplained shutdown.

[mvdveer]

11 hours ago, TitusADuxass said:

I did a home and got error - No Beacon Model Loaded. I've encountered this error before. But, I can't remember the solution.

Reinstall the beacon module. On the Pi:

cd ~/beacon_klipper
./beacon_klipper/install.sh

 

[TitusADuxass]

7 hours ago, mvdveer said:

Reinstall the beacon module. On the Pi:

cd ~/beacon_klipper
./beacon_klipper/install.sh

I've done that many times already.

[TitusADuxass]

8 hours ago, NikosSprocket said:

Does the Beacon getting power separately or from the Pi?

I have found out that all these peripherals "prefer" direct power supply from a PSU as the Pi cannot handle any spikes.

I used to power the LEDs from the Pi and I had random shutdowns, especially during printing.

Since then, I have re-wired all peripheral power to PCUs, 5V and 24V and I never had another unexplained shutdown.

The Beacon is powered by the Pi.

[polyneutron]

I use carto and gave my beacons away. Worked in can with Manta m8p v2 and cm4. Now have jabberwocky and it is all usb and works as well as can, but easier to set up. It also has touch mode and uses algorithms for heat.

[polyneutron]

The carto is working with the nighthawk usb pass through. 

[Penatr8tor]

On 12/22/2025 at 10:54 PM, polyneutron said:

I use carto and gave my beacons away.

First time I heard that one.

[polyneutron]

If you are using btt36  for can  they have a pass through for can to the Beacon  and/or Cartographer. It worked for me.

[TitusADuxass]

And, the game continues!

It will print short jobs but falls over when faced with a long job.

I don't believe that the Beacon has failed. I think that there's a comms problem somewhere.

I reflashed both the O2S and the Kraken and now ls /dev/serial/by-id shows 2 O2S and no Kraken!

[NikosSprocket]

11 hours ago, TitusADuxass said:

I reflashed both the O2S and the Kraken and now ls /dev/serial/by-id shows 2 O2S and no Kraken!

I know is painful, but probably is time to re-image your Pi from scratch and install only required add-ons like Beacon etc. even skip Katapult and flash the old way!

[TitusADuxass]

9 hours ago, NikosSprocket said:

I know is painful, but probably is time to re-image your Pi from scratch and install only required add-ons like Beacon etc. even skip Katapult and flash the old way!

This is with a Pi4 reimaged with 32 bit lite.

I think that I have a probable cause, I think the umbilical is rubbing on the inside of the lid. The O2S sit quite high on side of the extruder and the mount flexes. The connector is fixed with a cable tie. Maybe the rubbing is causing an intermittent contact. I'm going to try a Mellow HB3 which is a lot lower than the O2S.

[Penatr8tor]

On 12/28/2025 at 1:38 AM, TitusADuxass said:

I think that I have a probable cause, I think the umbilical is rubbing on the inside of the lid.

Interesting that you mentioned that... I too had some umbilical issues on my 2.4. Not with the umbilical rubbing on the top but losing connectivity when I moved the toolhead to 0,0 and the cable got stretched. I created a little more slack and moved on since it solved the problem. So, not a solution per se but definitely confirmation that you're not the only one where the cable connection at the CAN connector isn't the best.

[NikosSprocket]

For my custom toolhead and CPAP system I have incorporated PG7 Cable Gland for every umbilical cable for both ends:

and to keep everything from flapping around, I have printed some TPU rubber holders to guide everything together. Also, to keep the cable/tube curves smoother, I have added a piano wire. At this moment there are 2 wires (CAN and USB nozzle camera)  and the CPAP air tube.

 

PS. The toolhead picture shows only one cable (CAN) as the picture taken before added the nozzle camera!

I am working to add the PG7 Cable Gland for the nozzle camera cable too.

[TitusADuxass]

6 hours ago, NikosSprocket said:

For my custom toolhead and CPAP system I have incorporated PG7 Cable Gland for every umbilical cable for both ends:

and to keep everything from flapping around, I have printed some TPU rubber holders to guide everything together. Also, to keep the cable/tube curves smoother, I have added a piano wire. At this moment there are 2 wires (CAN and USB nozzle camera)  and the CPAP air tube.

PS. The toolhead picture shows only one cable (CAN) as the picture taken before added the nozzle camera!

I am working to add the PG7 Cable Gland for the nozzle camera cable too.

That's my next project.

[TitusADuxass]

I'm still going round in circles.

I mounted a new Fystec H36 combo (USB/CAN) toolhead board and reinstalled the Beacon.

Sent it a print job.

Loss of comms with Beacon!

Removed the Beacon from the configuration, set up the Z stop switch.

Sent it a print job.

Loss of comms with mcu H36 Combo!

I'm getting cheesed off with this now.

 

[polyneutron]

This sounds like a klipper issue. The H36 combo is a high (125) degree tool head. USB doesn't support it so it has to run can. Then it sounds as though your beacon is USB and can't operate above 85 degrees. With that said, flash Beacon firmware to make it can. If the H36 toolboard has a can pass through it will work. Otherwise run can wire  to the Beacon along with 5vdc from your tool board.

[polyneutron]

Your h36 v1.3 tool board has a passion through. It looks like the bottom plug on the right. 

[polyneutron]

Before flashing anything use the upper plug for USB pass through. If the board is can and to use the higher temperature it has to be can. In that situation, don't use the passthrogh. They both should be can or usb not either or.

[TitusADuxass]

18 hours ago, polyneutron said:

This sounds like a klipper issue. The H36 combo is a high (125) degree tool head. USB doesn't support it so it has to run can. Then it sounds as though your beacon is USB and can't operate above 85 degrees. With that said, flash Beacon firmware to make it can. If the H36 toolboard has a can pass through it will work. Otherwise run can wire  to the Beacon along with 5vdc from your tool board.

Sorry, but you've lost me.

The H36 is both CAN and USB. I am using it via USB i.e. it connects directly to the Pi.

The Beacon was wired to the H36.

[polyneutron]

Okay, the H36 is connected with USB through Klipper. Then the Beacon probe has to be usb and use the H36 pass through which is the plug on the H36. Any other touch probe has to be connected to the H36. 

I use the nighthawk and carto, all usb using the nighthawk pass through. Before the nighthawk, I used the ebb36 with carto and all can. It also worked without issue. Mellow fly sht pass through did not work.