@dc42 If I use the macro:

M291 P"Probe will be tested 10 times and return mean and standard deviation. Ok or Cancel?" R"WARNING" S3 ; User must click OK or cancel.
G28
M401
G30 P0 X151 Y161 Z-9999
G30 P1 X151 Y161 Z-9999
G30 P2 X151 Y161 Z-9999
G30 P3 X151 Y161 Z-9999
G30 P4 X151 Y161 Z-9999
G30 P5 X151 Y161 Z-9999
G30 P6 X151 Y161 Z-9999
G30 P7 X151 Y161 Z-9999
G30 P8 X151 Y161 Z-9999
G30 P9 X151 Y161 Z-9999 S-1
M402

It probes on the center of the bed X=0, Y=0 (I am using a Delta). Shouldn't it probe on X=151, Y=161????

@mgjosh I have added these to the firmware wish list.

@reefwarrior nobody knows it. What i know is that this is on the wishlist https://forum.duet3d.com/topic/12681/total-hours-of-operation-printing-feature?_=1622489457343

@dc42

Fair enough. Input shaping is probably the best first pass at all these resonance issues. I'm just worried my Maestro will miss the party.

Any ETA shaping up for the first beta?

@siam said in "Terms of use" implementation?:

my opinion is is it better to read this message from time to time

The thing is, the message doesn't show up when we start DWC. It appears coincidently, depending on the users behaviour. Hence their surprise/shock.
I better like to see a (surely short) terms of use message, everytime I update firmware.

@owend TBH, I was thinking more of the state used when Loading / Unloading / Changing filament from the UI when clicking the filament name next to the tool number.. I just found the filament type in the Object Model - I'm not sure how I missed that before! But I don't know where DWC is getting the state of the filament from..

@kj3d said in PID Tuning Bed Problems:

Heated bed size is 1100 x 1050 with 1800watts

It's probably taking a very very long time to drop temp?

@kj3d said in PID Tuning Bed Problems:

Warning: heater behaviour was not consistent during tuning

It means that the heating and cooling rates didn't settle down to consistent values after several cycles. One possible reason is noise on the temperature sensor readings, which would be apparent in the temperature graph. What did the graph look like during tuning? What does it look like in normal use?

You can take the values it provided and manually tune them if you're not getting good results with them.

https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control#Section_Setting_the_model_parameters_manually

@argo Thank you for the thoughtful response! I'm sorry for my lack of knowledge, I'm not a programmer so I am relatively clueless with this, but where exactly would I insert this code, does it go into the firmware?

I'm also confused about what is happening with the code itself, if you would like to maybe explain it/ comment the lines I would appreciate it but don't feel obligated to do so.

I would be willing to test it out once I get my printer back up and running but that may not be for a couple weeks.

Thanks again!

@dc42 perfect.
Thanks for the explanation!

@kenny_mc_cormick said in Command to turn heaters active/standby/off?:

@dc42 awsome !! can't wait to have it ! 🙂
you guys doing such a good job !

edit:
@Phaedrux i check that. I guess it's "M568 P2 A1 ; set tool 2 heaters to their standby temperatures" to use, but does it set the tool on standby or does it just turn the heating on ?

It turns the heaters on too.

@phaedrux The two issues with G10 are that you can't make changes on the fly that result in a nudge to the print head, and that it feels like a bit of a black art as to whether you need to plus or subtract to the existing values in order to effect the change you need.

I'll look into M500 P10 to see if there's anything more there to play with.

Ultimately, the existence of conditional code and variables allowed me to concoct a solution that works for now, but it's impossible to be certain the implementations won't change, leading to required adjustments in all that thinking.

I'm grateful that you led me towards a viable solution.

@phaedrux said in RRF3.2 request to enable G43 & G44 Tool height offset:

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

I have seen that, we are a bunch of mechanical oriented guys in our group, so programming is taking us quite a while, so much different then C that I used to use.

@dc42 said in Input Shapers: 2HUMP_EI & 3HUMP_EI + Auto Tuning:

@ccs86 that entry in that table is incorrect.

Edit: I have corrected it.

@dc42 That makes a lot more sense. Would you mind shooting me a PM?

@o_lampe but for crash detection you don't need to detect the deacceleration caused by the crash. Only the change of direction of earth's gravitational pull matters. And this you could poll every few seconds. Although I agree, I'd rather see a co-processor on the smart effector that enables some additional smart features

@dmandn said in Feature - M703 /flag possible request?:

Hi all, apologies if there is a way to do this already, what I'd like is to make a call like M703 to call settings per filament. However, I want to pull speed, retraction settings and bed temps for homing, etc without the nozzle temp being applied.
I'd like to have a M703 call that sets and applies pretty much everything except the nozzle temperature. I can then call M703 after homing, levelling, etc finished to set and heat nozzle to temp before priming and printing,

My first question is why do you want to do that?

Frederick

@dc42 Any advancement on this function?
Is there a current "todo" list?

@phaedrux said in reduce printarea while printing ?:

There is a DWC plugin that displays the currently loaded gcode file as a 3D object. You can choose can cancel from there.

Check your DWC plugins (3.2.2 and beyond)

the 3d viewer ?
hmm, after every start of the board i have to start this plugin manually, with my other duet3 it start from it self.

@generisi said in Independent input shapers per axis:

@dc42 Would the "offline" calculation solution work on both axes on Duet2 boards, or are the RAM limitations still an issue?

If we can use a single shaper to handle two frequencies, that is likely to be usable on Duet 2.

@dc42 thank you for fast response. I am looking for 13th and 14th (or even 15th and 16th) stepper driver so not existing expandability options within duet2+duex5. So not exactly what i asked but I'll settle for this kind answer.

Duet 3 mini with expansion would give 7 stepper drivers each, so 14 needed, but i do have to read up if this would also have 8 channels of PWMs for fans, five heaters + at least 1 PWM for bltouch/probe and stuff that is needed to drive one proper IQEX...
I'll have to read up but ain't thrilled on going anything mini. It's just the ordinary "go duet3" way then OR doing an addon PCB for multiplexing.. Ourighty then.

@nuramori
@dc42 said, I could change the whole kinematic model 'on the fly', so it's worth a try..
Some parameters can't be changed mid-print, it would be nice to have a table about those do's and don'ts