Do yourself a favor,use the tuning macros,top of this page
-
I should actually release the rest of my macros alongside these. Things like common diagnostic commands and example macros for things.
-
@RyanP said in Do yourself a favor,use the tuning macros,top of this page:
@Phaedrux has done us all a great service by posting and sharing tuning macros for us Duet users.
Yes I agree A big thanks to @Phaedrux for this,
But @RyanP you need to tweak it just a smidgen:
Phaedrux has done us all a great service by posting and sharing tuning macros for us NEW & Inexperienced Duet users.
Some of us have been using Duets since the first iteration, the 0.6 was released around December 2013
-
@CaLviNx I would say he even did the old-guard duet users a favor by formalizing institutionalized knowledge and providing it in an easy-to-share format. And even though I am not on the duet train since 2013 I would not call myself a new or inexperienced user, yet I find those macros super helpful.
-
@oliof said in Do yourself a favor,use the tuning macros,top of this page:
@CaLviNx I would say he even did the old-guard duet users a favor by formalizing institutionalized knowledge and providing it in an easy-to-share format. And even though I am not on the duet train since 2013 I would not call myself a new or inexperienced user, yet I find those macros super helpful.
That's good for you then.
-
Looks like a very thorough of macros and I will definitely try it. May worth linking it in the official commissioning pages.
-
@Phaedrux said in Do yourself a favor,use the tuning macros,top of this page:
Glad you found them useful.
In practice how many values need to be changed to tune one aspect?
I ask because I have been using dummy fans as a way to change values and was wondering what the smallest number of fans would be needed to be useful given that fans are "modal" in that I change the name of the fan, via a macro, and that determines what value is changed.
So a fixed number of fans could change a large number of values IF the values could be arranged in meaningful groups.
Thanks.
Frederick
-
@fcwilt said in Do yourself a favor,use the tuning macros,top of this page:
In practice how many values need to be changed to tune one aspect?
I'm not sure how to answer that. Can you be more specific?
-
@Phaedrux said in Do yourself a favor,use the tuning macros,top of this page:
I'm not sure how to answer that. Can you be more specific?
Well for example in the Acceleration folder you have six different folders full of macros to set values for X, Y, Z, E, Print & Travel acceleration.
Are they the only values that might need to be changed when tuning Acceleration?
If so then six different "dummy fans" could allow for changing those values.
On the other hand if there were many more values that might need to be changed if might exceed the number of fans that could be created and things could get cumbersome.
Of course if variables are implemented and there are suitable controls available in DWC it could become easier to change values then having dozens and dozens of macros.
Thanks.
Frederick
-
@fcwilt I don't know... I'd have to think about that. It's hard enough to try to devise a means of testing that holds a single variable in play, adding many at once in a programmatic fashion boggles the mind.
-
@Phaedrux said in Do yourself a favor,use the tuning macros,top of this page:
@fcwilt I don't know... I'd have to think about that. It's hard enough to try to devise a means of testing that holds a single variable in play, adding many at once in a programmatic fashion boggles the mind.
If we do get variables and good UI controls to set them imagine a single user defined page in the DWC with a control (be a pull-down combo control, a increment/decrement control, slider, etc) for each variable you might want to change.
The controls I envision would have a way of invoking the appropriate command with the selected value.
If not that than a single macro could apply all of the current values using the appropriate command for each currently selected value.
A quick glance at the page would allow seeing all currently selected values.
Time will tell.
Frederick
-
@Phaedrux said in Do yourself a favor,use the tuning macros,top of this page:
I should actually release the rest of my macros alongside these. Things like common diagnostic commands and example macros for things.
I've now released the rest of the macros I use on Github.
They can be found here. https://github.com/x0rtrunks/RRF-Example-Macros/tree/master/macros
-
Sorry if maybe my question is stupid, but I haven't found a clear answer for it: are these macros usable during a print?
For instance, I'm printing a cube, then during the print I manually go to the acceleration macro, select a value and then boom, the acceleration value will change for the rest of the print? Do I have to hit pause before doing that ?
I suppose (and hope) it works directly during print, but I'd like to be sure before giving it a try
-
@MrDui yes the new setting takes effect nearly instantly.
