So the first 2 things you posted here are not errors. The first item, the PTPCamera dialog is how you will be able to quit PTP Camera so that you can get your camera to be available to connect to it. If ptp camera keeps running, then it will block access, The dialog is a nice way to quit the program. The second item just says that you have not yet saved your driver configuration, it is not really an error per we, because that is optional.
The third item is actually a connection issue that you will want to investigate.
For this item what I usually do is to use an option that is located in the Focus module. There is a button called "Framing" that works exactly like what you are looking for. In fact, you can even set this Framing Image to display full screen which is quite helpful for manual focusing but would also be quite useful for your purposes.
I too would like QHY to do a driver update. The current Mac driver has a build error due to the fact that the QHY dylib has not been updated. So I haven't been able to include QHY in the latest Mac 3.1.0 beta versions. I hope this gets fixed soon because I don't think we can do a proper release without QHY.
Kstars/Ekos on Windows is a very active program. It is an open source, community driven program. Basically the same code in KStars is used on Mac, Windows, and Linux. There are new commits every single day from multiple people:
. There are new stable versions released for windows every few months with the last one released in December:
In fact if you want to test the latest code, you can download a nightly build. binary-factory.kde.org/job/KStars_Nightly_win32/
As for the program INDIServer for Windows, I assume you mean the Cloudmakers program? That is produced by a private company called Cloudmakers. You would need to check with them.
So that box that popped up is not an issue, it is the new feature that I added so that you can update the config file inside the app bundle to match the location of your computers index files. I added it to fix the issue that was reported the last time I posted the dmg of the path to the index files in the config file being incorrect.
Awesome, I knew it was probably either Prolific or FTDI, but couldn't remember for sure which.
Diskutier list should list any hard drives, I think the command you want is this one:
No you don’t need a driver from Synscan or skywatcher etc. that is what the INDI driver is for. The only thing you might need a driver for would be the Usb to serial adapter or FTDI internal adapter if there is one which it sounds like there is. I can check the settings that I used to connect to a synscan later this week
Ok now I understand what you mean about the picture now that you said "white picture". I think the issue you are referring to has to do with the image stretch and display of images in the fitsviewer. I suspect this does not have anything to do with your camera or the connection to kstars actually. It has everything to do with the stretch that is being applied and the either the brightness or signal to noise ratio of the items in your image if I understand your issue correctly. I have observed similar behavior in a couple of different circumstances myself recently.
One situation in which I have seen it was when some of my images were too short and had too little signal to noise ratio. They stopped showing a noise pattern and went all white. I'm planning to look into the cause of this. In the past, when this has happened, it just showed a dimmer noise pattern, but something seems to have changed in that regard. But a longer exposure time fixed the problem and showed a noise pattern again.
The other times I have seen it go all white was when the exposure time was too long. For instance when using a ZWO camera and taking pictures or viewing in live video during the daytime or in a room in your house with the lights on, you have to make the exposure time for images or frames in a video EXTREMELY short because the ZWO cameras are so sensitive. The last time I put it on live video in a room, I had to basically cover up the camera with my coat before I could see any details in the screen that were not over saturated. I would like to see if we can change the live video controls to allow exposure times shorter than 1 ms, because that is just too long with a ZWO camera for some targets like the moon and bright planets.
Birthdate19. 07. 1980
About meEven though I am relatively young, I have been an astrophotographer for about 20 years. Within the last 5 years or so, I have taken my hobby to new heights. I built my own 10 inch telescope including grinding the mirror, bought a wide field newtonian for wider fields, acquired a much better mount to put them on (separately), got an SBIG camera for cooled CCD photos, modified a Canon XSi for better DSLR photos, and got lots of accessories. I have been doing all of my astrophotography with a Mac computer. I have basically made my own portable observatory, everything is carefully organized into boxes that I can load into my car in about 20 minutes. I take these things to dark skies and do lots of imaging at star parties.
I found out about INDI in May 2016 when Pleiades Astrophoto sent me an email about including an INDI client in their software. When I investigated further, I found out about KStars and Ekos. I quickly realized that I could install everything on a Raspberry Pi, velcro that to my scope, and use VLC to configure it from my computer using wifi. I have implemented 2 modes. The first is using the Raspberry Pi as an INDI server and using my Laptop as a wireless client using either the EKOS VM (running KStars and Ekos) or PixInsight as the client software. The second is using KStars and Ekos on the Raspberry Pi and controlling everything through VNC. Both methods have allowed me to cut the cords, move to WIFI control, and make all USB connections shorter. The second method also allows me to put my computer to sleep after I have configured the PI to do all the work. All I have to do is check in once in awhile to make sure it is working properly. So far this experiment is going very well, but I did have to work out quite a few issues along the way. I have been keeping a couple of logs of everything I have done to make it work, however, which is very useful. There are still a few problems, but the system is fully functional. It is a good thing it is summer so I have time to work on this!
The remarkable part is that you can automate your astrophotography setup, make the connection wireless, simplify the software by just running one program (KStars/Ekos) that runs it all, and you can make the connection to the devices separate from that program using INDIServer. (The last item is important because if KStars/Ekos were to crash, the devices would still be running on INDIServer.) And all of this will cost you around $100 including the Pi, a case, a 32 MB microSD card, the software, and a powered USB hub. There was a bit more work involved in setting it up and figuring it all out, but it was worth it.
I am an:
Physics and Computer Science Teacher
Delaware Astronomical Society Member
Mt. Cuba Observatory Education Associate