×

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

Bi-monthly release with minor bug fixes and improvements

Omegon Pro / Touptek drivers

  • Posts: 12
  • Thank you received: 3
What Omegon camera's do you have? I have a Guide 2000M and have a lot of connection issues with it in INDI/Ekos. The camera works great with the ASCOM drivers but loses connection after some minutes in ekos. Sometimes it recovers, sometimes it doesn't. But it's not reliable at all. I tried so many things that I gave up on it. I really would love to make it work, because I love using Ekos-Kstars a lot.
2 years 8 months ago #72937

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

  • Posts: 401
  • Thank you received: 41
I have the Omegon 533 C for main and the Omegon 1200m for guide. I've tried both to connect them to PHD2 while are ON in Ekos but I had the same result "Unable to complete exposure, time out etc".

As soon as I disconnect the camera from indi tab, it works in PHD2.
2 years 8 months ago #72938

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

  • Posts: 12
  • Thank you received: 3
That's exactly the same with my guide camera. I get the exposure time-out message. Not only in PHD2 but also with the internal guider of Ekos. If the guide camera is the only device that's connected it works fine. But as soon as I connect my mount or when an image is being dowloaded from my dslr. I tried different usb-cables, powered hub, directly connected to a raspberry pi with Stellarmate and even ran Ekos on my Macbook Pro, everytime the same behavior
2 years 8 months ago #72939

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

I can confirm the issue with two camera (altair + toupcam). I'll look into it and see if it might be related to USB or something else.
2 years 8 months ago #72945

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

  • Posts: 12
  • Thank you received: 3
Thanks Jasem, Please let me know if you need more information on the issue. I can provide you with some logs but I already looked at them but couldn't find much info there except for the exposure time-out and that ekos tries to reconnect.
2 years 8 months ago #72967

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

I've spent a few hours on this. I see the same issue on my powerful PC, so it's not a USB issue at all. Something is broken in the Touptek library that causes then. Sometimes a frame times out without any reason. Even after I enabled "frame timeout notification" for touptek SDK, the timeout event wasn't triggered. Eventually, I had to introduce a custom timeout functionality and that appeared to did the trick. It's now on GIT.

Please test the nightlies later today and report back.
2 years 8 months ago #72981

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

  • Posts: 401
  • Thank you received: 41
Can I do that on my Astroberry setup too? Cause probably will have the same issue too. Are there any instructions how to?
2 years 8 months ago #72986

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

  • Posts: 401
  • Thank you received: 41
Jasem, I've just updated my Stellarmate copy to the latest stable and created a new simple profile (pic attached). As soon as I press start, the driver crashes. (In the meantime, it works in Astroberry copy).

That was the issue that you solved on the nightly?

This is from the debugger:

<code>2021-06-30T21:52:35: startup: /usr/bin/indiserver -r 0 -v indi_toupcam_ccd indi_manual_wheel indi_ioptronv3_telescope
[Attaching after Thread 0xb6ffa090 (LWP 2570) fork to child process 2580]
[Detaching after fork from parent process 2570]
2021-06-30T21:52:35: Driver indi_toupcam_ccd: pid=2580 rfd=3 wfd=6 efd=7
2021-06-30T21:52:35: Driver indi_manual_wheel: pid=2581 rfd=4 wfd=9 efd=10
2021-06-30T21:52:35: Driver indi_ioptronv3_telescope: pid=2582 rfd=5 wfd=12 efd=13
2021-06-30T21:52:35: listening to port 7624 on fd 8
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on GPS Simulator.TIME_UTC
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on Dome Simulator.DOME_PARK
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on Dome Simulator.DOME_SHUTTER
2021-06-30T21:52:36: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI3CCD22checkTemperatureTargetEv
2021-06-30T21:52:36: Driver indi_toupcam_ccd: stderr EOF
2021-06-30T21:52:36: Driver indi_toupcam_ccd: Terminated after #0 restarts.
Child process 2580 died
No stack.</code>


 
Last edit: 2 years 8 months ago by Euripides.
2 years 8 months ago #73003
Attachments:

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

