duet 3 mini 5+ ethernet broken

droftarts

@markus-calligaris check if config.g is still on the SD card. There have been instances of the config.g being deleted, so next reboot there is no Gcode to start the network. I haven’t heard anyone having this issue with newer firmware 3.3, so check firmware version too.

Connect via USB. Send M115 for firmware version. Send M552 S1 P[fixed_IP_address], or if you use DHCP and the machine name to connect, send M550 P"[machine_name]" then M552 S1 P0.0.0.0 to enable network. Then you should be able to connect to DWC.

Ian

markus calligaris

how can that be? the config g file was 0KB

droftarts

@markus-calligaris See my post here https://forum.duet3d.com/post/233267
We haven't had many reports recently of it happening, and haven't been able to replicate it. Please post what firmware and DWC version you are using.

Ian

markus calligaris

@droftarts FW 3.3 and dwc 3.3.0

Phaedrux

Haven't seen a report of this in quite some time.

With a new config.g are you back up and running?

Was there a config.bak present?

Spoke too soon, now I see another thread today with the same config missing issue.

When and where did you purchase the Duet?

BigDee

@phaedrux I have the exact same problem on a Mini 5+ Wifi. I bought the board approx. 4 weeks ago from a German dealer. It was shipped with Firmware 3.3 and runs DWC 3.3.0.
This now happened the third time within 3 days of testing. The first two times i wasn't familiar enough to understand what was going on. But after some trying and having the first movements on the machine i finally figured out what happened.

Setup of my machine:
12V power supply
only 4 stepper motors connected (X, Y and two Z motors), no hotend, not thermistors, no fans, no endstops etc.

My machine was running smooth. Got sensorless homing on X and Y working, homing on Z manually. Did a lot of testing on accelleration and speed. Created some very simple Macros for this (go to Z min, go to Z max, go to X and Y min, go to X and Y max) and played with them. All went without any problems. While everything was up and running i wanted to look into my config.g (which was shown in DWC) but got the error that no config.g is present. In this state i was still able to run any of my macros and the machine did the movement properly. After switching off power i was not able to re-connect. I connected it via serial tools and M552 reported "WiFi module is disabled". I have observed the exact same thing on the other two occasions.

I enabled the Wifi module but was not able to connect. Once i stored SSID and password again (M587) i was of course able to connect. But now there is no more config.g. Before all this there was a config.bak but this is not there anymore.

Interestingly my homex.g is still the original one i created. It seems as if only the config.g is affected.

What to do next?

Regards,
Dieter

Phaedrux

@bigdee said in duet 3 mini 5+ ethernet broken:

This now happened the third time within 3 days of testing.

So you're saying your config.g has disappeared 3 times in as many days?

BigDee

@Phaedrux Not sure if the config.g disappeared the two times before because i generally didn't understand what happened and simple did the whole process of connecting from scratch like described in the documentation.

But i can confirm: After i wrote my post i disconnected the board from the USB plug and reconnected and had the same problem again. M552 reported "WiFi module is disabled". I had stored the SSID and pw before with M587.

Still all my homing files and also my macros are there. It really seems to affect the config.g only.

I will do another test and create a config.g and observe if it will happen again.

Phaedrux

@bigdee There are two things that you can try, first is replacing the SD card with a new one. The other is to try the 3.4 final release that should be out tomorrow. If neither of those things solve the issue we should replace the board.

BigDee

@phaedrux I will try to get everything up and running first (and make a backup of config.g on my mac) ;-). If this problem occurs again i will change the SD card and try again. If it happens again with the new SD card i will get in touch with you.

Thanks for your support so far.