Then it is NOT,IMHO, 100% guaranteed to be the Synscan driver at fault - I have been using it for 9mths with no problems AND I USE WIRELESS ethernet RPI not wired - mount connection is wired obviously. OK your mount is a EQ and my 2 "Grab & Go" are AZ but the SW protocol is so similar for both.
What type of RS232 USb Adapter are you using (FDTI,Prolific etc) could this be the source of your problem. I have used both Prolific and FDTI adapters but settled on FDTI - more expensive but never a problem (touch wood)
Another test could be to use Indi Synscan driver on the RPI connected to Synscan App(via TCP port 11882 or 11885 - check I cant remember), via Serial for the mount ,running on Windows with the same cables/adapters and see if that drops the link. The Synscan App(pro) has some statistics (repeats,speed in MSec groups) and can perform min network tests.
Are you sure that the Router(and cables) are working ok ? Most routers have a log which might shed some light on the problem (but dont hold your breathe
)
As I say mine works so I would have hoped yours would too all things being equal. But being computer software etc nothing is 100% true.
Sorry Jasem but last time I tried EQMOD (on Linux/Indi) it would not drive my SW GoTo AZ mounts and using Synscan Indi driver by itself had parking issues. Can you guarantee EQMOD will now work with my SWAZGoto's without problems (no such thing as none
). Hence the use of the handset !
I did try the SWAZGTI Indi driver but that was even worse - in my experience
If EQMOD could drive all my mounts safely and 95% of the time that would be great but I do not wish to loose Clear Skies times - too few as it is.
I quite understand the monolith task of supporting numerous protocols (even if the SW protocols have common code) and appreciate and thank you (and others) for your devotion and hard work
P.S. I was an Windows EQMOD user for 2yrs .