one more tidbit of info:
only way H ave found to avoid the crash is to disable auto connect in the profile, and start the devices one at a time.

- Mike

Read More...

(continued from previous post from the RPI 4)

So the suspicious issue: in my .indi directory there are 2 different devices:
-rw-r--r-- 1 astro astro 13 Nov 11 13:10 'ZWO ASI290MM Mini_config.xml'
-rw-r--r-- 1 astro astro 5855 Nov 11 12:50 'ZWO ASI290MM Mini_config.xml.default'
-rw-r--r-- 1 astro astro 6649 Nov 11 13:35 'ZWO CCD ASI290MM Mini_config.xml'
-rw-r--r-- 1 astro astro 6060 Nov 11 10:31 'ZWO CCD ASI290MM Mini_config.xml.default'

Notice the short file length on the first one listed - I believe that is what was being used in the crashing scenario.

I was able to get past the crash by removing the 290MM camera from the config, and then adding it back in as a ZWO CCD device. (instead of ZWO Camera_1)

Included at the end of this post is the gdb output of the crash (captured before I isolated the issue to the ZWO device) that seems to show the same issue that Dan was running into..
(BTW: I have now installed the ekosdebugger application, so if I run into the issue again I will capture data by using it...)
(gdb) run
Starting program: /usr/bin/kstars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7feda7ec00 (LWP 1645)]
[New Thread 0x7fe7ffec00 (LWP 1646)]
[Thread 0x7fe7ffec00 (LWP 1646) exited]
[New Thread 0x7fe7ffec00 (LWP 1647)]
[New Thread 0x7fe77eec00 (LWP 1648)]
[Thread 0x7fe7ffec00 (LWP 1647) exited]
[Thread 0x7fe77eec00 (LWP 1648) exited]
[New Thread 0x7fe77eec00 (LWP 1649)]
[New Thread 0x7fe7ffec00 (LWP 1650)]
[Thread 0x7fe77eec00 (LWP 1649) exited]
[Thread 0x7fe7ffec00 (LWP 1650) exited]
[New Thread 0x7fe7ffec00 (LWP 1651)]
[New Thread 0x7fe77eec00 (LWP 1652)]
[Thread 0x7fe7ffec00 (LWP 1651) exited]
[Thread 0x7fe77eec00 (LWP 1652) exited]
Call to writableLocation without an application-based location.
[New Thread 0x7fe77eec00 (LWP 1653)]
[New Thread 0x7fe6f31c00 (LWP 1654)]
[New Thread 0x7fdfffec00 (LWP 1655)]
[New Thread 0x7fcfffec00 (LWP 1656)]
[New Thread 0x7fd7ffec00 (LWP 1657)]
[New Thread 0x7fe7ffec00 (LWP 1658)]
[New Thread 0x7fcdfeec00 (LWP 1659)]
[New Thread 0x7fcd7dec00 (LWP 1660)]
[New Thread 0x7fccfcec00 (LWP 1661)]
[New Thread 0x7fb94eec00 (LWP 1662)]
[New Thread 0x7fb8cdec00 (LWP 1663)]
[New Thread 0x7fa3ffec00 (LWP 1664)]
[New Thread 0x7fa37eec00 (LWP 1665)]
[New Thread 0x7fa2fdec00 (LWP 1666)]
[Thread 0x7fb94eec00 (LWP 1662) exited]
[Thread 0x7fa37eec00 (LWP 1665) exited]
[Thread 0x7fa3ffec00 (LWP 1664) exited]
[Thread 0x7fa2fdec00 (LWP 1666) exited]
[Thread 0x7fb8cdec00 (LWP 1663) exited]
[Detaching after fork from child process 1685]
[Detaching after fork from child process 1686]
INDI::BaseClient::connectServer: creating new connection...
[New Thread 0x7fb8cdec00 (LWP 1694)]
Dispatch command error(-1): INDI: Could not find property DRIVER_INFO in ZWO CCD ASI290MM Mini
<setTextVector device="ZWO CCD ASI290MM Mini" name="DRIVER_INFO" state="Idle" timeout="60" timestamp="2023-11-11T18:36:09">
<oneText name="DRIVER_NAME">
ZWO CCD
</oneText>
<oneText name="DRIVER_EXEC">
indi_asi_ccd
</oneText>
<oneText name="DRIVER_VERSION">
2.3
</oneText>
<oneText name="DRIVER_INTERFACE">
6
</oneText>
</setTextVector>
No ISwitch 'FLIP' in iOptron CEM70.ON_COORD_SET
CCD_CAPTURE_FORMAT: defSwitchVector with no valid members
Dispatch command error(-1): INDI: Could not find property CCD_TEMPERATURE in ZWO CCD ASI290MM Mini
<setNumberVector device="ZWO CCD ASI290MM Mini" name="CCD_TEMPERATURE" state="Idle" timeout="60" timestamp="2023-11-11T18:36:10">
<oneNumber name="CCD_TEMPERATURE_VALUE">
19.300000000000000711
</oneNumber>
</setNumberVector>
Dispatch command error(-1): INDI: Could not find property CCD_CAPTURE_FORMAT in ZWO CCD ASI290MM Mini
<setSwitchVector device="ZWO CCD ASI290MM Mini" name="CCD_CAPTURE_FORMAT" state="Idle" timeout="60" timestamp="2023-11-11T18:36:10">
<oneSwitch name="ASI_IMG_RAW8">
Off
</oneSwitch>
<oneSwitch name="ASI_IMG_RAW16">
On
</oneSwitch>
</setSwitchVector>
[New Thread 0x7fa2fdec00 (LWP 1704)]
INDI::BaseClient::connectServer: creating new connection...
[New Thread 0x7fa3ffec00 (LWP 1705)]

Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x0000005555ae4f30 in ISD::CameraChip::getISOList (this=0x0) at /home/astro/kstars/kstars/indi/indicamerachip.cpp:514
514 auto isoProp = m_Camera->getSwitch("CCD_ISO");
(gdb)

Read More...

Raspberry Pi 5 incoming...

I ran into the exact same crash from the ekosdebugger but with a different configuration on a clean install of Build 202311-11T03:03:56Z Version 3.6.8 Beta.
(I will post output that I captured in the next posting...)
A common item is seen early in his first posting:
Dan had:
Dispatch command error(-1): INDI: Could not find property DRIVER_INFO in Canon DSLR EOS M50
<setTextVector device="Canon DSLR EOS M50" name="DRIVER_INFO" state="Idle" timeout="60" timestamp="2023-11-03T22:29:44">

I get the identical message except with "ZWO CCD ASI290MM Mini".

Read More...

I am just integrating the QHY 268M into my setup - too many clouds to try it outside so far.
I notice that when I use 3x3 binning on the image capture, the fits viewer still indicates that it is a 16-bit image.
I know that the plate-solver likes to use binning to simplify the problem, but binning (at 16 bits) might lead to problems.

Is your 268C image showing up in the FITS viewer 16 bits?

Read More...

Wow - this sounds like fun. I will try it out (in the 1 image mode first), and soon be on the market for more equipment!

Has this feature been added to the 'official' ekos repository? (Are there plans to?). If so I would recommend adding this as an option (pre-job, pre-capture, post-capture, post-job?) to keep maximum flexibility.
-Mike

Read More...

So what solving method do you suggest for me? My rpi4 at the scope running astroberry with kstars 3.4.x does it all currently with only an external computer (or iPad) necessary to setup the schedule and polar align. The Indi platesolve works well in this scenario. I assumed the updated solver would also behave well in this use case, but from the last post it sounds like a laptop/ external computer is recommended. - or did I miss something?

Read More...

I was just wondering if an external (USB) wi-fi dongle would it still encounter the same interference issues?

I am about to try it out (have been using wired ethernet with great success) - so I will find out on my own...

With this info about interference, I may put it on a USB extension which will get it away from the USB 3.0 hub too..

Read More...

Since the built in wifi is degraded by the heatsink/ case I am using, external Wifi sounds like a good idea.

According to the adafruit website : "Look for a WiFi adapter that supports the RTL8192cu chipset the latest Raspbian distributions both have support for this built-in."

I just ordered this: www.adafruit.com/product/1030

I will update with how easy it is to use (I hope) soon after it arrives...

Read More...

FYI - I just had this same issue:

Brand new RPI 3+
Brand new SD card image
Updated/ upgraded and then got the 404 error page on the desktop

Tried the above command and it ended with:
Setting up indi-sbig (2.1-3) xxx
Processing triggers for ...
...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
Errors were encountered while processing:
libraspberrypi0
libraspberrypi-doc
libraspberrypi-bin
libraspberrypi-doc
rpi-eeprom

did a restart and the web based interface worked... just like jdain said it would!

Thanks for asking/ solving this issue so quickly...

Read More...