# CANBUS Communication timeout while homing Z

**URL:** <https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741>\
**Category:** General Discussion\
**Created:** [August 5, 2022, 4:35pm UTC](https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741 "2022-08-05T16:35:42Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![charlespick](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/charlespick/32/610_2.png) [@charlespick](https://klipper.discourse.group/u/charlespick)\
**Post date:** [August 24, 2022, 2:24pm UTC](https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741/10 "2022-08-24T14:24:53Z")

</div>

I flashed latest candlelight firmware last night and then left the printer overnight and just tried homeing again and got the same issue. I also lowered my transmission rate to 250k so my cabus should be fully compliant with the distance I’m running. Fully twisted pair, termination resistors at each end. Still failing to probe and still incrementing invalid bytes.

Same problem appears to be coming up [here](https://klipper.discourse.group/t/can-and-potential-sync-issue-when-performing-qgl/3815/3)

I did some research and I’m also fairly certain that the candlelight firmware Kevin was talking about was from far before I started using canbus toolheads. Unfortunately I don’t think that is where the problem here is.

---

_[View the full topic](https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741)._
