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

    Filament Sensor on Expansion with 3.3beta1 and 3.3beta3

    Beta Firmware
    filament sensor filament monitor expansion firmware
    3
    10
    518
    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.
    • vali3dundefined
      vali3d
      last edited by

      Hello,

      I have issues with my filament sensors since the firmeware versions 3.3beta1
      The sensors are connected to expansion boards, together with the extruder motors.
      This setup did work on the firmeware 3.2, but since 3.3beta1 the input pins wont give back any signal (the filament sensor readout with M122 always says filament present). I have tried pluging a sensor and motor to the mainboard, which works fine. Other inputs like endstops in the expansions work fine.
      (all boards are 3.3beta3)

      Is this an known issue and will be fixed later on?

      greetings Valentin

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

        Can you provide your config.g and the results of M122 and M122 B1?

        Z-Bot CoreXY Build | Thingiverse Profile

        vali3dundefined 1 Reply Last reply Reply Quote 0
        • vali3dundefined
          vali3d @Phaedrux
          last edited by

          @phaedrux

          It looks like the individual board´s get it right. The sensor on 2.io2 should return no filament, the other three are loaded.

          3.5.2021, 16:26:06 M122 B2
          Diagnostics for board 2:
          Duet EXP3HC firmware version 3.3beta3 (2021-04-21 20:41:46)
          Bootloader ID: not available
          Never used RAM 158940, free system stack 0 words
          Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,88) CanAsync(notifyWait,0.0%,72) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,22.8%,63) MAIN(running,75.9%,383) AIN(delaying,1.3%,263), total 100.0%
          Last reset 00:01:53 ago, cause: software
          Last software reset at 2021-04-30 13:19, reason: AssertionFailed, available RAM 158940, slot 0
          Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00430000 BFAR 0xe000ed38 SP 0x2000378c Task MAIN Freestk 795 ok
          Stack: 00000544 0002eb3c 0002614f 42000400 00022387 20001c90 00000001 00000003 20001c8c 20001c7c 0001d30f 00000001 200037e0 00000001 000190a7 0001e49a 41000000 00000000 00026043 08020c02 00000001 00000000 11a80200 00000024 a300a5a5 20003c78 00000003
          Driver 0: position 0, 201.9 steps/mm, standstill, reads 51251, writes 13 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Driver 1: position 0, 201.9 steps/mm, standstill, reads 51253, writes 13 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Driver 2: position 0, 201.9 steps/mm, standstill, reads 51257, writes 13 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
          Peak sync jitter 11, peak Rx sync delay 178, resyncs 0, no step interrupt scheduled
          VIN: 24.3V, V12: 12.1V
          MCU temperature: min 28.6C, current 29.6C, max 29.6C
          Ticks since heat task active 0, ADC conversions started 113346, completed 113346, timed out 0, errs 0
          Last sensors broadcast 0x00000000 found 0 5 ticks ago, loop time 0
          CAN messages queued 108, send timeouts 0, received 1496, lost 0, free buffers 36, min 36, error reg 0
          dup 0, oos 0, bm 0, wbm 0
          === Filament sensors ===
          Interrupt 5726621 to 0us, poll 1 to 80us
          Driver 0: ok
          Driver 1: no filament
          Driver 2: ok

          3.5.2021, 16:25:51 M122 B1
          Diagnostics for board 1:
          Duet EXP3HC firmware version 3.3beta3 (2021-04-21 20:41:46)
          Bootloader ID: not available
          Never used RAM 158196, free system stack 0 words
          Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,88) CanAsync(notifyWait,0.0%,72) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,23.5%,63) MAIN(running,75.0%,301) AIN(delaying,1.5%,263), total 100.0%
          Last reset 00:01:38 ago, cause: software
          Last software reset data not available
          Driver 0: position 0, 80.0 steps/mm, standstill, reads 50783, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Driver 1: position 0, 80.0 steps/mm, standstill, reads 50786, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Driver 2: position 0, 201.9 steps/mm, standstill, reads 50787, writes 13 timeouts 0, SG min/max 0/0, steps req 0 done 0
          Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
          Peak sync jitter 10, peak Rx sync delay 178, resyncs 0, no step interrupt scheduled
          VIN: 24.1V, V12: 12.1V
          MCU temperature: min 28.0C, current 29.1C, max 29.1C
          Ticks since heat task active 172, ADC conversions started 98468, completed 98468, timed out 0, errs 0
          Last sensors broadcast 0x00000018 found 2 176 ticks ago, loop time 0
          CAN messages queued 1275, send timeouts 0, received 916, lost 0, free buffers 36, min 36, error reg 0
          dup 0, oos 0, bm 0, wbm 0
          === Filament sensors ===
          Interrupt 5726621 to 0us, poll 1 to 117us
          Driver 2: ok

          3.5.2021, 16:24:43 M122
          === Diagnostics ===
          RepRapFirmware for Duet 3 MB6HC version 3.3beta3 (2021-04-22 16:28:03) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
          Board ID: 08DJM-956L2-G43S4-6JTD8-3SS6J-9B7GH
          Used output buffers: 3 of 40 (19 max)
          === RTOS ===
          Static ram: 149960
          Dynamic ram: 94824 of which 0 recycled
          Never used RAM 109408, free system stack 200 words
          Tasks: NETWORK(ready,27.8%,226) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,281) Move(notifyWait,0.0%,202) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,350) TMC(notifyWait,7.6%,93) MAIN(running,64.0%,1114) IDLE(ready,0.4%,19), total 100.0%
          Owned mutexes:
          === Platform ===
          Last reset 00:00:30 ago, cause: software
          Last software reset at 2021-05-03 16:24, reason: User, GCodes spinning, available RAM 109416, slot 2
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Aux0 errors 0,0,0
          Aux1 errors 0,0,0
          Step timer max interval 128
          MCU temperature: min 36.2, current 36.9, max 36.9
          Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
          12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
          Driver 0: position 0, standstill, reads 36613, writes 14 timeouts 0, SG min/max 0/0
          Driver 1: position 0, standstill, reads 36614, writes 14 timeouts 0, SG min/max 0/0
          Driver 2: position 0, standstill, reads 36614, writes 14 timeouts 0, SG min/max 0/0
          Driver 3: position 0, standstill, reads 36614, writes 14 timeouts 0, SG min/max 0/0
          Driver 4: position 0, standstill, reads 36614, writes 14 timeouts 0, SG min/max 0/0
          Driver 5: position 0, standstill, reads 36614, writes 14 timeouts 0, SG min/max 0/0
          Date/time: 2021-05-03 16:24:42
          Slowest loop: 4.76ms; fastest: 0.05ms
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 25.0MBytes/sec
          SD card longest read time 3.0ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          === GCodes ===
          Segments left: 0
          Movement lock held by null
          HTTP is idle in state(s) 0
          Telnet is idle in state(s) 0
          File is idle in state(s) 0
          USB is idle in state(s) 0
          Aux is idle in state(s) 0
          Trigger is idle in state(s) 0
          Queue is idle in state(s) 0
          LCD is idle in state(s) 0
          SBC is idle in state(s) 0
          Daemon is idle in state(s) 0
          Aux2 is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Filament sensors ===
          Extruder 0 sensor: no filament
          Extruder 1 sensor: no filament
          Extruder 2 sensor: no filament
          Extruder 3 sensor: no filament
          === CAN ===
          Messages queued 309, send timeouts 0, received 436, lost 0, longest wait 9ms for reply type 6018, peak Tx sync delay 6, free buffers 49 (min 48)
          === Network ===
          Slowest loop: 3.33ms; fastest: 0.02ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
          HTTP sessions: 1 of 8

          • Ethernet -
            State: active
            Error counts: 0 0 1 0 0
            Socket states: 5 2 2 2 2 0 0 0

          config (2).g

          1 Reply Last reply Reply Quote 0
          • vali3dundefined
            vali3d
            last edited by

            I did another test just now, and they worked. I have no Idea why, but the M122 is still saying no filament on all 4 extruders.

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

              Can you update to RC1 and see if it's the same? Maybe a display bug in M122 output.

              Z-Bot CoreXY Build | Thingiverse Profile

              vali3dundefined 1 Reply Last reply Reply Quote 0
              • vali3dundefined
                vali3d @Phaedrux
                last edited by

                @phaedrux
                4.5.2021, 11:46:52 M122 B2
                Diagnostics for board 2:
                Duet EXP3HC firmware version 3.3RC1 (2021-04-29 10:20:51)
                Bootloader ID: not available
                Never used RAM 159212, free system stack 0 words
                Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,88) CanAsync(notifyWait,0.0%,72) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,23.2%,63) MAIN(running,75.5%,389) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0%
                Last reset 00:01:35 ago, cause: power up
                Last software reset at 2021-05-03 17:21, reason: AssertionFailed, available RAM 158940, slot 1
                Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00430000 BFAR 0xe000ed38 SP 0x2000378c Task MAIN Freestk 795 ok
                Stack: 00000544 0002eb3c 0002614f 42000400 00022387 20001c90 00000001 00000003 20001c8c 20001c7c 0001d30f 00000001 200037e0 00000001 000190a7 3a36d584 41200000 00000000 00026043 20000010 00000001 00000000 11a80200 00000024 a300a5a5 20003c78 00000001
                Driver 0: position 0, 201.9 steps/mm, standstill, reads 27958, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Driver 1: position 0, 201.9 steps/mm, standstill, reads 27961, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Driver 2: position 0, 201.9 steps/mm, standstill, reads 27964, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                Peak sync jitter 10, peak Rx sync delay 180, resyncs 0, no step interrupt scheduled
                VIN: 24.3V, V12: 12.1V
                MCU temperature: min 20.4C, current 24.6C, max 24.6C
                Ticks since heat task active 175, ADC conversions started 95944, completed 95944, timed out 0, errs 0
                Last sensors broadcast 0x00000000 found 0 180 ticks ago, loop time 0
                CAN messages queued 100, send timeouts 0, received 1270, lost 0, free buffers 36, min 36, error reg 0
                dup 0, oos 0, bm 0, wbm 0
                === Filament sensors ===
                Interrupt 5726621 to 0us, poll 1 to 80us
                Driver 0: ok
                Driver 1: no filament
                Driver 2: ok

                4.5.2021, 11:46:34 M122 B1
                Diagnostics for board 1:
                Duet EXP3HC firmware version 3.3RC1 (2021-04-29 10:20:51)
                Bootloader ID: not available
                Never used RAM 158468, free system stack 0 words
                Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,88) CanAsync(notifyWait,0.0%,72) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,23.3%,63) MAIN(running,75.3%,301) IDLE(ready,0.0%,40) AIN(delaying,1.4%,263), total 100.0%
                Last reset 00:01:18 ago, cause: power up
                Last software reset data not available
                Driver 0: position 0, 80.0 steps/mm, standstill, reads 61770, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Driver 1: position 0, 80.0 steps/mm, standstill, reads 61773, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Driver 2: position 0, 201.9 steps/mm, standstill, reads 61771, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0
                Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                Peak sync jitter 9, peak Rx sync delay 177, resyncs 0, no step interrupt scheduled
                VIN: 24.1V, V12: 12.1V
                MCU temperature: min 19.9C, current 23.6C, max 23.6C
                Ticks since heat task active 10, ADC conversions started 78355, completed 78355, timed out 0, errs 0
                Last sensors broadcast 0x00000018 found 2 14 ticks ago, loop time 0
                CAN messages queued 1020, send timeouts 0, received 732, lost 0, free buffers 36, min 36, error reg 0
                dup 0, oos 0, bm 0, wbm 0
                === Filament sensors ===
                Interrupt 5726621 to 0us, poll 1 to 117us
                Driver 2: ok

                4.5.2021, 11:46:29 M122
                === Diagnostics ===
                RepRapFirmware for Duet 3 MB6HC version 3.3RC1 (2021-05-01 09:12:50) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
                Board ID: 08DJM-956L2-G43S4-6JTD8-3SS6J-9B7GH
                Used output buffers: 1 of 40 (19 max)
                === RTOS ===
                Static ram: 150680
                Dynamic ram: 94824 of which 0 recycled
                Never used RAM 108688, free system stack 182 words
                Tasks: NETWORK(ready,27.6%,238) ETHERNET(notifyWait,0.1%,118) HEAT(delaying,0.0%,301) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,350) TMC(notifyWait,7.3%,93) MAIN(running,64.7%,1114) IDLE(ready,0.2%,29), total 100.0%
                Owned mutexes:
                === Platform ===
                Last reset 00:01:13 ago, cause: power up
                Last software reset at 2021-05-03 18:17, reason: User, GCodes spinning, available RAM 108672, slot 1
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x00
                Aux0 errors 0,0,0
                Aux1 errors 0,0,0
                Step timer max interval 127
                MCU temperature: min 19.1, current 31.3, max 31.6
                Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
                12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
                Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                Driver 0: position 0, standstill, reads 14259, writes 14 timeouts 0, SG min/max 0/0
                Driver 1: position 0, standstill, reads 14259, writes 14 timeouts 0, SG min/max 0/0
                Driver 2: position 0, standstill, reads 14259, writes 14 timeouts 0, SG min/max 0/0
                Driver 3: position 0, standstill, reads 14259, writes 14 timeouts 0, SG min/max 0/0
                Driver 4: position 0, standstill, reads 14260, writes 14 timeouts 0, SG min/max 0/0
                Driver 5: position 0, standstill, reads 14260, writes 14 timeouts 0, SG min/max 0/0
                Date/time: 2021-05-04 11:46:28
                Slowest loop: 4.80ms; fastest: 0.05ms
                === Storage ===
                Free file entries: 10
                SD card 0 detected, interface speed: 25.0MBytes/sec
                SD card longest read time 3.1ms, write time 0.0ms, max retries 0
                === Move ===
                DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === AuxDDARing ===
                Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === Heat ===
                Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                === GCodes ===
                Segments left: 0
                Movement lock held by null
                HTTP is idle in state(s) 0
                Telnet is idle in state(s) 0
                File is idle in state(s) 0
                USB is idle in state(s) 0
                Aux is idle in state(s) 0
                Trigger is idle in state(s) 0
                Queue is idle in state(s) 0
                LCD is idle in state(s) 0
                SBC is idle in state(s) 0
                Daemon is idle in state(s) 0
                Aux2 is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty.
                === Filament sensors ===
                Extruder 0 sensor: no filament
                Extruder 1 sensor: no filament
                Extruder 2 sensor: no filament
                Extruder 3 sensor: no filament
                === CAN ===
                Messages queued 697, send timeouts 0, received 992, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 4, free buffers 49 (min 48)
                === Network ===
                Slowest loop: 4.64ms; fastest: 0.02ms
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
                HTTP sessions: 1 of 8

                • Ethernet -
                  State: active
                  Error counts: 0 0 1 0 0
                  Socket states: 5 2 2 2 2 0 0 0
                dc42undefined 1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators @vali3d
                  last edited by

                  @vali3d do M591 D0, M591 D1, M591 D2 and M591 D3 return the correct status?

                  What type of filament sensors are they? Please show us the M591 lines in config.g that you use to configure them.

                  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
                  • vali3dundefined
                    vali3d
                    last edited by

                    @dc42

                    config (2).g

                    M591 D0 P1 C"1.io2.in" S1
                    M591 D1 P1 C"2.io1.in" S1
                    M591 D2 P1 C"2.io2.in" S1
                    M591 D3 P1 C"2.io3.in" S1

                    The sensors are simple switches (high signal when filament present).
                    Like I wirten, in the M122 B1/B2 the readout is correct.

                    3.5.2021, 16:26:06 M122 B2
                    Driver 0: ok
                    Driver 1: no filament
                    Driver 2: ok

                    3.5.2021, 16:25:51 M122 B1
                    Driver 2: ok

                    5.5.2021, 09:01:04 M591 D3
                    Simple filament sensor on pin 2.io3.in, enabled, output low when no filament, filament present: yes
                    5.5.2021, 09:00:59 M591 D2
                    Simple filament sensor on pin 2.io2.in, enabled, output low when no filament, filament present: no
                    5.5.2021, 09:00:56 M591 D1
                    Simple filament sensor on pin 2.io1.in, enabled, output low when no filament, filament present: yes
                    5.5.2021, 09:00:46 M591 D0
                    Simple filament sensor on pin 1.io2.in, enabled, output low when no filament, filament present: yes

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

                      @vali3d thanks, so it's just the M122 main board filament monitor summary that is wrong. I'll log this as a known issue for fixing in a future release.

                      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

                      vali3dundefined 1 Reply Last reply Reply Quote 0
                      • vali3dundefined
                        vali3d @dc42
                        last edited by

                        @dc42
                        at my first try, the sensors didn´t work(3.3beta1/3). One day later, without any changes they did work(3.3beta3and 3.3RC1). Since then they do work and only the M122 readout is wrong(3.3RC1).

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