Clifford Roche

@FormerLurker I had the same issue, I can confirm that it's working now on the devel package.

I found a new case, though most of my prints have worked this one fails ``` Send: N43661 G1 X147.902 Y114.831 E-0.14948*78 Recv: ok Send: N43662 G1 X148.208 Y114.831 E-0.09100*75...

I updated to the latest release on the dev branch before re-running and confirming (this morning).

Actually I think this issue is also caused by #94 and isn't fixed yet. I pushed a PR #100 though, and since the reconnect message was already corrected I think...

@ProfEngr the case you described should be fixed then by #100 once it is merged and released. LWTT has its own option for retain, which you should set to enable,...

Thanks @Kunsi . I think that's a fair proposition, I'm ok to close this issue if you agree.

If you check `octoprint/progress/printing` section at https://github.com/OctoPrint/OctoPrint-MQTT progress is only reported in seconds. If you are seeing "hh:mm:ss" then I believe you are using the [HomeAssistant-Discovery](https://github.com/cmroche/OctoPrint-HomeAssistant) plugin. If you are...

This will be fixed by #100

I'm seeing this problem too, sometimes mid print and fairly reliably when calling `ERCF_UNLOAD`. I've been investigating for the last couple of days, and noticed that the "timer too close"...

It dawned on me, the issue might be latency in solving the steps for the given hardware configuration. More microsteps and a long path means more solving to do. I...