I haven't used this camera for awhile and I can't recall if the gain and offset were available with the revised firmware and/or driver. When I get some time, I'll connect my QHY8 and see what the INDI panel shows. What version of qhy driver are you using?

Regards,

jmh

What I get from indi_getprop:
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_NAME=QHY CCD
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_EXEC=indi_qhy_ccd
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_VERSION=2.6
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_INTERFACE=18

Thank jmh for your help.

JC

I will add ...
when I keep by indi_getprop the driver interface I have :
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_INTERFACE=18

But on the INDI control panel, I get 22...?

This day off inFrance, I try other HEX files... Instead of QHY8V2.HEX, I tryed QHY8L.HEX and QHY8PRO.HEX. With those HEX file, the gain is available in the capture module. And the offset and USB speed are available in the INDI control panel but... when I start an acquisition, the image is always dark...(...and even if have chage the offset and the USB speed is not changing ( always fast )...
I am questioning agout those HEX file generation which seems to the answer of my acquisition problem.
How are they build ( in C, other lagage, compiled with ? ...) . If no devloppers can do the update, where can I find the input to corrected if to be compatible with my CP6-CS camera.

I am quite familiare with C,C++,linux GNU or makefile and I fill confident to adjust it for INDI. I have already mad the job for a home made mount application under Raspberry that I made compatible as a LX200 GPS mount.

Here under I put all the INDI properties that I Get with the QHY8V2.HEX release that can show clealy that no GAIN nor Offset properties nor USB speed has been declared:

QHY CCD QHY8-C-010103XX.CONNECTION.CONNECT=On
QHY CCD QHY8-C-010103XX.CONNECTION.DISCONNECT=Off
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_NAME=QHY CCD
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_EXEC=indi_qhy_ccd
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_VERSION=2.6
QHY CCD QHY8-C-010103XX.DRIVER_INFO.DRIVER_INTERFACE=18
QHY CCD QHY8-C-010103XX.POLLING_PERIOD.PERIOD_MS=1000
QHY CCD QHY8-C-010103XX.DEBUG.ENABLE=Off
QHY CCD QHY8-C-010103XX.DEBUG.DISABLE=On
QHY CCD QHY8-C-010103XX.SIMULATION.ENABLE=Off
QHY CCD QHY8-C-010103XX.SIMULATION.DISABLE=On
QHY CCD QHY8-C-010103XX.CONFIG_PROCESS.CONFIG_LOAD=Off
QHY CCD QHY8-C-010103XX.CONFIG_PROCESS.CONFIG_SAVE=Off
QHY CCD QHY8-C-010103XX.CONFIG_PROCESS.CONFIG_DEFAULT=Off
QHY CCD QHY8-C-010103XX.CONFIG_PROCESS.CONFIG_PURGE=Off
QHY CCD QHY8-C-010103XX.ACTIVE_DEVICES.ACTIVE_TELESCOPE=LX200 GPS
QHY CCD QHY8-C-010103XX.ACTIVE_DEVICES.ACTIVE_ROTATOR=Rotator Simulator
QHY CCD QHY8-C-010103XX.ACTIVE_DEVICES.ACTIVE_FOCUSER=Focuser Simulator
QHY CCD QHY8-C-010103XX.ACTIVE_DEVICES.ACTIVE_FILTER=
QHY CCD QHY8-C-010103XX.ACTIVE_DEVICES.ACTIVE_SKYQUALITY=SQM
QHY CCD QHY8-C-010103XX.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=0
QHY CCD QHY8-C-010103XX.CCD_ABORT_EXPOSURE.ABORT=Off
QHY CCD QHY8-C-010103XX.CCD_FRAME.X=0
QHY CCD QHY8-C-010103XX.CCD_FRAME.Y=0
QHY CCD QHY8-C-010103XX.CCD_FRAME.WIDTH=3040
QHY CCD QHY8-C-010103XX.CCD_FRAME.HEIGHT=2016
QHY CCD QHY8-C-010103XX.CCD_BINNING.HOR_BIN=1
QHY CCD QHY8-C-010103XX.CCD_BINNING.VER_BIN=1
QHY CCD QHY8-C-010103XX.FITS_HEADER.FITS_OBSERVER=Unknown
QHY CCD QHY8-C-010103XX.FITS_HEADER.FITS_OBJECT=Unknown
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_MAX_X=3040
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_MAX_Y=2016
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_PIXEL_SIZE=7.8000001907348632812
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_PIXEL_SIZE_X=7.8000001907348632812
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_PIXEL_SIZE_Y=7.8000001907348632812
QHY CCD QHY8-C-010103XX.CCD_INFO.CCD_BITSPERPIXEL=16
QHY CCD QHY8-C-010103XX.CCD_COMPRESSION.CCD_COMPRESS=Off
QHY CCD QHY8-C-010103XX.CCD_COMPRESSION.CCD_RAW=On

The sky is cloudy...But we know that clear night are always comming !

JC

JC,

Sadly, the camera is an older camera no longer properly supported by the new driver. I don't know how many EKOS/indilib users have older cameras (support for the QHY9S may also be deprecated shortly as well) but perhaps a gentle lobby from users to QHY may help. I think they'd prefer that we purchase new cameras ...

I was thinking an older vintage driver, perhaps a few years old, might be able to be dusted off and used instead, but I haven't had the cycles to dig through the archives for one. Perhaps some of the maintainers might know where to look, or even indicate if this is possible.

Regards,

jmh

Thank you jmh for your reply.

I am totaly understanding your answer ! So the way will be be hard ... I will try this WE to generate a customized CCD driver interface ( based on github.com/openastroproject instruction ...) And we will see.

Have clear night !

JC

jmh

If you want to play again with the QHY8, I let you know that I finaly succed. I had to recompile the Indi 3rd library for the QHYCCD patching the possibilities to use the gain Offset and low speed USB necessary to used this Cam. The last item I not succeed is patching the driver for using binning 2X and 4X useful for MAP or accelerating the atrometry resolution. But it works now for nominal acquisition.

Have a nice sky.
JC

I would keep watching this topic. I tried to replace the .HEX file with the one provided here. www.qhyccd.com/bbs/index.php?topic=5789.0 I was able to connect QHY8 afterward but there is no way for me to control the gain and offset of the camera.

Hi Reticyte

If you are using the hex file you have mentionned, you will not be able to use gain/Ofsset and USB speed ( you need to slow with the camera... )
To get those functionalities I succed ( After almost one year....) to find how in re-compiling the QHY 3rd driver modifying ( very slightly... ) in the code test concerning those three prperties.
I have recompile for rasbian buster with Astroberry environnement.

The small remaining bug is that when you stop the camera during acquisition, the connexion is completly jamed. But here also I found a way with a unix command in reintialisation to restart the connexion. This permit to avoid a deconnexion of the usb cable which was necessary before. I plan to use Ekos in remote at 500 km from where I am living so I was wondering not to move each time the connexion was out !

So If your are using astroberry/Rasbian , I can send to you those released of QHY 3rd Driver if you are interrested in (without garanty ...! ) or is you are confident to recompile the drivers in your environment, I can show you the modification done in the code whiche is very small. As you want ..

JC

Wow, that was quite an effort you made, I am currently using Astroberry + EKOS, I believe your work will solve my problem. If you don't mind, would you send me the driver first so I can get the camera to work on Astroberry?

Meanwhile, I am also curious to know what kind of modification you did to the driver to make it work, maybe I can look into the jammed connection problem with some digging and lucks.

Hi JC,

I have the same problems as you, not being able to set gain and offset or the USB speed. Over the years, I have tried various incarnations of the QHY8.HEX file (from this forum and the QHY forum), with no real luck.

If you managed to work out a 'fix' in the driver that would indeed be amazing. Would you mind sharing your .HEX? (or mods in the source code which then needs to be recompiled)

Currently working in a windows 7 environment (which runs great), but would love to run in the Astroberry+Ekos env.

Cheers,
B

So...

Firstly I had to review the step to compile and install this driver through the make file.

See firstly the file "qhy_ccd.ccp" that I have modify to validate gain,offset and USB Speed. You will see that the modification is very simple but not portable ( be care if your using QHY8L and 8Pro...). As you will see there one point that I was not able to activate is the binning 2X2 and 4X4... that a little bit frustarting whan I making a atroresolution wit hte 1X1 binning. It take longer timer than if I was able to active the 4X4 binning. That will be the next step.
If you fill confident, you can follow the indication done on "github.com/indilib/indi-3rdparty" to recompile the QHY CCd driver with the "qhy_ccd.ccp" file I have send to you and install it.. If you do so, of course I will convince you to make a copy of your entire rasberry system due to the risk of installation crash you may.

If you don't fell confident , I propose to you to copy the lib here with "indi_qhy_ccd" and copy it in the /usr/bin directory renaming the existing file with old extention in case it is not working . you should do that with the "sudo" prefix comman I supose as you are in the systme files. I am not sure that it will works due to that fact that I have use the "github.com/indilib/indi-3rdparty" indication to compile and install the new lib. But let try... I think it shoud works.

in any case, let me know if it works !

If it works, on last thing, the command to reintithe usb connection if you interrupt the acquisition before the end of the exposition..:
open a command line and type:



JC