Just to make sure, when you say the image exposure does not change. You have turned of the stretch-button in the FITS-viewer then, otherwise the stretch function will normalize the exposure, with more or less noise as a side-effect.
I'm finding that if I start EKOS and go straight to the camera exposure tab, change gain first to anything 1 or higher, then change exposure to something long. It will give me a true long exposure straight away, and carry on doing so for the session.
Ive found you must not touch the exposure before the gain, as the moment exposure has been entered, a test image is captured automatically, which prevents future long exposures.
The command line I gave before still continues to be 'foolproof'.
I have the Pi HQ Camera and want to try it in an All Sky Camera. Previously I have been using ZWO cameras for this with RPi 3B, in particular the ASI178MC but this is a relatively old camera and needs quite a lot of cooling (using 60s exposures) to reduce thermal noise and hot pixels. This system has worked well with KStars/Ekos/INDI but cooling has produced a complicated setup - cooling the case of a non-cooled astro camera is inefficient. I have friends who would like to make an ASC too but ZWO astro cameras are expensive and would be interested if I can get it working with a cheaper camera.
My thinking is that the Pi HQ Camera is a much later addition to the Sony sensor range and could well be a lot more advanced and more sensitive in spite of smaller pixels.
To summarise, I'm looking to use the Pi HQ Camera with INDI and RPi, maybe the RPi Zero, using exposures of around 30s to 60s.
Its quite useable with the current indi driver if ones takes care to set the parameters in the right order. I'm able to get exposures up to 200 sec, both through indi, and direct RPi command line.
However, I've been running it alongside a ZWOASI 120MM-S in a plate-solving project to compare performances. The small pixels do seem to be an issue. To get anywhere near the same sensitivity as the ZWO camera I have to bin it 4x4.
From what I can gather, it appears the RaspiHQ camera is perfectly usable within Ekos, as long as the correct setup order is done (Gain before exposure if I've read the thread correctly?). I've yet to test this in anger, but I appear to be getting some output during the day which is promising.
What I can't get to work though, is live video or video recording. The live video button below the sequence order window has a cross-through it?! Is this supported yet, or have I missed something on setup?
(Video seems to work fine via comman line and raspivid
Has there been any progress on this driver?
Unfortunately now something is wrong with forum and I can read only First page, and last using Reply trick so I cannot see any posts regarding driver.
I have installed and tried indi_rpicam that does not support video, I would guess that that is this one we are talking about here? but it seems a bit slow and I do not think it can be used for autoguiding, but it can be used for capturing.
I have tried V4L2 CCD driver(sudo apt-get install indi-webcam) and that one does stream video, but it can stream or capture as far as I saw(played for less then 15 minutes), it is also detected in PHD2 and I think it can be used for autoguiding, it might be best at this moment but additional testing and reading needed.
I have tried Indi Webcem driver(sudo apt-get install libindi1), that one is not good for this purpose.
There should also be support for "libcamera" for raspberry pi. That one should be the best option, but clean new driver will have to be written, but I am not sure about progress as information is scarce, but there is Google coding camp this summer for libcamera, so that is a good news. Libcamera should enable Raspberry Pi to plugin any sensor you want that has appropriate interface(MIPI CSI)