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

    Firmware from 2.02 to 2.05.1

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    4
    17
    718
    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.
    • FlyingScotundefined
      FlyingScot
      last edited by FlyingScot

      My printer has been working perfectly for years untiI I upgraded to 2.05.1 to use a laser filament sensor.
      Since the upgrade the printer is stuttering around radius moves.
      Has anyone else had this kind of problem? I did copy the sd card before upgrading can I revert back to old firmware?

      Arthur

      FlyingScotundefined 1 Reply Last reply Reply Quote 1
      • FlyingScotundefined
        FlyingScot @FlyingScot
        last edited by

        @flyingscot
        I have gone back to firmware v2.01 and the printer is working perfectly again so it is either the firmware upgrade that is causing the stuttering radial moves or the addition of the laser filament sensor.

        Has anyone any idea what may be causing this?

        Art

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

          Would help to see the config.g and the results of M122 after it had stuttered.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • FlyingScotundefined
            FlyingScot
            last edited by

            @phaedrux The problem seems to be between v2.01 and v2.02.
            2.01 perfect as it was before but with v2.02 x and y motors are stuttering on radial moves.
            Both with the same config file.

            I have also removed the filament sensor so it is not that

            Art

            droftartsundefined 1 Reply Last reply Reply Quote 1
            • droftartsundefined
              droftarts administrators @FlyingScot
              last edited by

              @flyingscot big list of changes between those two. https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-1.x-&-2.x#version-202-duet-2-series-and-123-duet-06085
              As I’m lacking the powers of omniscience and omnipresence, if you’d like help resolving this, please give more info like @Phaedrux asked for.

              Ian

              Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

              FlyingScotundefined 1 Reply Last reply Reply Quote 0
              • FlyingScotundefined
                FlyingScot @droftarts
                last edited by FlyingScot

                @droftarts

                Hi Ian

                I did notice that in the change logs.

                I also tried to include the results of m122 but they were flagged as spam. how do you upload them?

                Art

                droftartsundefined 1 Reply Last reply Reply Quote 1
                • droftartsundefined
                  droftarts administrators @FlyingScot
                  last edited by

                  @flyingscot I’ve given you some upvotes, you should be able to post them now.

                  Ian

                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                  FlyingScotundefined 1 Reply Last reply Reply Quote 0
                  • FlyingScotundefined
                    FlyingScot @droftarts
                    last edited by

                    @droftarts
                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later
                    Board ID: 08DGM-917NK-F23T0-6JTF0-3SJ6J-TY84G
                    Used output buffers: 3 of 20 (15 max)
                    === RTOS ===
                    Static ram: 28476
                    Dynamic ram: 96284 of which 16 recycled
                    Exception stack ram used: 508
                    Never used ram: 5788
                    Tasks: NETWORK(ready,464) HEAT(blocked,1248) MAIN(running,3132)
                    Owned mutexes:
                    === Platform ===
                    Last reset 00:21:16 ago, cause: software
                    Last software reset at 2021-05-14 23:23, reason: User, spinning module GCodes, available RAM 11488 bytes (slot 2)
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                    Error status: 16
                    Free file entries: 9
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest block write time: 360.5ms, max retries 0
                    MCU temperature: min 31.3, current 31.9, max 32.4
                    Supply voltage: min 11.8, current 11.9, max 12.2, under voltage events: 0, over voltage events: 0
                    Driver 0: standstill, SG min/max 0/307
                    Driver 1: standstill, SG min/max 0/225
                    Driver 2: standstill, SG min/max 0/0
                    Driver 3: standstill, SG min/max 0/259
                    Driver 4: standstill, SG min/max 0/0
                    Date/time: 2021-05-15 00:27:32
                    Slowest loop: 78.47ms; fastest: 0.08ms
                    === Move ===
                    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 150, MaxWait: 2ms, Underruns: 0, 0
                    Scheduled moves: 1557, completed moves: 1558
                    Bed compensation in use: none
                    Bed probe heights: 0.355 -0.692 0.000 0.000 0.000
                    === Heat ===
                    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                    Heater 0 is on, I-accum = 0.2
                    Heater 1 is on, I-accum = 0.8
                    === GCodes ===
                    Segments left: 0
                    Stack records: 2 allocated, 0 in use
                    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
                    serial is idle in state(s) 0
                    aux is idle in state(s) 0
                    daemon is idle in state(s) 0
                    queue is idle in state(s) 0
                    autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 362.38ms; fastest: 0.08ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                    HTTP sessions: 1 of 8

                    • WiFi -
                      Network state is running
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 1
                      WiFi firmware version 1.22
                      WiFi MAC address bc:dd:c2:89:a1:95
                      WiFi Vcc 3.42, reset reason Turned on by main processor
                      WiFi flash size 4194304, free heap 28600
                      WiFi IP address 192.168.1.100
                      WiFi signal strength -38dBm, reconnections 0, sleep mode modem
                      Socket states: 0 0 0 0 0 0 0 0
                      === Expansion ===

                    This is the one that stutters and slows during radial moves both x and y motors.

                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
                    Board ID: 08DGM-917NK-F23T0-6JTF0-3SJ6J-TY84G
                    Used output buffers: 3 of 20 (13 max)
                    === RTOS ===
                    Static ram: 25524
                    Dynamic ram: 98596 of which 12 recycled
                    Exception stack ram used: 416
                    Never used ram: 6524
                    Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,1692) IDLE(ready,200)
                    Owned mutexes:
                    === Platform ===
                    Last reset 00:07:15 ago, cause: software
                    Last software reset at 2021-05-14 23:23, reason: User, spinning module GCodes, available RAM 11488 bytes (slot 2)
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                    Error status: 16
                    Free file entries: 10
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest block write time: 355.0ms, max retries 0
                    MCU temperature: min 29.9, current 30.8, max 31.2
                    Supply voltage: min 11.8, current 12.0, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
                    Driver 0: standstill, SG min/max 0/299
                    Driver 1: standstill, SG min/max 0/219
                    Driver 2: standstill, SG min/max 0/31
                    Driver 3: standstill, SG min/max 0/244
                    Driver 4: standstill, SG min/max 0/45
                    Date/time: 2021-05-14 23:59:23
                    Cache data hit count 1572954085
                    Slowest loop: 199.40ms; fastest: 0.07ms
                    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
                    === Move ===
                    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 150, MaxWait: 83163ms, Underruns: 0, 0
                    Scheduled moves: 0, completed moves: 0
                    Bed compensation in use: none
                    Bed probe heights: 0.100 -0.095 0.000 0.000 0.000
                    === Heat ===
                    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                    Heater 0 is on, I-accum = 0.2
                    Heater 1 is on, I-accum = 0.5
                    === GCodes ===
                    Segments left: 0
                    Stack records: 2 allocated, 0 in use
                    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
                    serial is idle in state(s) 0
                    aux is idle in state(s) 0
                    daemon is idle in state(s) 0
                    queue is idle in state(s) 0
                    autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 355.16ms; fastest: 0.00ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                    HTTP sessions: 1 of 8

                    • WiFi -
                      Network state is running
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 0
                      WiFi firmware version 1.22
                      WiFi MAC address bc:dd:c2:89:a1:95
                      WiFi Vcc 3.42, reset reason Turned on by main processor
                      WiFi flash size 4194304, free heap 29000
                      WiFi IP address 192.168.1.100
                      WiFi signal strength -39dBm, reconnections 0, sleep mode modem
                      Socket states: 0 0 0 0 0 0 0 0
                    FlyingScotundefined 1 Reply Last reply Reply Quote 0
                    • FlyingScotundefined
                      FlyingScot @FlyingScot
                      last edited by

                      @flyingscot

                      Config

                      ; General preferences
                      M111 S0 ; Debugging off
                      G21 ; Work in millimetres
                      G90 ; Send absolute coordinates...
                      M83 ; ...but relative extruder moves

                      M555 P1 ; Set firmware compatibility to look like RepRapFirmare
                      M564 H0 ; Limit axis

                      :M572 D0 S0.22 ; Set extruder pressure advance.
                      M667 S1 ; Select CoreXY mode

                      ; Network
                      M550 P"dBOT" ; Set machine name
                      M552 S1 ; Enable network
                      M587 S"BT-2TA8SR" P"9T9eXAftdqtvfJ" ; Configure access point. You can delete this line once connected
                      M586 P0 S1 ; Enable HTTP
                      M586 P1 S0 ; Disable FTP
                      M586 P2 S0 ; Disable Telnet

                      ; Drives
                      M584 X0 Y1 Z2:4 E3 ; 2 Z motors connected to driver outputs 2 & 4
                      M671 X-80:480 Y200:200 S10 ; Z lead screws are at (-80,200) (480,200)

                      M579 X1.0015 Y1.003
                      M569 P0 S0 ; Drive 0 goes forwards
                      M569 P1 S1 ; Drive 1 goes forwards
                      M569 P2 S0 ; Drive 2 goes backwards
                      M569 P3 S1 ; Drive 3 goes backwards
                      M569 P4 S0 ; Drive 4 goes backwards
                      M350 X128 Y128 Z128 E16 ; Configure microstepping without interpolation
                      M92 X800 Y800 Z3200 E408 ; Set steps per mm
                      M566 X600 Y600 Z120 E2000 ; Set maximum instantaneous speed changes (mm/min)
                      M203 X9000 Y9000 Z600 E6000 ; Set maximum speeds (mm/min)
                      M201 X600 Y600 Z300 E5000 ; Set accelerations (mm/s^2)
                      M205 X15 : set x and y jerk
                      M906 X1000 Y1000 Z1200 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
                      M84 S30 ; Set idle timeout

                      ; Axis Limits
                      M208 X0 Y0 Z0 S1 ; Set axis minima
                      M208 X380 Y380 Z400 S0 ; Set axis maxima

                      ; Endstops
                      M574 X1 Y2 S0 ; Set active low endstops

                      ; Z-Probe
                      M574 Z1 S2 ; Set endstops controlled by probe
                      M558 P8 I1 X0 Y0 Z1 F200 T1000 ; Set Z probe type to unmodulated and the dive height + speeds
                      G31 P1000 X-50 Y5 Z0.612 ; Set Z probe trigger value, offset and trigger height
                      M557 X20:380 Y40:380 S75 ; Define mesh grid
                      :M591 D0 P5 C4 S0

                      ; Heaters
                      M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
                      M143 H0 S120 ; Set temperature limit for heater 0 to 120C
                      M305 P1 T100000 B4725 C7.06e-8 R4700 ; Set thermistor + ADC parameters for heater 1
                      M143 H1 S285 ; Set temperature limit for heater 1 to 280C
                      M307 H1 A318.9 C165.3 D2.7 B0
                      M307 H0 A312.4 C710.8 D0.8 B0

                      ; Fans
                      M106 P0 S255 ; Set fan 0 tool fan half speed
                      M106 P1 S1 I0 F500 T45 H1 ; Set fan 1 tool1 heatsink fan on at 45 degrees
                      M106 P2 S0 ; Set fan 2 is turned off

                      M501

                      ; Tools
                      M563 P0 D0 H1 F0 ; Define tool 0
                      G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
                      G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

                      ; Automatic saving after power loss is not enabled

                      ; Custom settings are not configured
                      T0

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

                        @flyingscot said in Firmware from 2.02 to 2.05.1:

                        M350 X128 Y128 Z128 E16 ; Configure microstepping without interpolation
                        M92 X800 Y800 Z3200 E408 ; Set steps per mm

                        Try again, but switch to x16 microsteps with interpolation enabled I1. Adjust the steps per mm accordingly.

                        The difference may be that it's using quad stepping in older firmware but not in the newer firmware.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        FlyingScotundefined 1 Reply Last reply Reply Quote 0
                        • FlyingScotundefined
                          FlyingScot @Phaedrux
                          last edited by

                          @phaedrux Morning

                          Unfortunately it is still the same.
                          its strange printing a circle anticlockwise the speed is not constant it slows down between 2 o'clock and 10 o'clock and again between 8 o'clock and 4 o'clock,
                          Back to 2.01 and its fine.
                          Printer is a core x,y

                          Change to config was:
                          M350 X16 Y16 Z16 E16 I1 ; Configure microstepping
                          M92 X100 Y100 Z400 E408 ; Set steps per mm

                          Art

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

                            @flyingscot said in Firmware from 2.02 to 2.05.1:

                            its strange printing a circle anticlockwise the speed is not constant it slows down between 2 o'clock and 10 o'clock and again between 8 o'clock and 4 o'clock,
                            Back to 2.01 and its fine.

                            Is the circle commanded using G2/G3 or using a sequence of G1 moves?

                            The usual cause of slowing down on curves is jerk set too low in M566.

                            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

                            FlyingScotundefined 1 Reply Last reply Reply Quote 0
                            • FlyingScotundefined
                              FlyingScot @dc42
                              last edited by FlyingScot

                              @dc42 I will look into not sure where to look. The test file is a cylinder drawn in solidworks saved as an stl and sliced with cura. it prints well with V2.01 but not in V2.02.

                              M566 in config is: M566 X600 Y600 Z120 E2000

                              Art

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

                                @flyingscot, check that the GCode file does not contain any M205 commands, because they would change the jerk limit. I don't remember which RRF version was the first to support M205.

                                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

                                FlyingScotundefined 1 Reply Last reply Reply Quote 0
                                • FlyingScotundefined
                                  FlyingScot @dc42
                                  last edited by

                                  @dc42 The circle is generated by G1 moves and there is no M205 in the GCode.

                                  Art

                                  FlyingScotundefined 1 Reply Last reply Reply Quote 0
                                  • FlyingScotundefined
                                    FlyingScot @FlyingScot
                                    last edited by

                                    @flyingscot Its now running well on v2.05. It must have been the microstepping with interpolation that fixed it.

                                    I did go back to 2.02 and the problem returned. Back to 2.05 and all is well.

                                    Thanks for your help

                                    Art

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

                                      Glad it's working well now. I suspect that if you'd run with the higher stepping on 2.05 and done a M122 it would have shown some hiccups.

                                      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