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

Rotating Magnetic Sensor - Keeps Pausing Printer

Scheduled Pinned Locked Moved Solved
Filament Monitor
9
151
8.8k
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
    PetrKroupa
    last edited by PetrKroupa 11 Sept 2021, 18:27 9 Nov 2021, 17:52

    Today I upgraded to BETA6 and it is interesting that my sensor started pause job. On BETA5, no problems. sensor.png

    M591 D0
    Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, disabled, sensitivity 24.80mm/rev, allow 75% to 125%, check printing moves every 5.0mm, version 3, mag 131 agc 91, measured sensitivity 25.72mm/rev, min -56% max 107% over 10658.5mm

    My setup is 6HC+1LC, SBC. bondtech mosquito. 20211109_184858.JPG

    I must disable sensor because it is not possible to print.

    ; Configuration file for Duet 3 (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Apr 21 2021 11:35:55 GMT+0200 (Středoevropský letní čas)
    M81 C"pson"
    G4 S1
    M80
    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"velkej" ; set printer name
    G4 S1
    ; Drives
    M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E121.0 ; set drive mapping
    ;M569 P40.0 S0 R1 T3:3:50:50
    ;M569 P41.0 S0 R1 T3:3:50:50
    ;M569 P40.0 S0 R1 T2.7:2.7:6:6 ; change enable polarity, active = disable drive
    ;M569 P41.0 S0 R1 T2.7:2.7:6:6 ; change enable polarity, active = disable drive
    M569 P0.0 S1
    M569 P0.1 S0
    M569 P0.2 S0 ; physical drive 0.2 goes forwards
    M569 P0.3 S0
    M569 P0.4 S0 ; physical drive 0.3 goes forwards
    M569 P0.5 S0
    M671 X26:380:380:26 Y20:20:380:380 S10
    M350 X16 Y16 Z8 E16 I1 ; configure microstepping with interpolation
    M92 X142.22 Y142.22 Z400.00 E420.00 ; set steps per mm
    M566 X600.00 Y600.00 Z60.00 E150.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X18000.00 Y18000.00 Z1500.00 E7500.00 ; set maximum speeds (mm/min)
    M201 X5000.00 Y5000.00 Z250.00 E5000.00 ; set accelerations (mm/s^2)
    M906 X1200 Y2500 Z2000 E450 I40 ; set motor currents (mA) and motor idle factor in per cent
    ;M569 P40 T2.7:2.7:2.7:2.7
    ;M569 P41 T2.7:2.7:2.7:2.7
    M84 S10 ; Set idle timeout
    ; Axis Limits
    M208 X-5 Y0 Z0 S1 ; set axis minima
    M208 X400 Y400 Z420 S0 ; set axis maxima
    ; Endstops
    M574 X1 S1 P"io2.in" ; configure active-high endstop for low end on X via pin io0.in
    M574 Y2 S1 P"io5.in" ; configure active-high endstop for low end on Y via pin io1.in
    M574 Z1 S2 ; configure Z-probe endstop for low end on Z
    ; Z-Probe
    M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch
    M558 P9 C"^121.io0.in" H5 F400 T18000 ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X26 Y0 Z1 ; set Z probe trigger value, offset and trigger height
    M557 X30:400 Y5:400 S41 ; define mesh grid
    ; Filament sensor
    M591 D0 P3 C"121.io1.in" S1 R75:125 L24.8 E5.0
    ; Heaters
    M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0
    M950 H0 C"out0" Q10 T0 ; create bed heater output on out0 and map it to sensor 0
    M307 H0 B0 R0.161 C1877.2 D21.70 S1.00 ; disable bang-bang mode, set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M308 S1 P"121.temp0" Y"thermistor" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin temp1
    M950 H1 C"121.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1
    M307 H1 R2.856 C161.2:95.6 D7.68 S1.00 V24.9 ; disable bang-bang mode for heater and set PWM limit
    M143 H1 S300 ; set temperature limit for heater 1 to 300C
    ;CPU temperature calib
    M912 P0 S-12
    ; Fans
    M950 F0 C"121.out1" Q500 ; create fan 0 on pin out7 and set its frequency
    M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
    M950 F1 C"121.out2+out2.tach" ; Q500
    ;M950 F1 C"121.out2+121.out2.tach" ; create fan 1 on pin out4 and set its frequency + snimaní otáček
    M106 P1 S1 H1 T50 ; set fan 1 value. Thermostatic control is turned on
    ; Tools
    M563 P0 S"Mosquito" D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
    ; M591 ;filament sensor monitor
    M150 X1 Q3000000
    M150 U120 S15
    ; Custom settings are not defined
    M955 P121.0 I42 ; specify orientation of accelerometer on SAMMYC21 with CAN address 121
    ; Miscellaneous
    T0 ; select first tool

    Presure advance is used: M572 D0 S0.04

    BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
    SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

    Petr

    undefined 1 Reply Last reply 10 Nov 2021, 08:22 Reply Quote 0
    • undefined
      T3P3Tony administrators @PetrKroupa
      last edited by 10 Nov 2021, 08:22

      @petrkroupa please share the gcode file you were printing that has this issue. Also what Z height did you have the really bad low value.

      www.duet3d.com

      undefined 1 Reply Last reply 10 Nov 2021, 15:56 Reply Quote 0
      • undefined
        PetrKroupa @T3P3Tony
        last edited by 10 Nov 2021, 15:56

        @t3p3tony - Here is file - 0.6 nozzle, PLA https://uloz.to/tamhle/FnGywCyC0Lbx#!ZGNmZQR2AwZ1ZmV0BGV3LzExATWvBUuvGQOzJUqHASq3MwSvBD==
        It is 8Mb. I had to upload it to another server. Anyway, the error occurred many times in the first 4 layers. Then I turned off the sensor (m591 D0 S0). Today morning before the end of printing I tried M591 D0 and measured sensitivity was min -53% max 105%. Printing was completed successfully without any problems.

        Z height? Do you mean : G31 P500 X26 Y0 Z1? Or?

        BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
        SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

        Petr

        undefined 1 Reply Last reply 10 Nov 2021, 16:01 Reply Quote 0
        • undefined
          T3P3Tony administrators @PetrKroupa
          last edited by 10 Nov 2021, 16:01

          @petrkroupa thanks. The answer to the Z height question is that it happened many times in the first few layers. Just makes it easier to reproduce if I don't need to print the whole part.

          www.duet3d.com

          undefined 1 Reply Last reply 10 Nov 2021, 16:18 Reply Quote 0
          • undefined
            PetrKroupa @T3P3Tony
            last edited by 10 Nov 2021, 16:18

            @t3p3tony - maxi_dvojka_CUT- Telo32-2_0.6n_0.3mm_PLA_velkej_2h10m.gcode

            OK, here is a cut off model. It is only 1.5 mm high. Sliced with same setings.

            I thing my Z height is OK. Not too much on the bed. BuildTak doesn't like it. Rather, I feel like I'm almost too high. However, the value entered in G31 still depends on the position of the probe. I use BLTouch and I believe it's ok. Anyway, I believe this is not a filament sensor problem. 😊

            first layer:
            20211110_171502.JPG

            BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
            SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

            Petr

            undefined 1 Reply Last reply 10 Nov 2021, 18:44 Reply Quote 0
            • undefined
              alankilian @PetrKroupa
              last edited by alankilian 11 Oct 2021, 18:45 10 Nov 2021, 18:44

              @petrkroupa I notice your layer change has something I've never seen before:

              • Two very fast negative movement on the extruder.
              • Normal speed negative movement on the extruder
              • Normal speed positive movement on the extruder

              This is the only unusual thing I see.

              Starting at line 730 in the file:

              ;WIPE_START
              G1 F14400
              G1 X264.546 Y233.289 E-.42543
              G1 X264.445 Y232.993 E-.04957
              ;WIPE_END
              G1 E-.025 F2400
              G1 Z.7 F18000
              G1 X265.067 Y236.944
              G1 Z.2
              G1 E.5 F2400
              ;TYPE:External perimeter

              SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

              undefined 1 Reply Last reply 10 Nov 2021, 19:01 Reply Quote 0
              • undefined
                PetrKroupa @alankilian
                last edited by 10 Nov 2021, 19:01

                @alankilian - Hmm Im using prusa slicer. the question is what is there for. Most likely it's a remnant of the original profile. But the error always occurs somewhere during the layer, I never observed it at the beginning. But good point, thanks. I try remove it.

                BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                Petr

                undefined undefined 2 Replies Last reply 10 Nov 2021, 21:25 Reply Quote 0
                • undefined Phaedrux moved this topic from Using Duet Controllers 10 Nov 2021, 20:21
                • undefined
                  alankilian @PetrKroupa
                  last edited by 10 Nov 2021, 21:25

                  @petrkroupa If you can slice something smaller, I can try printing on my Delta and see if I get errors also. (If you can center at (0,0) that would be even better.)

                  SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators @PetrKroupa
                    last edited by 10 Nov 2021, 22:50

                    @petrkroupa likewise, if you can slice it centred at (0,0) I will try it on my delta and on my toolchanger.

                    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 2 Replies Last reply 11 Nov 2021, 08:42 Reply Quote 0
                    • undefined
                      PetrKroupa @dc42
                      last edited by 11 Nov 2021, 08:42

                      @alankilian, @dc42 - Today i will finish last big print. Then I will try to create some small GCODE (50 * 100mm) where the error will definitely show up. I'll test it and upload it here. We'll see what shows. So far, it seems that the error does not occur during the first layer.

                      BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                      SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                      Petr

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        PetrKroupa @dc42
                        last edited by 11 Nov 2021, 13:41

                        @dc42 - One question, if the problem was somewhere on the HW side, the measured % value would be lower. Because the sensor simply turns less than the extruder. Correct?

                        However, this does not explain how a min -53% can happen. The extruder would have to create the filament. 🙂

                        Am I thinking right or am I completely out of it?

                        BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                        SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                        Petr

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          PetrKroupa
                          last edited by 12 Nov 2021, 10:03

                          I finally figured out what was happening.

                          sensor.mp4

                          When the filament is slightly bent, the sensor restarts. Not always. But I managed to film it during manual extrusion. What is certain is that it cannot be wiring because nothing moves. It's weird that it only showed up with BETA6, but until then I didn't have a problem with it.

                          The question is why the sensor restarts.

                          BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                          SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                          Petr

                          undefined undefined 2 Replies Last reply 12 Nov 2021, 13:39 Reply Quote 1
                          • undefined
                            alankilian @PetrKroupa
                            last edited by 12 Nov 2021, 13:39

                            @petrkroupa said in Rotating Magnetic Sensor - Keeps Pausing Printer:

                            When the filament is slightly bent, the sensor restarts

                            OH! That's a good catch.

                            SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              dc42 administrators @PetrKroupa
                              last edited by 12 Nov 2021, 15:07

                              @petrkroupa is the AGC value reported by M591 consistently below 100 ?

                              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 1 Reply Last reply 12 Nov 2021, 15:13 Reply Quote 0
                              • undefined
                                PetrKroupa @dc42
                                last edited by 12 Nov 2021, 15:13

                                @dc42 - Yes, it is solid somewhere between 91-93. I also verified that the spindle rotates freely and has no axial move.

                                I tried to tap the sensor in various ways, bend the connectors and twist it in every way. Strange....

                                BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                                SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                                Petr

                                undefined 1 Reply Last reply 13 Nov 2021, 11:36 Reply Quote 0
                                • undefined
                                  dc42 administrators @PetrKroupa
                                  last edited by 13 Nov 2021, 11:36

                                  @petrkroupa I think either there is a dodgy power connection somewhere, most likely in the wiring but possibly on the PCB itself; or something is causing the watchdog timer to time out. I can't see any reason in the firmware why the watchdog timer would time out, other than bad power or a transient causing the microcontroller to get into a bad state.

                                  If you are sure that you can't provoke it or temporarily fix it by bending the wiring, then I suggest we replace the circuit board. Please email warranty@duet3d.com with a link to this thread.

                                  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 1 Reply Last reply 13 Nov 2021, 12:47 Reply Quote 0
                                  • undefined
                                    PetrKroupa @dc42
                                    last edited by 13 Nov 2021, 12:47

                                    @dc42 - I will make new wiring to sensor. I have order new sensor to my second printer. After it arrives, I will try found where is problem. If you are sure there is no FW reason to restart sensor intself, it must be somewhere in board/wiring. And since only the sensor is restarted and not tool board, the solution must be easy.

                                    Waranty for that small and cheap thing it doesn't make sense to me. 🙂 Thank you anyway.

                                    I think we can close this thread. Thank you for your help.

                                    BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                                    SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                                    Petr

                                    undefined 1 Reply Last reply 13 Nov 2021, 13:35 Reply Quote 0
                                    • undefined
                                      T3P3Tony administrators @PetrKroupa
                                      last edited by 13 Nov 2021, 13:35

                                      @petrkroupa thanks for the diagnostic work. I came here to say i could not reproduce the problem with my test setup and your earlier print code - should have checked here again first!

                                      Please do update this thread once you have tested your new board for the other printer.

                                      www.duet3d.com

                                      undefined 1 Reply Last reply 19 Nov 2021, 18:34 Reply Quote 0
                                      • undefined
                                        CNCModeller
                                        last edited by CNCModeller 15 Nov 2021, 18:50

                                        Hi All,
                                        I'm still getting behaviour that I don't understand, I'm using the automated meta gcode for generating a PA calibration print. I've attached the gcode and some log files. The log file contains a readout of the filament sensor status triggered at each layer change.

                                        Inspecting the print optimal PA seems to be at about 25mm, Pressure advance: 0.25

                                        eventlog.txt

                                        PATuning.g

                                        The sensor is tripping out at about 40mm, but the measured sensitivity seems to start gradually reducing at about 20mm (0.2 PA).

                                        Not sure if this data is useful, seems to me that the brim prints OK at slower speeds with measured calibration there being in line with settings. So IMO that seems correct.

                                        The speeds don't vary after the first layer so the only thing that's changing is the PA as we go up the tower. And the first 20mm of Z seems OK in terms of measured filament usage. But starts to decrease after that. But then warns of too much filament?

                                        As I said it doesn't make sense to me.

                                        Hope this helps the bigger picture.

                                        Cheers
                                        Barry M

                                        Polar Duet3 Mini + 1HCL
                                        https://youtube.com/playlist?list=PLWjZVEdMv1BY82izahK45qKh-hp3NFkix
                                        Wanhao D4S: Duet2
                                        https://forum.duet3d.com/post/296755
                                        K40 Laser, Duet2
                                        https://forum.duet3d.com/post/312082
                                        Wanhao D5S
                                        https://www.youtube.com/CNCModellerUK

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          T3P3Tony administrators
                                          last edited by 15 Nov 2021, 22:23

                                          @cncmodeller you have your filament monitor configured as a pulse type not a magnetic type. If it is pulse type the the configured sensitivity looks wrong.

                                          www.duet3d.com

                                          undefined 1 Reply Last reply 15 Nov 2021, 22:38 Reply Quote 0
                                          136 out of 151
                                          • First post
                                            136/151
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA