Home › Forums › Technical Support › X axis bugs
This topic contains 8 replies, has 2 voices, and was last updated by
Vyacheslav 1 day, 22 hours ago.
-
AuthorPosts
-
15/05/2016 at 6:38 pm #29841
When printing some things, there are accidental shifts along X axis, sometimes up to 1 mm. It happens not every time and I can’t see any correlations.
It is not problem of model - it happens on downloaded things that are printed by other people. And it seems no PEI shifts - I’m using wedges of Dr.Woo and PEI stays in place.
I’ve noticed that before shift happens head does some strange trick - it stops and then swings (as it wants to activate 0.8 nozzle), then swings back.
Attachments:
You must be logged in to view attached files.15/05/2016 at 11:11 pm #29848@aim-4 You may be looking at a combination of issues. The pausing and swapping nozzles may be due to a poor connection between the head and head carrier.
The offset looks like a PEI shift, but it may also be due to an issue with the nozzle offset calibration. Please run that calibration again and try to replicate the issue.
I operate two Betas and one Production Robox.
See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben16/05/2016 at 5:25 am #29854@bhudson You mean calibration of nozzle height? This one I’ve done.
I don’t think it’s PEI shift: I was observing specially while printing and registering PEI position - I would have noticed moves for so big value (1 mm).
Can I try to fix first variant - poor connection - by removing and installing the head?
16/05/2016 at 2:30 pm #29860@aim-4 There are three calibrations - nozzle opening, nozzle height, and nozzle alignment. You need to do the third one, nozzle alignment, to make sure your current values are valid.
I operate two Betas and one Production Robox.
See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben23/05/2016 at 3:26 pm #30071It seems that my Robox “hates” some things… Or it is broken… ):
I’ve specially downloaded some things from Thingiverse made by many others. Some of them always got X shifts when I print its. Shift does not depends of material, Automaker version, thing’s orientation on bed etc.
Shift is always to right. Before it happens, head makes “double swing” and prints layer with bad perimeters (does not glued together).
Some other things have no troubles…
Attachments:
You must be logged in to view attached files.23/05/2016 at 3:47 pm #30075@aim-4 Have you opened a support ticket?
If the shifting is consistent in certain files, you may be looking at a slicer error due to a bad STL file.
Try printing the same file 3-4 times and see if the problem always shows up at the same place every time. If it does, you may be looking at a bad file. If not, you may be looking at a hardware issue.
I operate two Betas and one Production Robox.
See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben23/05/2016 at 4:42 pm #30076@bhudson No, I have not opened ticket yet, just because I don’t know how to separate bad STL from print error. It’s strange, but bug happens very rare on things designed by myself, but often on downloaded things.
I have printed same files many times - it most cases problem repeats.
Maybe someone can print one of these things to compare with my prints?
http://www.thingiverse.com/thing:147050
24/05/2016 at 2:48 am #30085@aim-4 I was reviewing your original post and noticed you had the same issue with the Robox Robot V1. That is a known good file, so the issue is hardware. You are seeing one of a couple of possibilities.
- The X belt isn’t tight enough.
- The nozzle is hitting the part hard enough to throw off the X position, which I doubt.
- You have a loose connection to the X motor. This can be a bad crimp, a connector coming out, or a broken connector contact. This issue will eventually fry your mainboard.
Might be worth opening a ticket to get more directed troubleshooting.
I operate two Betas and one Production Robox.
See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben25/05/2016 at 5:56 pm #30111@bhudson Thank you. I have opened a ticket.
-
AuthorPosts
You must be logged in to reply to this topic.




