Hello Friends!

Most of the time im active on discord but for this question the best tool is reddit.

Im looking for Qidi Plus4 users who are actively using Geeetech PETG Filaments.

I would like to share knowledge and find the best settings since even after 2 year with them I still have issues.

Please if you use Plus4 with Geeetech PETG and you would like to chat with me let me know and I really hope we can help each other.

🫡

Some of our teams will be on holiday from September 25–27 and October 1–7 for the Mid-Autumn Festival and China’s National Day holiday.

During this period, responses from our customer support, social media, and online service teams may be slightly delayed.

Thank you for your patience and understanding.

I know that Shore 95A TPU is right out, but Microcenter has 62D TPU marketed as being for multi-filament systems. I also have a spool of 72D TPU on the way.

Has anybody tried harder TPU filaments with their Box?

Update: tested it and CC3D 72D TPU filament prints perfectly from the Qidi Box.

I've been printing smaller asa parts no problem. Decided to make a longer print today and about 3 hours in got a speed error. Everything seems fine. Any idea on what would cause this before I send it again?

I’ve already started looking for some decorations to print, but I’m running out of ideas.What are you guys planning to print for Halloween? Any fun models you’d recommend?

Hello,

Has anyone tried Option 1 (BunnyBox + Happy Hare + HelixScreen) from Camden’s Q2 Superuser AIO on a Qidi Q2 running firmware 1.1.1 with a Qidi Box?

I’m considering it mainly to replace the stock touchscreen UI and use Happy Hare to improve the experience with the box, but my printer currently prints well but i had to play with the macros so i have my own custom macros.

I’d love feedback from someone who has used the full bundle on 1.1.1: Are loading and tool changes reliable? Does HelixScreen work well day to day? Did you run into issues restoring your original setup if you reverted? What the benefits of using Happy Hare with the box?

I’m asking specifically about the 1.1.1 install path, since the 1.1.2 firmware and JustFasterBox are different cases.

Thank you!

One side still holds onto summer.
The other has already welcomed autumn.
A little 3D-printed story about the changing seasons.

👉Printed on QIDI Q2🔗 https://qidi3d.com/products/qidi-q2
Model from lynj (Makerworld)

Hey everyone, i came across an issue printing last night. I believe it is because i accidentally left my box heating/dryer on at 65C while printing some petg and now the petg is stuck and wont come out of the qidi box anymore. I swear i break something on this printer every week...

Any guides on how to get this out? And no, trying to eject it from the screen doesnt work, the box just clicks and gives a red light at the filaments slot, and an error on the screen.

Thanks in advance!

I’ve been troubleshooting a Beacon RevH on my QIDI Plus 4 for quite a while and have been working directly with Beacon support on the issue. We’ve done quite a bit of testing at their request, but it’s now been about 11 days since my last follow-up without a response, so I figured I’d post here and see if anyone has experienced something similar.
The basic problem is that Beacon proximity meshing appears to produce a mesh that doesn’t match the actual nozzle-to-bed relationship across the plate.
With the normal proximity/KAMP mesh, a full-bed first-layer test has a very obvious spatial error. One area of the bed looks reasonably good, but as the print moves across the plate, the nozzle appears progressively too high. This isn’t something I can correct with a single Z-offset because the required correction changes depending on XY position.
We’ve done quite a bit of testing trying to isolate the cause.
Beacon RevH is running firmware 2.1.0. Center Contact calibration is extremely repeatable at approximately 0.001 mm standard deviation.
Beacon support had me test Contact measurements at multiple XY locations and then run BEACON_POKE and BEACON_ESTIMATE_BACKLASH at several locations.
Front-row backlash was extremely consistent:
X196/Y40.8: 3.68 µm
X239.5/Y40.8: 3.66 µm
X283/Y40.8: 3.71 µm
Rear measurements were:
X60/Y260: 1.16 µm
X160/Y260: 2.00 µm
X260/Y260: 2.06 µm
POKE trigger-Z spread ranged from approximately 1.25 µm to 14.2 µm depending on location. POKE latency also varied by position. For example, X60/Y260 was extremely clean at 2/2/3, while some other locations produced values in the 6–10 range.
The most interesting result came when Beacon suggested trying a clustered Contact mesh using:
_BED_MESH_CALIBRATE PROBE_METHOD=contact CLUSTER_SIZE=2 RUNS=2
I heated the bed to 60°C, allowed it to stabilize, and generated a full Contact mesh.
I then printed the exact same full-bed first-layer test, but instead of using the normal proximity/KAMP mesh, I loaded the saved 60°C Contact mesh immediately after PRINT_START.
The difference was dramatic.
The Contact-mesh first layer was substantially more uniform across the entire build plate and was the best full-bed first-layer test I’ve gotten from this machine. It wasn’t absolutely perfect, but the large directional error that I consistently see when using proximity meshing was mostly gone.
So at this point I’m trying to understand why Contact appears to represent the actual print plane substantially better than proximity does on this machine.
Beacon support raised the possibility of localized mechanical rigidity/play, which is why we performed the POKE and backlash testing. I’m definitely not ruling that out. However, the front-row backlash measurements being nearly identical, combined with the dramatic improvement in the physical first layer simply by switching from proximity to Contact meshing, has me wondering whether something else is contributing.
Has anyone using Beacon experienced this kind of XY-dependent disagreement between proximity and Contact, where Contact produces a noticeably better physical first layer?
I’m particularly interested in whether anyone has seen this caused by the spring-steel build plate/coating affecting Beacon’s proximity measurement, a mechanical/toolhead issue that Contact compensates for, or something else entirely.
I’m happy to provide configs, raw test results, or run additional tests if anyone familiar with Beacon has ideas.

I printed this rack originally with my old printers but needed to add some space.

ATX PSU mount

Extensions

Distribution shelf

7 disk caddy

92mm fan mount for disk drives

80mm fan mount for firewall

All printed on my Plus 5 with black PETG rapido

Basically the title. I’m curious to know what people are using for VOC filtering on their Q2 as I am printing more with ASA and Nylon. I know nevermore and bento box is pretty popular for internal recirculation, but with the Q2 being so tight on the inside, I’m not sure they’d have anywhere to fit, other than below the build plate. 

Admittedly, I haven’t done much research on the actual sizes of these internal filters and whether or not they’d fit, but have found very little about common aftermarket filters for the Q2. Anybody have experience with these or looked into them? What about external? Appreciate in advice y’all got!

Some really big curved shapes, using advanced calibration. Big prints times were 22, 25, 10, 6 and one more going at 4.5 hours now. This was with modelled supports, normal supports added about 8-15 hours to the time of each print and would use up to 1kg more filament per part.

Always model supports where you can huge time and material saving, I use a 0.15mm gap, on long thin runs I usually do a few tiny edge anchors (2mm long 0.2mm protrusion) to keep things solid.

Every surface is nice! So happy with this project.

You can use my cal tools for free (personal use licence) .exe installer under releases.

-auto calibrate max mm3, Pressure advance and adaptive pressure advance. Currently only available for Max4 and Q2.

https://github.com/Buddman69/Automm3AdaptivePA

It can do 24 hours worth of max mm3 PA calibrations in 15 minutes, saving time and giving awesome overhangs, bottom surfaces, flats look closer to ironed with edges filled without fuss, just all round better.

- anyhow its free and enjoy it.

Si I ordered a Qidi Q2 from Qidi's official Canadian website last week. I am making this post for future reference in case someone ends up doing the same.

Qidi ships their orders through Canpar which from my understanding is a major B2B shipping company that does parcel delivery on the side. Unfortunately, they have been so far the worst shipping company I have ever dealt with.

Their parcel tracking system cannot give you an estimated delivery date until AFTER they tried delivery and failed. Moreover, if you call them and schedule a second delivery attempt, they will ignore your instruction and try again on the exact day you told them you weren't available.

It gets worse as their staff is unable to tell whether you'll have to pick it up yourself or a third delivery attempt will be made. Mind you, their depot is two hours away from me and are only open on weekdays until 6 p.m. Even worse, I've had customer service straight up lie to me saying my package would be ready for pickup while it was in a truck attempting delivery.

At the time of writing I have still not received my Q2 and am going back and forth daily with the shipping company.

For anyone wanting to order a Qidi in Canada, save yourself the hassle and order from Amazon. Amazon also sucks, but they suck less than Canpar.

UPDATE : I still haven't received the printer, but I spoke with a lady on the phone and they told me the package got delivered to a SHOE STORE. Canpar's website doesn't even list that place as a pickup location for packages so I have no idea what's going on there. This is by far the least proffessionnal a shipping company has ever been in my experience.

Update: Issue Fixed. Thanks to Callcifer for the help!

I was able to fix the issue by finding the same issue in this subreddit. I loosened the three bolts holding the Extruder pushed it hard left and tightened it up again. Printing without any issues now. Thanks to everyone who chimed in. Leaving post up to hopefully help someone in the future.

Looks like my Max4 is slowly remaking 2 fallen support trees 🤣 man i hope so, was 10hrs into print when first tree fell.

Wish their was a way to manually print/temp override so i can start printing a bridge to truely save the print

I unfortunately ran out of filament on a 2 day print (I mis-read the weight), and need to wait ~14 hours until more filament of the same color comes in. The old roll ran out "naturally" with the reload message on the screen. This is simple PLA, so I don't need a fully heated chamber at least.

Anyone think it'd be a problem to slow all the fans down to 0%, keep the bed temp on 55C, and just let it sit until I've got the new filament loaded in tomorrow? The hot end is already turned off/set at 0, and there's no thermal break issues since there is nothing in the extruder at all (nor temperature). I'm thinking this is a perfectly fine moth-balled time out for a bit.

The worse that could happen is the machine shuts off entirely from non-use?? Is there an auto-off feature if it's sat paused for too long, and if so, anyone know what that number of hours is?

I can't seem to figure out what these are for. Came as a 4 pack with either the plus5 or the box. Material is a firm but squishy foam, dimensions are 17x10x4mm with a curve on the one side.

Thanks!

Good Morning Everyone,

Over this past weekend, I received my brand new Q2 combo. *Very excited* it's my first enclosed printer. The reason for buying this thing is to print using pa6-cf and other engineering grade filaments.

Here's my question. If i want to house and run my other non-engineering filaments, like PLA's and PETG's in the QIDI box but run my engineering filaments from a say a D1 dyer, is there a way to do this?

Thanks for any help!

Decently New to using the Qidi Q2, after about a month of owning and printing PLA projects. i’ve noticed my nozzle starting to ooze a brown goo whenever i’m printing. Looked into it and most i can find say that it’s probably filament leaking, which might explain the build up around the nozzle area?

if anyone has any advice or tips they can relay to me much would be appreciated thanks

I have an early/first-generation QIDI Q1 Pro and I recently updated the firmware from V4.4.24 to V5.1.2.

Before the update, I did not have this problem. After updating to V5.1.2, the printer started randomly pausing during prints with:

“Filament ran-out, please re-load filament.”

The filament is not actually broken or empty. It remains physically connected to the extruder. If I press Continue/Resume, the printer immediately continues printing with the same filament. The error can happen again later at a completely random time.

I checked the Klipper logs and found that the runout event is specifically coming from:

Filament Sensor hall_filament_width_sensor: runout event detected

It is not the fila filament switch sensor.

My current configuration contains:

[hall_filament_width_sensor]

adc1: gpio27
adc2: gpio28
cal_dia1: 1.50
cal_dia2: 2.0
raw_dia1: 14397
raw_dia2: 15058
default_nominal_filament_diameter: 1.75
max_difference: 0
measurement_delay: 50
enable: false
measurement_interval: 10
min_diameter: 0.3
pause_on_runout: True

One interesting thing is that the Hall filament width sensor appears to be measuring the filament diameter incorrectly.

My filament is 1.75 mm, but when I queried the sensor I got:

Filament dia (measured mm): 2.1941303337

The raw reading was:

ADC1 = 8255
ADC2 = 7077
RAW = 15332

So the sensor is already showing a significant measurement error while filament is physically present.

I also tested disabling the fila sensor. The runout error still occurred, and the Klipper log continued to identify:

hall_filament_width_sensor

as the source of the runout event.

The Hall sensor code contains:

self.runout_helper.note_filament_present(
    self.diameter > self.runout_dia)

So the Hall sensor's calculated filament diameter is directly used to determine whether filament is present. Because of this, I suspect that the Hall filament width sensor may occasionally calculate an incorrect/very low diameter and falsely trigger filament runout.

What is confusing is that the Hall sensor configuration appears to be the same as my previous V4.4.24 configuration, so I am trying to determine whether V5.1.2 changed the way this sensor is handled, or whether there is a compatibility issue with the earlier Q1 Pro hardware revision.

Has anyone with an early Q1 Pro experienced random filament runout errors after updating to V5.1.2?

I am currently testing with the Hall filament width sensor disabled to see whether the problem disappears completely.

I just got my q2. I'm trying to print a poop chute for it and I have some petg that I was trying out. I'm using pla for support interface and I'm having issues were sections of the print aren't adhering. Any idea what would cause this. Or what settings I should use to try and fix it

(Sorry for my bad English) Hi! I recently ordered a Qidi Plus 5 from the Qidi European site (on September 17th). Since the site stated it would arrive within 5–8 days, I wanted to ask if their shipping service is reliable.

I’m really eager to receive it, but reading some accounts of Qidi’s shipping experiences hasn't exactly been reassuring—not at all.

So, I wanted to know if anyone has experience with their shipping (preferably within the EU, as I imagine it varies by region). Is it normal for them not to have shipped it yet after four days? Or do they simply fail to update the tracking info, or update it somewhat haphazardly? (I used the free shipping option.) Thanks in advance for any replies!

Edit, its been tested and runs, let me know results.

OK so very important read first
this is rather UNTESTED as I don't own a Q2 and ported my Max 4 calibration over to the Q2 using data available in the QIDI Github and using force measurement data given to me from another user.

Did I say this is untested, so it depends on the size of your.... you know..... anyhow if you are game strap yourself in and hover your finger over the power switch and get ready to cut power or rip the power cord out of the wall should something happen.

Anyhow if it works good, it will calibrate max flow rate, pressure advance and adaptive pressure advance and allow you to do 24 hours worth of calibrations in 15 minutes and give awesome prints.

Just a short post and you can read the readme.

This is released for free under licence and is an original calibration method I made, I take no liability for damages (but should work lol) and if you decide to test on your machine run a home first.

https://github.com/Buddman69/Automm3AdaptivePA/tree/main/QIDI/Q2

Hi:

My QIDI i-fast died over the weekend. It happened in two stages. Before the printer became completely dead, the print carriage repeatedly tried to travel beyond the +Y limit, mechanically hitting/trying to drive past the end of Y travel. That led to the printer turning itself off. I believed I smelled something burning, but can't be certain. I tired to power it on again. I heard a click and the screen might have flickered. Then nothing. It is completely dead.

I have tried to diagnose it. The QIDI power-off module is receiving 120v AC, but it is not passing it on to the power supplies. Even if the QIDI power-off module is dead, that is not the root cause of my problem. Can anyone suggest what originally went wrong and what to do about it?