@danny_v1 Further to @oliof's suggestion, see https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#configuring-duet-in-wifi-access-point-mode

Ian

The SD card contains the configuration files. Almost never need to wipe it. The firmware is stored on the board itself. If you're having trouble accessing the board, after restoring the SD card, try this guide,

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

Programming Z probes connected to expansion boards is not yet supported. For now you need to temporarily connect the Smart Effector to the main board if you want to change its sensitivity. I've logged this issue: https://github.com/Duet3D/RepRapFirmware/issues/815

dc42 created this issue in Duet3D/RepRapFirmware open Support programming Smart Effector sensitivity when the effector is connected to an expansion board #815

@oliof That is a really good idea to rule out different possiblilites. im printing right now but later today i can try that. Thank you so much for your input and support.

You can find some hardware source here: https://github.com/Duet3D/Duet-2-Hardware

Have you used the erase jumper or button on the Duet to clear the firmware yet?

If you already have a working firmware on the board you don't need to erase it like that.

Please try following these procedures #1 and if that doesn't work, proceed to #2.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-1

Hello @phaedrux! I am sorry for not responding, I was away.

I ended up solving my problem.

Turns out, that due to me not putting the cover on while using the printer in order to be able to debug, the board was just overheating causing it to shut down in order not to melt.

Thank you for your courage to help me.

-Cheers!

@gloomyandy OUTPUT.txt

@dc42 It's the second module which failed on the board. I will wait my ethernet module for swap now, more reliable

@dc42 Interestingly it did however I assumed you suspected that the values were either not applied / were overwritten.

It turns out there was already a line in the config file specifying the parameters that occurred later that where I had included the correct ones. This was overriding the values and seems to have been what was causing the issues.

Needs some testing to be sure but it seems likes its running smoothly again.

Can you confirm that you are still running main firmware 2.02, as shown in the M122 listing in your first post?

I can ask chrishamm to look into this message, but he will probably ask you to upgrade to Duet Web Control 2.0.0-RC6, available at https://github.com/chrishamm/DuetWebControl/releases.