@3DOeste please would you test this with 3.6beta3 RRF and 3.5.1 Paneldue firmware:

https://forum.duet3d.com/topic/37289/software-version-3-6-0-beta-3-now-available
https://forum.duet3d.com/topic/37179/paneldue-firmware-3-5-1-released

these together should have resolved this issue.

@jay_s_uk
#############################################################
; AutoZ - Automatic probe offset adjustment
;
; to use autoz, please place the following near the end
; of your slicer start gcode
; M98 P"/macros/autoz/autoz.g" <<< Place in slicer
;##################################################################

;##################################################################
; prepare
;##################################################################

M98 P"/macros/autoz/autoz_settings.g" ; Load your settings
M98 P"/macros/autoz/scripts/autoz_globals.g" ; Load autoz framework
G29 S2 ; Disable mesh
M290 R0 S0 ; Reset baby stepping

;##################################################################
; Probe the nozzle on teh Z-pin
;##################################################################

;G1 E-5 F1000
M98 P"/macros/autoz/scripts/autoz_move_up.g" ; large z hop incase the nozzle is low and you have a high pin
M400
M98 P"/macros/autoz/scripts/autoz_goto_zpin.g" ; go to the z pin
M400
M98 P"/macros/autoz/scripts/autoz_adjust_safe_zdrive.g" ; set z drive safe physics
M400
M98 P"/macros/autoz/scripts/autoz_probe.g" K1 H5 A4 S0.004
M400

if !exists(global.macrocallresult)
echo "Call to macro failed. Aborting"
abort
;end if

var nozzleheight = {global.macrocallresult}
echo "nozzleheight: ", {var.nozzleheight}

M98 P"/macros/autoz/scripts/autoz_restore_zdrive.g" ; restore the z drive to the state before autoz
M400
M98 P"/macros/autoz/scripts/autoz_move_up_small.g" ; move up 2mm
M400

;##################################################################
; Load the magprobe
;##################################################################

M98 P"/macros/autoz/scripts/autoz_move_up.g"
M400
M98 P"/macros/magprobe_attach.g" ; pick up and verify clicky
M400
M98 P"/macros/autoz/scripts/autoz_goto_zpin_magprobe_offset.g" ; move the clicky probe switch body over the z pin
M400
M98 P"/macros/autoz/scripts/autoz_adjust_safe_zdrive.g" ; set z drive safe physics
M400

;##################################################################
; Probe magprobe body on the Z-pin
;##################################################################

M98 P"/macros/autoz/scripts/autoz_probe.g" K1 H5 A4 S0.004
M400

if !exists(global.macrocallresult)
echo "Call to macro failed. Aborting"
abort
;end if

var magprobeheight = {global.macrocallresult}
echo "magprobeheight: ", {var.magprobeheight}

;##################################################################
; Probe the bed
;##################################################################

M98 P"/macros/autoz/scripts/autoz_move_up.g" ; hop to clear the switch
M400
M98 P"/macros/autoz/scripts/autoz_goto_bedcenter.g" ; go to the center of the bed
M400

M98 P"/macros/autoz/scripts/autoz_probe.g" K0 H5 A4 S0.004
M400

if !exists(global.macrocallresult)
echo "Call to macro failed. Aborting"
abort
;end if

var bedheight = {global.macrocallresult}
echo "bedheight: ", {var.bedheight}

;##################################################################
; Calculate probe offset
;##################################################################

var nozzleswitchoffset = {var.magprobeheight - var.nozzleheight + global.switchoffset}
echo "nozzleswitchoffset: ", {var.nozzleswitchoffset}

var probeoffset = {var.bedheight - var.nozzleswitchoffset}
echo "probeoffset: ", {var.probeoffset}

;##################################################################
; Set probe offset as baby step offset
;##################################################################

M290 R0 S{var.probeoffset}
M400

;##############################################
; Finish up
;##############################################

M98 P"/macros/autoz/scripts/autoz_restore_zdrive.g" ; restore the z drive to the state before autoz
M98 P"/macros/autoz/scripts/autoz_move_up.g" ; small z hop
M400
M98 P"/macros/magprobe_dock.g" ; unload the clicky probe
M98 P"/macros/autoz/scripts/autoz_goto_bedcenter.g" ; go to the center of the bed

;##############################################
; Done
;##############################################

@darylprice sending M997 from DWC should be sufficient to update the 6HC to the same firmware version as DSF. I think DSF will only auto update minor versions (ie 3.5.3 to 3.5.4) but not major versions (ie 3.4 to 3.5), but M997 should fix that. See https://docs.duet3d.com/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

Ian

@MichaelKallner the change logs detail what changes have been made between 3.4 and 3.5. That is quite a big jump so there will be a fair few changes however most won't apply to your specific machine config.
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

how do i mark this as solved?

@RodrigoRMaraujo said in Duet maestro - Diag led does not turn off:

I've been buying Duets on AliExpress since 2019

