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

    PanelDue and Motors will not function properly with Duet Wifi

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    11
    80
    3.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.
    • infiniteloopundefined
      infiniteloop @firex726
      last edited by

      @firex726 That makes sense, if you want to have the origin of the X/Y coordinate system to be front/left.

      – Just to be clear: at this point in space and time, your end stops and your min./max. settings are perfect. Don’t touch these lines again. –

      Now, the question is how to change the direction of a single axis on a coreXY: honestly, I don’t know. With my cartesian, it’s simple, but here, either you know what to do, or one of the coreXY experts has to chime in.

      Last, you will likely have to adjust your homeXY moves - possibly to a negative Y value.

      firex726undefined 1 Reply Last reply Reply Quote 0
      • firex726undefined
        firex726 @infiniteloop
        last edited by firex726

        @infiniteloop said in PanelDue and Motors will not function properly with Duet Wifi:

        Last, you will likely have to adjust your homeXY moves - possibly to a negative Y value.

        Tried that too... Sadly the issue is just when it's home. If I just move it around manually it'll be OK.

        The motors and endstops seem to be OK based off the linked articles; it's just logically it think's it's mirrored once it hits home.


        I think it was noted earlier that the firmware is expecting a Right hand build, but I have a Left hand one, so one axis will be flipped.

        infiniteloopundefined 1 Reply Last reply Reply Quote 0
        • infiniteloopundefined
          infiniteloop @firex726
          last edited by

          @firex726

          I think it was noted earlier that the firmware is expecting a Right hand build, but I have a Left hand one, so one axis will be flipped.

          I noticed that. What I do not understand is this:

          logically it think's it's mirrored once it hits home.

          You mean that before homing, positive Y values move the head to the back of the printer?

          firex726undefined 1 Reply Last reply Reply Quote 0
          • firex726undefined
            firex726 @infiniteloop
            last edited by

            @infiniteloop said in PanelDue and Motors will not function properly with Duet Wifi:

            You mean that before homing, positive Y values move the head to the back of the printer?

            Sadly no... Whichever is mirrored will move in the opposite direction. But due to the design of the mount it's easier to deal with on the Y.

            I think I may just rebuild it to how the firmware thinks it's designed. I had assumed there would just be a simple setting I could flip to mirror whatever axis I want.

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

              Alright, let's take one more shot at this.

              Please post your current config.g and homing files.

              Also please confirm where your Y endstop is located. Your photo shows X but not Y. From previous descriptions it sounds like it's located at the front as labeled on your last photo?

              Z-Bot CoreXY Build | Thingiverse Profile

              firex726undefined 1 Reply Last reply Reply Quote 0
              • Danalundefined
                Danal @firex726
                last edited by

                @firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

                there would just be a simple setting I could flip to mirror whatever axis I want

                There are such settings. Any function of this whole setup can be flipped with a single change to config.g.

                The issue is: Endstops at which end of the machine vs. travel direction vs. homing with + or - numbers in the homing files. They all have to match each other. And the VERY first thing that has to work is CoreXY movement.

                Work through ONE of these at a time, and it can all be figured out.

                Since we can't see your printer, nor exact results of various commands, it is very difficult to remote support (btw, I'm just a customer) unless we get so very meticulous in our terminology and photos and etc that everyone gets impatient... and then there is an ever so slight miscommunication and the whole 9 way (3 axis, 3 things to get aligned with each other) thing becomes confusing again.

                Which is a really long winded way of saying: Work slowly, first movement (NO HOME), then endstops (still no home), then home to endstops and you will actually be able to figure this out faster on your own than all the interaction on the forum here.

                We will all still try to help (I've been in workshops all day, so I didn't post much earlier today)... at the same time, the "do not attempt the next thing until the first thing works" approach can iron this out in minutes.

                1 Reply Last reply Reply Quote 1
                • firex726undefined
                  firex726 @Phaedrux
                  last edited by

                  @Phaedrux said in PanelDue and Motors will not function properly with Duet Wifi:

                  Alright, let's take one more shot at this.

                  Please post your current config.g and homing files.

                  Also please confirm where your Y endstop is located. Your photo shows X but not Y. From previous descriptions it sounds like it's located at the front as labeled on your last photo?

                  Hi there,

                  Here ya go... I figured I'd start with fresh config files, and a new photo for us to base things on. The labels are for where I intend the machine to think each set of coordinates is at.

                  homez.g
                  homey.g
                  homex.g
                  homeall.g
                  config.g

                  20200212_213601_HDR2.jpg

                  1 Reply Last reply Reply Quote 0
                  • Danalundefined
                    Danal
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator
                      last edited by Phaedrux

                      Ok that photo looks good. Looks like the Y endstop is at the front now for Y min.

                      Just noticed your drive mappings are pretty... non-standard

                      M584 X3 Y4 Z2 E1 ; set drive mapping

                      Don't think it really matters here, but wondering if there's rhyme to the reason? Are we dealing with a blown driver or something?

                      Typically they'd be connected like so:
                      M584 X0 Y1 Z2:3 E4:5:6 ; Driver 0 controls the X motor, 1 controls Y, 2 and 3 control Z motors, 4 5 and 6 control E motors

                      Axis limits and endstops look correct.

                      ; Axis Limits
                      M208 X0 Y0 Z0 S1                               ; set axis minima
                      M208 X280 Y280 Z280 S0                         ; set axis maxima
                      
                      ; Endstops
                      M574 X1 S1 P"xstop"                            ; configure active-high endstop for low end on X via pin xstop
                      M574 Y1 S1 P"ystop"                            ; configure active-high endstop for low end on Y via pin ystop
                      M574 Z1 S1 P"zstop"                            ; configure active-high endstop for low end on Z via pin zstop
                      

                      Your homing moves look correct.

                      ; homeall.g
                      G91                    ; relative positioning
                      G1 H2 Z5 F600          ; lift Z relative to current position
                      G1 H1 X-285 Y-285 F600 ; move quickly to X or Y endstop and stop there (first pass)
                      G1 H1 X-285            ; home X axis
                      G1 H1 Y-285            ; home Y axis
                      G1 X5 Y5 F600          ; go back a few mm
                      G1 H1 X-285 F180       ; move slowly to X axis endstop once more (second pass)
                      G1 H1 Y-285            ; then move slowly to Y axis endstop
                      G1 H1 Z-285 F180       ; move Z down stopping at the endstop
                      G90                    ; absolute positioning
                      G92 Z0                 ; set Z position to axis minimum (you may want to adjust this)
                      

                      The next thing to nail down is the direction of rotation for the X/Y motors.

                      ; Drives
                      M569 P3 S1                                     ; physical drive 3 goes forwards
                      M569 P4 S1                                     ; physical drive 4 goes forwards
                      M569 P2 S0                                     ; physical drive 2 goes backwards
                      M569 P1 S1                                     ; physical drive 1 goes forwards
                      

                      Now in your setup P3 and P4 would be X and Y. This is where we'd do the G91 G1 H2 X10 and G91 G1 H2 Y10 moves and go from there.

                      https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement

                      The testing begins with the assumption that we'd be using M569 P3 S0 and M569 P4 S0 so change those to S0 and do the movement test.

                      Z-Bot CoreXY Build | Thingiverse Profile

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

                        This would also be a good time to test the endstops before even testing homing just to ensure they are configured corrected. If you trip them manually do they show as triggered in the machine status view?

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • Danalundefined
                          Danal
                          last edited by

                          Curious where the X endstop is, physically?

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

                            I believe it's on the printhead on the HEVO. You can see the Red green black wires for the optical endstop running to it. The flag is on the left X gantry block.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            1 Reply Last reply Reply Quote 1
                            • firex726undefined
                              firex726
                              last edited by firex726

                              Hi All,

                              Carriage is in the center, normally 140, 140...

                              G91 G1 H2 X10

                              Moves diagonal towards 0, 280.

                              G91 G1 H2 Y10

                              Moves diagonal towards 0, 0.


                              M569 P3 S0
                              M569 P4 S0
                              G91 G1 H2 X10

                              Moves diagonal towards 280, 0.

                              G91 G1 H2 X10

                              Moves diagonal towards 280, 280.


                              If you trip them manually do they show as triggered in the machine status view?

                              Correct, which is also why the homing speed is so slow, to give my hand time.


                              Just noticed your drive mappings are pretty... non-standard

                              Yes, earlier when having issues with only one motor moving it ended up being the diver was blown.

                              A Former User? Phaedruxundefined 2 Replies Last reply Reply Quote 0
                              • A Former User?
                                A Former User @firex726
                                last edited by

                                @firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

                                is also why the homing speed is so slow, to give my hand time.

                                you can test the switches without moving the motors, just press and hold a switch while you run M119 release switch and run M119again to confirm both states. repeat for each axis

                                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                • jay_s_ukundefined
                                  jay_s_uk @A Former User
                                  last edited by

                                  @firex726 Or use the machine specific settings page in DWC to watch the endstops while triggering them, rather than running M119

                                  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
                                  • Danalundefined
                                    Danal
                                    last edited by

                                    This post is deleted!
                                    droftartsundefined 1 Reply Last reply Reply Quote 0
                                    • droftartsundefined
                                      droftarts administrators @Danal
                                      last edited by

                                      This post is deleted!
                                      Danalundefined 1 Reply Last reply Reply Quote 0
                                      • Danalundefined
                                        Danal @droftarts
                                        last edited by

                                        This post is deleted!
                                        droftartsundefined 1 Reply Last reply Reply Quote 0
                                        • droftartsundefined
                                          droftarts administrators @Danal
                                          last edited by droftarts

                                          Edit: Posts deleted to avoid confusion! But leaving this bit because of note about documentation.

                                          He's basically doing this: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement
                                          Though document needs updating to change S2 to H2 moves.

                                          Ian

                                          1 Reply Last reply Reply Quote 0
                                          • Danalundefined
                                            Danal
                                            last edited by Danal

                                            YIKES!!!

                                            Working from memory, I thought the H2 was endstop related ( as a safety net).

                                            I've deleted my above post... thanks for catching that.

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