Is this a bug? Wifi crashes when adjusting Z axis offset

EyeQ45 · 20 Nov 2020, 08:25

Hi

I've noticed I lose Wifi signal when I micro adjust the Z axis offset during a cutting program on my Duet 2. I'm in the test stage of my build and getting to know how the system and software works, so curious to know if it's a bug, caused by the data interrupt when asking for the micro adjustments while it's in a process, or just a wifi thing?

I can more or less get away with a single click of 0.5 mm either up or down, but when I try and add more the crash potential increases.

I'm using my mobile phone as a hotspot all within 3 metres of the machine and laptop, the connection is stable the rest of the time.

Cheers

Phil

jay_s_uk · 20 Nov 2020, 08:31

that shouldn't be happening.
What version of RRF are you running?
Can you post the output of M115 for the firmware?
Also, when it does crash, can you get the output of M122 when it reconnects?

EyeQ45 · 20 Nov 2020, 09:36

Actually it's started to go a bit odd regardless of any inputs. Here's the response from M115

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2

Here's M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85T0-6JKFD-3S86T-TBS7P
Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93304 of which 0 recycled
Exception stack ram used: 268
Never used ram: 11820
Tasks: NETWORK(ready,924) HEAT(blocked,1236) MAIN(running,4100) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:03:21 ago, cause: software
Last software reset at 2020-11-20 09:31, reason: Heat task stuck, spinning module GCodes, available RAM 11428 bytes (slot 2)
Software reset code 0x00a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200049a4 Task 0x4e49414d
Stack: 00446abf 0043aa96 81000000 00000000 00000000 00000000 00000000 3331bb4c 40000000 3f317200 b5ddea0e 388aa908 bb35fe81 3c4192f5 00000000 00000000 3f800000 00000000 00000000 60000010 0043aa9b 00000000 00000fe8
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 11.5, current 12.1, max 12.2
Supply voltage: min 24.0, current 24.1, 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
Date/time: 2020-11-20 09:35:07
Cache data hit count 789966599
Slowest loop: 2.09ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, 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 = -1 -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: 15.55ms; 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.23
WiFi MAC address bc:dd:c2:2d:a1:28
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24120
WiFi IP address 192.168.43.81
WiFi signal strength -62dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk · 20 Nov 2020, 09:42

i would start of by upgrading to 2.05.1
your release is pretty old. https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1
I would also read through the upgrade notes incase there is anything you need to change

EyeQ45 · 20 Nov 2020, 09:45

Okay, thanks for your help and prompt reply. I'll post back with any issues.