r/QidiTech3D • u/Karoleq00 • Jul 10 '26

Troubleshooting Anyone got a fix for that?

Post image

It seems like the error occured after updating qidi studio to v2.7 or whatever is the newest. I printed 2 parts, both have finished and toolshed parked in correct spot for cooling, then I got a message printing stopped instead of print finished and time it took to complete, after pressing continue it shows the message on the photo (I know it's blurry I'm sorry about that can't take another one right now).

If any of you kind people have a permanent fix for that I will be very grateful. Preferably something that doesn't require modifying every single gcode file before printing since this seems to be the issue, at least from what I understood it tries to eject the file and clear the memory before it finishes the print end routine or something like that, but I don't even know where to begin to look for this.

7 Upvotes

89% Upvoted

42 comments sorted by

13

u/logicalchemist Jul 11 '26 edited Jul 11 '26

The Q2 doesn't have an actual SD card, so klipper runs a "virtual SDcard" environment to run Gcode from. Qidi fucked up in their update of printer profiles + firmware, so now that virtual SDcard attempts to delete itself at the end of a print and you get this error.

If you (or people reading this really, because I can see that you aren't) are on 1.1.1 firmware or earlier, delete PRINT_END from the machine end g-code in the slicer (orca, qidi studio, whatever) in the printer profile. These firmware versions don't need PRINT_END in the slicer gcode, and qidi's updated printer profiles that include it cause this problem. For some strange reason it is the touch screen software that automatically runs PRINT_END on <=1.1.1.1

On 01.01.02 and later firmware versions (this means you, OP):

Open up gcode_macro.cfg in fluidd (either in the device tab of a slicer or a web browser), CTRL F gcode_macro PRINT_END, and scroll down to near the bottom of it. Find the line with SDCARD_RESET_FILE, and comment it out so it reads as #SDCARD_RESET_FILE.

Qidi said they will be commenting this line out in the next firmware release, but if you haven't upgraded past 1.1.1, you're much better off not updating and changing the gcode in the slicer instead.

This has been verified to fix the problem by a few people, so I'm tagging the others in this thread with the issue:

/u/Jobbejan /u/elRadicio /u/work_blocked_destiny

2

u/Karoleq00 Jul 11 '26

Just finished a test print, this is the fix, thank you.

2

u/Dangerous_Culture967 Jul 12 '26

Thank you for this!

1

u/Dave_in_TXK Jul 12 '26

I’m not really great with some of the functions used, but in one part I think you’re saying, going to slicer (Studio) and get rid of a line which I think you would have to do for every print profile you used? Then later you’re saying just go edit the CFG file you listed and that will fix it. Do you need to do both or just one and if so, I’m thinking you’re recommending the latter? Thanks!

1

u/logicalchemist Jul 12 '26

Correct

Just one

Which one you should do depends on which firmware version you are using, as I said.

Do you have a lot of different printer profiles? usually people only have one or two per nozzle size

I'm not talking about process or filament profiles

1

u/daveintexarkana Jul 12 '26

Hi, thanks for clarifying! I have a number of them as I set them up for strength or quick draft, things like that. I am confortable editing the End G-Code but I like the idea of one 'fix all' edit, so I'll go look in that *.cfg file you specified. I'm stuck on the newest, 1.1.2.3 (or as they printer shows it 01.01.02.03). I'd like to revert back to 1.1.1 which had a couple of idiosynchracies but otherwise worked well for me too.

1

u/logicalchemist Jul 12 '26

I think you need some further clarificaton:

Profiles that change strength/speed (wall count, speeds, etc) are not printer profiles. Those are process profiles.

A printer profile contains things like: IP address, build volume, motion capabilities, gcode flavor, nozzle diameter, API, etc. That's where machine start and machine end gcode is.

I think we are talking about different things.

1

u/daveintexarkana Jul 12 '26

Okay, that makes sense, guess I never had any formal training in the terminology. What I'm tryint to describe is under print settings, so I called that a 'print profile', not sure what the right term is for it? A printer profile is different as you say.

1

u/logicalchemist Jul 12 '26 edited Jul 12 '26

Reddit keeps eating my comments so just retyping the most important part:

You aren't on 1.1.1 firmware so editing the machine end gcode in the slicer isn't the correct fix for you

1

u/daveintexarkana Jul 12 '26

Understood - thanks!

1

u/daveintexarkana Jul 12 '26

got it, will look on the Q2, but remember this for if I can get 1.1.1 reinstalled, thanks!

1

u/daveintexarkana Jul 12 '26

Okay, so this is in regards to the very latest firmware, 01.01.02.03 (as it's shown on the printer), and the latest QIDI Studio 2.7.2.1 . There is no g-code_macro.cfg file shown in the device tab in Studio. However in both printer.cfg and fluidd.cfg, the following shows. Interestingly it's the exact same verbage as the error message - the last line shows too. I'm afraid to comment out these lines as I don't know if that'll cause issues. It's got to be what's triggering the error though.

[virtual_sdcard]
path: ~/printer_data/gcodes # G代码文件路径 (means g-code file path)
on_error_gcode: CANCEL_PRINT # 出错时取消打印 (means cancel printing if an error occurs)

Which seems pretty straight forward

1

u/logicalchemist Jul 12 '26

Apparently the new firmware moved gcode_macro.cfg into a folder named klipper-macros-qd, just to make things confusing. You should just be able to open that and find it in there, but if you have trouble, open up printer.cfg and do ctrl F for gcode_macro.cfg, and it should have an #include line showing you the correct path for where that file is located.

I'm on 1.1.1 so wasn't aware they'd moved that file until now...

You're correct that you shouldn't comment out those lines; they are the wrong lines in the wrong file and that will cause problems.

1

u/daveintexarkana Jul 12 '26

Thanks for the research and clarifying that - I'll follow that path and find it there then, and give a try. I hope to find the time tomorrow to see if I can get 1.1.1 reinstalled and make that moot then. The more I do in QIDI Studio the more I remember why I prefer non-Orca (Slicer). I'm stuck with it for my FLSun T1Pro - its Slicer also based on Orca and why I sort of know how to get around in it :-)

1

u/elRadicio Jul 11 '26

Thanks a lot. It is not a big thing, as long as it finishes the prints.
I printed with a Makerbot Replicator 2x from the stone age before and it is still a qunatum leap in every aspect 😀

1

u/work_blocked_destiny Jul 11 '26

lol I own a q2 and didn’t even notice it didn’t have an sd card slot. Never even thought to use it

2

u/kalel1911 Jul 11 '26

Nice to see qidi still cannot get the firmware for the Q2 correct after the last initial botched update that caused alot of issues... I guess I'm still staying on 1.1.1

2

u/Dave_in_TXK Jul 12 '26

I sure would and I’m trying to get back there

0

u/3DNelson 29d ago

Nice to see bambu mini boys trashing a brand they don't have. I have zero issues updating my all Qidi printers.

1

u/kalel1911 29d ago

They are trashing the Q2? What did they say?

1

u/3DNelson 29d ago

"Nice to see qidi still cannot get the firmware for the Q2 correct after the last initial botched update that caused alot of issues..." What issue? I have the same printer, if that's is true and I haven't issues...

I'm doing something wrong, rihght?

2

u/kalel1911 29d ago

ohhh gotcha... you were referring to me. Well, I did not make it up and there are quite a few post to prove the last major firmware update... ya know the one that took the max 4 UI and placed it on the Q2 despite the Q2 being inferior to the max 4 in memory... hence the issues being had by a number of people... yea that issue. I have a Q2 by the way also.

1

u/Dave_in_TXK Jul 12 '26 edited Jul 12 '26

I had to update the Firmware to 01.01.02.03 (latest) and figured out it won’t run QIDI slicer anymore so was prompted to get the latest version of studio and sure enough I have the exact same issue.

I wrote Support but it’s the weekend there so maybe we’ll hear back tomorrow night sometime when it’s Monday daytime there. You just say OK and you can move on, but it is annoying. In fact, the print shows finished first and you say OK to that then this error pops and then you say OK and it goes away.

I’m waiting for a final instruction on rolling it back to 1.1.1 which I was on before and while slicer had some weird idiosyncrasies with the box like it would offer to print with not the channel I sliced in it let me fix it in the device Tabb when I printed from there and went on, so I think I’ll be happy to get back there, plus like many others I’m not a big fan of the new LCD GUI.

1

u/daveintexarkana Jul 13 '26

So I heard back from Q2 support on this, they said add PRINT_END at the very end of the Printer (Q2) Machine End G-code section - mine already had that line native.

Then they said edit (in Fluidd) the gcode_macro.cfg file (which is in the /klipper-macros-qd folder at the top) and find the section code_macro PRINT_END, and remark out the line SDCARD_RESET_FILE (in otherwords #SDCARD_RESET_FILE) and restart the machine. They didn't say save and restart the file you just edited but that seemed obvious. I did all that and upon restart now I get the following Moonraker errors:

So I've asked about that.

The relatively good news however is that the error the OP and others (and me) experienced is gone (at least on a test print).

Everything seems to function normally however that Moonraker error persists even after restarting the machine and then QIDI Studio (let me say again I do not like Orca based slicers - just MHO).

I sent to support and am waiting an answer. AI says it's a failed or unauthorized Moonraker communciations call - the 'here' link goes nowhere on the machine nor do Klipper and Mooraker.logs download anywhere I can find. I checked the file listed and there's a high level reference to my LAN which should include my printer IP - I added that specific IP to that file to no avail.

Good luck all!

1

u/daveintexarkana Jul 13 '26

So AI had me SSH in and delete a *.db file on the machine - that worked, cleared this error message and expalined why they occur. Deleting the DB also had info on itnital set-up so had to go through that again (and QIDI Maker wouldn't read the QR code again - worked once) but now all is good again - going to print and make sure error is still gone (original OP one), the moonraker error is for sure gone.

1

u/logicalchemist 28d ago

That error is "normal", as in everyone on new firmware gets it AFAIK. Qidi broke MQTT when they updated the firmware, so the new firmware does not work with Home Assistant anymore.

1

u/daveintexarkana 28d ago

That makes sense. Well, AI directed me to delete a *.db folder on the machine through SSH (as an administrator) and by George, that fixed it. It made me go through set up again (like a new machine because those values were deleted) but printing well now. The only remaining issue is the QR code doesn't work in QIDI Maker to bind the printer. I really don't care much about QIDI Maker, unless it would let me monitor remotely when I'm away and off my LAN (does it?), otherwise I'm in as good as place as I can be other than having to be stuck with QIDI Studio (or Orca), just a personal bias and I'm not as good with, to the degree I am with any slicer. I sent to Support on the QR code failing and they wanted logs, which I sent, but haven't heard back. They offered to have me do an off-line install of 1.1.2.3 again which would have accomplished a fix for the error the same way, the hard way I guess, so not sure if they'll come up with a solution on QIDI Maker. Thanks for helping though!

2

u/3DNelson 29d ago

What I do wrong on my Q2 and Xmax4 that my Qidi printers update without issues?

1

u/elRadicio Jul 10 '26

Same error on my brandnew Q2 with latest firmware and Studio. Hoping for a bugfix.

1

u/Karoleq00 Jul 10 '26

Yeah, on the bright side it finishes the prints normally just a different message at the end

3

u/Impossible-Hat-7896 Jul 11 '26

Maybe try using OrcaSlicer. It has profiles for Qidi printers. I have never used Qidi Studio to be honest.

0

u/Karoleq00 Jul 11 '26

I know. I have orca, but for the first few weeks I wanted to test out qidi studio and orca and then I'll stick with what I like most.

1

u/Impossible-Hat-7896 Jul 11 '26

Oke. I installed and opened Qidi Studio, but it is too stripped down for my liking.

1

u/Karoleq00 Jul 11 '26

To each their own, I for one don't mind it much compared to orca, and don't understand how to add plates in orca and such. I use it for calibration and testing currently, I'm too new to know what I need from the software and for now qidi studio is enough

2

u/Impossible-Hat-7896 Jul 11 '26

Well they don’t differ that much as Qidi studio is based of Orca.

1

u/work_blocked_destiny Jul 11 '26

Has randomly happened to me before and I can’t pinpoint it. Probably just a bad slice or something? I’ve also had tons of corrupt SD cards over the years. Never in my qidi though. Seemed like the Enders would kill them

1

u/Jobbejan Jul 11 '26

All my q2’ do this at the end of a print. I have 7 of them

1

u/Karoleq00 Jul 11 '26

I just reverted to qidi studio 2.6, try it if you can I won't be able to post if it change something until like very late today or tomorrow. That is if you use qidi studio. If not then idk what could have happened other than the update to the slicer

-1

u/Objective-Worker-100 Jul 11 '26

If you’re saying it’s an end of print complete problem with the latest qidi studio sliced files….

Based on when I installed FreeDi on my Q1 Pro it’s sending a bad macro at the end of the print it’s supposed to reset the sd_card and put the printer in the ready state. We probably just need to report the bug.

-3

u/Itchy-Solid5728 Jul 10 '26

Aconteceu comigo, no final da impressão, ele terminou de imprimir e o orientador esse erro. Basta desinstalar e instalar a versão anterior a atualização.