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

    Setting up DUET wifi + Duex5 - help needed

    Scheduled Pinned Locked Moved
    General Discussion
    4
    31
    4.3k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      Yes H is the heater number. Heater 100 is the default virtual heater number for the CPU temperature.

      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
      • CTRDevelopmentsundefined
        CTRDevelopments
        last edited by

        Many thanks for the help. I have got most things working but have a mechanical issue on the z axis. I have redesigned and am printing (on a different print) the new parts and waiting for some others to arrive in the post! Cheers

        1 Reply Last reply Reply Quote 0
        • CTRDevelopmentsundefined
          CTRDevelopments
          last edited by

          Sorry for the long delay in getting back. Things always seem to take longer than hoped! However I now have the z axis working properly and the IR sensor triggering. I have a 3 z motor setup, so am hoping to do 'hardware' bed leveling as well as mesh leveling. However, I am running into a strange issue. Note, I have updated to firmware 1.21RC5, and when using the machine control tab all axis move correctly and homing of x and y works perfectly

          When i call home z from the web interface the machine appears to randomly move and then all of a sudden it goes to a point that almost appears to be the probe point. During the random moves however it crashed the x axis into the hard stop and then the motor skips. I then get worried and turn it off before it breaks something!

          I know it must be something i am doing but not sure what.

          Any help greatly appreciated

          thanks

          Bed.g
          M561 ; clear any bed transform

          ; Probe the bed at 5 points
          G30 P0 X40 Y280 Z-99999
          G30 P1 X450 Y40 Z-99999
          G30 P2 X450 Y390 Z-99999 S3

          config.g
          ; Configuration file for Duet WiFi (firmware version 1.20 or newer)
          ; executed by the firmware on start-up
          ;
          ; generated by RepRapFirmware Configuration Tool on Mon Jan 01 2018 19:47:24 GMT+0000 (GMT Standard Time)

          ; General preferences
          M111 S0 ; Debugging off
          G21 ; Work in millimetres
          G90 ; Send absolute coordinates…
          M83 ; ...but relative extruder moves
          M555 P2 ; Set firmware compatibility to look like Marlin
          M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Configure automatic saving on power loss
          M208 X0 Y-25 Z0 S1 ; Set axis minima
          M208 X450 Y415 Z400 S0 ; Set axis maxima

          ; Endstops
          M574 X1 S1 ; Set active high endstops
          M915 P5:6 S6 R0 ; Configure Stall endstops
          M574 Y2 S3 ; Set Stall endstops
          M574 Z1 S2 ; Set endstops controlled by probe
          M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
          G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
          M557 X15:385 Y15:400 S20 ; Define mesh grid

          M564 H0 ; Allow movements before homing

          ; Drives
          M569 P0 S1 ; Drive 0 goes forwards, X Axis
          M569 P3 S1 ; Drive 3 goes forwards, E0
          M569 P4 S1 ; Drive 4 goes forwards, E1
          M569 P5 S1 ; Drive 5 goes forwards, Y Axis
          M569 P6 S1 ; Drive 6 goes forwards, Y Axis
          M569 P7 S1 ; Drive 7 goes forwards, Z Axis
          M569 P8 S1 ; Drive 8 goes forwards, Z Axis
          M569 P9 S1 ; Drive 9 goes forwards, Z Axis

          M584 X0 Y5:6 Z7:8:9 E3:4 ; New drive mapping

          M671 X-85:620:620 Y280:40:480 S2 ; Ballscrews at centre left, front right and rear right

          M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
          M92 X320 Y320 Z1600 E420 ; Set steps per mm
          M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
          M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
          M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
          M906 X1000 Y1000 Z2100 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
          M84 S30 ; Set idle timeout

          ; 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 X200 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 100
          M143 H1 S280 ; Set temperature limit for heater 1 to 280C

          ; Tools
          M563 P0 D0 H1 ; 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

          ; Network
          M550 PCTR 3DPrintR ; Set machine name
          M552 S1 ; Enable network
          ;*** Access point is configured manually via M587
          M586 P0 S1 ; Enable HTTP
          M586 P1 S0 ; Disable FTP
          M586 P2 S0 ; Disable Telnet

          ; Fans
          M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
          M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
          M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
          M106 P7 L30 H100 T10:30 ; Case Cooling fan

          ; Custom settings are not configured

          homez.g
          ; homez.g
          ; called to home the Z axis
          ;
          ; generated by RepRapFirmware Configuration Tool on Mon Jan 01 2018 19:47:24 GMT+0000 (GMT Standard Time)
          G91 ; relative positioning
          G1 Z5 F6000 ; lift Z relative to current position
          G90 ; absolute positioning
          G1 X40 Y40 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

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

            If you upgraded from pre-1.19 firmware, delete any default deployprobe.g and retractprobe.g files that came on the SD card.

            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
            • CTRDevelopmentsundefined
              CTRDevelopments
              last edited by

              Super, it now no longer wanders around somewhat randomly! Many thanks.
              To call the leadscrew adjustments i call G32, which seems to work and the console tells me the adjustments it has made, even better!

              The printer is quite large, X and Y approx 500mm, so can I still use mesh bed levelling also? I realise it will add wear to the ballscrews but given the size I am sure the bed will have slight curvature etc.

              Then presumably I can add the G32 command, and whatever call the mesh bed at the start of each print gcode file?

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

                Yes you can still use G29 mesh bed compensation after G32 bed levelling. However, some users find they need to run G32 more than once to get the bed level, if it is a long way off level to start with. Firmware 1.21 includes a "fudge factor" parameter in the M671 command to help achieve faster convergence.

                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
                • CTRDevelopmentsundefined
                  CTRDevelopments
                  last edited by

                  OK, thanks. Is there an auto way of calling it multiple times, or do I just call G32 5 times at the start of the file? I have had a look at M671 but which is the fudge factor? Or do you mean this is inbuilt in the firmware?

                  I have another quick question on G31 - probe setup. I am using your IR probe and it is behind the nozzle (+ve y direction) and to the left of the nozzle (-ve x direction). Would this mean I need to write in the config.g file
                  G31 X-2.0 Y30

                  thanks

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

                    Just call G32 as many times as needed (2 may be enough in normal use). Or duplicate the sequence of G30 commands in bed.g.

                    I'm sorry, I forgot to document the M671 F parameter in the GCodes wiki page in the Duet3D wiki. I've corrected that.

                    Your G30 offsets are correct because they are measured from the print head reference point to the probe, just like tool offsets are.

                    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
                    • CTRDevelopmentsundefined
                      CTRDevelopments
                      last edited by

                      OK, many thanks for the update, I will give this a try this evening

                      1 Reply Last reply Reply Quote 0
                      • CTRDevelopmentsundefined
                        CTRDevelopments
                        last edited by

                        @ctrdevelopments said in Setting up DUET wifi + Duex5 - help needed:

                        M208 X0 Y-25 Z0 S1 ; Set axis minim

                        Hi, I am still struggling with mesh bed leveling. If I call G32 that all seems to work, if I call it 2-3 times the changes very rapidly go to zero. However, I then call G29 and I dont seem to be able to probe the whole bed.

                        in config file I have

                        M557 X15:450 Y15:410 S50 ; Define mesh grid

                        However, it only probes in 100mm steps and only goes to x 352 and y 285

                        I have also got this in config

                        M208 X-8 Y-18 Z0 S1 ; Set axis minima
                        M208 X451 Y410 Z400 S0 ; Set axis maxima
                        G31 P500 X-12 Y55 Z2.5 ; Set Z probe trigger value, offset and trigger height

                        Cheers

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

                          Please run M557 without parameters to check that your M557 command in config.g was accepted.

                          Which firmware version are you using?

                          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
                          • CTRDevelopmentsundefined
                            CTRDevelopments
                            last edited by

                            Dc, all seems fixed now. Not sure what I changed this morning that I hadn't done previously, but it's working.

                            I have used all the motor outputs on the duet and the duex5. Is there a way to get anymore? I am thinking of implementing more extruder but cannot currently.

                            Cheers

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

                              You can connect 2 more stepper drivers to the CONN_LCD connector. See the wiki page on connecting external drivers.

                              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
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA