I'm using ReplicatorG to run my reprap, with a standard atmega/ramps 1.2 electronic on client side. The firmware is the last version of Kliments Sprinter.
The communication between ReplicatorG and Sprinter seems to be synchronous, that means: ReplicatorG waits for the "ok" before it sends a new command. Sprinter acknowledges only after finishing the current command. If I manually send some commands without waiting for an ack, everthing's ok, i recieve a bunch of "ok"s directly after the current move.
ReplicatorG always waits for an ok and therfore makes the firmware-buffer useless. The ReplicatorG driver is reprap5d but i've tried some others with the same/similar effect.
I could write a new driver to solve this, but as it seems to be a common problem, I assume i've done something wrong.
Anyone who knows how this should work? are my assumptions correct? Is there a known solution?