CAN network failures - M8P CB2 EBB42

[Sineos]

@Bacheshatonee

The 2 big problems with a “regular” hardware instability is that the error is happening on the physical connection between the M8P and the CB2, so if there is a physcial defect on one of the 2 boards or the connectors, there is no cable involved just the Pi CM connectors, that may make partial sense.

@Bacheshatonee

If this is a “normal” hardware instability, I will need to track down what in klipper itself is causing this failure mode.

@Bacheshatonee

I don;t see anything that is even remotely close to slowing down either with cycles/memory/or bandwidth.

You are misinterpreting the error.

Your actual error is Missed scheduling of next digital out event. The reasons for this error are similar to the TTC error.

The key message in the TTC error is true for your error as well:

1. In the first place, the error means nothing more than “Hey, I’m the klippy host and I have been waiting for a call from you (the MCU). You did not call and now I’m disappointed and won’t talk to you any more.”
2. The knowledge base entries give pointers to what could be the reason for this behavior.
3. Klipper just does not know and thus cannot put anything in the logs.
4. There is no indication that it is CAN or EBB related.

Conclusion:

• Something in your local setup is causing this. Again, refer to the KB for potential contributors and reasons.
• You need to identify “something.”
• In a recent post here, a neon tube installed right over the printer was emitting so much electrical dirt that the communication was sufficiently disturbed.