×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Touptek Camera SDK Major Update

  • Posts: 22
  • Thank you received: 1

Hi,
therfore I reinstalled my Stellarmate OS I have done the update again via

update_indi_core
update_indi_drivers

The toupcam driver crashes again immediatly in kstars.

I typed in indiserver -v indi_toupcam_ccdindiserver

indiserver -v indi_toupcam_ccd
2023-01-06T14:28:46: startup: indiserver -v indi_toupcam_ccd
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23204 rfd=6 wfd=6 efd=7
2023-01-06T14:28:46: listening to port 7624 on fd 5
2023-01-06T14:28:46: Local server: listening on local domain at: @/tmp/indiserver
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #0
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23205 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #1
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23206 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: stderr EOF
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #2
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23207 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #3
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23208 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: stderr EOF
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #4
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23209 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #5
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23210 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #6
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23211 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #7
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23212 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #8
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23213 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: restart #9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: pid=23214 rfd=7 wfd=7 efd=9
2023-01-06T14:28:46: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:28:46: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:28:46: Driver indi_toupcam_ccd: Terminated after #10 restarts.

Afterwards I run the kstars debugger with the following log

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New inferior 2 (process 21436)]
[Inferior 1 (process 21433) detached]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
process 21436 is executing new program: /usr/bin/indi_toupcam_ccd
[Inferior 2 (process 21436) exited with code 0177]

2023-01-06T14:08:07: startup: /usr/bin/indiserver -r 0 -v indi_toupcam_ccd indi_simulator_telescope
[Attaching after Thread 0xb6ff7940 (LWP 21433) fork to child process 21436]
[Detaching after fork from parent process 21433]
2023-01-06T14:08:07: Driver indi_toupcam_ccd: pid=21436 rfd=6 wfd=6 efd=7
2023-01-06T14:08:07: Driver indi_simulator_telescope: pid=21437 rfd=8 wfd=8 efd=9
2023-01-06T14:08:07: listening to port 7624 on fd 5
2023-01-06T14:08:07: Local server: listening on local domain at: @/tmp/indiserver
2023-01-06T14:08:07: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2023-01-06T14:08:07: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2023-01-06T14:08:07: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2023-01-06T14:08:07: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2023-01-06T14:08:07: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
2023-01-06T14:08:07: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI13DefaultDevice18getDriverInterfaceEv
2023-01-06T14:08:07: Driver indi_toupcam_ccd: read: Connection reset by peer
2023-01-06T14:08:07: Driver indi_toupcam_ccd: Terminated after #0 restarts.
No stack.

What do you think?

Best Regards
Sven
1 year 3 months ago #89477

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

  • Posts: 21
  • Thank you received: 9

Replied by max on topic Touptek Camera SDK Major Update

Hi lanco,

my ATR3CMOS26000KMA reports flag high full well capability = 0. Do I need a firmware update to use this feature?

By the way... the driver library v53 is running well on my RPi4 8GB.

CS Max

Update: I had a bug in my first version... report is now true :)
Last edit: 1 year 3 months ago by max.
1 year 3 months ago #89516

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

  • Posts: 21
  • Thank you received: 9

Replied by max on topic Touptek Camera SDK Major Update

Hello,

I have worked on the implementation of the High Fullwell Mode.

You can find a first version under

github.com/42-max/indi-3rdparty/tree/Hig...ellDev/indi-toupbase

Some notes:
- this is work under progress.
- configuration will not be safed yet
- only the indi_toupcam_ccd driver is generated. The feature is not available for the OMEGON SDK.

First tests with the PIXINSIGHT Basic CCD Parameters Script gives the following results
- Gain 100
- LCG enabled
- ATR3CMOS26000KMA

see Folie1 for High Full Well Mode OFF and Folie2 for High Fullwell Mode ON

I am not quite sure if I made the flats, darks and biases for the pixinsight script correctly. The absoute values do not match with other measurements. I will contunue testing.
At least the fullwell capacity is much higer with the new setting ;)

CS Max
The following user(s) said Thank You: Jasem Mutlaq
1 year 3 months ago #89528
Attachments:

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

Is it possible to ask Touptek to release a fix for the x86_64 library? otherwise, we'd have to revert to an older library.
1 year 3 months ago #89538

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

  • Posts: 21
  • Thank you received: 9

Replied by max on topic Touptek Camera SDK Major Update

OK, I will contact Touptek and try to get a x86_64 environment running.
1 year 3 months ago #89539

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

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

I just contacted Karas again, who is in charge. And he said that the SDK fix will be released next Monday. He said he was sorry, this crash issue was noticed before, but he was busy recently, so he hasn't finished changing it yet. = =

Once the sdk fix is released. I will post here and update a new download link immediately.


Lanco
Best Regards
The following user(s) said Thank You: Jasem Mutlaq
Last edit: 1 year 3 months ago by lanco.
1 year 3 months ago #89540

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

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

A few days ago, I installed the latest auto-bulid mac version(https://binary-factory.kde.org/view/MacOS/job/KStars_Release_macos/) successfully, and found that the driver sdk is new. But there is no new readout mode switch button, I'm wondering whether this belongs to the problem of SDK or of INDI panel?

Lanco,
Best Regards
1 year 3 months ago #89541
Attachments:

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

  • Posts: 21
  • Thank you received: 9

Replied by max on topic Touptek Camera SDK Major Update

Hi Lanco,

the new mode has to be implemented in the INDI driver. This is almost done. I will make a pull request when I have tested my version with the new SDK.
Could you and maybe Karas have a look to my measurements with the pixinsight script in post #89528. I am not a camera expert. The absolute values that I measured with the pixinsight script are different from your measurements.... but at least the tendency between high fullwell mode on and off is visble.
What tools do you recommend beside Sharpcap to mesure fullwell capacity?

CS Max
1 year 3 months ago #89551

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

  • Posts: 29
  • Thank you received: 3
I only know the purely manual way to measure, currently only sharpcap is known to be able to fully automatic analysis of the sensor tool, I think you can ask the professionals in the indi forum or next door cloudynights. If you get any clues, also look forward to telling me.
1 year 3 months ago #89553

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

  • Posts: 239
  • Thank you received: 38
I am working with Karas at Touptek to test the SDK. We were working last night and hope to continue this evening.

Hopefully we will have it resolved very soon.

Thanks.
The following user(s) said Thank You: Jasem Mutlaq
1 year 3 months ago #89587

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

  • Posts: 12
  • Thank you received: 1
It's an ubuntu 20.04.5 LTS intel x64 system + INDI 2.0.0 version + Kstars nightly 3.6.3. It is working fine and here is the screenshot.

We will try on 22.04 later.

If there is anything that we do wrong, please let me know.
The following user(s) said Thank You: Jasem Mutlaq
1 year 3 months ago #89601
Attachments:

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

With Toupcam G3M178C, I still get a crash on x86_64 system.
1 year 3 months ago #89603

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

Time to create page: 0.835 seconds