Connecting duet wifi 2
-
@hellpilot said in Connecting duet wifi 2:
Is this because local network access is restricted on guest networks?
I would say yes
Have you followed this Docu : https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s9
If Yes can you see your 2.4 GHZ network with
If you get an error, check the network SSID and password you entered with the M587 command. Make sure that the WiFi is in idle mode before sending M587, with M552 S0. Send M587 to get a list of remembered networks, though this does not show the password. -
@siam I have followed that documentation. I've cleared all remembered networks, so that M587 only shows the 2.4 GHZ network that my duet cannot establish a connection with. Under my router interface "Espressif Inc" will make a connection for about 3 seconds before reattempting.
-
@hellpilot you make it not easy for me
did you allow new connections on your WLAN (some router have this setting disabled) -
@siam I'd like to make it easy!
I believe there are no restrictions. Other devices can connect with ease. -
@hellpilot Can you try to restart your Router and Your Printer and after this, post the result from M122
-
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet
version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02
or later<LF>Board ID: 08DJM-9178L-L2MS8-6JKDA-3S86K-K8G2N<LF>Used
output buffers: 1 of 24 (13 max)<LF>=== RTOS ===<LF>Static ram: 23
876<LF>Dynamic ram: 75352 of which 0 recycled<LF>Never used RAM 15
188, free system stack 185 words<LF>Tasks: NETWORK(ready,6.7%,3
40) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(r
unning,93.2%,439) IDLE(ready,0.0%,29), total 100.0%<LF>Owned mu
texes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:02:32 ago, c
ause: power up<LF>Last software reset at 2021-09-19 13:42, reas
on: User, GCodes spinning, available RAM 12332, slot 1<LF>Softw
are reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0
x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0
n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max inte
rval 0<LF>MCU temperature: min 31.4, current 32.2, max 34.7<LF>Sup
ply voltage: min 0.4, current 0.5, max 0.6, under voltage ev
ents: 0, over voltage events: 0, power good: no<LF>Heap OK, han
dles allocated/used 0/0, heap memory allocated/used/recyclab
le 0/0/0, gc cycles 0<LF>Driver 0: position 0, ok, SG min/max n
ot available<LF>Driver 1: position 0, ok, SG min/max not availa
ble<LF>Driver 2: position 0, ok, SG min/max not available<LF>Drive
r 3: position 0, ok, SG min/max not available<LF>Driver 4: posi
tion 0, ok, SG min/max not available<LF>Driver 5: position 0<LF>Dr
iver 6: position 0<LF>Driver 7: position 0<LF>Driver 8: position 0
<LF>Driver 9: position 0<LF>Driver 10: position 0<LF>Driver 11: posit
ion 0<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 42
94967295<LF>Slowest loop: 3.00ms; fastest: 0.12ms<LF>I2C nak error
s 0, send timeouts 0, receive timeouts 0, finishTimeouts 0,
resets 0<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 det
ected, interface speed: 20.0MBytes/sec<LF>SD card longest read
time 0.4ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs
created 83, maxWait 0ms, bed compensation in use: none, com
p offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, comple
ted moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns
[0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves
0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, U
nderruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters =
0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1<LF>=== GCodes ===<LF>Seg
ments left: 0<LF>Movement lock held by null<LF>HTTP is idle in sta
te(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s
) 0<LF>USB is ready with "m122" in state(s) 0<LF>Aux is idle in st
ate(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in stat
e(s) 0<LF>LCD is idle in state(s) 0<LF>Daemon is idle in state(s)
0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== N
etwork ===<LF>Slowest loop: 0.61ms; fastest: 0.00ms<LF>Responder s
tates: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 s
essions<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is chan
gingMode<LF>WiFi module is trying to connect<LF>Failed messages: p
ending 0, notready 0, noresp 0<LF>WiFi firmware version 1.26<LF>Wi
Fi MAC address ec:fa:bc:5b:42:ca<LF>WiFi Vcc 3.35, reset reason
Turned on by main processor<LF>WiFi flash size 4194304, free h
eap 28776<LF>Clock register 00002002<LF>Socket states: 0 0 0 0 0 0
0 0<LF>ok<LF>WiFi reported error: Wrong password while trying to
connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi reported err
or: Wrong password while trying to connect to WuTangLan24<LF>Wi
Fi module is idle<LF>WiFi reported error: Wrong password while
trying to connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi re
ported error: Wrong password while trying to connect to WuTa
ngLan24<LF>WiFi module is idle<LF>WiFi reported error: Wrong passw
ord while trying to connect to WuTangLan24<LF>WiFi module is id
le<LF>WiFi reported error: Wrong password while trying to conne
ct to WuTangLan24<LF>WiFi module is idle<LF>WiFi reported error: W
rong password while trying to connect to WuTangLan24<LF>WiFi mo
dule is idle<LF>WiFi reported error: Wrong password while tryin
g to connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi reporte
d error: Wrong password while trying to connect to WuTangLan
24<LF>WiFi module is idle<LF> -
@hellpilot are you really sure that you use the correct password? Did you use in your password, maybe special chars?
-
@siam 100%. Even changed it briefly to something simple.
Connections to my guest network have no issue, however. Just cannot connect to the web interface after that. -
@hellpilot said in Connecting duet wifi 2:
100%. Even changed it briefly to something simple.
Connections to my guest network have no issue, however. Just cannot connect to the web interface after that.That is what i'm not understand ... did you use the same encoding (wpa2 ) in your guest account as in your closed wifi (in my router I can set here different settings)?
-
@siam Yeah I changed it all to WPA2 after issues with WPA3.
-
Here is the terminal after connecting to my guest network. IP Address does not pull up the web interface.
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 20
WiFi: cnt
WiFi:
WiFi: connected with WuTangGuest, channel 9
WiFi: dhcp client start...
WiFi: wifi evt: 0
WiFi: ip:192.168.50.167,mask:255.255.255.0,gw:192.168.50.1
WiFi module is connected to access point WuTangGuest, IP add
ress 192.168.50.167
WiFi: wifi evt: 3
WiFi: pm open,type:2 0
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 20
WiFi: cnt
WiFi:
WiFi: connected with WuTangGuest, channel 9
WiFi: dhcp client start...
WiFi: wifi evt: 0
WiFi: ip:192.168.50.167,mask:255.255.255.0,gw:192.168.50.1
WiFi module is connected to access point WuTangGuest, IP add
ress 192.168.50.167
WiFi: wifi evt: 3
WiFi: pm open,type:2 0 -
@hellpilot Is there a difference between your WuTangGuest and your WuTangLan network (maybe wutanguest without password? Another ip-Adress range?)
Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
Duet WiFi 1.02 or later + DueX5
RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
Duet WiFi Server: 1.26
Duet Web Control 3.4.0beta4 (2021-09-27) -
@hellpilot are you trying to access the printer from an IP outside of the local network range of the guest network ? i.e. the machine you are connecting from should by 192.168.50.nnn try that.
-
@t3p3tony Looks like all the IPs im using are 192.168.50.nnn or .nn
-
@siam I don't see any major differences. Intranet access is disabled on my guest network. But changing it doesn't seem to have effect.
-
@hellpilot can you ping the Duet from your machine?
(thanks @SIam)!
-
@t3p3tony said in Connecting duet wifi 2:
cn you pin the Duet from your machine?
translated: can you ping your machine
-
@hellpilot said in Connecting duet wifi 2:
@siam I don't see any major differences. Intranet access is disabled on my guest network. But changing it doesn't seem to have effect.
I'm not sure that this will help, but this is the last idea I have.
Remove all known networks (M588) then reflash your duet board (M997) and after this try to add your wifi againHypercube-Evolution-Hybrid, Piezo Orion, Orbiter
Duet WiFi 1.02 or later + DueX5
RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
Duet WiFi Server: 1.26
Duet Web Control 3.4.0beta4 (2021-09-27) -
@hellpilot and the other related question from me is what is the IP you are trying to connect from.
-
Awh no luck with this method of reflash of M588. Even reinstalled firmware. Interesting enough I changed my main 2.4 network to enable WPS. I no longer get "Failed while trying to connect to WuTangLan24", it is now "Wrong password while trying to connect to WuTangLan24".
I am not to sure what is meant by pinging?
