Closed probonopd closed 5 years ago
ok.. that's a weird thing in prusa firmware...
KEEPALIVE_STATE(NOT_BUSY);
while ( (target_direction)&&(!cancel_heatup) ? (isHeatingBed()) : (isCoolingBed()&&(CooldownNoWait==false)) )
{
if(( millis() - codenum) > 1000 ) //Print Temp Reading every 1 second while heating up.
{
if (!farm_mode) {
float tt = degHotend(active_extruder);
SERIAL_PROTOCOLPGM("T:");
SERIAL_PROTOCOL(tt);
SERIAL_PROTOCOLPGM(" E:");
SERIAL_PROTOCOL((int)active_extruder);
SERIAL_PROTOCOLPGM(" B:");
SERIAL_PROTOCOL_F(degBed(), 1);
SERIAL_PROTOCOLLN("");
}
codenum = millis();
}
if set system not busy and when open a loop waiting for temp...and it report a custom temp message
WOW it is busy to wait temp but it set a no busy state....that may be defined as pure logic!
Why are some lines not prefixed with <
? Are they not coming from the printer?
yes since there is no ok and is not parsed as a know line it goes to "unhandled"
..and there no timeout reset... I'm working now to fix this and other issue
We should make the code more robust by printing everything coming from the printer to telnet, prefixed with <
, and reset the "alive" timer. Regardless of what it is. And only thereafter try to do something with it. If we can't do something with the line, we could say "Last line could not be interpreted".
<
>
I do not understand what the following means: