Orbiter Sensor / Ratos MCU error after loading filament and Resume

I have a orbiter 2 with filament sensor, configured as per attached printer.cfg on a EBB36. This used to operate with the OrbiterSensor.cfg but this is very complex so I changed it acc. to Helge's suggestion in another post (adopting the Pins to the setup with EBB36).

One change that I had to make between the 2 configs is that I had to inverse the functions (remove the exclamation marks) and added the ^ sign as per suggestion of Helge.
- Pressing the unload butten works
- Sensor activates the Park & unload sequence during a print.

2 issues remain however
- Minor issue: When I pull out the last filament-bit out of the extruder, the extruder immediately starts the Load Filament routine. I quickly put the new filament in and it then continues loading and purging and waits for me to press the resume button.
- Bigger issue: after pressing resume, it briefly moves the extruder towards the resume point, the halts and throws an error:

10:11 FIRMWARE_RESTART
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
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
10:11 Klipper state: Shutdown
10:11 Filament loaded!
10:10 Filament unloaded! Please inspect the tip of the filament before reloading.
10:10 SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1

Printer:
RatRig VCore 3.1 300 (Enclosed)
Manta M8P with CM4 + EBB36
Orbiter 2.0 with filament sensor
Revo Voron
Printer.cfg + klippy.log attached

(I will add @ of Helge later this evening, not to ping him now as per his request)
printer.cfg22.96KB
klippy.log4.61MB
Was this page helpful?