Have you tried setting the solver options to solve without using position (so it does a blind solve). Sometimes that has helped my out of this fix, but usually not and I also have to restart everything.

Read More...

Ronald Scotti replied to the topic 'Solver crashing Kstars' in the forum. yesterday

I don't know, I saw that also and did not know what Phonon was. It looks like it is a video/music player app that Kstars uses if you play sound. I don't know whether I can just uninstall it or whether I need to reinstall it and make sure it finds what it needs to work. I am not sure why it is coming into play here, but it is there.

I was thinking the crash might have something to do with the solver running multiple threads and not cleaning up it's 'buffers,' because the way I got it to work again was to limit it to a single thread. It would be nice to have a 'restore' function that when Kstars crashes you can clean up any memory it was using, so a restart would leave the Rpi in a start fresh condition. The server continues to run, the equipment all stays connected, PhD2 is still running in the background, just Kstars, Ekos, the Fits viewer and Indi control panel go away. Restarting Kstars/Ekos is not a problem as all the equipment is still connected, so it only takes a minute to get back running. But if the solver continues to crash it, that is where it really becomes annoying.

thanks for that insight,
Ron

Read More...

Ronald Scotti created a new topic ' Solver crashing Kstars' in the forum. yesterday

I am running Kstars 3.5.0 Stable (build 2020-12-06T18:17:19Z) on an Rpi 4 with 8 Gb memory. I have logging turned on with a separate log for astrometry, but it has stopped writing any astrometry logs. I have renamed the log file to include the date and set it for _verb, but a few days ago it stopped writing these logs. I get the regular logs and all they show is that everything just stops when the internal StellarSolver starts. It does not do this all the time, some nights it works fine (but still no Astrometry log). Once Kstars crashes, restarting it does not help. I have to reboot the Rpi and even then it may crash unless I set the solver option to only use one thread in solving.

Tonight was an example of this 'unusual' behavior. Everything worked fine thru polar alignment, slewing to a target, imaging and slewing to another target. After about 2 hours of imaging I began a move to another target, the log ended like this:
" 2021-01-18T21:32:07.210 EST INFO ][ org.kde.kstars.ekos.align] - "Image received."
[2021-01-18T21:32:07.214 EST INFO ][ org.kde.kstars.ekos.align] - "Automatically downsampling the image by 1"
[2021-01-18T21:32:07.342 EST INFO ][ org.kde.kstars.ekos.align] - "Evaluating Installed RAM for inParallel Option. Total Size of Index files: 2.74134 GB, Installed RAM: 7.64054 GB, Free RAM: 5.27455 GB"
[2021-01-18T21:32:07.346 EST INFO ][ org.kde.kstars.ekos.align] - "There should be enough RAM to load the indexes in parallel."
[2021-01-18T21:32:07.349 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-01-18T21:32:07.352 EST INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Sextractor with the 4-SmallScaleSolving profile . . ."
[2021-01-18T21:32:07.484 EST INFO ][ org.kde.kstars.ekos.align] - "Stars Found before Filtering: 85"
[2021-01-18T21:32:07.487 EST INFO ][ org.kde.kstars.ekos.align] - "Removing the stars with a/b ratios greater than 1.5"
[2021-01-18T21:32:07.490 EST INFO ][ org.kde.kstars.ekos.align] - "Keeping just the 50 brightest stars"
[2021-01-18T21:32:07.493 EST INFO ][ org.kde.kstars.ekos.align] - "Stars Found after Filtering: 50"
[2021-01-18T21:32:07.497 EST INFO ][ org.kde.kstars.ekos.align] - "Starting 4 threads to solve on multiple depths"
[2021-01-18T21:32:07.500 EST INFO ][ org.kde.kstars.ekos.align] - "Child Solver # 1, Depth Low 1, Depth High 13"
[2021-01-18T21:32:07.503 EST INFO ][ org.kde.kstars.ekos.align] - "Child Solver # 2, Depth Low 13, Depth High 25"
[2021-01-18T21:32:07.506 EST INFO ][ org.kde.kstars.ekos.align] - "Child Solver # 3, Depth Low 25, Depth High 37"
[2021-01-18T21:32:07.509 EST INFO ][ org.kde.kstars.ekos.align] - "Child Solver # 4, Depth Low 37, Depth High 49"
[2021-01-18T21:32:07.512 EST INFO ][ org.kde.kstars.ekos.align] - "Child Solver # 5, Depth Low 49, Depth High 61"
[2021-01-18T21:32:07.515 EST DEBG ][ org.kde.kstars.ekos.capture] - setAlignStatus: 4
[2021-01-18T21:32:07.626 EST DEBG ][ default] - WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioOutput ( no objectName ).
[2021-01-18T21:32:08.028 EST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: request: "{\"id\":13039,\"jsonrpc\":\"2.0\",\"method\":\"get_connected\"}"
[2021-01-18T21:32:08.029 EST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: defer call "get_app_state"
[2021-01-18T21:32:08.032 EST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: response: "{\"jsonrpc\":\"2.0\",\"result\":true,\"id\":13039}\r\n"
[2021-01-18T21:32:08.032 EST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: request: "{\"id\":13040,\"jsonrpc\":\"2.0\",\"method\":\"get_app_state\"}"
[2021-01-18T21:32:08.034 EST DEBG ][ org.kde.kstars.ekos.guide] - PHD2: response: "{\"jsonrpc\":\"2.0\",\"result\":\"Stopped\",\"id\":13040}\r\n"
[2021-01-18T21:32:08.129 EST INFO ][ org.kde.kstars.ekos.align] - "Scale range: 56.1163 to 112.233 arcmin wide"
[2021-01-18T21:32:08.148 EST INFO ][ org.kde.kstars.ekos.align] - "Image width 1280 pixels; arcsec per pixel range: 2.63045 to 5.2609"
[2021-01-18T21:32:08.152 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-01-18T21:32:08.156 EST INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 4-SmallScaleSolving profile. . ."
[2021-01-18T21:32:08.177 EST INFO ][ org.kde.kstars.ekos.align] - "Scale range: 56.1163 to 112.233 arcmin wide"
[2021-01-18T21:32:08.181 EST INFO ][ org.kde.kstars.ekos.align] - "Image width 1280 pixels; arcsec per pixel range: 2.63045 to 5.2609"
[2021-01-18T21:32:08.184 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-01-18T21:32:08.188 EST INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 4-SmallScaleSolving profile. . ."
[2021-01-18T21:32:08.196 EST INFO ][ org.kde.kstars.ekos.align] - "Scale range: 56.1163 to 112.233 arcmin wide"
[2021-01-18T21:32:08.199 EST INFO ][ org.kde.kstars.ekos.align] - "Image width 1280 pixels; arcsec per pixel range: 2.63045 to 5.2609"
[2021-01-18T21:32:08.203 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-01-18T21:32:08.206 EST INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 4-SmallScaleSolving profile. . ."
[2021-01-18T21:32:08.266 EST INFO ][ org.kde.kstars.ekos.align] - "Scale range: 56.1163 to 112.233 arcmin wide"
[2021-01-18T21:32:08.270 EST INFO ][ org.kde.kstars.ekos.align] - "Image width 1280 pixels; arcsec per pixel range: 2.63045 to 5.2609"
[2021-01-18T21:32:08.274 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
[2021-01-18T21:32:08.281 EST INFO ][ org.kde.kstars.ekos.align] - "Starting Internal StellarSolver Astrometry.net based Engine with the 4-SmallScaleSolving profile. . ."
[2021-01-18T21:32:08.362 EST INFO ][ org.kde.kstars.ekos.align] - "Scale range: 56.1163 to 112.233 arcmin wide"
[2021-01-18T21:32:08.365 EST INFO ][ org.kde.kstars.ekos.align] - "Image width 1280 pixels; arcsec per pixel range: 2.63045 to 5.2609"
[2021-01-18T21:32:08.369 EST INFO ][ org.kde.kstars.ekos.align] - "+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
"
At this point Kstars completely crashed and I had to restart it, but it would then crash on every solve even after a reboot. I finally tried turning off multiple thread solving and then it worked for awhile, but eventually
crashed on another solver later on. Again, there was no Astrometry log written for any of these sessions, even though I explicitly set it to write a separate log before starting my profile in Ekos.

I don't know what I can do to shed any more light on this, if anyone has any ideas please let me know.

thanks,
Ron

Read More...

I have a 10 year old Celestron CGEM DX, which I purchased new. Other AP'ers consider the CGEM a lower quality mount, but it does carry its weight. However, the older CGEM's, like mine, may have had a better quality build than the newer ones made by Synta (I don't really know because the design has not really changed). I have mixed results with this mount; some nights it works like a charm and others I cannot get it to calibrate (I have an OAG with a Lodestar guide camera and have always used Phd1 or 2). I too think it depends on seeing and where in the sky I am looking. I do rebalance the mount to keep it East side heavy where ever the scope is pointed. But I don't know what to do about Dec (I purchases some ankle weights that I thought I might try using to keep it South heavy as well). On a good night my Cal looks like this:



and my guiding can look like this for several hours:



I will not spend the money for a much better mount (2-5x times), so I am thinking of purchasing a "hypertune" kit that will replace the bearings and worm gears with better quality ones. Also, my mount is very stiff; it does not rotate freely and I suspect it has the old 'black' grease in it that makes it sluggish, the kit comes with newer grease. Running it with Kstars/Ekos (as I have done for the past several years)is fine and goto's have greatly improved with plate solving. I can "slew" dead on to a target with usually only 2 solves. So I don't think there is anything wrong with the mount and that is why I am thinking I should not try fix it! But I do think it could work better.

Ron

Read More...

Thanks, no worries. You can run "solve-field" from a window independent of EKOS, I have just been too lazy to go thru all the options and figure out what a command line should look like. There was a test configuration for the Stellar solver that I have on one SD card (have to figure out which one, as I am now booting from an SSD).

So there are other solutions at this time.
thanks,

Ron

Read More...

That would be fine, if there was an option in the Fits viewer to load a file and solve it. I find that trying to change settings, like changing the button to "do Nothing" during a solve is usually the cause of any crashes I have had. It would be better to just be able to select load, solve and do nothing (report the results as usual).

Read More...

Ronald Scotti replied to the topic 'Interface with Home Assistant' in the forum. 1 month ago

ok, thanks.

Read More...

Danke, but when I do that it changes back to "load and slew." the do nothing only seems to work on currently collected images, not one you load from a file.

Ron

Read More...

Ronald Scotti replied to the topic 'Interface with Home Assistant' in the forum. 1 month ago

Can you explain what the bridge does and how to implement it? I would like to run ASIStudio remotely by access the equipment at the scope on the Rpi running a server.

thanks,
Ron

Read More...

I would like an option just to plate solve an image and do nothing. Right now you have to "load and slew," but sometimes I just want to know where this previous taken image is in the sky but not slew the scope to that location. So I would like to "load, solve and do nothing option." There may be an option to do this already by disabling slewing on the mount but I am not sure.

I would also like to interface other programs thru the Indi Server, so I can run these programs on a laptop remotely but access the equipment thru the server running on the Rpi at the scope. Specifically the program I would like to interface to is ZWO's ASIStudio, which has good interface to run planetary imaging using video capture mode. I know this utility exists in EKOS, but I don't think it has access to all the capability of the ZWO camera's (ROI, etc). I know people are working on enhancing the planetary imaging capability of EKOS and there maybe other ways to access the equipment remotely with Indi, but I am not aware of it.

thanks,
Ron

Read More...

Ronald Scotti replied to the topic 'Snoop Devices' in the forum. 1 month ago

Darn, I looked all over those pages and did not see that there!

thanks,
Ron

Read More...

Ronald Scotti replied to the topic 'Snoop Devices' in the forum. 1 month ago

Unfortunately, there is no save in the Indi Control panel, where they show up. There are no other devices listed in the Ekos Profile Manager (where you can save your profile), only the devices I actually have. But once I connect to the mount (in the Indi Control Panel) and move to the "options tab" in the mount section, that is where the "Snoop Devices" show up. I can clear their entry and then "set" that cleared entry, but there is no place to 'save' that change.

thanks anyway, it looks like I have to remove them every time I start, unless there is a configuration file somewhere that they are in, where they can be removed.

Ron

Read More...

Ronald Scotti replied to the topic 'Indi server status confusion' in the forum. 1 month ago

Ok, so I am answering my own question. I followed my own advice and went back and watched that tutorial. When he gets to the part of running his equipment profile in Ekos he makes a passing remark about starting it as remote instead of local (it is a checkbox in the profile edit box in Ekos) (note: he makes this remark because he went thru the procedure of starting the Indi Server - in the left side panel - before starting Kstars/Ekos). Both use the "localhost" because both are running on the same machine, but if you hover the mouse over those boxes it says, use "local" if you are starting the indi server from inside Kstars/Ekos and use "remote" if you are starting the Indi server from the web manager or other method outside of Kstars/Ekos. I have had the "local" box checked because I (reasonably or not) thought that my system was local as everything was connected to it right at the telescope, but I should have checked the "remote" box because the Indi Server is 'remote' from Kstars/Ekos. If I check the "remote" box and still leave the connection to "Local Host," then when I "Start" the profile in Ekos that question never comes up!

thanks,
Ron

Read More...

Ronald Scotti replied to the topic 'Indi server status confusion' in the forum. 1 month ago

Thanks, I was pretty sure that was what I needed to do and how it works. If you watch the first minute or so of this: Astroberry Server Tutorial you will see what the panel on the left side looks like and how it is used. What I am not quite sure of is what is the difference between starting the server from that left panel (outside of Kstars/Ekos) or from inside Kstars/Ekos when you run them, if everything is connected to and running on that local Rpi? The server runs in the background in either case (I believe), so that if Kstars/Ekos crashes (and I don't need to reboot the Rpi), then the server is still running and I can just start up Kstars/Ekos again, connect the equipment and pick up where I left off. But I am not sure of that. I think the original reason for the server was for when you have your equipment connected to the Rpi, but you are running Kstar/Ekos on a remote machine (like a laptop). Then if Kstar/Ekos crashes the Rpi is somewhat oblivious to that fact and the server is still running (I don't know if it will continue imaging jobs already started or not).

I really feel bad about being confused on this, because I have been using Kstars/Ekos for three or four years now! I do see the advantage of just running the server on the Rpi at the equipment and running Kstars/Ekos on a laptop remotely. It is likely faster and as I said a Kstars crash does not affect the Rpi. And I have gone back an forth, running my system both ways over the years. I currently have upgraded to an Rpi 4 with 8 Gb Ram and have it booting from a 240 Gb SSD, which I connect to just from a browser window from the laptop in the garage (warmer and bugless). My reason is "Why Not!" the expense of that equipment is minimal (relatively speaking) and there is gain in transfer speed both for the Rpi and my cameras (all connected on a powered USB 3.0 hub). So I seem to be committed to running everything on the local Rpi and as long as everything hums along I see no reason not to.

So maybe my confusion is illusionary, just because of the complexity of the software. There have been several upgrades in my time frame with Kstars/Ekos and by trying to keep up with them I have lost track of where I am at!

So I agree, if I have already started the server (either from the left panel or from a command line entry) then there is no reason to shut it down and start a new instance, just enter "no" at that question ; that may be the default (it defaults to one or the other in a few seconds, so I have to go back and check what the default is).

thanks,
Ron

Read More...

Ronald Scotti created a new topic ' Snoop Devices' in the forum. 1 month ago

I have a Celestron CGEM mount, when I connect to the mount using the Indi control panel it shows Snoop devices under the Options tab. One device is a Dome Simulator and the other is a GPSD Simulator. Sometimes I cannot move the mount because the Dome simulator has to be disabled for the mount to move. Usually I go to this options tab first thing when I connect and I erase the snoop devices and they hit 'set', so they are removed from that section of the control panel. How can I get rid of them so that they don't show up initially?

thanks,
Ron

Read More...