Try the attached firmware for the QHY8 instead of the default. It will save as a mono image and you'll need to debayer the image to make it colour. You will also need to adjust the size as well as it includes the overscan regions.

Many Thanks fmozza to your reply !

Finaly, I was able to connect my old CP6-CS based on QHY8 camera.

To do this , I put your file QHY8.HEX in the /lib/firware/qhy diretory in place of the old one.
I run the lsusb command to recover information of the camera and I configure in the /lib/udev/rules.d/85-qhyccd.rules file.

What I have deteted is that the information send by the CP6-CS ( based on QHY8 camera ) is changing...

I recover:
Bus 001 Device 012: ID 16c0:2972 Van Ooijen Technische Informatica ... the first time I connected the camera
when I have restarted the rasberry I get
Bus 001 Device 012: ID 1618:6000 ... without other information...

the third time
Bus 001 Device 012: ID 1618:6001..

So To be reconnized by EKOS, each time I restart the Rasberry, it is necessary to detect information send by the CP6-CS, and to reprogramme the /lib/udev/rules.d/85-qhyccd.rules according to info read by the lsusb command.

Are you award about this very strange behaviour ?

In any case many thanks for your driver which seems to work for the moment !

JC

i'm not exactly sure what you have changed, and I'm not familiar with the CP6-CS, but perhaps there is an issue with the firmware loader fxload. Run "sudo apt-get install fxload" to see if you have it installed or what version you have running.

jmh

Thank for your quick reply. Before trying hte "sudo apt-get install fxload" command, I have an other comment. Apprently, the gain and offset is not available in the capture module nor in the INDI control panel . When I send a get_indiprop, gain and ofset are available the inova camera but not for the QHY8 .. Is this normal ?

Best regards.
JC

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.