Duet2 WiFi frequently disconnects when Paneldue 7i is connected

edsped

@edsped
M122 without duet connected, mid print

Derp
Status
Printing
Mode: FFF
Tool Position
X
126.6
Y
174.0
Z
52.80
U
0.0
Extruder Drives
Drive 0
391.5
Drive 1
17248.9
Drive 2
279.9
Drive 3
262.9
Speeds
Requested Speed
80.0 mm/s
Top Speed
52.2 mm/s
Sensors
Vin
24.3 V
MCU Temperature
35.4 °C
Z-Probe
0
Tools
Extra
Control Heaters
Tool Heater Current Active Standby
Amy
T0 - Load Filament Heater 1
standby 22.0 °C

Betty
T1 - Load Filament Heater 2
active 205.0 °C

Chloe
T2 - Load Filament Heater 3
standby 22.9 °C

Daisy
T3 - Load Filament Heater 4
standby 22.3 °C

Bed Heater 0
active 60.3 °C

Temperature Chart
11/19/2022, 11:27:52 AM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7J9FA-3S86K-1BABN
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 78684 of which 12 recycled
Never used RAM 8396, free system stack 98 words
Tasks: NETWORK(notifyWait,25.0%,199) HEAT(notifyWait,0.1%,308) Move(notifyWait,2.7%,282) DUEX(notifyWait,0.0%,24) MAIN(running,71.6%,421) IDLE(ready,0.6%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 04:33:49 ago, cause: power up
Last software reset at 2022-11-02 22:03, reason: User, GCodes spinning, available RAM 9940, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 34.6, current 35.3, max 35.9
Supply voltage: min 24.2, current 24.4, max 24.7, 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: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: ok, SG min 0
Driver 10:
Driver 11:
Date/time: 2022-11-19 11:27:58
Cache data hit count 4294967295
Slowest loop: 25.60ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.1ms, write time 3.8ms, max retries 0
=== Move ===
DMs created 83, segments created 47, maxWait 542ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 136346, completed 136321, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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
Heater 0 is on, I-accum = 0.2
Heater 2 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X173.706 Y125.667 E.02351" 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
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 99.93ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.27
WiFi MAC address f4:cf:a2:6e:7e:56
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22968
WiFi IP address 192.168.1.238
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
11/19/2022, 11:27:35 AM Connected to 192.168.1.238

edsped

@edsped
Did the no no and plugged it in mid print... With paneldue plugged in, meant to say without paneldue plugged in above.

Derp
Status
Printing
Mode: FFF
Tool Position
X
127.7
Y
134.4
Z
53.80
U
0.0
Extruder Drives
Drive 0
391.5
Drive 1
17366.2
Drive 2
279.9
Drive 3
262.9
Speeds
Requested Speed
40.0 mm/s
Top Speed
40.0 mm/s
Sensors
Vin
24.5 V
MCU Temperature
35.5 °C
Z-Probe
0
Tools
Extra
Control Heaters
Tool Heater Current Active Standby
Amy
T0 - Load Filament Heater 1
standby 22.0 °C

Betty
T1 - Load Filament Heater 2
active 204.9 °C

Chloe
T2 - Load Filament Heater 3
standby 22.9 °C

Daisy
T3 - Load Filament Heater 4
standby 22.3 °C

Bed Heater 0
active 60.0 °C

Temperature Chart
11/19/2022, 11:30:02 AM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7J9FA-3S86K-1BABN
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 78684 of which 12 recycled
Never used RAM 8396, free system stack 98 words
Tasks: NETWORK(ready,14.9%,199) HEAT(notifyWait,0.1%,308) Move(notifyWait,2.7%,282) DUEX(notifyWait,0.0%,24) MAIN(running,82.2%,421) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 04:35:58 ago, cause: power up
Last software reset at 2022-11-02 22:03, reason: User, GCodes spinning, available RAM 9940, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,2
Step timer max interval 0
MCU temperature: min 34.8, current 35.7, max 36.2
Supply voltage: min 24.2, current 24.5, max 24.8, 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: ok, SG min 0
Driver 1: stalled, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: ok, SG min 0
Driver 10:
Driver 11:
Date/time: 2022-11-19 11:30:07
Cache data hit count 4294967295
Slowest loop: 49.63ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 12.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 47, maxWait 540ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 138222, completed 138182, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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
Heater 0 is on, I-accum = 0.2
Heater 2 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X172.344 Y136.439 E.02028" 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
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 99.85ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 4
WiFi firmware version 1.27
WiFi MAC address f4:cf:a2:6e:7e:56
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22968
WiFi IP address 192.168.1.238
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

edsped

@edsped
Connectors and solder joint

https://imgur.com/MTTXe9Y

On a side note, I've been running this setup for a couple of years now and issue seems to have popped up in the past couple of months. At first I thought the wifi unit was faulty.

edsped

@edsped
https://imgur.com/7zawTmY

Phaedrux

I mean the soldering around the wifi module itself.

edsped

@edsped
Doh!!! Will have to do later as I don't want to try to rotate the printer mid print as it's pretty heavy. That being said if I disconnect the paneldue the disconnect issues go away. I've run for weeks without the paneldue without a single disconnect.

edsped

as soon as the paneldue is connected the disconnects start up again.

dc42

@edsped it could be that the enclosure that you have mounted the PanelDue in is pressing the touch screen and sending continuous commands. Please check that is not the cause, for example by loosening the mounting screws.

Another possibility is that the PanelDue cable is picking up a lot of interference, for example from an adjacent stepper motor cable. However, that seems unlikely if the problem occurs mostly at startup when the motors have (I presume) not been energised yet.

edsped

@dc42
I took the case off so the Paneldue is now sitting bare on a pile of napkins and am still getting the WiFi drops. I also switched from the 4 wire to a ribbon cable and the WiFi drops persist.

All that being said the drops pretty much only occur during G32. Once the print starts the connection stays solid. Not sure if it makes a difference but the consol on the paneldue doesn't show any issues. And disconnecting the paneldue eliminates the WiFi drops completely.

edsped

@dc42
As can be seen below, no disconnects once bed is leveled. I'm not going to go too crazy on this as I'm not sure how long it's been happening or if it's even worth chasing at this point as it's more of an annoyance and doesn't affect printing.

Phaedrux

What's in your bed.g? What kind of probe is it?

edsped

@Phaedrux
It's an omron switch, (Jubilee Printer)

I tried commenting out M558 as an experiment and it had no effect.

I'm not overly concerned and as far as I know it may have been happening for the past couple of years and I just never noticed but I don't believe that was the case.

M290 R0 S0 ; Reset baby stepping
M561 ; Disable any Mesh Bed Compensation
G91 ; Switch to relative positioning to drop the bed
G1 Z3 F700 ; Drop Bed 3mm
G90 ; Return to absolute positioning
G1 X150 Y150 F18000 ; Move to the center of the bed
M558 H3 A3 F100 T20000 ; Set the probing speed
G30

G30 P0 X290 Y290 Z-99999 ; probe near front left leadscrew
G30 P1 X10 Y290 Z-99999 ; probe near front right leadscrew
G30 P2 X152.5 Y10 Z-99999 S3 ; probe near back leadscrew and calibrate 3 motors

G1 X150 Y150 F18000 ;Move probe to center of bed
M558 H3 A3 F100 ; Set the probing speed
G30 ; Set Z = 0
G1 X0 Y0 Z4 F18000 ;Move probe home

Phaedrux

Just to test a theory, since it seems to only be a problem during the bed.g file, and it contains a bunch of probing moves, can you create a macro that has a similar amount of z axis moves and see if it can trigger the wifi issue?

That would indicate some noise being picked up from the Z steppers. Perhaps shielding or twisting/braiding the cables would help there.

edsped

@Phaedrux
Will do but probably Friday before I give it a go as I feel like I'm in the Griswold house at the moment.

dc42

@edsped As you have a DueX5 connected, one possibility is that a wire connected to an endstop input or a GPIO pin on the DueX5 is picking up noise. Whenever the state of a DueX input changes, an interrupt is generated and a task is activated to read the status change, and if this happens very frequently then it can starve the CPU. Are you using any inputs to the DueX5?

edsped

@dc42 A quick follow up to finish out this thread...

I very incorrectly assumed the issue was with the Duet board. I ended up moving to a Duet3 6HC with an RPi v4 SBC and upon connecting the PanelDue the same "connection interrupted" errors. At this point I'm going to assume there's some sort of issue with the PanelDue and will put it off to the side as I don't want to damage the 6HC board.

edsped

Just a quick addition…. The duet Wi-Fi and duet3 w/SBC are in two separate networks. WiFi was on a 2.4 GHz and SBC is on a 5GHz both managed by two separate ubiquiti UAP’s