speed of sending data to the board

I'm testing a board from a PC program created by me.

The problem is that I don't know how many lines of G code can be sent to the board ...

should I wait for a few milliseconds before sending a new G code command ?

or is there a command that tells me that the board has executed all the commands in its cache ?

thanks,
mihai

typically it is 4 to 16 commands and a maximum of 63 char per line

or is there a command that tells me that the board has executed all the commands in its cache ?


You can wait for the checksum return, or the ok response.

Edited 1 time(s). Last edit at 06/17/2013 08:32PM by jamesdanielv.

Quote

The problem is that I don't know how many lines of G code can be sent to the board ...

After accepting a line of G-code, firmwares send back an "ok". This is sort of a flow control. Marlin ans Sprinter limit G-code lines to 63 characters.

Teacup offers XON/XOFF flow control in addition to the "ok"-type. The advantage of XON/XOFF is, it's handled at the driver layer, no need for the application to take care. The drawback is, pausing a print is almost imossible, because drivers have rarther large buffers (typically 16k or several hundred lines of G-code).

For an even more advanced concept, see [reprap.org] AFAIK, no implementation, so far.

---

Generation 7 Electronics	Teacup Firmware	RepRap DIY