×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

SkySafari 6 doesn't connect

  • Posts: 4
  • Thank you received: 0
Hello, I've bought SkySafari 6 Plus on my iPhone and tried to connect it to INDI 1.6 installed on my Raspberry PI3.
When I try to connect to it it gives the following error:

"SkySafari 6 Plus can't make a wireless network connection to the scope. Make sure you've joined the Wi-Fi network, and entered its IP address correctly".

Anyway, after seeing the logs and making a tcpdump, I saw that SkySafari actually sent commands to INDI:

Logs:
[2018-02-19T18:25:22.897 CET DEBG ][           org.kde.kstars.indi] - SkySafari : "[DEBUG] CMD <RS> "
[2018-02-19T18:25:22.899 CET DEBG ][           org.kde.kstars.indi] - SkySafari : "[DEBUG] CMD <> "

Tcp Dump:
18:25:22.660028 IP 192.168.1.2.61138 > 192.168.1.7.9624: Flags [F.], seq 1337371763, ack 3385647281, win 2058, options [nop,nop,TS val 826118294 ecr 1732977], length 0
	0x0000:  4500 0034 0000 4000 4006 b76a c0a8 0102  E..4..@.@..j....
	0x0010:  c0a8 0107 eed2 2598 4fb6 ac73 c9cc e0b1  ......%.O..s....
	0x0020:  8011 080a fce5 0000 0101 080a 313d 9096  ............1=..
	0x0030:  001a 7171                                ..qq
18:25:22.683224 IP 192.168.1.7.9624 > 192.168.1.2.61138: Flags [F.], seq 3385647281, ack 1337371764, win 227, options [nop,nop,TS val 1733488 ecr 826118294], length 0
	0x0000:  4500 0034 91c1 4000 4006 25a9 c0a8 0107  E..4..@.@.%.....
	0x0010:  c0a8 0102 2598 eed2 c9cc e0b1 4fb6 ac74  ....%.......O..t
	0x0020:  8011 00e3 020d 0000 0101 080a 001a 7370  ..............sp
	0x0030:  313d 9096                                1=..
18:25:22.688637 IP 192.168.1.2.61138 > 192.168.1.7.9624: Flags [.], ack 3385647282, win 2058, options [nop,nop,TS val 826118350 ecr 1733488], length 0
	0x0000:  4500 0034 0000 4000 4006 b76a c0a8 0102  E..4..@.@..j....
	0x0010:  c0a8 0107 eed2 2598 4fb6 ac74 c9cc e0b2  ......%.O..t....
	0x0020:  8010 080a faad 0000 0101 080a 313d 90ce  ............1=..
	0x0030:  001a 7370                                ..sp
18:25:22.690348 IP 192.168.1.2.61139 > 192.168.1.7.9624: Flags [S], seq 1845076892, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 826118351 ecr 0,sackOK,eol], length 0
	0x0000:  4500 0040 0000 4000 4006 b75e c0a8 0102  E..@..@.@..^....
	0x0010:  c0a8 0107 eed3 2598 6df9 a39c 0000 0000  ......%.m.......
	0x0020:  b002 ffff cb93 0000 0204 05b4 0103 0306  ................
	0x0030:  0101 080a 313d 90cf 0000 0000 0402 0000  ....1=..........
18:25:22.690497 IP 192.168.1.7.9624 > 192.168.1.2.61139: Flags [S.], seq 2991017903, ack 1845076893, win 28960, options [mss 1460,sackOK,TS val 1733489 ecr 826118351,nop,wscale 7], length 0
	0x0000:  4500 003c 0000 4000 4006 b762 c0a8 0107  E..<..@.@..b....
	0x0010:  c0a8 0102 2598 eed3 b247 4faf 6df9 a39d  ....%....GO.m...
	0x0020:  a012 7120 f5e3 0000 0204 05b4 0402 080a  ..q.............
	0x0030:  001a 7371 313d 90cf 0103 0307            ..sq1=......
