Duet disconnects

Phaedrux

That's right, the Duet won't be affected by the internet portion of the router at all.

Your signal strength is good, so that's not an issue.

Are there other devices that could be causing interference?

Are you in an apartment with congested wireless spectrum?

Have you rebooted the router?

GPetropoulos

@phaedrux said in Duet disconnects:

congested wireless spectrum

Not sure what congested wireless spectrum is.
My internet provider is a wireless internet service that transfers the internet signal via antennas through the air if that matters.

GPetropoulos

@phaedrux Also my router is next to my computer and that is 1.5meters away from the printer.

Phaedrux

Without knowing the exact details of your whole network I'm not sure what else to recommend at the moment. But you can try to identify a source of interference.

https://en.wikipedia.org/wiki/List_of_2.4_GHz_radio_use#Resolving_interference

In your case, with your internet provider being wireless itself, it's actually possible that it could be the source of interference. It might actually help to move your router out into a different room.

GPetropoulos

@phaedrux The provider signal hits an antenna on the roof of the building, 4floors higher, and then an ethernet cat6 cable brings it to the router. It is not wireless till the router.

Phaedrux

Ah I see. I thought it might be like one of those portable cellular wifi hotspots.

dc42

@gpetropoulos, what does the blue LED on the WiFi module do? After it connects the first time, does it remain solid blue, or does it flash?

If the problem is due to 2.4GHz interference from another device (e.g. cordless phone, baby monitor, microwave oven) then changing the router WiFi channel may help.

GPetropoulos

@dc42 I see the led of the wifi module staying stable blue even after disconnects.

dc42

@gpetropoulos said in Duet disconnects:

@dc42 I see the led of the wifi module staying stable blue even after disconnects.

That means the WiFi module thinks it is still connected to your router. So I suspect the problem is not with the Duet WiFi.

When the problem occurs, are you still able to ping the Duet from a PC? If so, does the ping fail after you turn the Duet off?

GPetropoulos

@dc42 I cannot manage to ping it as it reconnects immediately after it disconnects.

GPetropoulos

@dc42 This is what M122 gives after the last event.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6JKD4-3S06T-9YANF
Used output buffers: 3 of 20 (20 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98604 of which 0 recycled
Exception stack ram used: 384
Never used ram: 6560
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:03:16 ago, cause: software
Last software reset at 2019-01-07 01:09, reason: User, spinning module GCodes, available RAM 6600 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 4
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 8.3ms, max retries 0
MCU temperature: min 33.1, current 33.4, max 33.8
Supply voltage: min 24.1, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/252
Driver 1: standstill, SG min/max 0/229
Driver 2: standstill, SG min/max 0/140
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-01-07 01:12:34
Cache data hit count 728214923
Slowest loop: 35.97ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 230, MaxWait: 26033ms, Underruns: 0, 0
Scheduled moves: 74, completed moves: 74
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 56.46ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22beta1(30b14
WiFi MAC address b4:e6:2d:53:0a:f4
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28576
WiFi IP address 192.168.11.39
WiFi signal strength -44dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

dc42

I don't know what's causing the disconnects, but increasing the number of AJAX retries in the DWC user interface settings may be a workaround.

GPetropoulos

@dc42 I connected my pc via lan for now and it seems that the disconnects have been reduced greatly. I also increased the ajax number. I will continue to check on this and see if it appears again. Thank you.