Jury’s still out, but I think I’ve got it licked. I’ve added external cooling, dropped the effector fan so it’s blowing on the SS heat break…and the thing that I think really did it: changed the Prime/Suck in KISSlicer from 1.25 to .25
I really want to see this to completion, but I think I’ll let it finish up while I go to bed.
Makezine robot, scaled 2.0, 0.1 layer width, 10% infill, 180 degrees…
Nice work, finally work out your rocking issue?
There’s still a Little left, it was a combination of slip in the mount, from the mount to the plate, a couple of the U-Joints being loose, and lubricating everything with some lithium grease.
The way G+ summarizes the video and animates it, makes it look like the object being printed was shifting back and forth. I had to watch the video to confirm that wasn’t happening. I think it was due to the camera motion when recorded.
I agree, @Freeman_Pascal I thought the same thing.
It’s because @Mike_Miller doesn’t have camera stabilization turned off in his phone software (or whatever he’s using to record) – what you’re seeing is the result of the software detecting frame movement and trying to compensate.
Ya, if you watch the top right quadrant background, you can see the background shift slightly also. And the shift is non linear - almost like a scanline tear. Video artifact exaggerated by GIF reduction, imo.
@ThantiK I think it’s a google thing. There’s no stabilization turned on in my Galaxy S4, and the original video doesn’t show that artifacting. I think they throw that in on the GIF preview as a ‘feature’.
Image stabilization analysis in the GIF reduction would significantly reduce the size of the GIF data.
@Mike_Miller you’re right, looks to be on Googles side (the image stabilization bit)
