Are you referring to this?sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update && sudo apt-get install libindi1I don’t see anything specific to the Sky Safari driver.
Read More...
I’d like to add the Sky Safari INDI middleware “driver” to my INDI install. How do I install a single driver? Installing on Raspberry Pi 4 with Raspbian Buster.
Read More...
Hi Jasem,
I'm not sure how to try the next nightly build. My INDI install comes from Radek's astroberry Raspberry Pi repository. I don't want to break anything.
By the way, I've worked around this issue by initializing the driver using PyIndi. Probably a more robust method than depending upon the save anyway.
Steve
Read More...
Hi,
I'm using the Astro-Physics GTO CP2 INDI driver to interface PHD2 to my Mach1 while I use TheSkyX for mount (and its native Astro-Physics driver) and imaging camera control. TheSkyX is connected to one of the mounts serial ports and PHD2 to the other. I'm writing a Python script that sequences the imaging and allows for dithering with PHD2 (TheSkyX doesn't allow for dithering with PHD2). All of this on a Raspberry Pi 4 with Raspbian Buster.
Generally it's all working although I'm having intermittent issues with the INDI mount driver erroneously initializing the mount location latitude and longitude to 0 and 0. I'm also not sure how the driver configuration is loaded. I've set up and saved a configuration but it seems I always have to manually load my saved configuration after the driver connects to the mount. How do I automatically load my saved configuration?
Regards,
Steve
Read More...
Thanks for the reply, Eric. I don't know if TheSkyX can handle multiple clients but one step at a time It's something I may be able to work around.
Anyway, the solution to the problem is here:
indilib.org/forum/general/6907-paramount-connection-on-mac.html
Unfortunately my scripts require that the "TCP Responses Close Socket" option is selected so I'm at a bit of an impasse. No big deal though. There are other options.
Steve
Read More...
Hi,
Due to some annoying and apparently unfixable SBIG driver issues (can't connect my ST-i and my ST-8300M to theSkyX simultaneously), I'm trying to use indiserver to connect PHD2 to TheSkyX so that I can use my ST-i for guiding with dithering and theSkyX to drive my scope; I've written a python script that controls both theSkyX and PHD2 via their servers. I was able to connect PHD2 to theSkyX and slew the scope with PHD2. Now I can't seem to connect to the Sky with the Paramount indi driver. If I try to connect when theSkyX is not connected to the telescope, I can see that theSkyX successfully connects to the telescope but PHD2 doesn't say that it's connected to theSkyX and indi says there was a handshake failure. By the way, TCP server is enabled in theSkyX and I know it's communicating as I'm using it with my Python script. I'm even using the same "sky6RASCOMTele.IsConnected" command in my script successfully. Note that my script was not running at the same time that I was attempting this.
I'm using an RPi4 4GB with Raspbian Buster. I'm using Radek Kaczorek's indiserver repository.
Here's the interesting part of the log:
2020-05-02T21:15:09: Driver indi_paramount_telescope: read message Paramount '[INFO] Connecting to localhost@3040 ...'
2020-05-02T21:15:09: Client 0: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 5: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Driver indi_paramount_telescope: read message Paramount '[DEBUG] Connection successful, attempting handshake...'
2020-05-02T21:15:09: Client 0: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 5: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[INFO] Connecting to localhost@3040 ..."/>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[INFO] Connecting to localhost@3040 ..."/>
2020-05-02T21:15:09: Driver indi_paramount_telescope: read message Paramount '[DEBUG] CMD: /* Java Script */var Out;sky6RASCOMTele.ConnectAndDoNotUnpark();Out = sky6RASCOMTele.IsConnected;'
2020-05-02T21:15:09: Client 0: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 5: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] Connection successful, attempting handshake..."/>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] Connection successful, attempting handshake..."/>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 1:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] CMD: /* Java Script */var Out;sky6RASCOMTele.ConnectAndDoNotUnpark();Out = sky6RASCOMTele.IsConnected;"/>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 1:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] CMD: /* Java Script */var Out;sky6RASCOMTele.ConnectAndDoNotUnpark();Out = sky6RASCOMTele.IsConnected;"/>
2020-05-02T21:15:09: Driver indi_paramount_telescope: read message Paramount '[ERROR] Error reading from TheSky6 TCP server.'
2020-05-02T21:15:09: Client 0: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 5: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Driver indi_paramount_telescope: read message Paramount '[DEBUG] Handshake failed.'
2020-05-02T21:15:09: Client 0: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 5: queuing <message device='Paramount' name=''>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[ERROR] Error reading from TheSky6 TCP server."/>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[ERROR] Error reading from TheSky6 TCP server."/>
2020-05-02T21:15:09: Driver indi_paramount_telescope: read setSwitchVector Paramount CONNECTION Alert
CONNECT='Off'
DISCONNECT='On'
2020-05-02T21:15:09: Client 0: queuing <setSwitchVector device='Paramount' name='CONNECTION'>
2020-05-02T21:15:09: Client 5: queuing <setSwitchVector device='Paramount' name='CONNECTION'>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] Handshake failed."/>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 2:
<message device="Paramount" timestamp="2020-05-02T21:15:09" message="[DEBUG] Handshake failed."/>
2020-05-02T21:15:09: Client 0: sending msg copy 2 nq 1:
<setSwitchVector device="Paramount" name="CONNECTION" state="Alert" timeout="60" timestamp="2020-05-02T21:15:09">
<oneSwitch name="CONNECT">
Off
</oneSwitch>
<oneSwitch name="DISCONNECT">
On
</oneSwitch>
</setSwitchVector>
2020-05-02T21:15:09: Client 5: sending msg copy 1 nq 1:
<setSwitchVector device="Paramount" name="CONNECTION" state="Alert" timeout="60" timestamp="2020-05-02T21:15:09">
<oneSwitch name="CONNECT">
Off
</oneSwitch>
<oneSwitch name="DISCONNECT">
On
</oneSwitch>
</setSwitchVector>
Hi,
I attempted to follow the instructions
here
to install INDI server on a Raspberry Pi 4 with Buster but ran into problems. First when executing
wget -O - https://www.astroberry.io/repo/key | sudo apt-key add -
[sudo] password for steve: --2020-04-18 11:48:29-- https://www.astroberry.io/repo/key
Resolving www.astroberry.io (www.astroberry.io)... 87.98.235.184
Connecting to www.astroberry.io (www.astroberry.io)|87.98.235.184|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4365 (4.3K)
Saving to: ‘STDOUT’
- 100%[===================>] 4.26K --.-KB/s in 0s
2020-04-18 11:48:29 (155 MB/s) - written to stdout [4365/4365]
sudo apt update
The following signatures couldn't be verified because the public key is not available
Thanks Rolf. This is great to know. This behaviour has always annoyed me. This does raise the question, however, why isn't separate windows the default behaviour? What is the advantage of the current default behaviour?
Read More...
ppapadeas wrote: Motor control is a bit of an overkill at this point imho, mainly because most of the newer focusers have the control integrated, but please let me know if you feel this is a showstopper.
This looks fantastic!
Here's a pic of my Indi/Kstars RPi box, which I mount on top of my scope:
Radek,
A question? How does the position reset function work? I’ve had kstars/ekos crash a few times while focusing leaving the focuser near focus and near focus being the zero position rather than the zero position being racked in. I understand position reset allows one to move to negative positions while still identifying the new position as zero. How many steps is the focuser moved inward when selecting position reset?
Regards,
Steve
Read More...
I see this problem from time to time as well. I don’t know what the root cause is. You can increase the size or crop the affected images. The most annoying thing is you need to be aligned with your darks.
Here’s a thread that mentions a similar issue although it seems it was fixed:
indilib.org/forum/ccds-dslrs/2849-asi160...-image-geometry.html
Steve
Read More...
Thanks Radek. The problem was that i had "Default" as the selected output rather than "File".
By the way, I seemed to have fixed the astroberry motor hat driver crashing issue by reinstalling the driver.
Steve
Read More...