×

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

Bi-monthly release with minor bug fixes and improvements

Can not connet my Dobson SW Flextube 300P SynScan via Wifi

  • Posts: 10
  • Thank you received: 0
Yes indeed. I connected the SynScan to my home network via WiFi; I can use it through my android tablet with the SynScan App, who shows the IP number found by the scanning of the net. More over the same IP number appears on che connection list of the router (and so the Raspberry does), so I suppose the Raspberry shoud not have problems connecting the SynScan which lays on the same network.
2 years 8 months ago #73235

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

Is the mount already aligned using 2-star alignment?
2 years 8 months ago #73238

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

  • Posts: 10
  • Thank you received: 0
In reality, during my attempts I always used the bright star alignment; I can't suspect any difference in order to have the telescope able to be connected by the INDI driver.
Today I'll try with the other alignment methods, if it works I'll remain curious about why a different alignment method makes the difference: in the end any method only define the sky model used by SynScan to calculate the movements of the telescope to point at a new object, I can't see any reason to deny the connection; that seems to me a pure software choice for which I can't understand the reasons.
2 years 8 months ago #73257

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

It shouldn't make a difference. I just meant that ANY alignment method would work. At this stage, please enable the log, there is some communication issue between you and the mount.
2 years 8 months ago #73258

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

  • Posts: 10
  • Thank you received: 0
Here are the logs I've got:

[2021-07-06T17:43:30.085 CEST INFO ][           org.kde.kstars.ekos] - Websocket Message "{\"type\":\"device_property_set\",\"payload\":{\"device\":\"SynScan\",\"property\":\"CONNECTION\",\"elements\":[{\"name\":\"CONNECT\",\"state\":1},{\"name\":\"DISCONNECT\",\"state\":0}]}}"
[2021-07-06T17:43:30.147 CEST INFO ][           org.kde.kstars.indi] - SynScan :  "[INFO] Connecting to 192.168.1.109@11882 ... "
[2021-07-06T17:43:30.149 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] Connection successful, attempting handshake... "
[2021-07-06T17:43:30.149 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] CMD <Kx> "
[2021-07-06T17:43:30.153 CEST INFO ][           org.kde.kstars.indi] - SynScan :  "[ERROR] Serial read error: Read Error: Connection refused. "
[2021-07-06T17:43:30.154 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] Handshake failed. "
[2021-07-06T17:43:30.154 CEST DEBG ][           org.kde.kstars.ekos] - "SynScan"  is disconnected.
[2021-07-06T17:43:30.155 CEST INFO ][           org.kde.kstars.ekos] - "SynScan failed to connect.\nPlease ensure the device is connected and powered on."
 
2 years 8 months ago #73274

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

  • Posts: 10
  • Thank you received: 0
[[2021-07-06T17:43:30.147 CEST INFO ][           org.kde.kstars.indi] - SynScan :  "[INFO] Connecting to 192.168.1.109@11882 ... "
[2021-07-06T17:43:30.149 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] Connection successful, attempting handshake... "

This seems to me to confirm that the ethernet connction does exist.

[2021-07-06T17:43:30.149 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] CMD <Kx> "
[2021-07-06T17:43:30.153 CEST INFO ][           org.kde.kstars.indi] - SynScan :  "[ERROR] Serial read error: Read Error: Connection refused. "
[2021-07-06T17:43:30.154 CEST DEBG ][           org.kde.kstars.indi] - SynScan : "[DEBUG] Handshake failed. "
[2021-07-06T17:43:30.154 CEST DEBG ][           org.kde.kstars.ekos] - "SynScan"  is disconnected.

This, instead, seems to show an error in the code which continues to use a "serial" connection while it should use the ethernet one.
Am I wrong?
Last edit: 2 years 8 months ago by Marco Voli.
2 years 8 months ago #73303

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

No it's still over TCP/IP. There is no response from the mount. You can use socat to connect directly.
socat - UDP:192.168.1.109:11882

Then after connection, simply type in Kx and press enter. Do you get any response?
2 years 8 months ago #73308

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

  • Posts: 10
  • Thank you received: 0
I can't try right away, I hope I have the chance tomorrow or later.
Meanwhile, I got an idea: is it possible that the connection to the SynScan App on my tablet can inhibit other connections such as the one attempted by the INDI driver on the Raspberry?
Last edit: 2 years 8 months ago by Marco Voli.
2 years 8 months ago #73327

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

  • Posts: 10
  • Thank you received: 0
Here is the result of the socat command.

stellarmate@stellarmate:~ $ socat -v - UDP:192.168.1.109:11880
Kx

> 2021/07/09 21:04:23.389731  length=3 from=0 to=2
Kx
^Cstellarmate@stellarmate:~ $

Using the port 11882 after the Kx command I get a "Connection refused"
 
2 years 8 months ago #73362

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

  • Posts: 10
  • Thank you received: 0
So... no any more ideas about what's happening?
2 years 8 months ago #73566

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

Have you tried using SkyWatcher Alt-Az driver?
2 years 8 months ago #73570

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

  • Posts: 10
  • Thank you received: 0
In the end it does work!
I used the Alt-Az driver as you suggested, and finally I got the SynScan connected, and StellarMate able to drive the mount.
Thanks a lot.
2 years 7 months ago #74273

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

Time to create page: 0.293 seconds