Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Serial errors can cause Marlin to restart on 32-bit Archim #13509

Closed
marcio-ao opened this issue Mar 27, 2019 · 3 comments
Closed

[BUG] Serial errors can cause Marlin to restart on 32-bit Archim #13509

marcio-ao opened this issue Mar 27, 2019 · 3 comments

Comments

@marcio-ao
Copy link
Contributor

Description

Under certain conditions, Marlin can crash and restart the printer. I have not been able to find a way to consistently reproduce this, but it seems to involve occasions where the host fails to read the serial port and may be related to some buffer filling up. This could either be a problem in Marlin or possibly the code that drives the USB serial emulation on the SAM chip.

In the case we encountered, we changed Cura to read the serial port more regularly and the problem went away. Creating this issue so there is a record of this, even though I suspect it is a low priority since the problem can be avoided by having the host read the serial buffer consistently. We have not seen any problems with un-tethered prints, so it seems isolated to an open serial USB link.

LulzBot tickets associated with this:

@gloomyandy
Copy link
Contributor

See this issue: #11715
On the LPC1768 we added a timeout that will drop output if the output queue is full for longer than a few milliseconds (Which is sort of what happens with a real hardware port).

@marcio-ao
Copy link
Contributor Author

@gloomyandy: A good to know. I guess I'll close this since it has already been discussed elsewhere and it is unclear whether this is a bug or a feature.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants