Printer cancels randomly (Timer too close)

[kennygunner]

Basic Information:

Printer Model: DIY kinematics: cartesian
MCU / Printerboard: Octopus Pro / ebb42
Host / SBC : PI3
klippy.log

hello my printer always crashes randomly, I have now restricted the error to the webcam!
is always the same error: in the log
Receive: 92 5939.870377 5939.778534 14: seq: 1e, analog_in_state oid=27 next_clock=1334841408 value=8061
Receive: 93 5939.880777 5939.817670 15: seq: 1f, analog_in_state oid=28 next_clock=1336641408 value=31481
Receive: 94 5939.996803 5939.935739 11: seq: 15, clock clock=1304707997
Receive: 95 5940.080795 5940.016405 15: seq: 1a, analog_in_state oid=18 next_clock=1372641408 value=31426
Receive: 96 5940.160412 5940.075735 14: seq: 1d, analog_in_state oid=26 next_clock=1387041408 value=7637
Receive: 97 5940.170369 5940.075735 14: seq: 1d, analog_in_state oid=27 next_clock=1388841408 value=8061
Receive: 98 5940.180511 5940.112298 15: seq: 1e, analog_in_state oid=28 next_clock=1390641408 value=31462
Receive: 99 5940.181247 5940.122199 12: seq: 1f, shutdown clock=1338074185 static_string_id=Timer too close

the time is calculated incorrectly…

what else can I do to get the webcam running again?

Timer too close

Background A “Timer too close” error occurs when the MCU attempts to schedule a timer for a target time that is in the past. It almost always occurs as a result of a message from the host requesting an action at a time that is now in the past. It is important to understand that Klipper essentially knows which command was scheduled in the past, but not why it happened. For example, a message is delayed because the webcam is blocking the USB port: The message contains a command whose target time …

I have already worked through the report

abort always comes from Octopus pro… where can is made via bridging function… would it help to switch to extra u2c?

Printer ran for 10 days when debian10 was still running with a webcam… error is only turned up since I changed to debain 11 and CAN bus.

klippy (9).log (5.9 MB)

[kennygunner]

hello, my post can be closed! i found the error … it was CAN via Octopus pro board via the bridges function. with extra CAN to USB board error did not appear anymore!