**** Is there a way to get ekos to fire a capture command to a port on the rpi3 server without a driver?****
Or alternately is there an easy driver I can use to get the trigger? --Or maybe I need to write something? I'm up for whatever but hoping for an easy answer we can all use for old school external triggering for ekos scheduling.
I've been working for quite a while on getting a remote set up with my DIY Arduino_cgem_driver mount ,an Rpi3 running Raspian and indiserver drivers lx200, v4l2(picam guinding), and gphoto2 for the DSLR camera capture. I kept getting stumped by a lack of support for my Pentax K-50 or Eos-m cameras. This appears to be due to manufacturers not allowing it in firmware. Since the remote IR trigger works on both units I decided to make an Arduino based IR trigger for the system and integrate that through the trigger port in the indi driver using the gphoto2 indi driver. I was able to get the trigger to work standalone using serial commands sent to the usb but the eos-m will not allow function or IR while plugged in, and the k-50 lacks support of any kind in gphoto2 and so gphoto won't start in order to provide ekos with a capture port to request. ARGGGH!
Picture recovery is currently going to be done by way of Flashair card to the rpi3/indiserver on the mount or directly to the pc on the lan.
Or alternately is there an easy driver I can use to get the trigger? --Or maybe I need to write something? I'm up for whatever but hoping for an easy answer we can all use for old school external triggering for ekos scheduling.
I've been working for quite a while on getting a remote set up with my DIY Arduino_cgem_driver mount ,an Rpi3 running Raspian and indiserver drivers lx200, v4l2(picam guinding), and gphoto2 for the DSLR camera capture. I kept getting stumped by a lack of support for my Pentax K-50 or Eos-m cameras. This appears to be due to manufacturers not allowing it in firmware. Since the remote IR trigger works on both units I decided to make an Arduino based IR trigger for the system and integrate that through the trigger port in the indi driver using the gphoto2 indi driver. I was able to get the trigger to work standalone using serial commands sent to the usb but the eos-m will not allow function or IR while plugged in, and the k-50 lacks support of any kind in gphoto2 and so gphoto won't start in order to provide ekos with a capture port to request. ARGGGH!
Picture recovery is currently going to be done by way of Flashair card to the rpi3/indiserver on the mount or directly to the pc on the lan.