I have run in to a strange issue where the X and Y axes don’t move to the specified coordinate beyond a certain range.

The steps/unit are calibrated, when i tell an axis to move to position 100mm (using G0 or G1 command manually), it moves to position 100mm, this goes for both X and Y axis…but it seems like it hits a software-stop when i tell it to move beyond 225mm on both of them, which is weird since build plate is 230mmx230mm, and nozzle wipe-pad and Z-offset calibration are located at Y position 240mm-245mm.

The stepper just stops at 225mm even if i tell it to move beyond this point, and if i tell it to move back to 0mm, it positions itself correctly at the starting point. It doesn’t sound like any skipping on the belt or the stepper itself is happening, it’s completely silent but just stops. I can easily move the bed and print-head beyond this point by hand, and i can’t feel any noticeable increased resistance in the movement.

The odd thing is, that this worked just fine a week ago, i haven’t changed anything on the config of the printer. It’s an anycubic Kobra 2 bedslinger.

EDIT: i can trick it to move beyond the 225mm point by changing the steps/unit, but that messes with the general print size accuracy.

EDIT 2: It seems a FW update enabled SW end-stops, a simple “M211 S0” command from the terminal disabled them again and now it works just fine.

  • DreadPotato@sopuli.xyzOPEnglish
    1·
    11 months ago

    It’s running a version of marlin 2.xx, but it’s a build made by anycubic themselves, so I’m not sure about the specific version it’s based on or the detailed config.

    • Footnote2669@lemmy.zipEnglish
      2·
      11 months ago

      I was hoping you’re on Klipper 😅 not sure what to do honestly, but idk if it’s worth troubling yourself with 5mm haha

      • DreadPotato@sopuli.xyzOPEnglish
        4·
        11 months ago

        Turns out SW end-stops got enabled by a FW update i did. I just disabled them, and now I can move beyond the bed size.

      • DreadPotato@sopuli.xyzOPEnglish
        2·
        11 months ago

        Its an issue since my custom g-code to wipe the nozzle before a print (which has worked just fine BTW) now tries to wipe the nozzle on the bed area, but the Z-setpoint is 1mm below bed surface (the Z-position of the wiping-pad at the back), so it kind of destroys both nozzle and bed.