Welcome to INDI Community

No, I don't have a PPBA.

Read More...

Just found the log from the last crash when imaging so adding that - last result is a camera capture:

File Attachment:

File Name: log_20-32-26.txt
File Size: 226 KB

<code>[2022-03-26T00:33:03.487 GMT INFO ][ org.kde.kstars.ekos.capture] - "Capturing 60.000-second image..."
[2022-03-26T00:33:03.500 GMT INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 550D : "[INFO] Starting 60 seconds exposure. "</code>

with RAM report looking like the crash appears at the end of the exposure:
<code>2022-03-26 00:34:01, Temp=25.3ºC. RAM available: 2.4GB; RAM used: 1.1GB.
2022-03-26 00:34:02, Temp=25.8ºC. RAM available: 2.5GB; RAM used: 1.1GB.
2022-03-26 00:34:03, Temp=26.2ºC. RAM available: 2.5GB; RAM used: 1.0GB.
2022-03-26 00:34:04, Temp=25.3ºC. RAM available: 2.5GB; RAM used: 1.0GB.
2022-03-26 00:34:05, Temp=25.8ºC. RAM available: 3.1GB; RAM used: 417MB.
2022-03-26 00:34:06, Temp=26.2ºC. RAM available: 3.1GB; RAM used: 442MB.
2022-03-26 00:34:07, Temp=25.3ºC. RAM available: 3.1GB; RAM used: 429MB.</code>
Hope this helps?

Read More...

I started an SGL thread about this topic and due to less daylight, etc, haven't progressed with it. Thinking it might be Astroberry related, posted the following content on Astroberry Github , and suggestion was to post here.

In short, running RPi4 4GB with astroberry installed on 128GB micro SD. I use a combination of Anydesk and VNC to access the RPi which is mounted on my mount, controlling guiding, tracking and DSLR.

Several imaging sessions have been interrupted by kstars closing shortly after closing my connection to the RPi. In effort to debug, I'd saved out the log files but didn't get round to really getting into them. Read a couple of places about memory leaks and wrote shell script to output ALL memory parameters out to text file whilst running anything else on the RPi.

As the nights are short (and weather of late not the best!), I have even used the simulator to duplicate the crashing, with log files being saved as verbose, etc.
I have enabled the FITS Limited Resouces Mode and disabled FITS viewer as had read about this possibly causing issues.

My most recent is the most detail I've had on the issue - started the imaging at ~12:30 and closed connections ~18:00. Log file ends about 30min later with:

[2022-05-16T18:28:14.871 BST DEBG ][           org.kde.kstars.indi] - Telescope Simulator : "[SCOPE] Current RA:  3:05:52 Current DEC: 90:00:00 "
[2022-05-16T18:28:14.892 BST INFO ][   org.kde.kstars.ekos.capture] - "Capturing 2.500-second Luminance image..."

At this point, the simulator has 'captured' 7652x 2.5sec exposures, just using the default settings in EKOS:

My shell script outputs memory info just before starting:

2022-05-16 12:23:54; Temp=39.4ºC. RAM 'Used': 399MB (10.5%); RAM 'Free': 2.4GB (64.7%); RAM 'Available': 3.1GB (84.4%); RAM used in Shared & Buffer: 26.0%. Swap used: 0.0%. µSD @/dev/root uses 20,178,276kB.
2022-05-16 12:23:55; Temp=39.9ºC. RAM 'Used': 399MB (10.5%); RAM 'Free': 2.4GB (64.7%); RAM 'Available': 3.1GB (84.6%); RAM used in Shared & Buffer: 26.0%. Swap used: 0.0%. µSD @/dev/root uses 20,178,276kB.

Here's memory stats just before and after crash time:

2022-05-16 18:28:02; Temp=42.3ºC. RAM 'Used': 1.2GB (31.3%); RAM 'Free': 114MB ( 3.0%); RAM 'Available': 2.4GB (63.8%); RAM used in Shared & Buffer: 66.4%. Swap used:100.0%. µSD @/dev/root uses 39,596,736kB.
2022-05-16 18:28:03; Temp=43.3ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 112MB ( 3.0%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.5%. Swap used:100.0%. µSD @/dev/root uses 39,596,748kB.
2022-05-16 18:28:05; Temp=41.3ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 112MB ( 3.0%); RAM 'Available': 2.4GB (63.9%); RAM used in Shared & Buffer: 66.5%. Swap used:100.0%. µSD @/dev/root uses 39,596,484kB.
2022-05-16 18:28:06; Temp=42.8ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 109MB ( 2.9%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.6%. Swap used:100.0%. µSD @/dev/root uses 39,599,312kB.
2022-05-16 18:28:08; Temp=41.8ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 110MB ( 2.9%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.6%. Swap used:100.0%. µSD @/dev/root uses 39,599,312kB.
2022-05-16 18:28:09; Temp=43.3ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 106MB ( 2.8%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.6%. Swap used:100.0%. µSD @/dev/root uses 39,601,876kB.
2022-05-16 18:28:10; Temp=41.8ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 106MB ( 2.8%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.6%. Swap used:100.0%. µSD @/dev/root uses 39,601,884kB.
2022-05-16 18:28:12; Temp=43.3ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 105MB ( 2.8%); RAM 'Available': 2.4GB (63.9%); RAM used in Shared & Buffer: 66.7%. Swap used:100.0%. µSD @/dev/root uses 39,604,444kB.
2022-05-16 18:28:13; Temp=43.3ºC. RAM 'Used': 1.2GB (31.4%); RAM 'Free': 104MB ( 2.8%); RAM 'Available': 2.4GB (64.0%); RAM used in Shared & Buffer: 66.7%. Swap used:100.0%. µSD @/dev/root uses 39,604,448kB.
2022-05-16 18:28:15; Temp=42.8ºC. RAM 'Used': 1.0GB (24.4%); RAM 'Free': 489MB (17.1%); RAM 'Available': 3.1GB (83.1%); RAM used in Shared & Buffer: 66.8%. Swap used:98.8%. µSD @/dev/root uses 39,607,008kB.
2022-05-16 18:28:16; Temp=42.3ºC. RAM 'Used': 459MB (12.1%); RAM 'Free': 847MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,008kB.
2022-05-16 18:28:18; Temp=42.8ºC. RAM 'Used': 460MB (12.2%); RAM 'Free': 846MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,008kB.
2022-05-16 18:28:19; Temp=42.3ºC. RAM 'Used': 461MB (12.2%); RAM 'Free': 847MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,012kB.
2022-05-16 18:28:20; Temp=42.3ºC. RAM 'Used': 459MB (12.1%); RAM 'Free': 848MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,012kB.
2022-05-16 18:28:22; Temp=41.8ºC. RAM 'Used': 459MB (12.1%); RAM 'Free': 848MB (22.4%); RAM 'Available': 3.1GB (83.7%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,024kB.
2022-05-16 18:28:23; Temp=42.3ºC. RAM 'Used': 459MB (12.1%); RAM 'Free': 848MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,024kB.
2022-05-16 18:28:25; Temp=41.8ºC. RAM 'Used': 458MB (12.1%); RAM 'Free': 848MB (22.4%); RAM 'Available': 3.1GB (83.8%); RAM used in Shared & Buffer: 65.7%. Swap used:98.8%. µSD @/dev/root uses 39,607,024kB.

As seen, there's virtually no memory available at the time of crash, and 100% swap used. The above results have been generated using "free" in a script outputting to txt every second. I can share if needed, but attach the log file and full output of this script in hopes that it may lead to a solution?
I'm running it again without additional things going on (had been running Conky on the RPi, but disabled it for now).

File Attachment:

File Name: log_12-24-22.txt
File Size: 6,945 KB

File Attachment:

File Name: SystemLog.txt
File Size: 11,214 KB

I do have to setup mount and so on to test with it as Radek has suggested on github, but wondered if I can start the ball rolling anyway by posting and running simulators again without anything else going on.

Read More...

Thanks!

Read More...

Next version in about ~10 days.

Read More...

After a bit more fiddling I believe the issue may stem from my Pocket Power Box Adv Gen2.

If I unplug PPBA from the Pi with it turned off and then plug everything directly into the Pi and boot up....I can start indi servies which is able to detect everything just fine.
I have auto-connect turned off. At this point, I can plug my PPBA back into the Pi and the other gear back into the PPBA. Then I can go through and connect each piece of gear within the indi control panel.

However, if I stop indi services and then start them up again, the ASI120mm-mini no longer shows up again.

Jasem, I will check when I get back home tonight.

Thanks, Max! I will try your solution as well. Do you have PPB too?

Read More...

I have the same issue and installed the TestFlight version for the time being.
Question: when the new version will be released?

Thanks

Read More...

Odd, lsusb shows it as detected? or SM Dashbaord -> Hardware page?

Read More...

It should work for guiding.

Read More...

see my thread - www.indilib.org/forum/stellarmate/11638-...-working-solved.html

Read More...

Thanks, I will update the scripts accordingly. For now run this command first:

sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev

Then run update_indi_drivers

Read More...

Hi Rob,
Yes. I used Jasem's Stable INDI PPA. I solved the problem by reinstalling Linux Mint.

Now I use Kubuntu 20.04.4 and everything works.

Thank you for the technical support ;-)

Tomas

Read More...

To spend beautiful moments with these sexy call girls you can call us anytime 24/7. You can also hire teenage or college girls if your taste is... Show more

I recently upgraded my Rpi4 to the 8GB version so I decided to give 64bit Stellarmate a try. No matter how I connect my 120mm-mini (the newer one with the USB-c)- Directly to the Rpi4, powered hub, or the ASI533 Hub,., indi doesn't see it.
It sees my ASI533 just fine as well as all my other gear.

My older Rpi4 2GB version running the 32bit version of Stellarmate sees it just fine. Same cables.

Has anyone else run into this with the 64bit version?

Read More...

Thanks for the quick reply!
I'm excited to try this new feature

I switched the StellarMate to beta, but saw no change.
So I ran the update_indi_core, which seemed to complete successfully.
However update_indi_drivers complains about not finding several LIBAV libraries...
Is this a bug in the script? Or, do I need to do something to setup the dev environment before running these?

Read More...

If you go to stellarmate.local:3000; you might have to turn on the beta channel but it's there. Other option is to go to the website and download it. I found the GUI version installs easier.

Read More...

Hi PDB,
thanks very much! That's it. I didn't look exactly enough.

Greetings,
Jörg!

Read More...

Get Connected!

File Attachment:

File Attachment:

File Attachment: