Timer too close SB2040 Pro and Manta M8P V2.0

[oleks]

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: BTT Manta m8p V2.0
Host / SBC CB1
klippy.log
klippy_dmesg_moonraker.zip (2.0 MB)

Describe your issue:

Controller Board: Manta M8p V2.0 with CB1
Stepper Drivers for XY: Fysetc v3.1 tmc2209
Stepper Drivers for Z0-Z3:BTT tmc2209
Motors: LDO 42STH48-2504AC and LDO HT Pancake Nema14
Power Supply: MeanWell 350W
Slicer: Orca

Some prints complete successfully, but often longer prints are interrupted with a “Timer too close” error, causing the print to stop.
Tried to set microsteps to 16, reduced bitrate from 1M to 500K.

biqu@VoronGreen:~$ cat /etc/network/interfaces.d/can0
allow-hotplug can0
iface can0 can static
    bitrate 500000
    up ip link set $IFACE txqueuelen 1024

Despite these changes, the issue persists.
Is there anything in the logs that might indicate the root cause of this problem?

[oleks]

Today I received different message

Stats 11926.2: gcodein=0  mcu: mcu_awake=0.030 mcu_task_avg=0.000002 mcu_task_stddev=0.000001 bytes_write=44338329 bytes_read=8325669 bytes_retransmit=0 bytes_invalid=64 send_seq=805817 receive_seq=805817 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=48 upcoming_bytes=1965 freq=399995821 CB1: mcu_awake=0.001 mcu_task_avg=0.000009 mcu_task_stddev=0.000014 bytes_write=72906 bytes_read=226632 bytes_retransmit=0 bytes_invalid=0 send_seq=12126 receive_seq=12126 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49999925 adj=50000482 sb2040: mcu_awake=0.026 mcu_task_avg=0.000010 mcu_task_stddev=0.000019 bytes_write=19406355 bytes_read=4475632 bytes_retransmit=0 bytes_invalid=0 send_seq=391578 receive_seq=391578 retransmit_seq=0 srtt=0.003 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000042 adj=12000192 sd_pos=22811966 BTT_Manta: temp=45.8 Chamber: temp=42.5 FLY-SB2040: temp=60.6 Toolboard_SB2040: temp=50.2 heater_bed: target=70 temp=70.1 pwm=0.086 sysload=0.44 cputime=1984.411 memavail=509184 print_time=11930.378 buffer_time=2.217 print_stall=0 extruder: target=240 temp=240.6 pwm=0.304
toolhead: max_velocity: 650.000000
max_accel: 14000.000000
minimum_cruise_ratio: 0.500000
square_corner_velocity: 15.000000
Stats 11927.2: gcodein=0  mcu: mcu_awake=0.030 mcu_task_avg=0.000002 mcu_task_stddev=0.000001 bytes_write=44343538 bytes_read=8326475 bytes_retransmit=0 bytes_invalid=64 send_seq=805907 receive_seq=805907 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=57 upcoming_bytes=1202 freq=399995811 CB1: mcu_awake=0.001 mcu_task_avg=0.000009 mcu_task_stddev=0.000014 bytes_write=72912 bytes_read=226648 bytes_retransmit=0 bytes_invalid=0 send_seq=12127 receive_seq=12127 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49999924 adj=50000477 sb2040: mcu_awake=0.026 mcu_task_avg=0.000010 mcu_task_stddev=0.000019 bytes_write=19408563 bytes_read=4476029 bytes_retransmit=0 bytes_invalid=0 send_seq=391621 receive_seq=391621 retransmit_seq=0 srtt=0.002 rttvar=0.002 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000041 adj=12000187 sd_pos=22815837 BTT_Manta: temp=45.9 Chamber: temp=42.5 FLY-SB2040: temp=59.9 Toolboard_SB2040: temp=50.3 heater_bed: target=70 temp=70.1 pwm=0.086 sysload=0.44 cputime=1984.626 memavail=509184 print_time=11931.184 buffer_time=2.023 print_stall=0 extruder: target=240 temp=240.7 pwm=0.224
toolhead: max_velocity: 650.000000
max_accel: 6000.000000
minimum_cruise_ratio: 0.500000
square_corner_velocity: 8.000000
Transition to shutdown state: MCU shutdown
Dumping gcode input 0 blocks

Maybe it’s something g-code related from Orca cause such errors?

New klippy log attached:
klippy.log.zip (1.3 MB)

[oleks]

I checked other people’s klippy.log files, and I don’t see these sections in mine:

toolhead: max_velocity: 650.000000
max_accel: 14000.000000
minimum_cruise_ratio: 0.500000
square_corner_velocity: 15.000000

Is this something that could indicate problem with MCU shutdown?

[Sineos]

While you should have these settings with proper values according to your printer model, it will not cause a TTC error.

Check Timer too close for some pointer on this error.

[oleks]

Thank you for your reply.

I have another Voron 2.4 with almost the same configuration (BTT Manta M8P v1.1 + CB1 + Mellow SB2040 v2) and slightly different settings, but it doesn’t have any TTC issues.
I suspect the Mellow SB2040 Pro version might be unstable. I just want to check all possibilities before replacing it with the BTT EBB36.

BTW, I had a TTL issue again just after a purge. The printer didn’t even start to print. The issue appears randomly.

[Sineos]

@oleks

The issue appears randomly.

Unfortunately, this is (in most cases) exactly the nature of this error.

[oleks]

I have different stepper drivers on the m8p

Stepper Drivers for XY: Fysetc v3.1 tmc2209
Stepper Drivers for Z0-Z3:BTT tmc2209

Could this cause the issue?

[Sineos]

@oleks

Could this cause the issue?

No.
All known reasons for this issue are listed in the article I linked above.

[oleks]

I’ve been printing for 4 days with the disconnected KNOMI (power is supplied), and there hasn’t been a single disconnect (average print duration 5-6 hours).
Previously, the issue typically occurred around the 3rd hour.

Maybe the problem wasn’t entirely with the CAN bus, and it was just contributing to the issue, which eventually caused a complete failure.
I found a potentially similar problem on Discource, which seems to be unresolved: CAN-Bus suddenly losing connection ~3 Hours into Prints - #2 by VoltexRB