Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Mini5+ "mcu-temp" sensor definition does not work

    Using Duet Controllers
    3
    6
    124
    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.
    • oc_geek
      oc_geek last edited by oc_geek

      ; Define MCU sensors which will be available in DWC Extra View
      M308 S3 A"MCU" Y"mcu-temp"
      M308 S4 A"Duet Drivers" Y"drivers"

      For some reason the M308 "mcu-temp" doesn't work - error sensor "mcutemp" does not exist (and yes the "-" is removed in the error message)
      (The drivers one perfectly works)

      Any help please ?
      Does the Mini5+ use a different name for the MCU Temp Sensor ?
      (i saw this same command in the Wiki)

      Thanks

      dc42 1 Reply Last reply Reply Quote 0
      • Phaedrux
        Phaedrux Moderator last edited by

        Can you send M122 and report the results? Should be running fw 3.2 final.

        https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • oc_geek
          oc_geek last edited by

          Yes i'm on Rel 3.2

          Here is the dump of M122

          1/21/2021, 9:46:46 PM M122
          === Diagnostics ===
          RepRapFirmware for Duet 3 Mini 5+ version 3.2 running on Duet 3 Mini5plus WiFi (standalone mode)
          Board ID: F8W09-K196U-D65J0-40KM0-LH03Z-Z1XLX
          Used output buffers: 3 of 40 (11 max)
          === RTOS ===
          Static ram: 98732
          Dynamic ram: 113696 of which 92 recycled
          Never used RAM 32696, free system stack 200 words
          Tasks: NETWORK(ready,202) HEAT(blocked,316) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,123) MAIN(running,440) IDLE(ready,20) AIN(blocked,267)
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 00:01:05 ago, cause: power up
          Last software reset at 2021-01-19 23:49, reason: User, GCodes spinning, available RAM 32696, 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
          Aux1 errors 0,0,0
          Supply voltage: min 0.0, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
          Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
          Date/time: 2021-01-21 21:46:45
          Cache data hit count 137638723
          Slowest loop: 27.84ms; fastest: 0.12ms
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 22.5MBytes/sec
          SD card longest read time 3.8ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters = 0 -1, chamberHeaters = -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: 21.01ms; 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.25
            WiFi MAC address f4:cf:a2:6f:e9:87
            WiFi Vcc 3.46, reset reason Power up
            WiFi flash size 2097152, free heap 25104
            WiFi IP address 10.0.0.7
            WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode modem
            Clock register 00002002
            Socket states: 0 0 0 0 0 0 0 0
            === CAN ===
            Messages queued 585, send timeouts 583, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
          1 Reply Last reply Reply Quote 0
          • dc42
            dc42 administrators @oc_geek last edited by dc42

            @oc_geek said in Mini5+ "mcu-temp" sensor definition does not work:

            Does the Mini5+ use a different name for the MCU Temp Sensor ?

            Unfortunately the SAME54P20A chip used in the Duet 3 Mini does not have a functioning temperature sensor. In theory it does have an on-chip temperature sensor, but the errata document for the chip says it doesn't work. Microchip has told me that they don't expect to fix this in a new revision of the chip any time soon.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            • oc_geek
              oc_geek last edited by oc_geek

              ok that explains a lot, thanks !

              Perhaps worth to mention it in the docs so others will know as well

              1 Reply Last reply Reply Quote 0
              • Phaedrux
                Phaedrux Moderator last edited by

                I'll add a note to the documentation.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA