this post was submitted on 06 Jan 2024
19 points (95.2% liked)

3DPrinting

15250 readers
30 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] tagginator@utter.online -1 points 8 months ago

New Lemmy Post: Printer not moving to expected coordinate (https://lemmy.dbzer0.com/post/11786045)
Tagging: #3dprinting

(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)

I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md