Can't get DWC to show up in browser
-
Duet2 WiFi board, connect with YAT via USB, firmware version reported is 3.3, shows wifi module active and connected to my network with IP address 192.168.0.176. The blue light on the wifi module is on. All the same before and after board and router reboots.
I check router- it shows the connection to the Duet board at 192.168.0.176. I reboot router- reconnects at same IP address.
I go to web browser and enter 192.168.0.176 and it says "site can't be reached, took too long to respond"
I try to ping 192.168.0.176 and all requests time out.
Config file:
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up; General preferences
G90 ; send absolute coordinates...
M550 P"Arrakis" ; set device name
M669 K1 ; select CoreXY mode; Network
M551 P"dune" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P5 S1 R0 T4.0:5.0:6.0:12.0 ; drive 5 reverse, lo enable, timing parameters for servomotors
M569 P6 S1 R0 T4.0:5.0:6.0:12.0 ; drive 6 reverse, lo enable, timing parameters for servomotors
M584 X5 Y6 ; set drive mapping- X at drive 5, Y at drive 6
M350 X1 Y1 ; configure microstepping without interpolation
M92 X31.25 Y31.25 ; set steps per mm
M566 X3000.00 Y3000.00 ; set maximum instantaneous speed changes (mm/min)
M203 X96000.00 Y96000.00 ; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 ; set accelerations (mm/s^2)
M84 S3 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X590 Y980 S0 ; set axis maxima; Endstops
M574 X2 S1 P"!xstop" ; configure active-high endstop for high end on X via pin zstop
M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z0; macro to run at power up- wifi will not work until this file is finished
; M98 P/macros/BVGN22Any suggestions?
Thanks!
-
What does M122 say about the wifi module?
Can you try setting up the Duet in access point mode to see if the module itself is still working correctly?
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m589-configure-access-point-parameters
-
@Phaedrux Here's the M122 result from YAT:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JTD2-3S86P-KA7LL
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73860 of which 28 recycled
Never used RAM 16652, free system stack 164 words
Tasks: NETWORK(ready,13.3%,417) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,86.6%,519) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:22:41 ago, cause: power up
Last software reset at 2022-07-21 23:28, reason: User, GCodes spinning, available RAM 13620, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 17.5, current 26.6, max 27.2
Supply voltage: min 0.2, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 3.41ms; fastest: 0.12ms
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 2.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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.
=== Network ===
Slowest loop: 15.55ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:e3:14:57
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24616
WiFi IP address 192.168.0.176
WiFi signal strength -53dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
I'll try access point setup...
- WiFi -
-
Could also try a fresh SD card.
-
????
-
I just tried backing up the card and it's taking forever to read it. Maybe that's the problem...
It's getting late- I'll try again tomorrow morning.Thanks!
-
I went through 3 cards before I found one that was working right. That fixed it. Thanks!
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
