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

    Duet3D 1HCL - Closed Loop Controller Beta test

    Scheduled Pinned Locked Moved
    Hardware dev
    20
    209
    18.9k
    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.
    • supertb1undefined
      supertb1 @T3P3Tony
      last edited by

      @t3p3tony I disconnect the motor and turn it one full revolution then M122 P50, resulting:
      Diagnostics for board 50:
      Duet EXP1HCL firmware version 3.4.0beta3 (2021-08-24 14:56:43)
      Bootloader ID: SAME5x bootloader version 2.4beta (2021-07-23)
      Never used RAM 52992, free system stack 2578 words
      Tasks: Move(notifyWait,0.0%,126) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,72) TMC(notifyWait,15.5%,28) CLSend(notifyWait,0.0%,150) CLData(notifyWait,0.0%,142) MAIN(running,82.6%,380) IDLE(ready,0.0%,39) AIN(notifyWait,1.9%,265), total 100.0%
      Last reset 00:36:45 ago, cause: software
      Last software reset time unknown, reason: HardFault bfarValid precise, available RAM 51580, slot 0
      Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00430803 BFAR 0x20030008 SP 0x2001eba8 Task MAIN Freestk 531 ok
      Stack: 00000000 00000000 00000002 20030000 00030f39 0001b8f9 0001ea4c 41000000 bf800000 00000000 533c0605 04001200 a808a700 06420000 c3210828 19a21429 50708239 5d000040 2a60041c 5dd40122 4143051f 41200000 41c22c02 4142f6d6 20000010 0002699b 00000002
      Closed loop enabled: yes, live status: 0x4, encoder type linearQuadrature, pre-error threshold: 20.000000, error threshold: 100.000000, coil A polarity: +, coil B polarity: -, tuning: 0, tuning error: 0x1f, position -1515866801, raw count = 4010, collecting data: no, ultimateGain=0.000000, oscillationPeriod=0.000000
      Driver 0: position -50588, 106.5 steps/mm, standstill, reads 27092, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
      Moves scheduled 5, completed 5, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
      Peak sync jitter -5/4, peak Rx sync delay 182, resyncs 0/0, no step interrupt scheduled
      VIN: 24.3V, V12: 12.2V
      MCU temperature: min 27.4C, current 28.7C, max 28.9C
      Ticks since heat task active 14, ADC conversions started 2187517, completed 2187516, timed out 0, errs 0
      Last sensors broadcast 0x00000000 found 0 18 ticks ago, loop time 0
      CAN messages queued 11760, send timeouts 0, received 13191, lost 0, free buffers 37, min 37, error reg 0
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

      T3P3Tonyundefined 2 Replies Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @supertb1
        last edited by

        @lirwin17 can you have a look at this please

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • T3P3Tonyundefined
          T3P3Tony administrators @supertb1
          last edited by

          @supertb1 please upgrade the 1HCL firmware to the latest here:
          https://www.dropbox.com/sh/qkexrvhgsebbz0g/AAD9gfyS8UIU5Sau311WS1oLa?dl=0

          www.duet3d.com

          supertb1undefined 1 Reply Last reply Reply Quote 0
          • supertb1undefined
            supertb1 @T3P3Tony
            last edited by

            @t3p3tony I updated my firmware using the link above, E-stop, Ran
            M569.6 P50.0 V31 then M122 B50:
            M122 B50
            Diagnostics for board 50:
            Duet EXP1HCL firmware version 3.4.0beta3+1 (2021-09-14 15:07:31)
            Bootloader ID: SAME5x bootloader version 2.4beta (2021-07-23)
            Never used RAM 51580, free system stack 2582 words
            Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,95) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,81) CanClock(notifyWait,0.0%,72) TMC(notifyWait,30.6%,358) CLSend(notifyWait,0.0%,148) CLData(notifyWait,0.0%,142) MAIN(running,67.4%,410) IDLE(ready,0.0%,39) AIN(notifyWait,2.0%,265), total 100.0%
            Last reset 00:02:18 ago, cause: software
            Last software reset time unknown, reason: HardFault bfarValid precise, available RAM 51580, slot 0
            Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00430803 BFAR 0x20030008 SP 0x2001eba8 Task MAIN Freestk 531 ok
            Stack: 00000000 00000000 00000002 20030000 00030f39 0001b8f9 0001ea4c 41000000 bf800000 00000000 533c0605 04001200 a808a700 06420000 c3210828 19a21429 50708239 5d000040 2a60041c 5dd40122 4143051f 41200000 41c22c02 4142f6d6 20000010 0002699b 00000002
            Closed loop enabled: no, live status: 0, encoder type none, pre-error threshold: 0.000000, error threshold: 0.000000, reverse polarity: no, tuning: 0, tuning error: 0, collecting data: no, ultimateGain=0.000000, oscillationPeriod=0.000000, Control loop runtime (ms): min=0.000000, max=0.056000, avg=0.000000, Control loop frequency (Hz): min=5859.375000, max=18292.683594, avg=17441.861328
            Driver 0: pos 0, 106.5 steps/mm, standstill, reads 56348, writes 19 timeouts 0, SG min/max 0/0, steps req 0 dMoves 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 -3/4, peak Rx sync delay 183, resyncs 0/0, no step interrupt scheduled
            VIN: 24.3V, V12: 12.2V
            MCU temperature: min 28.0C, current 28.0C, max 28.4C
            Ticks since heat task active 200, ADC conversions started 136156, completed 136155, timed out 0, errs 0
            Last sensors broadcast 0x00000000 found 0 204 ticks ago, loop time 0
            CAN messages queued 1154, send timeouts 0, received 1251, lost 0, free buffers 37, min 37, error reg 0
            dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
            9/20/2021, 8:13:33 AM M569.6 P50.0 V31
            Error: M569.6: Drive is not in closed loop mode.

            as above in my config Channel 50 is in closed loop mode

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @supertb1
              last edited by

              @supertb1 can you increase the G4 S1 in your config to at least S2 if not S3?

              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

              supertb1undefined 3 Replies Last reply Reply Quote 0
              • supertb1undefined
                supertb1 @jay_s_uk
                last edited by

                @jay_s_uk increased S1 to S3:
                ; Drives
                G4 S3 ;wait for expansion boards to start
                M569.1 P50.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 50 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
                M569.1 P51.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 51 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
                M569 P50.0 D4 S1 ; Configure the motor on the 1HCL at can address 50 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) X axis
                M569 P51.0 D2 S1 ; Configure the motor on the 1HCL at can address 51 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) Y axis
                M569 P0.0 S1 ; physical drive 0.0 goes forwards Z 1-2 axis
                M569 P0.4 S1 ; physical drive 0.4 goes forwards Extruder
                M584 X50.0 Y51.0 Z0.0:0.1 E0.4 ; set drive mapping
                M671 X-122.25:689.20 Y0:0 S3.0 ; leadscrews at left (connected to Z0) and right (connected to Z1) of X axis
                M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation
                M92 X106.5 Y257 Z795.00 E339.00 ; set steps per mm
                M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
                M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
                M906 X1000 Y3000 Z3000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
                M84 S30 ; Set idle timeout
                M917 X0 Y0 ; Set the closed loop axes to have a holding current of zero

                1 Reply Last reply Reply Quote 1
                • supertb1undefined
                  supertb1 @jay_s_uk
                  last edited by

                  @jay_s_uk M122 B50
                  Diagnostics for board 50:
                  Duet EXP1HCL firmware version 3.4.0beta3+1 (2021-09-14 15:07:31)
                  Bootloader ID: SAME5x bootloader version 2.4beta (2021-07-23)
                  Never used RAM 51580, free system stack 2580 words
                  Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,81) CanClock(notifyWait,0.0%,72) TMC(notifyWait,30.6%,358) CLSend(notifyWait,0.0%,148) CLData(notifyWait,0.0%,142) MAIN(running,67.4%,400) IDLE(ready,0.0%,39) AIN(notifyWait,2.0%,265), total 100.0%
                  Last reset 00:01:06 ago, cause: software
                  Last software reset time unknown, reason: HardFault bfarValid precise, available RAM 51580, slot 0
                  Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00430803 BFAR 0x20030008 SP 0x2001eba8 Task MAIN Freestk 531 ok
                  Stack: 00000000 00000000 00000002 20030000 00030f39 0001b8f9 0001ea4c 41000000 bf800000 00000000 533c0605 04001200 a808a700 06420000 c3210828 19a21429 50708239 5d000040 2a60041c 5dd40122 4143051f 41200000 41c22c02 4142f6d6 20000010 0002699b 00000002
                  Closed loop enabled: no, live status: 0, encoder type none, pre-error threshold: 0.000000, error threshold: 0.000000, reverse polarity: no, tuning: 0, tuning error: 0, collecting data: no, ultimateGain=0.000000, oscillationPeriod=0.000000, Control loop runtime (ms): min=0.000000, max=0.057333, avg=0.001333, Control loop frequency (Hz): min=8241.758789, max=18750.000000, avg=17441.861328
                  Driver 0: pos 0, 106.5 steps/mm, standstill, reads 52300, writes 19 timeouts 0, SG min/max 0/0, steps req 0 dMoves 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 -4/4, peak Rx sync delay 177, resyncs 0/0, no step interrupt scheduled
                  VIN: 24.3V, V12: 12.2V
                  MCU temperature: min 27.8C, current 28.0C, max 28.0C
                  Ticks since heat task active 110, ADC conversions started 65762, completed 65761, timed out 0, errs 0
                  Last sensors broadcast 0x00000000 found 0 115 ticks ago, loop time 0
                  CAN messages queued 579, send timeouts 0, received 603, lost 0, free buffers 37, min 37, error reg 0
                  dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
                  9/20/2021, 8:50:40 AM M569.6 P50.0 V31
                  Error: M569.6: Drive is not in closed loop mode.

                  lirwin17undefined 1 Reply Last reply Reply Quote 0
                  • supertb1undefined
                    supertb1 @jay_s_uk
                    last edited by

                    @jay_s_uk No change

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @supertb1
                      last edited by

                      @supertb1 worth a shot

                      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 1
                      • lirwin17undefined
                        lirwin17 @supertb1
                        last edited by

                        Hi @supertb1,

                        Sorry, I'm not 100% clear on the actual issue here. Thanks for providing your M122 output, from tuning error: 0x1f, it seems like no runtime tuning has happened. Similar to when an axis is un-homed, a driver that is untuned will not move, so if the issue is that the axis isn't moving then that would be the expected behaviour in this instance.
                        However, if you have run tuning, there is a deeper issue here.

                        Details of tuning can be found on this page. Specifically, the two 'what do I need to do?' sections (1, 2) are compulsory before the system will move (eventually these should be part of the online config tool, but not just yet for the beta test)

                        If you weren't aware of this page in the docs, that's really useful for us to know because it tells us we need to draw more attention to that page 🙂

                        Thanks!
                        Louis

                        supertb1undefined 4 Replies Last reply Reply Quote 0
                        • supertb1undefined
                          supertb1 @lirwin17
                          last edited by

                          @lirwin17 When I manually try to tune the X axis which is on closed loop mode on my config with everything selected it gives this error:
                          M569.5 P50.0 S500 A0 R0 D8191 V71
                          Error: M569.5: Drive is not in closed loop mode
                          M569.5 P50.0 S500 A0 R0 D8191 V71

                          Here is my config:
                          G4 S3 ;wait for expansion boards to start
                          M569.1 P50.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 50 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
                          M569.1 P51.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 51 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
                          M569 P50.0 D4 S1 ; Configure the motor on the 1HCL at can address 50 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) X axis
                          M569 P51.0 D2 S1 ; Configure the motor on the 1HCL at can address 51 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) Y axis
                          M569 P0.0 S1 ; physical drive 0.0 goes forwards Z 1-2 axis
                          M569 P0.4 S1 ; physical drive 0.4 goes forwards Extruder
                          M584 X50.0 Y51.0 Z0.0:0.1 E0.4 ; set drive mapping
                          M671 X-122.25:689.20 Y0:0 S3.0 ; leadscrews at left (connected to Z0) and right (connected to Z1) of X axis
                          M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation
                          M92 X106.5 Y257 Z795.00 E339.00 ; set steps per mm
                          M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                          M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
                          M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
                          M906 X1000 Y3000 Z3000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
                          M84 S30 ; Set idle timeout
                          M917 X0 Y0 ; Set the closed loop axes to have a holding current of zero

                          1 Reply Last reply Reply Quote 0
                          • supertb1undefined
                            supertb1 @lirwin17
                            last edited by

                            @lirwin17 and it fails to manually tune

                            1 Reply Last reply Reply Quote 0
                            • supertb1undefined
                              supertb1 @lirwin17
                              last edited by

                              @lirwin17 with just raw encoder reading and step maneuver it throws fault: M569.5 P50.0 S500 A0 R0 D1 V64 and maintains that the motor is not in closed loop mode

                              1 Reply Last reply Reply Quote 0
                              • supertb1undefined
                                supertb1 @lirwin17
                                last edited by

                                @lirwin17 with just current motor steps and target motor steps selected performing the step maneuver yields: M569.5 P50.0 S500 A0 R0 D6 V64 and maintains that the drive is not in closed loop mode

                                T3P3Tonyundefined lirwin17undefined 2 Replies Last reply Reply Quote 0
                                • T3P3Tonyundefined
                                  T3P3Tony administrators @supertb1
                                  last edited by

                                  @supertb1 i think you first need to tune the motors

                                  M569.6

                                  as outlined here:
                                  https://duet3d.dozuki.com/Wiki/Tuning_the_Duet_3_Expansion_1HCL#Section_Tuning

                                  If you are using a quadrature encoder (i.e. your M569.1 command includes T1 or T2), then from the table above, manoeuvres 1, 2, 4, 8 and 16 are required - this means that they must be run every time the printer is powered on. This can be achieved by using the following command:
                                  M569.6 P##.# V31 ; Where P##.# is the driver address to tune

                                  www.duet3d.com

                                  supertb1undefined 1 Reply Last reply Reply Quote 0
                                  • lirwin17undefined
                                    lirwin17 @supertb1
                                    last edited by

                                    @supertb1
                                    Hmm there are are a few M122 outputs so I've lost track a little...

                                    The first ones show Closed loop enabled: yes, but then some later ones show no.

                                    The problem seems to be that when you come to run the tuning move, that yes has flipped to a no...

                                    Please could you run through the following:

                                    • power up (so config.g runs)
                                    • run a manoeuvre command - it might be best to start with the simplest one V1

                                    And at each point check M122 to see when yes flipps to no. Is it showing yes after config.g has run, or is it only when the move is run that it flips to no?

                                    supertb1undefined 6 Replies Last reply Reply Quote 0
                                    • supertb1undefined
                                      supertb1 @lirwin17
                                      last edited by

                                      @lirwin17 That yes to the closed loop enable was there before I updated the 1HCL board to the latest firmware and now at power up it reports "no" to the close loop enable

                                      1 Reply Last reply Reply Quote 0
                                      • supertb1undefined
                                        supertb1 @lirwin17
                                        last edited by

                                        @lirwin17 9/20/2021, 4:20:18 PM M122 B50
                                        Diagnostics for board 50:
                                        Duet EXP1HCL firmware version 3.4.0beta3+1 (2021-09-14 15:07:31)
                                        Bootloader ID: SAME5x bootloader version 2.4beta (2021-07-23)
                                        Never used RAM 51580, free system stack 2594 words
                                        Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,81) CanClock(notifyWait,0.0%,72) TMC(notifyWait,30.6%,358) CLSend(notifyWait,0.0%,148) CLData(notifyWait,0.0%,142) MAIN(running,67.4%,414) IDLE(ready,0.0%,39) AIN(notifyWait,2.0%,265), total 100.0%
                                        Last reset 00:02:47 ago, cause: power up
                                        Last software reset time unknown, reason: HardFault bfarValid precise, available RAM 51580, slot 0
                                        Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00430803 BFAR 0x20030008 SP 0x2001eba8 Task MAIN Freestk 531 ok
                                        Stack: 00000000 00000000 00000002 20030000 00030f39 0001b8f9 0001ea4c 41000000 bf800000 00000000 533c0605 04001200 a808a700 06420000 c3210828 19a21429 50708239 5d000040 2a60041c 5dd40122 4143051f 41200000 41c22c02 4142f6d6 20000010 0002699b 00000002
                                        Closed loop enabled: no, live status: 0, encoder type none, pre-error threshold: 0.000000, error threshold: 0.000000, reverse polarity: no, tuning: 0, tuning error: 0, collecting data: no, ultimateGain=0.000000, oscillationPeriod=0.000000, Control loop runtime (ms): min=0.000000, max=0.058667, avg=0.000000, Control loop frequency (Hz): min=7281.553223, max=18292.683594, avg=17441.861328
                                        Driver 0: pos 0, 106.5 steps/mm, standstill, reads 42667, writes 19 timeouts 0, SG min/max 0/0, steps req 0 dMoves 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 -5/4, peak Rx sync delay 181, resyncs 0/0, no step interrupt scheduled
                                        VIN: 24.3V, V12: 12.2V
                                        MCU temperature: min 27.4C, current 29.5C, max 29.5C
                                        Ticks since heat task active 230, ADC conversions started 164966, completed 164965, timed out 0, errs 0
                                        Last sensors broadcast 0x00000000 found 0 235 ticks ago, loop time 0
                                        CAN messages queued 1384, send timeouts 0, received 1509, lost 0, free buffers 37, min 37, error reg 0
                                        dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

                                        1 Reply Last reply Reply Quote 0
                                        • supertb1undefined
                                          supertb1 @lirwin17
                                          last edited by

                                          @lirwin17 I just reinstalled the latest firmware and it is still reporting no to close loop enable at power up

                                          1 Reply Last reply Reply Quote 0
                                          • supertb1undefined
                                            supertb1 @lirwin17
                                            last edited by

                                            @lirwin17 I tried rolling back the 1HCL board firmware to the previous one, still showing no on the enabled... and it won't let me do any of the tuning variables

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