@phaedrux said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

@alpenprinter said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

What's the latest firmware version known to run stable?

2.02 was the last stable release.

What version of DWC and PanelDue firmware are you running?

I downgraded to 2.02 and all is running fine again. I kept DWC 2.0.0, no problem with this.

@phaedrux said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

@alpenprinter said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

What's the latest firmware version known to run stable?

2.02 was the last stable release.

What version of DWC and PanelDue firmware are you running?

Panel Due 1.20
DWC 2.0.0

What's the latest firmware version known to run stable?

@zerspaner_gerd said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

@alpenprinter said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:

Within long prints, the display and the web interface twice got unresponsive about in the middle of a print (after around 5h).
But the print was finished correctly. After finishing, the duet display (7´) and the web interface still show the bed and hotend temperature that where used during the print.

I also observed that!
At first I thought only of wireless problems but also the PanelDue did not react anymore.
I also had this in 2.03 RC, Final 2.03 I have just installed today.

Since updating to 2.03, I think, that there is a new issue.

Within long prints, the display and the web interface twice got unresponsive about in the middle of a print (after around 5h).
But the print was finished correctly. After finishing, the duet display (7´) and the web interface still show the bed and hotend temperature that where used during the print.

The "STOP" button on the display reacts, but failed to connect to the duet board again.

Power on/off fixes the problem.

In the 2.03 RC the fault did not appear.

For homing and bed tilt leveling I use the endstops. The probe is only used for mesh bed leveling from time to time.
I thought, the Z-offset of the probe does not matter, because the probe is only used for generating the heightmap and leveling is done by the endstops, anyway.

; homez.g
G91
M584 Z2 U4 P4. ; split Z motor control to Z and U for it to work we have to show U (param P4) in the UI
G1 S2 Z6 U6 F6000 ; move bed down 6mm
G1 S1 Z-300 U-300 F4000 ; move quickly to Z axis endstops and stop there (first pass)
G1 Z2 U3 F4000 ; go back a few mm
G1 S1 Z-300 U-300 F300 ; move slowly to Z axis endstops once more (second pass)
M584 Z2:4 P3. ; back to combined axes and hidden U
G90 ; Back to absolute positioning
G92 Z4.66 ; Z offset (positive is closer to bed)
G91
G1 Z5 F3000 ; lift Z after probing
G90

Hi!

My Z-Offset is increasing about 1mm with ever print. If I restart the firmware, it is not increasing.
The heatmap is under the Z= level - may be this has to do with the problem?

Setup:
Duet Wifi, Slicer S3D
Bed leveling is done with two optical Z-min endstops and two steppers - working fine.
Than the stored heatmap is used vor auto bed leveling.

Autobed leveling is done with a precision piezo orion probe.

config.g:
; Z-Probe
M558 P8 I1 R0.4 F300 T10000 H1 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z0 ; Set Z probe trigger value
; Endstops - empty

The sequences before printing are:

Set the Z-offset in homeall.g and homez.g
G92 Z4.66 ; Z offset (positive is closer to bed)

In the S3D start-script home all axis and activate bedleveling with the stored heatmap:
G28 ; home all axes (homeall.g)
G29 S1 ; enable mesh grid compensation from saved file

Any ideas?

Hi!

I use a XY Core Hypercube evolution printer with duet wifi and a precision piezo orion as Z min sensor.

Is it possible to let the precision piezo do the Z homing on top of the print and then set „0“ to the last stored Z position?

How should the config files look for that?

Martin

Hi!

I get mad with the configuration of my capacitive Z-probe.

The probe is connected to E0 switch. It switches the E0 led on the duetwifi as it should. P0 changes to P1000.

On the web interface, in machine status, the Z stop does not change status, but the E0 status does when switching.

And further more I can't invert the E0 status.

What I am doing wrong? Could s.o. please give me a hint on this?

; Endstops
M574 Z2 S0 ; Set active low endstops
M574 E0 S1
M574 X1 Y1 S1 ; Set active high endstops

; Z-Probe
M558 P4 I1 Z2 H3 F200 T5000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds H5 F120 T6000
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S20 ; Define mesh grid

You are right. It is the cable!

I rolled up the cable and the checksum errors disappeared.

I will make a shielded, shorter cable. That should fix the problem.

Duet3D should deliver a shielded cable with the duetwifi.

Martin