Is some "stopPrint" like "keepAlive" possible as signal from printer to Repetier-Host/-Server?
Hello again 
(I was not able to find the answer by myself)
I would like to send some signal from the printer towards Repetier-Host / Repetier-Server in case of some emergency.
The actual use is for cases like:
- Temperature sensor error
- unexpected restart
- recovery after emergency stop / german "Notaus"
- users choice within menu
- filament problems and other problems with no chance of recovery / total print fail
Is there some signal implemented that is understood by Repetier-Host/Repetier-Server?
-> some anything like: void GCode::keepAlive( StopPrint )
Rightnow all the Gcode is spooled through the dataline and moves are just ignored if some problem occurs.
The reason for my question is that this would be some better and much cleaner solution than preventing moves if the printer is not homed or than stopping repetier-server first in browser and then cut the printers power in some case of problems.
Sidequestion: Does Repetier-Server or Repetier-Host react if the printer reboots?
How would they recognize that the printer rebooted?
Some special string?
Greetings
(I was not able to find the answer by myself)
I would like to send some signal from the printer towards Repetier-Host / Repetier-Server in case of some emergency.
The actual use is for cases like:
- Temperature sensor error
- unexpected restart
- recovery after emergency stop / german "Notaus"
- users choice within menu
- filament problems and other problems with no chance of recovery / total print fail
Is there some signal implemented that is understood by Repetier-Host/Repetier-Server?
-> some anything like: void GCode::keepAlive( StopPrint )
Rightnow all the Gcode is spooled through the dataline and moves are just ignored if some problem occurs.
The reason for my question is that this would be some better and much cleaner solution than preventing moves if the printer is not homed or than stopping repetier-server first in browser and then cut the printers power in some case of problems.
Sidequestion: Does Repetier-Server or Repetier-Host react if the printer reboots?
How would they recognize that the printer rebooted?
Some special string?
Greetings
Comments
Is this what I am looking for?
https://github.com/repetier/Repetier-Firmware/blob/development/src/ArduinoAVR/Repetier/Printer.cpp#L1486
GCodeSource::printAllFLN(PSTR("RequestPause:Homing failed!"));
https://github.com/repetier/Repetier-Firmware/blob/development/src/ArduinoAVR/Repetier/Printer.cpp#L2124
GCodeSource::printAllFLN(PSTR("RequestPause:Extruder Jam Detected!"));
https://github.com/repetier/Repetier-Firmware/blob/development/src/ArduinoAVR/Repetier/Printer.cpp#L2964
GCodeSource::printAllFLN(PSTR("RequestPause:"));
https://github.com/repetier/Repetier-Firmware/blob/development/src/ArduinoAVR/Repetier/Printer.cpp#L2979
GCodeSource::printAllFLN(PSTR("RequestContinue:"));
https://github.com/repetier/Repetier-Firmware/blob/development/src/ArduinoAVR/Repetier/Printer.cpp#L2991
GCodeSource::printAllFLN(PSTR("RequestStop:"));
Why didnt I see it...
But Is this really something that gets understood by repetier-server and -host?
Would it be wise to send
GCodeSource::printAllFLN(PSTR("RequestStop:"));
at boot time for nasty crashes/emergency stop button hits?
Greetings from Stuttgart again
What you have above is just like a pause form host/server only requested from firmware side. If you really rebootet you will not know why any more and also since "start" is always first line hosts will already react to it.
I begin to understand.
And I guess that "blablabla"-start did not make the job right. Reason for my questions are that I formerly had crashes because of this https://github.com/repetier/Repetier-Firmware/issues/691 or just because I did not see things right while developing.
It might have been such an behaviour:
Now I put some println(); bevor "start" and I guess that will never happen again.
And Conrad put some "If debug output" in front of "start" so I have to remove this.
If I still would have problems I can play with it and test.
Many thanks for your input on this!!