Slow Z movement returns!
Posted: Thu Dec 05, 2013 11:56 am
OK.... I reported a few months ago that when running a print over USB from Repteier that once in a while the axes would home at normal speeds and then super slooooooooowly move down as the first move of the print. Like multiple minutes to get down to Z0 slow. I had some scatter brained observations based on random chance and hurried troubleshooting, but eventually found out that it didn't really matter which slicer I used or anything else like that, it just randomly would happen. (happens printing from SD too, if you're curious) Rebooting the printer and clicking "run job" again or printing the SD file on the LCD almost always works the second time.
The consensus from that thread was that I probably needed ferrite cores on my LCD ribbon cables to sort out the EMI sorts of flukes and anomalies that are possible in unshielded ribbon cables. I believe the cores have been prescribed for the "it just stopped printing" phantom as well. Anyway, I haven't done that yet and have just come to accept that it happens once in a while, and it's probably a very specific "me only" kind of thing like cable routing.
The plot thickens.
A good friend of mine bought a Rostock kit last week and put it together by himself over the holiday weekend. I showed up to help him for the last few steps, and his printer did the exact same thing. We had a dead LCD which John helped us with in his own personal time over the holiday weekend (extra props to John!), so we had the LCD cables completely out of the machine when we were observing the "slowness glitch".
His machine is also considerably different than mine. He has the newest Rambo, one version newer firmware, used his own laptop, had a virgin install of everything from the download.seemecnc.com website that day, and is running Windows 7-32 instead of 8-64 like me... We also live in different parts of town on different utilities... I can't think of something common between our two scenarios except the printer itself and the software we're using.
Any idea what the common denominator might be? I'm stumped because it really doesn't seem to be an environment specific thing, you know?
The consensus from that thread was that I probably needed ferrite cores on my LCD ribbon cables to sort out the EMI sorts of flukes and anomalies that are possible in unshielded ribbon cables. I believe the cores have been prescribed for the "it just stopped printing" phantom as well. Anyway, I haven't done that yet and have just come to accept that it happens once in a while, and it's probably a very specific "me only" kind of thing like cable routing.
The plot thickens.
A good friend of mine bought a Rostock kit last week and put it together by himself over the holiday weekend. I showed up to help him for the last few steps, and his printer did the exact same thing. We had a dead LCD which John helped us with in his own personal time over the holiday weekend (extra props to John!), so we had the LCD cables completely out of the machine when we were observing the "slowness glitch".
His machine is also considerably different than mine. He has the newest Rambo, one version newer firmware, used his own laptop, had a virgin install of everything from the download.seemecnc.com website that day, and is running Windows 7-32 instead of 8-64 like me... We also live in different parts of town on different utilities... I can't think of something common between our two scenarios except the printer itself and the software we're using.
Any idea what the common denominator might be? I'm stumped because it really doesn't seem to be an environment specific thing, you know?
