Closed probonopd closed 5 years ago
In essence, we are not sending anything to the printer before the previous response started with ok
. And we are waiting for a looong time for this - 240000ms.
I usually don't like the toooo long wait for timeout... I think that we have to detect if printer is live and if communication is still live and have calibrated timeout for it. Going back to your issues during heating, they are because it seems your printer send a different message when it is heating, it sends only current temp. Since temp format is different it is not parsed and it will timeout. I prefer to add anoter timeoutreset in "unhandled" if branch. In that case I reset timer because communication is live and printer is live.... but this is just my idea
Can you implement waiting forever on ok
in a branch, for testing purposes?
I think we need to distinguish two different things:
ok
Does this make sense?
I'm working on it
This is how I was doing it in 1.x and I had never any trouble with it.
Using such a logic should hopefully solve https://github.com/probonopd/WirelessPrinting/issues/72.