What hardware version of panel due is it?
What do you mean the colors are incorrect?

Endstops only stop movement during a homing move.

If you want them to act as a stop during normal opperation you can reconfigure them after homing to act as a trigger that can do an estop, (or whatever actions you want).

https://docs.duet3d.com/en/User_manual/Tuning/Triggers#firmware-configuration

In your homing files at the start you'd want to have the normal endstop configuration so that they work during homing. Then at the end, reconfigure them as a trigger. Or enable the trigger only during a print by putting it in your start gcode after homing is finished.

@Esteban said in Untimely stop and reversal of movement, SZP sensor reading error:

I get an error telling me that the points have been skipped

This means your grid has points that are outside of the reachable area of the probe. When choosing the grid extents, take into account any offset your probe has.

For the problem of prints failing, can you gather a diagnostics report using M122 right after it happens?

For the problem with drivers, it's not totally clear what the issue is. Are you saying that motors connected to the mini2 card, don't work?

In general I think it would be beneficial to split up your issues into individual forum posts. It's much easier to tackle one thing at a time.

Also please share your config.g and the results of M122 here so we have a better idea of what you're working with.

@Surgikill you can certainly have a trigger generate a M291 dialog.

@genioluiz7 did you try using M997 S1 to reinstall the WiFi firmware?

@nicaris said in Duet 2 wifi homing issue:

The probe does deploy. I can home the x and y but the head will move away from the x and Y axis along the x axis (emergency stop triggered !

Can you share a video if what you're seeing during homing?

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.2

It may be a good idea to go back to firmware version 3.5.3 stable release until everything is working well before testing a beta firmware.

@gnydick what frequency did you offer from measuring the wavelength of the ringing and knowing the print speed at that point?

@gnydick the units are 1 = gravitational acceleration. As the amplitudes of the peaks in your plot are so small, it may be that your machine doesn't need input shaping.

Input shaping is more effective in RRF 3.6 beta versions than in 3.5.x.

@PetrKroupa please try the updated MB6HC firmware binary at https://www.dropbox.com/scl/fo/kaxbpbsyq2lxbae4tmzpk/AAPVUAh6CO_FMO-cG9ttX6U?rlkey=f0aesppc8d2p7bzwwi2s1jayo&dl=0.

@PetrKroupa thanks for reporting this issue, which I have just confirmed. I'll work on a fix.