Topics created by Simon 4

@Simon-4 To permanently set spreadcycle, change the M569 command for that motor to include the D parameter, set to 2. eg:

M569 P0.4 S1 D2

spreadCycle is actually the default, so probably you have D3 with a V parameter. If you set the V parameter very high, eg V25000, you can set the changeover to a very low speed. This means that the motor will at least be quiet at standstill. Send M569 P#, where # is the stepper driver number, to see the current setting and the speed the changeover happens, e.g.:

M569 P121.0 S0 D3 V2000 M569 P121.0 Driver 121.0 runs in reverse, active low enable, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 2000 (0.9 mm/sec), pwmScaleSum 16, pwmScaleAuto 0, pwmOfsAuto 36, pwmGradAuto 14, pos 8 M569 P121.0 V25000 M569 P121.0 Driver 121.0 runs in reverse, active low enable, mode stealthChop, ccr 0x00053, toff 3, tblank 0, tpwmthrs 25000 (0.1 mm/sec), pwmScaleSum 16, pwmScaleAuto 0, pwmOfsAuto 36, pwmGradAuto 14, pos 8 M569 P121.0 D2 M569 P121.0 Driver 121.0 runs in reverse, active low enable, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 8

See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m569-set-motor-driver-direction-enable-polarity-mode-and-step-pulse-timing

Ian

@Simon-4 As you are not using firmware retraction, then the retraction parameters will be whatever you set them to in the slicer. The firmware doesn't "know" anything about the speed and distance values on the data sheet, unless you configure them using M207.
For info, the published retraction distance of 1.25 mm will vary depending on things like nozzle diameter, filament type, temperature and few other factors.

Edit. I should probably add that the maximum speed, acceleration and jerk values that you define elsewhere in config.g (using M203, M201 and M566) will be respected regardless of whether you use slicer retraction or firmware retraction. However, these are maximum allowable values which largely depend on what the motor/machine/mechanics are capable of and therefore should only be used to cap the maximum allowable values, and not be used as a means of controlling retraction settings.

@Simon-4 If the fan you want to monitor is fan 1, and your tool is using heater 1 the basics would be something like this:

; pause if fan is slow if state.status = "processing" & heat.heaters[1].current > 50 & fans[1].rpm <= 1000 M118 S"fan problem" M25

Loops are indicated by the indentation, so make sure you copy the indentation - you need the equal spaces at the start of the lines after the 'if'.

This checks to see if the printer is currently printing, and heater 1 is currently at more than 50 and fan 1 is at less than 1000 rpm, if all that is true, it displays a message and does M25 to pause the print. You will need to remedy the problem before resuming the print manually.

You should create a file in sys folder, it doesn't matter what it is called, put that text in it and save it. Then rename the file to 'daemon.g'. The file will run every ten seconds, and check the fan speed.

If you want to edit the file rename it to something else (I normally just make it daemon.g.x), edit the file and then rename it back. If you just edit it when the machine is trying to run it every 10 seconds things can go wrong.

@Simon-4

I thought because of statistics which the sensor sends back with M591 D0 there has to be an internal memory.

In fact, there is - well, kind of. Apart from the RAM which the DUETs use to maintain, calculate and organise data during operation, some specific settings can be written to the SD card for permanent storage. These then can be recalled when the system starts up again. See the GCodes M500: Store parameters and M501: Read stored parameters for details.

The problem with this mechanism is that the settings are typically defined in config.g - which is a good way to understand how your printer is set-up - but are then altered by the contents of a second file (config-override.g) which may introduce some level of confusion. So, many of the Duet users prefer to edit the config.g instead of relying on this mechanism, just to keep all settings in a single place.

@deckingman 4 wire fans have an always on power connection and rely on a PWM signal on a separate cable for the control

@Simon-4 said in Duet mini5+ forgets config after power off >30secs:

seems to work with the formated and the "hand crafted" sd file

SD card media can be fickle. Let us know if you encounter any other issues.

@Simon-4 please can you email warranty@duet3d.com with a link to this thread.