RatOS Manta CB1 - Repeated "Timer too close" Failures
Hello, I am posting about this issue again. Last time, the issue was mostly during print start, and the suggestion was to use a faster SD card, and I purchased the SanDisk Extreme as suggested. This seems to have helped a bit, but the issue is back with a vengeance, print start, during the print, etc. My current solution is to just reboot the host every day.
Just to be clear: I very much appreciate that support was extended to this board, and I know it may simply not be capable of supporting the software. I am putting this here in case it helps. I may move the Octopus if I can find a good deal in that direction.
Thank you.
8 Replies
You sure this is the right log? I can't even find where it is having the error you are describing
Timer too close is the unknown issue on klipper. It says nothing specific.
That said, it can be different things. But most likely it is related with the processing power of the CB1
what are you basing your conclusion that the CB1 isn't powerful enough?
I’m one of the original testers and know it quite well…
Not that is can compromise working flow but RatOS has a lot of things over vanilla klipper that can make things laggy. And the CB1 chip is not the best thing around…
By chip I mean SOC
Every single tester complained about the same things. Laggy, no CSI, low ram, etc
RatOS runs on a pi zero 2, the CB1 should be fine
The memory leaks etc i can't really comment on
Doesn't happen on raspberry pi os
Besides this CB1 we haven't had anyone else report memory leaks
I've heard about it happening to others (not on RatOS)
I don't have much to add, just to state that I am happy to provide whatever information might be helpful. I am inclined to think it is the CB1.