I am trying to get my Vixen SXD2 mount with Starbook 10 working with Stellarmate,
When I connect a ethernet cable from the RpI4 to the Starbook 10 it gives an address of 169.254.0.1 (as it did on my Intel NUC under Ascom which worked pefectly)
But it will not connect and Ekos is showing 169.254.1.1 so I change it to 169.254.0.1 and still won't connect2021-04-09T22:25:37: [ERROR] Connection failed2021-04-09T22:25:37: [ERROR] Couldn't connect to server2021-04-09T22:25:37: [INFO] Creating HTTP handle for 169.254.0.1@80Any ideas much appreciated
Got the same problem with my Vixen Starbook 10 first. I suppose the Starbook 10 the does have a static IP in his own /24 network (subnetmask 255.255.255.0). On the actual version this is 169.254.0.1. If you choose "Direct Ethernet" on your StellarMate network connection menu (upper right on the StellarMate VNC Screen) StellarMate want to have 169.254.0.1, two. But he don't can, because this address is allready used by starbook 10, so StellarMate hops to the next network and chooses the IP 169.254.100.1. And now the problem is completed. Both devices are in complete diffrent networks and can't talk to each other. The StellarMate has to be configured that he don't choose 169.254.0.1 with "Direct Ethernet"
That's how I solved the problem:
1. Connect to StellarMate by VNC
2. On StellarMate go to Preferences->Advanced Network Configuration
3. Choose "Direct Ethernet" and enter settings (wheel icon on the lower left)
4. Go to the "IPv4 Settings" Tab
5. Under "Method" choose "Shared to other computers"
6. Under "Address (optional)" add 169.254.0.2 for "Address", 24 for "Netmask" and leave "Gateway" empty
7. Save Settings (lower right) and leave the "Advanced Network Configuration"
8. Connect StellarMate, addionally to your Wifi connection, to "Direct Ethernet" (network icon on the upper right of your StellarMate Screen)
9. Now Ekos should connect to your Vixen Starbook 10. Don't forget to reconfigure Ekos to use 169.254.0.1, as you have written on your question. This still have to be done.
in SM OS v1.5.8, it should work right away without having to do the trick suggested above. I haven't tested this with Starbook 10, but tried it with a direct connection to a PC and the auto-configuration IP was OK.