UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Posted
(edited)
· Communicating via USB while printing from SD?
Ok, I read through the marlin firmware and the result (if I got it right) is okay.
The main loop first reads from serial in a loop until the buffer (8 commands) is full or no more serial communication happens and then from SD again in a loop until card EOF or buffer full.
So, if I send too many commands fast enough, I could fill the buffer with serial commands (as they will be read first) and starve the SD communication and make my print fail...
...this should be unlikely because generally, when just occasionally sneak in a command it should work fine as the serial loop would stop and it can happily fill up the buffer with SD commands.
Edited by Guest
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Recommended Posts
derbroti 4
Ok, I read through the marlin firmware and the result (if I got it right) is okay.
The main loop first reads from serial in a loop until the buffer (8 commands) is full or no more serial communication happens and then from SD again in a loop until card EOF or buffer full.
So, if I send too many commands fast enough, I could fill the buffer with serial commands (as they will be read first) and starve the SD communication and make my print fail...
...this should be unlikely because generally, when just occasionally sneak in a command it should work fine as the serial loop would stop and it can happily fill up the buffer with SD commands.
Edited by GuestLink to post
Share on other sites