Closed tomek-szczesny closed 11 months ago
Okay my test pattern generating code does the same with parameter "32", worth noting.
please don't translate :joy:
Nice find, I can reproduce it. It seems the PnP is rather prudish.
Maybe the new image parsing code will solve it.
What new image parsing code?
with parameter "32"
Which parameter?
The new image parsing code I've declared to work on in 420p support. I think something's wrong with data sent to the printer, it must be getting more bytes than it anticipated or something.
My test pattern procedure, when run with parameter "32" reproduces similar behavior.
I removed matrix optimization code and this issue appears to be resolved. The printer prints profanities just great, and --test-pattern 32
works as well.
I pushed it into my test pattern pull request.
I cannot explain how this happens, but I found a set of magic words that crash the printer. For any reason, the crash happens only with them and I didn't find any other working combination!
This combination works:
dymoprint dddd ccccc cccc
And this one doesn't:dymoprint dupa cycki chuj
(all those are profanities, please don't translate. That happens to be my usual test pattern)The printer prints the first batch of data (what looks like three small c's in one row, and then times out. The printer must be turned off and on again to send a new task to it.
I also determined that "dup cyc chu" still works, but crashes after fourth letters are added to each word. I suspected the matrix optimization issues but nope, if "dd cc cc" works I'd rule that out.
Maybe the new image parsing code will solve it.