Follow the disconnections... Ideas?

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
klippy.log

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed

Describe your issue:

Hi,

after managing to install the EBB42 by CAN, before I had it by USB… I thought that the disconnections were over… but no… When changing to Fluidd, I receive another message, which I don’t know if it will be similar who received before…

I enclose a copy of the message and a copy of the log.

I have to say that I have been able to finish some impressions, less than 1 hour… and that these failures are usually at the beginning of the impression, sometimes I have had them before starting, while I am doing the Tilt adjust…

klippy (2).log (5.6 MB)

I have to say that I have a baud rate of 500,000, when they recommend 250,000

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

2

Hi,

this morning i have place a post with a issue with EBB42 v1.1… think remeber that these board uses these Chip…

In this moment i have installed firmwares:

  • Octopus pro: v0.10.0-588-g51da02b7
  • EBB42v1.1: v0.10.0-591-ga2482d4f

EBB42v1.1, its affected for the explained in post?

Is there any other way to update Klipper on the EBB42 other than using a USB cable and STM32?

Thx

3

Try this if you haven’t already:

sudo nano /etc/network/interfaces.d/can0

Change auto can0 to allow-hotplug can0

Save and reboot

4

now I’m in an impression… we’ll see if it ends.

Out of curiosity, what does that line do?

That if you disconnect… you can reconnect and hopefully continue?

5

Yep, hot plug is what you think.

6

Is there a way to see if there has been a disconnection? Maybe some message in the console or looking for something in the log?

7

You can test the bus but not the disconnects that I know of.

sudo apt-get install can-utils

Run cangen

Then open a second ssh terminal and run ifconfig

Look at packet loss and errors for can0 note these numbers. Wait for a few minutes and run ifconfig and check to see if those have increased; if so, there might be a connection, termination, or interference.

If those numbers haven’t changed then you might be able to run at a faster bitrate.

Also, in your /etc/network/interfaces.d/can0

If txqueuelen is less than 1024 the change it to 1024, this is the buffer setting.

1 Like
8

It sounds to me like I tried this, or something similar… and it gave me an error… but tomorrow I’ll try again…

one thing that I’ve changed in can0, is the value of txqueuelen that I had at 128…

I just finished a short impression about 35 min, and everything went well…

edit

Try find the limit…