Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. omtek
    • Profile
    • Following 0
    • Followers 0
    • Topics 8
    • Posts 64
    • Best 8
    • Controversial 0
    • Groups 0

    omtek

    @omtek

    9
    Reputation
    6
    Profile views
    64
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location NY, USA

    omtek Unfollow Follow

    Best posts made by omtek

    • RE: Question about Sammy-C21 board

      @fcwilt

      For cloning the repositories, I use git from the command prompt. I believe you can also use Github Desktop if you're more comfortable with a GUI, though I've never used it personally. You need to install git or Github Desktop for your OS if you haven't already.

      For each repository, there is a 32145175-d8bf-45d0-9682-c4c978beaad7-image.png button. If you click it'll have the particular URL for cloning the repository using the command line, or a button for opening in Github Desktop.

      So for example, to clone the 3.5-dev branch of Duet3Expansion, I open my terminal inside the workspace folder I created and type:

      git clone --branch 3.5-dev https://github.com/Duet3D/Duet3Expansion.git

      Do that for each of the repositories above, changing the URL for each, and placing them all into the same folder.

      In the end, it should look something like this:

      e114b181-6cf6-421b-8975-0d37c376262b-image.png

      After that, open Eclipse. It should ask you to select a directory as a workspace. Point it to the folder with your cloned repositories.

      Then to the File menu, and select Open Projects from File System....

      Set the Import Source is your workspace folder and it should show your folders.
      9a91afb4-9cc7-4c48-b0d9-29a91878d5d7-image.png

      Click finish and you should see everything in Eclipse

      d84b74b6-61f9-48da-b0ad-bda24d718b34-image.png

      Hope this helps!

      posted in Firmware developers
      omtekundefined
      omtek
    • RE: Raspberry Pi OS - Bullseye

      @chrishamm That was the problem!

      pi@legionXY:~ $ sudo systemctl enable duetpluginservice-root
      Created symlink /etc/systemd/system/multi-user.target.wants/duetpluginservice-root.service → /lib/systemd/system/duetpluginservice-root.service.
      pi@legionXY:~ $ sudo systemctl start duetpluginservice-root
      pi@legionXY:~ $
      

      62fc4fb4-1710-426f-8d00-edc6d87c57bb-image.png

      Success!

      posted in General Discussion
      omtekundefined
      omtek
    • RE: 3.5.1 - 'Error: Pop(): stack underflow on Aux'

      This appears to be fixed with v3.5.2. I'm no longer getting the error message using the above steps. Additionally the 3 macros in the upper right corner of the 'Control' page have returned.

      Marking as solved.

      posted in Beta Firmware
      omtekundefined
      omtek
    • RE: Question about Sammy-C21 board

      @fcwilt I'm using a Sammy-C21 on a CannedERCF and created a build environment for compiling firmware so I'll try to remember the steps:

      Towards the bottom of the Duet3Expansion repository are the links to three packages you need to download (gcc cross compiler, the Eclipse IDE, and the GNU Arm Eclipse bundle)

      Install them.

      When installing Eclipse you want Eclipse for C/C++.

      I created a folder on my drive, then cloned the following repositories:

      • Duet3Expansion 3.5-dev
      • CANlib 3.5-dev
      • RRFLibraries 3.5-dev
      • CoreN2G 3.5-dev
      • FreeRTOS 3.5-dev
      • Qfplib-M0-full 3.5-dev

      and added that folder as a workspace.

      The FreeRTOS repository also has instructions for adding a PATH variable to the project in Eclipse necessary to compile for the Sammy-C21.

      After that you make the necessary changes to your code, set the build target in eclipse to SAMMY-C21, cross your fingers, and hope for the best!

      posted in Firmware developers
      omtekundefined
      omtek
    • RE: SBC-mode config shows console errors in standalone mode

      @Phaedrux It looks like the error was in one of the nested macros I use to lower motor current during homing as after running the blank operations I mentioned above on the files in the /sys folder, the error no longer appears. I guess SBC-mode was acting as an additional filter and caught it which was why I never encountered the errors before.

      Thanks for the help!

      posted in General Discussion
      omtekundefined
      omtek
    • Duet 3 Mini 5+ standalone 3.5.2 - HardFault bfarValid precise

      I saw a couple of older posts about resets occurring with reason: HardFault imprec, but on 3.5.1, and after encountering the issue myself I added M122 P500 S0 for the more helpful M122 output.

      Printer is the same one as here, just running in standalone mode now.

      Duet 3 Mini 5+ running 3.5.2
      CannedERCF running 3.5.2
      SHT36MAX3 running 3.5.2

      M122

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF
      Used output buffers: 18 of 40 (25 max)
      === RTOS ===
      Static ram: 103368
      Dynamic ram: 124620 of which 0 recycled
      Never used RAM 10572, free system stack 202 words
      Tasks: NETWORK(2,nWait 7,6.2%,242) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,353) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,353) TMC(4,delaying,1.5%,101) MAIN(1,running,90.2%,665) IDLE(0,ready,1.2%,29) AIN(4,delaying,0.9%,259), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:00:24 ago, cause: software
      Last software reset at 2024-07-13 14:02, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 10404, slot 1
      Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20012008 Task NETW Freestk 482 ok
      Stack: 0000016e 00000002 200014e8 0000016d 20033aba 000a0bff 00030152 810f0000 00030149 00000000 00000000 00000000 200310cc 00000800 2002c640 2002c640 00000001 2002c496 2001882c 2001ea80 000302e3 00000000 00000000 00000000 200120b8 00000014 b5ddbf73
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 25301, completed 25301, timed out 0, errs 0
      MCU temperature: min 36.1, current 36.3, max 37.8
      Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/304/132, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 46, reads 2198, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 46, reads 2198, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 2201, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 2198, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 46, reads 2198, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 2198, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 2201, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2024-07-13 14:02:38
      Cache data hit count 46575139
      Slowest loop: 4.76ms; fastest: 0.16ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 0.4ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000803
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 209, received 716, lost 0, errs 0, boc 0
      Longest wait 1ms for reply type 6042, peak Tx sync delay 3, free buffers 26 (min 25), ts 123/122/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 4.13ms; fastest: 0.00ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 1 of 8
      === WiFi ===
      Interface state: active
      Module is connected to access point 
      Failed messages: pending 0, notrdy 0, noresp 0
      Firmware version 2.1.0
      MAC address d8:bf:c0:14:e5:fc
      Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 39688
      WiFi IP address 192.168.2.8
      Signal strength -72dBm, channel 1, mode 802.11n, reconnections 0
      Clock register 00002001
      Socket states: 0 0 0 0 0 0 0 0
      

      Printer was idle at the time the reset occurred. DWC was open in Chrome 126.0.6478.127 (but I can't be certain on the version with how often Chrome can update). Installed languages were English (United States) and English, for the Chrome UI.

      Let me know if there's any other information I can provide.

      posted in Beta Firmware
      omtekundefined
      omtek
    • RE: Random Hard Fault resets on Duet 3 Mini WiFi

      @dc42 Build installed and running.

      9c95a8bc-c67b-4ab1-93ad-f067da9d30db-image.png

      and I've logged a message in the console already:

      *** Memory difference at offset 24: was a5a5a5a5 now 00000000

      That was the final message in the console before the reset. The printer was idle. DWC was open in Chrome.

      No reset to report.
      M122

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.5.3+1dbg (2024-10-14 09:45:56) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF
      Used output buffers: 3 of 40 (26 max)
      === RTOS ===
      Static ram: 103368
      Dynamic ram: 124576 of which 0 recycled
      Never used RAM 10952, free system stack 156 words
      Tasks: NETWORK(2,nWait 7,8.3%,228) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,361) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait 6,1.5%,101) MAIN(1,running,87.7%,665) IDLE(0,ready,1.6%,29) AIN(4,delaying,0.8%,259), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 00:00:18 ago, cause: software
      Last software reset at 2024-10-17 18:07, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 7892, slot 0
      Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20012008 Task NETW Freestk 482 ok
      Stack: 00000165 00000002 200014e4 00000164 20033af1 000a102f 0003041a 810f0000 00030411 00000000 00000000 00000000 2003111c 00000800 20036670 2002c5d8 2001882c 2002c42e 2001882c 2001ea80 000305ab 00000000 00000000 00000000 200120b8 00000014 b5ddddb2
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 14510, completed 14510, timed out 0, errs 0
      MCU temperature: min 33.7, current 33.7, max 35.1
      Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/304/132, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 1693, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 1693, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 1696, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 51, reads 1692, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 51, reads 1693, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 1693, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 1696, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2024-10-17 18:07:41
      Cache data hit count 35094639
      Slowest loop: 5.03ms; fastest: 0.16ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 0.5ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000803
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 181, received 573, lost 0, errs 0, boc 0
      Longest wait 2ms for reply type 6060, peak Tx sync delay 90, free buffers 26 (min 25), ts 95/94/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 4.31ms; fastest: 0.00ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 1 of 8
      === WiFi ===
      Interface state: active
      Module is connected to access point 
      Failed messages: pending 0, notrdy 0, noresp 0
      Firmware version 2.1.0
      MAC address d8:bf:c0:14:e5:fc
      Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 42932
      WiFi IP address 192.168.2.8
      Signal strength -47dBm, channel 1, mode 802.11n, reconnections 0
      Clock register 00002001
      Socket states: 0 0 0 0 0 0 0 0
      

      And a second reset about an hour later.

      M122

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.5.3+1dbg (2024-10-14 09:45:56) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF
      Used output buffers: 3 of 40 (28 max)
      === RTOS ===
      Static ram: 103368
      Dynamic ram: 124564 of which 12 recycled
      Never used RAM 10952, free system stack 156 words
      Tasks: NETWORK(2,nWait 7,15.5%,241) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,335) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,773) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.5%,101) MAIN(1,running,82.1%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.8%,259), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 01:14:36 ago, cause: software
      Last software reset at 2024-10-17 19:14, reason: HardFault bfarValid precise, none spinning, available RAM 10952, slot 1
      Software reset code 0x0073 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x0000001c SP 0x20012008 Task NETW Freestk 482 ok
      Stack: 2002c5f0 200328a0 200014e4 00000000 ffffffff 00030425 00030338 610f0000 00030411 00000000 00000000 00000000 200328ac 00000800 200365c0 2002c5d8 2001882c 2002c42e 2001882c 2001ea80 000305ab 00000000 00000000 00000000 200120b8 00000014 b5ddddb2
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 3357571, completed 3357570, timed out 0, errs 0
      MCU temperature: min 30.2, current 30.7, max 32.1
      Supply voltage: min 24.3, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/304/132, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 61, reads 13726, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 61, reads 13726, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 13729, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 13726, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 13726, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 61, reads 13726, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 13729, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2024-10-17 20:29:25
      Cache data hit count 4294967295
      Slowest loop: 9.45ms; fastest: 0.16ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 4.7ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000803
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 40299, received 127619, lost 0, errs 0, boc 0
      Longest wait 2ms for reply type 6031, peak Tx sync delay 282, free buffers 26 (min 25), ts 22384/22383/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 7.94ms; fastest: 0.00ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 1 of 8
      === WiFi ===
      Interface state: active
      Module is connected to access point 
      Failed messages: pending 0, notrdy 0, noresp 0
      Firmware version 2.1.0
      MAC address d8:bf:c0:14:e5:fc
      Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 42772
      WiFi IP address 192.168.2.8
      Signal strength -48dBm, channel 1, mode 802.11n, reconnections 0
      Clock register 00002001
      Socket states: 0 0 0 0 0 0 0 0
      
      posted in General Discussion
      omtekundefined
      omtek
    • RE: Random Hard Fault resets on Duet 3 Mini WiFi

      @dc42 Logged a memory difference message with the new build. Printer was idle. No reset as of yet.

      *** Memory difference at line 2228 offset 12: original 0d0a0d39 copy 20032958, original changed, copy ok, fix=yes

      Logged another memory difference message. Still no reset.

      *** Memory difference at line 2228 offset 60: original 2001882c copy 0d0a0d39, original ok, copy changed, fix=no

      posted in General Discussion
      omtekundefined
      omtek

    Latest posts made by omtek

    • RE: [3.6.0-rc.1] DWC Webcam page displays broken image

      I will confirm that changing from /?action=stream to /?action=snapshot in the webcam URL and setting an update interval (I chose 500ms), you can get something resembling a webcam slideshow in the window.

      af77bca3-3b8b-426a-b5bd-7c9a53809039-image.png

      posted in Beta Firmware
      omtekundefined
      omtek
    • RE: [3.6.0-rc.1] DWC Webcam page displays broken image

      @chrishamm Here is a screenshot of the webcam settings 1575d625-50e2-49eb-992e-156d3a3c57f8-image.png

      I reverted back to 3.5.4 to grab a screenshot from the inspector too.
      84662f9f-ea79-4c35-ac1b-2bb959cb354b-image.png

      And the same page in 3.6.0-rc.115245e0b-222f-4e20-b6ad-9dcc1f71cdd5-image.png

      Let me know if you need any more info!

      ~oM

      posted in Beta Firmware
      omtekundefined
      omtek
    • [3.6.0-rc.1] DWC Webcam page displays broken image

      I have updated my Duet 3 Mini 5+ machine and its related boards to 3.6.0-rc.1 and while kicking the tires I noticed that that webcam page in MS Edge wasn't displaying the webcam feed that I was seeing in 3.5.4.

      The webcam is using ustreamer on a raspberry pi. The duet3mini5+ is running in standalone mode.

      b41d26b7-f730-4b47-aa20-ce5a9ce61a5e-image.png

      Waterfox (Mozilla Firefox fork) also displays something similar

      745da185-45b6-4c40-a0af-db3d4bdfc78c-image.png

      I have verified the stream is working in a separate browser tab
      8a697223-c598-4992-aa11-bd43b8bd5ca3-image.png

      All boards, WiFi server and DWC are at their latest versions.

      55ab6deb-1eac-49b6-8c8b-1c0ee2f1623a-image.png

      posted in Beta Firmware
      omtekundefined
      omtek
    • RE: RRF 3.5.4 - Hardfault bfarValid precise

      @T3P3Tony I wasn't planning on trying 3.6 until the RC phase as I have a SHT36MAX3 toolboard and a CannedERCF board on the printer and generally have to wait on Team Gloomy for their firmware updates before I can do any updating (and I'm compiling my own firmware for the CannedERCF).

      Do you know if there is any way to induce (for lack of a better term) the HardFault? Two months is a long time to go between faults and unlike the series of HardFault restarts that started this post, I haven't encountered another one since last night.

      posted in General Discussion
      omtekundefined
      omtek
    • RE: RRF 3.5.4 - Hardfault bfarValid precise

      Adding to this post as I just had another HardFault occur.

      • Printer had recently finished a print without error; printer was idle but bed and tool heaters were pre-soaking for new print

      • Prusaslicer 2.9.0 was in the middle of uploading g-code when the reset occurred.

      This is the first HardFault that I have encountered since first posting in this thread.

      M122 follows:

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (standalone mode)
      Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF
      Used output buffers: 3 of 40 (26 max)
      === RTOS ===
      Static ram: 103496
      Dynamic ram: 124556 of which 0 recycled
      Never used RAM 10844, free system stack 198 words
      Tasks: NETWORK(2,nWait 7,9.7%,241) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,349) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.5%,101) MAIN(1,running,86.5%,665) IDLE(0,ready,1.3%,29) AIN(4,delaying,0.9%,255), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:00:22 ago, cause: software
      Last software reset at 2025-02-22 01:04, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 9328, slot 2
      Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x3730302e SP 0x20011f70 Task NETW Freestk 444 ok
      Stack: ffffffff 20033e6c 00000002 00000000 00000000 3730302e 0002e638 01010000 00000000 20011807 000a26a3 004202c0 2002c438 00000000 2002c438 00000001 00000000 00000004 0002e8d5 2002c43c 2002c401 3730302e 85a74255 00000000 0000011c 2002c658 200321a8
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 18027, completed 18027, timed out 0, errs 0
      MCU temperature: min 33.9, current 34.4, max 35.4
      Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/300/128, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 142, reads 2039, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 143, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 2041, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 142, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 143, reads 2039, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 5: standstill, SG min 2, read errors 0, write errors 1, ifcnt 143, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0
      Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 2041, writes 10, timeouts 0, DMA errors 0, CC errors 0
      Date/time: 2025-02-22 01:05:09
      Cache data hit count 42967048
      Slowest loop: 4.91ms; fastest: 0.16ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 2.5ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks held by null, 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000803
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 214, received 694, lost 0, errs 0, boc 0
      Longest wait 2ms for reply type 6031, peak Tx sync delay 3, free buffers 26 (min 25), ts 114/113/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 25.43ms; fastest: 0.00ms
      Responder states: MQTT(0) HTTP(0) 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
      MAC address d8:bf:c0:14:e5:fc
      Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 35896
      WiFi IP address 192.168.2.8
      Signal strength -46dBm, channel 1, mode 802.11n, reconnections 0
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      

      EDIT: I wanted to add that since the initial HardFault in December and last night, I updated Duet Wifi Server to 2.2.1.

      posted in General Discussion
      omtekundefined
      omtek
    • RE: Unexpected startup behavior.

      @fcwilt You set the name in DWC using the drop-down menu: 0b500961-d2b0-489b-83ff-9726afc65748-image.png

      and you configure your filaments in the Filament section of DWC:
      96f13617-c1bb-4114-9ba6-30a521528573-image.png

      clicking on "New FIlament" will prompt you for a name8e4aa82f-907f-4925-b4db-35eb1b9b8450-image.png

      which will create the folder /filaments/<filament name>/ and empty config.g, unload.g, and load.g macros for you to use.

      If you want to update the filament using a macro you'll have to echo > <your filament name> to filaments.csv; the value is stored at the end of the file. When you change the filament using DWC this file is updated automatically so your macro changes may be overwritten.

      posted in Duet Web Control
      omtekundefined
      omtek
    • RE: Unexpected startup behavior.

      See M703:

      https://docs.duet3d.com/User_manual/Reference/Gcodes#m703-configure-filament

      "After assigning a filament to a tool, this command may be used to run /filaments/<filament name>/config.g to set parameters like temperatures, extrusion factor, retract distance. If no filament is loaded, the code completes without a warning."

      posted in Duet Web Control
      omtekundefined
      omtek
    • RE: Question about Sammy-C21 board

      @fcwilt

      For cloning the repositories, I use git from the command prompt. I believe you can also use Github Desktop if you're more comfortable with a GUI, though I've never used it personally. You need to install git or Github Desktop for your OS if you haven't already.

      For each repository, there is a 32145175-d8bf-45d0-9682-c4c978beaad7-image.png button. If you click it'll have the particular URL for cloning the repository using the command line, or a button for opening in Github Desktop.

      So for example, to clone the 3.5-dev branch of Duet3Expansion, I open my terminal inside the workspace folder I created and type:

      git clone --branch 3.5-dev https://github.com/Duet3D/Duet3Expansion.git

      Do that for each of the repositories above, changing the URL for each, and placing them all into the same folder.

      In the end, it should look something like this:

      e114b181-6cf6-421b-8975-0d37c376262b-image.png

      After that, open Eclipse. It should ask you to select a directory as a workspace. Point it to the folder with your cloned repositories.

      Then to the File menu, and select Open Projects from File System....

      Set the Import Source is your workspace folder and it should show your folders.
      9a91afb4-9cc7-4c48-b0d9-29a91878d5d7-image.png

      Click finish and you should see everything in Eclipse

      d84b74b6-61f9-48da-b0ad-bda24d718b34-image.png

      Hope this helps!

      posted in Firmware developers
      omtekundefined
      omtek
    • RE: Question about Sammy-C21 board

      @fcwilt I'm using a Sammy-C21 on a CannedERCF and created a build environment for compiling firmware so I'll try to remember the steps:

      Towards the bottom of the Duet3Expansion repository are the links to three packages you need to download (gcc cross compiler, the Eclipse IDE, and the GNU Arm Eclipse bundle)

      Install them.

      When installing Eclipse you want Eclipse for C/C++.

      I created a folder on my drive, then cloned the following repositories:

      • Duet3Expansion 3.5-dev
      • CANlib 3.5-dev
      • RRFLibraries 3.5-dev
      • CoreN2G 3.5-dev
      • FreeRTOS 3.5-dev
      • Qfplib-M0-full 3.5-dev

      and added that folder as a workspace.

      The FreeRTOS repository also has instructions for adding a PATH variable to the project in Eclipse necessary to compile for the Sammy-C21.

      After that you make the necessary changes to your code, set the build target in eclipse to SAMMY-C21, cross your fingers, and hope for the best!

      posted in Firmware developers
      omtekundefined
      omtek
    • RE: RRF 3.5.4 - Hardfault bfarValid precise

      @dc42 I built a new computer in the first week of December '24 and started using Microsoft Edge for DWC; prior to that I was using Google Chrome. I use Google Chrome on my S22U phone to access DWC, as well. This installation of Windows 11 Professional is only a few weeks old and was a fresh installation. I haven't installed any additional languages aside from 'English (United States)' in Windows and Edge just shows two instances of English ('English' and 'English (US)') under preferred languages.

      posted in General Discussion
      omtekundefined
      omtek