FirmwareResponseProtocol

From RepRap
Revision as of 15:07, 26 November 2011 by Glenn (talk | contribs) (catchg)
Jump to: navigation, search

Notes about the messages that the firmware sends back to the host

this is what I know so far:

the firmware sends "start\n" when it has booted and is ready for commands

the firmware sends "ok\n" when it has successfully processed a line.


"processed" in this case means a gcode command is added to the queue, or an mcode has been accepted, or a comment has been ignored.


if the queue is full, the firmware will not send "ok" until a space has become available. this provides rate limiting without the host needing to know anything about the queue or its format.


The command M101 waits for the temperature to reach a set value. Can this be queued, or does the firmware block all new commands until the temp has reached this value? Blocking may cause problems since M101 starts the extruder.

does this matter with FiveD firmware and a stepper-driven extruder? or does M101 just wait for the temperature?

there is no way for the host to request the firmware's idea of current position, or any other data except extruder temperature