Its strange in that I did an experiment using a PI Zero W using UDP 11880 via SER2NET with a USB adapter connected to the Zero W using the Indi Skywatcher ALTAZ driver on another RPI3 which works in "Direct Serial Mode" using ALTAZ driver - it fails after the connection is made ("handshake failure") - the reason why I say this is strange is If I swop RPI3/Indi for Synscan app on windows this set up works perfectly .
1 I would have expected the Indi ALTAZ driver over UDP via the SER2net to have worked as it is transparent to Indi Driver which is unaware of the hardware connections being used -- Or is it??????
2. Is the Indi Driver ok but its a timing issue - i.e. it doesn't get a response within a timeout (NOTE I did NOT change any timeout parameters in the Driver Connection Option)
3. What are the reasons the driver creates an error "Hand shake error" ?
I have been debugging mount with few modifications on the ALT AZ drive code . I am using UDP with 11880 port and i am not seeing any response from the mount back. Basically it's been timing out at tty_read method.
What my doubt here is , does it need UDP protocol to work with mount or is it going to be Serial?
No the chip is a CH340G which I use over many environments and works as well as the FTDI chipset. As I say the same CH340G adapter works well with Synscan App when on Windows or Android or when used directly on RPI3 via Serial TTYUSB0. I am guessing that it was the UDP route that is the issue as I have written a serial-UDP bridge routine for Ardunio's (ESP286/ESP32) and had issues with the first command sent from the Synscan software. However its not that as the Wireshark is reporting that the Mount has replied with what looks like a valid reply ( I think) so the UDP/Wireless etc is working its the hand shaking is the issue.
My SER2NET line is different as it uses UDP instead of RAW and 11880 as the port number and is running on the RPI Zero W - but as say I dont think ,famous last words,that is the problem.
I will change the timeout to a smaller value as TKOTTARY has done and see if it makes a difference - but setting it to a lower figure seems counter intuitive to me but if that produced a reply from TKottary's mount then thats a good thing.
Had a quick look at the code to see what I could find but fell asleep reading it as I have not done C for a good while I will let the experts do that
A little worrisome is to handle SkyWatcher 's Wi - Fi. If serial communication is possible with only one port, it can be set with the INDI driver, but if it is set to communicate using multiple ports, the current INDI driver can not communicate.
In the latest version of SER2NET there is real UDP comms no need to use Serial at all and this is what I used and works very well with both Windows and Andriod SynScan App using UDP NOT serial
So the Synscan app(Windows or Android)is set to use UDP and expects the Zero W to be listening on port 11880 and the IP address set in SynScan App is that of the ZERO W . The ZERO W is conneced to the SWAZ Mount via a USB Adpter (TTL at Mount END) - THIS WORKS even in the field
So using the same set up BUT replacing SynScan App with Indi/Kstars/SkywatcherALAZ I would expect that this would work. As I have said Wireshark shows the network is connected to the mount and the Mount answers the Indi/Kstars initial handshake of ":e1" with ":e1=010982" but the Indi driver fails to reply and the log says the handshake has failed BUT with a result 0
Even though the Indi driver and mount dont work the UDP communications is working - initially anyway.