Config.g

; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 10 2021 22:07:00 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Red Queen" ; set printer name M665 L298.700:298.700:298.700 R149.058 H355.596 B130.0 X0.428 Y0.399 Z0.000 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0.453 Y0.269 Z-0.722 A0.00 B0.00 ; put your endstop adjustments here, or let auto calibration find them ; Network M551 P"*************" M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S0 ; physical drive 3 goes backwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X200.00 Y200.00 Z200.00 E620.00 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E3600.00 ; set maximum speeds (mm/min) M201 X4000.00 Y4000.00 Z4000.00 E600.00 ; set accelerations (mm/s^2) M906 X2000 Y2000 Z2000 E500 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S1200 ; Set idle timeout M571 x1 y1 ; set axis correction factor ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S3 ; configure sensorless endstop for high end on X M574 Y2 S3 ; configure sensorless endstop for high end on Y M574 Z2 S3 ; configure sensorless endstop for high end on Z M574 E2 S1 P"e0stop" ; configure active-high endstop for high end on E via pin estop ; Z-Probe M558 P5 R0.4 C"zprobe.in+zprobe.mod" H5 F800 T10000 ; set Z probe type to effector and the dive height + speeds G31 P500 X0 Y0 Z-0.255 ; set Z probe trigger value, offset and trigger height M557 R130 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 R0.350 C261.300:261.300 D1.57 S1.00 V23.9 B0 ; bed tuning data M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M307 H1 R4.061 C128.0 D9.76 S1.00 V24.1 ; hot end tuning data M307 H1 R4.061 C128.0 D9.56 S1.00 V24.1 M143 H1 S320 ; set temperature limit for heater 1 to 320C ; Fans M950 F0 C"fan0" Q60 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 L0.25 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q60 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q60 ; create fan 2 on pin fan2 and set its frequency M106 P2 S255 H-1 L0.25 ; set fan 2 value. Thermostatic control is turned off ; Tools M563 P0 S"Squirt squirt" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M572 D0 S0.02 ; set K-factor M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M591 D0 P7 C"e0stop" L7 R50:200 E15 S1 ; configure BTT smart filament sensor M911 S23.5 R24 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool

bed.g

; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 10 2021 22:06:59 GMT-0400 (Eastern Daylight Time) M561 ; clear any bed transform ; Probe the bed at 12 peripheral and 3 halfway points, and perform 6-factor auto compensation ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g. G30 P0 X0 Y124.9 H0 Z-99999 G30 P1 X62.45 Y108.17 H0 Z-99999 G30 P2 X108.17 Y62.45 H0 Z-99999 G30 P3 X124.9 Y0 H0 Z-99999 G30 P4 X108.17 Y-62.45 H0 Z-99999 G30 P5 X62.45 Y-108.17 H0 Z-99999 G30 P6 X0 Y-124.9 H0 Z-99999 G30 P7 X-62.45 Y-108.17 H0 Z-99999 G30 P8 X-108.17 Y-62.45 H0 Z-99999 G30 P9 X-124.9 Y0 H0 Z-99999 G30 P10 X-108.17 Y62.45 H0 Z-99999 G30 P11 X-62.45 Y108.17 H0 Z-99999 G30 P12 X0 Y62.4 H0 Z-99999 G30 P13 X54.04 Y-31.2 H0 Z-99999 G30 P14 X-54.04 Y-31.2 H0 Z-99999 G30 P15 X0 Y0 H0 Z-99999 S6 ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

homedelta.g

In my home routine I have an initial bump, then a move away from the hard end-stop and another slower bump with appropriate currents and sensitivity for both to function flawlessly outside of the call from "M915 X Y Z S3 F0 R3" after a stall.

The trouble seems to come on the second bump where, as far as I can tell, Y tower is skipping or something strange is happening.
EDIT: after closer observation the stall on first bump does not work and indeed the homing routine is not carried out properly past the first bump regardless of my settings for current or sensitivity while called by R3 of M915.

; homedelta.g ; called to home all towers on a delta printer ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 10 2021 22:07:00 GMT-0400 (Eastern Daylight Time) G91 ; use relative positioning ;M400 ; make sure everything has stopped before we make changes M915 X Y Z S3 F0 R0 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered, R 0 = no action (default), 1 = just log it, 2 = pause print, 3 = pause print, execute /sys/rehome.g, and resume print M201 X800 Y800 Z800 ; set max acceleration M913 X32 Y32 Z32 ; reduce motor current to 32% to prevent belts slipping G1 H1 X12000 Y12000 Z12000 F4500 ; move all carriages up 12000mm, stopping at the endstops M400 ; make sure everything has stopped before we make changes M913 X100 Y100 Z100 ; motor currents back to normal M201 X4000 Y4000 Z4000 ; set max acceleration G1 H2 X-20 Y-20 Z-20 F15000 ; down a few mm so that we can home again slowly M201 X800 Y800 Z800 ; set max acceleration M915 X Y Z S2 F0 R0 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered, R-do nothing M913 X29 Y29 Z29 ; reduce motor current to 25% to prevent belts slipping G1 H1 X12000 Y12000 Z12000 F2600 ; move all carriages up 12000mm, stopping at the endstops M913 X100 Y100 Z100 ; motor currents back to normal G90 ; back to absolute positioning M400 ; make sure everything has stopped M915 X Y Z S3 F0 R3 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered

rehome.g
SAME AS HOMEDELTA.G although it functioned poorly as simply G28 as well
Again, only strange on a call from the stall detection home on skipped steps of M915 with R3

G91 ; use relative positioning M400 ; make sure everything has stopped before we make changes M915 X Y Z S3 F0 R0 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered, R 0 = no action (default), 1 = just log it, 2 = pause print, 3 = pause print, execute /sys/rehome.g, and resume print M201 X800 Y800 Z800 ; set max acceleration M913 X32 Y32 Z32 ; reduce motor current to 32% to prevent belts slipping G1 H1 X12000 Y12000 Z12000 F4500 ; move all carriages up 12000mm, stopping at the endstops M400 ; make sure everything has stopped before we make changes M913 X100 Y100 Z100 ; motor currents back to normal M201 X4000 Y4000 Z4000 ; set max acceleration G1 H2 X-20 Y-20 Z-20 F15000 ; down a few mm so that we can home again slowly M201 X800 Y800 Z800 ; set max acceleration M915 X Y Z S2 F0 R0 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered, R-do nothing M913 X29 Y29 Z29 ; reduce motor current to 25% to prevent belts slipping G1 H1 X12000 Y12000 Z12000 F2600 ; move all carriages up 12000mm, stopping at the endstops M913 X100 Y100 Z100 ; motor currents back to normal G90 ; back to absolute positioning M400 ; make sure everything has stopped M915 X Y Z S3 F0 R3 ;set stall detect drives, S-threshold (-64 to 63), F1 filtered

pause.g

; pause.g ; called when a print from SD card is paused ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 10 2021 22:07:00 GMT-0400 (Eastern Daylight Time) M83 ; relative extruder moves G1 E-20 F3600 ; retract 10mm of filament G91 ; relative positioning G1 Z150 F3600 ; lift Z by 5mm G90 ; absolute positioning G1 X0 Y0 F3600 ; go to X=0 Y=0

Thanks for reading all the way down here....hope you have an idea on this one....what am I missing?

@ahwitmer said in Stepper definition Z motors:

It was somehow surprising to see that the temperatures measured by the NTC's were significantly different, although I used the same parameters as before. But that is a next step.

Please see https://duet3d.dozuki.com/Wiki/Calibrating_thermistor_and_PT1000_readings.