The changes are in nightly, not stable. Also, you need to run: sudo apt-get -y dist-upgrade as well since the crash above is due to missing package.
The following user(s) said Thank You: Euripides
2 years 8 months ago #73013

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

  • Posts: 12
  • Thank you received: 3
Hi Jasem,

I ran some test on a freshly installed Stellarmate with the nightly builds. My Omegon 2000M Guide Camera seems to be stable now without the 'Exposure time out' warnings. But I have a problem now with the Canon DSLR driver which crashes everytime the INDI server tries to start it up. So I haven't been able to test the guide camera drop outs when I take an image with my Canon 650D. I have put the debugger log below. Maybe you can have a look at it.

Thanks a lot for all the work so far!

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New inferior 2 (process 2010)]
[Inferior 1 (process 2007) detached]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
process 2010 is executing new program: /usr/bin/indi_gphoto_ccd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xb4de9080 (LWP 2018)]
[Thread 0xb4de9080 (LWP 2018) exited]
[New Thread 0xb4de9080 (LWP 2023)]
[Thread 0xb4de9080 (LWP 2023) exited]
[New Thread 0xb4de9080 (LWP 2024)]
[Thread 0xb4de9080 (LWP 2024) exited]
[New Thread 0xb4de9080 (LWP 2025)]
[Thread 0xb4de9080 (LWP 2025) exited]
[New Thread 0xb4de9080 (LWP 2026)]
[New Thread 0xb43ff080 (LWP 2027)]

Thread 2.1 "indi_canon_ccd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4dea010 (LWP 2010)]
INDI::StreamManager::setStreamingExposureEnabled (this=0x0, enable=false) at ./libs/stream/streammanager.cpp:1283
#0 INDI::StreamManager::setStreamingExposureEnabled (this=0x0, enable=false) at ./libs/stream/streammanager.cpp:1283
#1 0x00416688 in GPhotoCCD::initProperties (this=0x47ce18) at ./gphoto_ccd.cpp:333
#2 0xb6e8f8fa in INDI::DefaultDevice::ISGetProperties (this=this@entry=0x47ce18, dev=dev@entry=0x0) at ./libs/indibase/defaultdevice.cpp:767
#3 0xb6e9ae4a in INDI::CCD::ISGetProperties (this=0x47ce18, dev=0x0) at ./libs/indibase/indiccd.cpp:457
#4 0x004167a4 in GPhotoCCD::ISGetProperties (this=0x47ce18, dev=0x0) at ./gphoto_ccd.cpp:361
#5 0xb6e8ee44 in ISGetProperties (dev=dev@entry=0x0) at ./libs/indibase/defaultdevice.cpp:57
#6 0xb6e7d060 in dispatch (root=0x467c80, msg=msg@entry=0xbeffef2c "") at ./indidriver.c:815
#7 0xb6e7e148 in clientMsgCB (fd=<optimized out>, arg=0x4781d0) at ./indidrivermain.c:84
#8 0xb6e7e49c in callCallback (rfdp=0xbefff76c) at ./eventloop.c:409
#9 oneLoop () at ./eventloop.c:501
#10 0xb6e7e5de in eventLoop () at ./eventloop.c:109
#11 0xb6e7ad92 in main (ac=0, av=<optimized out>) at ./indidrivermain.c:131
#12 0xb6635718 in __libc_start_main (main=0xbefff984, argc=-1233747968, argv=0xb6635718 <__libc_start_main+268>, init=<optimized out>, fini=0x42f72d <__libc_csu_fini>, rtld_fini=0xb6fde4c4 <_dl_fini>, stack_end=0xbefff984) at libc-start.c:308
#13 0x0041591c in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2 years 8 months ago #73085

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

  • Posts: 12
  • Thank you received: 3
Sorry Jasem,

I spoke to soon. After letting the guide camera run for a longer period. I get the exposure time outs again. The camera does recover though. See the screenshot below. If there is anything I can do to help, please let me know.

  
2 years 8 months ago #73087
Attachments:

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

Hmmm odd.. I actually let this go for 2 hours straight without a single guide exposure timeout.
2 years 8 months ago #73089

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

Time to create page: 0.764 seconds