# MCU discconnecting, rpi not respoding

**URL:** <https://klipper.discourse.group/t/mcu-discconnecting-rpi-not-respoding/9096>\
**Category:** General Discussion\
**Created:** [June 22, 2023, 5:04pm UTC](https://klipper.discourse.group/t/mcu-discconnecting-rpi-not-respoding/9096 "2023-06-22T17:04:51Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![BitPatcher](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@BitPatcher](https://klipper.discourse.group/u/BitPatcher)\
**Post date:** [July 3, 2023, 1:20pm UTC](https://klipper.discourse.group/t/mcu-discconnecting-rpi-not-respoding/9096/20 "2023-07-03T13:20:47Z")

</div>

To prevent timing issues, I’ve changed the way Linux schedules the `klipper.service` in order to increase its priority. This way, other services (from kiauh) will not delay klipper.

```auto
# ...
[Service]
# ...
# Increase scheduling priority for the service
# https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Scheduling
Nice=-20
CPUSchedulingPolicy=rr
CPUSchedulingPriority=99

```

@Sineos, If it makes sense, we could increase the priority by default. Have you seen other people mentioning this problem going away after getting rid of extra services? Or of issues appearing when loading a frontend after some period of inactivity?

---

_[View the full topic](https://klipper.discourse.group/t/mcu-discconnecting-rpi-not-respoding/9096)._