M122 does not work from DWC console
I have seen an occasional failure of M122 to give a response in the DWC g-code console. With the current firmware and DWC (2.02rc1 and 1.22.3), M122 will cause a pause, disconnect, and immediate reconnect. This usually happens when I return to the printer some time after the print has finished. I can connect with YAT, and I get a response to M122 - this is the output: 0_1536068880847_20180904m122 from yat.txt
This output does not relate to the completed print, so presumably the M122 from DWC was processed to some extent. Interestingly, the DWC g-code console is still responsive to some commands - I can send an M999 reset for example. Have seen this with previous versions of firmware/DWC.
Are you saying that after the problem occurs, most commands sent from the GCode Console don't work?
A few commands (from memory M112 and M122, I can't remember about M999) are recognised early and bypass the normal command queue.
@dc42 my impression is that quite a few commands do work. I will do a more comprehensive check next time it happens
I tried again today, and the output of the DWC g-code console is here:
0_1536253098443_20180906m122 from dwc.txt
M122 just over 1hr after the print finished did not give a response, although there was no disconnect/reconnect this time. I then tried M665, M666, head movement, homing and adjusted the hot end temperature, and listed the sd card with M20 - all seemed to work. Re trying M122 worked this time. Simply retrying M122 has not previously worked. Will check again when I get the full disconnect response to M122.
Added to my list to look at.
sigxcpu last edited by sigxcpu
Here's a traffic capture when M122 fails on DWC (but works on serial & telnet).
That response means that you have already sent some commands to be executed from DWC, that are waiting to be executed, and the input pipeline is full. So the M122 command has probably not completed. Perhaps you need to make more rr_reply calls to retrieve the M122 response.