Random Firmware Restarts

General Discussion
1

Printer Model: Ender 3 Pro
MCU / Printerboard: BTT EBB42 / Creality 4.2.2
Host / SBC: Raspberry Pi 4b
klippy.log

Describe your issue:

I just finished installing a BTT EBB42 board with the USB to CANbus expansion board from BTT. Everything is wired up properly. Everything has been tuned using the Ellis Tuning Guide and Im ready to start printing. Ive been getting some testing done and keep getting random firmware restarts. If someone could take a look at it I would be super grateful. Ive already swapped out USB cables as well as put some RFI / EMI ferrules on the cable. Thanks for any suggestions!

Exception:
JRpcError{code: 503, message: Klippy Host not connected}

#0 JsonRpcClient.sendJRpcMethod (package:common/network/json_rpc_client.dart:187)
#1 PrinterService._printerObjectsList (package:common/service/moonraker/printer_service.dart:511)
#2 PrinterService.refreshPrinter (package:common/service/moonraker/printer_service.dart:190)
#3 new PrinterService. (package:common/service/moonraker/printer_service.dart:131)
#4 _ProviderSelector._selectOnChange. (package:riverpod/src/framework/selector.dart:86)
#5 ResultData.map (package:riverpod/src/result.dart:74)
#6 _ProviderSelector._selectOnChange (package:riverpod/src/framework/selector.dart:84)
#7 _ProviderSelector.addListener. (package:riverpod/src/framework/selector.dart:112)
#8 ProviderBase.addListener. (package:riverpod/src/framework/provider_base.dart:98)
#9 _RootZone.runBinaryGuarded (dart:async/zone.dart:1621)
#10 ProviderElementBase._notifyListeners. (package:riverpod/src/framework/element.dart:542)
#11 ResultData.map (package:riverpod/src/result.dart:74)
#12 ProviderElementBase._notifyListeners (package:riverpod/src/framework/element.dart:536)
#13 ProviderElementBase.setState (package:riverpod/src/framework/element.dart:140)
#14 AsyncTransition.asyncTransition (package:riverpod/src/common.dart:28)
#15 FutureHandlerProviderElementMixin.onData (package:riverpod/src/async_notifier/base.dart:284)
#16 StreamProviderElement.onData (package:riverpod/src/stream_provider/base.dart:205)
#17 FutureHandlerProviderElementMixin._handleAsync. (package:riverpod/src/async_notifier/base.dart:390)
#18 _RootZone.runUnaryGuarded (dart:async/zone.dart:1609)
#19 _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:366)
#20 _DelayedData.perform (dart:async/stream_impl.dart:542)
#21 _PendingEvents.handleNext (dart:async/stream_impl.dart:647)
#22 _PendingEvents.schedule. (dart:async/stream_impl.dart:618)
#23 _microtaskLoop (dart:async/schedule_microtask.dart:40)
#24 _startMicrotaskLoop (dart:async/schedule_microtask.dart:49)

2

Maybe uploading the klippy.log?

1 Like
3

klippy.log.zip (1.1 MB)

4

Sorry, thought I had it added. Thanks for any suggestions!

6

See Timeout with MCU / Lost communication with MCU

7

I removed the USB web camera I was using to stream my prints, along with the UPS apc server I was running. After a reboot I still am having an issue with the print failing due to a firmware restart. Could this be coming from the CANBus board? Thanks

8

All shutdowns are related to the main MCU and not to the CAN board. This does not mean that the CAN board cannot be the root cause and make the main MCU fail. Unfortunately, only systematic analysis will reveal it, as the logs can not provide enough information to know what caused the shutdowns.

9

Found the source of the problem. I have a shop light that’s mounted above the printer and the AC power cord was too close to the CAN cable. I rerouted the power cable to keep it at least a foot away, and the firmware restarts stopped. Thanks for the help everyone!

1 Like
10

Can I ask how you’ve implemented your CAN cable as well as how you are doing your power wiring (ie is the light and AC on the same circuit as your printer)?

I’m always interested in understanding EMI issues.

1 Like