Yeah, dunno know what to think of it. Fortunately AstroDMX will be an effective planetary app when I finally get around to shooting planets, and the long exposure simulation from Ekos rendered well enough to make me think it's not going to be an issue for low res DSO shooting.
Well yes I know the RGGB array (or GRBG, as it is in the IMX290 sensor), but it's the bizarre posterization that I was really referring to. As I mentioned working with FITS is new territory for me, so when I see stuff like this, I'm not sure what to think of it.
OK, so I got Ekos to record data from my SV305 Pro camera again, but running some tests, I get some crazy looking data, and I'm not sure what to think of it.
This started when I was curious as to whether I should adjust RGB channel gain settings to adjust the color balance that comes out of FITS files, which are always predominately green-yellow.
So below first are 2 screen grab images are from AstroDMX, first the image as it first appears onscreen when I connect the camera, the second is a color corrected image using the "one touch" auto color correction button in AstroDMX. This color chart is being lit by 5000k lights. As you can see, AstroDMX applied R and B bias adjustments to balance out the color. This was the premise I thought I may apply to the the R and G gain settings in the INDI control panel for the SV305 Pro for color balance. So I decided to take some tests first with the Ekos default values for the SV305 Pro, and what I got throws me for a loop. These images are saved out as JPEGs from the ASI FITS Viewer app in Windows.
So the first set is:
5 second exposure no gain auto debayer (KStars)
5 second exposure no gain no debayer
5 second exposure 50 gain no debayer
Than, being as this is primarily an planetary camera, I tried a:
.01 second exposure 100 gain no debayer
And then finally I turned off the room lights and tried to emulate a DSO sub at:
30 second exposure no gain no debayer
So the $64,000 question is; Is this normal? Besides planetary imaging with AstroDMX, I want to experiment with the camera for some DSO work, and the long exposure shot at zero gain gives me hope LOL. However, what's going on with all those other shorter exposure shots? Looking at the 30 second exposure, it appears I don't need to adjust the R and B channel gain setting in the INDI control panel and can just leave them alone.
Working with FITS files is a new territory for me, so I don't really understand why I'm seeing what I'm seeing here, and for DSO work it appears as tho I don't really have to worry about it and just shoot at whatever exposure I may need for a given target. But any insight on why this stuff looks like it does is appreciated.
Wow, that worked! Thanks! I thought I was going to have to use my ASCOM setup to shoot with this camera. I hate having to deal with the ASCOM setup.
I hope it doesn't do that again, but if it does, I hope this fixes it again.
Begs the question tho, why is it happening in the first place? I had brought the camera into the Windows ASCOM machine, where i had installed new drivers for the camera and for ASCOM, and I wonder if the new SVBONY driver(s) updates the firmware in the camera somehow. There's no mention of that in their info tho, so I would suspect not, but you never know.
BYW, I contacted them about back focus information, as surprisingly there is none in the docs. With the C mount adapter attached (which I use to screw the camera to the scope and bypass the 1.25 mount, which can skew the sensor off-axis), the total back focus is 17.5mm. FYI.
Thanks again. I'm so happy I don't have to rig this camera up to my ASCOM system!
Ekos is all of a sudden recording zero data off my SVBONY SV305 Pro camera. It was working fine before, but now it collects no data. I creates FITS files, but there's nothing on them. I switch over to AstroDMX (not running concurrently) and it can record data and give me a preview, which Ekos no longer does as well. It doesn't matter how high a gain or how long an exposure time, it just records blank files.
I decided to run an Astroberry update in hopes that would help, but it did not change. I'm at a loss as to why this is all of a sudden happening, as it was running just fine. I've not made any changes to the system in any other way. As I said, it works in AstroDMX, as well as with apps on my Windows ASCOM setup.
Well I changed the password in the Pi VNC. The PC is mere connecting to it, so I just changed the connection password in the VNC Viewer app on Windows to the new VNC password.
I think that will take care of the situation, but if need be I'll change the host name as well. Thanks for your help.
OK well, I changed the VNC login password using the VNC applet, I did not realize it had it's own password. I assume that's how the 2 computers got intertwined. However you got me thinking about the host name, how do you change that?
I recently changed my WiFi password, but when I try to log in from VNC, I can't log in unless I type the default astroberry password. I've tried using both astroberry.local and the IP address for the server, but I can't log in with anything but astroberry for a password. This created an issue recently when my friend and I were both using Astroberries, and he was still at the default name, and our two machines became connected.
So I'm at a loss as to why this is.
I'm renting an Oly E-M5 Mk II this week to see if I can control it from Ekos. Looking at the libgphoto2 camera list, it should be able to be controlled.
Have you tried to import files into the Pi from the Olympus? Without the ability to import files you cannot plate solve.
How do you get Ekos to take bias frames? My cameras, a Nikon D600, D5300, both have 1/4000 second shortest speed.
However when I try to set it for bias, Ekos shoots and 11 second exposure. I noticed if you hit the down arrow in the exposure box, it goes through a few settings, then jumps down to 1/25000 sec. None of the sub-second exposures work however, they just take an 11 second exposure, then re-open the shutter and then leaves it opened. I have to turn the camera off to close the shutter.
So how does one get Ekos to properly take bias frames?