@owend Thank you...i open the gcode dictionary nearly everyday and i'm still missing some 😃 However as suggested in the dictionary i've put in tpost0.g (i'm on a single extruder) so i'm sure that it is always called and, if no filament is loaded, i can stop the print with a conditional gcode.

@phaedrux your the best thank you

@dc42 Thanks!
just to verify before I order.
Keeping like type motors, to like type drivers is best.

for Z1,Z2,x,y =Duet3 mini5+,
for E0-e1-e2-e3 = 1xDUET 3 TOOL DISTRIBUTION BOARD and 4x DUET 3 TOOLBOARD 1LC

correct?
thanks!
`mike

@resam Whatever it was, you can also avoid high load when using pydsfapi 3.2.0 or later by making use of the filters parameter when instantiating Intercept_connection. It takes a list of strings specifying those codes you are interested in. DSF will then only forward these codes to your client.

I have modified your new code example to show how to use it.

@st3phen I think the Dire warning is because people will try to disable the heater protections when it doesn't work at first which is where the fire risk comes from.

If you can derive sane values for the thermistor based on what you know about it, you should be ok.

Ok, I understand the behavior now. This is the very start of a log file. So, if I understand correctly, the DWC login occurred at 00:00:19 after power up, the clock was set and time stamps used after that.

power up + 00:00:15 [info] Event logging started at level warn power up + 00:00:15 [info] Running: Duet Ethernet 1.02 or later: 3.2 (2021-01-05) power up + 00:00:17 [warn] Network running, IP address = X.X.X.X power up + 00:00:19 [warn] HTTP client Z.Z.Z.Z login succeeded 2021-02-26 18:43:10 [warn] Date and time set at power up + 00:00:19 2021-02-26 18:43:11 [warn] HTTP client Z.Z.Z.Z login succeeded

@del87 said in Duet 3 mini 5+ sensorless homing not working:

Btw at V parameter = 10 there was some strange errors "driver short to ground".

This is not unusual. From section 6.5 of the TMC2209 datasheet at https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_Datasheet_V103.pdf:

For applications requiring high velocity motion, SpreadCycle may bring more stable operation in the upper velocity range.
...
A motor stall or a sudden change in the motor velocity may lead to the driver detecting a short circuit or to a state of automatic current regulation, from which it cannot recover. Clear the error flags and restart the motor from zero velocity to recover from this situation.

Hi @CSLTM
I fell in the same trap lately > M584 should come very early in config.g
I'd put it before M669 to be sure.
The configuration tool will be adapted soon.

@zapta The supply I used had overvoltage protection. good for 28.8-33.6 V. Apparently the voltage spike exceeded 33.6...

@resam I don't maintain the Python API client so I cannot really comment on the internals. Model subscribers in patch mode get either the full object model or the requested filtered model props after connecting so it should be safe to assume that props in the dict are already present. List items may change, though.

There is some more documentation about the IPC API in the README where some JSON objects are described, see here. In general DCS should not shut down because of an API error or invalid command. It's right that it should output an error and terminate the client connection when invalid data is supposed to be processed, but DCS should continue operating after that.

When a code is intercepted, a client must send back a definite action to DCS to avoid locking up the G-code stream. If a client disconnects while DCS is still waiting for an interception result, DCS should resume the code execution. I already wrote a few plugins (although obviously in C# and not Python) and I can confirm the API works well in general. But if you do find errors, feel free to submit bug reports on GitHub and I'll comment on them there.

No problem. Glad we got you sorted.

https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors#Section_Axis_levelling_using_endstops

Yes it is. Easier with RRF3. Use E0stop or E1stop as the second z endstop pin.

Instead of powering off, have you tried either using M999 to reset the Duet, or sending M98 P"config.g" to set it up again?

You can use the object model browser to check whether relative motion is selected for the File input channel:

1b18358a-0a4b-46b3-8737-d6a5b498b297-image.png

Messy, very messy on 3.3beta2. When using M600 the delay before refilling the syringe is longer (as expected from comments in the gcode wiki) and the resume.g gets interleaved into the main gcode stream after the resume happens, along with odd error messages about bad commands which indicate it has broken the reading of the gcode too.

The only way to get the above system to function well is with the contents of pause.g and resume.g commented out, and things are quicker with M25. I'd guess the length of the increase would likely be very build gcode dependent putting more emphasis on the parsing of gcode.

I think the bug report on needing to ensure trigger files (and any additional macros that they may call) are run in their entirety before running back to the build gcode needs to be investigated:

https://forum.duet3d.com/topic/22338/bug-ways-to-ensure-gcode-within-trigger-is-uninturupted

Glad you figured it out. The homing files look ok.

@dc42 Thanks for the information. That'd work for me.

I would suggest re-tuning again, but this time using a lower PWM factor to reduce the overshoot. 50w on a hotend is a lot of power in a small area. By the time the temperature rise has registered with the sensor the temperature has already shot past. Try P0.7 maybe.

The bin files could be deleted but they are handy to have in place in case you need to reflash in an emergency. The IAP files are required to perform a flash.