Native canbus MCU 'EBBCan' shutdown: Timer too close

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:RK3568 as host, Bigtreetech Octopus MAX EZ Driver Board (USB),Bigtreetech EBB42 CAN V1.2As extruder (CANBUS)
klippy.log
klippy (11).log (2.8 MB)

I’m trying to use RK3568’s native CANBUS to communicate with EBB42 CANTools ，canbus bitrate=500K, but at the beginning of the printing, there is a fault of MCU ‘EBBan’ shutdown: Timer too close. Here’s what I’ve tried:

  1. I tried changing the power supply, but the fault still exists.
  2. Check the canbus for packet loss and abnormality, as shown in the figure below. Also found nothing wrong
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1024
    link/can  promiscuity 0 minmtu 0 maxmtu 0
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
          bitrate 498322 sample-point 0.865
          tq 13 prop-seg 64 phase-seg1 64 phase-seg2 20 sjw 1
          rockchip_canfd: tseg1 1..128 tseg2 1..128 sjw 1..128 brp 1..256 brp-inc 2
          clock 148500000
          re-started bus-errors arbit-lost error-warn error-pass bus-off
          0          0          0          0          0          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
    RX: bytes  packets  errors  dropped overrun mcast
    185246     24874    0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    28057      4361     0       0       0       0
  1. My operating system information is as follows

System information as of Sat Aug  5 04:27:58 UTC 2023

System load:   1.22 0.29 0.10   Up time:       0 min
Memory usage:  14 % of 1971MB   IP:            192.168.1.3
Usage of /:    48% of 14G
  1. This problem does not occur when I reduce the canbus rate to 250K, but if the vibration compensation is added later, this speed cannot be satisfied.
    Let me know if you have any possible suggestions, I’m open to testing them all, thanks.
2

Did you end up fixing this?

3

Please do not necro-ressurect some 1 year old “Timer too close” thread, There are countless threads here about this error and the solutions are always the same.

A comprehensive overview of the known reasons for this error are to be found in Timer too close

1 Like