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

    HOMING ERROR

    Scheduled Pinned Locked Moved Solved
    General Discussion
    2
    5
    236
    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.
    • GBusy24undefined
      GBusy24
      last edited by GBusy24

      I'm commissioning a CR-10S S4 that I recently dropped a Duet Wifi V2 into. I get the following error when homing. "Error: in file macro line 9 column 8: G1: expected number after 'Y'". I searched thru all the system folders along with my config.g, homeall, homex and homey files but can't seem to find how to fix it. Hopefully someone can help me out. Thanks

      No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

        @GBusy24 said in HOMING ERROR:

        I get the following error when homing. "Error: in file macro line 9 column 8: G1: expected number after 'Y'". I searched thru all the system folders along with my config.g, homeall, homex and homey files but can't seem to find how to fix it.

        Don’t know how many macros you heed, especially those with 9 or more lines and a G1 Gcode in its line #9…

        Well, you have two options, one of them is the method described above: look for a G1 in line 9, then, look if the numeric value from the Y parameter is missing.

        The other method is to apply simple logic: which macros are called on homing? Narrow that down by homing one axis at a time: do you get the error when you home X, Y or Z?

        If you are not sure which macros are called, run the homing macros from the command line, e.g. M98 P"homex.g".

        Now, you should be almost spot-on, apart from the case in which a macro invokes another macro - this might for instance happen in homeall.g …

        Well, reading a macro reveals these M98 calls - so, you have to inspect these macros, too, for a G1 in line 9, missing the numeric value from the Y parameter.

        GBusy24undefined 2 Replies Last reply Reply Quote 1
        • GBusy24undefined
          GBusy24 @infiniteloop
          last edited by

          @infiniteloop Thanks, I will give those methods a try.

          No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

          1 Reply Last reply Reply Quote 0
          • GBusy24undefined
            GBusy24 @infiniteloop
            last edited by

            @infiniteloop Found it. I somehow had an equal sign(=) between Y and a number in my homeall.g.

            No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

              @GBusy24 said in HOMING ERROR:

              Found it.

              Glad you got it!

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined Phaedrux marked this topic as a question
              • Phaedruxundefined Phaedrux has marked this topic as solved
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA