×

INDI Library v1.7.6 Released. (27 Feb 2019)

First release of 2019 comes with quite a few new drivers across the board along with significant performance improvements to INDI camera and live streaming performance. Many drivers received significant updates to improve performance & stability, while a few were re-written from scratch to be in line with INDI standards. Here are some of the highlights:

Atik 383L+ on raspi crashes

  • Posts: 99
  • Thank you received: 38

Atik 383L+ on raspi crashes was created by ChrisRowland

I tried my Atik 383L+ on my raspi and I get a crash when I try to set the bin size or start an exposure.
This is what happens setting the bin values:

[2019-04-15T13:44:47.923 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisBin 101 2 2 "
[2019-04-15T13:44:47.924 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisBin Done "
[2019-04-15T13:44:47.927 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-04-15T12:44:47: Driver indi_atik_ccd: stderr EOF"
[2019-04-15T13:44:47.928 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 5047 died"
[2019-04-15T13:44:47.928 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-04-15T12:44:47: Driver indi_atik_ccd: restart #1"

And this is what happens starting an exposure:

[2019-04-15T13:49:41.412 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisStartExposure 101 1.000000 "
[2019-04-15T13:49:41.413 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] Start Exposure: 1 1.00ms (0) "
[2019-04-15T13:49:41.414 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisStartExposure Done: 0 "
[2019-04-15T13:49:41.961 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisImageReady 101 "
[2019-04-15T13:49:41.961 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisImageReady Done: False "
[2019-04-15T13:49:41.961 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisCameraState 101 "
[2019-04-15T13:49:41.962 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisCameraState Done: 1 "
[2019-04-15T13:49:41.962 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisExposureTimeRemaining 101 "
[2019-04-15T13:49:41.962 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] ArtemisExposureTimeRemaining Done: 0.999000 "
[2019-04-15T13:49:41.967 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] Toggle Debug Level -- Driver Debug "
[2019-04-15T13:49:41.967 BST DEBG ][ org.kde.kstars.indi] - Atik 383L : "[DEBUG] Toggle Logging Level -- Driver Debug "
[2019-04-15T13:49:41.970 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 8960 died"
[2019-04-15T13:49:41.970 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-04-15T12:49:41: Driver indi_atik_ccd: stderr EOF"
[2019-04-15T13:49:41.971 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-04-15T12:49:41: Driver indi_atik_ccd: restart #1"
[2019-04-15T13:49:41.971 BST DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-04-15T12:49:41: Driver indi_atik_ccd: pid=10067 rfd=5 wfd=19 efd=20"

I suspect this has failed inside the binary library.

Some other things, there is no indication of the CCD temperature, even though this is available from the camera and there is a message saying that Abort Exposure isn't supported, even though it is in the camera and driver.

I may have a go at looking at this, I wrote the original Atik ASCOM driver many years ago. They took it in house subsequently but some of this is still vaguely familiar.

I've attached the full log file.

Chris

File Attachment:

File Name: log_13-43-00.txt
File Size:143 KB
4 days 13 hours ago #37790
Attachments:

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

  • Posts: 99
  • Thank you received: 38

Replied by ChrisRowland on topic Atik 383L+ on raspi crashes

Got it going. I noticed that the cooler information wasn't present so I compiled and installed from the sources so I could debug. And all it needed was compiling and installing.

I'm not sure exactly what version I had installed, are the 3rdparty drivers installed as part of the 1.7.6 install or could it have been even earlier?
4 days 10 hours ago #37808

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

Replied by knro on topic Atik 383L+ on raspi crashes

I asked Atik to look into it. Meanwhile, do you think you can get a backtrace?
gdb -ex "set follow-fork-mode child" -ex run --args indiserver -v indi_atik_ccd indi_simulator_telescope

In Ekos, create a new profile, turn off Auto Connect and add Telescope Simulator + Atik CCD. Set mode to remote and leave it to localhost. In Logs, make sure to select Verbose Logging to File, check INDI + CCD. Click Start then in INDI Control Panel --> Atik CCD --> Options, make sure "Driver Debug" is checked. Then go back to Main Control Panel and press "Connect". Check the terminal to see if the driver crashed, if it did, type backtrace and paste the trace here. Also attach the KStars log file.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 days 14 hours ago #37847

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

  • Posts: 99
  • Thank you received: 38

Replied by ChrisRowland on topic Atik 383L+ on raspi crashes

Thank you for the reply Jasem. It looks as if I was using some old and unknown version of the driver.
As I said in my second message I got it fixed by recompiling but it also survived an install/update following the instructions in the Atik driver details on the web site.
I have no idea what versions I was using so reverting to them will be tricky.

Incidentally would it be worth having a way to identify components accurately such as by adding a day number to the version data?

Sorry to put you to this work.

Chris
3 days 7 hours ago #37878

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

Time to create page: 0.431 seconds