Didn't mean to suggest that your issue is power related....it was a side note about long term stability. Looking at the log, it seems clear that a memory stomp is occurring, and it's bad enough to corrupt the stack. It's not clear whether memory has been exhausted, or it's just a memory bug that your configuration/setup has tickled. If you are getting 70 subs, what about trying a test where you setup for 2 sets of 50 subs. Does that run clean? If it does, it will give a hint that memory exhaustion is occurring. You probably should plan to have a terminal window up as you're running, and run the memory free command a few times as the job is running to see how memory is being consumed. That will give you a good clue as to what's going on. I would do this for both tests (2x50, and the 70 crash). You want to catch this just prior to the crash in the 2nd case, and then after the crash. The output will be along the lines of:

$ free -h
total used free shared buff/cache available
Mem: 3.5Gi 654Mi 2.0Gi 170Mi 921Mi 2.7Gi
Swap: 2.0Gi 0B 2.0Gi

Hmmm that would be a good idea, with 2 sets. I am gonna try it. I can’t believe that there is no enough memory to run the EKOS, cause I have already the memory graph in the menu bar and I’m struggling to see even a slight pick there.
But surely I am gonna keep that in mind to test it!

Thanks!


Sent from my iPhone using Tapatalk

After you run your tests, if you are still experiencing the crash, I recommend creating a support ticket on the SM OS site. Jasem will respond and help to resolve. Having the full logs will be helpful. Good luck, Doug

Also please try to update StellarMate to all latest packages and then restart it. A memory issue was resolved recently.

I’ve done it yesterday, before my session. I’ll redo it tonight.


Sent from my iPad using Tapatalk

Just to be clear....Don't use the package updater app on the desktop (doesn't work). Use this command in a terminal instead:

sudo apt-get update && sudo apt-get -y dist-upgrade

If running this command brings a bunch of packages, it might be advisable to reboot the PI before running your test.....

Never worked for me either..

Every time I boot my RPI I always run the update commands. I've done the same today, nothing new to install.

I load PHD2 and run the guiding as usual. Then I load Ekos and setting up my sequence and everything goes smoothly.

Today I've noticed something and I do not know if this is right. After starting my sequence I took a glimpse back in PHD2 and saw this message. The guiding was going on but the message was there. So I've done 2 more times my process from the top (even restarting RPI). This message appears as soon as I load Ekos.

ok, we're getting to a different topic from the crash, but here's a tip about PHD2. Assuming your PHD2 profile is setup correctly, then start the PHD2 app but DON'T connect. Just bring up PHD2 on the desktop. Then, assuming your Ekos profile is correct for PHD2, go into the guide tab and push the connect button. That should connect Ekos to PHD2, and PHD2 to the mount and camera. Sometimes the state machine between the two (Ekos & PHD2) can get confused. If this happens, just disconnect from the Ekos side, and reconnect again via the guide tab connect button. Once you are connected, it should stay connected. IMO, you probably should get into the habit of disconnecting and reconnecting from the Ekos guide tab (not the PHD2 side) if you don't already. I've seen it work fine connecting from PHD2 to Ekos, but I experience more problems with interface states when done that way.

I tried to reproduce the crash using different method but I failed to. Please open a ticket at StellarMate support so we can follow up with this.

Hello,

In another thread, using WIFI 2.4G and USB 3.0 produces unstable USB3 performance. Change your wireless to 5G and retest your configuration. Any hardware driver that is unstable will crash any application using it.

Good to know that!

I do believe that something is going on with USB3 ports. Yesterday everything was running ok, again until 60-70 subs and then suddenly I wasn't able to connect to the system (wifi wrong pass etc.). As soon as I pulled out the camera from the USB3 port, the system worked again correctly.
Surely I have to take a closer look to locate the issue. It may be power related (stated earlier above). I'm gonna try with a power source (no power banks) and powered USB Hub and I'll report back.

The OP started this chase with a memory crash. If you now think this is a USB3 issue, please see this post on RF interference (2.4Ghz wireless only):
www.indilib.org/forum/general/6576-pi4-u...erference.html#59667

The stated symptoms don't matchup very well, but there could be multiple issues in play.