-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
if checksum == NL or CR, false NOCHECKSUM generated? #4166
Comments
The assumption the checksum is a single byte is wrong - it's the ASCII representation of a single byte. |
Ah. Ok then. Sorry! |
I admit this is a bit hidden
And somewhere is a misleading comment.
That's wrong. '#' can't appear in the checksum. Repetie Host:
|
hello can someone explain to me what is wrong when i try to send it after a M28 command why it seems to don't find the checksum ?? |
A) This is a closed bug report not a support forum. |
Thank for your very quick reply A) I know it’s not a support forum but there is no information in documentation about this function. As I worked 2 days to find why it doesn’t work, I could think there is an issue and open a new one. Before doing that I prefer asking somewhere people maybe know if it’s or not an issue. B) it’s not obvious : the documentation explain M28 command is to send a file and the example is a .txt file. So the transfer shouldn’t care about what is in the file. You can want to send a config file or to keep comments in gcode file to use them later. I don’t really understand this choice. Anyway thanks a lot, I will not find it alone |
I'd start with a search for the problem by reverting #16840. |
@spilz87 — Here are the resources you should use instead of hijacking our issue queue:
|
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. |
3 similar comments
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. |
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. |
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. |
get_serial_commands() reads each line off the serial buffer until it hits a \r (13) or a \n (10) character.
commands follow the format
N[line number] [gocde];*[single byte checksum][CR and/or NL]
if the checksum of the line is equal to 10 or 13, the line would be truncated prematurely and a NOCHECKSUM error would be generated. If the PC software sends the exact same line again, an infinite loop would result.
A possible fix is to treat * as an escape character for the \n or \r check.
The text was updated successfully, but these errors were encountered: