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

    G32/Bed Trim Bug in 3.5B1

    Scheduled Pinned Locked Moved
    Beta Firmware
    4
    7
    311
    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.
    • PCRundefined
      PCR
      last edited by PCR

      • Start Printer
      • Print Part
      • Start another Print
      • Printer resets itself after the first Calculation of the bed plane
        *Need full reset to start a new print (M999)
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.5beta1 (2022-12-23 18:25:34) running on Duet 3 Mini5plus WiFi (standalone mode)
      Used output buffers: 3 of 40 (25 max)
      === RTOS ===
      Static ram: 102208
      Dynamic ram: 116780 of which 24 recycled
      Never used RAM 22700, free system stack 198 words
      Tasks: NETWORK(notifyWait,10.2%,243) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,359) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,349) TMC(notifyWait,0.6%,114) MAIN(running,87.3%,449) IDLE(ready,1.0%,30) AIN(delaying,0.8%,272), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 00:00:24 ago, cause: software
      Last software reset at 2022-12-28 14:31, reason: HardFault unaligned, GCodes spinning, available RAM 16400, slot 1
      Software reset code 0x4063 HFSR 0x40000000 CFSR 0x01000000 ICSR 0x00446803 BFAR 0xe000ed38 SP 0x200037c0 Task MAIN Freestk 636 ok
      Stack: 00000000 000000a5 00000000 00000000 2001ce64 00046bef 00046c5e 81030000 ffffffff 00000066 00000000 40727000 20003850 20018448 20024704 00033ec9 20018448 00000003 00000003 000468c3 00000003 20024704 00000000 00000000 0000000a 32000000 00000000
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 24611, completed 24610, timed out 0, errs 0
      Step timer max interval 1488
      MCU temperature: min 23.6, current 24.9, max 25.3
      Supply voltage: min 24.4, current 24.4, max 24.4, 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
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 84, read errors 0, write errors 1, ifcnt 226, reads 1261, writes 14, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 128, read errors 0, write errors 1, ifcnt 226, reads 1261, writes 14, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 82, read errors 0, write errors 1, ifcnt 215, reads 1261, writes 14, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 88, read errors 0, write errors 1, ifcnt 68, reads 1260, writes 14, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 50, read errors 0, write errors 1, ifcnt 69, reads 1261, writes 14, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: not present
      Driver 6: not present
      Date/time: 2022-12-28 14:32:01
      Cache data hit count 48566923
      Slowest loop: 3.99ms; fastest: 0.13ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 0.6ms, 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
      no step interrupt scheduled
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      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 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, 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 assembling a command 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000803
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === Filament sensors ===
      Extruder 0: no data received
      === CAN ===
      Messages queued 223, received 533, lost 0, boc 0
      Longest wait 3ms for reply type 6026, peak Tx sync delay 166, free buffers 18 (min 17), ts 123/122/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 3.76ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      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 2.1beta2
      WiFi MAC address f0:08:d1:02:e9:51
      WiFi Vcc 3.26, reset reason Power up
      WiFi flash size 4194304, free heap 42952
      WiFi IP address 192.168.178.133
      WiFi signal strength 0dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002001
      Socket states: 0 0 0 0 0 0 0 0
      

      bed.g

      G28 X Y
      M401
      M98 P"homez_wp.g"
      M561 ; clear any bed transform
      M201 X1200 Y1200 
      ;G28
      G30 P0 X10 Y10 Z-99999 ; probe near a leadscrew
      G30 P1 X150 Y260 Z-99999 ; probe near a leadscrew
      G30 P2 X250 Y10 Z-99999 S3
      ;G30 P3 X250 Y130 Z-99999
      ;G30 P3 X250 Y0 Z-99999 S3
      
      
      G30 P0 X10 Y10 Z-99999 ; probe near a leadscrew
      G30 P1 X150 Y260 Z-99999 ; probe near a leadscrew
      G30 P2 X250 Y10 Z-99999 S3
      ;G30 P3 X250 Y130 Z-99999
      ;G30 P3 X250 Y0 Z-99999 S3
      
      G30 P0 X10 Y10 Z-99999 ; probe near a leadscrew
      G30 P1 X150 Y260 Z-99999 ; probe near a leadscrew
      G30 P2 X250 Y10 Z-99999 S3
      ;G30 P3 X250 Y130 Z-99999
      ;G30 P3 X250 Y0 Z-99999 S3
      
      ;G30 P0 X10 Y10 Z-99999 ; probe near a leadscrew
      ;G30 P1 X150 Y270 Z-99999 ; probe near a leadscrew
      ;G30 P2 X250 Y10 Z-99999 S3
      ;G30 P3 X250 Y130 Z-99999
      ;G30 P3 X250 Y0 Z-99999 S3
      
      G1 X195 Y134 F6000 ; go to first probe point
      G30              ; home Z by probing the bed
      G29 S0
      M402
      M201 X2000 Y2000
      M569 P0.3 D3 V10
      M569 P0.4 D3 V10
      
      PCRundefined dc42undefined 2 Replies Last reply Reply Quote 1
      • PCRundefined
        PCR @PCR
        last edited by

        @PCR seems like reset from webUI does not work. Reset from paneldue does

        oliofundefined 1 Reply Last reply Reply Quote 0
        • oliofundefined
          oliof @PCR
          last edited by

          @PCR just to make sure this is the re-uploaded 3.5b1firmware, not the first one?

          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @oliof
            last edited by

            @oliof it was 3.4.5 that had the upload issue, not 3.5b1

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            oliofundefined 1 Reply Last reply Reply Quote 1
            • oliofundefined
              oliof @jay_s_uk
              last edited by

              @jay_s_uk shoot, I keep mixing up things.

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

              1 Reply Last reply Reply Quote 0
              • Diamondbackundefined Diamondback referenced this topic
              • dc42undefined
                dc42 administrators @PCR
                last edited by

                @PCR thank for your report. I can't identify the cause immediately from the M122 report, so this issue is on my list to reproduce.

                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

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

                  This issue is now fixed. See https://forum.duet3d.com/post/303514 for more details.

                  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