Im looking for advise. At this point Im out of ideas.
Have build the printer with Octopus V1.1 that initially was in Can Bridge mode firmware. Everything was working fine but after 2 hours of printing it was stopping. Klippy was showing alot of retransmits counting in thousands after 2 h of printing. Replaced the cable with expensive CAN bus cable that at the end I have soldered straight to the EBB36 jus tto make sure there were no bad crimps. That did not help. As the next step I have changed the octopus firmware to work with USB transmission over PA11/PA12 and used dedicated U2C Canbus interface for EBB36 . This route eliminated moist of the retransmits. Now Over the print lhat lasted 9 H I had just 221 retransmits which I'm learning is way within the spec. That being said at last 9th hour of printing my printer halted again with error message
Klipper reports: SHUTDOWN
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event
This is generally indicative of an intermittent
communication failure between micro-controller and host.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
At this point I have no idea what is going on.
Im attaching the klippy log file.
All is going well up to the Stats 40940.4 and then things start happening.
Transition to shutdown state: MCU shutdown
Dumping gcode input 0 blocks
...
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event
...
Printer is shutdown
It seems is related to EBB36
I have just installed new EBB36 thinking it could be related to the hardware problem .
I have connected all the fans to EBB36 5v power supply that in the spec shows can handle 1000mA. My fans all together draw 850 mA if all in full power that rarely happens.
What else could I be missing?
Have build the printer with Octopus V1.1 that initially was in Can Bridge mode firmware. Everything was working fine but after 2 hours of printing it was stopping. Klippy was showing alot of retransmits counting in thousands after 2 h of printing. Replaced the cable with expensive CAN bus cable that at the end I have soldered straight to the EBB36 jus tto make sure there were no bad crimps. That did not help. As the next step I have changed the octopus firmware to work with USB transmission over PA11/PA12 and used dedicated U2C Canbus interface for EBB36 . This route eliminated moist of the retransmits. Now Over the print lhat lasted 9 H I had just 221 retransmits which I'm learning is way within the spec. That being said at last 9th hour of printing my printer halted again with error message
Klipper reports: SHUTDOWN
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event
This is generally indicative of an intermittent
communication failure between micro-controller and host.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
At this point I have no idea what is going on.
Im attaching the klippy log file.
All is going well up to the Stats 40940.4 and then things start happening.
Transition to shutdown state: MCU shutdown
Dumping gcode input 0 blocks
...
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event
...
Printer is shutdown
It seems is related to EBB36
I have just installed new EBB36 thinking it could be related to the hardware problem .
I have connected all the fans to EBB36 5v power supply that in the spec shows can handle 1000mA. My fans all together draw 850 mA if all in full power that rarely happens.
What else could I be missing?
