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

    [SBC] Version 3.4-b1 now available

    Scheduled Pinned Locked Moved
    Beta Firmware
    8
    17
    1.1k
    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.
    • Alex.crundefined
      Alex.cr @chrishamm
      last edited by Alex.cr

      @chrishamm

      While attempting to upgrade, the installation is hanging at the following line:
      Untitled picture.png

      The first time this happened I rebooted the PI4 and DSF had updated to 3.4-b1 but it did not update the firmware, was still showing 3.3 release. Firing an M999 would cause the whole system to hang and require a PI reboot in order for DCS to reconnect.

      I was able to successfully downgrade back to 3.3 release. I have attempted the upgrade again and it hangs at the same place. I am usually running the latest betas to help test so this is no the first time I have been on the unstable package feed. Any thoughts moving forward?

      Below is the log from: journalctl -u duetcontrolserver -e

      pi@voron:~ $ journalctl -u duetcontrolserver -e
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] Environment initialized
Jul 10 17:32:25 voron DuetControlServer[3786]: [warn] Incompatible firmware, ple
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] Connection to Duet establi
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] IPC socket created at /var
Jul 10 17:32:26 voron systemd[1]: Started Duet Control Server.
Jul 10 17:32:33 voron DuetControlServer[3786]: [info] Starting macro file daemon
Jul 10 17:32:33 voron DuetControlServer[3786]: [warn] Daemon: Aborting orphaned 
Jul 10 17:32:33 voron DuetControlServer[3786]: [info] Aborted macro file daemon.
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] Abnormal program terminat
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] SPI task faulted
Jul 10 17:32:34 voron DuetControlServer[3786]:    System.NotSupportedException: 
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDi
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDi
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.Model.Upd
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Inter
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Inter
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] SPI task faulted
Jul 10 17:32:34 voron DuetControlServer[3786]:    System.NotSupportedException: 
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDi
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDi
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.Model.Upd
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Inter
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Inter
lines 201-223/223 (END)
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] Environment initialized
Jul 10 17:32:25 voron DuetControlServer[3786]: [warn] Incompatible firmware, please upgrade as soon as possible
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] Connection to Duet established
Jul 10 17:32:25 voron DuetControlServer[3786]: [info] IPC socket created at /var/run/dsf/dcs.sock
Jul 10 17:32:26 voron systemd[1]: Started Duet Control Server.
Jul 10 17:32:33 voron DuetControlServer[3786]: [info] Starting macro file daemon.g on channel Daemon
Jul 10 17:32:33 voron DuetControlServer[3786]: [warn] Daemon: Aborting orphaned macro file daemon.g
Jul 10 17:32:33 voron DuetControlServer[3786]: [info] Aborted macro file daemon.g
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] Abnormal program termination
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] SPI task faulted
Jul 10 17:32:34 voron DuetControlServer[3786]:    System.NotSupportedException: Specified method is not supported.
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDictionary`1.Remove(String key) in /home/christ
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDictionary`1.Clear() in /home/christian/Duet3D/
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.Model.Updater.ConnectionLost() in /home/christian/Duet
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Interface.Invalidate(String message) in /home/chri
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/Duet3D/DuetSoft
Jul 10 17:32:34 voron DuetControlServer[3786]: [fatal] SPI task faulted
Jul 10 17:32:34 voron DuetControlServer[3786]:    System.NotSupportedException: Specified method is not supported.
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDictionary`1.Remove(String key) in /home/christ
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetAPI.ObjectModel.ModelDictionary`1.Clear() in /home/christian/Duet3D/
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.Model.Updater.ConnectionLost() in /home/christian/Duet
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Interface.Invalidate(String message) in /home/chri
Jul 10 17:32:34 voron DuetControlServer[3786]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/Duet3D/DuetSoft
lines 201-223/223 (END)

      Edit: I should also include hardware: Pi4+6HC+3HC+1TL

      Voron2.4/Duet3 SBC+6HC+3HC+1LC+1HCL(x2) - Delta/Duet2 Wifi - CubePro/Duet2 Wifi+Duex5 - Laser/Duet3 Mini5+ - Cel Robox - U̶p̶3̶0̶0̶+/D̶u̶e̶t̶3̶ ̶6̶H̶C̶+̶LC1̶ - F̶T̶-̶5̶/̶D̶u̶e̶t̶2̶ ̶W̶i̶f̶i̶ - S̶o̶l̶i̶d̶o̶o̶d̶l̶e̶

      dc42undefined chrishammundefined 2 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Alex.cr
        last edited by dc42

        I have just added the following list of known issues to the 3.4.0beta1 RRF release notes:

        • If the slicer uses the M486 command to label objects in the GCode file, and there are more than 20 (Duet 2) or 40 (Duet 3) objects, then RRF crashes when printing the file. This bug is also present in release 3.2.x and 3.3.
        • If you home any axes when workplace coordinates are in use, then any absolute moves in the homing files have workplace coordinate offsets applied; whereas they should not. This bug is also present in release 3.3.
        • When M955 reports the configuration of an accelerometer that is connected to the main board using SPI, the orientation is always reported as 20 even if a different orientation has been selected (and is being used) by means of the M955 I parameter. This bug is also present in release 3.3.
        • Sending a M956 command that refers to an accelerometer on a CAN-connected board via the Pi (e.g. from DWC) does not work and reports that the accelerometer was not found. Workaround: send the command to the Duet from a PanelDue or via USB 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

        CadetCundefined 1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators @Alex.cr
          last edited by

          @alex-cr Please share the full DCS logs, the stack traces are truncated (journalctl --no-pager -e duetcontrolserver should print everything). Once I get them, I'll be happy to fix it. Also note that M997 updates RRF while M999 resets it.

          Duet software engineer

          Alex.crundefined 1 Reply Last reply Reply Quote 0
          • Alex.crundefined
            Alex.cr @chrishamm
            last edited by

            @chrishamm

            This should be better. Sorry for the truncation initially.

            Jul 11 13:22:31 voron DuetControlServer[390]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:22:32 voron DuetControlServer[390]: [info] Finished macro file daemon.g
Jul 11 13:22:42 voron DuetControlServer[390]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:22:42 voron DuetControlServer[390]: [info] Finished macro file daemon.g
Jul 11 13:22:52 voron DuetControlServer[390]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:22:52 voron DuetControlServer[390]: [info] Finished macro file daemon.g
Jul 11 13:23:02 voron DuetControlServer[390]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:23:02 voron DuetControlServer[390]: [info] Finished macro file daemon.g
Jul 11 13:23:12 voron DuetControlServer[390]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:23:12 voron DuetControlServer[390]: [info] Finished macro file daemon.g
Jul 11 13:23:20 voron systemd[1]: Stopping Duet Control Server...
Jul 11 13:23:20 voron DuetControlServer[390]: [warn] Received SIGTERM, shutting down...
Jul 11 13:23:20 voron DuetControlServer[390]: [info] Application has shut down
Jul 11 13:23:20 voron systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=143/n/a
Jul 11 13:23:20 voron systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Jul 11 13:23:20 voron systemd[1]: Stopped Duet Control Server.
Jul 11 13:23:37 voron systemd[1]: Starting Duet Control Server...
Jul 11 13:23:37 voron DuetControlServer[9915]: Duet Control Server v3.4-b1
Jul 11 13:23:37 voron DuetControlServer[9915]: Written by Christian Hammacher for Duet3D
Jul 11 13:23:37 voron DuetControlServer[9915]: Licensed under the terms of the GNU Public License Version 3
Jul 11 13:23:38 voron DuetControlServer[9915]: [info] Settings loaded
Jul 11 13:23:38 voron DuetControlServer[9915]: [info] Environment initialized
Jul 11 13:23:39 voron DuetControlServer[9915]: [warn] Incompatible firmware, please upgrade as soon as possible
Jul 11 13:23:39 voron DuetControlServer[9915]: [info] Connection to Duet established
Jul 11 13:23:39 voron DuetControlServer[9915]: [info] IPC socket created at /var/run/dsf/dcs.sock
Jul 11 13:23:39 voron systemd[1]: Started Duet Control Server.
Jul 11 13:23:44 voron DuetControlServer[9915]: [info] Starting macro file daemon.g on channel Daemon
Jul 11 13:23:45 voron DuetControlServer[9915]: [info] Finished macro file daemon.g
Jul 11 13:23:47 voron DuetControlServer[9915]: [fatal] Abnormal program termination
Jul 11 13:23:47 voron DuetControlServer[9915]: [fatal] SPI task faulted
Jul 11 13:23:47 voron DuetControlServer[9915]:    System.NotSupportedException: Specified method is not supported.
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetAPI.ObjectModel.ModelDictionary`1.Remove(String key) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelDictionary.cs:line 377
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetAPI.ObjectModel.ModelDictionary`1.Clear() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelDictionary.cs:line 231
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.Model.Updater.ConnectionLost() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 453
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.SPI.Interface.Invalidate(String message) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1780
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 783
Jul 11 13:23:47 voron DuetControlServer[9915]: [fatal] SPI task faulted
Jul 11 13:23:47 voron DuetControlServer[9915]:    System.NotSupportedException: Specified method is not supported.
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetAPI.ObjectModel.ModelDictionary`1.Remove(String key) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelDictionary.cs:line 377
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetAPI.ObjectModel.ModelDictionary`1.Clear() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelDictionary.cs:line 231
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.Model.Updater.ConnectionLost() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 453
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.SPI.Interface.Invalidate(String message) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1780
Jul 11 13:23:47 voron DuetControlServer[9915]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 783

            Also yes I have tried M997 and M999 after this issue. Both cause DCS to crash and then not allow a reconnect without a reboot of the PI.

            Voron2.4/Duet3 SBC+6HC+3HC+1LC+1HCL(x2) - Delta/Duet2 Wifi - CubePro/Duet2 Wifi+Duex5 - Laser/Duet3 Mini5+ - Cel Robox - U̶p̶3̶0̶0̶+/D̶u̶e̶t̶3̶ ̶6̶H̶C̶+̶LC1̶ - F̶T̶-̶5̶/̶D̶u̶e̶t̶2̶ ̶W̶i̶f̶i̶ - S̶o̶l̶i̶d̶o̶o̶d̶l̶e̶

            chrishammundefined 1 Reply Last reply Reply Quote 1
            • CadetCundefined
              CadetC @dc42
              last edited by

              @dc42 said in [SBC] Version 3.4-b1 now available:

              • Sending a M955 command that refers to an accelerometer on a CAN-connected board via the Pi (e.g.rom DWC) does not work and report that the accelerometer was not found. Workaround: send the command to the Duet from a PanelDue or via USB instead.

              In my case sending M955 from DWC works just fine -Duet3 +SBC

              12.07.2021, 06:22:09	M955 P121.0 I41
Accelerometer 121:0 with orientation 41 samples at 1344Hz with 10-bit resolution

              12.07.2021, 06:23:26	M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2680, free system stack 2762 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,117) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,2.8%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:08:33 ago, cause: VDD brownout
Last software reset data not available
Driver 0: position 0, 409.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 59923, writes 11, timeouts 0, DMA errors 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 0/4, peak Rx sync delay 216, resyncs 0/0, no step interrupt scheduled
VIN: 24.9V
MCU temperature: min 26.4C, current 42.8C, max 42.8C
Ticks since heat task active 120, ADC conversions started 512757, completed 512755, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 125 ticks ago, loop time 0
CAN messages queued 5914, send timeouts 0, received 4556, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0

              But when i tried to collect some data there is a problem:

              12.07.2021, 06:25:44	G1 X-50 G4 S2 M956 P124.0 S1000 A0 G4 P10 G1 X50 F20000
Error: 

M956: Accelerometer not found

              So, M955 works and there is a problem with M956?

              Chris

              jay_s_ukundefined dc42undefined 2 Replies Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @CadetC
                last edited by

                @cadetc i believe this is a known issue that is being investigated

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                CadetCundefined 1 Reply Last reply Reply Quote 0
                • CadetCundefined
                  CadetC @jay_s_uk
                  last edited by

                  @jay_s_uk
                  Yes, the problem is known, I reported it earlier in another thread. This post is just to point out that in "list of known issues" there is talk about M955, where in my case everything is OK while there is no mention of M966

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

                    @cadetc said in [SBC] Version 3.4-b1 now available:

                    So, M955 works and there is a problem with M956?

                    Correct. I have corrected the list of known issues.

                    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
                    • chrishammundefined
                      chrishamm administrators @Alex.cr
                      last edited by chrishamm

                      @alex-cr Thanks, this problem is related to global variables and I've got a fix ready. To work-around this problem, start up your machine without any global variables and then upgrade the firmware. I've got a fix ready for M956, too.

                      Duet software engineer

                      CadetCundefined 1 Reply Last reply Reply Quote 0
                      • oozeBotundefined
                        oozeBot
                        last edited by

                        Which beta will inverting PS_ON levels be included in? Thanks

                        1 Reply Last reply Reply Quote 0
                        • CadetCundefined
                          CadetC @chrishamm
                          last edited by

                          @chrishamm said in [SBC] Version 3.4-b1 now available:

                          I've got a fix ready for M956, too.

                          is this fix will be published soon?

                          chrishammundefined 1 Reply Last reply Reply Quote 0
                          • chrishammundefined
                            chrishamm administrators @CadetC
                            last edited by

                            @cadetc Yes, I hope I can do another prerelease on Thursday as I won't be available tomorrow.

                            Duet software engineer

                            Frederikundefined CadetCundefined 2 Replies Last reply Reply Quote 0
                            • Frederikundefined
                              Frederik @chrishamm
                              last edited by

                              @chrishamm hello, are there any news on the accelerometer not found error when using a toolboard v1.1 and sbc?

                              Kindly regards
                              Frederik

                              1 Reply Last reply Reply Quote 0
                              • CadetCundefined
                                CadetC @chrishamm
                                last edited by

                                @chrishamm said in [SBC] Version 3.4-b1 now available:

                                @cadetc Yes, I hope I can do another prerelease on Thursday as I won't be available tomorrow.

                                Is there any change in accelerometer +SBC issue? First we hear that the problem is fixed, then that new firmware will be released on Thursday, and then there is silence and nothing happens.

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

                                  @cadetc said in [SBC] Version 3.4-b1 now available:

                                  @chrishamm said in [SBC] Version 3.4-b1 now available:

                                  @cadetc Yes, I hope I can do another prerelease on Thursday as I won't be available tomorrow.

                                  Is there any change in accelerometer +SBC issue? First we hear that the problem is fixed, then that new firmware will be released on Thursday, and then there is silence and nothing happens.

                                  It was released, but did not get announced here. Sorry about that.

                                  https://github.com/Duet3D/DuetSoftwareFramework/releases/tag/v3.4-b1

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  CadetCundefined 1 Reply Last reply Reply Quote 0
                                  • CadetCundefined
                                    CadetC @Phaedrux
                                    last edited by

                                    @phaedrux said in [SBC] Version 3.4-b1 now available:

                                    @cadetc said in [SBC] Version 3.4-b1 now available:

                                    @chrishamm said in [SBC] Version 3.4-b1 now available:

                                    @cadetc Yes, I hope I can do another prerelease on Thursday as I won't be available tomorrow.

                                    Is there any change in accelerometer +SBC issue? First we hear that the problem is fixed, then that new firmware will be released on Thursday, and then there is silence and nothing happens.

                                    It was released, but did not get announced here. Sorry about that.

                                    https://github.com/Duet3D/DuetSoftwareFramework/releases/tag/v3.4-b1

                                    I think I may have misspoken, I know about version 3.4 b1, I even have it installed right after the release but there is a problem with the toolboard v1.1 +SBC . I described it above in this thread. Apparently the problem has been fixed and next prerelease was supposed to be released last Thursday

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