I inquired about doing this myself a while ago. I’d still do it if I need to, but it occurred to me that maybe the feature has broader appeal. Besides, for somebody that really knows the code inside and out, this would be much easier;-). So: Sometimes it would be useful if TinyG would sent out something when it has done the commands it has received. I would use this to take a picture with the camera for precise optical alignment.
Cool. I missed the fact that if I set the status interval longer than the movement would really take, I get a message immediately when the machine stops (and there is not a cunfusing message at the end of the interval). Thank you for pointing this out. The more I use the TinyG, the more I like it!
The way status reports work in 0.95 (now in Master) is that they are requested on (1) any gcode command, (2) at the end of movement and (3) during movement. The minimum interval (si) sets the maximum rate automatic SRs can be generated for any of these triggers – in order to preserve serial bandwidth and UI processing.
There’s more. Rather than explain it all here I refer you to this page that explains status reports for version 0.95. Most of this is also applicable to 0.94 as well:
.