18:25:22.692914 IP 192.168.1.2.61139 > 192.168.1.7.9624: Flags [.], ack 2991017904, win 2058, options [nop,nop,TS val 826118354 ecr 1733489], length 0
	0x0000:  4500 0034 0000 4000 4006 b76a c0a8 0102  E..4..@.@..j....
	0x0010:  c0a8 0107 eed3 2598 6df9 a39d b247 4fb0  ......%.m....GO.
	0x0020:  8010 080a 8dc3 0000 0101 080a 313d 90d2  ............1=..
	0x0030:  001a 7371                                ..sq
18:25:22.693571 IP 192.168.1.2.61139 > 192.168.1.7.9624: Flags [P.], seq 1845076893:1845076897, ack 2991017904, win 2058, options [nop,nop,TS val 826118354 ecr 1733489], length 4
	0x0000:  4500 0038 0000 4000 4006 b766 c0a8 0102  E..8..@.@..f....
	0x0010:  c0a8 0107 eed3 2598 6df9 a39d b247 4fb0  ......%.m....GO.
	0x0020:  8018 080a 0042 0000 0101 080a 313d 90d2  .....B......1=..
	0x0030:  001a 7371 3a52 5323                      ..sq:RS#
18:25:22.693695 IP 192.168.1.7.9624 > 192.168.1.2.61139: Flags [.], ack 1845076897, win 227, options [nop,nop,TS val 1733489 ecr 826118354], length 0
	0x0000:  4500 0034 3cc1 4000 4006 7aa9 c0a8 0107  E..4<.@.@.z.....
	0x0010:  c0a8 0102 2598 eed3 b247 4fb0 6df9 a3a1  ....%....GO.m...
	0x0020:  8010 00e3 94e6 0000 0101 080a 001a 7371  ..............sq
	0x0030:  313d 90d2                                1=..

INDI SkySafari driver was configured to use the Telescope Simulator and is listening on default port (9624).
On SkySafari 6 Settings, I've set:

- Telescope Type: Meade LX-200 GPS
- Mount Type: Equatorial GoTo (German)
- IP Address: 192.168.1.7 (the IP of the Raspberry)
- Port: 9624

Is it an issue with the new SkySafari 6?
6 years 1 month ago #23441

Please Log in or Create an account to join the conversation.

No need for low-level TCP dumps now, what about the SkySafari INDI driver log? Also, in the SkySafari INDI driver, is the mount name specified under Options?
6 years 1 month ago #23443

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0

Replied by Artix on topic SkySafari 6 doesn't connect

INDI Logs:
[2018-02-19T18:45:16.742 CET INFO ][           org.kde.kstars.indi] - SkySafari :  "[INFO] SkySafari Server is running. Connect the App now to this machine using SkySafari LX200 driver. "
[2018-02-19T18:45:16.743 CET INFO ][           org.kde.kstars.ekos] - SkySafari is connected.
[2018-02-19T18:45:16.743 CET DEBG ][           org.kde.kstars.ekos] - 1  devices connected out of  4
[2018-02-19T18:45:16.802 CET INFO ][           org.kde.kstars.indi] - SkySafari :  "[INFO] Debug is enabled. "
[2018-02-19T18:45:16.802 CET DEBG ][           org.kde.kstars.indi] - < SkySafari >: < DEBUG_LEVEL >
[2018-02-19T18:45:16.825 CET DEBG ][           org.kde.kstars.indi] - < SkySafari >: < LOGGING_LEVEL >
[2018-02-19T18:45:16.826 CET DEBG ][           org.kde.kstars.indi] - < SkySafari >: < LOG_OUTPUT >
[2018-02-19T18:25:22.897 CET DEBG ][           org.kde.kstars.indi] - SkySafari : "[DEBUG] CMD <RS> "
[2018-02-19T18:25:22.899 CET DEBG ][           org.kde.kstars.indi] - SkySafari : "[DEBUG] CMD <> "

In SkySafari Driver Options I have:

Active Devices: Telescope: "Telescope Simulator"
6 years 1 month ago #23445

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

SkySafari 6 attempts the following.

HTTP GET /setserial?baud=9600;bit=8,parity=N;stop=1/
The service replies.

HTTP 1.6 404.

StarSafari closes the connection.
6 years 2 weeks ago #23979

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello

The issue is that the command is an HTTP GET.

HTTP GET /setserial?baud=9600;bit=8;parity=N;stop=1

The Raspberry INDI does not know what to do with it.

NGINX responds with a

HTTP 1.6 404 error.

Looks like something has to change.
6 years 2 weeks ago #23981

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

The call is an HTTP GET command.

HTTP GET /setserial?baud=9600;bit=8;parity=1;stop=N

The INDI driver does not know what to do with this command.

IT gives up. NGINX responds with a 404 message.
6 years 2 weeks ago #23982

Please Log in or Create an account to join the conversation.

Is this SKySafari Desktop or Mobile version?? On mobile, it just communicated directly using whatever protocol was set eg. LX200. Above it looks like it's using internal server to perform the connection. Obviously, SkySafari and expecting an HTTP Response from the server, what's the response? and what happens after the response is OK? does it continue to send GET/POST requests or it starts sending raw low level mount commands?
6 years 2 weeks ago #24002

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

For iOS, SkySafari is open to iPhone, iPod, and iPad any size. The dumps provided do not show the communication.

To connect to the scope, a SETUP screen is given to connect to the Web interface. On a PI, INDI is the Web manager for HTTP connections. On SkySafari 6, the scope selections are stated to be the ones compatible to itself. This is stated on its website.

I used tshark to peer into the the client/server response. I collated the time to find the exchange and residuals. This the sequence in mil-seconds.

SS6Pro - 10.0.0.2 "HTTP GET /setserial?baud=9600;bit=8;parity=N;stop=1"

INDI - 10.0.0.1:7642 HTTP 1.6 404 "-" "-"


On iPad or iPhone, this is message. (The iPod cannot talk to the INDI with SS6Pro.)

"SkySafari 6 Pro can make a wireless connection to the scope, but the scope is not responding. Make sure it is connected and powered on. Also check that your scope type is correct. "

No matter which scope driver identified on the SkySafari, the client response is the same. Setting up communication with the scope is always the first step to assuming control of the scope. Per the company offerings, SkyFI and Wired SkyFi are their tools for connect a scope for mobile control. This makes it a nice homogeneously closed system.

So, if anyone hot rods the scope to be any of the following:
1. reduces PEC by two decimals.
2. changes any gears to a different ratio.
3. modifies any focus system.
tough luck. Stock is what is given under SkySafari. No avenue is available to change the game to anything better in this paradigm.

I have the PCAP that has this exchange.
6 years 2 weeks ago #24008

Please Log in or Create an account to join the conversation.

I'm using SkySafari 5 Plus on my Android tablet. I just specified the IP address and port (9624) and "Auto Detect SkyFi" was unchecked. Is it checked in your case?
6 years 2 weeks ago #24015

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello

Thank you for the reply. 7624 and 9624 are the ports used by the SkySafari INDI driver. This driver is for the SS5. That is apparent. SS6 has broken away from the past. It does not recognize this driver.

Yes. 9624 was used and SkyFI is turned off. It does not connect. On CloudyNights, the specs said they were cutting a new path. Well, the get /setserial request is a new path.
Last edit: 6 years 2 weeks ago by John Robison.
6 years 2 weeks ago #24031

Please Log in or Create an account to join the conversation.

Well, I'll update the documentation to indicate that SkySafari 6 is not compatible with the driver. If anyone wants to look into handling SS6, be my guest. You can also contact them to request INDI support.
6 years 2 weeks ago #24040

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello knro,

This looks to be the case. However, the connection is USB to mini USB to the AstroEQ. The AstroEQ has an ST4 port. If the ST4 port was attached to PI then communication would be different. I think this might be a different option to investigate. I have a few cables to investigate.

All communication to scopes are either Ethernet or RS232. As such, USB to USB is similar but not actual. In Windows, the AstroEQ works fine under EQmod and ASCOM over the USB port. There, COMX is used. Trying to think outside the box.
6 years 2 weeks ago #24053

Please Log in or Create an account to join the conversation.

Time to create page: 0.843 seconds