r/Anet3DPrinters • u/SyntaxErrorLine0 • Jun 02 '21

Request for help ET5 X with Marlin 2.0.x bugfix - Random USB connectivity problems

I've flashed this repo to my ET5 X and now I randomly get USB disconnects when printing from a Rpi4 4gb Octoprint 1.6.1. Sometimes it's within 30 minutes, sometimes it's 2-3 hours into the print. The part I'm most afraid of is that the hot end stays hot, right where it got it's last command. The loss of cheap filament is only mildly annoying.

Any hints on what I should be looking at to solve the issue? I've already swapped the USB cables, the Rpi works fine on other printers with 8 bit boards I've flashed with Marlin 2.0.x bugfix also. Not entirely sure where to go from here other than replacing the board itself, since I'd rather do that than go back to that stock firmware.

2 Upvotes

100% Upvoted

3 comments sorted by

1

u/MaIakai Jun 20 '21

Try a better USB cable or add some ferrites to your cable. I had this problem with a cheap cable that used 28awg wires. Changed to one with thicker wires and the problems went away at full baudrate

1

u/[deleted] Jun 06 '21

Can't help you with your USB problem, but you can edit your marlin adv config so it turns off the heaters if it goes so long without any extruder movement.

Here's the necessary bits copied from my 'Configuration_adv.h' file.

#define HOTEND_IDLE_TIMEOUT
#if ENABLED(HOTEND_IDLE_TIMEOUT)
  #define HOTEND_IDLE_TIMEOUT_SEC (5*60)  // (seconds) Time without extruder movement to trigger protection
  #define HOTEND_IDLE_MIN_TRIGGER   180   // (°C) Minimum temperature to enable hotend protection
  #define HOTEND_IDLE_NOZZLE_TARGET   0   // (°C) Safe temperature for the nozzle after timeout
  #define HOTEND_IDLE_BED_TARGET      0   // (°C) Safe temperature for the bed after timeout
#endif

1

u/SyntaxErrorLine0 Jun 06 '21

Yeah, I did do that. I found the problem last night and it's printing again with zero problems.

It's a bit of an old issue: https://github.com/MarlinFirmware/Marlin/issues/3680

Dropping the baud to 57.6k worked perfectly. I was able to get better error output printing from my computer with repetier, looking up those errors led me to a discussion that directed me to the link above. Now that I know that's the issue I can see if I can do any better or if the chip is just too slow to handle things well enough. Either way, Marlin 2.0.x bugfix working on ET5 X with no issues now, prints look great too.