3. On the Linux host, use the Linux tool / application to send the command to the device that will run the SynScan App. Uses the UDP port 11881 for the SynScan Mobile command set using the IP address of the device of "SynScan serial communication protocol" and TCP port 11882. The command set is in the following location.
Looking at this sentence, I think that UDP 11881 is the port setting of SynScanApp (Smartphone).
192.168.4.1 (← INDI mount)
TCP 11882 (serial communication)
How is the setting?
I ordered a wireless LAN adapter.
When it arrives I will check the connection with INDI.
I am using the SynScanalTAZ driver.
The rack is not EQ but ALTAZ.
The INDI driver is SynScanAltAz.
This driver is for AltAz mount.
This driver must be connected directly to the mount.
Therefore, port setting for serial communication with the mount is necessary.
Upon investigation on the net, UDP 11880
It seems to be a serial communication with the mount, but in your description, TCP 11882 looks like a serial communication with the mount.
It is Skywatcher AZ GTi ← → SynScanAltAz.
← → becomes wireless serial communication.
The explanation of Skywatcher assumes that SynScanAPP is started, but here we connect directly to mount with the wireless serial port of Skywatcher AZ GTi mount.
The possibility is UDP 11880 or TCP 11882.
If you are using serial communication using both ports, you can not connect at this time. (Since the driver only recognizes one port)
When using a smartphone application (this is a virtual wireless handle controller) or a hand controller, it becomes the SynScan driver.
Currently, Skywatcher Alt - Az driver thinks that "Park" function and "Unpark" function are not working properly.
I can not use it unless I avoid that part, so I think that people who use this driver for the first time with INDI are confused.
The lack of the most important function is that position information has not been acquired since the mount is not synchronized with the north pole which is the home position when the driver is turned on. Since there is no positioning information, the position information does not operate properly in the initial state.
Since the EQMOD driver has acquired home position synchronization and position information, the parking function functions normally because the mount information is correctly stored.
Skywatcher Alt - I think that if you can synchronize the Arctic information where the Az driver is at the mount and home position, and reset the mount position information with the home position information, you can avoid the problem.