Klipper Updates - why do I do this to myself!?

[TitusADuxass]

I asked on the Beacon Users help on that there discord (horrible) and received this response:

Timer too close means a system overload as in timings couldn't be met. This can be caused by the new Beacon change because the more efficient position recovery code no longer works after klipper update. This affects all current eddy current based probes so it's not specific to beacon. In your case the sysload is only .62, so would likely need to drill down further to figure out where to optimize. Good choice is always to setup up CPU isolation (isolcpus) first.

I am even more clueless now!

 

[NikosSprocket]

I do not use Beacon and I have no experience with any eddy current probes. Try/search Klipper and Beacon. That means all Beacon users cannot update Klipper? I doubt that.

Some info. from Klipper discourse (not discord) about the latest releases:

https://klipper.discourse.group/t/can-interface-down-after-reboot-pi4-mainsailos-2-2-0/24950/6

 

[PFarm]

4 minutes ago, NikosSprocket said:

I do not use Beacon and I have no experience with any eddy current probes. Try/search Klipper and Beacon. That means all Beacon users cannot update Klipper? I doubt that.

Some info. from Klipper discourse (not discord) about the latest releases:

https://klipper.discourse.group/t/can-interface-down-after-reboot-pi4-mainsailos-2-2-0/24950/6

Appreciate the info, but like @TitusADuxass mentioned, some of us who have the BTT Manta use BTT CB1. The CB1 is not on the MainSail list, only Pi boards on bookworm. BTT Pi is on Debian 12.

[TitusADuxass]

5 hours ago, NikosSprocket said:

I do not use Beacon and I have no experience with any eddy current probes. Try/search Klipper and Beacon. That means all Beacon users cannot update Klipper? I doubt that.

Some info. from Klipper discourse (not discord) about the latest releases:

https://klipper.discourse.group/t/can-interface-down-after-reboot-pi4-mainsailos-2-2-0/24950/6

My 25-can.network does not have the RestartSec=0.1s line.

And, if I try to bring up the network with sudo ip link set can0 up type can bitrate 1000000

it returns with Cannot find device "can0"

I think I am going first try reflashing the O2 Toolboard with a reduced amout of the extras enabled.

If that fails it case start again from scratch with esoterics guide.

[PFarm]

 

Found this on Discord:

[PFarm]

@TitusADuxass Using the above fix, I was able to upgrade via SSH. Then updated Klipper and Beacon on both Trident and V2, both are up and printing.  Any luck with yours?

[SamppaD]

Hi to everyone. Finally had some time to changed a new  fast samsung sd card and cable hi speed 3.1 that comes between rpi and octopus board.  
Started printing long print,got paused due to filament run out triggered and after that start printing again but midway printer just stop printing,
klipper screen is frozen,connection to moonraker/mainsail lost. 
This Klipper update is making me crazy,not happy about this at all.  
There is no work around this issue,cant ssh,cant access mainsail,touchscreen frozen. 
There is no other way to get printer working but cycle the power switch.  Working printer is now broken due to klipper update. 
I don't know what to do next any ideas? Is there a way to downgrade this Klipper update crap to get printer working as intended?

moonraker (1).log klippy (2).zip

Edited October 11, 2025 by SamppaD

[PFarm]

@SamppaD You should be able to downgrade using Kiauh. 

[SamppaD]

Hi. I will downgrade it using Kiauh thanks for the tip.  I was trouble shooting this issue last night,as mentioned,sd card and cable replaced. Run every stress test on RPI to rull out overheating and power issues..temperature stay at 46-47C at full load 1.5ghz.

No issues detected during stress-test klipper screen respond normally.
Desided to checked power supply for octopus and rpi. 24V 14A supply outputing 24.2V at terminal side  and at the octopus side 24.2V and rpi supply outputting 5.1V 5A, at the gpio power pins measured 5.03V. Cables are as thick as connectors on gpio  will accept to be crimped so 0.07V 
power loss over short distance? 
I don't like it,just in case need to replace thicker cables and adjust power supply to 5.2V (genuine rpi power supply outputs 5.2V) ..
Im searching for a screw terminal that can be connected to gpio pins,and will accept thicker cables...
Does any one know where to get this connector?

