DWC no longer connects to my laptop
-
Previously I had no issues with wifi connections. I could connect to the DWC on my laptop or phone. I recently had my internet upgraded to ATT fiber, I connected to DWC for 2 prints, and then all of a sudden I get "err_timed_out" through the web browser. I kept the same SSID and password so all devices connected after the internet switch. I was running RRF 3.4.0 and Wifi firmware 1.26. After reading the forums, it was suggested to update, so I updated to 3.5.2 and 2.1.0, to no change. I attempted M554 and M589 and nothing worked.
My network is setup from ATT router, to google mesh. I can see on the google home app the printer IS connected to the 2.4 ghz wifi and when I stand close to the printer my phone connects to DWC. The printer now loses connection from the phone when I walk away but before I could be upstairs and still be connected. But no matter what, the laptop won't connect even if its close to the printer. I am not smart with router things. I assumed the new internet firewall was blocking the laptop from connecting but I couldn't figure that out.. Below I posted the M122.
8/3/2024, 8:44:01 AM M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet WiFi 1.02 or later Board ID: 08DGM-917DA-G4MSD-6JKD2-3S46N-TTVBB Used output buffers: 3 of 26 (14 max) === RTOS === Static ram: 23384 Dynamic ram: 73352 of which 12 recycled Never used RAM 16396, free system stack 184 words Tasks: NETWORK(2,nWait 6,13.3%,228) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,85.5%,750) IDLE(0,ready,1.1%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:01:29 ago, cause: power up Last software reset at 2024-02-05 18:42, reason: User, Gcodes spinning, available RAM 13120, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU temperature: min 22.1, current 26.5, max 26.8 Supply voltage: min 24.1, current 24.2, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-08-03 08:44:00 Cache data hit count 3192612722 Slowest loop: 14.74ms; fastest: 0.19ms 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 6.6ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === 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 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks 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 idle 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === check 0 clear 361099 Extruder 0: pos 2160.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 149.95ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1.0 MAC address xx:xx:xx:xx:xx:xx Module reset reason: Turned on by main processor, Vcc 3.36, flash size 4194304, free heap 34908 WiFi IP address xxx.xxx.xx.xx Signal strength -56dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
undefined Sgt G 294 marked this topic as a question
-
You might want to give ATT support a try on getting the device connected. It's odd that your phone can connect to DWC when close but not farther away.
-
Yeah it's just a weird problem because it connects to my phone just not the PC and it only happened when I upgraded internet
-
Does my networking section of the config.g file seem correct?
; Network M552 S1 ; connect to strongest network with known SSID M552 S1 P"mySSIDname" ; enable network M552 S2 P"mySSIDname" ; enable access point M554 Pipaddress M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet -
Perhaps you need to reset the saved wifi profiles on the printer.
In my config.g, I have the following:
; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable TelnetI created the following macro files:
Wifi - Clear All (clears all saved profiles from memory)
M588 S"*" G4 P1000 M587Wifi - Set (creates a profile entry in memory)
M552 S0 G4 P5000 M587 S"myssid" P"mywifipassword" G4 P1000 M587 M552 S1Wifi - Cycle (when I'm having connectivity issues, I can cycle the wifi and reconnect)
M552 S0 G4 P5000 M587 M552 S1 -
@Sgt-G-294 said in DWC no longer connects to my laptop:
Does my networking section of the config.g file seem correct?
; Network M552 S1 ; connect to strongest network with known SSID M552 S1 P"mySSIDname" ; enable network M552 S2 P"mySSIDname" ; enable access point M554 Pipaddress M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable TelnetIs this your current config.g? Because the last M552 command is setting up the Duet in Access Point mode, ie your phone is connecting direct to the Duet, rather than using your ATT network router. You should only need one M552 command, and it really depends how you want to connect. You can also remove the M554 command that sets the Gateway address, that should also be set by the DHCP server, and is unnecessary in Access Point mode.
Ian
-
Yeah thats in my config file, I'll remove the extra m552 and the m554 and give that shot 1st
-
@Sgt-G-294 It might be worth following the 'initial setup' guide to connect the Duet to your ATT WiFi, using a USB connection, delete saved SSIDs as @bLiTzJoN suggests with
M588 S"*", and add the SSID afresh. See https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_DuetAs you have the 2.1.0 WiFi firmware installed, you can do a scan for WiFi SSIDs. See M587.1 and M587.2.
It is odd that, though the last command sets up the Duet in Access Point mode, your M122 reports says it is connected to an access point. See if the above helps.
Ian
-
@droftarts I have unfortunately followed that many times and used the M588 without change. Maybe I should reflash the wifi firmware?
-
@Sgt-G-294 So currently to even connect to the phone, I still have to connect the PC to YAT and tell it M552 S0 then M552 S1 and then I can connect. As a band-aid, I added the below code at end of the networking in the config and this at least allows me to connect by not carrying the laptop downstairs every time.
M552 S0 G4 S2 M552 S1 -
@Sgt-G-294 Can't hurt to reflash. Now, it should be mentioned that I performed the incremental upgrade as noted which might be the issue here if you overlooked it.
-
I have found that it's very hard to maintain connection to the Duet board via wifi network if the computer I am using has VPN switched on.
