Bug: Luban in 3d printing when connecting to printer

[jenkins007]

🐞 bug report

Affected Version(s)

The issue is caused by version x.y.z

Is this a regression? (optional)

Yes, the previous version in which this bug was not present was: ....

To Reproduce

Steps to reproduce the behavior:

1. Go to Luban Workspace
2. Move the Print module away from the Home spot.
3. Click on Connect
4. See screen panel that stated Go Home. You must click on OK, then wait for the printer to go home.
5. Most of the time I send the gcode to the printer. Luban should not be on hold to go home.

A clear and concise description of the problem and expected behavior...The program (Luban) should not wait for the printer to go HOME when connecting. If anything, this should happen in the background if nothing else is being printed (although connecting to the printer when printing is disrupting to the active print job. However, 90% of the time, I send the gcode file to the printer. The printer should manage in this situation. If starting on Luban, go home during the print job activity as the starting point. BUT do not pause Luban just to connect.

Exception or Error (optional)

• Operating System: [macOS Monterey] on M1 iMac (ARM)
• Printer: [Snapmaker 350T]

[jane-rose]

Due to some limitations of the machine, doing some other operations (such as printing, etc.) when go HOME may cause abnormal machine status. So we define go HOME as blocking behavior.

[zeroClearAmerican]

I was able to recreate this organically with version 4.4.0. I downgraded to v4.3.2 and no longer experience the blocked UI.

@jane-rose for me, the printer isn't doing anything when Luban is blocked. When first connecting to the machine Luban tells the machine to home. After the machine has completed homing and given the "ok" message, the modal does not go away, blocking the rest of the UI and forcing me to restart Luban.

75% of the time, the exact same thing happens after restarting Luban and/or the machine.

[jane-rose]

Since i coultn't reproduce it. Please tell me more about it, firmware version and are there any special steps or phenomena? When blocking, is the screen connected to the Internet and luban?

[zeroClearAmerican]

Firmware version: Snapmaker2_V1.14.3_20220617 Luban version: 4.4.0

Steps I take to reproduce:

1. Start Luban (computer is connected to internet)
2. Select Workspace
3. Connect to printer (over wifi) and select "ok" when it says that the toolhead needs to return home
4. Machine starts homing the toolhead (still connected to WiFi and to Luban) a. Luban UI is blocked by the "loading" modal while machine is homing the toolhead
5. Printer returns "ok" to the console window after homing but Luban never removes the "loading" modal, which blocks the UI and any menu options.

Only way to restore functionality is to restart Luban, which often times results in the same thing.

[zeroClearAmerican]

@jane-rose any update on this? I'd like to be able to upgrade to Luban 4.4.0 for other reasons but I can't even use the machine with 4.4.0 because of this issue.

[marhaus]

I have the exact same problem with Luban 4.4.0 but on the Snapmaker Original (firmware 2.11). See screenshot; the console obviously says "OK" from the machine but the "Go Home" window never vanishes.

[sesobebo]

Same problem here. Luban 4.7.0 Snapmaker Original (firmware 2.11) Windows 10

The printer is connected to PC with a USB cable.

[ChilliSawse]

Same issue for me, attempting to connect over USB with a Snapmaker Original. Not only can Luban not recognise the printer I am using but when I input the details I get the same result. Asked to home, click okay, the tool head moves and homes but the popup with the spinning circle never goes away.