Ok, here's where I am right now. I found a 1.3.0 image and made a fresh drive with it. Installed it, but with out any updates it would not recognize my miniCAM5. After running the update app it now recognizes my camera but has the same issues as 1.4.6. It will work in manual but AUTO sets the power to 1.18% and nothing ever happens from here. Can't set a target temperature so the camera is useless under StellarMate. Trying to work out something with my laptop so I can at least image if we ever get some clear weather. Camera works fine under ASCOM. Any help to fix StellarMate would be greatly appreciated.

Regards,
Mike

This is a QHYSDK issue. INDI driver on StellarMate simply asks the driver to sets the temperature. If you can turn on debug logging (check my signature for how), then attach the log here, then we can ask QHY to look into it.

Thanks Jasem. The log file attached to message #47570 was done following your directions. Will it work for troubleshooting?

Regards,
Mike

Ok we need to send a very concise report to QHY.

Problem: Describe the issue exactly.
Expected Result: what is the expected behavior.
Log: Attach log with the issue.

Hello,

Same problem as yours.

Lastly, I observe problems on the regulation of the temperature of my QHY183M.

The behavior is random, the automatic regulation works, the next day not.
Ditto with manual control, it works for two or three inputs, after the command does not seem to reach the camera.

I would post the logs for the next test.

Laptop or PI, with two QHY cameras (183M and 5LII-M).

Hi,

there is indeed some testing required -- by QHY. I'ts an issue of their SDK.

With the latest sources (QHY SDK 6.0.5) and my QHY163M the regulation stops after a while and the PWM value get stuck.

I rebuilt the driver with SDK 6.0.1. (had to comment out a new feature). Now it works, but its unstable: the PWM value jumps between a few percent and 90%. Because at least the 163's have a lot of power supply induced noise that's no solution.

I'll test which version is stable and send a report.

Update:
SDK 5.1.0 which can be found in the indi source package 1.8.0 seems to be the last version with stable temperature control.


Regards Stefan

Jasem:

Sorry for the slow reply, busy work week.

Problem: Describe the issue exactly:

Using a MiniCAM5F with INDI you cannot pick a set point for temperature. Example: if you tell the system to use the target temperature of -10C it will not reach this set point. In fact the power is always set to 1.18% no mater what target temperature chosen, with cools down to about +10C.

Expected Result: what is the expected behavior:

The camera should cool to the expected temperature as long as the requested temperature is within the cameras parameters.

Log: Attach log with the issue.

Logs attached. Please let me know if I can give you any additional information.

Regards,
Mike

Hello,

I have the same problem with my QHY 183C. Into the Control Panel it is not possible to setup a temperature to focus. Into the Capture tab, the temperature reached is that of the control panel. But I can't change it.

It seems that 3.4.0 version of Kstars solves well this issue.

No luck, I'm still having the same issue with my MiniCAM5F. I have reached out to QHY as I would like this fixed...

Regards,
Mike

I just updated to latest Kstars and INDI bits for QHY. With my QHY163m cooling is improved and stabilises within a couple of minutes. When I get some time, I'll try my older QHY9 as well. Also no issues recognising my QHY5L-II-M either.

jmh

This is my last experience with Kstars 3.4.0 and QHY 183C.
- Cooling: The temperature is twisting between -8° and -12° when setup is -10° with 0.1° tolerance. Normal ? Sometimes the cooler disconnects and it is not possible to connect it again. I have to close and open a new Ekos session.
- In looping frame mode, randomly Ekos freezes. The Indi server crashes with return to the desktop immediate.
- Issue when the capture must be saved on the HD, the directory that I setup, is modified. The initial directory is /mnt/DATA/Ekos_capture/20200303 into the Capture tab and Directory field.

[2020-03-03T23:48:59.116 CET CRIT ][ org.kde.kstars.indi] - ISD:CCD Error: Unable to open "/mnt/0C2F541F66995919/Test/Light/Light_001.fits"
[2020-03-03T23:48:59.116 CET INFO ][ org.kde.kstars.ekos.capture] - "Échec dans l'enregistrement du fichier vers /mnt/0C2F541F66995919/Test/Light/Light"
[2020-03-03T23:48:59.117 CET INFO ][ org.kde.kstars.ekos.capture] - "CCD capture aborted"