Rob Lancaster replied to the topic 'Solver fails consistently' in the forum. 1 week ago

kbahey wrote: @gbeaton, @rlancaste

I am also seeing that PAA never completes. It takes the 3rd image, completes the solve, then just hangs there with the 'Capture' button greyed out. Or the entire KStars will crash sometimes. I see this with the CCD simulator and telescope simulator, so not a driver issue.

I reported this here .

Meanwhile, the regular Capture and Solve works fine, with the Sync action, all that works fine.

PAA was working fine until around the 4th of July or so.

Also, I see the same thing regarding WCS: if I disable WCS in the solver options and in INDI, but still the code tries to do it, and the code crashes in a method called loadWCS, which points to where the issue may lie.


Yes, Jasem made a change to wcs so that it does not always load when an image is loaded, but instead is loaded when needed. This also broke a couple of the methods that I had written, but I have since corrected them. I dont have much experience with the polar alignment helper, maybe Jasem can help.

Read More...

Rob Lancaster replied to the topic 'Solver fails consistently' in the forum. 1 week ago

Vox45 wrote: Thank you for your answer.

(1) "The -O option is required in Ekos since the -o option overwrites the previous solution files and if that were not included"

-> what I meant is that when I open the "edit solver options" the checkbox for the -O is not cheked, yet the option appears in the option line. This is odd and I was wondering if this is to be expected, maybe some kind of refresh needs to happen ?


The -O option is supposed to be a disabled checkbox that is permanently checked. That one and the noplots option. Is it not that way on your system? I can take a look and see if that was changed recently. You should not be able to uncheck it.

Read More...

Rob Lancaster replied to the topic 'Solver fails consistently' in the forum. 1 week ago

I can answer a couple of these questions.

Gbeaton, i dont know about any issues with the polar align function, since I use my polar scope, but i can say that sometimes there can be problems plate solving near the pole. It can help to try a couple of locations a little farther from the pole.

Also gbeaton, yes offline solver is often much faster and more reliable than the online one but requires tweaking. Once you get its settings configured well for your system, it can often solve in even less time than the 4 seconds you stated.

Vox45, ekos uses the astrometry.net software which i do think is what astrotortilla uses. As for the missing options, you could try them out and see if they help. Astrometry.net has lots of capabilities and options, no Ekos does not have all of them built in as checkboxes but they can still be used in ekos by typing them in the options line in or tested by running it from the command line.

The -O option is required in Ekos since the -o option overwrites the previous solution files and if that were not included, it would fail to solve the next image since it cannot overwrite. And the noplots option is required since ekos does not use the plots produced and they just take more time to produce.

Read More...

Rob Lancaster replied to the topic 'KStars 2.7.9 is released!' in the forum. 2 weeks ago

gbeaton, I did a fresh build of the kstars DMG with the latest version after you reported an issue. This may have fixed the problem. Please test this one and see if it works any better than before.

Thanks,

Rob

drive.google.com/file/d/0B_ivMJINsdQ8RVV...djA/view?usp=sharing

Read More...

Rob Lancaster replied to the topic 'KStars 2.7.9 is released!' in the forum. 2 weeks ago

Hmm, Looks like something in indi was changed. I will look into it. "dyld: Symbol not found: __ZN4INDI13DefaultDevice9ISNewBLOBEPKcS2_PiS3_PPcS5_S5_i". Meanwhile, yes, just reinstall the last version right over top of the new one. Thats no problem. I am keeping a copy of all of the OS X dmg builds that I do so I can go back to an old one just in case. Here is the last one that I built before the current one. Hopefully we can see what is wrong and I will build a new dmg.

drive.google.com/file/d/0B_ivMJINsdQ8cGt...RlE/view?usp=sharing

Read More...

Rob Lancaster replied to the topic 'Solver index files won't install' in the forum. 3 weeks ago

I think I know what might have happened. Those are two of the largest single file downloads. Below the 4208 set, the files are broken up into multiple files due to their large size. Can you download 4107? I suspect the download is timing out because it took too long. I programmed a timer in the downloader so that it doesn't keep on trying to download massive files when there might be a dropped connection or some other issue that won't let it finish. With the timeout feature, you can try the download again if it doesn't work. But I guess if your internet connection is too slow, you might not be able to get the big files in the allotted time. We might need to increase the time.

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Temmerman wrote: That's great Rob because indeed overtime the DSLR is switched off one has to kill the PTPCamera again.

