Ignore "No Checksum with line number" errors as they trigger a resend just as well as e.g. "No Line Number with checksum" (quick check of the Marlin source seems to confirm this).

Should hopefully help with #5 and #9 -- will not reduce the communication errors (that's most probably not the comm stacks fault but rather a noise issue or something) but will lead to a more error resilient behaviour. Please test (I can't reproduce the issue(s)).
master
Gina Häußge 2013-01-05 00:00:38 +01:00
parent 99ed13160f
commit 83bf6efb1d
1 changed files with 1 additions and 1 deletions

View File

@ -328,7 +328,7 @@ class MachineCom(object):
if re.match('Error:[0-9]\n', line):
line = line.rstrip() + self._readline()
#Skip the communication errors, as those get corrected.
if 'checksum mismatch' in line or 'Line Number is not Last Line Number' in line or 'No Line Number with checksum' in line:
if 'checksum mismatch' in line or 'Line Number is not Last Line Number' in line or 'No Line Number with checksum' in line or 'No Checksum with line number' in line:
pass
elif not self.isError():
self._errorValue = line[6:]