search

Stephan3 / dwc2-for-klipper

A translator between DWC2 and Klipper
GNU General Public License v3.0
160 stars 38 forks source link

Starting next job #56

Closed tealbrains closed 4 years ago

tealbrains commented 4 years ago

Hi,

I think there is a little bug when starting a new job after finishing one. It takes a couple of attempts. The first one will execute the end of the previous job again (it will not load the new job and will display the old one as 100%), then once that is done you have to reload the new job for it to start. That's what I have observed. It's not a major issue as there is a way around it but something I thought was worth mentioning.

Stephan3 commented 4 years ago

I dont know what you are reffering to. For me i start / stop / pause /cancel Jobs daily. i cant reproduce this. maybe your hardware is just very slow?

tealbrains commented 4 years ago

I can try to take a video next time. I can confirm it's not just a one time thing, it's just happened again today. It may not be anything to do with your dwc2 port, maybe it's a klipper thing. It seems as if the previous job had not been fully cleared.

I don't think my hardware is slow: -Host: Orange Pi Zero Plus (quad core) -Printer: Trigorilla (ATMEGA2560)