# Issues with CANable

**URL:** <https://klipper.discourse.group/t/issues-with-canable/7970>\
**Category:** General Discussion\
**Created:** [April 21, 2023, 7:54pm UTC](https://klipper.discourse.group/t/issues-with-canable/7970 "2023-04-21T19:54:51Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [April 23, 2023, 11:41am UTC](https://klipper.discourse.group/t/issues-with-canable/7970/21 "2023-04-23T11:41:12Z")

</div>

My impression is, there are still some unexplained phenomenons concerning CAN and Klipper.

koconnor just wrote a utility to parse Klipper messages in a candump capture [Comparing master...work-parsecandump-20230417 · Klipper3d/klipper · GitHub](https://github.com/Klipper3d/klipper/compare/work-parsecandump-20230417)  
First you need a candump.log [CANBUS Communication timeout while homing Z - #12 by koconnor](https://klipper.discourse.group/t/canbus-communication-timeout-while-homing-z/3741/12)  
To get the candump utility you need to install can-utils [Debian -- Details of package can-utils in sid](https://packages.debian.org/sid/can-utils)

Good luck, hcet14

---

_[View the full topic](https://klipper.discourse.group/t/issues-with-canable/7970)._
