Wifi module disabled - start timed out
-
This Duet 2 Wifi came with a Modix Printer I am trying to construct. I've been unable to get the wifi module to work. I would like to get it set up in access point mode so that I can access the web interface.
I've run an m122 with the result below.
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9X6JA-JUNSN-6JTDJ-3S46J-T9QMV
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 76044 of which 0 recycled
Never used RAM 9344, free system stack 192 words
Tasks: NETWORK(ready,7.4%,458) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,92.5%,452) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:14:07 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 9272, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 24.6, current 31.0, max 31.4
Supply voltage: min 0.5, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/136/4, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: ok, SG min n/a
Driver 6: ok, SG min n/a
Driver 7: ok, SG min n/a
Driver 8: ok, SG min n/a
Driver 9: ok, SG min n/a
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 99.82ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 9.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== DueX ===
Read count 1, 0.07 reads/min
=== Network ===
Slowest loop: 1.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok -
@ZekeAtWork What happens when you follow the instructions here: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet
Please show the commands you are sending, and the response the Duet returns. You can copy and paste the text from YAT (or any other serial terminal you use) into you reply, which is preferable to screen shots.Ian
-
Thank you for the quick response!
I followed this guide to get the USB connection and YAT set up.
I ran the codes in the guide up through "Configure network SSID and password" below.
WiFi module disabled - start timed out
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet WiFi 1.02 or later + DueX5v0.11 FIRMWARE_DATE: 2022-11-30 19:36:12
ok
m552 s-1
ok
m552
WiFi module is disabled
ok
m552 s0
ok
WiFi module disabled - start timed out
m552
WiFi module is disabled
ok
m587
Failed to retrieve network list: WiFi module is disabled
ok -
What does it say if you send M552 S1? Or M997 S1?
-
@Phaedrux The following is a copy of the whole terminal output from startup.
WiFi module disabled - start timed out
m552 s-1
ok
m552 s0
ok
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
WiFi module disabled - start timed out
m997 s1
T0:20.9 /0.0
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
okAdditionally, the config files were provided by Modix and are more complex than those I have seen from others on this forum. It's not impossible that there are issues there. I haven't tried using the config files from the configurator on this website as I don't know if it could cause issues with the components that are already installed and wired in if the startup sequence specified in the Modix files is not followed.
-
@ZekeAtWork try M997 S1 after sending M552 S0
-
@jay_s_uk looks like the same
WiFi module disabled - start timed out
m552 s0
ok
WiFi module disabled - start timed out
m997 s1
T0:21.0 /0.0
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
okI may not have waited quite long enough after the m552 s0 to get the WiFi module disabled response in the previous message
-
@ZekeAtWork thats not looking great for the board then. wait for @Phaedrux to respond
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
Understood, thank you!
Is it generally possible to run everything from the touchscreen while we get the wifi module sorted out or are there some things that can only be done via the web interface?
-
uploading gcode files without the network connection is problematic. The PanelDue requires the ribbon cable to be able to use the SD card slot on it, but due to length limits of the ribbon cable the Modix printer may be using the 4-wire PanelDue cable instead.
-
@Phaedrux It looks like that is correct. The panel just has a smaller plug with 4 wires going into it. And the ribbon cable on the Duet is only connected over to a second, different board. I guess the 4-wire PanelDue cable doesn't have a high enough transfer rate to be able to upload printable gcode files?
-
@ZekeAtWork said in Wifi module disabled - start timed out:
doesn't have a high enough transfer rate to be able to upload printable gcode files?
It lacks the pins needed for the SD card.
-
Alright, thank you all for the help. I'll work on opening a support ticket with the supplier and see if they can get this resolved!
-
@ZekeAtWork You could wire an external SD card direct to the Duet mainboard on a short ribbon cable, and wire it so it is accessible, maybe? See https://forum.duet3d.com/topic/7406/external-sd-card-reader-with-duetwifi
Ian
-
@droftarts That would be convenient! I would only be concerned about installing plugins, which the instructions I have from our printer supplier only show how to install using the web interface. Also, I am not sure about the wiring details, especially considering there is a second board connected with a ribbon cable already. The CONN_SD and EXP_ALT pins are available though.
That said, is it possible to load files using the existing SD card? That wouldn't be too inconvenient for our setup, at least as a temporary measure.
-
@Phaedrux said in Wifi module disabled - start timed out:
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
Just wondering if you have sent the warranty email yet?
-
@Phaedrux I have not sent a warranty email yet, I've just sent one to the reseller so far to see if they have a fix or if they will replace the module. Would it be better to start the warranty claim in addition to trying to work with the supplier to resolve the issue?
-
Based on the mode of failure I think a board replacement is in your future, no sense in delaying it.
-
Ok, I will get that started as well, then! Thank you for the help
