MCU Shutdown in Performance Mode (Rescheduled Timer in the past)
I'm having an issue when activating "Performance Mode" as instructed by the V-Core 4 Commisioning guide. As soon as I do this an attempt to home the printer I am getting a Klipper shutdown due to a rescheduled timer in the past. Normally it occurs when homing the Y axis. From what I've read this happens because the MCU can't keep up with the required step rate.
Not sure how to resolve this? My controller board is a Manta M8P with a CM4. Should this board be able to handle performance mode? Or do I need override the performance mode settings to use lower limits?
3 Replies
Is your controller actively cooled?
Hi. Do you mean the CM4? It has a heat sink installed on it. And I have the 3 fans in the electronics enclosure fitted and they are running so there is some active cooling for the controller board.
I seemed to have potentially resolved the issue by reducing the number of microsteps for the motors from 64 to 32. Perhaps the controller clock speed is too low to handle 64? AFAIK the octopus is clocked at 160MHz, whereas the Manta M8P v1.1 is only 64Mhz.
Quite possible. I was referring to having air flow from fans over the stepper motor drivers as they would be over heating if in performance mode and you didn't have active cooling