Edited October 12, 2025 by SamppaD
Update

[TitusADuxass]

No matter what I do I cannot clear this error - 

MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. 

Neither can I see which MCU is "overloaded".

It looks like a full reinstall is going to be necessary. 

[SamppaD]

Done some testing,checked all connectors to stepper motors,re-check connections to power supplies,checked grounding points for frame and grounds 
between power supplies and rpi/octopus. Everything checked OK. 
However I found out that 0.07V  power drop on RPI4 power pins is due chamber light. So That Meanwell 5V5A psu is under load.  I adjusted output to 5.2V.This power supply is delivering power to chamber lights and a RPI. Under printing conditions RPI cpu load is under 20% , MCU at 1%, memory usage 10%. 
Chamber light count is 54.White light takes a lot of amps. Set chamber lighting to blue to reduce power load on the supply..So its testing time...if this doesnt help then its downgrade time.
I have a Meanwell 5V 10A supply but will not fit in to electronic bay.

Edited October 12, 2025 by SamppaD

[TitusADuxass]

15 minutes ago, SamppaD said:

Done some testing,checked all connectors to stepper motors,re-check connections to power supplies,checked grounding points for frame and grounds 
between power supplies and rpi/octopus. Everything checked OK. 
However I found out that 0.07V  power drop on RPI4 power pins is due chamber light. So That Meanwell 5V5A psu is under load.  I adjusted output to 5.2V.This power supply is delivering power to chamber lights and a RPI. Under printing conditions RPI cpu load is under 10% and chamber light leds 
count is 54.White light takes a lot of amps. Set chamber lighting to blue to reduce power load on the supply..So its testing time...if this doesnt help then its downgrade time.
I have a Meanwell 5V 10A supply but will not fit in to electronic bay.

54 neopixels running white are going to draw a large amount of current. I used some plain warmweiss LED strips powered via a heater output on the mainboard. 

[SamppaD]

 

1 hour ago, TitusADuxass said:

54 neopixels running white are going to draw a large amount of current. I used some plain warmweiss LED strips powered via a heater output on the mainboard. 

Hi. Yes you are correct. Originally ordered 24V strips but got a 5V instead. Due to that had to connect leds to RPI psu. 
I did a cold start test,full load,all leds on,with rpi on and checked with a clamp meter,  power consumption was 2.22A 11.09W using AWG 18 cable  
expected voltage drop was 0.3V. Done a thermal camera check also and no heatspots at cables or terminals. 
So yes RPI needs 3A at full load and leds 2.22A..thats over psu limit but RPI never uses 3A in normal case scenario however its possible
that power needed spikes at some point and this can make problems. 
I will remove one strip so total 36 leds remain. So expected current consumption should be around 1.48A with a voltage  drop of 0.253v.

At the moment test printing with chamber light set to minimum,color blue,and again lost connection to moonraker after 30 min of printing, no ssh,no mainsail connection but klipper screen works,printing fine...

Lets make some changes and test again...

 

 

Edited October 12, 2025 by SamppaD

[TitusADuxass]

On 10/10/2025 at 4:02 PM, PFarm said:

@TitusADuxass Using the above fix, I was able to upgrade via SSH. Then updated Klipper and Beacon on both Trident and V2, both are up and printing.  Any luck with yours?

I did that, it did a raft of updates but I still get the same error when trying to print.

This is the beacon part of the klippy log before I send a print:

 

