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

Do my settings look ok"

Scheduled Pinned Locked Moved
Tuning and tweaking
3
8
765
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.
  • undefined
    Ozzzzzzy
    last edited by 28 Aug 2018, 20:51

    ; BLTouch - Heaters
    M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.

    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S0 ; Drive 2 goes backwards
    M569 P3 S1 ; Drive 3 goes forwards
    M208 X330 Y330 Z400 S0 ; Set axis maxima

    ; Define the X and Y coordinates of the leadscrews.
    ; Must come after M584 (Set drive mapping), M667 (Select CoreXY Mode) and M669 (Choosing Kinematics type)
    ; Motor order: Front right (1), front left (2), rear center (3).
    ; Snn Maximum correction in mm to apply to each leadscrew (optional, default 1.0)
    M671 X378.5:-86.52 Y165.0:165.0 S3.0

    ; Endstops
    M574 X1 Y1 S0 ; X home to min. Y home to max. Normally Closed limit switches.
    M574 Z1 S2 ; Define Z to use Probe. Home to Min
    M350 X32 Y32 Z16 I0 ; Configure microstepping without interpolation
    M350 E16 I0 ; Configure microstepping with interpolation
    M92 X160 Y160 Z400 E390 ; Set steps per mm
    M566 X900 Y900 Z12 E900 ; Set maximum instantaneous speed changes (mm/min)
    M203 X250000 Y250000 Z200 E6000 ; Set maximum speeds (mm/min)
    M201 X6000 Y6000 Z15 E6000 ; Set accelerations (mm/s^2)
    M906 X1000 Y1000 Z1000 E1000 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

    ; Z-Probe
    M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
    G31 P25 X37.4 Y0.0 Z0.60 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
    M557 X95:290 Y85:290 S80 ; Define mesh grid

    ; Heaters
    M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; Set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; Set temperature limit for heater 1 to 270C

    ; Fans

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F1500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

    ; Tools
    M563 P0 D0 H1 ; Define tool 0
    G10 P0 X-4 Y-13 Z0 ; Set tool 0 axis offsets
    G10 P0 R0 S0

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by dc42 29 Aug 2018, 08:46

      • Your M203 X and Y maximum speeds are absurdly high. I suggest you try 12000 i.e. 200mm/sec. You may be able to increase it when you have the machine working well.
      • Your M201 X and Y accelerations are rather high, but not necessarily impossible. I suggest you reduce them to 2000 until everything is working.
      • The M558 X, Y and Z parameters are no longer used by the firmware and can be removed.
      • If you have a BLtouch Z probe then using recent firmware versions you should use P9 in the M558 command, not P5.
      • The M301 H0 command should be removed. Run heater tuning to find what M307 parameters you should use instead.
      • If you know what thermistors you are using, then it's better to put the correct B and C parameters in the m305 commands.

      That's all I spotted.

      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
      • undefined
        Ozzzzzzy
        last edited by 30 Aug 2018, 04:29

        Thats awesome man, thank you.

        1 Reply Last reply Reply Quote 0
        • undefined
          Phaedrux Moderator
          last edited by 30 Aug 2018, 05:20

          You have microstepping interpolation disabled. If you have a Duet 2 board you can enabled it on axis using 16 microsteps which should make your motors a bit quieter.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • undefined
            Ozzzzzzy
            last edited by 1 Sept 2018, 19:28

            If I am ok with the noise should i leave it at 32.

            undefined 1 Reply Last reply 1 Sept 2018, 19:38 Reply Quote 0
            • undefined
              Phaedrux Moderator @Ozzzzzzy
              last edited by 1 Sept 2018, 19:38

              @ozzzzzzy Noise is part of it, but high microstepping can sometimes lead to very high stepping rates that the Duet may not be able to handle. One way to check if this is an issue is after doing a test print use M122 to generate a diagnostic report. Look for the Move heading and see if there are any hiccups or steperrors or under runs. If you do that might indicate that you're missing steps. Especially during high acceleration moves and high speeds.

              Generally speaking 16 microsteps with interpolation is considered the best of both worlds. Manageable step rates with quiet operation.

              What do you seek to gain from 32 microsteps?

              Z-Bot CoreXY Build | Thingiverse Profile

              undefined 1 Reply Last reply 2 Sept 2018, 18:50 Reply Quote 0
              • undefined
                Ozzzzzzy @Phaedrux
                last edited by 2 Sept 2018, 18:50

                @phaedrux I just thought 32 was better, more accurate. I'm switching to 16 with interpolation.

                1 Reply Last reply Reply Quote 0
                • undefined
                  Phaedrux Moderator
                  last edited by 2 Sept 2018, 19:02

                  Once you're up and running you can compare the two. Print the same gcode. Once with 16 and again at 32. Run M122 after each to see if there are hiccups. See if you can tell the difference. Repeat for higher microsteps if you want to see how far it will go. Choose the one that best suits your needs.

                  Z-Bot CoreXY Build | Thingiverse Profile

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