AnHardt
commented
8 years ago If you get messages like "Serial: incoming chars rejected - ring buffer full" the likely causes are:
- Marlin is sending to many 'ok's - animating the host to send to much input.
- G-code lines are longer then RX_BUFFER_SIZE. (128)
- Broken host.
With https://github.com/AnHardt/Marlin/pull/32/commits/eab04ebc48bfd72079ecb2986dd67f82e5c5faad you get a printout of the g-code line with the defect, when a communication error is detected.
- Missing chars -> an ISR takes too long, or a
CRITICAL_SECTIONis not closed properly. The serials RX-interrupt is executed too late - the RX-registers content was replaced by the next char. - Wrong chars can be caused by noise between USB-chip and processor (serial connection) or buffer corruption by Marlin.
With the extended ADVANCED_OK you get a more detailed view on the buffer usage and the info what line is actually 'ok'ed. If you fell there is too much output just deactivate ADVANCED_OK or comment one of the added lines
If the protocol errors are rare, they like to disappear in the logs history. Activate //kill(PSTR("ERR: ring buffer full"));. and add something similar to gcode_line_error(). The printer will be killed then!!! Parts are ruined!!! This is most suitable for testing with dry-runs.
Some little helpers to debug input stream errors.
Activate ADVANCED_OK.