@Yar m503 reads config.g not what currently stored in flash. Run G31 to find the current value. You will have to edit config.g to save the value

@JlunaMX said in Error: Probe already triggered at start of probing move:

"Error: Heater 0 fault: temperature rising much more slowly"

Have you done a PID tuning of the heater yet?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Heaters_tuning

@Sindarius
Sweet, first time in a long time i look forrward to a RRF update 😅

@Phaedrux
Fixed it thank you. Some how the tool settings got unclicked

@Exerqtor release 3.5beta1 is currently undergoing internal testing. We may release it later today.

There will almost certainly be a 3.4.6 release and the change will be in that one too.

@Phaedrux
that worked thank you!

It will automatically connect to the access point that has the best signal strength.

You could clear your currently save SSIDs and then only re-add the access point that works.

Or you could change your config.g to specify the SSID you want to use.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m552-set-ip-address-enabledisable-network-interface

M552 S1 P"MyNetwork"

@chrishamm Wow. I’m astonished with the almost instantaneous answer and, on top of that, a double solution. Thank you so much. This is also why I use only Genuine Duet3d stuff.

@chrishamm interesting; perhaps there might be some delay issue?

The power supply goes as follow:

24V PSU ------- Duet 3
\______________ 5V DC/DC PSU ________ Rpi 3B+

With the 5V Rpi jumper removed as follows:

5V enable ON,
Duet --> SBC OFF
SBC --> Duet OFF

Perhaps the rpi power up a fraction of a second too late as powers through the additional 5V DC/DC converter?

That might also explain why it would start up fine after a repower; perhaps thanks to some residual juice in that 5V PSU?

Could disabling the 5V Enable jumper and jump SBC --> Duet be worth trying?

@Sindarius that made the trick! thanks

@paolozampini1973 marocco vs spain, marocco won. My country germany is out.

@droftarts
Hi Ian,

M918 P2 E2 F2000 C30 R6
;M918 P2 E4 C70 R4
M150 X2 R255 U0 B0;

Either M918 works

Cheers
Bengt

@Malarius thanks for updating us. I'll mark this as solved but feel free to revert that if the problem occurs again.

@jens55 said in Confusion re DWC 'control heaters':

@dc42 , cool, thanks for that extra info!

Thanks for pushing the issue. 😉

@CCS86 said in Ages "Connecting" From Ext Network:

What is the best practice to secure the machine while allowing external access? I like to be able to check in on my webcam and kill the print if something goes wrong. I am running a password on the Maestro, but I know that isn't very high security.

Look into setting up a VPN if you want full access to DWC. It's a bit beyond the scope of what we can guide people on since it comes down to your own network hardware etc.

If all you want is to see the webcam, exposing that is less of a risk, but you can't remotely kill the print either.

Once way around it would be to setup a computer on the local network and use something like VNC software that has more robust authentication and then use remote desktop access to reach DWC on that local machine.

@Phaedrux
Thank you, sir.
I glanced over those docs before I asked this question, and I misunderstood it to mean that it was asking for a PIN number.
I didn't think about 'PSON' being the PIN name.

All is well now.
Thank you!

@gbartsch To be clear, M109 will wait until the heater reaches temperature. My suggestion was to add an additional G4 pause after the M109 command. The length of the pause would equal the time it takes for the overshoot to settle. But DCs suggestion to reduce the overshoot would be better.

@Kernel_Panik You can delete the file from the sys directory of your microSD card and reload dwc. It looks like you are not using the latest versions either because the notifications look different in the latest version. Potential parse errors caused by dwc settings are better handled in the latest version, too.

@Phaedrux Not. until now. I am gonna try with these settings and let you know.

@Phaedrux Thanks it worked with turning off automatic unpacking