Executing Beacon update script failed: Traceback (most recent call last):
  File "/home/biqu/klipper/klippy/extras/beacon.py", line 277, in do
    output = subprocess.check_output(
  File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/home/biqu/beacon_klipper/update_firmware.py', 'check', '/dev/serial/by-id/usb-Beacon_Beacon_RevH_4FC744785157355957202020FF113614-if00']' returned non-zero exit status 127.

beacon: loaded fnorm=5129780.95 temp=20.05 amfg=0.907 from nvm
beacon: built tempco model version 1 {'amfg': 0.9067685605279543, 'tcc': -5.776959116755578e-06, 'tcfl': -0.0006535968200513998, 'tctl': 0.0020124779713568196, 'fmin': 5129780.950024724, 'fmin_temp': 20.04865837097168}
Enabling Beacon accelerometer
Selected Beacon accelerometer scale 16g
Configured MCU 'beacon' (0 moves)
Starting heater checks for extruder
Stats 127.1: gcodein=0 mcu: mcu_awake=0.000 mcu_task_avg=0.000000 mcu_task_stddev=0.000000 bytes_write=3336 bytes_read=7791 bytes_retransmit=0 bytes_invalid=0 send_seq=269 receive_seq=269 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=519989224 orbitoolO2: mcu_awake=0.013 mcu_task_avg=0.000022 mcu_task_stddev=0.000026 bytes_write=1229 bytes_read=4202 bytes_retransmit=9 bytes_invalid=0 send_seq=126 receive_seq=126 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=47997164 adj=47997506 Hotend_power: temp=0.0 toolboard: temp=0.0 M8P: temp=0.0 heater_bed: target=0 temp=50.2 pwm=0.000 beacon: mcu_awake=0.000 mcu_task_avg=0.000000 mcu_task_stddev=0.000000 bytes_write=359 bytes_read=2079 bytes_retransmit=0 bytes_invalid=0 send_seq=53 receive_seq=53 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=32003683 adj=32004079 coil_temp=35.6 refs=0 mcu_temp=34.42 supply_voltage=3.028 print_time=0.000 buffer_time=0.000 print_stall=0 extruder: target=0 temp=0.0 pwm=0.000 sysload=0.49 cputime=3.438 memavail=1772004
 

And this is it after the print fail:

 

 

 

klippy (5).log

[SamppaD]

 

On 10/12/2025 at 10:21 AM, TitusADuxass said:

54 neopixels running white are going to draw a large amount of current. I used some plain warmweiss LED strips powered via a heater output on the mainboard. 

Can i use a free heater output to supply 24V to dc to dc converter and then supply voltage to the chamber lights,would this be good solution? This way RPI will be only component connected to the 5V psu. I have a spare 24V to 5V 15A converter and its compact size that i can install in to electronic bay. LRS350 psu is taking a lot of space so Im limited with what i can install.

[NikosSprocket]

I stopped powering up the Pi from the Octapus more than 3 years ago as I was getting a lot of "brownout" warnings from Klipper on Pi power. Since I started powering Pi with an external PSU MEAN WELL 323282 RS-25-5 AC to DC Power Supply, Single Output, 5V, 5 Amp, 25W all these problems were gone away. Also, another thing can be done is to connect the 5V positive lead for the LEDs directly to the 5V PSU. Just wired the PSU the same way you powered your other 24/48V PSUs from 110/220V.

If you have USB camera(s) connected to the Pi they also draw power from the Pi so that's another reason to use an external PSU.

Actually, the Voron team recommends to power-up the Pi from a separate 5V PSU.

[TitusADuxass]

10 hours ago, SamppaD said:

Can i use a free heater output to supply 24V to dc to dc converter and then supply voltage to the chamber lights,would this be good solution? This way RPI will be only component connected to the 5V psu. I have a spare 24V to 5V 15A converter and its compact size that i can install in to electronic bay. LRS350 psu is taking a lot of space so Im limited with what i can install.

You could but why don't you connect the dc-dc converter directly to the 24v PSU?

[SamppaD]

8 hours ago, TitusADuxass said:

You could but why don't you connect the dc-dc converter directly to the 24v PSU?

Hi,Yes i could do that but i only have one free positive screw terminal available on my LRS350 psu,no free ground terminal,all terminals are occupied with thick wires. 
I would need to swap a bigger connector to fit two ground wires under one connector to be able to connect it . 
However that's one option.. After some testing I came to conclusion that RPI 5V5A psu has some issues,non stable output under load, so i will swap RPI psu for a new one. Chamber  lightning then needs some other solution DC to DC  converter would be easy to install but as you suggested connecting chamber lights to 24 v PSU output directly would be the best option.  Added picture is old but you can see limited space issue,bigger RPI PSU is not an option, Meanwell 10A psu is bigger then this 5A version

Edited October 14, 2025 by SamppaD

[NikosSprocket]

Nice cabling job @SamppaD! Mine looks like a ... spaghetti!

In front of the 24V large PSU, is that a 5V PSU?
 

[TitusADuxass]

16 hours ago, SamppaD said:

Hi,Yes i could do that but i only have one free positive screw terminal available on my LRS350 psu,no free ground terminal,all terminals are occupied with thick wires. 
I would need to swap a bigger connector to fit two ground wires under one connector to be able to connect it . 
However that's one option.. After some testing I came to conclusion that RPI 5V5A psu has some issues,non stable output under load, so i will swap RPI psu for a new one. Chamber  lightning then needs some other solution DC to DC  converter would be easy to install but as you suggested connecting chamber lights to 24 v PSU output directly would be the best option.  Added picture is old but you can see limited space issue,bigger RPI PSU is not an 

 

A Wago would help you out there.

[SamppaD]

23 hours ago, NikosSprocket said:

Nice cabling job @SamppaD! Mine looks like a ... spaghetti!

In front of the 24V large PSU, is that a 5V PSU?
 

Hi. That picture was old,here is the latest picture of electronic bay. As you can see on that side is all AC powered stuff,filtered input,wago connectors, omron ssr that is mounted on the custom heatsink,then there is meanwell 5V5A psu and its big brother LRS350 14A psu. On the other side all DC power stuff,octopus pro 1.1 board,RPI4B,small free space left for Klipper expander board...

Edited October 15, 2025 by SamppaD

[SamppaD]

7 hours ago, TitusADuxass said:

A Wago would help you out there.

Jep,Wago is a solution,small and compact.

[NikosSprocket]

4 hours ago, SamppaD said:

Hi. That picture was old,here is the latest picture of electronic bay. As you can see on that side is all AC powered stuff,filtered input,wago connectors, omron ssr that is mounted on the custom heatsink,then there is meanwell 5V5A psu and its big brother LRS350 14A psu. On the other side all DC power stuff,octopus pro 1.1 

.................

It is still very, very nice and clean installation!

The 5Amp Meanwell should provide enough juice to the Pi for all the peripherals, I think. Soon I will be adding a second camera, nozzle camera, which will also connect to the Pi5. I hope will not have any power issues as already have cabinet and toolhead LEDs. 

Just have to actually install the 3DO camera to my toolhead design. On CAD it fits, but I have found out some manufacturers provided CAD drawings of their products that do not much the actual product!

 

 

[SamppaD]

19 hours ago, NikosSprocket said:

It is still very, very nice and clean installation!

The 5Amp Meanwell should provide enough juice to the Pi for all the peripherals, I think. Soon I will be adding a second camera, nozzle camera, which will also connect to the Pi5. I hope will not have any power issues as already have cabinet and toolhead LEDs. 

Just have to actually install the 3DO camera to my toolhead design. On CAD it fits, but I have found out some manufacturers provided CAD drawings of their products that do not much the actual product!

 

Nice,like it...yes 5V5A psu no issues with RPI and usb devices.  I found out that the same way,cad is ok, but product itself is not the same as cad..funny..

[TitusADuxass]

Back on topic.

My v2.4 is back in operation.

I had to do a complete reinstall which included erasing the eMMC on the BTT.

I also reflashed with Debian 12 which in now on BTT's Github.

Plus, I upgraded to a Orbiter Toolboard O2S which had a couple of Gotchas!