Duet 3 6HC + Wifi Module error at startup
-
Hello,
I have a Duet 3 and I have just installed the Wifi Module in it. I have the wifi setup from the usb serial tool fine and when started from the usb connection it works great. I have added M552 I1 S1 to my config.g file (actually I use the ooznest DWC so it's the config-network.g file but I tried both), the wifi module never starts by itself.
When I connect to usb to check the status of the module it directly spits out this error:Error: failed to initialise WiFi module: unknown response code
M552 I1 says that the wifi module is disabled, and it starts fine when I send M552 I1 S1 by hand.
I have tried Beta 4 and Beta3 of the Wifi module firmware and had the same issue with both. I have also disabled the Ethernet interface as I've seen it was recommended in other posts here but I haven't found a way to start wifi automatically yet.
I would very much appreciate your help!
S.
-
I have just tried inserting a pause in the config file before enabling wifi and found by trial and error that pausing for 500ms will let enough time for the Wifi module to warmup and be able to be activated without error by the Duet. In the config file it looks like this:
G4 P500 ; wait for 500 milliseconds for the Wifi module to warm up M552 I1 S1 ; Then enable Wifi
This seems to work fine, however I haven't seen this documented anywhere. Is there a real fix for that? Shouldn't the Duet 3 Know about the Wifi board limitation and do the waiting by itself if needed?
Cheers!
S.
-
What is your main firmware version on the Duet 3?
-
@Phaedrux I just checked and here is what I have:
- Board: Duet 3 MB6HC (MB6HC)
- Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.4+1 (2022-11-15)
- System Settings Version: 1.2
-
@meeloo please upgrade to 3.4.6. There were some fixes for the wifi module
-
@Phaedrux I have updgraded the firmware to check and it still have the issue.
What I have now:- Board: Duet 3 MB6HC (MB6HC)
- Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.6 (2023-07-21)
- System Settings Version: 1.2
-
I second the fix, my module has always had the same issue, I gave up on it awhile back and just waited hoping each firmware upgrade would solve it. I just did the latest upgrade to 3.5.0 rc1. still didn't resolve it- continued trouble shooting and ran across this thread- tried the 500ms pause and it works flawless!!! Thanks