ChrisRowland wrote: The earliest is NS+ HC 5.22 for gems and 5.24 for fork mounts. This is when Celestron implemented the command in their HCs.
Version 4.22 also has the hibernation function, I use it every night.
No problem, I continue to do it manually.
ChrisRowland wrote: I worked with the Celestron developers to arrange a set of RS232 ...
It's for the NexStar Plus HC only...
Only for Plus version? .. is not possible port also in non Plus version ? ( NexStar 4.22 )
hy wrote: I was wondering, for the folks with the memory leak--do you have the option "Single Preview Tab" checked? (I think you should have it checked).
You find that under the KStars options, then FITS, then it's a checkbox on that page.
I believe that KStars/fitsviewer would leak tabs if you had it unchecked (perhaps it should limit the number of tabs, I don't know if it does or doesn't).
Yes is checked and Fits viewer is disabled.
knro wrote: I would like to know how I can replicate this.. I took 500 images on StellarMate a couple of weeks ago and I couldn't detect any memory leak. Was HIPS overlay enabled? I'd like to replicate exact conditions.
Thanks knro, next time I create a log, HIPS is disabled.
I forgot to mention that they are all FITS image ( fits viewer is disabled ).
Lead_weight wrote: I have a 4GB RPi4 and the memory leak stops it too after about 4 hours of imaging. Happens every single time. I've since changed how I use KStars/EKOS. I used to run it all on the Pi device and would VNC in to the desktop and monitor it from a computer in the house. But since the memory leak, I only run the INDI Server now on the Pi Device and connect to it from KStars/EKOS in the house. This method does not experience the memory leak, and I've been able to image reliably now for about a month.
I also use it remotely, and as I said in the computer I have 8GB of memory.
After the automatic capture of over 100 images (asteroid orbit measurement) the computer becomes slow, so much so that I have to close kstars to free up more than 7gb of memory.
Every time download an image it takes up a lot of ram memory.
I'm experiencing the same behavior.
When it got to finishing a capture, downloading, and beginning the next capture however the memory would increase by ~20 MiB each time until it ran out of memory when downloading a capture and kstars would force close.
Yes, that's the problem, it seems that Kstars doesn't free up memory after the image has been downloaded (in my case every FITS image has a weight greater than 30 MB), after more than 100 images are captured, my computer with 8 GB of memory it does not respond and requires "absolutely" that I close kstars.
With the latest kstars, indi, indi-3rdparty.
And all image captured in automatic scheduler.
In the INDI Control Panel SET option "Use Pulse Cmd" Off, this value is "Obligatory" for me with internal guide and Nexstar C8 GPS.
In my phone ( huawei p8 lite 2017 ) crash any version. ( also last in
Version downloaded from Play store when load NGC at 90%
Pipeline version after load NGC 100%
because of the heat, my meade dsi has several hot pixels
and the internal guide always tries to follow a defective pixel and returns an error
using a dark does not solve, only the "median" effect works
it would be useful to say not to use small stars less than half a millimeter
Now I have deleted the files:
and restarted the program, No problem.
I updated the data on asteroids and comets, from menu: Data->Updates