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

    RepRapFirmware 3.2beta4.1 now available

    Scheduled Pinned Locked Moved
    Beta Firmware
    16
    34
    1.8k
    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.
    • jbarrosundefined
      jbarros @jbarros
      last edited by jbarros

      Ok, I've been getting more 2000º and other missing things from the Toolboards
      2 printers running 3.2beta4.1 on 6HCs and 3.2beta4.1 on the Toolboards
      It seems to happen when saving config.g and accepting the reload popup

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

        Latest tool board firmware is now 3.2beta4.1.

        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

        jbarrosundefined 1 Reply Last reply Reply Quote 0
        • jbarrosundefined
          jbarros @dc42
          last edited by

          @dc42 I wrote the version bad on my post but my Toolboards run 3.2beta4.1 from the day you announced it's availability.

          1 Reply Last reply Reply Quote 0
          • KipKundefined
            KipK
            last edited by KipK

            Got a problem updating to latest beta.
            After upgrade printer doesn't connect to wifi anymore.

            When doing M587 I get an error saying another SPI transfer is pending.

            Tryed rebooting but it's still stuck, any tip ?

            Thanks

            Edit: I solved it by manually flashing again the wifi module. Wondering what did happened

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

              @KipK said in RepRapFirmware 3.2beta4.1 now available:

              Edit: I solved it by manually flashing again the wifi module. Wondering what did happened

              Unfortunately the firmware upload protocol defined by the manufacturer of the wifi chip does not include error detection. It appears that flashing the wifi firmware occasionally appears to succeed but leaves the wifi module running corrupt firmware.

              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
              • smoki3undefined
                smoki3
                last edited by smoki3

                After a bit of research I noticed that the filament assignment is handled by the firmware not by DWC.

                So this issue is related to the firmware right?

                https://forum.duet3d.com/topic/20307/duet2sbc-load-filament-not-working

                The duet2sbc doesn't load the filament assigment on start up.

                1 Reply Last reply Reply Quote 0
                • BoAundefined
                  BoA
                  last edited by

                  I am checking from time to time M122, and this one is particularly curious result (printing in progress):

                  M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 MB6HC version 3.2-beta4.1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
                  Board ID: 08DJM-956L2-G43S8-6J1D6-3SJ6R-KA0YG
                  Used output buffers: 1 of 40 (26 max)
                  === RTOS ===
                  Static ram: 123292
                  Dynamic ram: 170684 of which 112 recycled
                  Never used RAM 98104, free system stack 116 words
                  Tasks: NETWORK(ready,159) ETHERNET(blocked,103) HEAT(blocked,276) CanReceiv(blocked,947) CanSender(blocked,348) CanClock(blocked,349) TMC(blocked,18) MAIN(running,696) IDLE(ready,19)
                  Owned mutexes:
                  === Platform ===
                  Last reset 03:24:13 ago, cause: software
                  Last software reset time unknown, reason: User, GCodes spinning, available RAM 98312, slot 1
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task MAIN
                  Error status: 0x00
                  MCU temperature: min 39.1, current 39.2, max 39.4
                  Supply voltage: min 27.1, current 27.3, max 27.4, under voltage events: 0, over voltage events: 0, power good: yes
                  12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
                  Driver 0: position 19983, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/1023
                  Driver 1: position 28137, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/1023
                  Driver 2: position 14970, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/168
                  Driver 3: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max not available
                  Driver 4: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max 0/0
                  Driver 5: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max 0/0
                  Date/time: 2020-12-14 12:34:38
                  Slowest loop: 5.90ms; fastest: 0.26ms
                  === Storage ===
                  Free file entries: 9
                  SD card 0 detected, interface speed: 25.0MBytes/sec
                  SD card longest read time 2.4ms, write time 0.0ms, max retries 0
                  === Move ===
                  FreeDm 354 (min 344), maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
                  === MainDDARing ===
                  Scheduled moves 971089, completed moves 971030, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
                  === 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 = 3 -1 -1 -1
                  Heater 0 is on, I-accum = 0.4
                  Heater 1 is on, I-accum = 0.4
                  === GCodes ===
                  Segments left: 1
                  Movement lock held by null
                  HTTP is idle in state(s) 0
                  Telnet is idle in state(s) 0
                  File is doing "G1 X91.461 Y150.354 E0.04368" 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 not empty:
                  Queued 'M106 S127.5�����������������������������������������������������' for move 971061
                  Queued 'M106 S76.55�����������������������������������������������������
                  ' for move 971063
                  2 of 16 codes have been queued.
                  === Network ===
                  Slowest loop: 14.15ms; fastest: 0.03ms
                  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 0 0 0
                  Socket states: 5 2 2 2 2 2 0 0
                  === Filament sensors ===
                  Extruder 0: pos 190.90, errs: frame 1 parity 0 ovrun 0 pol 0 ovdue 0
                  Extruder 1: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
                  === CAN ===
                  Messages queued 20, send timeouts 44, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47
                  
                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators
                    last edited by dc42

                    Thanks for that. The code to print the queued GCodes assumed that the commands were null-terminated, but they are not. Fixed in next beta/RC.

                    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

                    BoAundefined 1 Reply Last reply Reply Quote 0
                    • BoAundefined
                      BoA @dc42
                      last edited by

                      @dc42 What about move number? They are not consecutive numbers. Is that OK? Was something executed Out-Of-Order ?

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

                        @BoA said in RepRapFirmware 3.2beta4.1 now available:

                        @dc42 What about move number? They are not consecutive numbers. Is that OK? Was something executed Out-Of-Order ?

                        No. A "queued GCode" is one that needs to be delayed until a command that has been put in the movement queue is executed. Only a few command types are queued, for example heat, fan and GPIO commands. Most of the time there will be no commands in that queue. The movement command queue is separate.

                        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 1
                        • jay_s_ukundefined
                          jay_s_uk
                          last edited by

                          @dc42 anything else I can do with this?

                          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

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

                            @jay_s_uk said in RepRapFirmware 3.2beta4.1 now available:

                            @dc42 anything else I can do with this?

                            With what?

                            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
                            • jay_s_ukundefined
                              jay_s_uk
                              last edited by

                              @dc42 sorry, wrong topic

                              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

                              1 Reply Last reply Reply Quote 0
                              • delta1undefined
                                delta1
                                last edited by

                                Using Duet Wifi. Upgraded to 3.2-beta4.1. Bed heater disappeared.

                                Config heater info.
                                ; >>>>>>>>>>>>>>>>>> Heaters
                                ;Extruder
                                M143 S300 ; Set maximum heater temperature to 300C
                                M950 H1 C"e0_heat" T1 ;Extruder heater
                                M308 S1 P"spi.cs1" Y"rtd-max31865" R395 F50
                                ;Bed
                                M308 S0 P"bedtemp" Y"thermistor" A"Bed temp" T100000 B4725 C0 R2200 ;Set thermistor + ADC parameters for heater 0
                                M950 H0 C"bedheat" T0
                                M143 H0 S110 ;Bed heat max 110 deg C
                                M307 H1 A385.0 C163.1 D3.3 V23.9 B0; PID ran on 01/12/2020 Heater 1 model: gain 385.0, time constant 163.1, dead time 3.3, max PWM 1.00, calibration voltage 23.9

                                Did the port change?

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

                                  I guess you upgraded from firmware 3.1. You now need to declare the bed heater explicitly using:

                                  M140 H0

                                  after creating heater 0 with M950.

                                  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
                                  • GTechundefined
                                    GTech
                                    last edited by

                                    Yesterday I tried to update to 3.2 Beta 4.1.
                                    After the update DCS lost all communiucation to the board.
                                    I flashed the board a 2nd time via USB to ensure that firmware was installed properly, which did not change anything.

                                    In the end I was forced to roll back to the last stable release by flashing the firmware via USB.

                                    root@GPDMk1:/opt/dsf# /opt/dsf/bin/DuetControlServer -l debug
                                    Duet Control Server v3.2.0-beta4
                                    Written by Christian Hammacher for Duet3D
                                    Licensed under the terms of the GNU Public License Version 3
                                    
                                    [info] Settings loaded
                                    [info] Environment initialized
                                    [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
                                    [debug] System.OperationCanceledException: Timeout while waiting for transfer ready pin
                                       at DuetControlServer.SPI.DataTransfer.WaitForTransfer() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1081
                                       at DuetControlServer.SPI.DataTransfer.ExchangeHeader() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1122
                                       at DuetControlServer.SPI.DataTransfer.PerformFullTransfer(Boolean connecting) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 164
                                       at DuetControlServer.SPI.DataTransfer.Init() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 104
                                       at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 113
                                    root@GPDMk1:/opt/dsf#
                                    

                                    My setup: Pi4, 4GB + Duet 3 6HC + Panel Duei7

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

                                      The most likely explanation is that you didn't manage to install the correct version of RRF. After flashing via USB and rebooting, if DCS won't connect then you can send M115 from USB to check the RRF version number, and M122 to get a diagnostic report.

                                      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
                                      • Phaedruxundefined
                                        Phaedrux Moderator @GTech
                                        last edited by

                                        @GTech It might also be worth getting a fresh Duet Pi image and redoing the Pi SD card and updating it from there, especially if you're using the same Duet Pi build that came on the card originally.

                                        Z-Bot CoreXY Build | Thingiverse Profile

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