After upgrading to 12.9.5, setting up a new instrument network connection with type expedition tcp port 5010, ip addres blank or 127.0.0.1(in earlier version this ip address field was uneditable). When running the command netstat -a i should have seen that there is a listening port 5010 so that expedition is ready to accept a connection, but there is no line in the output showing that expedition is able to accept a connection to port 5010.

Before the upgrade, Expedition acted as a TCP server accepting incomming connection to port 5010. Now it acts as a TCP client.

Last edited by Martin.Elms (9/09/2026 8:42 pm)

Thank you. I have now reprogrammed my app ExpPinger to act as a server instead, so Expedition connects to it instead of the other way around. So the the network issue i had is fine now. I use the connection to send data to expedition, like:
- Line-end pings, port and starboard.
- Race timer: start with a set number of minutes, sync to the nearest minute, kill.
- Marks: advance to next, step back to previous, ping the active mark.
- Rounding-log entries written into Expedition's event log.

Another thing, could you verify if the variables Sail, SailMark and SailNext is working in 12.9.5? I cannot get it to display in number boxes.

Thank you, found the solution, I had lost my nav polar.