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

    Diagnostics Missing?

    Scheduled Pinned Locked Moved
    Beta Firmware
    5
    18
    610
    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.
    • GeneRisiundefined
      GeneRisi @GeneRisi
      last edited by

      @generisi When I enter M122 on the Paneldue, I get the first few lines on its' screen.

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • GeneRisiundefined
        GeneRisi @sebkritikel
        last edited by

        @sebkritikel Thanks for the confirmation!

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

          @generisi Unfortunately the PanelDue doesn't have enough ram and display capacity to show the entire M122 report on it's screen.

          Can yu confirm that you are using 3.4 beta 2 and are experiencing the same symptoms as @sebkritikel ?

          Z-Bot CoreXY Build | Thingiverse Profile

          GeneRisiundefined 1 Reply Last reply Reply Quote 0
          • GeneRisiundefined
            GeneRisi @Phaedrux
            last edited by GeneRisi

            @phaedrux Yes, I am running 3.4beta2. I haven't tried opening two browsers from two different IP addresses; should I ?

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

              You could. You might see the same behaviour as seb did and see the output of M122 at least.

              Z-Bot CoreXY Build | Thingiverse Profile

              GeneRisiundefined 1 Reply Last reply Reply Quote 0
              • GeneRisiundefined
                GeneRisi @Phaedrux
                last edited by GeneRisi

                @phaedrux I just tried 2 different browsers on same PC.Diagnostic info shows on first duet web session and browser when entered into the second web browser session. It does not appear to work the other way around

                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta2 (2021-08-03 12:41:37) running on Duet WiFi 1.02 or later + DueX5
                Board ID: 08DGM-9T6BU-FG3SJ-6JKF4-3SD6L-TUXRF
                Used output buffers: 3 of 24 (24 max)
                === RTOS ===
                Static ram: 23932
                Dynamic ram: 79440 of which 0 recycled
                Never used RAM 4940, free system stack 98 words
                Tasks: NETWORK(ready,14.0%,227) ACCEL(notifyWait,0.0%,348) HEAT(delaying,0.1%,326) Move(notifyWait,1.7%,285) DUEX(notifyWait,0.0%,24) MAIN(running,84.1%,381) IDLE(ready,0.0%,29), total 100.0%
                Owned mutexes: WiFi(NETWORK)
                === Platform ===
                Last reset 03:58:03 ago, cause: software
                Last software reset at 2021-08-05 09:23, reason: User, GCodes spinning, available RAM 8916, slot 2
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x0c
                Aux0 errors 0,0,0
                Step timer max interval 0
                MCU temperature: min 37.1, current 37.6, max 38.1
                Supply voltage: min 24.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
                Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/0, gc cycles 0
                Driver 0: position 24822, ok, SG min/max 0/1023
                Driver 1: position 4516, ok, SG min/max 0/1023
                Driver 2: position 90248, standstill, SG min/max 0/1023
                Driver 3: position 3300, ok, SG min/max 0/1023
                Driver 4: position 0, standstill, SG min/max not available
                Driver 5: position 0, standstill, SG min/max not available
                Driver 6: position 0, standstill, SG min/max not available
                Driver 7: position 0, standstill, SG min/max not available
                Driver 8: position 0, standstill, SG min/max not available
                Driver 9: position 0, standstill, SG min/max not available
                Driver 10: position 0
                Driver 11: position 0
                Date/time: 2021-08-05 13:21:32
                Cache data hit count 4294967295
                Slowest loop: 12.86ms; fastest: 0.18ms
                I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                === Storage ===
                Free file entries: 9
                SD card 0 detected, interface speed: 20.0MBytes/sec
                SD card longest read time 1.3ms, write time 0.0ms, max retries 0
                === Move ===
                DMs created 83, segments created 38, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 168818, completed moves 168778, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
                === 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 -1 -1, chamberHeaters = -1 -1 -1 -1
                Heater 0 is on, I-accum = 0.0
                Heater 1 is on, I-accum = 0.5
                === GCodes ===
                Segments left: 1
                Movement lock held by null
                HTTP is idle in state(s) 0
                Telnet is idle in state(s) 0
                File is doing "G1 X140.012 Y77.042 E0.0100" 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
                Daemon is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty
                === DueX ===
                Read count 0, 0.00 reads/min
                === Network ===
                Slowest loop: 201.01ms; fastest: 0.08ms
                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 2
                WiFi firmware version 1.26
                WiFi MAC address ec:fa:bc:25:34:dd
                WiFi Vcc 3.34, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 24632
                WiFi IP address 192.168.123.68
                WiFi signal strength -69dBm, 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
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Thanks for confirming.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  GeneRisiundefined 1 Reply Last reply Reply Quote 0
                  • GeneRisiundefined
                    GeneRisi @Phaedrux
                    last edited by

                    @phaedrux And it only displays the diagnostics issues once. After that, all it shows in the console on both browsers is "M122"

                    1 Reply Last reply Reply Quote 0
                    • sebkritikelundefined
                      sebkritikel
                      last edited by

                      @chrishamm I just upgraded to DWC and RRF 3.4.0-b3/3.4.0beta3 (2021-08-24) and am still having this issue.

                      === Diagnostics ===
                      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta3 (2021-08-24 13:56:10) running on Duet WiFi 1.02 or later + DueX5
                      Board ID: 08DGM-917DA-G4MSD-6JTDD-3SN6L-1STR9
                      Used output buffers: 3 of 24 (24 max)
                      === RTOS ===
                      Static ram: 23940
                      Dynamic ram: 77256 of which 44 recycled
                      Never used RAM 10840, free system stack 184 words
                      Tasks: NETWORK(ready,15.8%,227) HEAT(notifyWait,0.0%,326) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,84.1%,441) IDLE(ready,0.1%,29), total 100.0%
                      Owned mutexes: WiFi(NETWORK)
                      === Platform ===
                      Last reset 00:01:03 ago, cause: software
                      Last software reset at 2021-08-25 15:58, reason: User, GCodes spinning, available RAM 10840, slot 0
                      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                      Error status: 0x04
                      Aux0 errors 0,0,0
                      Step timer max interval 0
                      MCU temperature: min 31.2, current 31.8, max 31.8
                      Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
                      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                      Driver 0: position 0, standstill, SG min/max not available
                      Driver 1: position 0, standstill, SG min/max not available
                      Driver 2: position 0, standstill, SG min/max not available
                      Driver 3: position 0, standstill, SG min/max not available
                      Driver 4: position 0, standstill, SG min/max not available
                      Driver 5: position 0, standstill, SG min/max not available
                      Driver 6: position 0, standstill, SG min/max not available
                      Driver 7: position 0, standstill, SG min/max not available
                      Driver 8: position 0, standstill, SG min/max not available
                      Driver 9: position 0, standstill, SG min/max not available
                      Driver 10: position 0
                      Driver 11: position 0
                      Date/time: 2021-08-25 15:59:56
                      Cache data hit count 2383346339
                      Slowest loop: 6.10ms; fastest: 0.16ms
                      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 1.0ms, write time 0.0ms, max retries 0
                      === Move ===
                      DMs created 83, segments created 0, 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 -1 -1, chamberHeaters = -1 -1 -1 -1
                      === 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
                      Daemon is idle in state(s) 0
                      Autopause is idle in state(s) 0
                      Code queue is empty
                      === DueX ===
                      Read count 0, 0.00 reads/min
                      === Network ===
                      Slowest loop: 201.10ms; fastest: 0.09ms
                      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                      HTTP sessions: 2 of 8
                      - WiFi -
                      Network state is active
                      WiFi module is connected to access point 
                      Failed messages: pending 0, notready 0, noresp 2
                      WiFi firmware version 1.23
                      WiFi MAC address cc:50:e3:0d:25:4b
                      WiFi Vcc 3.40, reset reason Turned on by main processor
                      WiFi flash size 4194304, free heap 23960
                      WiFi IP address 192.168.0.8
                      WiFi signal strength -39dBm, mode none, reconnections 0, sleep mode modem
                      Clock register ffffffff
                      Socket states: 0 0 0 0 0 0 0 0
                      

                      Large(ish?) IDEX - 6HC, 1HCL
                      Stratasys Dimension 1200es to 6HC Conversion

                      dc42undefined 1 Reply Last reply Reply Quote 1
                      • dc42undefined
                        dc42 administrators @sebkritikel
                        last edited by

                        @sebkritikel we've identified an issue in DWC that prevents the M122 response from a Duet WiFi being displayed in some situations. It looks like it may have been triggered by the response getting a little longer.

                        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 1
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA