I hoped that the firmware offers such functionality, as even crappy flashforge firmware does. But the mdns approach is a good starti g point.

As I'm writing a centralized 3D printer monitoring and management application that not only works with Duet's. Such functionality would be good.

Hi,
Does the duet firmware provides a method for discovering all duets (incl. their IP's) in a network?

@Furbyhaxx 8 factor calibration did not work..

@Veti I'm not sure if I tried this already, but will do it again.

But what's the cause of this?

Hi folks. I have a long lasting problem with my delta machine (TEVO Little Monster).
I use the nozzle as probe (24v to nozzle, GND to aluminium bed)and custom magball arms.

Auto bed leveling gives me this S-curve warped bed but it actually is flat min max is -0.2/+0.6mm according to auto leveling.

What could cause this? I don't know any further..

HI guys

Today I discovered that every filament related gcode crashes the board immediatly without additional infos (also not in the log)

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2-beta2 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-10-05b2

This happen if I issue the commands directly or over the DWC functions. Also with an emtpy filament.

found the error trought RRF, this line was missing from my config:

M575 P1 S1 B57600                                                ; enable support for PanelDue

interesting is that another machine with the same config and firmware 3.0 also not had this line but the PanelDuet worked without problems after updating.

Hi,
Today on one of our printers the PanelDue stopped communicating with the DuetWifi while updating to firmware 3.1.0. I Tested 3 LCD incl. boards and two 4 pin cables but the PanelDuet stays at "connecting".

When I update the Duet firmware over DWC the PanelDue shows the messages from the firmware update.

Ah, PanelDue firmware was also updated to v1.24

If i pause the print (over DWC or PanelDue) and restart the file resume.g is not executed.
What can cause this?

Board: Duet WiFi 1.02 or later + DueX2
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Version von Duet WiFi Server: 1.23

thanks, when I mesaure across GND and Z PROBE IN I get constant 3.2v, when probe is not triggered and around 17v with a 10k resistor. without the endstop connected I also read 3.2 between GND and Z PROBE IN, is there something defective?