New beta firmware 2.02beta1

wilriker

@phaedrux said in New beta firmware 2.02beta1:

For acceleration you can do a test print and start with a low value and increase it every 20 layers or so. a 100mm cube is a pretty decent model to test with. You can use the formula from the Periodicity of Ringing thread to try and measure your results and find a more suitable acceleration value.

I was always wondering what is the upper limit I am looking for with accel? Or put another way: how do I recognize the upper limit of what is possible with my machine? I still have the values set that I took from Marlin config and never really touched this topic yet.

dc42

@phaedrux said in New beta firmware 2.02beta1:

You can use the formula from the Periodicity of Ringing thread to try and measure your results and find a more suitable acceleration value.

Dynamic Acceleration Adjustment does that for you. So all you need to do is find out how high you can set the acceleration without any risk of missing steps.

brunofporto

@dc42 said in New beta firmware 2.02beta1:

@phaedrux said in New beta firmware 2.02beta1:

You can use the formula from the Periodicity of Ringing thread to try and measure your results and find a more suitable acceleration value.

Dynamic Acceleration Adjustment does that for you. So all you need to do is find out how high you can set the acceleration without any risk of missing steps.

That is what I loved about this update I'll test it ASAP.

@dc42 Is it possible to use stall detection and some macro sequence to "auto-tune" max acceleration and/or jerk? Not now, but as a future improvement

For now, I'll use @Phaedrux tuning macro collection to tune them. But would be nice if the firmware was able to automatically tune those settings like we already do with PIDs from heaters.

dc42

@brunofporto said in New beta firmware 2.02beta1:

@dc42 Is it possible to use stall detection and some macro sequence to "auto-tune" max acceleration and/or jerk? Not now, but as a future improvement

The problem is that so-called "stall detection" doesn't actually detect motors stalls, what it detects is abnormally high loads that may indicate an approaching stall.

garlicbread

Just like to say thanks to dc42 (I think Dave) and the other firmware developers for all they're hard work.

I've recently managed to get my Anycubic Kossel Delta to work with the new duet board. It took a little while to figure out but I've got a lot more confidence in the bed leveling now than the original Marlin board.

I plan on writing up some docs on my blog at some point with a more step by step guides to try and simplify the setup process, and list some of the things / quirks I've noticed.

zerspaner_gerd

What does the new M703 command do?
Wiki is not completely understandable to me!

wilriker

@zerspaner_gerd The filaments have a new entry in the context menu. Besides load and unload macros you can now also define a filament specific config. M703 will check if such a config had been setup by the user for the currently loaded filament and execute it. It will do nothing (especially no error) of no config exists.

EDIT: Use-case: If you have e.g. different retraction settings for your different filaments (and use firmware retract) you could add these settings in the config and load it as part of your start GCODE via M703. (That's how I actually use it)

brunofporto

Ok,

I tested the DAA function... First time I thought I had great results, until turn it off and print the same gcode and had the same result....

Then I tested my maximum acceleration until I had to miss steps (2500mm/s²) to be sure and printed some single perimeter hollow cubes at three different speeds with the DAA turned off to check if my frequencies where close to the DAA setting.

Well... They are always around 40Hz and the DAA was set to this frequency.

I could see no improvement (the ripples are already very subtle before it anyway)

Am I doing something wrong or the test subjects had features that does not benefit from the algorithm? Is there a test model to use as a common reference?

I used a 20mm simple cube and this (printed hollow, single perimeter, etc) : https://www.thingiverse.com/thing:277394

Thanks!

Phaedrux

@brunofporto can you post a photo of the ringing? Perhaps it's not actually ringing at all.

burtoogle

Some more F593 testing...

I printed https://www.thingiverse.com/thing:277394 without (left) and with M593 F40 (right) on my Kossel XL with flex3drive extruder.

On this example, the ringing is maybe a little reduced but not everywhere and also the piece on the right has some noticeable roughness which can be seen as a shiny area downstream of sharp corners.

So M593 actually makes this print worse for me.

zerspaner_gerd

@wilriker Nice, I did not see that. I can do something with that. Thank you

dc42

@burtoogle said in New beta firmware 2.02beta1:

...On this example, the ringing is maybe a little reduced but not everywhere and also the piece on the right has some noticeable roughness which can be seen as a shiny area downstream of sharp corners.

So M593 actually makes this print worse for me.

Reduced acceleration will cause the head to spend more time near corners. On a Bowden extruder, that will make it more important to use the correct pressure advance setting.

burtoogle

@dc42 said in New beta firmware 2.02beta1:

On a Bowden extruder, that will make it more important to use the correct pressure advance setting.

It's not a Bowden extruder, it's a flex3drive.

dc42

A Flex3drive might require pressure advance to compensate for the torsional elasticity of the Bowden cable. I've never used one, so I don't know whether this is the case or not.

gtj0

@dc42 said in New beta firmware 2.02beta1:

A Flex3drive might require pressure advance to compensate for the torsional elasticity of the Bowden cable. I've never used one, so I don't know whether this is the case or not.

I don't use pressure advance on my flex3drive and the corners are way sharper than any bowden I've used. I think the high gear ratio takes care of that.

brunofporto

@phaedrux Here!
Left DAA (40Hz) Right No DAA

burtoogle

@gtj0 said in New beta firmware 2.02beta1:

@dc42 said in New beta firmware 2.02beta1:

A Flex3drive might require pressure advance to compensate for the torsional elasticity of the Bowden cable. I've never used one, so I don't know whether this is the case or not.

I don't use pressure advance on my flex3drive and the corners are way sharper than any bowden I've used. I think the high gear ratio takes care of that.

Apologies for the off-topic question but what speed, accel, jerk are you using with the flex3drive? I am using 25, 400 and 10 with no pressure advance and normally get good results.

zerspaner_gerd

Too bad that M703 does not already work with filament loading.

Thus, no change to the filament load macro would be necessary!

dc42

@zerspaner_gerd said in New beta firmware 2.02beta1:

Too bad that M703 does not already work with filament loading.

Doesn't it, in firmware 2.02beta1?

zerspaner_gerd

@dc42 said in New beta firmware 2.02beta1:

@zerspaner_gerd said in New beta firmware 2.02beta1:

Too bad that M703 does not already work with filament loading.

Doesn't it, in firmware 2.02beta1?

When filament loading it does not work (no temperature is set, no error messages)
My guess is that the filament name is updated only after the load, so M703 has no macro name.

When unloading it works!