Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    no TRP trigger after prolonged Connection issue to CAN board

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    1
    1
    93
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Superbrain8undefined
      Superbrain8
      last edited by

      Good Day,

      Noticed that my Printer running a Duet 3 Mini5+ and a Duet Toolboard had a failing CAN connection during a print,
      noticed this error after about 5 minutes.
      My question is why didnt the printer stopped with an Error?
      i know that the heater control loop should be not interrupted if the heater and thermistor are on the same CAN Board, but having it running for over 5 minutes with no reaction of the Mainboard should not be a thing.

      the failing Can connection where solved by wiggling the JST connector for the CAN connection on the Toolboard (should add a dab of hotglue)

      M122 Readout (after having resolved the issue)

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
      Used output buffers: 3 of 40 (24 max)
      === RTOS ===
      Static ram: 103684
      Dynamic ram: 111292 of which 0 recycled
      Never used RAM 23088, free system stack 112 words
      Tasks: NETWORK(notifyWait,13.6%,185) HEAT(notifyWait,0.0%,340) Move(notifyWait,3.7%,261) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.2%,325) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,106) MAIN(running,80.7%,409) IDLE(ready,0.2%,30) AIN(delaying,0.9%,263), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 01:29:32 ago, cause: software
      Last software reset at 2023-02-17 13:28, reason: User, GCodes spinning, available RAM 23568, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 5372758, completed 5372757, timed out 0, errs 0
      Step timer max interval 1489
      MCU temperature: min 19.2, current 25.2, max 25.4
      Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/316/282, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 20011, writes 9, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: not present
      Driver 6: not present
      Date/time: 2023-02-17 14:58:27
      Cache data hit count 4294967295
      Slowest loop: 1077.90ms; fastest: 0.11ms
      === Storage ===
      Free file entries: 9
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 6.5ms, write time 181.4ms, max retries 0
      === Move ===
      DMs created 83, segments created 33, maxWait 231032ms, bed compensation in use: mesh, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 459661, completed 459621, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 7855, 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 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 85
      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) 3
      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
      === Filament sensors ===
      Extruder 0: no data received
      === CAN ===
      Messages queued 492187, received 108998, lost 0, boc 248
      Longest wait 3ms for reply type 6053, peak Tx sync delay 48919, free buffers 18 (min 3), ts 26863/22456/0
      Tx timeouts 38321,0,4280,0,0,3342 last cancelled message type 51 dest 20
      === Network ===
      Slowest loop: 1077.92ms; fastest: 0.00ms
      Responder states: HTTP(0) 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.27
      WiFi MAC address f0:08:d1:02:e5:fa
      WiFi Vcc 3.42, reset reason Power up
      WiFi flash size 2097152, free heap 26144
      WiFi IP address 192.168.188.70
      WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      
      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Unless otherwise noted, all forum content is licensed under CC-BY-SA