[3.2-beta-3.2] Software reset after assertion doing Z probing



  • So I was trying to do a BLTouch quick mode (mode 5) mesh probe to later find out it's not supported when using a Toolboard, when I switched to normal mode and while probing Z at the beginning and the board resetted.

    Let me know if additional information is relevant:

    14/11/2020, 17:38:36	M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
    Board ID: 08DJM-956BA-NA3TN-6JKDL-3SS6K-9T92V
    Used output buffers: 2 of 40 (15 max)
    === RTOS ===
    Static ram: 122236
    Dynamic ram: 167964 of which 220 recycled
    Never used RAM 101772, free system stack 188 words
    Tasks: NETWORK(ready,195) ETHERNET(blocked,109) HEAT(blocked,318) CanReceiv(blocked,903) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,54) MAIN(running,1125) IDLE(ready,19)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:19 ago, cause: software
    Last software reset at 2020-11-14 17:37, reason: AssertionFailed, GCodes spinning, available RAM 101300, slot 1
    Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0x00000000 SP 0x2045fea4 Task NETW
    Stack: 00000193 00488688 00469673 00000200 00000400 a5a5a5a5 2043eab0 204233a0 20438118 00000001 20438090 204381b4 204381b0 2040a924 0046ea21 00000001 00433a0b 40020200 2045ff04 00000000 000000fa 00000000 0000000b 20438030 00000000 0000000c 00000000
    Error status: 0x00
    MCU temperature: min 39.5, current 39.8, max 40.0
    Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
    Driver 0: position 0, standstill, reads 32213, writes 15 timeouts 0, SG min/max 0/0
    Driver 1: position 0, standstill, reads 32217, writes 11 timeouts 0, SG min/max 0/0
    Driver 2: position 0, standstill, reads 32214, writes 15 timeouts 0, SG min/max 0/0
    Driver 3: position 0, standstill, reads 32219, writes 11 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 32217, writes 14 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 32218, writes 14 timeouts 0, SG min/max 0/0
    Date/time: 2020-11-14 17:38:34
    Slowest loop: 5.18ms; fastest: 0.15ms
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 25.0MBytes/sec
    SD card longest read time 2.6ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -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
    LCD is idle in state(s) 0
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 6.14ms; fastest: 0.03ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
    HTTP sessions: 1 of 8
    - Ethernet -
    State: active
    Error counts: 0 0 0 0 0
    Socket states: 2 2 2 2 2 0 0 0
    === CAN ===
    Messages sent 94, send timeouts 94, longest wait 2ms for type 6011, free CAN buffers 47
    
    14/11/2020, 17:38:25	Connection established
    
    14/11/2020, 17:38:24	Connection interrupted, attempting to reconnect...
    HTTP request timed out
    
    14/11/2020, 17:37:56	Error: Z probe was not triggered during probing move
    
    14/11/2020, 17:37:43	M98 P"0:/macros/Mesh Probing/Probe 90x90mm"
    Error: Z probe already triggered at start of probing move
    
    14/11/2020, 17:37:11	M98 P"0:/macros/Mesh Probing/Probe_BLTouch_Fast_Mesh"
    Error: Invalid remote handle
    Error: M558: only Z probe types 8 and 9 are supported on expansion boards
    Error: Invalid Z probe index
    Error: in file macro line 17: G29: Z probe 0 not found
    

  • administrators

    Thanks, I will look into it. You may be able to use mode 8 to do a quick probe.



  • This post is deleted!

Log in to reply