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

    Laser filament monitor frame errors with 3.6rc1 but not 3.6beta4

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    2
    6
    150
    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.
    • Adrian52undefined
      Adrian52
      last edited by

      I am getting high numbers of frame errors with a laser filament monitor under 3.6rc1 on my delta with standalone duet2wifi

      06/03/2025, 15:42:03 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-rc.1 (2025-02-28 14:56:47) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 1 of 26 (21 max)
=== RTOS ===
Static ram: 24016
Dynamic ram: 68004 of which 12 recycled
Never used RAM 17908, free system stack 108 words
Tasks: NETWORK(1,ready,17.3%,195) LASER(5,nWait 6,1.4%,214) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,4.2%,263) MAIN(1,running,77.1%,836) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:44:08 ago, cause: software
Last software reset at 2025-02-28 19:38, reason: User, Gcodes spinning, available RAM 25988, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 10.2ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 419, maxWait 655163ms, bed comp in use: none, height map offset 0.000, hiccups added 0/69 (2.20ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 104132.00/104132/0.00 104132.00/104132/-0.00 104132.00/104132/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 607467, completed 607467, LaErrors 0, Underruns [0, 0, 0]
Segments left 0
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
=== Filament sensors ===
Driver 11: pos 0.00, brightness 20, shutter 131, errs: frame 31209 parity 0 ovrun 0 pol 0 ovdue 0
=== Network ===
Slowest loop: 204.68ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 39404
MAC address 5c:cf:7f:2c:24:6b
IP address 192.168.1.16
Signal strength -50dBm, channel 8, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

      the same print with 3.6beta4 does not show this effect

      06/03/2025, 13:54:14 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.4 (2025-02-11 09:50:40) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 1 of 26 (19 max)
=== RTOS ===
Static ram: 24016
Dynamic ram: 68468 of which 12 recycled
Never used RAM 17300, free system stack 108 words
Tasks: NETWORK(1,ready,15.2%,181) LASER(5,nWait 6,1.3%,214) HEAT(3,nWait 5,0.1%,292) Move(4,nWait 5,3.8%,239) MAIN(1,running,79.5%,745) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:53:31 ago, cause: software
Last software reset at 2025-02-28 19:38, reason: User, Gcodes spinning, available RAM 25988, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 9.9ms, write time 4.2ms, max retries 0
=== Move ===
Segments created 425, maxWait 1215359ms, bed comp in use: none, height map offset 0.000, hiccups added 0/123 (4.02ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 104132.00/104132/0.00 104132.00/104132/-0.00 104132.00/104132/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 607474, completed 607474, LaErrors 0, Underruns [0, 0, 0]
Segments left 0
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G4 S90" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
=== Filament sensors ===
Driver 11: pos 0.00, brightness 27, shutter 102, errs: frame 0 parity 0 ovrun 0 pol 1 ovdue 0
=== Network ===
Slowest loop: 52.48ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 36000
MAC address 5c:cf:7f:2c:24:6b
IP address 192.168.1.16
Signal strength -47dBm, channel 8, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

      I see 1-2 thousand frame errors if I do an M122 after switching on and homing the printer, but before doing any printing..

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

        @Adrian52 thanks for reporting this. I suspect that it is caused by enabling debouncing of inputs on Duet 2 and Duet 3 6HC and 6XD in rc1. I'll disable debouncing on filament monitor inputs in the next build.

        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

        Adrian52undefined 1 Reply Last reply Reply Quote 0
        • Adrian52undefined
          Adrian52 @dc42
          last edited by

          @dc42 Thank you. I dont know if its relevant, but on my old fuseless duet2wifi, I followed your suggestion of several years ago to use the lcd input for the laser filament monitor:
          M591 D0 P5 C"connlcd.encb" R01:300 E10 L0.65 S1 A0
          It has been working very reliably since then.

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

            @Adrian52 please try the firmware at https://www.dropbox.com/scl/fo/0xdvvzgqfrs5abyk75ss8/AL3i6s7z9UacEGYsxiR7pXw?rlkey=xpm61w2jlyqlawwjzy4zsq2lt&dl=0. Use it with caution because I don't have a Duet 2 machine to test it on. I have disabled debouncing on filament monitor inputs in this build.

            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

            Adrian52undefined 1 Reply Last reply Reply Quote 0
            • Adrian52undefined
              Adrian52 @dc42
              last edited by

              @dc42 Thank you - that seems to have fixed it. Here is an M122 if you want to check anything. Did not notice anything untoward during this print.

              07/03/2025, 13:51:42 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-rc.1+1 (2025-03-07 09:35:55) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 1 of 26 (19 max)
=== RTOS ===
Static ram: 24016
Dynamic ram: 68004 of which 12 recycled
Never used RAM 9244, free system stack 108 words
Tasks: NETWORK(1,ready,17.5%,181) LASER(5,nWait 6,1.5%,214) HEAT(3,nWait 5,0.1%,313) Move(4,nWait 5,5.7%,243) MAIN(1,running,75.1%,836) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:45:51 ago, cause: software
Last software reset at 2025-02-28 19:38, reason: User, Gcodes spinning, available RAM 25988, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 12.6ms, write time 7.4ms, max retries 0
=== Move ===
Segments created 780, maxWait 121347ms, bed comp in use: none, height map offset 0.000, hiccups added 0/45 (1.43ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 104132.00/104132/0.00 104132.00/104132/-0.00 104132.00/104132/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 327303, completed 327303, LaErrors 0, Underruns [0, 0, 0]
Segments left 0
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
=== Filament sensors ===
Driver 11: pos 0.00, brightness 15, shutter 85, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== Network ===
Slowest loop: 201.64ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 35964
MAC address 5c:cf:7f:2c:24:6b
IP address 192.168.1.16
Signal strength -50dBm, channel 8, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @Adrian52
                last edited by

                @Adrian52 thanks for confirming that.

                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
                • dc42undefined dc42 marked this topic as a question
                • dc42undefined dc42 has marked this topic as solved
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA