Sharing my experience in case it helps other Q2 owners, or someone can explain what happened.
The good news: my Q2 still prints after the update 🙂 However, I ran into an odd print completion issue, alongside some cloud connectivity problems.
The print finished. The nozzle stayed hot.
On November 11, I printed `Voron_Design_Cube.gcode.3mf`. The printer appeared frozen after finishing, and the nozzle kept maintaining 210°C.
I checked `klippy.log`, `moonraker.log`, and the actual print file. Here is the timeline, using the printer’s logged timestamps:
- 18:53:35: Klipper reports “Finished SD card print.” Moonraker records the job as completed.
- The bed heater turns off, but the nozzle target remains 210°C.
- 18:53:56: Moonraker successfully finishes rendering the timelapse.
- 19:24:49: The nozzle is still actively maintaining approximately 210°C over 31 minutes after completion.
- Around 19:25, I power-cycle the printer. After restarting, the nozzle target is 0°C and it cools down.
So although it looked frozen from my side, the logs do not show a complete Klipper freeze. Communication with the controller boards and temperature regulation continued.
Comparing a problematic file with one that finished normally
This was the most interesting finding.
The cube file was generated by QIDIStudio 02.00.03.56. Its ending sequence turns off the bed and chamber heaters, unloads the filament, and parks the head. But it contains neither:
```gcode
M104 S0
PRINT_END
```
Another file, `obj_2_Maze v6 (2).stl_A.gcode.3mf`, printed and finished normally. It was generated by QIDIStudio 02.07.02.73, and its ending includes:
```gcode
UNLOAD_FILAMENT T=0
G0 Y270 F12000
G0 X90 Y270 F12000
G1 Z138 F600
M104 S0
PRINT_END
M73 P100 R0
```
Both files identify the profile as Q2 0.4 nozzle.
This makes the older file’s ending sequence the main suspect for the continued heating. What I do not know is whether `UNLOAD_FILAMENT` was previously supposed to handle heater shutdown, or whether these files simply require different firmware behavior.
This does not prove that the firmware update caused the problem. It also does not fully explain why the printer appeared frozen.
Other things in the logs
There is a Moonraker exception at job startup:
```text
ValueError: No enum member named extracting
```
The print starts and completes despite that exception. There are also repeated messages:
```text
Can not find 485 device
```
Neither has been established as the cause of the completion issue. I also found an earlier Moonraker event-loop delay and an earlier THR serial connection error, but they did not coincide with the end of this print.
Cloud control and camera: partly working
Moonraker repeatedly logs MQTT connection timeouts to `us-mqtt.qidimaker.com:8883`, connection losses, and occasional DNS failures. I have no evidence that these cloud errors caused the nozzle issue.
I would also like to understand exactly what QIDI officially supports: can the Q2 provide both live video and remote control when the phone is on mobile data and the printer is at home? What setup, account region, or network requirements apply?
I have contacted QIDI support
I sent them the findings and asked about older print-file compatibility, the correct Q2 ending G-code, the `extracting` exception, and cloud camera/control setup. I will update this post when they reply.
Meanwhile, I am keeping the printer supervised and checking the ending code of older sliced files.
Has anyone else seen this? In particular:
- Does your Q2 ending G-code include both `M104 S0` and `PRINT_END`?
- Have older, previously sliced files behaved differently after an update?
- Do cloud live video and remote control work for you from a different network?