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

    Random 'sensorError' on MFM

    Scheduled Pinned Locked Moved Unsolved
    Filament Monitor
    2
    6
    344
    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.
    • PetrKroupaundefined
      PetrKroupa
      last edited by

      What is "Extruder 0 reported 'sensorError' " ? It is random pause print and in log is this mesage. After resume print, no problem. Sometimes not happend 3 days. Sometimes two times per day. 3.4 beta 6. Ideas?

      2021-12-17 16:21:42 Event logging started
      2021-12-17 16:22:13 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 131 agc 94, measured sensitivity 24.99mm/rev, min 98% max 102% over 1638.1mm
      2021-12-17 17:36:51 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 130 agc 98, measured sensitivity 25.21mm/rev, min 97% max 104% over 14297.0mm
      2021-12-17 18:11:30 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 133 agc 96, measured sensitivity 25.25mm/rev, min 97% max 104% over 22962.7mm
      2021-12-17 18:48:11 Resume state saved
      2021-12-17 18:48:11 Extruder 0 reported 'sensorError'
      2021-12-17 18:48:14 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 131 agc 98, measured sensitivity 25.26mm/rev, min 97% max 105% over 31632.6mm
      2021-12-17 18:48:14 filament error
      2021-12-17 18:48:14 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 131 agc 98, measured sensitivity 25.26mm/rev, min 97% max 105% over 31632.6mm
      2021-12-17 18:48:20 Printing paused at X113.7 Y193.1 Z3.5
      2021-12-17 18:48:34 Printing resumed
      2021-12-17 18:48:34 Printing resumed
      2021-12-17 19:32:58 G10 P0 S242
      
      

      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
      • Phaedruxundefined Phaedrux marked this topic as a question
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you share your sensor config?
        What does it show if you send M591 D0 after it gives the error?

        Is your filament monitor connected to the same board as the extruder motor?

        Z-Bot CoreXY Build | Thingiverse Profile

        PetrKroupaundefined 1 Reply Last reply Reply Quote 0
        • PetrKroupaundefined
          PetrKroupa @Phaedrux
          last edited by PetrKroupa

          @phaedrux - Since I have been dealing with this for some time, it has worked for me to insert "M591 D0" directly into filament-error.g. Then I know exactly what the values were at the time of the error. When you look at the log from my first post, at 16:22, 17:36 and 18:11 I entered "M591 D0" manually to know how the sensor is doing. And then 18:48 an error occurred. Since I was sitting nearby, I immediately gave a resume print. And the printing was completed without any problems. Therefore, I would like to know what "sensor error" means. What is the trigger for this error.

          filament-error0.g

          M83            ; relative extruder moves
          G1 E-10 F3600  ; retract 10mm of filament
          G91            ; relative positioning
          G1 Z25 F360     ; lift Z by 5mm
          G90            ; absolute positioning
          G1 X50 Y50 F6000 ; go to X=0 Y=0;
          set global.beepbeep1 = 1
          
          set global.fuufuu1 = fans[0].actualValue
          M106 S0
          
          
          M591 D0
          M118 P0 S"filament error" L2
          

          MFM.jpg

          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
          • PetrKroupaundefined
            PetrKroupa
            last edited by

            Does anyone know what is the trigger for this error?

            In the meantime, I try to replace the hall sensor on the board. It can be bought cheaply. I solder out old and solder in new. The old looked a slight scratch from the magnet. It probably rubbed against the magnet for a while during assembly. I gently underlaid the screws to make the AGC 95 and we'll see how the sensor behaves.

            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
            • PetrKroupaundefined PetrKroupa referenced this topic
            • PetrKroupaundefined
              PetrKroupa
              last edited by

              After several prints, it turned out that nothing had changed. I also uploaded beta 7 if anything doesn't change. Best of all, the sensor works perfectly, no stopping for no reason. Except for "sensor error".

              I think the only one who knows the answer is @dc42 .

              2021-12-30 20:21:15 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 125%, check printing moves every 8.0mm, version 4, mag 130 agc 98, measured sensitivity 25.14mm/rev, min 97% max 104% over 59288.5mm
              2021-12-31 00:26:34 Error: Filament error on extruder 0: sensorError
              2021-12-31 00:26:38 Resume state saved
              

              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
              • PetrKroupaundefined
                PetrKroupa
                last edited by

                I will have to try to replace the whole sensor. It's weird.

                Here is the event log, including the log from 1LC

                2021-12-31 17:39:33 Error: Filament error on extruder 0: sensorError
                2021-12-31 17:39:33 Resume state saved
                2021-12-31 17:39:37 Printing paused at X328.0 Y217.3 Z9.5
                2021-12-31 17:39:37 Printing paused at X328.0 Y217.3 Z9.5
                2021-12-31 17:39:37 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 25.00mm/rev, allow 50% to 125%, check printing moves every 10.0mm, version 4, mag 129 agc 95, measured sensitivity 25.11mm/rev, min 97% max 104% over 89544.7mm
                2021-12-31 17:39:37 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 25.00mm/rev, allow 50% to 125%, check printing moves every 10.0mm, version 4, mag 129 agc 95, measured sensitivity 25.11mm/rev, min 97% max 104% over 89544.7mm
                2021-12-31 17:39:38 Diagnostics for board 121:
                Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7 (2021-12-16 12:25:01)
                Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
                Never used RAM 2188, free system stack 2717 words
                Tasks: Move(notifyWait<null>,11.3%,91) HEAT(notifyWait<null>,5.6%,95) CanAsync(notifyWait<null>,0.0%,59) CanRecv(notifyWait<null>,2.3%,74) CanClock(notifyWait<null>,0.4%,65) ACCEL(notifyWait<null>,0.0%,61) TMC(notifyWait<null>,59.6%,57) MAIN(running<null>,381.7%,351) IDLE(ready<null>,0.0%,26) AIN(delaying<null>,98.4%,142), total 559.3%
                Last reset 08:20:10 ago, cause: VDD brownout
                Last software reset data not available
                Driver 0: pos 39923177, 420.0 steps/mm,standstill, SG min 0, read errors 14, write errors 0, ifcnt 13, reads 27915, writes 0, timeouts 16, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 39412543 done 39412543
                Moves scheduled 414732, completed 414732, in progress 0, hiccups 0, step errors 0, maxPrep 654, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                Peak sync jitter 0/6, peak Rx sync delay 230, resyncs 0/0, no step interrupt scheduled
                VIN voltage: min 27.9, current 28.0, max 28.1
                MCU temperature: min 38.7C, current 52.7C, max 58.5C
                Last sensors broadcast 0x00000002 found 1 182 ticks ago, 0 ordering errs, loop time 0
                CAN messages queued 495202, send timeouts 0, received 614292, lost 0, free buffers 37, min 35, error reg 0
                dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 751, adv 35393/104433
                Accelerometer: LIS3DH, status: 00
                I2C bus errors 0, naks 0, other errors 0
                === Filament sensors ===
                Interrupt 4 to 40us, poll 8 to 4836us
                Driver 0: pos 140.27, errs: frame 89 parity 0 ovrun 0 pol 0 ovdue 0
                2021-12-31 17:39:38 filament error
                2021-12-31 17:39:38 Diagnostics for board 121:
                Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7 (2021-12-16 12:25:01)
                Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
                Never used RAM 2188, free system stack 2717 words
                Tasks: Move(notifyWait<null>,11.3%,91) HEAT(notifyWait<null>,5.6%,95) CanAsync(notifyWait<null>,0.0%,59) CanRecv(notifyWait<null>,2.3%,74) CanClock(notifyWait<null>,0.4%,65) ACCEL(notifyWait<null>,0.0%,61) TMC(notifyWait<null>,59.6%,57) MAIN(running<null>,381.7%,351) IDLE(ready<null>,0.0%,26) AIN(delaying<null>,98.4%,142), total 559.3%
                Last reset 08:20:10 ago, cause: VDD brownout
                Last software reset data not available
                Driver 0: pos 39923177, 420.0 steps/mm,standstill, SG min 0, read errors 14, write errors 0, ifcnt 13, reads 27915, writes 0, timeouts 16, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 39412543 done 39412543
                Moves scheduled 414732, completed 414732, in progress 0, hiccups 0, step errors 0, maxPrep 654, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                Peak sync jitter 0/6, peak Rx sync delay 230, resyncs 0/0, no step interrupt scheduled
                VIN voltage: min 27.9, current 28.0, max 28.1
                MCU temperature: min 38.7C, current 52.7C, max 58.5C
                Last sensors broadcast 0x00000002 found 1 182 ticks ago, 0 ordering errs, loop time 0
                CAN messages queued 495202, send timeouts 0, received 614292, lost 0, free buffers 37, min 35, error reg 0
                dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 751, adv 35393/104433
                Accelerometer: LIS3DH, status: 00
                I2C bus errors 0, naks 0, other errors 0
                === Filament sensors ===
                Interrupt 4 to 40us, poll 8 to 4836us
                Driver 0: pos 140.27, errs: frame 89 parity 0 ovrun 0 pol 0 ovdue 0
                

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