Posts made by Demi

@dc42
Ohhhh, yep that makes all the sense in the world. Many thanks for the help. I just got off the phone with a company we work with that is producing printers, and they are looking to build their next line around the Duet 3. I passed how impressed with are with it, and how amazing the customer support is. Thanks so much for all the help, you guys rock.

@dc42
I was hoping to circle back with you on this, primarily on the inclusion of M915 in the rehome.g file. I dont have a M915 command in my rehome.g only a G28 XY. What is required in rehome?

@bearer thanks! Found it.

Im not sure the best way to show it other than an image. It certainly seems to work fine without sensorless homing for me, but I actually found the guide after I started playing with it, and was afraid I was doing something wrong.

Hi all, is there a way to send gcode to multiple printers at once, or to send gcode to a specific IP via DWC? I have 4 printers (soon to be 6) running Duet3 boards. At the beginning of the day it would be great to be able to have them all home, preheat, and create a height map. Is this possible?

BLUF/TLDR: What all needs to be in rehome.g and can stall detection can be used without sensorless homing. Seems to be working, but I want to make sure Im doing things correctly.

Hi all, I was hoping to get a little clarification on stall detection and some of the information in the guide. Im using a Duet 3 on a core XY printer, and I have read through all the documentation, and know its a bit more difficult to configure reliably on XY.

I added to the last line of my config:

M915 X Y S2 R3		

I wrote a test gcode file that just moved the head around, and I stopped it with my hand and it seems to work great (so maybe I should just leave it alone). My question is, in the Dozuki, it states "You must enable senorless homing if you want to use stall detection". Is this still true? I have a BLTouch, and Im using end stop switches and everything seems to be working as it should. In my rehome.g I only have:

M400
M118 S"CRASH DETECTED"
G28 X Y
M400

Does resume.g run when rehome.g is triggered? Is there more I need to add? I also read:
"Step 2: Enable M915 in your slicer

This step requires the same M915 command that is in your rehome.g file be at the END of your STARTING gcode script in your slicer of choice. Place it at the end of your start script gcode commands.

Step 3: Include M915 X Y S3 R0 F0 at the BEGINNING of your ENDING gcode script in slicer of choice"

I dont have an M915 command in my rehome.g. It seems like what is being implied is that stall detection should only be enabled (with an consequent action) during printing. If so, thats easy enough, Im just confused on what all needs to be in rehome.g and if stall detection can be used without sensorless homing.

Using stand alone Duet 3, MB6HC 3.01-RC10, Duet Web Control 2.1.5. I think youre right. Went I went line by line, M558 is where it changed back to 0.7.

@Phaedrux
It sure does. It works like an absolute champ. Thank you so much.

@Phaedrux
Woah. This is a treasure trove of information. So many new uses, that solve a number of things I have been working on. The M913 is exactly what I was looking for, thats brilliant. Im starting to understand part of my learning problem, I go to the zuki, look for the command and immediately scroll to the applicable firmware, not realizing that often only changes are listed. M558 for example, I had no idea feedrate was supported. Headslap. I used your changes, and it works perfectly thank you so much!

One I dont fully understand is the P flag for G31. If I half understand, it sets the threshold for the signal for , in my case, the BLTOUCH. How is this value determined?

Phaedrux, and everyone here, you have all been so helpful, and it really is appreciated. This seems to be a really amazing community, and thank you for taking the time.

Okay, so I went line by line to see when the z-trigger height changed. In my latest config its set to 2.8
G31 reports the same. When Homeall.g runs:

M558 P9 C"io7.in" H5 F600 T5000 

G31 reports 0.7.
Thats when it is changing but I dont understand why. Unless re-declaring the pin without defining the mesh defaults to 0.7? I suppose I could just define the mesh 3 times?

Oh thats handy, okay I will check that and see if it changes as soon as I can.

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Apr 17 2020 12:59:14 GMT-0400 (Eastern Daylight Time)

M564 H0
G91                     ; relative positioning
G1 H2 Z5 F7200          ; lift Z relative to current position
M558 P9 C"io7.in" H5 F600 T10000  

G1 H1 X-345 Y-345 F7200 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-345             ; home X axis
G1 H1 Y-345             ; home Y axis
G1 X5 Y5 F7200          ; go back a few mm
G1 H1 X-345 F1800       ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-345             ; then move slowly to Y axis endstop
G90                     ; absolute positioning
G1 X-7 Y-9 F7200        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed
M558 P9 C"io7.in" H5 F150 T10000  
G30

M564 H1

 
; Uncomment the following lines to lift Z after probing
;G91                    ; relative positioning
;G1 Z5 F120             ; lift Z relative to current position
;G90                    ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Apr 17 2020 12:59:14 GMT-0400 (Eastern Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F7200   ; lift Z relative to current position
G90              ; absolute positioning
G1 X-7 Y-9 F7200 ; go to first probe point
G30              ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91             ; relative positioning
;G1 Z5 F120      ; lift Z relative to current position
;G90             ; absolute positioning

@Phaedrux

Whoops, sorry about that!

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Apr 17 2020 12:59:14 GMT-0400 (Eastern Daylight Time)

; General preferences
G90                                          ; send absolute coordinates...
M83                                          ; ...but relative extruder moves
M550 P"Evo Duet 1"                           ; set printer name

M667 S1                                      ; select CoreXY mode

; Network
M552 P0.0.0.0 S1                             ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                   ; enable HTTP
M586 P1 S0                                   ; disable FTP
M586 P2 S0                                   ; disable Telnet

; Drives
M569 P0.0 S1                                 ; physical drive 0.0 goes forwards
M569 P0.1 S0                                 ; physical drive 0.1 goes backwards
M569 P0.2 S0                                 ; physical drive 0.2 goes backwards
M569 P0.5 S0                                 ; physical drive 0.5 goes backwards
M584 X0.0 Y0.1 Z0.2 E0.5                     ; set drive mapping
M350 X16 Y16 Z16 E16 I1                      ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z806.45 E837.00          ; STOCK E837 STOCK Z806 set steps per mm
M566 X800.00 Y800.00 Z15.00 E12.00         ; set maximum instantaneous speed changes (mm/min)
M203 X7800.00 Y7800.00 Z1500.00 E1200.00     ; set maximum speeds (mm/min)
M201 X850.00 Y850.00 Z20.00 E250.00          ; set accelerations (mm/s^2) (LAST 3000XY)too much
M906 X1500 Y1500 Z1500 E1680 I30                 ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                      ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                             ; set axis minima
M208 X290 Y285 Z570 S0                       ; set axis maxima

; Endstops
M574 X1 S1 P"io0.in"                         ; configure active-high endstop for low end on X via pin io0.in
M574 Y1 S1 P"io1.in"                         ; configure active-high endstop for low end on Y via pin io1.in
M574 Z1 S2                                   ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io7.out"                           ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H5 F350 T10000             ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X22 Y24 Z2.75                   ; set Z probe trigger value, offset and trigger height
M557 X15:300 Y15:300 S60                     ; define mesh gridM557 X5:255 Y10:300 S40 


; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                           ; create bed heater output on out0 and map it to sensor 0
M143 H0 S120                                 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00                             ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                      ; map heated bed to heater 0
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                           ; create nozzle heater output on out1 and map it to sensor 1
M143 H1 S280                                 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00                             ; disable bang-bang mode for heater  and set PWM limit
M308 S2 P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2                           ; create chamber heater output on out2 and map it to sensor 2
M143 H2 S280                                 ; set temperature limit for heater 2 to 280C
M307 H2 B1 S1.00                             ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2                                      ; map chamber to heater 2

; Fans
M950 F0 C"out7" Q500                         ; create fan 0 on pin out7 and set its frequency
M106 P0 C"Part Fan" S0 H-1                   ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out9" Q500                         ; create fan 1 on pin out9 and set its frequency
M106 P1 C"HotEnd Fan" S1 H1 T45              ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"out3" Q500                         ; create fan 2 on pin out3 and set its frequency
M106 P2 C"CaseFan1" S0.25 H-1                ; set fan 2 name and value. Thermostatic control is turned off

; Tools
M563 P0 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
M307 H0 A110 C600 D60 S1
M307 H1 A598.7 C312.1 D3.3 S1
M307 H2 A70 C600 D60 S1
						; filament sensor
;M950 J12 C"io6.in" ;working
;M581 P12 T3 S1 C1	;working
M591 D0 P2 C"io6.in" S1




; Miscellaneous
T0                                           ; select first tool

Good lord. Thats pretty embarrassing. Of course its in resume. Thank you so much!

@Phaedrux
I played with it some more to get a better idea of how to explain what I am seeing. Its as if any z trigger defined in config.g is no longer effecting the z trigger height. If I dont use the "double home" and travel to Z0, its exactly where it should be. If I do, its 2.5-3mm off the bed at Z0. I have set the trigger height all the way down to 1mm and it always ends up at the same height, floating above home.

I have ```
M558 P9 C"io7.in" H5 F150 T16000

in config.g and the cgode in the first post in homeall.g. Should I be using G28Z instead of G30?

Hi everyone....its me again. The title captures the issue pretty well.

From config.g:

M591 D0 P1 C"io8.in" S1

Working like a champ. It pauses, right on cue, life is good.

But when it resumes the print (after I load fresh filament and purge a bit) it happily bounces back to its previous location, and dumps a bunch of filament and then continues.

pause.g is pretty much untouched:

M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

Any ideas what sort of silly noob mistake Im making this time? Thanks everyone for all the help.

I have absolutely no idea. The Z-off just seems to......drift? I had to add .50 to it, so its not too much or anything, but it seems to effect.

Hey all. So I have a machine that has a high end Z-stop and a BLtouch. I would like the initial home to be fast, and an immedaite followed by a more accurate probe. If I define:

M558 P9 C"io7.in" H5 F800 T16000 
G30
M558 P9 C"io7.in" H5 F150 T16000       
G30

It seems to work well, as far as finding a "rough z" quickly and then an accurate Z, but it seems to effect the z-offset and and I dont know why. Is there a better way?

@Phaedrux
I want to thank everyone here, it seems to be a really amazing community. What I have blindly achieved with the duet on old chinese crap hardware has blown my mind. I think its really hard for well versed people to make guides for noob window lickers. Maybe I can give back a little bit and contribute from a tech savvy but largely stupid point of view? Is there a way I can help? Maybe the walls I hit I can help document?

@Phaedrux
OH! Wow, that cleared up all kinds of stuff. I was just uploading the firmware file (singular) that I thought I needed.

Board: Duet 3 MB6HC v0.6 or 1.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.01-RC10 (2020-04-25b3)
Duet Web Control 2.0.7

Okay so I will try uploading the DWC, firmware, and IAP and see what happens...

Everything worked! Im now on DWC 2.1.5 and the firmware updated just fine from DWC. Thank you so much. Where is the information that explained all this? I do really appreciate the help, but I would like to not ask questions that are in the reading, but I really cant find this guidance anywhere. Am I missing something?
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
doesnt answer these questions (or does and Im just extra special) is the dozuki intended as a jumping off point and the forum is the primary guidence?

@dc42

Thanks for the reply DC. I dont experience any issues when running standalone mode.
I was just trying to get a better understanding of how the system works. As I am no longer running a the DuetPi setup, I no longer have any issues with macros getting called. The current setup is the Duet 3 running in stand alone connected via ethernet, with a Repetier Pi server connected via USB for a touch screen interface, with the Repetier server using wifi to connect to the network.

The only issue I am having, is probably a user error issue. I tried to upload the firmware (Duet3Firmware_MB6HC.bin) via the DWC. It didnt recognize it. Deleted it uploaded again, no joy. I fired up Bossa and it uploaded perfectly. I do not understand what I am doing wrong. Is there documentation the outlines the different firmware files and their use?

SDuet3Firmware_EXP3HC.bin - I assume this is for the expansion board.

Duet3Firmware_MB6HC.bin - for the mainboard upload via Bossa and DWC?

Duet3Firmware_TOOL1LC.bin - No idea.

Duet3_SDiap_MB6HC.bin - I was told this is to allow the board to update itself, but I can find no information for usage.

DuetWebControl-SD-2.1.5.zip - I am 98.64% sure this is for making the stand alone or pi SD card, but it doesnt look to be an image that would be used via etcher.

I dont want to bother everyone if there is documentation to explain this, but I have been through the guides front and back and havent found an explanation.