Cannot re-access to DWC, after I close my explorer window.
-
Hello,
I have a duet wifi 2, configured on Wifi host mode.
Whenever I close my Explorer window, or my pc goes to sleep mode, I cannot access to DWC. So, when I start printing and my pc goes to sleep mode some hours later, I am not able to do anything during the print, besides wait to end.
On my previous, duet I did not have this issue. Where do I start??
Router configuration or config.g ???PS, I did change m586 telnet and ftp command from disabled to enabled, but it didnt make any difference
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Feb 21 2022 20:39:43 GMT+0200 (Eastern European Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Print Machine" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S1 ; enable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.160 Y80 Z401.2 E159.73 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z600.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.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 Y0 Z0 S1 ; set axis minima
M208 X245 Y245 Z240 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-47 Y-15 Z3.15 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; 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
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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S10 Y"mcu-temp" A"MCU" ; defines sensor 10 as MCU temperature sensor
M308 S11 Y"drivers" A"Duet stepper drivers" ; defines sensor 11 as stepper driver temperature sensor; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 ; set fan 0 value.
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 H1 S1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q100 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H10:11 T40:70 ; set fan 2 value; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X-15 Y-15 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
m501
-
I use Advanced IP Scanner to scan my network, a good tool to have.
-
@tecno so, this is the solution???
-
@cozyp said in Cannot re-access to DWC, after I close my explorer window.:
I have a duet wifi 2, configured on Wifi host mode.
What do you mean by wifi host mode? Are you having the Duet create a wifi network that your connect to with your PC? Or are you connecting the Duet to a wifi router?
What URL are you using to connect to the Duet with?
Can you send M122 and post the results here?
-
@phaedrux I am using duet to connect to wifi modem. I experience the abovementioned issues.
This is my 122 command
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0rc1 (2022-02-09 10:26:56) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SN-6J1F0-3SD6M-1VTZL
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23852
Dynamic ram: 74120 of which 0 recycled
Never used RAM 14108, free system stack 184 words
Tasks: NETWORK(ready,12.4%,243) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,364) MAIN(running,87.2%,442) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:30 ago, cause: power up
Last software reset at 2022-06-06 16:01, reason: User, GCodes spinning, available RAM 14036, 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
Step timer max interval 0
MCU temperature: min 37.9, current 41.7, max 41.9
Supply voltage: min 24.3, current 24.4, max 24.6, 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: pos 0, standstill, SG min n/a
Driver 1: pos 0, standstill, SG min n/a
Driver 2: pos 0, standstill, SG min n/a
Driver 3: pos 0, standstill, SG min n/a
Driver 4: pos 0, standstill, SG min n/a
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2022-07-08 19:31:42
Cache data hit count 4294967295
Slowest loop: 8.51ms; fastest: 0.18ms
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 5.9ms, 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 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
Code queue is empty
=== Network ===
Slowest loop: 81.19ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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 8c:aa:b5:50:6a:55
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 20600
WiFi IP address 192.168.2.6
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
- WiFi -
-
@cozyp said in Cannot re-access to DWC, after I close my explorer window.:
3.4.0rc1
Can you try a complete firmware update?
In DWC upload this zip file as is.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1/Duet2and3Firmware-3.4.1.zip
-
I installed the newest firmware as you suggested.
The motherboard performed a restart upon finish.I cannot connect to DWC after the restart, although motherboard is connected to wifi ( blue light is on, NOT flashing ).
Seems that this issue is not over yet. Don't know where to start from, router or duet??
-
It sounds like the wifi module didn't flash correctly. You can connect via USB terminal and send M997 S1 to manually reflash it. That should do it.
You can also send M115 to check that the main firmware version is now up to date.
-
No change at all. For example, I connected to dwc via my laptop. I shut the laptop down, DUET stays on, then I try to connect to DWC via my PC.
This happens every time I shut my explorer window down. Now, I used my laptop browser, shut it down, then re-opened it from my PC. There is a conflict somehow and I don't know if it is Duet hardware or router wifi relatedConnection error.
Should I just change the connection type of duet to broadcast?? I mean, no need to connect to router, be independent network.Would that act as a solution??
-
That would be a good means of testing the wifi module anyway.
Do you have another computer to test with?
-
also, if I simultaneously try to open DWC from my laptop, while I am on DWC from my PC, there is conflict, laptop cannot access to DWC.
let me know your thoughts
-
@Phaedrux same thing happens on access from phone
-
Can you show a screenshot of your DWC settings page?
-
-
Can you try configuring it in access point mode and see if it behaves differently?
https://docs.duet3d.com/User_manual/Reference/Gcodes#m589-configure-access-point-parameters
