Hello Tony, Thanks for your reponse. Any idea how the firmware would react to very high values like displaying pressure in pascal (1bar is 100000 pascal) or Kpascal. If i use absolute pressures the values that i need should be in the range of 50 to 150 kpascal. I assume that this should be fine for the firmware?

@Loris

you can use a raspberry pi and map the sd card folder in any way that you like.

Glad that worked out. Adjustable probing depth could still be useful. Though I think something could still be worked out with conditional gcode and the commands as they are available currently.

@dc42 said in Just thinking out loud here...:

Yes I have been considering that. Machines with Z min endstop switches (and no Z probe) would benefit from this.

One discussion that came to mind as I pondered this was a person who had XY end stop sensors outside the min/max range but wanted to keep M208 to just the valid ranges for printing.

So the use of G91 G1 moves and G92 was mentioned to him.

Which of course works and I use it myself - but it has always seemed a bit inelegant - to me.

It would be somewhat like the trigger height setting for Z probes, only for end stop sensors.

Frederick

@bearer
Thanks!
I am going to wait to play with this until after 3.2 comes out. Printer build is not finished yet, and want to stick to stable releases until I have it well tuned and reliable.

Thanks again for the head start!

@BoA said in Would be nice to set FAN target speed by RPM instead of PWM:

My concern was voltage on tacho pin and pwm pin.

they're generally active low to avoid voltage issues

@Generic-Default, I think that the solution to this is going to be macro files that can be passed parameters. So you would create a G83.g macro file that would have all the parameters to the G83 command available to it. Do you think this would be sufficient for you? You would need to use conditional GCode commands to check that the required parameters have been supplied and to supply default values if appropriate.

@Phaedrux Works! Thanks!

Because M41 is what thinkyhead plans to implement, and it would spare us from yet another split in G-Code commands.

@engikeneer

You are totally right 🙂

(But... just for fun I share why:
On the big printer I build a while ago as a inbetween-job the z-axis has a certain movement-speed it crosses when I want to do a really fast homing (400mm up or down with a 25-30kg almost 1x1meter heatplate on trapezoidals with only 2mm pitch on a 0.9° big stepper that for torquereasons is on a 1:2 pulley...)
Of course I can stay below that specific spot with the speed but then it feels like it takes forever... Otherwise the homing takes just super long if I do not want to cross that certain spot where it resonates really ugly... Now at this point you might think just accelerate faster to cross that point - nope tried it, above a certain acceleration speed it just looses steps so for ca. 2-3 seconds you have the feeling like in the old days in the classroom where someone scratched on the board with the fingernails or the chalk in a really bad way - bäh 😵
Yeah I know superspecial use case, might be the only one on earth I guess, a bit selfish I admit it - hope you understand 🙂 )

@droftarts said in Klipper features in RRF - Input shaping, -jerk, cal. scripts ?:

@pandaym For Input shaper, RRF version is https://duet3d.dozuki.com/Wiki/Gcode#Section_M593_Configure_Dynamic_Acceleration_Adjustment

klipper claims it works much better and have ability to remove more than one frequency

For Acceleration / square corner velocity / jerk you can change the jerk policy with P parameter in https://duet3d.dozuki.com/Wiki/Gcode#Section_M566_Set_allowable_instantaneous_speed_change. I'm not sure how it's 'gone' in Klipper (haven't really looked at it), unless they're using S curve motion planning. There's been a number of long threads about the arguments for and against S-curve; general view is there's little advantage in 3D printing, but probably good for slower CNC-type applications. (Cue flame war!)

they used something very similar to S curve with talk to moving to full S curve and the benefits are immediately visible on images of printed parts ppl shared (I have not tried myself)...

Calibration scripts - the addition of conditional gcode should make this much easier. Someone just needs to write them!

I think this is a good start, not sure what's missing here:
https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance

there is this
https://github.com/martinj/duet-telegram

@infamous_panda M4 is CNC specific, what sort of software is generating M4 for laser cutting?

@dc42

O.K. so now I get it! The code does something like this (?): You calc how much pwm is needed for 5°C less and see how long it takes for the sensor to arrive there, then adjust your pwm val by the diffrence between your pre-calced temp and the actual by the sensor? Then you know a basic dead-time. Then you iterate with the adjusted vals again until the deviation is below a certain envelop. Or something like this...?

O.K. so no need there. 🙂

(Ähm - yeah 15sec is because of the thick stainless-steel-sleeve, we need in some low-to-middle-pressure fluid circuits. I guess for them /usit was easier to have one sleeve for more then 1 customer/client (we are too small at the moment in terms of quantities) for all those use-cases e.g. but I am working currently with them to make a version for us, with thin walls for low-pressure-fluid-circuits made out of aluminum to have something faster. Smaller we made it already (now in stainless, samples arrived) and switch to a material with higher thermal conductivity will be the next thing I am currently working on with them 🙂 . Sounds complicated for others but of course for the company it makes most sense to use the same sensors also for the printers that we anyway have in the inventory for other stuff...)

Edit:

@dc42

In terms of speed, what would you suggest as ntc10k to measure our new one when it arrives against? Maybe you can e-mail me a name?

Edit: I consider this solved -> Can it please be locked?

@dc42, Is it now possible to test I²C read byte(s)?

@catshow said in BLTouch and Duet 3 - Probe is not deploying.:

So it would be nice if the console would show a warning/error if it can't find the the probe files.

That sounds like a reasonable request.

@poohzaza said in TMC2209 Sensorless Homing:

any update on duet Maestro with tmc 2209

see
https://forum.duet3d.com/topic/17409/duet-3-mini-5-initial-announcement

If in trigger2.g i write:
G4 S1
M582 T2

Starting a loop....