Purged the settings, now everything seems fine but the camera still does not fire the shutter, I get the message, failed to expose, error downloading image from camera: directory not found. Which is of course set and created. I already found images from previous "successful" attempts in this directory.
And now, whiever way I connect to the camera it just doesn't work. Ekos tells me to check indi settings, where I am instructed to check image info as there is no CCD info set. No problem, I try to set it, and no matter how many times I click SET, nothing happens. It won't enter the numbers. If I click to many times it crashes. Did I forget to feed it donuts today?
I will check that out.
A side note, I have both DSUSB and FTDI chip for the camera in subject.
Thanks kross I had no idea that's how Linux sees COM ports. However, I have tried that yesterday without any success. Would the /dev/ttyUSB0 need to be set under Gphoto camera or under Nikon camera driver?
El Corazon, you are partly right. I agree, the DSUSB is really just a dummy shutter. All it does that it shorts three cables and holds it for the desired seconds, thus long exposure.
But, the D5100 is not a full fledged astro camera. I utilizes two USB cables to achieve anything over 30 seconds exposure. 30s or less only requires the main USB cable, no DSUSB needed. This is the cable that is used to download the image to the PC/Pi 4. As I could do 30s< exposures even if I picked the native Nikon driver in INDI, it always downloads the image to Pi 4 via this cable.
Exposures over 30 however is a different question. I have the DSUSB control box and built myself a USB shutter control that is based on FTDI chipset from CN forum. They both work under windows and do the same thing. Short three cables for the desired time and use the main cable to download the image. I have never had to use memory card in the camera for this too.
So, in summary, the D5100 does need the help of an extra long exposure cable. If you go to any capture software website, they have this detail in their camera compatibility matrix.
No more idea? I guess it's Windows then...
I have the D5100. Regardless, no matter what I do it just doesn't work. It now fires 30sec or less. It crashed on me like 5 times though
No. Should I have one?
In Ekos Equipment Profile, select GPhoto driver and not Nikon. Save your profile and try again. I'd turn turn off Auto Connect in the profile. Check the Logs button in Ekos summer screen and make sure it is set to Verbose File logging and both INDI + Camera checkboxes are ticked.
After you start the profile, set DSUSB in the GPhoto driver, then go to Options --> Save Config.
Then click Connect and let's see how it goes. Locate (in the same Ekos logs window you can open the logs directory) and then attach the log file here.
Yes, finding and using terminal is not an issue. This is where the static IP needed to be set to
This is what it looks like on my set up
Section in here about shoestring astronomy and GPhoto use with DSLR;
"When using external shutter release cable, you must use the GPhoto generic driver and not a camera-specific driver (e.g. Nikon) as only the GPhoto generic driver would work with external shutter release cables. Additionaly, users may employ DSUSB/DSUSB2 from Shoestring Astronomy in order to control the shutter. Before you connect, the port field must be set to DSUSB."
And one more thing. I had figures out how to connect and VNC into my Astroberry Pi via internet. I had to have a very good friend of mine helping me out from overseas, yeah from another continent.
And in summary the solution, and organized solution could have been listed to me in four very short line. Something along the lines like this:
Regular Joe, Google the followings:
- How to set static IP to your Pi
- Set up port forwarding
- Use whatismyip.org
I could not find anything like that on anywhere. Solution so simple...
I have never meant to offend anyone here or any of the developers I've made that clear in my first post in this thread. I have a beef with Linux/Indi/Ekos as they seem to work rather erratic then organized, and I've heard poems about the reliability and simplicity of Linux in general. Absolutely contradicting with my experience.
For example, take the link you provided: indilib.org/forum/ccds-dslrs/5047-kmtron...e.html?start=0#37912 I have searched and searched before started this thread and came across this one. There are several little problems with that thread.
1. The op makes it clear he has no serious Linux computing background
2. Dispite this fact there is virtually no real help in that thread, as people just say things out of the box like "Gphoto driver" and "dmesg". Let me translate that to English for people who are not software developers or engineers... ??????? That is what those things mean to me and the forum, not just this one, is filled with "information" like this. Again, have nothing against people here, just trying to shed lights on this from a perspective of a regular Joe.
3. Knowing now that update, upgrade and install in linux does not work like in windows (download installer, install etc), I am sure there is a "sudo apt, sudo update, sudo upgrade" command somewhere in that thread. It is just lust in the process of assuming that everyone is versed in programming language.
If you'd be so kind and educate me please what all those mean, how do I check if the FTDI USB created a /dev/ttyUSBX entry under astroberry/Indi/Ekos, and how do I update Gphoto driver and how to check if I even have to, I'd really appreciate it.
And BTW, I have the same issue that the very last post by CedrictheBrave says there. I guess he did not understand the thread as well.