MCU Shutdown/Timer issues.

[Mart7Mcfl7]

K-Shake&Tune module branch

• I confirm using the main branch

Version

V5.2.1

Describe the bug and expected behavior

Not sure if this is still the same issue that I read was fixed but I keep getting these shutdowns.

There is no reason to them, sometimes I can run multiple tests one after the other and other times I can't even complete one test.

I've tried restarting the host/mcu, cpu isn't overloaded, I really don't know what's going on

Additional information and klippy.log

klippy (3).zip

[Mart7Mcfl7]

Also, I'd like to add, this tool is great, please keep up the good work :)

[thibaled]

Same issue here with COMPARE_BELTS_RESPONSES while doing B belt. The A belt always completes successfully.

Setup: BTT CB1 on Manta M8P v2.0.

I tried disabling Led_Effect and Klipper_Screen. It works once, but then fails on subsequent attempts.

klippy-9.log

[Makhaira]

Also having this issue, Pi 3B+, only on B belt. klippy log shows absolutely nothing.

[bsafh]

same here - Orange Pi Zero 3, newest mainline klipper, only on Y belt

[gelius1959]

Hello. The same error when checking the tension of the belt B ,controller CB1. X, Y axis tests pass well. I tried all the recommendations for solving the problem.

[BTAARMIX]

I opened a new ticket a little quickly, I have the same problem still no solution for months. I came back to previous versions of klipper and shake and tune, it worked once then doesn’t work anymore

[ormarek]

Having the same issue on M8P v2.0 and CB1

[gelius1959]

Installed CB2 instead of CB1, everything works fine. But then it is necessary to indicate in the description of the plug-in the requirement for hardware for normal operation, or to find a solution so that it works with a less productive platform. I think that the problem is with the memory in CB2 2 GB and in CB1 1 GB and the clipper displayed as the limit of the memory used. Sorry for my bad English.

[ormarek]

Unfortunately I don't have any CB2. I decided to leave a comment because it worked previously. I've been running those tests many times on this printer, but was changing carriage and wanted to check my belts, and I can't anymore. I'd love the maintainers confirm if this is hardware issue or just a bug

[Limb]

I was having the same problem with my CB1 and COMPARE_BELT_RESPONSES. The first belt would complete fine, but I would get timer errors somewhere during the second belt.

I increased the dwell time at line 140 in compare_belt_responses.py from 5 to 30 (just chose a random time, I'm sure this can be tuned lower) and was able to get the macro to complete successfully.

[timj79]

I'm getting this same issue with the CB2 installed, failing at belt B. Tried increasing the dwell time to 30 as posted above but it didn't help

[gelius1959]

I installed CB1, and the belt test failed.
Replaced it with CB2. The belt test worked for a while, then stopped.
Replaced it with CM4, ran 10 belt tests, and everything was fine.
It seems the BTT CBx MCU isn't as fast as the CM4.

So, I have two unnecessary BTT MCUs. I won't buy them again; the price was attractive; they're cheaper.:(

[timj79]

Would be a shame to have to replace the CB2 already, as I've only just got it.
This set to be the error that's happening each time

MCU error during connect
Traceback (most recent call last):
File "/home/biqu/klipper/klippy/klippy.py", line 135, in _connect
cb()
File "/home/biqu/klipper/klippy/mcu.py", line 962, in _connect
config_params = self._send_get_config()
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/biqu/klipper/klippy/mcu.py", line 958, in _send_get_config
raise error("Can not update MCU '%s' config as it is shutdown" % (
mcu.error: Can not update MCU 'mcu' config as it is shutdown
mcu 'mcu': got {'oid': 8, 'sequence': 64053, 'data': b'\x00\xf8\xec\xe0~\x00\xfc\xf0\xe0~\x00\xf8\xf0\xe0~\xfc\xfa\xee\xff~\x00\xf8\xee\xe0~\x00\xf8\xe8\xe0~\x00\xfc\xe8\xe0~\x00\xfa\xea\xe0~\xfc\x00\xf4\xff\x7f\x00\xfa\xee\xe0~', '#name': 'sensor_bulk_data', '#sent_time': 38.330970027, '#receive_time': 38.339973777}
Can not update MCU 'mcu' config as it is shutdown

[gelius1959]

It was a pity for me too, two SBCs were bought and they are useless.
We need to think about how to use them for other purposes :))