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

Ajax error after bed probe

Scheduled Pinned Locked Moved
General Discussion
7
13
1.7k
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
    Sniffle
    last edited by 29 Nov 2016, 04:06

    the "Auto Bed Correction" enacts your Bed.g file so yes it does whatever you set it to.

    1 Reply Last reply Reply Quote 0
    • undefined
      StephenRC
      last edited by 29 Nov 2016, 04:42

      @bendy:

      Note that this issue also occurs after using the "Auto Bed Correction" button from the Machine control page (which I am guessing just does some flavour of a G32 in the background)

      Check your bed.g file, there may be a bad gcode in there.

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 29 Nov 2016, 07:01

        What we really need to see is the json message that provoked the error. Can you provide a Wireshark pcap file?

        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
          bendy
          last edited by 29 Nov 2016, 23:01

          Here are the contents of my bed.g -

          [[language]]
          ; bed.g
          ; called to perform automatic bed compensation via G32
          ;
          ; generated by RepRapFirmware Configuration Tool on Sun Nov 27 2016 09:59:20 GMT+1100 (AEDT)
          ; Clear any bed transform
          M561
          ; Probe the bed at 4 points
          G30 P0 X75 Y110 H0 Z-99999
          G30 P1 X345 Y110 H0 Z-99999
          G30 P2 X345 Y355 H0 Z-99999
          G30 P3 X75 Y355 H0 Z-99999 S

          I will get a packet trace done later on and post it up.

          1 Reply Last reply Reply Quote 0
          • undefined
            bendy
            last edited by 30 Nov 2016, 01:08

            Quick update - I have manually executed the commands in bed.g and the first 4 commands work fine, it is only when the last line -

            [[language]]
            G30 P3 X75 Y355 H0 Z-99999 S
            ```Is executed that the system crashes. The probe works as expected but I am guessing when the calculation of the Z plane is done it is causing an issue. I have tried it with both S and S4 with the same result. Packet trace still to come.
            1 Reply Last reply Reply Quote 0
            • undefined
              Jackal
              last edited by 30 Nov 2016, 01:20

              Your probe points have to been in a clockwise order, starting nearest to 0,0

              1 Reply Last reply Reply Quote 0
              • undefined
                bendy
                last edited by 30 Nov 2016, 02:02

                OK, Another update - the Ajax error is masking some other error here related to z plane calculation by the looks of it - If I run the probe for 3 points it works fine, it only fails if I do it for 4 points (am running a cartesian setup so 4 points should be supported?)

                1 Reply Last reply Reply Quote 0
                • undefined
                  Qdeathstar
                  last edited by 30 Nov 2016, 04:25

                  @Jackal:

                  Your probe points have to been in a clockwise order, starting nearest to 0,0

                  Is that true? DC42's calibration calculator suggestions points starting at the z-tower, then moving clockwise moving towards 0,0 with the last probe being 0,0…. should i rearrange the probes?

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    lignumaqua
                    last edited by 30 Nov 2016, 06:11

                    Your sequence is anti-clockwise instead of clockwise, I suggest trying:

                    G30 P0 X75 Y110 Z-99999 ; Bottom Left
                    G30 P1 X75 Y355 Z-99999 ; Top Left
                    G30 P2 X345 Y355 Z-99999 ; Top Right
                    G30 P3 X345 Y110 Z-99999 ; Bottom Right
                    G30 P4 X210 Y232 Z-99999 S0 ; centre, and calibrate compensation
                    1 Reply Last reply Reply Quote 0
                    • undefined
                      Jackal
                      last edited by 30 Nov 2016, 07:06

                      @Qdeathstar:

                      @Jackal:

                      Your probe points have to been in a clockwise order, starting nearest to 0,0

                      Is that true? DC42's calibration calculator suggestions points starting at the z-tower, then moving clockwise moving towards 0,0 with the last probe being 0,0…. should i rearrange the probes?

                      The calibration calculator is for Deltas. For Cartesian machines, you need them in clockwise order.
                      I stumbled upon a similar discussion before, you can find them by searching 'clockwise' in the forum.

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        bendy
                        last edited by 1 Dec 2016, 22:12

                        OK, looks like going clockwise fixed it

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