Is there a way to update the INDI drivers? I have tried...
sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
...but I still have issues getting my Player One Uranus-C camera to be able to shoot in the 16-bit setting in Ekos. The camera is actually 12-bit, but you can only use a 16-bit setting in Ekos to capture in high bit. It only shoots and captures one image, then locks up. The system itself is not.
I contacted Player One on this issue, and they showed me a video of the Uranus-C working properly in 16-bit on their Astroberry setup. Therefore I can only surmise that somehow my INDI drivers are not the most recent ones, because it's working on their Pi and not on mine.
So is there a way to update these drivers? Below is a screen grab of what my system is listing as versions. With these versions my Uranus-C refuses to work in high bit.
Any help with this is appreciated, thanks.
It's never reassuring when there is no reply to a serious problem with INDI/Ekos...
So I've updated my Astroberry system to version 2.0.5, and KStars to v 3.6.0, and I'm running some tests with my Player One Uranus-C IMX585-based camera.
Ekos recognizes the camera, but my file options are FITS or Native, RAW 8-bit, RAW 16-bit, RGB24, and Luma. The camera is a 12-bit camera, so I assume I have to set the camera to record at RAW 16-bit in order to capture the full bit depth data.
However when I do that Ekos only captures the first image it shoots, and then hangs indefinitely. I have to shut down and restart the Ekos session in order to have access to the camera again. If I set the file format from FITS to Native in any bit depth, Ekos simply crashes.
If I set the camera to RAW 8-bit or RGB24, then Ekos can capture a successive series of FITS files without issue, but these are 8-bit per channel format.
Below are the basic settings I have for the Uranus-C.
So how can you get Ekos to record the full bit-depth data from the 12 bit per channel data coming out of the camera?
Title says it all. I'm considering getting the new Uranus-C camera, which runs off the IMX585 sensor. Has the Player One driver in Ekos been updated to recognize this camera?
Hi folks, if I'm guiding via PHD2 in Ekos and I want to change the guidecam settings like gain and contrast, if I change them in the Ekos Profile Editor, do they have affect in PHD2, or will PHD2 automatically select the gain values it wants? I see no settings for gain, contrast, etc. in PHD2.
Well my modus operandi is to have two profiles, one with the SV305 as the imaging camera and CEM26 mount (for plate solving to position), and a separate profile with an ASI120MM camera set as the guide camera with the CEM26, sans main camera. I can also apply a sim camera emulating the '305 FOV, but that's not really important. Once plate solved with the '305 as the main camera, I would switch profiles, start autoguiding with the ASI, and connect the '305 to AstroDMX.
However running some tests I'm seeing massive CPU usage and rising temps when running simulated shooting sessions with AstroDMX, as you can see below. When idle at shooting speed, CPU usage is around 85%(!) the temps are up around 65°C(!). For some reason CPU usage drops somewhat when actually shooting. There's slightly less CPU overhead at 8 bits, but "the song remains the same". Some formats are more taxing than other.
So I'm wondering if I should just scrap planetary shooting with the Pi altogether and just use my Windows ASCOM setup tethered instead
Thing is, I can't tell if Ekos will be able to solve, because I can't really see what it's recording. If I set the FITS viewer to debayer I can see something, but honestly I don't know if it's sufficient for Ekos to plate solve. I have the 305 on the C5 with a 2X Barlow, so I have a very narrow FOV. I have the entire astrometry database, but I think it will have to blind solve, assuming it can see something. I actually plan to shoot with AstroDMX, but first I have to get the camera locked on the target, hence why I want to plate solve (and guide) with Ekos. I would have no idea otherwise how I would find a needle like Jupiter in a haystack like a 2500mm scope with a 1/2.8" sensor attached to it.
So does Ekos know how to properly use the FITS image data to plate solve?
Hi folks, I would like to use my SVBONY SV305 Pro camera as a primary camera. In order to use it as such, and especially to be able to plate solve with it, do I need to set AUTO DEBAYERING to ON in the FITS configuration settings? What about AUTO STRETCH? Are there any other particular settings that should be on, off, or set to a given parameter?
Thanks for any info on this.
What kind of load is on your rig? Are you at the halfway point, or at, or surpassing, the load limit? My friend was over capacity on the Star Adventurer. We think think that's the problem.
What mount are you using? Are you well balanced and within the mount's weight capacity? We believe the problem with the Star Adventurer was that it was overloaded and mistracking, causing the guider to autocorrect, probably making the situation worse. We have yet to try and confirm this with a lighter load.
That's probably not a bad idea, but just making a note that the SV305 driver will work with the SV905C would be good.
Well to whom this may concern, the driver for the SV305 will work with the SV905C. I was informed of this at an SVBONY forum.