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

    [RRF3.3B2] Possibly bug with filamentmonitors[x].status

    Scheduled Pinned Locked Moved
    Beta Firmware
    1
    1
    108
    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.
    • lahn92undefined
      lahn92
      last edited by

      i updated from 3.1.1 to 3.2.2 earlier today and encountered a problem with the way i use a filament sensor i then tried going to 3.3B2 to see if the problem was the same and it is.

      i only use my filament sensor as a check when i switch filament with a MMU2 and as such require it to be disabled in the M591 command
      so my command is M591 D0 P1 C"xstop" S0

      and in version 3.1.1 when checking with sensors.filamentMonitors[0].filamentPresent
      it worked just fine.
      but in 3.2.2 and 3.3B2 where the object model har changed to
      sensors.filamentMonitors[0].status

      it will only show the status as "ok" as long as the filament sensor is disabled in M591

      to get sensors.filamentMonitors[0].status working i have to enable the monitor in M591 and that will give me problems during printing as a retraction will sometimes trigger it.

      picture show my console where the status command only shows as "noFilament" when i enable the monitor in M591
      even when a "M591 D0" command show it as no filament present
      consol.png

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