×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Can't get "Amp Glow" Option in EKOS for QHY163m

  • Posts: 24
  • Thank you received: 1
Just tried with the latest git repo (self-compiled). Still the Same result:


2 years 2 months ago #79054
Attachments:

Please Log in or Create an account to join the conversation.

Ok last time I talked with QHY regarding this issue, I was told the option was removed from the SDK. You may contact them about this.
2 years 2 months ago #79057

Please Log in or Create an account to join the conversation.

  • Posts: 24
  • Thank you received: 1
I don't understand. Why was it removed? Out of error?
2 years 2 months ago #79058

Please Log in or Create an account to join the conversation.

No, this is the official response:

We have set some camera to force anti-ampv enabled. So these camera's amp glow setting is removed. For these camera it will automatically enable the ampv control.
Last edit: 2 years 2 months ago by Jasem Mutlaq.
2 years 2 months ago #79066

Please Log in or Create an account to join the conversation.

  • Posts: 24
  • Thank you received: 1
The official response from QHYCCD:

In fact, we have automatically turned on the amplifier glow controller in the firmware and set it to be turned on by default. So the current image is the effect of turning on the amplifier glow controller. However, due to the limitation of the CMOS chip, this camera cannot completely avoid the effects of amplifier glow.Most of our new generation CMOS cameras have achieved zero glow, such as QHY268 and QHY600
Last edit: 2 years 2 months ago by RononDex.
2 years 2 months ago #79083

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 23
Ok for the new cameras equipped with new firmware, but the ones purchased previously???
2 years 2 months ago #79084

Please Log in or Create an account to join the conversation.

  • Posts: 109
  • Thank you received: 8
I can't be really sure because I don't know this exact model, but all qhy cameras don't have a resident firmware fixed in the hardware.

What happens is the firmware included in the driver installation gets loaded inside the camera every time it's powered on. So you only need to make sure you have an up to date version of the indi driver to have the latest firmware.

Please anybody correct me if I'm wrong.
2 years 2 months ago #79109

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 23
I hope that you wrote is right.
At this time the repository does not have packages updated to latest version, for 32bit systems.
There are updates for the 64bit

libqhy_21.10.26-stable~202111111341_armhf.deb 2021-11-11 13:42
libqhy_21.10.26-stable~202112302141_arm64.deb 2021-12-30 21:42
2 years 2 months ago #79113

Please Log in or Create an account to join the conversation.

x86 32bit was discontinued long ago. Only 64bit and armhf/arm64 is supported.
2 years 2 months ago #79114

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 23
I know, i use an Raspberry system based on raspbian os at 32bit. There is no way to migrate the current system to the new 64bit, without reinstall all the stuffs?
2 years 2 months ago #79115

Please Log in or Create an account to join the conversation.

This is on StellarMate? stable packages would be released next week.
2 years 2 months ago #79116

Please Log in or Create an account to join the conversation.

  • Posts: 24
  • Thank you received: 1
I can only recommend to create a small .sh script with everything you do to install the system (and copy all your config files to the correct location, etc).

That way you only change your settings one, define it in your shell script (which you can have on github) and a reinstall will be fast and everything will be setup again.

Kind of like I did here: github.com/RononDex/dotfiles/blob/master/AstroPi-README.md

 
2 years 2 months ago #79117

Please Log in or Create an account to join the conversation.

Time to create page: 0.567 seconds