-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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] Line number is not Last Liner Number+1 #2910
Comments
it seems you enabled advanced_ok but it is not properly supported/configured on Marlin side. Disable it on TFT side only (it is enough). Those errors you reported are related to a corruption on Marlin side (data are properly read from SD card) |
yes it is enabled. And how to set it up correctly? It seems that I have followed all the instructions for setting up.
The instructions say
but only the following buffer size options are given in the configuration
what buffer size should I set? |
32 * 96 = 3KB, so if your hardware supports it set RX_BUFFER_SIZE to 2048, this should be fine. |
I used the following parameters:
everything seems to be working correctly |
@MrKuskov remember that |
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. |
Description
When printing any G-Code with the
Command checksum
function enabled, I constantly see errors. For example, in the calibration retraction test, I see the following errors at the beginning of printing.line: cur=6437, exp =6431.
Line number is not Last Liner Number+1, last line: 6442.
line: cur=6433, exp =6431.
Line number is not Last Liner Number+1, last line: 6434.
line: cur=6440, exp =6435.
This is all when printing this file. The values change for different files, but the essence does not. At the same time, messages like "unknown command *84" or "-1.65 Y23" appear in the upper line, that is, it is clear that these are card reading errors (*84 - X84). Skipping one command has almost no effect on print quality, but when printing a thin-walled part, it is almost always a defect. I have tried using different cards in different connectors and USB FLash, sometimes errors disappear, but most often 1 or 2 per printing session appear. How to set up error-free printing or G-code duplication?
retraction_tower_PETG_16m39s.zip
TFT35 B1 V3
The text was updated successfully, but these errors were encountered: