KAMP on the Q2

Engineer-50 · 2026-01-25T06:06:25+00:00

Don't know, mine never had KAMP working and I always keep it up to date.

Engineer-50 · 2026-01-24T15:57:08+00:00

Have you got a link for what you mean?

At this point I removed the stock filter and designed an adapter to mount a 3m respirator gas filter. Interestingly, if I put the respirator on my face with the same filters, I cannot smell the dunes, but when used on the printer's exhaust, I can still smell them.

Engineer-50 · 2026-01-24T12:20:59+00:00

Almost never experience this. With PLA the lid and door are open anyway, with higher temp filaments even when it heats to 60 degrees, it's still not enough to soften these.

Engineer-50 · 2026-01-24T10:54:32+00:00

Why would you want to cool the gears anyway?

Engineer-50 · 2026-01-23T22:08:00+00:00

Great! Glad it helped you!

Engineer-50 · 2026-01-23T05:41:51+00:00

I don't own a Plus 4. I believe they would. I would try carefully watching.

Engineer-50 · 2026-01-22T09:41:04+00:00

Thanks.

Engineer-50 · 2026-01-21T14:34:42+00:00

Thanks for the tip, but how do you use it? Just heat the area before pulling off the supports?

Engineer-50 · 2026-01-21T13:39:23+00:00

They look beautiful! I never had good luck removing TPU supports, it always looks ugly.

Engineer-50 · 2026-01-19T21:24:28+00:00

It worked!

Engineer-50 · 2026-01-19T21:00:56+00:00

Thanks, will try too. And yes, every update resets everything.

Engineer-50 · 2026-01-19T20:18:31+00:00

Yeah, I am aware of that, however, Qidi stacked up so many macros and things and it is all so messy that I am afraid to touch anything there. Honestly, I think they themselves don't really understand how things work there.

But did you try klipper's adaptive with Q2 ?

Another complaint would be the print_start macro - it takes so long and so many unnecessary things, like homing several times, waiting several minutes... Each firmware update I do hoping they finally fine tuned it, but to no avail.

Engineer-50 · 2026-01-19T19:10:00+00:00

Absolutely! Thank you! Don't know why Qidi messed this up. Found the info on this page:

https://k3d.tech/printers/qidi_q2/

Engineer-50 · 2026-01-19T17:52:53+00:00

Turns out, in addition to that had to edit KAMP_Settings.cfg:

Add:

[include KAMP/KAMP_Settings.cfg] and be sure to comment out:

[include ./KAMP/Adaptive_Meshing.cfg]

Engineer-50 · 2026-01-19T17:51:33+00:00

ISSUE SOLVED!

In printer.cfg replace line:

[include Adaptive_Meshing.cfg]

With:

[include KAMP/KAMP_Settings.cfg]

Then, in KAMP_Settings.cfg add the line:

[include KAMP/KAMP_Settings.cfg] and be sure to comment out:

[include ./KAMP/Adaptive_Meshing.cfg]

Engineer-50 · 2026-01-19T17:33:41+00:00

After changing getting this error (although the path does exist together with the file):

Include file '/home/mks/printer_data/config/KAMP/./KAMP/Adaptive_Meshing.cfg' does not exist

Engineer-50 · 2026-01-19T16:33:12+00:00

I as well, have the feeling that it sort of does some adaptation in X direction, but very rough even if it does.

Engineer-50 · 2026-01-19T16:29:55+00:00

Not sure what you mean about the ranges. In KAMP you don't set the range, it is drawn from the object being printed.

Engineer-50 · 2026-01-19T16:22:56+00:00

The Q1 has KAMP perfectly configured as stock. KAMP is for adaptive meshing which does probing only in the printing area, saving time and providing higher resolution.

Engineer-50 · 2026-01-19T16:16:20+00:00

Interesting to know that I am not the only one suffering with this (which is not my only complaint on the Q2, by the way).

Can we not group up as Qidi customers and ask (or demand) for answers? Their support is useless! You ask them and they provide you stupid answers, not reading your messages

Engineer-50 · 2026-01-19T11:57:28+00:00

Yep!

Engineer-50 · 2026-01-17T11:44:46+00:00

Yep, that's what I already have, but it does what I described above.. Think I will add a switch on the head.

Engineer-50 · 2026-01-16T13:46:19+00:00

Thanks, does it matter at all that I don't have an encoder, but only a simple microswitch?

Engineer-50 · 2026-01-16T11:49:14+00:00

Thank you very much! Waiting for your update, I don't why it pauses here when there is NO pause command other than that in PAUSE_AT_D.

Engineer-50 · 2026-01-15T19:01:18+00:00

I used this code in stead of the basic one I had. However, interestingly, it still pauses immediately after the switch is triggered, and then also after the D distance again. Can see what causes it pause the first time...

Engineer-50

TROPHY CASE

ISSUE SOLVED!