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

    Your Duet rejected the HTTP request: page not found

    Scheduled Pinned Locked Moved
    Firmware installation
    6
    178
    20.4k
    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.
    • sleeplessundefined
      sleepless
      last edited by

      I think my steps are wrong. When i am homed on the x it is 230 but when i move the x with the jog 100 or so it zeros out the x and im only at the center of the bed, its the same for the y

      1 Reply Last reply Reply Quote 0
      • sleeplessundefined
        sleepless
        last edited by

        // default settings

        #define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,800,723.38} // default steps per unit for RoBo 3D R1

        I used the above when creating the config in the reprap website. I believe i chose 32steps

        ; Drives
        M569 P0 S0 ; Drive 0 goes forwards
        M569 P1 S1 ; Drive 1 goes forwards
        M569 P2 S0 ; Drive 2 goes forwards
        M569 P3 S0 ; Drive 3 goes forwards
        M350 X32 Y32 Z32 I0 ; Configure microstepping without interpolation
        M350 E16 I1 ; Configure microstepping with interpolation
        M92 X80 Y80 Z800 E723.38 ; Set steps per mm
        M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
        M203 X30000 Y30000 Z300 E1500 ; Set maximum speeds (mm/min)
        M201 X500 Y250 Z250 E250 ; Set accelerations (mm/s^2)
        M906 X1000 Y1000 Z1000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
        M84 S30 ; Set idle timeout

        1 Reply Last reply Reply Quote 0
        • sleeplessundefined
          sleepless
          last edited by

          ok i doubled my e steps and now it looks appropriate. I will go ahead and run the test and calibration again now

          1 Reply Last reply Reply Quote 0
          • sleeplessundefined
            sleepless
            last edited by

            when i try to configure and claibrate the z probe. I center the x and y after homing them.then lower the z until it grips paper and send the g92 z0 command. zeros out the z.
            then i raise the nozzle by 5 and run g30 s-1 and the nozzle is too close to the bed. the values are still negative.
            What am I doing wrong here. I cant seem to get it to probe and leave the nozzle at the correct height for it to grip the paper

            1 Reply Last reply Reply Quote 0
            • sleeplessundefined
              sleepless
              last edited by

              tried a test print
              and got Error: Z probe already triggered at start of probing move
              Error: G29: No valid grid defined for bed probing

              1 Reply Last reply Reply Quote 0
              • sleeplessundefined
                sleepless
                last edited by

                G28 ; home all axes
                G29 ; probe the bed
                G1 Z5 F5000 ; lift nozzle
                M109 S[extruder0_temperature] ; set the extruder temp and wait
                G1 X0 Y0 ; move to begin wipe
                G1 X20 Z0 F4800 ; wipe here is my beiginingg script for S3D

                1 Reply Last reply Reply Quote 0
                • sleeplessundefined
                  sleepless
                  last edited by

                  do i need to change g29 to m557 in my simplify 3d scripts for auto leveling? or rather to define the mesh grid?

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

                    The M557 command to define your grid area may have unreachable areas. This gets complicated because you technically don't have a z probe. So you cant really probe the bed. I would just use g28 to home the printer until you get an actual probe.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • sleeplessundefined
                      sleepless
                      last edited by

                      thanks for the advise. after reading this forum i was under the impression I could keep using the original auto level style of the machine. https://forum.duet3d.com/topic/4737/zprobe-robo3d-r1

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

                        Yes it could auto level the x axis, but that's not the same as probing the bed.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        sleeplessundefined 1 Reply Last reply Reply Quote 0
                        • sleeplessundefined
                          sleepless @Phaedrux
                          last edited by

                          @phaedrux hmmm i am confused would you mind clarifying the difference for me. Sorry and thank you

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

                            A probe is normally attached to the print head and is movable to all areas of the bed so it can find the height of the bed across its whole surface. This can be used to get an idea of how the bed lays in relation to the print head.

                            What you have is two end stops in line with the x axis. This lets you adjust the tilt of the x axis to match the bed. But this is just a straight line between the two z motors. This lets you keep the z axis level on both sides, but that's about it.

                            Does that make sense?

                            Z-Bot CoreXY Build | Thingiverse Profile

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

                              @sleepless said in Your Duet rejected the HTTP request: page not found:

                              M557 X15:215 Y15:239 S20 I was curioius if the S20 in this code from the Zprobe area in the config.g file was the number of probing points? Also how do i increase my homing speed?

                              S20 is the spacing (in mm) between probing points.

                              Homing speeds are set by the F parameter in the G1 S1 commands in the homing files; except that if you home Z using a Z probe, then you will use a G30 command to home Z and the speed is the same as for all Z probing moves, as defined by the F parameter in the M558 command.

                              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

                              sleeplessundefined 2 Replies Last reply Reply Quote 0
                              • sleeplessundefined
                                sleepless
                                last edited by

                                But they both take multiple points from the bed to adjust for any misalignment so I guess I can see the difference in the way the do their calibrating based off those points, but in the end both styles (probe or microswitch) should go through the autolevel procedure. It seems you are saying the robo cant do this with the microswitch?

                                1 Reply Last reply Reply Quote 0
                                • sleeplessundefined
                                  sleepless
                                  last edited by

                                  https://www.youtube.com/watch?v=eFywzPM9lfA here is a link to the robo3d autolevel for reference

                                  1 Reply Last reply Reply Quote 0
                                  • sleeplessundefined
                                    sleepless @dc42
                                    last edited by

                                    @dc42 thank you.

                                    1 Reply Last reply Reply Quote 0
                                    • sleeplessundefined
                                      sleepless @dc42
                                      last edited by

                                      @dc42 would you mind if you have a moment looking at the config.g and bed.g file i uploaded and let me know why my I am getting a error code for autolevel when i try to print I also have a fan issue but will get to that later. I want to finish with autolevel .

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

                                        @sleepless said in Your Duet rejected the HTTP request: page not found:

                                        @dc42 would you mind if you have a moment looking at the config.g and bed.g file i uploaded and let me know why my I am getting a error code for autolevel when i try to print ...

                                        What error message are you getting?

                                        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

                                        sleeplessundefined 1 Reply Last reply Reply Quote 0
                                        • sleeplessundefined
                                          sleepless
                                          last edited by

                                          @sleepless said in Your Duet rejected the HTTP request: page not found:

                                          tried a test print
                                          and got Error: Z probe already triggered at start of probing move
                                          Error: G29: No valid grid defined for bed probing

                                          1 Reply Last reply Reply Quote 0
                                          • sleeplessundefined
                                            sleepless @dc42
                                            last edited by

                                            @dc42 Error: Z probe already triggered at start of probing move
                                            Error: G29: No valid grid defined for bed probing

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