Come and join our community. Expand your network and get to know new people!
Thanks Jerry and Thomas for explaining, that makes total sense!.
I believe I have a SSD disk laying around, I will try it to speed up the saving process.
Well speaking for myself, I've read the thread with interest, but sadly I have no advice to provide. I was thinking of an AZ-GTI as a portable mount at some point, so I am interested in seeing it working, but can't help.
Please don't let my frustration with the Stellarmate/AZ-GTI combo get in your way of your wide angle goal. While I have the same error message I'm not exactly sure whether it effects my operation or not. It could be part of the reason I don't track well with Stellarmate but sadly this hobby, at least when I'm off in my own less favored equipment set like the AZ-GTI and Stellarmate on a Raspberry Pi, just doesn't get much attention or support. Or possibly I haven't figured out how to get real support.
You are the only person who responded to this thread which was posted roughly 5 months ago so clearly either very few people see this problem and have nothing to say or no one's reading this thread.
I hope this year to do some wide angle mosaic shooting. It would work well with my setup. I think the way I would approach it with Synscan would be to do a few 3-star alignments and then just map out major stars in each section of the sky to center on ahead of time. Sadly it's monsoon season here in Tucson so I've barely seen stars in the last month or two but I hope to get back to shooting on a more regular basis in October or November.
Here you are.
The CEO at Player One is again quick in response on a Sunday, when I informed him about the discussion here.
Thank you for feedback. We are working on updating the new models in INDI, including Uranus and Saturn series.
I think it will be done soon. We will update info on our website and facebook page.
CEO | Player One Astronomy
the INDI Gphoto driver uses the libgphoto2 library to communicate with the DSLR.
Setting the camera's SD card is basically the same as e.g. using the command line tool and setting:
gphoto2 --set-config capturetarget=1
Just a simple yes/no would be fine.
Is it possible to use a star extractor other than the sextract from StellarSolver to extract stars from the guide camera frames?
I can't replicate your issue (using 3.5.9 on OSX).
Could you please take similar screenshots?
Sorry if I were not clear. I was talking about the Dome module, as you showed.
I have no dome driver in my profile and still the Dome module is shown. With the Simulators profile, it behaves as expected.
I had a look in ~/.local/share/kstars/userdb.sqlite and no occurence of a dome driver in my profile.
So why is the Dome module loaded?
Hi, I have exactely the same weird line with Raspberry, it seems a KDE bug.
A driver is alive but issues still going.
It will be fix soon.
I opened a ticket on github and had rescue from Jasem and Hiro.
ok just tried taking darks, dark flats and biases and didn’t get a single prompt to cover my camera lens. I’m sure I have in the past.
The camera took all the images using the shutter. The biases at an automatic speed supposedly of a blistering 1/32000 which I would have thought is faster than the camera can go.
Tried doing darks using the dark library with the same result.
The indi device log gave a warning saying my camera had no shutter and I needed to cover it.
I’m using a converted NUC and getting a display issue. Am I missing a driver or something else ?
@Peter I’ve wondered about that in the past and for some reason didn’t think it kept the shutter closed. Will have a play as that would be great.
@Jasem If Peters suggestion doesn’t pan out I will give that a go. Couldn’t the dark flats just follow the same type of process that darks follow and ask to cover the telescope? NB I currently tend to set things to take a batch of images and then sit and wait rather than set up a whole set of things so I’m not sure if that happens with darks when there’s a set of jobs