@chapelhill I am using this https://www.thingiverse.com/thing:2206664 + a thing I made https://www.thingiverse.com/thing:2868944

It is pretty accurate/repeatable.

@chapelhill I am using a nimble, yes, with their supplied 95 cm cable. My filament is feed from a shelf up the printer, so I don't think that can put any spin on it.

I've been playing/testing different belt tensions on the d-bot carriage to see if there's something that I can do there. Also a dude on the 3d printing discord chat suggested using a bullseye level to check the gantry and I will do that later today.

@deckingman indeed the straight edge on the front helped, the bed is indeed sagging in the middle. I also found almost half a millimeter drop measuring the left side front to bottom.

Somehow, I was able to bend this MIC6 plate.

@dc42 shouldn't that be compensated by the bed auto compensation thing with the independent z motors?

I read that as bed twist, not gantry twist. How one proceeds to try and identify/fix that?

So, I have this CoreXY with a bed made of MIC6 plate + steel plate + PEI, and I use the 3 independent Z screws to do bed compensation/leveling. Even so, I get horrible first layers some times. So I started using the mesh compensation and I get this every time I probe:

(I am using a lot of points on that one to give more detailed visuals). The thing is, I put a straight edge from the red area to the blue area, and tried to fit a 0.03 feeler gauge under it, and I can't find ANY gap, what kinda means to me that I am doing something wrong.

Everything is probed using a Precision Piezo probe, and I tested repeated probing and I get consistently:

G32 bed probe heights: -0.045 -0.049 -0.043 -0.046 -0.044 -0.049 -0.043 -0.045 -0.047 -0.046 -0.045 -0.047, mean -0.046, deviation from mean 0.002

So, now I am kinda lost on what to check? Maybe something mechanic on my build?

This is the bed, the lower right spot with filament squished is where I prime the struder at 15,15, so you can orient that with the probed mesh.

Also, this is my current gcode: https://gist.github.com/coredump/b0e76e62d348a3373ffaa67fd2f31052

Am I overlooking something?

@hurzhurz said in Berd-Air pump configuration notes for Duet users:

@msquared About the flayback diode, your link points to a 1N4007.
I have first tried this one, but it got pretty hot.
After some googling I think the reason is that the diode is just too slow for a high frequency of 25kHz (reverse recovery time of 30us).
I have replaced it by a schottky diode that doesn't get warm.

Are you using a 1N4148 or something different?

@bendiesel unfortunately they are all one piece injected plastic, so it's not trivial to open.

They definitely lower the noise tho.

Responding my own question: that mosfet module that I added definitely blocks the high frequency PWM trick. I took a chance and connected the 24v pump I got from markerhive and connected it directly to my duet wifi (1.02) and with the highfrequency PWM I can run it at 20-30% with minimal noise.

Lets see how many fan ports I burn on this tho

So, did anyone try the high frequency PWM with a module like this?

In my test here, using F500 and keeping the pump running at 30-40% gave me a lot of air, and not a lot of noise (I am using this on both intake and outtake), but the F25000 took away my ability to control the pump speed and sounds a little higher. I haven't tested temperatures yet with the two different F values.

I wonder if I should try to connect the pump directly to the DuetWifi. If there's not a lot to gain from that change in the noise department, I think keeping the module makes it safer.

@dc42 said in Probing speed changes with no reason:

The slow down is intentional for sensors that provide an analogue output that increases as it gets nearer the bed. It allows you to use a higher initial probing speed. But I'm not sure that the piezo sensor is intended to be used in analog mode.

Well it only happens on one of the points, that's what I think it's weird.
And I was following @DjDemonD post here.

EDIT: just noticed this was added after I configured it the first time:

Please note as of RRF version 1.20 you can use M558 P8 instead (other parameters are the same) which is a digital probe but without filtering or smoothing of the signal. This increases accuracy, as it takes less time to react to a trigger.

I will try that when I finish this 5h print...

So I am having a weird issue here. I have a precision piezo to act as a z-probe/endstop on my corexy. It works fairly well with the following exception: sometimes the z speed on probing will randomly slow down.

I have this:

; Endstops
M574 X1 Y2 Z0 S0 ; Define active low and unused microswitches

; Piezo
M558 P1 I0 R0.4 F420 X0 Y0 Z1
G31 X0 Y0 Z-0.360 P600

Firmware is latest (1.21) and it's a duet wifi+duex2.

And I have like 5 points defined on bed.g for 3 lead screw bed leveling. The thing is, sometimes one of the probe points will just be REALLY slow. Like less than half the speed of the other ones (that is set to 420 on G31 above).
I think there must be something to be related to jerk or changing speeds too fast, but I am unsure how to solve that. Maybe lower the travel time between the points so it has more time to 'recover'?

Thanks for any help.

Also I am pretty sure that I should change my M558 because apparently it changed on 1.20.

@dc42:

@coredump:

I am having slow upload speeds via the DWC. Via FTP it works as expected but over the web control it goes to like 20 K/s speeds.

Thanks for your feedback. Can you provide a Wireshark trace of a HTTP upload?

Sure: https://www.dropbox.com/s/4x20l1f4m59r12y/dbot.cap.pcapng?dl=0

But sems to be a lot of window errors and retransmissions. That doesn't happen with port 21/ftp.