Just curious, since you’ve benefited so much from their work without buying genuine hardware, have you offered to contribute to the Duet development team?

@pma_ (Thread restored as may be useful to others) See the language drop-down in DWC > Settings > General > Appearance > Language

6d49c39f-7ced-4362-9763-389dfb00dd6f-image.png

Ian

@pma_ I've restored this topic, in case other Maestro owners have problems.

It's a big jump to go from 2.05 to the latest RRF 3.x, and involves many config changes. Please post your 2.05 and 3.x config.g files. There have been changes to the network code, but they shouldn't affect connections, and I haven't had problems with my Maestro in testing.

Some suggestions:

The network code in the firmware has been changed, and causes a different MAC address to be generated. If your router has MAC address filtering, you may need to update this on the router. If you're using the original SD card that was supplied with the Maestro, it's probably quite old and slow. Newer versions of DWC do make more demands on the SD card. Test your current SD card; see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues. Replacing it with a faster card may help, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card Do you have other network protocols enabled, ie FTP, Telnet? If you don't use them, disable them. In DWC Settings > Machine-Specific > Communication, increase "Number of maximum AJAX retries" setting to 4. Change "Time to wait between AJAX retries (ms)" to 250. Don't have multiple browser pages across multiple devices connected to DWC at the same time.

Ian

@droftarts
Ian thank you very much!
Problem solved
🤗

@alil2096 said in Issues after upgrading to 3.5.4 | Duet2wifi:

Please send M122 and post the response.

For the fans, I can't think what would stop all the fan outputs from working other than the fan fuse blowing, or the jumper that sets the fan voltage being removed. Did you use the fan voltage jumper to jumper the erase pins, to flash the firmware, and perhaps put it back in the wrong place? See the wiring diagram https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#wiring-diagram and check 'V FAN JUMPER SELECT'.

What kind of probe? You have inverted the probe in your current config.g. What value does the probe report in DWC? I don't know what has changed with probing between 3.2 and 3.5 (something may have done) but if the probe is reading correctly, try just recalibrating the G31 Z offset. See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing

Your speeds on Z are quite high, particularly Z jerk (M566). Are the Z motors turning a leadscrew? Older RRF versions may have been limiting this. Try M566 Z20, and work up from there. You may also need to reduce the Z speed (M203) and acceleration (M201).

Additionally:

You have a number of lines in config.g that refer to a 'U' axis. Remove the U parameter from the following: M350 Z16 U16 E256:256 I1 ; configure microstepping with interpolation M92 X133.33 Y133.33 Z640 U640 E6550:6550 ; set steps per mm ... ; Axis Limits ... M208 X370 Y330 Z398 U398 S0 ; set axis maxima You are running the extruder at x256 microstepping. Most likely, changing to x16 microstepping with M350 E16:16 and changing steps per mm to M92 E409.375:409.375 will offer no reduction in print quality, while dramatically reducing the time the MCU has to spend calculating extruder stepper pulses.

Ian

@HiWing This is your third post on the Duet3D support forum, none of your previous posts have asked for help. If you want help, ask, and supply some information we can help you with (machine details, current config.g, M122 report). If you're having problems with firmware updating, check this guide. If you suspect a hardware problem, follow this guide, and ultimately our warranty support is robust. I can't help you if all you post is negativity with no content, and that attitude won't help you get support.

Of course it's easier to set up a fully commercial machine. The company that produces it has complete control of hardware and firmware, can test and tune it before it gets sent out. I appreciate this about the commercial printer I bought, it's pretty much plug and print, even though my intention is to swap it to Duet eventually. That's the part you have to do yourself on a custom built machine, or conversion. We offer tools to make the process easier, for example the RRF configuration tool, example configurations for machines (though while you may have the same machine, you may have wired it differently) and extensive guides and documentation. Then there's the forum here to ask questions directly to support staff, and even the firmware developers, for anything else. I doubt your commercial machine is as well supported, I know mine isn't.

If you have any suggestions for 'making better tools to make the user friendly', we're listening.

Ian

@oliof thank you, my friend

@Alex There were some compatibility issues between the old and new configtool but that's fixed now. On the start page you should be able to click "Load config template" and then load your config.json.

@chrishamm Thanks Christian. Thursday I'll be at formnext, maybe we see each other.

@Dbioceramics This is a pretty good summary for cartesian machines: https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_cartesian
CoreXY machines like the Ratrig vcore modify the X and Y drive mapping, see https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_coreXY

If you then use the configuration tool, for each section there is a 'Show Gcode Preview' so you can see how the configuration is set, eg

dfb0b992-5f70-4313-878e-677568440ea1-image.png

Pressing 'Show G-code preview' at the top of the section shows:

67e0c450-f942-4ab7-a621-381cb1197efd-image.png

Ian

Updating my previous toolchain from 10.1 to 13.2 fixed the problem and is compiling,
Thanks Guys 🙂