@dc42

Seems so. It is a Duet Smart Probe based system from SeeMeCNC. Being a strain probe I expected maybe some difference but this was a rather large difference in results.

It makes me think I might want to spend some time tuning the F parameter.

Also let us know what BL version you have got. Depending upon the version you may need different cabling (including a resistor, etc.). You find the version number on the back of the device.

@phaedrux

Thanks! this helped alot! its all working now 🙂

@phaedrux yes it goes away but I had some layershifts when the driver switched to spread cycle during prints, and keeping it spread cycle the entire time is louder, i should try since there was many update since I've tried having it switched, maybe also bad config, I don't know, switching was loud and sounded almost as what I experience now.

@engikeneer @bLiTzJoN

if it is mid band resonance there is a good description here:
https://www.geckodrive.com/support/step-motor-basics/mid-band-instability.html

@dc42 Thanks for clarifying the M669 reporting of S and T.

There has been some discussion of setting S and T to small values, so that the time delay and distance moved after a pause command can be reduced.

I wondered whether you be able to explain a little more about any trade offs as S and T are reduced ?

@jay_s_uk so simple 🙂 thanks

@secure your fan mapping looks wrong

; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P1 S0 H-1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P0 S1 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off

you have the M106 for P1 before the M950 for F1.
you should probably have this

; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H-1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

Note the layout change.
I've also inverted your S values on each M106 as they were incorrect
You should then map F0 and F2 to your tools in M563
This is of course assuming that fan 0 and fan 2 outputs are your cooling fans and fan1 are your heat sink fans

@phaedrux said in DWC - Filament definition help / clarification?:

With regards to filaments, when using a multi tool printer you may have to create multiples of each type of filament if you want to load the same type in multiple tools at once. PLA1 PLA2 PLA3 etc

@chrishamm is planning to change this to allow the same filament type to be loaded in multiple extruders.

@stubbedk not a problem hope it gets you printing again 😊

I want to thank you all very much. I ended up deleting everything related to probe and G30 and now while Z motion homes rrrreeeaaallllyyyyy slow, I was able to make some calibration prints to dial in the machine.

This is a great community and I appreciate you time!

@o_lampe Yes, that's why I asked. It looks like a value of 100 would double the switch speed to around 94 mm/s, I just want to make sure before I start messing up with parameters.
My print profiles are either "fast" (everything above 100 mm/s, except first layer), or "slow" (80 mm/s maximum), so there would not be a problem switching modes mid-print.

@apak

I had so many problems with IR sensors I gave up on them.

I have printers with BLTouch devices, inductive sensing devices and one with the Euclid micro-switch device. So far the Euclid outperforms the others but it was the most trouble to retrofit to my printer. For I new design I would use the Euclid.

Frederick

@fcwilt
Hello Frederick

Yes it worked. Thank you.

Maybe it didn't work because it's still at the endstop-triggering position and prevents any movement. I just misread ''terminate'' -> it seems it means both directions

"H1 terminate the move when the endstop switch is triggered and set the axis position to the axis limit defined by M208. On delta printers, H1 also selects individual motor mode as for H2. Normally used with relative motor coordinates (see G91)."

@phaedrux I was referring to a custom one that you'd have to write first. I believe ExecOnMCode lets you replace any code with a custom command and DuetPi Management Plugin handles several standard codes before they are sent to RRF.

Have a look through this article, the info in it allowed me to get the mesh and levelling / zero system working properly on my build.

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

Be very careful to follow the exact sequence for the initial probe setup and length offset measurement for that.

@o_lampe said in 2nd print too high and z-offset is inconsistent,config problem?:

I also repeat the G31 line everytime I change M558. I'm afraid it'll use default values instead, if I don't. (paranoid?)

Definitely paranoid. The G31 restatement is unneeded.

@cosmowave said in 2nd print too high and z-offset is inconsistent,config problem?:

your end code is not really nice if you print an object near zmax! So the z axle can't raise 5mm.
It moves the z axle 5mm if it is possible.
If not, it moves to zmax.

Also unnecessary. If the axis limits are set correctly, the firmware won't allow it to go beyond z max anyway, so a relative move close to the z limit would stop at zmax regardless. No need for conditional gcode there.

@lui2004 Did you end up figuring out your problem with the second print start?

@merlin246 perhaps use

M376: Set bed compensation taper

Then after the taper height I guess there shouldn't be any mesh related z moves for the rest of the print?

Just a thought...
Cheers
Barry M

@thedragonlord There's very little angular momentum on an extruder motor. The distances moved for direct drive extrusion and retraction are very small. You may hear more clicking as it goes back and forth rapidly, but I don't think there's much more wear and tear. I run 6000 on a titan aero without issue. I thought 4000 was a safe compromise.

So for folks trying to understand how tpwmthrs is calculated, and especially how to convert it to mm/s...

12,000,000 / (256 * tpwmthrs) = steps / second You need steps per mm from M92... be careful with units... Then multiply mm/step * step/second

Using evan38109's config as an example:

M350 X32 Y32 Z32 E32 I1 ; configure microstepping with interpolation M92 X{400 / (18 * 2) * 32} Y{400 / (18 * 2) * 32} Z6400.00 E1674.00 ; set steps per mm

They're using 32 microstep units, and M92 gives microsteps per mm.

400 / (18 * 2) * 32 = 355.55 microsteps / mm 355.55 / 32 = 11.11 steps / mm

So for 40 tpwmthrs...

(1 mm / 11.11 steps) * (12,000,000 / (256 * 40)) = 105.5mm/s

The 12,000,000 comes from the clock frequency, tpwmthrs is in units of clock period Check out the datasheet: https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2160A-datasheet_Rev1.06.pdf