Hi Mathias i just send you error message .
i have beta firmware too (soon update with official and retest)
meanwile you have any suggest?
after heating sentd 3-5 gcode and disconnect i use s4 for this test.
This beta firmware seems to respond with additional debug data which GCodeSimulator is not able to handle.
e.g. Simple M105 response is
17 (executing M105)
ok T:234 D8% B:130 D66%
ok 17 Q64 (0ms execute)
Is this a beta of the Makibox firmware or Marlin ?
makibox firmware(pre-production), based on Sprinter firmware.
i don’t read mail but issue don’t have it on on m105 but after when start print skirt suddenly disconnect without continue print.
when have time retry…and reduce serial speed port at 115200
also non M105 commands have a weird response:
go 60 (executing G1)
Unexpected response from printer: go 60 (executing G1)
ok 61 Q28 (3ms execute)
Normal firmwares just respond with: ok
mmm think same message in new firmware too…just open code and find it for example.
#define TXT_OK_SEQNUM_Q_MS_EXECUTE_CRLF “ok %ld Q%d (%lums execute)\r\n” 
so, they question is, is that only because it is pre-production or will the final Makibox firmware deviate from the standard as well ?
Current code on http://bitbucket.org is standard and installed on production machine .
All message are visible from this link https://bitbucket.org/makible/makibox-firmware/src/3d5665695519446d8af5468edc1514fb6c399d2c/src/language.h?at=default
do you know someone who can explain to me what the additional output means and how to parse it ? The simple parser which reads each line until it finds an “ok” doesn’t work well in this case.
as sugested in other post you can contact leader team Jonathan or Elliot Polk.but Currently other software as printrun i feel no check it and no have issue on printing(never have disconnect during printing).
if want try to understand reading firmware code.
see you tomorrow i try to take other test in evening for understand if only causal disconnect or failure of interpeter response.
thanks for your time and good night
ok just find mail and see log file send you yesterday… Really don’t know why response with GO too, try to understand(but as my frist impression from your log “GO” message and “Q” is logical position of gcode queue memorized in buffer).
re-try to reduce speed port to 115200 baud before request to you modify code for check if skip “GO” message for check if remove self discconect issue( normaly in test app)?.
Printrun/pronterface never give any issue on print same original software make for makibox 5dprint.
@Mauro_Manco It would help a lot if you could send me the console output of printrun (with debug enabled)
Ok put it in my todo list 
have nice day see you later
@Mauro_Manco I tried to install the makibox firmware on my arduino mega 2560 but this board is not supported.
I might see the reason for disconnect when debug output is enabled.
Could you enable debug logging and send me the console output ?
Just return in home(just finish xmas “party” in russian school of my son)…ok try this afternoon sorry yesterday return at home at 20:00 after 2h on ring of Rome and no having good mood for testing.
sended log with debug and same issue on s2 at baud 11520
I found the reason for the disconnect. The unexpected answer causes the app to send gcodes too fast, this causes a write failure and disconnect. I will publish a update soon.