Thank you for this fantastic tutorial. I didn't exactly follow your steps for taking the frames but all the explanation on how to install gphoto are a big help. Instead I used the moonraker-timelapse pluging and customized the provided timelapse.cfg (just added "RUN_SHELL_COMMAND CMD=gphoto2_trigger_snapshot" to _TIMELAPSE_NEW_FRAME macro and "RUN_SHELL_COMMAND CMD=gphoto2_set_config" to _SET_TIMELAPSE_SETUP. Like this I can use the moonraker-timelapse UI to set up the toolhead parking, timelapse mode (hyperlapse or timelapse, retraction...) and I also get a low quality timelapse sample via my PI cam. Hope this can give some ideas :)
That's is such a great idea, I was trying to figure out how to do that but couldn't quite figure it out. Does it matter where in those macros you put the lines?
Hey, that's a brillant idea but are you able to get the files in the proper place for moonraker (I mean in dedicated folers with proper naming convention) so that jpg and timelapses can appear in the mainsail UI?
Have been searching for couple hours now what would be the best way today to add dslr timelapse capability to klipper setup and THIS is exactly what I was thinking. I'm going to try to implement this when I get home. (damn work etc.) If you could share the timelapse.cfg that would be really usefull and speed things along!
sony A6000 doesnt do capture target command. Question is how do i modify that script to tell it to just download the snapshots to a directory on the device running klipper?
Same Problem with my A7M2: This one solves it: sudo gphoto2 --auto-detect --capture-image-and-download --filename=/home/pi/%Y%m%d%H%M%S.jpg Make sure make your camera into remote mode after attaching it via USB and run this macro manually once after connecting the USB cable, it will also keep the settings and not reset them. This Shell Macro: [gcode_shell_command gphoto2_connect_camera] command: sudo gphoto2 --list-config timeout: 10. ; make sure this is long enough to account for focus time verbose: False And This normal Macro: [gcode_macro GPHOTO_CONNECT_CAMERA] gcode: RUN_SHELL_COMMAND CMD=gphoto2_connect_camera
Also working on solution to use infrared light to trigger the sony, which will the have the camera work on its own without transfer time for the pictures. This should speed up the process to have less nozzle oozing in the meantime
Hi! @EB3D Printing, I'm wondering if you can help me. My camera (Sony ILCE-7M2) is somewhat supported but I have an issue where I cannot write to the internal SD. It does however write to my Pi if I use the command gphoto2 --auto-detect --capture-image-and-download I modified the shell command file to include this and if I manually run this command on ssh, the camera successfully captures and stores the image on my pi, if, however, this command is triggered using the shell command, it will take the image but not store it, even though the text in the command is identical. Can you provide any suggestions?
@@EB3DPrinting Thanks for the quick response!! First time interacting in the comments so I really appreciate it. Unfortunately this didn't work, I tried setting the timeout to 100, 1000, 10000, and 20000. None of which were successful. If I run the gphoto2 --auto-detect --capture-image-and-download in my ssh client, the photo appears in my pi root directory within a second. Sadly if this command is run through the mainsail console via command "gphoto_snapshot_test", the camera happily takes the picture but fails to download it to the pi. Super strange. Any other thoughts?
@Kyle Palframan When you say it doesn't write to the internal SD, are you setting that SD card as the capture target? gphoto2 --auto-detect --get-config capturetarget This will display the memory slots available If it displays the Memory card with choice number gphoto2 --auto-detect --set-config capturetarget= Enter the memory card choice number after capturetarget=
@@EB3DPrinting I don't think this camera can write to the internal SD of the camera. It's a problem with Sony cams as far as I can tell. They write to SDRAM and not the internal SD, and this can't be changed. If I run gphoto2 --auto-detect --get-config capturetarget, I get: pi@ender3:~ $ gphoto2 --auto-detect --get-config capturetarget Model Port ---------------------------------------------------------- Sony ILCE-7M2 (Control) usb:001,008 *** Error *** capturetarget not found in configuration tree. *** Error (-1: 'Unspecified error') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list , please run gphoto2 as follows: env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --auto-detect --get-config capturetarget Please make sure there is sufficient quoting around the arguments. It can successfully write to the SD of the Pi, however... for example, if I'm in Putty and I execute : gphoto2 --capture-image-and-download, it captures and successfully downloads to the SD card of the Pi. I can see the file there about 60s after it captures. It's the exact same command that i have it activating in the shell file when the command "gphoto_snapshot_test" is run in the mainsail console..I modified the shell command.cfg file to include the following : #===================================================== # DSLR CAPTURE IMAGE #===================================================== [gcode_shell_command gphoto2_trigger_snapshot] command: gphoto2 --auto-detect --capture-image-and-download timeout: 30000. ; make sure this is long enough to account for focus time verbose: False Now if I use mainsail to execute that shell command, it will successfully capture, it just never actually downloads to the sd of the pi if this command is run through mainsail, but if that same "capture-image-and-download" is run in the ssh, it does download to the sd of the pi, which is all I need it to do. Hope that makes sense?
@EB3DPrinting ahhhhhh ok. Soooooo I just did the setup after watching your video and I want to thank you! Everything is setup and kinda working. I have the same camera as you and am having an issue I hope you can help me with. When it takes a couple of pictures, the screen will say "busy" and will not take another picture unless I unplug the cable and replug it back in. After a couple more pictures it does it again. Any thoughts?
@Chris Woods mine does the same thing. It will not take inputs from the camera body because it is in "use" by the USB. It should, however, take inputs from macros/command line of the Pi or Mainsail. After I have the camera set up for time-lapse, I just close the rear screen and let it run through the printer
@Chris Woods Just close the back screen shut. What you can do is run the test snapshot macro to see if the camera still functions while it is saying its busy
NOTE to anyone watching this, Gcode Shell is now 8, not 9
Thank you for this fantastic tutorial. I didn't exactly follow your steps for taking the frames but all the explanation on how to install gphoto are a big help. Instead I used the moonraker-timelapse pluging and customized the provided timelapse.cfg (just added "RUN_SHELL_COMMAND CMD=gphoto2_trigger_snapshot" to _TIMELAPSE_NEW_FRAME macro and "RUN_SHELL_COMMAND CMD=gphoto2_set_config" to _SET_TIMELAPSE_SETUP. Like this I can use the moonraker-timelapse UI to set up the toolhead parking, timelapse mode (hyperlapse or timelapse, retraction...) and I also get a low quality timelapse sample via my PI cam. Hope this can give some ideas :)
That's is such a great idea, I was trying to figure out how to do that but couldn't quite figure it out. Does it matter where in those macros you put the lines?
Hey, that's a brillant idea but are you able to get the files in the proper place for moonraker (I mean in dedicated folers with proper naming convention) so that jpg and timelapses can appear in the mainsail UI?
trying to do the same with mine but being unfamiliar with the codes couldn't figure it out. can you share your timelapse.cfg file somehow?
Have been searching for couple hours now what would be the best way today to add dslr timelapse capability to klipper setup and THIS is exactly what I was thinking. I'm going to try to implement this when I get home. (damn work etc.) If you could share the timelapse.cfg that would be really usefull and speed things along!
Anyone work this out?
Thank you, bro! found what to do with my old canon 1100d!
WELL DONE! You earned a Like!
Thanks a ton. I got my canon dslr working with mainsail.
Great video. Tks so much. Is it possible to do this on the Creality K1 series?
Thank you so much !!
Qualitiy content👌
Super Like. Fantastic job. Thaks form Spain.
Is this still the best way to do it?
Great video, you do however need a better microphone.
would this work with a Creality Sonic Pad?
THANKS !!
sony A6000 doesnt do capture target command. Question is how do i modify that script to tell it to just download the snapshots to a directory on the device running klipper?
Same Problem with my A7M2:
This one solves it:
sudo gphoto2 --auto-detect --capture-image-and-download --filename=/home/pi/%Y%m%d%H%M%S.jpg
Make sure make your camera into remote mode after attaching it via USB and run this macro manually once after connecting the USB cable, it will also keep the settings and not reset them.
This Shell Macro:
[gcode_shell_command gphoto2_connect_camera]
command: sudo gphoto2 --list-config
timeout: 10. ; make sure this is long enough to account for focus time
verbose: False
And This normal Macro:
[gcode_macro GPHOTO_CONNECT_CAMERA]
gcode:
RUN_SHELL_COMMAND CMD=gphoto2_connect_camera
Also working on solution to use infrared light to trigger the sony, which will the have the camera work on its own without transfer time for the pictures. This should speed up the process to have less nozzle oozing in the meantime
This looks great, is there an easy way to modify the code so that the head does not move?
I answer myself after a few tries, by uncommenting the "snapshotPositionX" part it works wonderfully, thanks a lot!
Hi! @EB3D Printing, I'm wondering if you can help me. My camera (Sony ILCE-7M2) is somewhat supported but I have an issue where I cannot write to the internal SD. It does however write to my Pi if I use the command gphoto2 --auto-detect --capture-image-and-download
I modified the shell command file to include this and if I manually run this command on ssh, the camera successfully captures and stores the image on my pi, if, however, this command is triggered using the shell command, it will take the image but not store it, even though the text in the command is identical.
Can you provide any suggestions?
Try increasing the timeout of the shell command. The time it takes to download the image to the Pi may be longer than the timeout allows
@@EB3DPrinting Thanks for the quick response!! First time interacting in the comments so I really appreciate it. Unfortunately this didn't work, I tried setting the timeout to 100, 1000, 10000, and 20000. None of which were successful. If I run the gphoto2 --auto-detect --capture-image-and-download in my ssh client, the photo appears in my pi root directory within a second. Sadly if this command is run through the mainsail console via command "gphoto_snapshot_test", the camera happily takes the picture but fails to download it to the pi. Super strange. Any other thoughts?
@Kyle Palframan When you say it doesn't write to the internal SD, are you setting that SD card as the capture target?
gphoto2 --auto-detect --get-config capturetarget
This will display the memory slots available
If it displays the Memory card with choice number
gphoto2 --auto-detect --set-config capturetarget=
Enter the memory card choice number after capturetarget=
@@EB3DPrinting I don't think this camera can write to the internal SD of the camera. It's a problem with Sony cams as far as I can tell. They write to SDRAM and not the internal SD, and this can't be changed. If I run gphoto2 --auto-detect --get-config capturetarget, I get:
pi@ender3:~ $ gphoto2 --auto-detect --get-config capturetarget
Model Port
----------------------------------------------------------
Sony ILCE-7M2 (Control) usb:001,008
*** Error ***
capturetarget not found in configuration tree.
*** Error (-1: 'Unspecified error') ***
For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list , please run
gphoto2 as follows:
env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --auto-detect --get-config capturetarget
Please make sure there is sufficient quoting around the arguments.
It can successfully write to the SD of the Pi, however... for example, if I'm in Putty and I execute : gphoto2 --capture-image-and-download, it captures and successfully downloads to the SD card of the Pi. I can see the file there about 60s after it captures. It's the exact same command that i have it activating in the shell file when the command "gphoto_snapshot_test" is run in the mainsail console..I modified the shell command.cfg file to include the following :
#=====================================================
# DSLR CAPTURE IMAGE
#=====================================================
[gcode_shell_command gphoto2_trigger_snapshot]
command: gphoto2 --auto-detect --capture-image-and-download
timeout: 30000. ; make sure this is long enough to account for focus time
verbose: False
Now if I use mainsail to execute that shell command, it will successfully capture, it just never actually downloads to the sd of the pi if this command is run through mainsail, but if that same "capture-image-and-download" is run in the ssh, it does download to the sd of the pi, which is all I need it to do.
Hope that makes sense?
Hi. Are you using your dslr as a web cam as well?
No, I use a logitech c270 for the Webcam. It has something to do with the DSLR not being able to do live view
@EB3DPrinting ahhhhhh ok.
Soooooo I just did the setup after watching your video and I want to thank you! Everything is setup and kinda working. I have the same camera as you and am having an issue I hope you can help me with. When it takes a couple of pictures, the screen will say "busy" and will not take another picture unless I unplug the cable and replug it back in. After a couple more pictures it does it again. Any thoughts?
@Chris Woods mine does the same thing. It will not take inputs from the camera body because it is in "use" by the USB. It should, however, take inputs from macros/command line of the Pi or Mainsail. After I have the camera set up for time-lapse, I just close the rear screen and let it run through the printer
@EB3DPrinting when you say "close" do you mean set the camera to sleep? Because I have mine closed and it still does it.
@Chris Woods Just close the back screen shut. What you can do is run the test snapshot macro to see if the camera still functions while it is saying its busy