@wilriker said in Need advice on new heated bed aluminium plate:

who needs PEI on the side where the heater is attached anyway?

Lots of people use these plates on top of the heated alu bed (with clamps). It is nice to have a plate that you can turn over to choose between a glossy or a matte finish.

That actually makes sense, and I think it might be the cause of some problems I am having when printing smaller layerheights. I do not have the luxury of so many microsteps (Duet 0.6) but I makes me think if it is not better to go the absolute extrusion way instead of relative. I have read, long time ago, that relative extrusion was the preferred method, but I lost the "Why?". Maybe someone can shed some light on this.

@Phaedrux Yes, but I think the difficulty is getting no air trapped in the glue-liner. It expands when heated and causes the issues like unevenness and will work areas loose eventually. I have a glass plate and a 6mm alu plate both with thick PEI glued on top. I am very happy with how it sticks, but absolutely NOT with how even it is. I am a trained signmaker so I know how to prevent airbubbles and I have none visually, but nevertheless it's uneven enough to spoil first layers.

@deckingman said in Baby Stepping.. can it, or can it not be permanent?:

I'm just trying to understand why people want something that has to be changed regularly to be made to persist or be permanent.

I do see the value of the suggested feature. Especially for values that change regularly. I find myself babystepping down a bit for each print of the roll I am currently using. Yes, I need to compensate for that in the H parameter of G31 command, but call me lazy! (does everyone has to lookup if it needs to be added or subtracted?). What's wrong with a button that sets the default height compensation in config.g based on the currently set babystepping? I would like it for sure!

@bot said in Baby Stepping.. can it, or can it not be permanent?:

I wonder how much of the precious memory on the duets are used for features that are catering to people whose printers are so poorly built that they need to calibrate it every single time they print. How much of the development time put into RRF was for such features?

Babystepping works as it does now. Config-override exists for you to save settings, but not babystepping. Figure out a way to save your babystepping values with that you have now!

It's so frustrating that some of us jump through hoops, spend tens of thousands of dollars or euros, build a machine that is rock solid, but yet we have to deal with the onslaught of features and feature requests from people who can't be bothered to edit one line in one file?

We should not cater primarily to the lazy folks who can't be bothered to perform extremely simple actions.

A little respect please... Not anyone uses their machinery the exact same way you do so yes, other people have to be catered too. The suggested option is a nice one, even if you do not understand that. RepRap is supposed to be the most userfriendly firmware, no?

@deckingman said in Baby Stepping.. can it, or can it not be permanent?:

Scenario 1. With baby stepping as is (non permanent), you start a print, then adjust baby stepping. Repeat for the next print.

Only if you are homing again you will have to readjust. Making it permanent you do NOT have to readjust.

Scenario 2. With "permanent" baby stepping, you start a print, then adjust baby stepping, then save it. But you still repeat that process for the next print because you say "I find myself babystepping down a bit for each print........"

I find myself babystepping down for each print, because I cannot make it permanent. You have it the wrong way.

So all you are doing in scenario 2 is saving the value that you are going to change anyway next time you do a print. Why?

No, I do NOT need to change anyway if my value gets permanent.
I think you need to look at it not as permanent babystepping, but as an easy way to dial in the H value in config.g. Nothing is easier then looking at a result, adjusting, looking again, and when it is spot on, press the button and it is set. After pressing the button, babystepping is at 0 and no need for adjustment until you change material, adjust flowrate or esteps, or do something else that requires evaluation of your nozzle offset.

@Phaedrux, thanks, exactly what I needed!

I am picking up on 3d printing after a long pause. I have some trouble getting my prints neat. For troubleshooting purposes, I am trying to think up a macro that moves my carriages up and down a few times one tower after another. I thought I once read about a command in RRF that allows that, but can't seem to find it. Am I mistaken or just not looking good enough?

An entirely different approach to think about it:
Is it a single wall print with something like a gyroid infill?

