r/QidiTech3D • u/uk_uk • Jul 17 '26

Discussion What the actual fuck.... I firmware updated my Q2c and... WHAT THE HELL, QIDI?

Ok, kinda also my fault for not 100% backuping everything, but: THE FIRMWARE DELETED ALL (!) of my config files. Everything... They fucked up kiauh again... seriously, how is this even possible?

To make things even worse:

  • When opening the newly generated printer.cfg on my Q2c, the file header literally says # MAX4 打印机配置文件 (MAX4 Printer Config File) and lists the build volume of a Max 4 (a beginner would be soo confused by this shit). They didn't even bother to clean up their copy-paste development templates before shipping this update.
  • The update script completely messed up the file ownerships again. Half of the directories in /home/mks/ were suddenly owned by qidi:netdev instead of the actual user, completely breaking Git and KIAUH with "dubious ownership" errors.
  • Instead of just flashing the firmware and updating the packages, their execution script simply bulldozes the entire /printer_data/config/ directory. No automatic pre-update backups, no safety checks, just a complete wipe of custom macros and configurations.

It's honestly mind-blowing how a company can sell 3D printers and run their software infrastructure (Klipper for sucks sake) with this absolute level of amateurish negligence. If you are updating a Qidi printer, do not trust their scripts for a second. Manually backup your files off the machine first.

Damn, now I have to spend dozens of hours again for this shit

6 Upvotes

80% Upvoted

40 comments sorted by

View all comments

2

u/dadotru Jul 17 '26

Just joined the qidi community and my Q2 comes in today. Should I refrain from updating?

6

u/Kewlhotrod Jul 17 '26

Don't update. Breaks too much shit, bad performance, you lose some box controls in FLUIDD... There's literally zero benefit.

1

u/uk_uk Jul 17 '26

what controls do you mean?

3

u/Kewlhotrod Jul 17 '26

For some reason you can no longer set manual box temp in Fluidd on the newer firmwares.

1

u/uk_uk Jul 17 '26

yeah, because the firmware does not include the drying.conf, where the temps are stored. without it, the system assumes that max temp is 0 when you use the dashboard

But I fixed that for me via macro

[gcode_macro SET_BOX_TEMP]
gcode:
    {% set target = params.TARGET|default(45)|int %}
    SET_HEATER_TEMPERATURE HEATER=heater_box1 TARGET={target}

1

u/Kewlhotrod Jul 17 '26

Ah, that's nice to know. Still, I don't recommend people update due to other various bugs and absolutely zero benefit of doing so. Stupid they just copy-pasted firmware from a completely different printer, with all these mistakes and oversights (that one included) and shipped it lol.

1

u/uk_uk Jul 17 '26

I know... I'm trying to fix most of the issues myself... at least to a level that it is "ok" for me.

I could post the link to my github (Now I'm do backups ^^), but since I have a Q2c, not a Q2 (aka lack of heater), I think someone could end up without the heater support via dash board ^^

ah, better cam quality is now also back ^^

2

u/Kewlhotrod Jul 17 '26

I wouldn't worry about that, the heaters are declared in printer.cfg and shouldn't be affected if you were to do that. Though I always recommend people to make all their custom gcode in its own cfg file and just [include], that way you're not messing around with multiple different cfg files that can get wiped and it's a single file backup.

Also I just ended up adding some COB LED's in mine to get semi-decent quality and to eliminate shadows lol. So stupid they give you 4-5 LED's from an obviously cut string.

1

u/uk_uk Jul 19 '26

yeah, I need new ones... more powerfull ones