You can do it with Sharcap or Firecapture by example. So the background is more neutral.
Is there a way to adjust the histogram of the red, green and blue channels of a CMOS camera like the QHY183C?
It would be interesting to balance the background of the sky during capture.
I specify that in total remote mode, Kstars is executed in remote, the XML files are correctly generated for the two QHY cameras.
I made recently messages about wrong parameters loading for my two cameras. I investigate today what could happen.
When I work locally, all devices connected on my PC, no errors. The rights values for cameras parameters are saved and loaded from unique file for each camera: QHY CCD QHY183C-e7952d4_config.xml and QHY CCD QHY5III224C-bc5_config.xml. But when I am in remote configuration issues occure.
The setup: Mount, QHY183C and QHY224C connected to a TinkerBoard used as Indi server. Kstars runs on my PC. Thee XML configuration files are saved on the TB. But instead of two different files, one for QHY183C and one for QHY224C, the system creates only one file QHY_CCD_config.xml. When you save the indi parameters, there are writed into this file for the both cameras and so the last saved crashes the former.
I try to use client, local or both into the Indi tab options with the same result.
Thank for your help.
At the end I discover the origine of this issue. I have to put the brakes on really, really hard. So the guiding works perfectly.
Thinks for your help.
"Regarding mount, Celestron MUST be aligned from the handset before you can connect it to Ekos.". Is pointing at a star sufficient please?
Until the last version of Kstars, the cooling worked enough well.
Since the release it is less true. The temperature measured and displayed grows up to more than 5000°!
Deconnecting and connecting Ekos seems to cure the issue.
This function is really not stabilized.
Thank you for your answer. About guiding, it is via the mount. Using the Indi mount driver, the mount moves well. What is surprising is that sometimes the guidance starts on an object and not on the next, with an error in RA or DEC, during the same night.
If the mount must be aligned before connecting Ekos, what about the Ekos polar alignment and mount model in this case? No use ?
About indi device configuration, it occurs for the mount, all parameters about focal and aperture are all loosed ! I send you previously , the QHY183C XML file and the screen capture with different values. Load config doesn't work right in my thinking. I'll try next session.
Is there anybody out there ?
Yesterday night was an awful nightmare with Kstars-Ekos-Indi !
My setup : Celestron AVX, SW ED80, QHY 183C, QHY 224C. All device plugged on a TinkerBoard (with NAFABOX system). Connection between the TB and my laptop with a RJ45 cable. This setup works perfectly for the last two weeks. I do all the polar and stars alignment with the nextar. Kstars V3.4.2. On sunday night I could image M65-M66.
I began to have issue with the TB (?) after an update. The Indi server breaks some time to time, but I can take images until last Sunday.
First of all I don't understand at all how the mount reacts at the Ekos connection. The setting is Ekos updates all devices. The mount is not located on the Polaris in Kstars. I have to do a polar alignment with the nextar to obtain the right location. Why ? I Would think doing an Ekos polar and stars alignment was the right way. So I do an Ekos polar alignment. But the pointing during the stars alignment was absolutely wrong !
More, the park is not the same if I do it with the Nextar or with Ekos.
If the QHY 183C works well this night, it was not the case for the QHY224C. Impossible to capture images into the guiding module, internal or PHD2 as the cam was not connected. I change USB place on the TB, but the result was not convincing. So I connected all the device with an USB3 hub (not powered) to my laptop and the 224C works well.
One more time, the cam settings (gain, offset, USB trafic, USB buffer) were not loaded correctly. And even the mount settings were not correct. By example focal 1800 instead of 510, or all the focal and aperture settings were losted ! I don't think it is an issue with the QHY SDK in this case. I made several message about this issue with no answer.
Issue also with the internal guide. Often the calibration fails. Either on the RA or on the DEC. Sometimes the guiding starts and runs well ?????? It is more reliable with PHD2. My settings for the guiding are: cam gain 11, exposure 1 or 2 sec, dark used, bin 2.
I join all the log files of this awful night. thank you for your help.
I use a TinkerBoard with NAFABOX system (Ubuntu 18.04LTS) both a QHY 183C and QHY 224C. I use also an RJ45 cable 30m long to connect the TB and my laptop. I don't use USB3 HUB and all work perfectly. The wifi of this card are too feeble and need to be replaced by a directional antenna to run well.
The only issue I have, is the loading of default camera settings (gain, offset, USB trafic and USB buffer). The right values are not loaded correctly for some or all the settings.
More the USB buffer setting don't appear in the XML file configuration of the camera.
The cooler regulation works pretty much but no more.
join to this message the QHY183C XML configuration file and a screen capture of the Indi panel just after connection. Curiously, the parameter USB Buffer doesn't exist in the file. The XML .default file, all the value are 30.
Thank for your support.
I have always issue with saved configuration. At the next session, the QHY parameter are not well recovered. Often the offset is 0 when I saved 3. Same for USB trafic. It back to 30 value instead of 0 saved.
Do I have to load a right configuration or is these saved that will be load?