Duet 2 Wifi Always Disconnects from Wifi and PanelDue
-
Update:
I decided to send M552 S1 to the printer via YAT and then the printer showed up on my wireless network.
But still cannot access the Duet using DWC.
I sent M552 S0 and the blue LED next to the wifi module turned off.
I sent M552 S1 and the LED flashed and then stayed on.
Still cannot access the Duet board. -
@Quadcells Try M552 S-1 (disables Wifi module), then M552 S1. But I think it's unlikely to work, as it seems like all comms are not working. It would be really good to get an M122 report as soon as you can!
Ian
-
Hi, Well I could not feed the filament through and it paused and no way to resume.
Funny how "STOP" worked on the paneldue and nothing else. As soon as I hit Stop connection to YAT started to work.
M155 returned - Firmware ver: 2.05.1 Electronics: Duet Wifi 1.02 + DueX5 Firmware_date: 2020-02-09b1
M122 returned:Bill Tortorello billtortorello@gmail.com
12:01 PM (0 minutes ago)
to me=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5<LF>Board ID: 08DGM-9T6BU-FG3S0-7J1F0-3S86R-KA5VF<LF>Used output buffers: 1 of 24 (15 max)<LF>=== RTOS ===<LF>Static ram: 25712<LF>Dynamic ram: 95072 of which 0 recycled<LF>Exception stack ram used: 320<LF>Never used ram: 9968<LF>Tasks: NETWORK(ready,1440) DHTSENSOR(blocked,228) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3740) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:10:07 ago, cause: software<LF>Last software reset at 2020-09-24 11:48, reason: User, spinning module GCodes, available RAM 9744 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 35.5, current 35.8, max 36.0<LF>Supply voltage: min 24.1, current 24.2, max 24.3, un[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]
-
Can you change the line ending setting in YAT so that we can see the full report?
-
Hi,
M122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3S0-7J1F0-3S86R-KA5VF
Used output buffers: 1 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 95072 of which 0 recycled
Exception stack ram used: 320
Never used ram: 9968
Tasks: NETWORK(ready,1440) DHTSENSOR(blocked,228) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3740) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:10:07 ago, cause: software
Last software reset at 2020-09-24 11:48, reason: User, spinning module GCodes, available RAM 9744 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.5, current 35.8, max 36.0
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 1826154892
Slowest loop: 4.13ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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 ready with "M122" 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: 202.15ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address 84:f3:eb:42:ad:1b
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25696
WiFi IP address 192.168.39.129
WiFi signal strength -42dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: ok
- WiFi -
-
Thanks. Since you're running a Duex I have to ask if it's wired to spec as lockups like this can happen when the ground cable isn't wired as shown here: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
-
@Phaedrux is this wrong?
-
I can't really see with your wire sheaths on, but does it look like this?
-
@Phaedrux no, mine has the wires from the power supply going to the Duex5 then to the Duet wifi.
-
@Quadcells Wasn't there another thread about your power/GND wiring? I think we ended up thinking it was okay.
Ian
-
@droftarts that wasn't me, but if the gnd resistance from the Duet to the duex5 then what I have should be fine especially the same thing happens to my delta which only has a Duet.
-
Is there something in your network environment that could be causing the disruption?
-
Not sure what would do that. We have a mesh network. One of the 3 mesh points is 3 meters away from the printer. I have 2 wireless printers, cell phones, tablets, wifi cams (Wyze and Eufy), laptops, wifi printer, Amazon Alexa.
Can’t think of anything else./quadcells
-
-
very interesting read there. Well we have 4 flat screen TV's. Two are Smart and two are not. All on satellite, got rid of cable years ago when my local telephone company installed fiber optics for phone and internet. Not running any old crt tv's. I had a situation at my house about 10 years ago that every time my boiler would about to start all our TV's would flip out with noise and these were on cable. The problem wouldn't go away until we replaced the boiler with a new one(old one split open one day).
With all that said I did start a new print with a fresh roll of filament so not to run out this time. At the moment the print is 14hrs 52min in and 8hrs left. I still can access the duet with DWC and the Paneldue is still connected. I know that all the tv's have been switch on and off during the print. The only thing different this time is that I still have the duet USB connected to the laptop running YAT./quadcells
-
@Quadcells does your mesh network show as one network (combined 2.4 and 5ghz), or as two with one for each of 2.4 and 5ghz? There has been problems connecting to single, shared band networks, and also some routers (but they don’t connect at all). Have the Duets always disconnected? Or since some specific change? If you’ve got an old 2.4Ghz access point, you could set it up for the printers and see if it still does the same thing, to rule out network issues.
With your print, the Duet seemed to be accepting commands over USB, even if it wasn’t responding. Did you try resuming the print before stopping?
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@Quadcells said in Duet 2 Wifi Always Disconnects from Wifi and PanelDue:
The only thing different this time is that I still have the duet USB connected to the laptop running YAT.
That’s interesting. It’s possible something got sent on USB, but without a response the comms hung. Has it sent anything yet?Maybe turn debug on too, though this can slow printing down.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts said in Duet 2 Wifi Always Disconnects from Wifi and PanelDue:
@Quadcells does your mesh network show as one network (combined 2.4 and 5ghz), or as two with one for each of 2.4 and 5ghz? There has been problems connecting to single, shared band networks, and also some routers (but they don’t connect at all). Have the Duets always disconnected? Or since some specific change? If you’ve got an old 2.4Ghz access point, you could set it up for the printers and see if it still does the same thing, to rule out network issues.
With your print, the Duet seemed to be accepting commands over USB, even if it wasn’t responding. Did you try resuming the print before stopping?
Ian
My mesh shows as one (2.4ghz and 5ghz). I have this installed for since May 2019. I really don't think this problem started then. Pretty sure it started about 6-8 months ago, but time has been flying by for me the past few years has I been so busy.
I don't have an old 2.4ghz access point to try. -
@droftarts said in Duet 2 Wifi Always Disconnects from Wifi and PanelDue:
@Quadcells said in Duet 2 Wifi Always Disconnects from Wifi and PanelDue:
The only thing different this time is that I still have the duet USB connected to the laptop running YAT.
That’s interesting. It’s possible something got sent on USB, but without a response the comms hung. Has it sent anything yet?Maybe turn debug on too, though this can slow printing down.
Ian
No it has not sent anything to YAT over the USB.
-
@droftarts are there any mesh systems that have separate 2.4ghz and 5ghz. I have only seen them as a combine. I would be willing to change if that is the problem as I would save time and money in the long run. My old Linksys wireless router had them as separate networks but I had terrible coverage with it.
