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

    Stepper motors and endstops not appearing in dashboard

    Scheduled Pinned Locked Moved
    Firmware installation
    dashboard
    4
    5
    289
    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.
    • mogfrogundefined
      mogfrog
      last edited by

      I am attempting to connect stepper motors and endstops to a duet 3 board, but nothing turns up in the dashboard. I can control the motors using the console using commands such as G0 H0 X100 Y100 Z100 after adding the command M564 H0 to config.g , as per the information in the following link:

      https://duet3d.dozuki.com/Wiki/FAQ#Section_I_get_this_error_message_Error_G0_G1_insufficient_axes_homed

      Given that the motors can be controlled via the console, is there an additional step I should take to be able to control machine movement from the dashboard, and to get a readout from the endstops?

      I have followed the instructions on https://configtool.reprapfirmware.org/ in order to create the initial config files.

      See the config file generated below:

      ; Configuration file for Duet 3 (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Nov 04 2020 15:02:11 GMT+0000 (Greenwich Mean Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Duet 3" ; set printer name

      ; Drives
      M569 P0.0 S1 ; physical drive 0.0 goes forwards
      M569 P0.1 S1 ; physical drive 0.1 goes forwards
      M569 P0.2 S1 ; physical drive 0.2 goes forwards
      M569 P0.3 S1 ; physical drive 0.3 goes forwards
      M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
      M566 X900.00 Y900.00 Z12.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 X2000 Y2000 Z2000 E1600 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 X230 Y210 Z200 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"io0.in" ; configure active-high endstop for low end on X via pin io0.in
      M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in
      M574 Z1 S1 P"io2.in" ; configure active-high endstop for low end on Z via pin io2.in

      ; Z-Probe
      M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
      M557 X15:215 Y15:195 S20 ; define mesh grid

      ; Heaters
      M308 S0 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp1
      M950 H0 C"!out0" T0 ; create bed heater output on !out0 and map it to sensor 0
      M307 H0 B0 S1.00 ; disable 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"temp2" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp2
      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

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

      ; 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

      ; Custom settings are not defined

      ; Miscellaneous
      M575 P1 S1 B57600 ; enable support for PanelDue
      M501 ; load saved parameters from non-volatile memory
      T0 ; select first tool

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Rushmere3Dundefined
        Rushmere3D
        last edited by

        Being new to RepRap firmware myself I may be wrong but I wonder why you have a fan connected to the heater connector OUT3?

        Also I believe the PanelDue use the IO_0 by default so maybe move the endstop to a different IO.

        Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D

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

          @mogfrog said in Stepper motors and endstops not appearing in dashboard:

          I am attempting to connect stepper motors and endstops to a duet 3 board, but nothing turns up in the dashboard.

          Can you be more descriptive on what you mean? It sounds like you have the motors moving, so they are connected.

          What are you expecting to see in the dashboard? What dashboard exactly?

          Is this a cartesian machine?

          Perhaps this commissioning guide would be helpful to you.

          https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

          Z-Bot CoreXY Build | Thingiverse Profile

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

            Which firmware and Duet Web Control versions 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
            • mogfrogundefined
              mogfrog
              last edited by

              Hi, Thank you all for the responses! I have checked all the above over the past few days and it turned out it hadn't updated and upgraded the firmware files. I started again and followed the following link to the letter and everything is working fine!
              https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3

              Thanks again,

              Mogs

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