OpenSlider - Motorized Camera Slider

by RJ_Make Jun 1, 2017
Download All Files

Thing Apps Enabled

Please Login to Comment

Hello super project, I have a question, it may be that an STL file is missing. Where is the skin plate of the sliders. What the ball bearings are mounted on. Thanks in advance.

Are you referring to the Gantry (What the 'X-Mount (Yellow Mount) is connected to)? If so, that is a purchased item from Open Builds https://openbuildspartstore.com/v-slot-gantry-set-20mm/

Awesome elaboration on this project! Wish I found it sooner, I got most of the way through adapting Tom's code to work with this screen but your's was fully plug'n'play, thanks!

Hoping you might be able to give some guidance on further code changes, my carriage ends up moving too fast for the time values entered, plus my rail is 1500mm so it ends up even more inaccurate. I changed STEPSMM to 160 (I think this is right for a 1.8 degree step angle for my motor?), this seemed to get it a bit closer to the mark but still too fast. Any pointers on what I need to change to get this accurate?

Are you using my setup (with reversing end stops)? I don't think the rail length matters with Toms code as the calculation are based on travel speed. What do you have your driver setup for?

Steps per MM (STEPSMM) 160 = 1/16 Micro Steps and 320 = 1/32 Micro Steps

Yep, using your code as-is with working endstops. I assume it would have to have some distance value to calculate the runtime from the travel speed otherwise it would be meaningless right?

I have the driver set to 1/32 by running 5v to all 3 jumpers, so it should be 320 I guess, but it seems to run even faster with that value.

This line looks relevant but I don't understand what it is doing:
runtime = 1000 oldPosition oldPosition / 4;

So it looks like you have a few diff rail lengths you use, do you find the runtime anywhere near accurate on any of those lengths?

My understanding, (which could very well be incorrect) is the code Tom wrote is just based on steps per mm/s. I'm not sure it would resolve in an actual distance traveled. I would think the code would have to know all the pulley diameters, etc involved.

I really haven't payed much attention to the distance traveled. I just set the speed for the project I'm working on and let it run a few passes.

Perhaps I should look at this in more detail.