@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
@droftarts I have unfortunately followed that many times and used the M588 without change. Maybe I should reflash the wifi firmware?
Yeah thats in my config file, I'll remove the extra m552 and the m554 and give that shot 1st
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
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
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
@jay_s_uk
Thanks for the quick reply! I'll try removing that
I have the Duet 2 Wifi and I just updated the Firmware to 3.5.2 and now at start up, I get an error in the Console "Error in start-up file macro line 84: Pause the print before attempting to cancel it". I'll post my config file below. Thanks in advance!
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.7 on Wed Jan 15 2020 19:00:04 GMT-0500 (Eastern Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender5" ; set printer name
; Network
M552 S1 ; connect to strongest network with known SSID
;M552 S1 P"mywifi" ; enable network
;M552 S2
; M554 PmyIP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X256 Y256 I0 ; configure microstepping without interpolation
M350 Z16 E16 I1 ; configure microstepping with interpolation
M92 X1254.21 Y1251.72 Z392.53 E483.27 ; set steps per mm
M566 X480.00 Y480.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z800.00 E3000.00 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
;M208 X0:225 Y0:205 Z0:300 ; set axis minima
M208 X-3:234 Y0:205 Z0:300 ; set axis minima
; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Filament Sensor
M591 D0 P3 C"e0stop" S1 R30:150 L24.84 E3.0 ; E0 endstop, D3D magnet sensor, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection length
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y-38 Z2.08 ; set Z probe trigger value, offset and trigger height
;M557 X20:225 Y0:167 S102.5:83.5 ; define mesh grid
M557 X10:225 Y0:167 P3 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
;M307 H1 R5.086 K0.545:0.000 D1.38 E1.35 S1.00 B0 V24.2 ; Heater Tune see config override
; Fans
M950 F1 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P1 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F0 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P0 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S19.8 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M0
T0
My printer ran fine with no issues for months and TONS of prints. Now I cannot get through a print without numerous errors.
My current M591 settings:
M591 D0 P3 C"e0stop" S1 R30:150 L24.84 E3.0
M591 D0 (during print):
Duet3D rotating magnet filament monitor v3 on pin e0stop, enabled, sensitivity 24.84mm/rev, allow 30% to 150%, check printing moves every 3.0mm, version 3, mag 131 agc 87, measured sensitivity 21.54mm/rev, min 87% max 105% over 786.1mm
M591 D0 (after error/pausing print):
Duet3D rotating magnet filament monitor v3 on pin e0stop, enabled, sensitivity 24.84mm/rev, allow 30% to 150%, check printing moves every 3.0mm, version 3, mag 132 agc 87, measured sensitivity 21.67mm/rev, min -1% max 106% over 1107.7mm
I have changed nothing on the printer and have been using the same filament. It shows I have Duet Web Control version 3.4.0
Thanks for your help!