×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Omegon Pro / Touptek drivers

  • 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.
1 year 4 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.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 4 months ago #72981

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

  • Posts: 205
  • Thank you received: 17
Can I do that on my Astroberry setup too? Cause probably will have the same issue too. Are there any instructions how to?
1 year 4 months ago #72986

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

  • Posts: 205
  • Thank you received: 17
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: 1 year 4 months ago by Euripides.
1 year 4 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.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You: Euripides
1 year 4 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?)
1 year 4 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.

  
1 year 4 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.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 4 months ago #73089

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

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

I let it run for a bit longer now and I get a lot of exposure time outs. I add the kstars log but to me there's not much more information in it. The odd thing is that when i only connect the guide camera and a telescope simulator and ccd simulator, there is no problem and everything is rock solid. But as soon as i connect my mount, a Celestron Evolution, with a serial connection through the hand controller I get the exposure time outs. It also happens when Ekos tries to download an exposure from my Canon DSLR. When I use the guide camera with Windows and ASCOM it is rock solid all the time. I really hope you can resolve this because I love using Ekos/kstars on Stellarmate a lot. I find it the most user friendly imaging acquisition suite out there but for now it's not a reliable solution for me. If there is anything I can do to help, don't hesitate to reach out. Thanks again for all your hard work for the community. 

File Attachment:

File Name: kstars-log...3-39.txt
File Size:30 KB
1 year 4 months ago #73094
Attachments:

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

  • Posts: 12
  • Thank you received: 3
Some additional information. I see the same behaviour in PHD2. When I connect my guide camera to PHD2 and the INDI Telescope Simulator, the guide camera keeps on taking exposure. When I change the mount to the INDI Celestron GPS driver, I get exposure time outs in PHD2. Exactly the same as with the internal guider of Ekos. So it seems to me there is some interference with the serial connection to the mount and the USB connection to the Touptek camera's. I had a discussion about this with a member of my astronomy club who has the exact same issue with his Omegon camera and his iOptron mount. I'm not sure of this is of any help but I hope it narrows it down a little
1 year 4 months ago #73095

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

So I ran this thus far for 20 minutes without a single time out. Altair for primary camera and Toupcam for guide camera.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 4 months ago #73100
Attachments:

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

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

Please see my previous message. When I use Toupcam Guide Camera via the Telescope Simulator I also have no exposure time outs. But as soon as I use real mount with a usb to serial connection through the Celestron hand controller I get the time outs. Same behaviour in PHD2 on Stellarmate
1 year 4 months ago #73101

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

Time to create page: 1.830 seconds