@fcwilt

Thanks appreciate the help.

@LeeElms

Lee, I am not very familiar with its use but I believe M118 can be used for that purpose. You can also use the "echo" command in macros to sent messages to the console as he macros progress. No G code required and no parameters required. just add a line "echo "sending note to console"" and when it is read in the macro it will be sent. The following example is my current deployprobe.g file. Hope that helps.

M564 S0 ; let travel outside print zone if sensors.probes[0].value[0] == 0 ; if sensor is value ia 0 do this, 0 = probe attached echo "Probe already attached" if sensors.probes[0].value[0] == 1000 ; if sensor is 1000 do this, 1000 = probe detached G1 X53 F20000 ; X position of klicky dock G1 Y347 F20000 ; Y position of klicky dock M400 G1 Y175 F12000 ; slide out of dock return to bed Y center G1 X175 F12000 ; slide out of dock return to bed X center M400 ; wait for moves to finish if sensors.probes[0].value[0] == 1000 ;Check to see if probe is attached 1000 = not attached G1 X175 Y175 F10000 abort "Attach probe FAILED!" else echo "Attach Probe Successfull" M564 S1

@Rich-T Copy config.g.bak to config.g on /sys

@droftarts thanks a lot. I know the Zip download. Cool would be one button. I will look in the other options.

By the way, after changing the SD card to a new one, I did not face the issue anymore.

Thanks.

I am also having a similar issue. I am on 3.5.0 b4. Uploading files is hit or miss. DWC will disconnect and refresh. If I keep retrying it will eventually work. The larger the file, the more I need to retry. It was fine when I was on 3.4.5. I upgraded firmware to address other issues.

Running 3.5.0 rc2 causes layer shifts when using input shaping so upgrading is not an option

@oozeBot Looks good, feel free to send me a PR for this!

@chrishamm

@soare0 I commented T0 in config, as the printer started by default (at power on) with the corresponding heather active.
I see the point. As a beginner in working with GCODE, I associated the tool with the heather in my mind.

@Freddy said in How To upgrade DWC:

@airscapes where did you get the latest dwc zip file? I am trying to update mine.

They're posted here.

@Simone said in how to add the z-probe status?:

how i tell the difference in height between the probe and the nozzle to the height map?

See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height

It would help you a lot, and speed up helping you, if you did what I asked for earlier:

Please send M115 in the console and post the response so we know what hardware and firmware you are using. Please also post your config.g, homeall.g and homez.g.

Please post these as text, not images. Ideally, post code within code tags, by clicking the button that looks like </> in the toolbar.

Ian

@soare0

Thanks for the info.

Keep us informed.

Frederick

@soare0 Okay, thanks. I think you mean that the 6XD isn’t explicitly listed in the list of supported boards? I’ve updated the list to include the 6XD.

Generally users update using the zip file in the RepRapFirmware release, so rarely look at the DWC GitHub repo. But it’s good to get the documentation correct!

Ian

@Stan said in DWC 3.5.0-rc.1 disconnects after a while:

Y is 3400mA (dual Y motors)

If you're using a Duet 2, the motor current is probably just set to max, ie 2.5A.

Are your motors wired in parallel? I'd guess they are if you have doubled the motor current. However, due to the current limit of the Duet 2 drivers, they are only getting 1.25A each. If they are wired in series, the voltage is doubled rather than the current, which the stepper driver can do itself. You would potentially lose top speed, but the controller would run a lot cooler.

Ian

I will mark this as Solved

I have sadly become very disenchanted with D.W.C. and its ongoing issues which have spanned over a number of years now (as others have mentioned/posted about) with no evident solution pending from the Duet team.

So I have been left with no option but to take matters into my own hands and do the unthinkable (I have been a staunch supporter of both Duet hardware & and R.R.F. over the years) So it pains me greatly to be forced to switch my printers over to Klipper with the Fluidd web interface which is much cleaner, lean and configurable.

Its been a learning curve for sure but once you get it you get it. I have managed to get the exact same functionality in klipper as i had in R.R.F.

My final hurdle was to get my 6HC's & 1LC Tool boards to play nicely together with klipper which required a bit of lateral thought to get the Tool boards flashed with klipper compiled firmware.

I managed to set up my Rpi's to each run two instances reducing the hardware cost required to use Rpi's

So now D.W.C can be left to be as geriatric as it wants and it wont get on my ti** any more

Au revoir Duet3D

OK... might be solved / dump builder / user. I examined the antenna closely, and it might be that the case I have this is has such a thick wall, that the antenna screw in base, was just barely sticking out enough to have the antenna screw in to it. It might have been loosening up or jiggled around just a bit in the last few months and that is why it has been getting worse and worse.

I only solved this, because I was looking that the signal strength, through YAT, when it wouldn't connect. That was because of you folks pointing that out and me focusing a lot more on it. THANK YOU SO MUCH.

I'm not 100% sure this is going to fix it, but it is connecting atm and the signal strength is -64 on average. Which should work fine, but we will see.

@0nn0 You can put it in config.g with S1. As it says in the documentation...

1 = enable filament monitoring when printing from SD card,
...
Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled.

Ian