Yes there was a change that prevented movement of axis before they were homed.

You'll have to either add a command to the config.g to allow those movements by default or you can edit your homing files to allow just those homing moves. Usually it's the z lift before homing x and y.

From the FAQ

I get this error message: "Error: G0/G1: insufficient axes homed" ¶
Recent firmware versions do not allow axes to be moved before they have been homed. The only movements allows are homing moves (G1 moves with S1 or H1 parameter) and individual motor moves (G1 moves with S2 or H2 parameter). So any Z movements that your homing files make before Z is homed should use the S2 parameter. Alternatively, add M564 H0 to config.g to allow axis movement before homing.

@dc42 That's right, I forgot to mention about the #0 /menu issue, thanks for noticing that too! Thanks also for increasing buffer size, this will give even more freedom in menu creation.

Regarding menu button text alignment when a width is specified, both centered and right aligned would make sense for me. Centered would be perfect for text buttons (ex: buttons in top menu bar), right align for array of numbers (ex: temperatures, movements)

To avoid the addition of a new option, right aligned could be triggered by a negative width while centered is the default.

If just one option can be reasonably implemented, centered would have my preference. Personal opinion only for sure, others may have different views

@dc42 I know specifically that the Viki2 uses the ST7565 and I suspect the MKS mini does as well from what I have seen online.
Adafruit has some documentation that may be helpful including a datasheet http://www.ladyada.net/learn/lcd/st7565.html

I have also noticed that Marlin specifically is using the u8glib to interface with these displays. From what I can see online for the MKS mini displays people are using the minipanel configuration and in the Marlin defines that configs as being the ST7565 display.

That's the wrong folder. Those files and folders must be in folder /www. I think you have some old DWC files in /www instead.

@crchisholm a SDHC card is fine.

@dc42 thank you

Hi dc42:

Problem solved.

I have found 2 poor solderings in Ethernet module, RX, and TX pins.

Thank you very much for your support.

Awesome, Thanks Again!

@synergy41 also in the DWC manual here: https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_General

Thank you for answering me
I found the solution in web control manual
Added
M106 P2 H-1 and now I can drive my leds 🙂
thank you

Yout PT100 daughter board should have been supplied with a 100 ohm resistor. Try connecting it between the middle 2 terminals of the 4-way terminal block in place of the PT100, and see what reading that gives you. It should be close to 0C.

Also check that you have no other M305 P1 commands in config.g, that the M305 P1 X200 line.

@dc42 said in New Duet Maestro firmware:

I am anxious to resolve this problem before we start selling the Duet Maestro at Duet3D and through our distributors, so I will be grateful for your feedback in this thread.

Is there already a date for the availability of the Maestro sold by yourself?

The open load detection doesn't try to stop the motor moving, it just produces the message. I'm downgrading it to a warning in the next 2.02RC because it isn't totally reliable yet.

@t3p3tony its in the comments, within the linked forum post. Just click the link in my post and scroll down the page, you will see it.

You may use the P parameter instead 😄

M915: Configure motor stall detection

Parameters

Pnnn:nnn:... Drive number(s) to configure

@dc42 said in M906 reports E:0 on update to 1.19.2:

That's as expected.

Thanks a ton for your support! 🙂

I suggest you post yoir question at https://reprap.org/forum/read.php?13,569468,page=27 as well.