@Adrian52 thanks for reporting this. I suspect that it is caused by enabling debouncing of inputs on Duet 2 and Duet 3 6HC and 6XD in rc1. I'll disable debouncing on filament monitor inputs in the next build.

@thomasvanderwal said in Duet 2 v1.02 not responding:

Then g31 and then that value into the config.g.

What value do you get?

How are you doing the delta calibration? Is there a G30 at the center of the bed afterwards to establish Z0?

Have you seen this page yet?
https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration

It sounds like the firmware has been erased at the very least. Please try reflashing the board using these instructions.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards

If the board shows up in Bossa and takes a flash, you should be alright. If not, then it may be damaged.

Do you notice if any components on the board become very hot to the touch not long after power has been applied?

Can you take some clear high resolution photos of the board itself so we can check for any obvious signs of damage?

Have you given the board a blast of compressed air just incase there is still some debris left behind that could be causing a short?

How are you checking it?
What error does it report?
Are you following these steps to flash the firmware?
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards

For reference here are the instructions for updating the PD firmware.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

When it's showing the white screen do you hear any beeps when you touch the screen as if you were pressing buttons? This would assume that the firmware hasn't already been cleared.

https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#led-indications

The LED between the USB port and the reset button is the USB power indicator. Do you have the board connected via USB at all times?

Is the board responsive to USB terminal commands?

For networking issues, it would help to know if you're using wifi or ethernet and what the contents of your config.g are.

It may help to go through this guide.
https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

Thank you for the video.

Can you do a test for me? Manually send the commands from your homea.g or homeb.g files one line at a time and check the macro tab in between to see if there is a specific line that is causing it.

I'm also curious if your PanelDue cable runs near the cables for the A and B motors? What kind of cable are you using for the PanelDue? How long, etc.

Did you change your steps per mm as droftarts suggested?

M564 S0
G30 S-1
G92 Z0

Can you describe more clearly exactly how you're measuring the trigger height for the probe?

Have you gone through the probe testing and calibration steps from that link earlier? For instance, have you confirmed that you can stop Z movement during a G30 by taping the bed manually? As in, does the probe seem to be working?

@leodege which version PanelDue? Have you pressed the Erase button and then the Reset button?

What message if any do you get from the PC when you connect the USB cable?

If Bossa can't flash it because the Bossa port is not coming up on the PC then SAM-BA won't either.

@trulm You can make the system files read-only both in SBC and standalone mode. If you are using your board in standalone mode, you need to eject the microSD card, put it in a PC, and toggle the "read-only" flag of the files you wish to protect using a file explorer (in directory sys). In SBC mode, you can connect via SSH and remove the w flag from the files in /opt/dsf/sd/sys using chmod.