@deckingman Yes, I wonder what would cause this error to appear. I will update the firmware and if it happens again ill post the G-code along with it

@jay_s_uk I'm going to do that thanks. Do you know if a specific problem before that version that would have caused such problem ?

Hello everyone,

Last night I tried a 12h print on my duet 2 Wifi and for not apparent reason it just stoped.
I’v reformatted the SD card and ran the SD card test provided and the wiki but no errors was found.
If someone has an idea and could help that would be greatly appreciated, I'v tried looking online but haven't found any meaningful help.

Printer info:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)

Here's the M122 output after the crash (I was sleeping during it):

=== RTOS ===
Static ram: 27980
Dynamic ram: 93952 of which 24 recycled
Exception stack ram used: 304
Never used ram: 8812
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 06:44:46 ago, cause: software
Last software reset at 2021-09-05 03:22, reason: Stuck in spin loop, spinning module GCodes, available RAM 8452 bytes (slot 3)
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200051f4 Task MAIN
Stack: 00457b03 0045b488 61030200 3f000000 3e49ba00 3edb6db7 b7b4d800 49742400 44fa0000 447a0000 447a0000 
Error status: 0
MCU temperature: min 50.5, current 51.0, max 57.6
Supply voltage: min 23.9, current 24.0, max 24.1, 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: 2021-09-05 10:07:31
Cache data hit count 4294967295
Slowest loop: 356.64ms; fastest: 0.12ms
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 52.5ms, write time 0.0ms, max retries 4
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.69ms; fastest: 0.00ms
Responder states: HTTP(2) 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.23
WiFi MAC address b4:e6:2d:60:31:f9
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 20224
WiFi IP address 192.168.1.65
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 4 0 0 0 0 0 0"

console.csv

Thank you

@exerqtor I can get it to deploy and work but some time the probe extends two times and other times it does not trigger when colliding with the bed

Video on imgur

@Veti @dc42 @bearer Thank you very mutch for you help I have found my error It is sad sorry

@veti
I'v switched the yellow and blue wires,
with and without the resistor between blue and black wire as well
still blue led and nothing

@bearer The probe deploys and retracts a few times at boot and then has a steady blue light

Hi, yes here it is

Imgur album

Still nothing
I wonder if the probe being able to self test at boot but not deploying it manually shows that its either my wiring or an error in the config?

Here are the product info if it might help:
Solenoid Push-pin Up servo signal 90Degree(ex : M280 P0 S90 )
Solenoid Push-pin Down servo signal 10Degree(ex : M280 P0 S10 )
Manual Self-test servo signal 120Degree(ex : M280 P0 S120)
Alarm Release servo signal 160Degree(ex : M280 P0 S160)

3D printer z-probe Touch can be operated in the following condition.

• One I/O (PWM or Software PWM) for control
• One I/O for Zmin
• GND and +5V power
  If you use this on an Anet A8 then you need to cross over the YELLOW & BLUE wires. Couldn't figure out why it wouldn't work until I read the head unit. The Yellow is the endstop and the Blue is the pwm input, I just cut them and reversed them

Thanks

Hi veti,
here it is:

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Sat May 11 2019 10:43:23 GMT+0200 (Central European Summer Time)
M280 P7 S10 I1