search

bigtreetech / PandaTouch

123 stars 14 forks source link

Manual Pause - Load / Unload greyed out #25

Open UBEXHH opened 7 months ago

UBEXHH commented 7 months ago

When you manually pause a print (or the gcode has a M400 U1 pause) Panda Touch does not let you LOAD or UNLOAD the filament. You have to use the original printer interface to get it working.

Strangely the messages do appear (pull out or Done/Retry after loading)

Please fix

The number of issues is rising but I do not see any activity from bigtreetec. No categorization, reaction, first thoughts, prioritising, dispatching, help, support

DoTsTeR77 commented 7 months ago

Ya.. that occurred to me too.. not a peak from them... kinda figured at least 1 firmware update by now fixing a few things.. then again it's Chinese new year till the 16th.. so there's that.. but doesn't some ofvteam operate out of south Africa. Idk.

On Sat, Feb 10, 2024, 1:17 AM UBEXHH @.***> wrote:

When you manually pause a print (or the gcode has a M400 U1 pause) Panda Touch does not let you LOAD or UNLOAD the filament. You have to use the original printer interface to get it working.

Strangely the messages do appear (pull out or Done/Retry after loading)

Please fix

The number of issues is rising but I do not see any activity from bigtreetec. No categorization, reaction, first thoughts, prioritising, dispatching, help, support

— Reply to this email directly, view it on GitHub https://github.com/bigtreetech/PandaTouch/issues/25, or unsubscribe https://github.com/notifications/unsubscribe-auth/BF5SL7N7OK4OIUPUFS5SLTTYS4GIFAVCNFSM6AAAAABDCPORV6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDQMJTGQZTIMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

UBEXHH commented 7 months ago

Before or after the 16th... nothing happens. No reaction, no classification, no priorisation, nothing. Sad.

looxonline commented 7 months ago

@DoTsTeR77 I was also on vacation during the shutdown.

@UBEXHH We immediately got to work on the PT after returning but there were other priorities that it took precedence over the new firmware release. This issue has been logged for consideration for the V1.0.3 release.