Topics created by mildw4ve

I used to use a NEMA-23 driven ball screw on the Y axis of a printer. It had a horrible mechanical resonance that I was never able to get rid of. The axis could run just fine at any speed up to about 150 mm/sec, except at 50 mm/sec it would make awful noise and would skip steps. I limited maximum print speed to 40 mm/sec and it worked great. Eventually I converted it back to belt drive and there were no more resonance issues.

@dc42 said in How to limit extruder feedrate without limiting retraction speed:

Bear in mind that setting a low limit on positive E moves and a higher one on negative E moves (which I think is what @mildw4ve is asking for) would also make filament loading very slow. Reprime moves are also positive extruding moves, and for those I don't think you would want to apply the low speed limit. So if this were to be implemented, it would have to apply only to moves with positive extrusion and X or Y movement.

Which is a very good reason to separate "single" vs "multi" axis moves (and not Pos/Neg).

You have wrong X parameter
If you use PT1000 you should use 500 + ADC channel (more: https://duet3d.dozuki.com/Wiki/Gcode#Section_M305_Set_temperature_sensor_parameters)
In you case:

M305 P102 X503 S"Chamber"

@donstauffer said in Simplify3D dual extruder starting script tuning:

@fcwilt That does make sense. I'm exploring how to organize things now. Thanks for the input.

When you create a Filament in the DWC three filament specific files are created: load.g, unload.g and config.g

Here is the contents of one of those filament specific config.g files:

M291 R"PLA - Generic - Red" P"Configuring..." T0 M221 S100 D0 ; set extrusion multiplier G10 S190 R0 ; set extruder temps M140 S60 R0 ; set bed temps set global.g_print_beg_prime = 10 ; set global.g_print_beg_retract = 0.5 ; set global.g_print_end_retract = 0.5 ; M291 R"PLA - Generic - Red" P"Configuring - Done" T1

I have all of the code that is executed at the start of a print in a file called print_begin.g.

The essential part is this:

T0 M703

The M703 executes the config.g file of the filament loaded into tool zero. The tool has to be selected for M703 to work.

The other code in print_begin.g does things like check for valid temp settings, wait for temp set points to be reached, priming the extruder and anything else that needs to be done or you want to be done at the start of a print.

Frederick

I recommend making X0 Y0 the centre of the bed, and using equal but opposite tool offsets for the two nozzles (so that the head Reference Point is midway between them).

I would guess the reason there is no such thing is that there is no standardized peripheral that needs to be controlled by a telnet client, and if used on WiFi it would be subject to uncertainty. I would elaborate a little on the use case and see if you get any alternative solutions, maintaining a custom firmware mod across upgrades could be tedious.

@mildw4ve said in Extruder stepper motor tuning:

The model in the photo has XY dimensions of 40x40mm, horizontal distance between ribs is around 8mm and with 11mm diameter filament gear, 0.2mm layer height, 0.4mm nozzle, I don't believe there is a correlation there. My math might be wrong though.

Can you post a section of the GCode file showing at least one complete layer (not one of the the first few layers) so that we can see how much extrusion is being done per side of the cube?

Looks like you will need to power it from 5V, which you can get from the expansion connector or from the PanelDue connector. You can feed the output directly into an endstop input of your rev. 1.04 Duet.

Replaced both of the chips, it took some skillful work with a soldering iron but it worked.
Just a small followup in case anybody encounters the same issue with their DUEX 🙂

That was it, I forgot I changed my z probe setting file name, one that is referenced in config.g using M98 command and after the change it didn't load. Thank You.