Can't Connect to Duet Web Interface
-
Hello, I am needing some help with trying to figure out what issue I have. I have a Duet 3 Mini 5 and I can't connect to the web interface. Below are my results. Strangely enough, my router shows an IP address but I get a refused to connect, I have searched for hours trying to figure this out and I am at a loss.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 0XLDH-W296U-D65J0-40KM6-MJ03Z-7G7VP
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 109516 of which 256 recycled
Never used RAM 28256, free system stack 150 words
Tasks: NETWORK(ready,6.8%,466) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,92.3%,281) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:36 ago, cause: software
Last software reset at 2022-01-23 14:52, reason: User, GCodes spinning, available RAM 34624, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 276296, completed 276296, timed out 0, errs 0
Step timer max interval 696
MCU temperature: min 27.7, current 29.4, max 29.6
Supply voltage: min 1.0, current 1.4, max 1.4, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 594729675
Slowest loop: 100.01ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.5ms, 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 0 -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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 2484, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1381/0/0
Tx timeouts 0,0,1380,0,0,1102 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1.31ms; 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 changingMode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address d8:bf:c0:15:09:5e
WiFi Vcc 3.36, reset reason Power up
WiFi flash size 2097152, free heap 27712
WiFi IP address 192.168.1.89
WiFi signal strength -72dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-06-01 21:07:06
ok
M997 s1
T0:-273.1 /0.0 B:-273.1 /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
ok - WiFi -
-
@jwebb4616 said in Can't Connect to Duet Web Interface:
192.168.1.89
Are you able to ping this IP address from your machine?
What is the IP address of the computer you're trying to use?
What IP are you trying to reach in your browser?
What error do you get there? -
@phaedrux I am able to ping it, see results below.
Pinging 192.168.1.89 with 32 bytes of data:
Reply from 192.168.1.89: bytes=32 time=3ms TTL=255
Reply from 192.168.1.89: bytes=32 time<1ms TTL=255
Reply from 192.168.1.89: bytes=32 time=1ms TTL=255
Reply from 192.168.1.89: bytes=32 time=1ms TTL=255I did finally get connected to the interface, by touching the top of the wifi module the page suddenly loaded when I was checking the antenna to make sure it was secure. After a bunch of testing every time I apply an update in UI, it reboots and then I can't connect until I touch the module again. I think there is a ground short or something in the chip.
I have emailed printed solid to get an exchange as its clearly hardware related.
-
@phaedrux They have responded asking me to provide a link to my post authorizing a return. Which I obviously don't have here yet so any help would be appreciated. When I touch, its not even really pressing down its like I am helping either reception or grounding. But I don't have to keep touching it in order for the web interface to keep working, only on the first load. super weird I know.
-
Yes that does sound like a problem with the module.
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.
