25.95mm/rev, min -33% max 162% over 9615.6mm



  • Duet3D rotating magnet filament monitor

    M122
    === Filament sensors ===
    Extruder 0: pos 185.62, ok, measured sens 25.97mm/rev min -33% max 162% over 9456.6mm, errs: frame 0 parity 0 ovrun 0 pol 6 ovdue 0

    M591 D0
    Duet3D rotating magnet filament monitor v2 on input 3, disabled, sensitivity 24.61mm/rev, allow 80% to 130%, check every 3.0mm, current pos 342.4, measured sensitivity 25.95mm/rev, min -33% max 162% over 9615.6mm

    M591 D0 P3 C3 S1 R-35:166 L25.95 E3.0 ; <<--- correct syntax given output of test print??

    I dont think M591 likes "-35" as entered. Subsequent prints after making the filament detection active "S1" still falsely trigger pauses for filament issues. I'm I doing something wrong??



  • @nuroo I am experiencing difficulties too with the rotating magnet filament monitor (see https://forum.duet3d.com/topic/11591/rotating-magnet-filament-monitor-frame-errors) and I assume it has something to do with communication errors between the sensor and the duet mainboard.

    Your M122 line clearly shows

    errs: [...] pol 6 [...]
    

    I am getting

    errs: frame 10 [...] pol 2 [...]
    

    Maybe @dc42 can have a look at your problem, too?
    I'm eagerly awaiting resolution.
    It is quite frustrating to have the filament monitor installed and not usable at the same time.


  • administrators

    Please can you both confirm what firmware revision you are using on the Duet. Also, please post photos showing the location of the filament sensor relative to the extruder drive in the filament path.



  • @dc42 I'm running

    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04RC1 running on Duet WiFi 1.02 or later
    

    In fact, it's a Duet Wifi 1.04.

    Photo of the sensor arrangement below.
    0_1567192514018_IMG_0557.jpeg



  • thanks for chiming in @themelle.

    @dc42 , thank you sir from your response.
    Here is the info you requested:
    Duet Web Control 2.0.0-RC7
    Board: Duet2 pcb revision 1.04c + DueX5
    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.03 (2019-06-13b2)
    Duet WiFi Server Version: 1.23

    0_1567201994623_20190830_174405.jpg
    0_1567202016926_20190830_174419.jpg



  • Also had an issue today. once per print.
    Extruder 0 reported too much movement. Print paused.

    First time:
    Extruder 0: pos 153.28, ok, measured sens 24.51mm/rev min 85% max 118% over 272.5mm, errs: frame 7 parity 0 ovrun 0 pol 0 ovdue 0

    2nd time:
    Extruder 0: pos 92.81, ok, measured sens 22.91mm/rev min 77% max 120% over 1027.5mm, errs: frame 7 parity 0 ovrun 0 pol 0 ovdue 0

    I'm using this in my config.g
    M591 D0 P3 C3 S1 R70:130 L24.8 E3.0

    Ended up disabling monitoring and no issues.
    Firmware:
    Duet Web Control 2.0.0-RC6
    Duet Ethernet 1.02 or later + DueX5
    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.03 (2019-06-13b2)

    My filament path pictures:
    1_1567211636494_Screenshot 2019-08-30 20.32.36.png 0_1567211636493_Screenshot 2019-08-30 20.32.28.png



  • more data:
    M591 D0
    Duet3D rotating magnet filament monitor v2 on input 3, disabled, sensitivity 24.94mm/rev, allow 80% to 130%, check every 3.0mm, current pos 149.4, measured sensitivity 25.30mm/rev, min 0% max 114% over 11368.0mm


  • administrators

    @nuroo with that filament path - that might be the range of what the filament monitor is actually seeing as there will be loads of elasticity in the feed tube. short retractions probably hardly move the monitor. Have you tried with it close to the extruder like @themelle



  • @T3P3Tony The measured maximum value may be quite accurate, but 0 or negative numbers as minimum values do not really make any sense (at least to me), do they? 😉
    As @nuroo and me are having comparable issues (min values way to low, frame and/or pol errors in sensor communication) with different sensor placements I assume we are either missing something fundamental setup-wise, or there is an issue with the sensor itself, the way it is wired up, or how robust the firmwares' communications portions are. I do have high hopes to resolve those issues with you and @dc42 within an acceptable time frame, and in turn may contribute to make the Duet rotating magnet sensor more reliable for every user out there.



  • Hmm maybe I shouldn’t have just ordered one 😬



  • @samlogan87 Of course you should - the more of it in the wild, the better to resolve any random issues. It's a quite well designed product, and I am confident that it will perform as expected, once we have a larger user base and therefore more feedback as to what works and what (and more importantly: why) not.



  • Yeah I do agree, it’s more just if changes need to be made to the firmware on the sensor I am a bit screwed. I am really keen to get one so I guess we will see what happens when it arrives

    Regards
    Sam



  • @T3P3Tony im not sure I want to move the sensor above extruder. Certainly not ideal for a corexy setup. Already moving the mass of extruder, stepper motor, hotend etc around..... I didnt realize this sensor needed to be close to the extruder when I bought it. Is that requirement listed on product page?
    Can we not account for different setups in firmware with options for a setup like this.



  • @nuroo I will be in the same boat. Mine will have to go at the end of 650mm of tube. I am running a flex3drive and mounting the sensor on the carriage with the drive tube in the way will be impossible

    Regards
    Sam


  • administrators

    The filament monitor must be right next to the extruder drive input or output. Any other arrangement allows the filament to flex too much in the tubing between the two, in particular when the direction of motion reverses.



  • Well ok. I need to make an extension and try again. I wish this requirement was noted to customer on product page or wiki. I'll report back.



  • New Setup
    0_1567380530674_20190901_185722.jpg

    === Filament sensors ===
    Extruder 0: pos 188.09, ok, measured sens 24.89mm/rev min 95% max 103% over 1015.3mm, errs: frame 0 parity 0 ovrun 0 pol 1 ovdue 0

    M591 D0
    Duet3D rotating magnet filament monitor v2 on input 3, disabled, sensitivity 24.80mm/rev, allow 70% to 130%, check every 3.0mm, current pos 44.6, measured sensitivity 24.90mm/rev, min 95% max 103% over 1021.3mm

    much better numbers, but will I get false positives when I enable sensor?
    M591 D0 P3 C3 S1 R100:110 L24.90 E3.0 ;



  • 2 successful prints, no false positives with new setup.

    M591 D0 P3 C3 S1 R90:110 L24.96 E3.0 ;

    now to try a real filament outage



  • @nuroo Congratulations on getting it to work as intended!

    Now I'm left alone again with my "frame errors"/"sensor has stopped working" problem.
    May try to send it back to Filastruder as I am out of ideas now 😞


  • administrators

    @nuroo said in 25.95mm/rev, min -33% max 162% over 9615.6mm:

    Well ok. I need to make an extension and try again. I wish this requirement was noted to customer on product page or wiki. I'll report back.

    I am glad you got it working and thanks for the feedback, i have updated the installation section of the documentation to note the requirement: https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_RotatingMagnetVersion#Section_Installation

    @themelle i think asking filastruder to swap it will be a good test to see if this is a board that passed testing but is marginal in your setup.



  • @t3p3tony Thanks for your honest feedback.
    May I direct Filastruder support to your post confirming a warranty swap?


  • administrators

    @themelle yes



  • @t3p3tony Thank you!



  • Well I thought I was good to go with correct setup.
    2 small 1 hour long prints no false positives. 11hour print - false trigger to little movement, about 5 hours in. Had to disable sensor so I didn't have to sit there having to keep resuming print.



  • Are there any other troubleshooting measures I could try?


Log in to reply