After updating to KStars/EKOS 3.5.6, I am still having the issue that during the automagical slewing of the PAA, it just stops after about 10 to 20° of slewing. I have this on different computers and installations including the built-in EKOS installation on the RPi4 in the StarGO2, which is basically “hardwired” to the mount. But I always use the same INDI driver/server of the StarGO2.
Is this maybe an issue of the INDI driver? How can I test this?
(The slewing buttons in the KStars telescope work).
I just ordered a Raspberry Pi4 and will try Stellarmate…. Let’s see. What triggered this purchase was the new polar alignment assistant in EKOS, which seems to be supported in the iPad SM-app as well. I just saw a YouTube video on it. This is what I was looking for
Hi. I just ordered a Raspberry Pi 4B / ARMv8 / 8GB RAM / SD 128GB with an aluminium housing. I want to try StellarMate with that device and my iPad Pro.
Do you expect similar PAA issues with StellarMate on this RP4 as with the EKOS that is on the StarGO2 or with the EKOS on my MacBook?
I would also like to use the INDI driver for the mount that is already installed on the StarGO2 RP4. The StarGO2 has its own INDI server that starts up automatically on boot. So I would need to chain the SM server with the SG server… is this feasible?
While the StarGo2 has its own INDI server on a Raspberry Pi 4 with KStars/EKOS etc…. the interface via VNC is not that convenient on the iPad. This should basically be the same as a StellarMate.
Well, I am looking into the StellarMate/Astroberry set-ups. The StellarMate app, however, has a lot of negative reviews in the AppStore. Never sure what is true and what are user errors. Maybe I will give it a try anyway. If the StarGO2 would be more convenient over VNC, that would be the easiest approach. The ASIAIR is absolutely great and easy to use, but limited to ZWO hardware and support is spotty. I am sure StellarMate is more responsive .
Coming back to your previous post: I could imagine, that ZWO would use a very similar directory structure as the the standard INDI installation… therefore, let me rephrase, where would I need to change this setting/add that line in the standard INDI installation?
It seems that you a very familiar with the StarGO2 set-up
Where would I find the INDI startup command on the ASIAIR? I mean, where would that typically be, in which directory?
Once this command would be implemented on the ASIAIR, would the stargo2 show up in the drop-down list in the ASIAIR APP telescope list?
Oh…. Thank you! I missed that!
This seems to be straight forward and an easy fix!
I have been in touch with both ZWO and Avalon, but neither one has proposed this solution or a such an update. Well, Avalon is on it, but does not seem to find a full solution. They refer to the LX200 Basic driver on the ASIAIR, which does not allow guiding or interactive slewing. ZWO said they would look into it… but I have not heard from them since several weeks. No idea what is the status here. That why I started this thread.
Thank you for your quick reply. From what I understood in the link of chained INDI servers, that scenario does not apply to me.
I think I am having issues of two INDI servers /not) talking to each other:
My Avalon M-Uno mount is controlled by the new StarGO2 Pro controller, which is based on a Raspberry Pi 4 and runs its own local INDI server (starts automatically upon booting). It has it‘s own StarGO2 telescope (mount) driver which is detected, recognized and usable by external computers and EKOS, PHD, SkySafari, etc…. But I guess these are all INDI clients and not INDI servers.
Now I like to use my ASIAIR Pro, which seems to have its own INDI server. The ASIAIR does not allow me, or does not seem to have the option, to choose and use the INDI driver on the remote INDI server. So I can only use the available INDI drivers on the ASIAR… They seem to be very limited in functionality or not connecting at all. ZWO is not really responding to my request to fix this.
Actually, I have a similar issue when using INDIGO from my MacBook. In order to use INDIGO properly, I would need to have an INDIGO server on the StarGO2 RPi4. Not an option yet.
With ZWO not replying and no INDIGO server, is there a way to copy/install the StarGO2 INDI driver on the RP of the ASIAIR? Or are there other possible workarounds?
It also seems to me, the two INDI servers are conflicting each other.
Any help is highly appreciated.
BTW, remote login (VNC or Anydesk) to the StarGO2 is not my favorite solution.
I got it working in XCode in a SWIFT playground.
The NWNetwork framework seems straight forward for this task.
I have to check the timing and variable sizes, though. I don’t get all the xml response with a single receive call.
Building a SWIFTUI around it should not be too difficult.
I tried different speed settings within MAX but also the FIND speed. The later is only 100x sideral, very slow.
Did you see my issues with the guider? Do you have any idea what could be wrong there?
Could it be the StarGO2 INDI driver?