Timelapse Trigger Mounted on Prusa Mk3s X-axis Idler Side

Description

WARNING: Z AXIS CALIBRATION ISSUE - because this is on the top of the right hand x-axis idler, if your Prusa goes all the way to the top of the Z axis (for calibration) then it hits the top before the left side. This might be fixed by adding a spacer (6mm from idler, or 3mm over the trapezoidal nut on the screw). The better way is probably to redesign to mount underneath idler. Note: if you aren't running Z calibrations each print, then you might not experience this. I only encountered it when trying some Ending print script that raised it up. Background: Timelapses with DLSR I wanted to do time lapses but my RPi2 was struggling and so stuttering and taking forever. My first design worked but it was not pretty. This is the new and improved version. Essentially, you can take the USB out of the my Sony alpha series (and many other cameras with wired shutter releases) and you can trigger the shutter by crossing the right wires. On the multimeter, it reads 3v for the signal. For this you need a momentary switch. I had an old one from an arduino project. (The only other cheap momentary switch I could find locally was in a doorbell.) The mount is designed to go around both vertical rods and to screw into the trapazoidal nut on the right hand threaded rod. The nut stays in place, and you have to go up in size for the M3 type bolt. The button carriage is designed to accept two screws from the mount, though only one is needed to set it in place. It was designed to slide back and forth to allow greater flexibility in locating the momentary button - i.e. how far it poked out. For Gcode, this is a Prusa, so on mine, I moved the Extruder all the way to the left to zero out the X-Axis, then went to Settings > Move Axis > Xaxis and moved it all the way over to where the Extruder contacted the momentary switch. On mine that was x240. The button pressed all the way in at x244. Thus the code between layers moved it first to x240 y200, then to x244. Then paused for 1/2 second for the camera to take a picture, then resumed. It worked! It was not perfect. There's something in the Gcode that is causing the travel to be slower in travel from the print to the button... but not on the return to the print. Also, I'm printing with ABS at the moment, and it doesn't like this movement away and back and had nearly failed every time during the print.

Statistics

Category

Tags