What is Jasem's avatar because I couldn't find him through the search engine?

Kind regards,
Robert


He is KNRO www.indilib.org/support/community/1-jasem-mutlaq/profile.html

Read More...

We thank you for the kudos on the Mac version. And feel free if you are a software developer, to get involved. The source code is freely available and we have developed a script that you can use to build the code for editing in Xcode, in QTCreator, or other editors. See this link: github.com/jamiesmith/kstars-on-osx

I haven't done much with the custom colors, other than to make the night vision color scheme work on OS X. There very well might be some issues there because it was coded for Linux and assumes the use of palettes, whereas I had more luck with the night vision scheme using stylesheets. Also I ran into a problem with the night vision scheme where certain things in the OS wanted to maintain their colors even though it is terrible for night vision. Similar problems could be encountered with custom color options because they do not make use of the stylesheets that I used to make the night vision scheme work.

Please note any issues and try to track down their cause. We are always open to changing the code.

Thanks,

Rob

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Robert,

I just wrote some code that will have KStars check for "PTPCamera" when it starts up an indiserver on a local OS X machine and then give the user an option to quit that program. This should at least prevent PTPCamera from stealing the camera and not letting you connect in the first place. We will have to see if there are any cases when it can steal the camera later on. Maybe if the camera gets turned off and back on? But anyway, this should be a start.

I sent the patch to Jasem and we will include it in the next DMG build.

Thanks,

Rob

Read More...

Robert thanked Rob Lancaster in topic Ekos on Mac OS X ? 3 weeks ago
Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Temmerman wrote: That was the reason Rob. " killall PTPCamera" did the trick! Canon is now online!! Thank you so much! I didn't have to use any other INDI driver. Star's internal was sufficient. I guess I will have execute this command every session now.

Regarding my second problem; any ideas on the solving problems of my polar alignment?

Kind regards,

Robert


Thats a question for Jasem, since he developed that routine, but I haven't even used it. I use my polar scope to align it in the field. My scope is not permanently mounted and the polar scope is easy to use and fast. The polar alignment routine looks nice, I just haven't tried it yet.

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Robert,

I looked through your log file just now and saw several things. It looks like it is detecting the camera properly since it says there is 1 camera and it identifies it properly. The only error message I saw in the log file was that it couldn't claim the usb device. Do you have any other programs running that might tie up the camera?

Here is a thought, sometimes PTPCamera daemon on OS X steals the camera. Try this command in the terminal after you connect the camera but before you try to connect to it in INDI/KStars:

killall PTPCamera

You can also use Activity monitor to see the process and quit it as well if you prefer that to the terminal.

The same goes for any other programs/processes that want to steal the camera so that other programs cannot use it. But I suspect this one is the culprit because it did that to mine a few times.

Thanks,
Rob

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Temmerman wrote: Hello,
I have followed the instructions and included the Kstar logfile as well as some screencaptures.
After I started the indi server via Terminal I started the Canon 700D and Kstar.
When selecting Ekos and starting INDI it says that there is another instance of INDI running. When I answer No to shutting it down I can see on the Terminal window that I believe the Canon driver is being loaded. However I am not able to connect my devices such as the mount and the CCD. The Ksat configuration is Local not Remote. I have included the window where you can see what path the indi library is that Kstar uses.
I restarted Kstar but this time I selected Yes to the question of shutting down the already running INDI instance. Now everything connects except for the Canon and indeed in the terminal I can see that it is not loaded.

Hope this helps a bit.

Thanks again,

Robert


Yes that is correct, we only started the canon driver from the terminal, so that should be the only device that connects. In fact, I probably should have told you to make a profile in KStars that only includes the canon driver, so that the others don't try to connect. The primary reason for this is because we want to isolate the problem. The other devices and their messages while they are connecting will get in the way. You are correct to say "no" to starting another indiserver because right now we want to test it using the one from the terminal. The log file was very helpful, though as I said, getting the other devices out of the way would help. I saw some of the output from the indiserver in the window on the left but couldn't make it all out, could you copy and paste whatever it said?

Thanks!

Rob

Read More...

Eric Vickery thanked Rob Lancaster in topic Ekos on Mac OS X ? 3 weeks ago
Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

rlancaste wrote:

ColoradoSolar wrote: When I run indi server local it doesn't work right on my ASI camera and it doesn't work at all on my ZWO EFW but if I run the embedded indi server from the terminal then it all works fine. Is there something strange about how kstars starts the embedded indi server?


The main problem is that when a process is launched from a QT program, such as an indi server, or Astrometry solver, the environment variables are not the same as they are when you launch the same program from the command line. I am fairly sure this is done for security reasons. My solution has been to just add the environment variables that you need in order to make the program work when the process is started by KStars. Basically we just need to know what environment variable is missing.


By the way, if you would like to try, since I know you already have QT and all of the software installed on your computer to try this, you might try adding an environment variable or two and see if it works. The relevant file is KStars/INDI/ServerManager.cpp. Approximately Line 85 or so. You will notice there I added some lines for environment variables for GSC, GPhoto cameras, QHY, and the indiprefix. I do have an ASI camera but not an ASI filter wheel. So I can only test the camera.

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

ColoradoSolar wrote: When I run indi server local it doesn't work right on my ASI camera and it doesn't work at all on my ZWO EFW but if I run the embedded indi server from the terminal then it all works fine. Is there something strange about how kstars starts the embedded indi server?


The main problem is that when a process is launched from a QT program, such as an indi server, or Astrometry solver, the environment variables are not the same as they are when you launch the same program from the command line. I am fairly sure this is done for security reasons. My solution has been to just add the environment variables that you need in order to make the program work when the process is started by KStars. Basically we just need to know what environment variable is missing.

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

anofeles wrote: I have a problem with the ekos solver control...
If I make a "capture & solve" with "nothing" solver action checked, all works fine (online and offline) but if I make a "capture & solve" with "Sync" action checked (same image) ekos doesn't even solve (online or offline) the same image that it had solved in a few seconds with the "nothing" option checked...
Sorry my english...
Any idea, please?
Thanks in advance...


Do you have the latest version from the website?

Read More...

Rob Lancaster replied to the topic 'Ekos on Mac OS X ?' in the forum. 3 weeks ago

Temmerman wrote: Thank you for the swift reply. :-) I have all the Cloudmakers' software installed on my Mac. However when I start Kstar I think I use the Kstar's INDI as I haven't opened any of Cloudmaker's software (including their INDI server and INDI control panel). I was confused when I installed Kstar by the setup wizard's question whether I wanted the Internal INDI or external INDI. It says "In case of doubt choose Internal INDI server" so I did. I wasn't aware of the difference. Do they mean by external INDI server that it is located somewhere remotely on the' web' or simply not part of Kstar's software such as Cloudmaker's INDI server? Anyhow, I have included a screen capture which shows that I am using an Kstars' internal INDI server I think. Regarding the indilib I installed I got that from the Cloudmaker's site where they have an OSX version of the server. I am not versed in programming so I wouldn't have a clue how to use the source code.
I understand I am to try to use the Terminal software in OSX. Can you show me how to " run the indiserver from the command line and connecting to it from kstars as if it were a remote indiserver"?
And/or how to "built it from source and install it to /usr/local/bin".
And/or how to "run that one from the command line and connecting to it as if it were a remote indiserver from stars".
I have downloaded the "libindi_1.4.1.tar.gz" and have a "libindi 2 folder now. Wouldn't have a clue how to proceed. Sorry for my ignorance. :-(
What happened to the good old WYSIWYG ;-)
Where are the star log files located in OSX so I can send them to you?

A very appreciative Robert.


Basically, "internal" means it starts its own indi server. On os x, the goal is to have it bundled inside the app for simplicity. An external indiserver could be on a separate computer on the network, on the internet, over wifi, or even just on the same computer but launched from the command line or another program like the cloudmakers indi server.

To turn on logging, just go to the preferences in kstars, then advanced, and logging. You will want to check "indi" and tell it so save to a log file. In that same panel, there is a button that will show you where the log is located.

To try to run the indiserver from the command line:
1. Open Terminal.app
2. Right click on KStars.app (wherever you installed it) and click on "show package contents"
3. Navigate to the Contents/MacOS/INDI folder
4. Go back to the terminal and type "cd " in the terminal.
5. Drag the indi folder to the terminal window, it should type the path after your "cd". Hit enter.
6. Now you are "in" the indi folder in the terminal.
7. Type the following command exactly as it shows in the terminal:
./indiserver -vvv ./indi_canon_ccd

After you type that, it should be running and will print all output. You can connect your camera, start up kstars and connect to a "remote" indiserver with localhost as the host and the canon indi driver selected as the only driver. Make sure you take note of anything that it says in the terminal window since any issues should print.

If you have both a log file and the terminal output that would greatly help us figure out any problems.

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!