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

Strange bugs 3.3beta2

Scheduled Pinned Locked Moved Unsolved
Beta Firmware
8
48
2.4k
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.
  • undefined
    Dep @Phaedrux
    last edited by 19 Mar 2021, 10:18

    @Phaedrux said in Strange bugs 3.3beta2:

    @Dep said in Strange bugs 3.3beta2:

    M376 H20 ; bed compensation taper

    With a taper set the amount moved to compensate is diminished over the duration of the print and for small amounts can make it very hard to see.

    I've tried disabling taper. M376 H0
    Nothing changes.

    1 Reply Last reply Reply Quote 0
    • undefined
      jay_s_uk
      last edited by 19 Mar 2021, 10:27

      add G29 S1 after the G28 in your start script

      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

      undefined 1 Reply Last reply 19 Mar 2021, 10:35 Reply Quote 0
      • undefined
        Dep @jay_s_uk
        last edited by 19 Mar 2021, 10:35

        @jay_s_uk It is added:

        homeall.g (G29 S1 here)

        ; homeall.g
        ; called to home all axes
        ;
        M98 P"homex.g"
        M98 P"homey.g"
        M98 P"bed.g"
        G29 S1
        
        undefined 1 Reply Last reply 19 Mar 2021, 10:35 Reply Quote 0
        • undefined
          jay_s_uk @Dep
          last edited by 19 Mar 2021, 10:35

          @Dep ah, missed that

          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

          1 Reply Last reply Reply Quote 0
          • undefined
            Phaedrux Moderator
            last edited by 19 Mar 2021, 21:41

            All I can think is that the conditional gcode in your homing files is skipping something.

            Can you try adding G29 S1 to your slicer start gcode after the purge filament macro?

            Then check if mesh compensation is active in M122 during the print and see if the Z axis is moving.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • undefined
              OwenD
              last edited by 19 Mar 2021, 22:04

              Could it be that you're not homing Z after you run bed.g ?

              undefined 1 Reply Last reply 19 Mar 2021, 22:23 Reply Quote 0
              • undefined
                Phaedrux Moderator @OwenD
                last edited by 19 Mar 2021, 22:23

                @OwenD said in Strange bugs 3.3beta2:

                Could it be that you're not homing Z after you run bed.g ?

                Bed.g is getting called as part of homeall. bed.g calls homez.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • undefined
                  Dep
                  last edited by 20 Mar 2021, 07:57

                  The oddities continue. Now there is a problem with the filament monitor: min -5% and printing continues:

                  20.03.2021, 10:39:40	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.37mm/rev, min -5% max 105% over 153582.5mm
                  20.03.2021, 10:32:45	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 151673.8mm
                  20.03.2021, 10:25:49	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 149761.4mm
                  20.03.2021, 10:22:38	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148885.3mm
                  20.03.2021, 10:21:55	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148686.4mm
                  20.03.2021, 10:21:18	M591 d0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 131 agc 107, measured sensitivity 25.36mm/rev, min -5% max 105% over 148515.8mm
                  

                  After the "reset":

                  20.03.2021, 10:52:50	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.51mm/rev, min 97% max 104% over 2092.2mm
                  20.03.2021, 10:50:15	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.51mm/rev, min 97% max 104% over 1380.5mm
                  20.03.2021, 10:48:02	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.53mm/rev, min 97% max 104% over 766.6mm
                  20.03.2021, 10:47:35	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.54mm/rev, min 97% max 104% over 644.5mm
                  20.03.2021, 10:45:52	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.57mm/rev, min 97% max 104% over 171.1mm
                  20.03.2021, 10:45:22	M591 D0
                  Duet3D rotating magnet filament monitor v3 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, version 3, mag 132 agc 107, measured sensitivity 25.57mm/rev, min 97% max 101% over 26.5mm
                  20.03.2021, 10:45:02	M292
                  Printing paused at X-21.7 Y-33.3 Z2.5 C40.0
                  20.03.2021, 10:44:51	Resume state saved
                  20.03.2021, 10:44:24	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:44:14	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:43:53	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:43:39	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:43:19	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:42:57	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:42:43	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:42:34	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, enabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:42:31	M591 d0 s1
                  20.03.2021, 10:42:24	M591 d0
                  Duet3D rotating magnet filament monitor v1 on pin 21.io1.in, disabled, sensitivity 28.80mm/rev, allow 30% to 160%, check every 3.0mm, no data received
                  20.03.2021, 10:42:21	M591 d0 s0
                  

                  All settings are higher in this thread.

                  I ran 170 hours long print. I should have tried to install the old firmware, something is wrong here 😞

                  And a couple of screenshots to tread:
                  IMG_3010.jpg
                  IMG_3013.jpg

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    Dep
                    last edited by 20 Mar 2021, 08:14

                    And I already had it. But at that moment
                    I had one of the extruders disabled on the CAN bus and errors were pouring in. I thought it was because of this.

                    Last time min was -107% the extruder ended up stuck, but the printer kept printing in air all night.

                    In general, the filament monitor does not work on this firmware.

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      Dep
                      last edited by 20 Mar 2021, 18:40

                      I installed 3.2.2 firmware - the errors disappeared, the mesh is working, the filament monitor is working.

                      The printer is printing 5 hours, the flight is normal. So pay attention to what I wrote above.

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Phaedrux Moderator
                        last edited by 20 Mar 2021, 18:56

                        So it's all working fine in 3.2.2 but has problems with 3.3beta2?

                        If so I will remove the Solved tag as it still needs to be investigated.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Dep
                          last edited by 20 Mar 2021, 20:00

                          The errors that fell on the screen and the problem with the filament sensor disappeared immediately. So yes, this is a beta issue.

                          As for the mesh calibration, I still do not understand. Now it seems to be working. But it somehow still worked on beta. I recalibrated many times, so I got completely confused.

                          1 Reply Last reply Reply Quote 0
                          • oliofundefined
                            oliof
                            last edited by 22 Mar 2021, 08:38

                            FWIW I see those errors too with a Paneldue, so I removed it for the time being. Machine is down for other reasons right now, so I forgot to report it.

                            <>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
                            • dc42undefined
                              dc42 administrators
                              last edited by dc42 22 Mar 2021, 10:31

                              Next time one of you get these "Bad command" messages on PanelDue, please run M122 from the DWC console or USB. I am especially interested in what value it reports for "Aux0 errors".

                              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

                              undefined undefined 2 Replies Last reply 25 Mar 2021, 10:06 Reply Quote 0
                              • dc42undefined
                                dc42 administrators @Dep
                                last edited by 22 Mar 2021, 11:06

                                @Dep said in Strange bugs 3.3beta2:

                                Another dangerous bug!

                                M558 K0 H5 A5 F120
                                Works as it should

                                M558 K0 H5 A5 F120: 120
                                Also works as it should

                                M558 K0 H5 A5 F120: 60
                                Broke today probe.
                                The bed goes up and breaks the probe. And continue to rise.

                                I checked it several times.

                                What type of probe is it? Some types of probe (e.g. Smart Effector and piezo probes) don't work at low speeds.

                                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
                                • undefined
                                  Dep
                                  last edited by 25 Mar 2021, 10:05

                                  Simple micro switch.

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    Dep @dc42
                                    last edited by 25 Mar 2021, 10:06

                                    @dc42 I can't yet, because I installed version 3.2.2 and the messages disappeared.

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      psychotik2k3 @dc42
                                      last edited by 24 May 2021, 20:20

                                      @dc42 here it is:

                                      24/05/2021, 22:20:04	M122
                                      === Diagnostics ===
                                      RepRapFirmware for Duet 3 MB6HC version 3.3RC2 (2021-05-11 14:55:28) running on Duet 3 MB6HC v1.01 or later (standalone mode)
                                      Board ID: 08DJM-956BA-NA3TN-6JTD8-3S86J-1UB2T
                                      Used output buffers: 1 of 40 (40 max)
                                      === RTOS ===
                                      Static ram: 150680
                                      Dynamic ram: 93532 of which 108 recycled
                                      Never used RAM 107016, free system stack 120 words
                                      Tasks: NETWORK(ready,445.1%,226) ETHERNET(notifyWait,1.3%,124) HEAT(delaying,0.2%,295) Move(notifyWait,0.6%,242) CanReceiv(notifyWait,0.3%,773) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.1%,341) TMC(notifyWait,128.2%,59) MAIN(running,312.5%,619) IDLE(ready,0.0%,29), total 888.3%
                                      Owned mutexes:
                                      === Platform ===
                                      Last reset 03:22:59 ago, cause: software
                                      Last software reset at 2021-05-24 18:57, reason: User, GCodes spinning, available RAM 110188, slot 0
                                      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
                                      Error status: 0x04
                                      Aux0 errors 9,9,9
                                      Aux1 errors 0,0,0
                                      Step timer max interval 133
                                      MCU temperature: min 40.4, current 42.5, max 43.1
                                      Supply voltage: min 23.3, current 23.7, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
                                      12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
                                      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0
                                      Driver 0: position 12600, standstill, reads 41045, writes 30 timeouts 0, SG min/max 0/212
                                      Driver 1: position -22000, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/212
                                      Driver 2: position 4272, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/173
                                      Driver 3: position 0, standstill, reads 41046, writes 30 timeouts 0, SG min/max 0/168
                                      Driver 4: position 0, standstill, reads 41065, writes 11 timeouts 0, SG min/max 0/0
                                      Driver 5: position 0, standstill, reads 41066, writes 11 timeouts 0, SG min/max 0/0
                                      Date/time: 2021-05-24 22:18:43
                                      Slowest loop: 13.29ms; fastest: 0.05ms
                                      === Storage ===
                                      Free file entries: 10
                                      SD card 0 detected, interface speed: 25.0MBytes/sec
                                      SD card longest read time 2.2ms, write time 2.0ms, max retries 0
                                      === Move ===
                                      DMs created 125, maxWait 8863916ms, bed compensation in use: mesh, comp offset 0.038
                                      === MainDDARing ===
                                      Scheduled moves 410, completed moves 410, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 -1 -1 -1 -1 -1 -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
                                      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.
                                      === CAN ===
                                      Messages queued 110176, send timeouts 0, received 146584, lost 0, longest wait 2ms for reply type 6018, peak Tx sync delay 284, free buffers 49 (min 48)
                                      === Network ===
                                      Slowest loop: 5.93ms; fastest: 0.02ms
                                      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
                                      HTTP sessions: 1 of 8
                                      - Ethernet -
                                      State: active
                                      Error counts: 0 0 1 0 0
                                      Socket states: 5 2 2 2 2 0 0 0
                                      

                                      IMG_20210524_221838.jpg

                                      undefined 1 Reply Last reply 24 May 2021, 20:21 Reply Quote 0
                                      • undefined
                                        psychotik2k3 @psychotik2k3
                                        last edited by 24 May 2021, 20:21

                                        @psychotik2k3 and i reproduce for example when doing a bed leveling from the panel due (and other stuffs)
                                        the gcode executed is this one:

                                        ; bed.g
                                        ; called to perform automatic bed compensation via G32
                                        ;
                                        
                                        if (move.axes[2].homed=false ) 
                                        	echo "homing Z axis"
                                        	M98 P"homez.g"
                                        G30 P0 X297 Y154 Z-99999 s-1
                                        G30 ; home
                                        
                                        ;for bltouch
                                        G30 P0 X297 Y154 Z-99999 ; probe near a leadscrew, half way along Y axis
                                        G30 P1 X9 Y154 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
                                        
                                        
                                        
                                        undefined 1 Reply Last reply 24 May 2021, 20:23 Reply Quote 0
                                        • undefined
                                          psychotik2k3 @psychotik2k3
                                          last edited by 24 May 2021, 20:23

                                          @psychotik2k3 and i have these errors since today when i switched from 3.2.2 stable to 3.3 RC2
                                          allways a bad command * M409 *

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