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

    Voron 2.4 3MB6 §EB config issues.

    Scheduled Pinned Locked Moved
    General Discussion
    3
    46
    1.4k
    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.
    • Titus A Duxassundefined
      Titus A Duxass @jay_s_uk
      last edited by

      @jay_s_uk as per - https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @Titus A Duxass
        last edited by

        @Titus-A-Duxass so you're uploading the 3HC firmware file to the system tab?

        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

        Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
        • Titus A Duxassundefined
          Titus A Duxass @jay_s_uk
          last edited by

          @jay_s_uk I follow the instructions on that page.
          Download the file (Duet2and3firmware-345.zip)
          and then upload via the DWC
          Upload System Files button.

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @Titus A Duxass
            last edited by

            @Titus-A-Duxass i don't know why its not updating that way then.
            you could try turning the machine off, and turning all the dip switches off on the 3HC. This causes the board to request and update the firmware on startup https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_3HC#address
            can you also check what version of DWC you're running? it shows under general settings

            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

            Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
            • Titus A Duxassundefined
              Titus A Duxass @jay_s_uk
              last edited by

              @jay_s_uk Thanks, that forced it -
              21.12.2022, 11:21:12 M115 B1
              Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4 (2022-10-14 11:45:56)

              21.12.2022, 11:22:45 M122 B1
              Diagnostics for board 1:
              Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4 (2022-10-14 11:45:56)
              Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
              All averaging filters OK
              Never used RAM 158932, free system stack 200 words
              Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,99) MAIN(running,91.2%,441) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0%
              Last reset 00:02:06 ago, cause: power up
              Last software reset data not available
              Driver 0: pos 0, 1746.2 steps/mm,standstill, SG min 0, mspos 2, reads 27429, writes 16 timeouts 0, steps req 0 done 0
              Driver 1: pos 0, 320.0 steps/mm,standstill, SG min 0, mspos 2, reads 27430, writes 16 timeouts 0, steps req 0 done 0
              Driver 2: pos 0, 320.0 steps/mm,standstill, SG min 0, mspos 2, reads 27430, writes 16 timeouts 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 -1/8, peak Rx sync delay 178, resyncs 0/0, no step interrupt scheduled
              VIN voltage: min 24.1, current 24.2, max 24.2
              V12 voltage: min 12.2, current 12.2, max 12.2
              MCU temperature: min 32.5C, current 33.8C, max 33.9C
              Last sensors broadcast 0x00000000 found 0 173 ticks ago, 0 ordering errs, loop time 0
              CAN messages queued 1045, send timeouts 0, received 1146, lost 0, free buffers 37, min 37, error reg 0
              dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

              M122
              === Diagnostics ===
              RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (standalone mode)
              Board ID: 08DJM-9P63L-DJ3T8-6JKDA-3SJ6N-KB7MA
              Used output buffers: 3 of 40 (18 max)
              === RTOS ===
              Static ram: 152760
              Dynamic ram: 97332 of which 184 recycled
              Never used RAM 100396, free system stack 202 words
              Tasks: NETWORK(ready,31.9%,210) ETHERNET(notifyWait,0.1%,441) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,91) MAIN(running,60.0%,925) IDLE(ready,0.1%,30), total 100.0%
              Owned mutexes:
              === Platform ===
              Last reset 00:02:34 ago, cause: power up
              Last software reset details not available
              Error status: 0x00
              Step timer max interval 126
              MCU temperature: min 33.1, current 41.5, max 41.6
              Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
              12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
              Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
              Events: 0 queued, 0 completed
              Driver 0: standstill, SG min 0, mspos 8, reads 6751, writes 11 timeouts 0
              Driver 1: standstill, SG min 0, mspos 2, reads 6748, writes 14 timeouts 0
              Driver 2: standstill, SG min 0, mspos 8, reads 6751, writes 11 timeouts 0
              Driver 3: standstill, SG min 0, mspos 2, reads 6748, writes 14 timeouts 0
              Driver 4: standstill, SG min 0, mspos 2, reads 6748, writes 14 timeouts 0
              Driver 5: standstill, SG min 0, mspos 2, reads 6749, writes 14 timeouts 0
              Date/time: 2022-12-21 11:23:11
              Slowest loop: 21.06ms; fastest: 0.05ms
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 25.0MBytes/sec
              SD card longest read time 3.0ms, write time 0.0ms, max retries 0
              === Move ===
              DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === AuxDDARing ===
              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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
              Heater 1 is on, I-accum = 0.0
              === GCodes ===
              Segments left: 0
              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
              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 empty
              === CAN ===
              Messages queued 1401, received 1276, lost 0, boc 0
              Longest wait 2ms for reply type 6024, peak Tx sync delay 6, free buffers 50 (min 49), ts 773/772/0
              Tx timeouts 0,0,0,0,0,0
              === Network ===
              Slowest loop: 17.69ms; fastest: 0.03ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
              HTTP sessions: 1 of 8
              = Ethernet =
              State: active
              Error counts: 0 0 0 0 0 0
              Socket states: 5 2 2 2 2 0 0 0
              === Multicast handler ===
              Responder is inactive, messages received 0, responses 0

              jay_s_ukundefined dc42undefined 2 Replies Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @Titus A Duxass
                last edited by

                @Titus-A-Duxass fantastic. now go back to using your printer as you were before and see if you still have issues. there are a few of us (me included) that run v2.4's with RRF

                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
                • dc42undefined
                  dc42 administrators @Titus A Duxass
                  last edited by

                  @Titus-A-Duxass so is it working now or are there still problems?

                  How did two drivers on the 6HC come to be faulty?

                  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

                  Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
                  • Titus A Duxassundefined
                    Titus A Duxass @dc42
                    last edited by

                    @dc42 No it still has issues.
                    X and Y home as should.
                    Z motors along to 0X0Y and then hangs until it times out, you can here some motors running.

                    I bought the board knowing that the two drivers are kaputt, I suspect that there are more failures on the board.

                    So I either have to find another board or strip it out and fit a BTT Manta M8P that I have. This is not something that I want to do as a it means replacing all the connectors.

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @Titus A Duxass
                      last edited by

                      @Titus-A-Duxass can you try downgrading the mainboard to 3.4.4?

                      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

                      Titus A Duxassundefined 2 Replies Last reply Reply Quote 0
                      • Titus A Duxassundefined
                        Titus A Duxass @jay_s_uk
                        last edited by

                        @jay_s_uk Wait - my mistake! The Z is homing, it's just going extremely slow! Should be done about Tuesday.

                        1 Reply Last reply Reply Quote 1
                        • dc42undefined
                          dc42 administrators @Titus A Duxass
                          last edited by

                          @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                          M574 Z1 S2 ; configure Z-probe endstop for low end on Z

                          You should remove that line. Endstop mode S2 is used only when the Z probe is used to home axes other than Z.

                          Please post your homeall.g and homez.g files.

                          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

                          Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
                          • Titus A Duxassundefined
                            Titus A Duxass @jay_s_uk
                            last edited by

                            @jay_s_uk Oops!
                            21.12.2022, 11:34:07 G28 Z
                            Error: Probe was not triggered during probing move
                            Error: Probe was not triggered during probing move

                            This happened with the Z at about +100mm

                            1 Reply Last reply Reply Quote 0
                            • Titus A Duxassundefined
                              Titus A Duxass @dc42
                              last edited by

                              @dc42
                              ; homeall.g
                              ; called to home all axes
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Dec 18 2022 17:39:32 GMT+0100 (Mitteleuropäische Normalzeit)
                              G91 ; relative positioning
                              G1 H2 Z5 F6000 ; lift Z relative to current position
                              G1 H1 X295 Y295 F1800 ; move quickly to X or Y endstop and stop there (first pass)
                              G1 H1 X295 ; home X axis
                              G1 H1 Y295 ; home Y axis
                              G1 X-5 Y-5 F6000 ; go back a few mm
                              G1 H1 X295 F360 ; move slowly to X axis endstop once more (second pass)
                              G1 H1 Y295 ; then move slowly to Y axis endstop
                              G90 ; absolute positioning
                              G1 X40 Y15 F6000 ; go to first bed probe point and home Z
                              G30 ; home Z by probing the bed

                              ; Uncomment the following lines to lift Z after probing
                              ;G91 ; relative positioning
                              ;G1 Z5 F100 ; lift Z relative to current position
                              ;G90 ; absolute positioning

                              ; homez.g
                              ; called to home the Z axis
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Dec 18 2022 17:39:32 GMT+0100 (Mitteleuropäische Normalzeit)
                              G91 ; relative positioning
                              G1 H2 Z5 F6000 ; lift Z relative to current position
                              G90 ; absolute positioning
                              G1 X40 Y15 F6000 ; go to first probe point
                              G30 ; home Z by probing the bed

                              ; Uncomment the following lines to lift Z after probing
                              ;G91 ; relative positioning
                              ;G1 Z5 F100 ; lift Z relative to current position
                              ;G90 ; absolute positioning

                              jay_s_ukundefined 2 Replies Last reply Reply Quote 0
                              • jay_s_ukundefined
                                jay_s_uk @Titus A Duxass
                                last edited by jay_s_uk

                                @Titus-A-Duxass can you post your config as well just so we can see your probe settings?
                                btw, what probe arrangement are you using?

                                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

                                Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
                                • Titus A Duxassundefined
                                  Titus A Duxass @jay_s_uk
                                  last edited by

                                  @jay_s_uk

                                  Okay, I switch it off and manually lowered Z, it now homes. I think there maybe a time out issue.

                                  ; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
                                  ; executed by the firmware on start-up
                                  ;
                                  ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Dec 18 2022 17:39:32 GMT+0100 (Mitteleuropäische Normalzeit)

                                  ; General preferences
                                  G90 ; send absolute coordinates...
                                  M83 ; ...but relative extruder moves
                                  M550 P"voron" ; set printer name
                                  M669 K1 ; select CoreXY mode

                                  ; Wait a moment for the CAN expansion boards to start
                                  G4 S2

                                  ; Network
                                  M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
                                  M586 P0 S1 ; enable HTTP
                                  M586 P1 S0 ; disable FTP
                                  M586 P2 S0 ; disable Telnet

                                  ; Drives
                                  M584 X1.1 Y1.2 Z0.1:0.5:0.3:0.4 E1.0 ; set drive mapping

                                  M569 P1.1 S0 ; A motor goes forwards
                                  M569 P1.2 S0 ; B motor goes forwards

                                  M569 P0.1 S1 ; FL goes forwards
                                  M569 P0.5 S0 ; RL goes backwards
                                  M569 P0.3 S0 ; RR goes forwards
                                  M569 P0.4 S1 ; FR goes backwards

                                  M569 P1.0 S0 ; Extruder goes backwards

                                  M350 Z64 I0 ; configure microstepping without interpolation
                                  M350 X64 Y64 E64 I1 ; configure microstepping with interpolation
                                  M92 X320.00 Y320.00 Z400.00 E1746.16 ; set steps per mm
                                  M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                                  M203 X60000.00 Y60000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
                                  M201 X6000.00 Y6000.00 Z4000.00 E250.00 ; set accelerations (mm/s^2)
                                  M906 X1500 Y1500 Z1200 E400 I30 ; set motor currents (mA) and motor idle factor in per cent
                                  M84 S10 ; Set idle timeout

                                  ; Axis Limits
                                  M208 X0 Y0 Z0 S1 ; set axis minima
                                  M208 X290 Y290 Z250 S0 ; set axis maxima

                                  ; Endstops
                                  M574 X2 S1 P"^io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin ^io1.in
                                  M574 Y2 S1 P"^io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ^io2.in

                                  ; Z-Probe
                                  M558 P5 C"^io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
                                  G31 P500 X0 Y25 Z2.5 ; set Z probe trigger value, offset and trigger height
                                  M557 X40:260 Y40:260 S20 ; define mesh grid

                                  ; Heaters
                                  M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
                                  M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
                                  M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
                                  M140 H0 ; map heated bed to heater 0
                                  M143 H0 S120 ; set temperature limit for heater 0 to 120C
                                  M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
                                  M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
                                  M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
                                  M143 H1 S280 ; set temperature limit for heater 1 to 280C

                                  ; Fans
                                  M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
                                  M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
                                  M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
                                  M106 P1 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on

                                  ; Tools
                                  M563 P0 S"Revo" D0 H1 F0:1 ; 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

                                  ; Custom settings
                                  M584 Z0.1:0.5:0.3:0.4

                                  ; Miscellaneous
                                  M501 ; load saved parameters from non-volatile memory
                                  T0 ; select first tool

                                  1 Reply Last reply Reply Quote 0
                                  • jay_s_ukundefined
                                    jay_s_uk @Titus A Duxass
                                    last edited by

                                    @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                    G1 X40 Y15 F6000 ; go to first bed probe point and home Z

                                    so really you want to change that to the centre of your bed, taking into account the probe offset (i.e if the centre of X is 150 and the probe is 10mm to the left of the nozzle you would move to 160)

                                    same goes for homez

                                    @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                    M350 Z64 I0 ; configure microstepping without interpolation
                                    M350 X64 Y64 E64 I1

                                    i would stick to x16 rather than x64. you don't gain anything

                                    @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                    F120

                                    your probe speed is to move at 2mm/s. thats ok for a second pass but your first pass probably wants to be quicker. you can set a first and second probing speed like this F1200:120

                                    @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                    ; Custom settings
                                    M584 Z0.1:0.5:0.3:0.4

                                    you don't need this again

                                    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

                                    Titus A Duxassundefined 2 Replies Last reply Reply Quote 0
                                    • Titus A Duxassundefined
                                      Titus A Duxass
                                      last edited by

                                      I really appreciated your help this.
                                      Now you are stretching my 61yr old brain.
                                      I have a bed that is 300 x 300 so centre will be 150 x 150 - you can see the probe/nozzle set up in the photos.

                                      Voron02.jpg Voron01.jpg

                                      1 Reply Last reply Reply Quote 0
                                      • Titus A Duxassundefined
                                        Titus A Duxass @jay_s_uk
                                        last edited by

                                        @jay_s_uk

                                        @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                        M350 Z64 I0 ; configure microstepping without interpolation
                                        M350 X64 Y64 E64 I1

                                        i would stick to x16 rather than x64. you don't gain anything

                                        @Titus-A-Duxass said in Voron 2.4 3MB6 §EB config issues.:

                                        So I simply overwrite 64 with 16 in config.g?

                                        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                        • jay_s_ukundefined
                                          jay_s_uk @Titus A Duxass
                                          last edited by

                                          @Titus-A-Duxass you'll also have to divide your steps per mm by 4

                                          for the probe point you'd move to X150 Y125

                                          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

                                          Titus A Duxassundefined 1 Reply Last reply Reply Quote 0
                                          • Titus A Duxassundefined
                                            Titus A Duxass @jay_s_uk
                                            last edited by

                                            @jay_s_uk said in Voron 2.4 3MB6 §EB config issues.:

                                            F120

                                            your probe speed is to move at 2mm/s. thats ok for a second pass but your first pass probably wants to be quicker. you can set a first and second probing speed like this F1200:120

                                            Sorry but you've lost me there.
                                            Which file is this in and what am I editing.

                                            I'm going to need a beer after this!

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