Where Log messages



  • Hi,

    i am having troubles with temp, excesive hot, and i have upgraded firmware to:

    • 2.0(RTOS) (2018-06-05b3)

    But i can't find log messages, in version 1.21, they appear in console...

    Where i can find these error messages, that Duet generates with overtemperature?

    And

    There is some method of view drivers temps? If Duet send a message with hihg temperature has reached, this mean, that cant follow this temp. No?

    Thanks



  • Here is a link to a similar question about monitoring driver temps.

    https://forum.duet3d.com/topic/5507/detect-overheated-driver/3


  • administrators

    @peirof regarding the log messages - which ones are you referring to?

    Cheers

    Tony



  • @timcurtis67 Thanks



  • @peirof Messages on the console, noting that the temperature in the motors is high


  • administrators

    @peirof are you sure that the stepper drivers are ovettemperature. What does M122 report?



  • Hi,

    i have put a big fan, 120 mm 24v, over drivers in duet, the results of M122.
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-95BNL-MGPSN-6JKDL-3S06L-92W7W
    Used output buffers: 3 of 20 (9 max)
    === RTOS ===
    Static ram: 28380
    Dynamic ram: 95940 of which 16 recycled
    Exception stack ram used: 436
    Never used ram: 6300
    Task NETWORK ready, free stack 324
    Task HEAT blocked, free stack 1256
    Task MAIN running, free stack 3560
    === Platform ===
    Last reset 01:25:34 ago, cause: power up
    Last software reset at 2018-06-27 11:36, reason: User, spinning module GCodes, available RAM 6312 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 88.2ms
    MCU temperature: min 39.1, current 43.8, max 44.3
    Supply voltage: min 24.2, current 24.5, max 24.9, under voltage events: 0, over voltage events: 0
    Driver 0: ok, SG min/max 0/166
    Driver 1: ok, SG min/max 0/201
    Driver 2: ok, SG min/max 0/188
    Driver 3: ok, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2018-06-27 13:10:11
    Slowest loop: 34.95ms; fastest: 0.07ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 170, MinFreeDm 120, MaxWait: 60509396ms, Underruns: 0, 0
    Scheduled moves: 74920, completed moves: 74902
    Bed compensation in use: mesh
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 2 is on, I-accum = 0.3
    === GCodes ===
    Segments left: 1
    Stack records: 1 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 doing "G1 X-27.782 Y1.683 E3863.46408" 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: 90.77ms; fastest: 0.01ms
    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.21
      WiFi MAC address 2c:3a:e8:0b:05:a1
      WiFi Vcc 3.35, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 13992
      WiFi IP address 192.168.1.200
      WiFi signal strength -60dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Expansion ===

  • administrators

    @peirof the drivers are not reporting a temperature issue and the CPU is cool.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.