Are you SURE thhey are on the same network? I don't think so... You probably are using a router as accespoint / Switch, and it happens to DHCP in the same segment as your main router.

Seems obvious that 2 devices in unequal network segments cannot reach eachother.
Are you convinced they are connected to the same router / network? It is not normal that devices in the same network get IP addresses through dhcp that are not in the same segments.

@deckingman said in Baby Stepping.. can it, or can it not be permanent?:

Let's go the whole hog. Why stop with having a button to make baby stepping permanent instead of editing one value in config.g? Let's have another button that will set the steps per mm for extruders after we've calibrated them - one button for each extruder ideally. Then another button when we tune firmware retraction to save us editing config.g for that. The same for pressure advance and all the other things we have to tune.

Most things you mention are set and forget type of settings. Nozzle offset is not, it needs to be tuned from roll to roll, or evan after many other changes.

With enough buttons, we need never open config.g at all.

That's basically the idea of having a GUI, isn't it?

Look people, it is just not worth any more fuzz. It is certainly no dealbreaker for me. I did not invent the subject. I just think it is a plausible feature that got fired down with not enough valid arguments.

@bot said in Baby Stepping.. can it, or can it not be permanent?:

I wonder how much of the precious memory on the duets are used for features that are catering to people whose printers are so poorly built that they need to calibrate it every single time they print. How much of the development time put into RRF was for such features?

Babystepping works as it does now. Config-override exists for you to save settings, but not babystepping. Figure out a way to save your babystepping values with that you have now!

It's so frustrating that some of us jump through hoops, spend tens of thousands of dollars or euros, build a machine that is rock solid, but yet we have to deal with the onslaught of features and feature requests from people who can't be bothered to edit one line in one file?

We should not cater primarily to the lazy folks who can't be bothered to perform extremely simple actions.

A little respect please... Not anyone uses their machinery the exact same way you do so yes, other people have to be catered too. The suggested option is a nice one, even if you do not understand that. RepRap is supposed to be the most userfriendly firmware, no?

@deckingman said in Baby Stepping.. can it, or can it not be permanent?:

Scenario 1. With baby stepping as is (non permanent), you start a print, then adjust baby stepping. Repeat for the next print.

Only if you are homing again you will have to readjust. Making it permanent you do NOT have to readjust.

Scenario 2. With "permanent" baby stepping, you start a print, then adjust baby stepping, then save it. But you still repeat that process for the next print because you say "I find myself babystepping down a bit for each print........"

I find myself babystepping down for each print, because I cannot make it permanent. You have it the wrong way.

So all you are doing in scenario 2 is saving the value that you are going to change anyway next time you do a print. Why?

No, I do NOT need to change anyway if my value gets permanent.
I think you need to look at it not as permanent babystepping, but as an easy way to dial in the H value in config.g. Nothing is easier then looking at a result, adjusting, looking again, and when it is spot on, press the button and it is set. After pressing the button, babystepping is at 0 and no need for adjustment until you change material, adjust flowrate or esteps, or do something else that requires evaluation of your nozzle offset.

@deckingman said in Baby Stepping.. can it, or can it not be permanent?:

I'm just trying to understand why people want something that has to be changed regularly to be made to persist or be permanent.

I do see the value of the suggested feature. Especially for values that change regularly. I find myself babystepping down a bit for each print of the roll I am currently using. Yes, I need to compensate for that in the H parameter of G31 command, but call me lazy! (does everyone has to lookup if it needs to be added or subtracted?). What's wrong with a button that sets the default height compensation in config.g based on the currently set babystepping? I would like it for sure!

Tested the S1 parameter in M452 and that works. Thanks @bearer for showing me.

Extra questions for the experts:

What is a nice clean method for having a nice clean low-power dot for focussing purposes? Anyone have a ready to use macro for that?

And the second one is about the F parameter in M452. The specs of my lasermodule show a max PWM frequency of 20000Hz. Should I use that or is that some nonsense value? I see many people using different values here, but what values actualy make sense?