search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.59k stars 5.35k forks source link

EBB42 V1.1 STM32G0B1: MCU 'EBBCan' shutdown: Timer too close #5595

Closed cristianku closed 2 years ago

cristianku commented 2 years ago

I am running a Voron 2.4 with Octopus Pro 1.0, BTT U2C 1.1 and EBB42 1.1 STM32G0B1

All are with the latest firmware.

I am running the EBB42 with 4 wires from the U2C, using can bus communication.

I am also running a can bus communication, using a usb cable, from U2C to Octopus pro 1.0

I have set the can bus everywhere to 250000.

The error is repeatable over and over again, and always at the same point of the print. It actually starts after printing few layers, if my print is only few layers height , it doesn't appear.

So its not an overload . the raspberry pi 4 2gb I am using has 30% used CPU and 12% memory load... its not here the problem I think.

Can it be something in EBB42 from BigTreetech ?

and now after printing fine for few minutes, I am getting this error :

16:45:19 MCU 'EBBCan' shutdown: Timer too close

16:45:19

MCU 'EBBCan' shutdown: Timer too close This often indicates the host computer is overloaded. Check for other processes consuming excessive CPU time, high swap usage, disk errors, overheating, unstable voltage, or similar system problems on the host computer. Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Printer is shutdown

klippy.log

cristianku commented 2 years ago

I forgot to add that i am using CanBoot on Klipper Octopus pro 1.0, and this is connected via usb cable to the U2C BTT 1.1

cristianku commented 2 years ago

I have a raspberry pi 4 2gb

cristianku commented 2 years ago

Uninstalled Obico ( ex spaghetti ) but still the same problem and always on the same layer ! image

cristianku commented 2 years ago

image

cristianku commented 2 years ago

and if the problem is in EBB42 because the micro steps are too high ( 16 ) ?

cristianku commented 2 years ago

It's happening always at this layer

image

cristianku commented 2 years ago

maybe thats the reason ?

Compiling out/src/stm32/can.o src/stm32/can.c:68:3: warning: #warning CAN on STM32F4 is untested [-Wcpp]

warning CAN on STM32F4 is untested

^~~

cristianku commented 2 years ago

Solution ! the can communication between Bigtreetech U2C and OCTOPUS pro 1.0 STM32F4 is not working !!!! I switched back to serial and everything is working fine ! . I will try with the can communication using the branch https://github.com/KevinOConnor/klipper-dev/tree/work-usbcan-20220608 , so directly connecting via usb cable from raspberry and Octopus instead of using the U2C.

BUT ! the EBB42 still connected through U2C is working fine !.

I will try also for EBB42 using the branch above to connect directly from RJ11 on the Octopus Board instead of going through U2C

github-actions[bot] commented 2 years ago

It looks like this ticket is a request for help (or similar). Many helpful people will not see your message here and you are unlikely to get a useful response. Instead, see the contact directions at: https://www.klipper3d.org/Contact.html

We use github to share the results of work done to improve Klipper. We don't use github for requests. (In particular, we don't use github for feature requests, to answer questions, nor to help diagnose problems with a printer.)

Please follow the directions at: https://www.klipper3d.org/Contact.html

This ticket will be automatically closed.

Best regards, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

Sineos commented 2 years ago

Please shift this discussion to the Klipper Discourse. Matching threads are already existing there: https://klipper.discourse.group/t/experimental-usb-to-canbus-bridge-mode/3136 https://klipper.discourse.group/t/host-canbus-devices/37/8