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

    Webcontrol and filament sensor

    Scheduled Pinned Locked Moved Solved
    Duet Web Control
    4
    12
    657
    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.
    • Deluxe 600undefined
      Deluxe 600
      last edited by

      Hi, I wanted to set up a filament sensor using a Prusa MINi fil sensor just because i had one.
      But when i tried to test it to see if the printer detects it, i noticed that the tab "machine properties" had vanished.Im using Webcontrol 3.2.0 and duet 2 ethernet FW 3.0 .

      The second thing is that i dont know how to set up the fil sensor properly
      Sensor is just an optical gate so i guess its like a regular switch. Its pluged into the E0 endstop and all i want is for it to pause the print when it detects a run out.

      Here is the config
      ;Filament Runout Sensor
      M950 J0 C"!^e0Stop" ; create switch pin
      M581 P0:1 T2 S1 R1 ; run trigger2.g to pause if filament has run out during SD card printing

      Thank you and have a great day.

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        The machine properties tab has been moved to a plugin and I think will be included with the 3.3 release. Otherwise it can be found here: https://github.com/Duet3D/DSF-Plugins/tree/master/EndstopsMonitor

        In the meantime you can still check endstop status with M119.

        For a filament sensor you'd want to use M591 instead of M581.

        https://duet3d.dozuki.com/Wiki/Gcode#Section_M591_Configure_filament_sensing

        Z-Bot CoreXY Build | Thingiverse Profile

        Deluxe 600undefined 1 Reply Last reply Reply Quote 0
        • Deluxe 600undefined
          Deluxe 600 @Phaedrux
          last edited by

          @phaedrux Thank you for the reply.

          But so far i was unsucesful.
          I have tried to install the plugin but for some reason it does not want to work.
          I have exported the "Monitor Plugin" to the src/plugin folder and even modified "Index.js" as instructed, but it still doesnt show up in the "plugins" folder in webcontroll.
          Plugin install.png

          Meanwhile i also tried to setup the fil sensor but that too didnt manage to get it working i will send the config file also if you could please take a look if i have it setup corectly.
          Thank you very much.

          ; Drives
          M569 P0 S1 ; Drive 0 goes forwards
          M569 P1 S1 ; Drive 1 goes forwards
          M569 P2 S1 ; Drive 2 goes forwards
          M569 P3 S1 ; Drive 3 goes forwards
          M584 X0 Y1 Z2 E3 ; set drive mapping
          M350 Z8 X16 Y16 I1 ; Configure microstepping with interpolation
          M350 E32 I0 ; Configure microstepping without interpolation
          M92 X50 Y50 Z400 E280 ; Set steps per mm
          M566 X480 Y480 Z2 E270 ; Set maximum instantaneous speed changes (mm/min)
          M203 X12000 Y12000 Z720 E7200 ; Set maximum speeds (mm/min)
          M201 X1000 Y1000 Z125 E5000 ; Set accelerations (mm/s^2)
          M906 X1500 Y1500 Z2000 E700 I1 ; Set motor currents (mA) and motor idle factor in per cent
          M84 S5 ; Set idle timeout

          ; Axis Limits
          M208 X0 Y0 Z0 S0 ; Set axis minima
          M208 X545 Y545 Z700 S0 ; Set axis maxima

          ; Endstops
          M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop
          M574 Y2 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
          ;M574 Z1 S2 ; configure Z-probe endstop for low end on Z

          ; Z-Probe
          M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
          M558 P9 C"^zprobe.in" A5 H4 F100 T6000 ; set Z probe type to bltouch and the dive height + speeds
          G31 X0 Y0 Z0.9 ; set Z probe trigger value, offset and trigger height
          M557 X0:500 Y40:500 S100:100 ; define mesh grid

          ;Filament Runout Sensor
          M950 J0 C"!e0stop" ; create switch pin
          M591 P2 C"e0stop" S1 D0 ; filament monitor connected to E0 endstop

          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
          M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
          M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
          M140 H0 ; map heated bed to heater 0
          M143 H0 S100 ; set temperature limit for heater 0 to 100C
          M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
          M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
          M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 S0.5 H1 T60 ; set fan 1 value. Thermostatic control is turned on
          M950 F2 C"fan2" Q500 ; create fan 2 (bed) on pin fan2 and set its frequency
          M106 P2 S1 H0 T50

          ; Tools
          M563 P0 D0 H1 ; Define tool 0
          G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
          G10 P0 R20 S0 ; Set initial tool 0 active and standby temperatures to 0C

          ;LED control
          M950 P5 C"e1heat" ;set e1heat as a GPIO output pin
          M501
          M107

          Phaedruxundefined MintyTreborundefined 2 Replies Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator @Deluxe 600
            last edited by

            @deluxe-600 said in Webcontrol and filament sensor:

            ;Filament Runout Sensor
            M950 J0 C"!e0stop" ; create switch pin
            M591 P2 C"e0stop" S1 D0 ; filament monitor connected to E0 endstop

            I don't think you need the M950 here and that may be your problem.

            Can you send M98 P"config.g" and see if it shows any syntax errors.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • MintyTreborundefined
              MintyTrebor @Deluxe 600
              last edited by MintyTrebor

              @deluxe-600 I maybe wrong, but I get the impression from your post that you did not compile the endstops plugin before you attempted to install it. Copying the files as you describe will not typically work. Unless you have a dev environment already setup / or are willing to set one up, then I think you have 2 options:

              1: Enable the object model browser built-in plugin and use it to check if the sensor is working as expected (you will have to refresh it each time you want to check status).
              2: Use BtnCmd to make your own endstops monitor in the browser.

              Option 1 would be the easiest as its already available with no additional work, and unless you want a permanent endstop monitor, it will probably work OK. You could also be cheeky and ask if anyone on the forum has a pre-compiled zip of the endstops monitor @Phaedrux linked to. Or just install the pre-compiled version I completely missed as @jay_s_uk says below. (even better!!)

              NodeDSF - Native Node-Red integration with Duet boards.
              BtnCmd - Customise DWC with user defined buttons/layouts/panels (DWC Plugin)
              ReleaseMgr - Duet update info inside DWC.
              Repo

              jay_s_ukundefined 1 Reply Last reply Reply Quote 2
              • jay_s_ukundefined
                jay_s_uk @MintyTrebor
                last edited by

                There is a release available here https://github.com/Duet3D/DSF-Plugins/releases

                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

                Phaedruxundefined Deluxe 600undefined 2 Replies Last reply Reply Quote 1
                • Phaedruxundefined
                  Phaedrux Moderator @jay_s_uk
                  last edited by

                  @jay_s_uk Thanks. I should be using that link instead.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  Deluxe 600undefined 2 Replies Last reply Reply Quote 0
                  • Deluxe 600undefined
                    Deluxe 600 @Phaedrux
                    last edited by

                    @phaedrux And it works 🙂 . Thank you guys. Now only to solve the filament sensor, working on it right now. Im trying to use the sensor from Prusa MINI but it seems to need 5V power. So i conected the power pin one the sensor to the always on FAN that has 5V.

                    1 Reply Last reply Reply Quote 0
                    • Deluxe 600undefined
                      Deluxe 600 @jay_s_uk
                      last edited by

                      @jay_s_uk It works! Thank you 🙂 . But the filament sensor doesnt show up, thats strange isnt it? I just have X,Y,Z endstops in the "ENDSTOPS" page

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

                        @deluxe-600 filament sensors are different to endstops and that's why they don't show up

                        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
                        • Deluxe 600undefined
                          Deluxe 600 @Phaedrux
                          last edited by

                          @phaedrux Never mind i figured it out.
                          For anyone wondering the gcode that worked is M591 P1 C"e0stop" S1 D0

                          Thank you all for the help, you are the best 🙂

                          Phaedruxundefined 1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator @Deluxe 600
                            last edited by

                            Sending M591 by itself will report info on the sensor.

                            Z-Bot CoreXY Build | Thingiverse Profile

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