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

    G32 ERROR

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    7
    108
    5.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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Maybe stick to 3.2 instead of 3.1.1

      Z-Bot CoreXY Build | Thingiverse Profile

      moe.adams9093undefined 1 Reply Last reply Reply Quote 0
      • moe.adams9093undefined
        moe.adams9093 @Phaedrux
        last edited by

        @Phaedrux 3.2 for somereason my external driver Number 10 it won't work

        1 Reply Last reply Reply Quote 0
        • moe.adams9093undefined
          moe.adams9093
          last edited by

          So I downgraded to 3.1.1 and Main board is not working now YAT won't see it to enable ethernet via USB and can even erase firmware when i jump the reset pins deg light won't even turn red. Why did that happen

          1 Reply Last reply Reply Quote 0
          • moe.adams9093undefined
            moe.adams9093
            last edited by

            Never mind I figured it out

            fcwiltundefined 1 Reply Last reply Reply Quote 1
            • fcwiltundefined
              fcwilt @moe.adams9093
              last edited by

              @moe-adams9093 said in G32 ERROR:

              Never mind I figured it out

              Well don't leave us in suspense. What did you find?

              Frederick

              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

              1 Reply Last reply Reply Quote 0
              • moe.adams9093undefined
                moe.adams9093
                last edited by

                One of my endstops connection was reversed accidentally and it caused a short so the board automatically shut down power to the CPU thats why it wasn't abel to communicate via USB. All up and running now endstops works fine as well. One single problem im having now is when the bed go back to the min side it won't stop by the IR sensor. Any idea on how I can fix this. Same homeall .g file I posted previously. Thanks again for keeping up.

                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @moe.adams9093
                  last edited by fcwilt

                  @moe-adams9093 said in G32 ERROR:

                  One of my endstops connection was reversed accidentally and it caused a short so the board automatically shut down power to the CPU thats why it wasn't abel to communicate via USB.

                  Oops. I take if you are not using the mating connectors for the Duet which only go on one way?

                  All up and running now endstops works fine as well.

                  Glad to hear it.

                  One single problem im having now is when the bed go back to the min side it won't stop by the IR sensor. Any idea on how I can fix this. Same homeall .g file I posted previously.

                  Questions:

                  • So this file never works or only sometimes works?
                  • Why so much movement in this command G1 H1 Z500 F6000?
                  • Did you mean this to be a relative move G1 X235 Y235 F6000?
                  ;  homeall.g
                  
                  G91                      ; relative positioning
                  G1 H1 Z500 F6000         ; lift Z relative to current position
                  G1 H1 X-465 F8000        ; move quickly to X endstop and stop there (first pass)
                  G1 H1 Y-465 F8000        ; move quickly to Y endstop and stop there (first pass)
                  G1 H2 X5 Y5 F6000        ; go back a few mm
                  G1 H1 X-465 F360         ; move slowly to X axis endstop once more (second pass)
                  G1 H1 Y-465 F360         ; then move slowly to Y axis endstop
                   
                  G1 X235 Y235 F6000       ; Prob at Center 
                  M558 F600 A1 	         ; Dive fast once 
                  G30			 ; probe Z
                  M558 F300 A10            ; Slow second dive with more accuracy
                  G30			 ; probe z again
                  

                  Thanks again for keeping up.

                  Always willing to help when I can.

                  Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                  1 Reply Last reply Reply Quote 0
                  • moe.adams9093undefined
                    moe.adams9093
                    last edited by

                    So when I press homeall
                    These are the steps I wanted to do

                    1. Bed travel to Zmax which is 500 ☑

                    2. BED hit all four endStop at Zmax and stops axis individually ☑

                    3. X&Y travel to the center (235,235) prob at center ❎

                    So now X&Y are not traveling to (235,235) to perform probing sequence.

                    fcwiltundefined 1 Reply Last reply Reply Quote 0
                    • fcwiltundefined
                      fcwilt @moe.adams9093
                      last edited by

                      @moe-adams9093 said in G32 ERROR:

                      So now X&Y are not traveling to (235,235) to perform probing sequence.

                      Questions:

                      • Is there ANY movement at all on the X or Y axis in response to the G1 X235 Y235 F6000 command?
                      • Is there ANY movement at all on the Z axis back towards the bed in response to the first G30 command?

                      If I were trying to solve this I would first:

                      • Comment out all of the commands starting with the G1 X235 Y235 F6000 command.
                      • Perform a home all.
                      • Verify that the X and Y axes homed and ended up at X=0 Y=0.

                      So if you can provide those two answers and perhaps perform that test?

                      Thanks.

                      Frederick

                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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

                        I have increased the max length of the pin name string in the forthcoming 3.2.1 release.

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