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

    Filament sensor interface and actions

    Scheduled Pinned Locked Moved
    Gcode meta commands
    3
    4
    221
    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.
    • kb58undefined
      kb58
      last edited by kb58

      CoreXY, 3 Z axis, Duet3 6HC, v3.3, Tool Board v1.1, BondTech LGX + Mosquito hot end

      Using a clone of a Prusa sensor, it's connected to io2 on the toolboard:

      M591 D0 P2 C"121.io2.in" S1
      

      Checking it out using Settings > Object Model, it reports this when filament is present:

      8f7a1f68-9261-4c2e-a8e7-ebd0e7e56262-image.png

      When filament is not present:
      aef49c99-ff3e-4765-a418-5c2eaf824390-image.png

      Questions:

      1. Is this working correctly?
      2. Why isn't "filament present" changing state?
      3. If it is working correctly, how is the result used to pause a print and/or display a message?

      Scratch-built 350mmx350mm coreXY, linear rails, ballscrews, 3 Z axis, Duet3 6HC, v3.3, Tool Board v1.1, BondTech LGX + Mosquito hot end

      1 Reply Last reply Reply Quote 0
      • kb58undefined
        kb58
        last edited by

        Poking around here, I found this thread: https://forum.duet3d.com/topic/24529/problems-with-filament-error-g

        Scratch-built 350mmx350mm coreXY, linear rails, ballscrews, 3 Z axis, Duet3 6HC, v3.3, Tool Board v1.1, BondTech LGX + Mosquito hot end

        1 Reply Last reply Reply Quote 0
        • achrnundefined
          achrn
          last edited by

          Mine also has filamentPresent as false, even when filament is present.

          As to how it triggers pause or filament-error, I think the answer would be by some means that doesn't depend on that value (since it does pause - at least, mine does, the problems in the cited thread aren't to do with whether the filament out actions are triggered).

          While sensors.filamentMonitors[].filamentPresent is in the RRF object model documentation at https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation it is not in the DSF documentation at https://duet3d.github.io/DuetSoftwareFramework/api/DuetAPI.ObjectModel.FilamentMonitor.html. However, it is in the LaserFilamentMonitor class at https://duet3d.github.io/DuetSoftwareFramework/api/DuetAPI.ObjectModel.LaserFilamentMonitor.html. My guess would therefor be that it's a property not used or updated by a simple filament monitor, but is used or updated by the laser filament monitor.

          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @achrn
            last edited by dc42

            @achrn and @kb58, filamentPresent was removed from the object model in RRF 3.2 as documented in the change list. Use the "status" field instead.

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