Topics created by yoshimitsuspeed

@dc42

Did you see the results of my first test above?
If I am learning to read the filament sensor output correctly it doesn't seem like NLE is really doing anything at all.

I have a lot more data from tests yesterday but I need to go through it and test some things. I was testing TPU and had more drag on my filament before the extruder than is ideal. That might be causing under extrusion but in a test today I don't think it was really skewing results of NLE notably.

If all my results are accurate and like the results above it seems like NLE isn't really having any impact at all.

On the subject of reading the filament sensor data. Am I correct in my assessment that something in that 24.8-25.3 range is nominal and that higher numbers equate to less linear filament passing through and lower numbers mean more filament passing through?

So for example if 25.3 is what I get on a low speed test and 25.8 on a high speed test that would equate to 98/100 mm of filament passing through correct?

Leaving this for future reference.
https://forum.duet3d.com/topic/14544/guide-to-marlin-s-fast-bltouch-probing-feature-on-duet

The volumetric flow rate shown by DWC is the commanded flow rate before pressure advance or nonlinear extrusion is applied. Pressure advance only changes the commanded flow rate during acceleration and deceleration. For the steady speed part of a long move the volumetric flow rate should be the same as the value implied by the GCode command and the nozzle diameter, provided that the actual speed matches the requested speed.

One way to check the calibration of nonlinear extrusion is to use the Duet3D Magnetic Filament Monitor (or the MFM add on to the Roto Tool board) to compare actual vs commanded extrusion during a sequence of long straight moves executed at various speeds and corresponding flow rates.

@T3P3Tony I never felt at ease when navigating through various coordinate systems.
Changing a mill bit and setting new z-zero meant pure adrenalin and full concentration for me.
I had to switch through machine/workspace coordinate systems back and forth and without the conditional macros it was all done manually.

Nowadays it's just a matter of writing a bulletproof macro, but I already wrecked my Y-axis because one motor got stuck while the other went on.
IDK if there is a cross check method for stall detection now? (one y-motor stalls and both stop automatically)
When I tried to set it up, I only got popup messages in DWC and had to react accordingly. Fingernail biting time....

@yoshimitsuspeed I do likewise with setting different values for each filament type by using the slicer custom gcode. I tend to use a separate line for each extruder even when a colon separator is permissable as it reduces the possibility of errors and ambiguity. I also find that using global variables and a macro is a great help.

I agree that the use of "E" and "D" can be confusing. But afaik, "E" is only used where a command has values for both axes and extruders whilst "D" is only used for commands that only apply to extruders, so that is a good way to remember.

@yoshimitsuspeed I think a bigger problem than feed forward heating, is feed forward cooling. What I mean by that is, assuming you have a large print area that you want to print fast (and for which your hot end has a limited melt rate capability thus requiring elevated temperatures) and you then change to smaller detail that you have to print slower and cooler, then you have to rapidly cool the hot end which realistically would require a fan blowing cold air over the heater block. Even so, thermal inertia will always limit how fast you can switch between high and low filament temperatures, whether heating or cooling and regardless of how powerful the heating element.

Oops mixed up left and right extruders in second to last post but trying to edit now is getting flagged as spam.