@honeycris I think you be better off replacing the fuse with the same size that blew. Then move that 800W bed onto its own external mosfet and power line.

@fcwilt Yep Thanks for the help Put my settings inside the loop like you have. Works perfectly.

I got it... I love it when a plan comes together... Found the correct GPIO pin:

#68 located in device /dev/gpiochip1

thanks for putting up with my noise everyone

If you have one of these SBC's feel free to hit me up if you run into issues.

@paulhew I've been using it since it was turned on and it actually been pretty accurate and is spinning up my case fans reliably. So Far.

@fart_plume Right. That's correct. they only receive data during a print. should switch to :

Pulse-type filament monitor on pin io4.in, enabled, sensitivity 7.000mm/pulse, allowed movement 50% to 200%, check every 15.0mm, no calibration data

while printing. I cant remember what condition they collect calibration data under... if in doubt cut the filament.

@phaedrux said in Ask user to set bed temperature before bed mesh probing:

M291

How about writing a conditional macro placed the start gcode in your slicer to load a low|medium|high heightmap based on printing temp?...

@phaedrux Here is mine in io.4 of a mini5+

Black supplied wires reading "up" v3.3, signal, gnd.

On the sensor side I left it the way it comes from BTT. Which looking at it from the label side is a 4 pin plug only populated in 3 |V _ S G|
Where v is ~3.3-5v

in config.g
M591 D0 P7 C"io4.in" L7 R50:200 E15 S1

"M591 D0
Pulse-type filament monitor on pin io4.in, enabled, sensitivity 7.000mm/pulse, allowed movement 50% to 200%, check every 15.0mm, no data received"

I need to tweek the setting but its working fine.

@nurgelrot Nope. Don't use this one either It cools the board but causes it to drop below 4.6V from time to time... Who would think it so hard to find active cooling that works. Guess I'll wire a Noctua 40mm 5v right of my 5v PSU. Was hoping to not have to do that but since no one can make simple fan that doesn't block the header or screw up the voltage...

@keyz182 Man both myself and my browser's search function are blind.... okay well i set it the way i should have it through dumb luck. I can live with that.

Okay I removed the Q500 and that did the trick... I didn't think that would have any effect since they aren't PWM fans. And Q500 is listed for the default so you'd think that's what would be there even if it was not set but.. Fan is going like blazes now.

Please post pictures of your actual board and the relay wiring and momentary power on switch. I think there is an issue with what you are expecting voltage wise on you line from the duet to the relay but myself and others will want to see the wires before making blind suggestions that can damage your board.

@kb58 said in Number of probe point 400x400 bed?:

Anything more than than is impossible to answer.

I agree we can put this one to bed... Oh man that was a bad pun.

@fcwilt Well I don't see the point of getting into -my bed is more level than yours- discussions. But that first image proves my point. If the bed is that level why do you even apply mesh compensation? Its a tool to correct for crappy beds if you have a bed that is manufactured to that level you don't need it. The second one too cuz that one data point has to be a probing error (unless something really odd is going on with that bed) If it is an error you would be better served to have it averaged out. And #3 is a good example of a bed mesh. Still don't think you needed that many points but like you say if you have the time and don't mind gathering them...

@fcwilt I understand what you are saying and yes I agree more points are better. Especially in a theatrical model built in software. However what I'm getting at is: Are more points actually useful? (especially in terms of the time it takes to gather them).

For example you and I are both printing on reasonably smooth surfaces. Say glass on top of a aluminum heat spreader. Assume some warping for heat nothing too crazy. If I print a line between my point 0,0 and 50,50 and you do the same between 0,0 and 50,50 is there going to be a significant difference in +/-Z using my average and yours? Sure you gathered 2+ time the number of data points but over ~50mm glass was that useful? Factoring in the .005 accuracy of a BLtouch and the manufacturing tolerances of a better than average consumer 3d printer I just don't think so. The number model in the the software shows variation but at some point there is a trade off. At that point you're just collecting number for the sake of numbers. That's the point I'm looking for.

It will be a little different printer to printer sure layer height nozzle size and all that would could come into play depending on what you are printing. But I'm finding that for a better than average modified consumer grade printer ~80 or so points is enough. Ironically on a better printer where the data would probably be more accurate, useful and consistent you probably don't need it since your build surfaces would be better.

@engikeneer I'll take all the posts under advisement. I still think you guys with high probing numbers are chasing fairy dust. I have a really hard time seeing how 2 stepper motors ~430mm apart who are in turn attach to a 400+/- mm not to precision made threaded rod is going to have the ably to constantly adjust points in space that densely packed. I feel you are collecting more data then you can use. A 9-12x12 will average out to the same as a 20x20 and take far less time to setup.

Maybe I'm totally wrong; Sure wouldn't be the first time. I'll try some prints and see.

@kingofthegeeks yeah that's my concern too want a mesh that works but doesn't take and hour to probe for. 8 or 9 way grid seem to be the sweet spot for working mesh/time

@generisi Just a Bltouch nothing fancy. Im thinking of giving the IR probe a go cuz I have a bed it should work well on but I haven't found a good way to get it mounted to the correct height yet.

@fcwilt That sound like massive overkill to me. Need to work withing the limitations of the hardware tolerances. You're just rattling around inside the massive error cone that is probe accuracy and consistent thermal expansion with that many data points.
Also my Duet Mini 5 gave an error last time I tried that may points. Wont do 20x20. It will do 20% spacing which works out to about 17x17 I think. Maybe I have something miss configured..

Hello, What's a good number of probe points to build a mesh for a 400x400 bed? Been experimenting trying to find the best trade off for time vs usefulness. 8x8 is looking pretty good. More Less?

@phaedrux The RRF config tool makes them as 500 as well. So that may need to be updated