# CANBUS Missed scheduling of next digital out event

**URL:** https://klipper.discourse.group/t/canbus-missed-scheduling-of-next-digital-out-event/21757
**Category:** General Discussion
**Created:** [February 1, 2025, 5:54pm UTC](https://klipper.discourse.group/t/canbus-missed-scheduling-of-next-digital-out-event/21757 "2025-02-01T17:54:06Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![OiD-W](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/oid-w/32/17426_2.png) [@OiD-W](https://klipper.discourse.group/u/OiD-W)
#### Post date: [February 4, 2025, 6:56pm UTC](https://klipper.discourse.group/t/canbus-missed-scheduling-of-next-digital-out-event/21757/19 "2025-02-04T18:56:27Z")

</div>

![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/3X/d/0/d06205885727c06c6be49cacd8ca4fdcbe466e3d.png)

Other than Moonraker being very unhappy about some path stuff (well I am too, took me 3 tries to get Klipper, Moonraker and Mainsail on the 8GB CM3 😭) and struggling with the Pi not finding the printer mainboard under **/dev/serial/by-id/** (yeah yeah I should have [listened to my own words](https://klipper.discourse.group/t/klipper-on-smoothie-lpc1769/21761/4)) it’s printing…

# **bytes\_invalid is zero across the board!!!**

```auto
Stats 1212.6: gcodein=0 mcu: mcu_awake=0.021 mcu_task_avg=0.000026 mcu_task_stddev=0.000054 bytes_write=1667043 bytes_read=301243 bytes_retransmit=74 bytes_invalid=0 send_seq=31858 receive_seq=31858 retransmit_seq=29269 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=120005349 
canstat_UCAN: bus_state=active rx_error=0 tx_error=0 tx_retries=0 UCAN: mcu_awake=0.050 mcu_task_avg=0.000023 mcu_task_stddev=0.000005 bytes_write=15142 bytes_read=45109 bytes_retransmit=0 bytes_invalid=0 send_seq=2496 receive_seq=2496 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=47996658 adj=47994564 
canstat_EBBCan: bus_state=active rx_error=0 tx_error=0 tx_retries=0 EBBCan: mcu_awake=0.017 mcu_task_avg=0.000017 mcu_task_stddev=0.000022 bytes_write=714827 bytes_read=189167 bytes_retransmit=391 bytes_invalid=0 send_seq=14822 receive_seq=14822 retransmit_seq=13530 srtt=0.002 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=63999826 adj=63996962 
sd_pos=648484 ambient: temp=-99.6 heater_bed: target=60 temp=60.1 pwm=0.173 sysload=0.50 cputime=56.751 memavail=690356 print_time=1221.933 buffer_time=2.121 print_stall=0 extruder: target=205 temp=205.0 pwm=0.448

```

and yes… it seems like the Raspberry Pi Imager MainsailOS 64/32bit has some older kernel?

Raspberry PI OS LITE 32bit (Bookworm):

```auto
pi@pi:~ $ uname -a && getconf LONG_BIT
Linux pi 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux
32

```

Mainsail OS 1.3.2 is Bullseye based I guess?

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/3X/c/a/cafc6a361a0eea5c419d6bab41cf52384014e22a.png)

(Any tips on how to proceed with the Moonraker issue would also be greatly appreciated)

```auto
/=======================================================\
| a) [Update all] | | |
| | Installed: | Latest: |
| Klipper & API: |---------------|--------------|
| 1) [Klipper] | v0.12.0-429 | v0.12.0-429 |
| 2) [Moonraker] | v0.9.3-29 | v0.9.3-29 |
| | | |
| Klipper Webinterface: |---------------|--------------|
| 3) [Mainsail] | v2.13.2 | v2.13.2 |
| 4) [Fluidd] | | v1.31.4 |
| | | |
| Touchscreen GUI: |---------------|--------------|
| 5) [KlipperScreen] | v0.4.5-40 | v0.4.5-40 |
| | | |
| Other: |---------------|--------------|
| |------------------------------|
| 14) [System] | System up to date! |
|-------------------------------------------------------|
| B) « Back |
\=======================================================/

```

---

_[View the full topic](https://klipper.discourse.group/t/canbus-missed-scheduling-of-next-digital-out-event/21757)._