New beta firmware 2.02beta1

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!

dc42

Have you read https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M703_Configure_filament to see how M703 is intended to be used?

gtj0

@burtoogle said in New beta firmware 2.02beta1:

@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.

XY Speed: 80 mm/s
XY Accel: 1000 mm/s^2
XY Jerk: 800 mm/min

E Accel: 125 mm/^s
E Jerk: 120 mm/min

No pressure advance

I haven't even attempted to do any advanced tuning let alone tried to tune out the ringing yet but the corners are pretty sharp.

burtoogle

@gtj0 said in New beta firmware 2.02beta1:

XY Speed: 80 mm/s
XY Accel: 1000 mm/s^2
XY Jerk: 800 mm/min
E Accel: 125 mm/^s
E Jerk: 120 mm/min

Thanks for the numbers. Interesting, very different from what I am using. For the extruder, I am using higher acceleration and much smaller jerk (currently 1000 and 10 , respectively) and get good results. Until recently I have been using 400 for the accel and have upped it to 1000 now as it still behaves OK. 3000 was too much as it wasn't retracting at all using that. I shall try increasing the jerk now.

burtoogle

I upped the extruder jerk to 100 and it's printing fine along with extruder acceleration of 1000.

Back to testing M593. The results I am seeing are still very much like the picture I posted earlier in the thread in that some ringing that was occurring after a relatively shallow hole was pretty much getting removed but ringing that occurred downstream of a longer edge wasn't being reduced (or maybe just a little, hard to tell).

Another oddity is that when I print that little 20mm widget that has X and Y and dots on the other sides. I get more ringing downstream of the X / Y / dots in the upper half of the print than the lower half and the upper half of the model has rounded corners and the lower half has sharp corners! When not using M593, the amount of ringing downstream of the X / Y / dots is similar for both the top and the bottom of the print. Don't understand that at all.

GizmotronX5000

Were there any changes in the compiling process? I brought these files into Eclipse, but when I go to compile I get about 30 errors coming from "WiFiInterface.h". Most are of the form "symbol/type xxxxx cannot be resolved." I also get this error: make: *** [Duet2CombinedFirmware.elf] Error 1.

I have make.exe and MessageFormats.h in a folder included in the path, and I can confirm that they are listed in the includes folder of the project. Is that still the correct process?