×

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

Bi-monthly release with minor bug fixes and improvements

Touptek Camera SDK Major Update

  • Posts: 22
  • Thank you received: 7
Is it possible / a good idea saving temperature and heater status in camera configuration?
Last edit: 1 year 1 month ago by Matteo.
1 year 1 month ago #90196
Attachments:

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

  • Posts: 114
  • Thank you received: 17
If to take image with short exposure (0.01 second) indiserver will instantly send about one hundred XML like this
<setNumberVector device="Toupcam ATR3CMOS26000KPA" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2023-02-11T12:42:15">
    <oneNumber name="CCD_EXPOSURE_VALUE">
0
    </oneNumber>
</setNumberVector>
I don't think this is good
PS: no such problem with long exposures
The following user(s) said Thank You: Jasem Mutlaq
1 year 1 month ago #90426

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

Good catch. Can you please report this in Touptek latest PR so they might take an action to resolve it?
1 year 1 month ago #90546

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

  • Posts: 114
  • Thank you received: 17
Hi, do you mean simply write this as comment for PR?
1 year 1 month ago #90547

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

Correct, or create an issue as well.
1 year 1 month ago #90548

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

  • Posts: 114
  • Thank you received: 17
Hm... I tried to reproduce this with EKos with no success. So it looks like the problem is only when I take shot from my client.
1 year 1 month ago #90577

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

  • Posts: 29
  • Thank you received: 3
Hi,

Update the recommendation for the best settings by the current version SDK.

Karas said he will later make a Python script that can run sensor analysis under LINUX. It can be used to validate this data set. And get finer discrete values. This data set can now be verified under linux using Pixinsight, and since I'm not a PI expert, if anyone is interested they can follow this tutorial: www.lightvortexastronomy.com/measuring-your-camera-sensor- parameters-automatically-with-pixinsight.html

The current Mode0 recommended settings are as follows.

HFW = On
LCG = On (By threshold AUTO)
LN = On
Gain 177
OFFSET = 700

Reasons Why and How to select:

Slightly less than 1e/ADU to obtain the best sampling, one electron converts one ADU.

Consider a limit capacity of 60ke for 16bit, and a full well of no more than that amount of RMS after deducting the noise component is available.

Consider the loss of dynamic range and keep it above 14.

Consider the noise distribution characteristics, the histogram should be closer to the Gaussian distribution.

Consider pre-addition of voltage to make all histogram values greater than 0.



2023 Jan Toup Ascom Driver (Same file with INDI 3rd)


QHY268M
Last edit: 1 year 1 month ago by lanco.
1 year 1 month ago #90591
Attachments:

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

  • Posts: 174
  • Thank you received: 27
I recently updated my system and Touptek INDI driver seems to be changed dramatically:
- Now it takes offset between 1 and 31 only
- If does not show parameter for switching between high and low gains
- gain parameter does not switch between low and high gain as it used to be
Looks like now I am supposed to switch between low and high gain using INDI control panel.
Is this expected?
I much prefer the old way of doing things because i was able to switch between low and high gain just by using the gain value.
10 months 3 weeks ago #92684

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

  • Posts: 3
  • Thank you received: 0
I've also got the problem with offset being 31 max but I haven't tried gain adjustment yet
10 months 5 days ago #93003

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

  • Posts: 969
  • Thank you received: 94
Hi everyone
I have the Omegon veTEC571. Connecting using the omegonpro driver, I don't see the offset issue and all the other stuff works too. I wonder if the Omegon and other Touptek re-badged models really do use the same code?
The libraries seem different. Here are the listings built from NOU's scripts for the current stable:

steve@steve-desktop:/usr/lib/x86_64-linux-gnu$ ls -l libtoup*
lrwxrwxrwx 1 root root 16 abr 5 18:45 libtoupcam.so -> libtoupcam.so.53
lrwxrwxrwx 1 root root 22 abr 5 18:45 libtoupcam.so.53 -> libtoupcam.so.53.22376
-rw-r--r-- 1 root root 44632232 may 5 14:19 libtoupcam.so.53.22376

steve@steve-desktop:/usr/lib/x86_64-linux-gnu$ ls -l libomegon*
lrwxrwxrwx 1 root root 21 abr 5 18:44 libomegonprocam.so -> libomegonprocam.so.53
lrwxrwxrwx 1 root root 27 abr 5 18:44 libomegonprocam.so.53 -> libomegonprocam.so.53.22376
-rw-r--r-- 1 root root 21501992 may 5 14:19 libomegonprocam.so.53.22376

Can anyone confirm?
Cheers and clear skies,
Steve
Last edit: 10 months 4 days ago by alacant.
10 months 4 days ago #93006

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

  • Posts: 21
  • Thank you received: 2
For OpenSUSE tumbleweed using the later release of the RisingCam IMX571 (colour)

ls -l libtoup*
lrwxrwxrwx 1 root root 16 May 23 13:30 libtoupcam.so -> libtoupcam.so.53
lrwxrwxrwx 1 root root 22 May 11 16:20 libtoupcam.so.53 -> libtoupcam.so.53.22376
-rw-r--r-- 1 root root 44642257 May 11 16:18 libtoupcam.so.53.22376

ignore the dates as I was playing around with the RisingCam libs

My offset settings are greyed out completely
10 months 4 days ago #93007

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

  • Posts: 80
  • Thank you received: 4
with my vetec571M the maximum blacklevel is 31, with my vetec571C 256 is possible (my standard) in the INDI Control panel using the Toupcam driver. With the Omegonpro driver both cameras work with 256. It is still not possible to use the offset setting in the EKOS panel.

CS, Markus
9 months 3 weeks ago #93227

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

Time to create page: 1.647 seconds