Offline
That is the puzzle. We aren't having any issues connecting and using the Iridium GO! with Sailmail, Squid, QTVlm, or PredictWind. The 4 applications all work fine and Expedition succesfully connects to the Iridium GO!, but nothing further.
Offline
Given Exp can get the Go to dial up and connect, that does suggest Windows is routing the internet traffic elsewhere.
Last edited by Nick (3/30/2024 1:36 pm)
Offline
When it stopped while "Waiting for server" the messages says:
"The server name or address could not be resolved."
Why would the Windows treat Expedition differently than the other applications that are working? I haven't been able to work that out.
Offline
I don't know that. Maybe it is a different Windows call etc.
What other networks do you have? Maybe Windows thinks one of them is the internet connection, as per the Exp help.
Have you looked at the NCIS and Metric topics in the Exp help?
Email would be a lot easier than this ...
Offline
Perhaps helpful? As I am experimenting with Glasswire, it seems Host Process for Windows Services needs to be enabled for Expedition. I am guessing this is DNS related. Without that enabled, I get the "The server name or address could not be resolved."
Offline
we have used an iridium go with expedition but as suggested via predict wind.
We now have the grown up version iridium exec ... it is brilliant with predict wind!!! -- the software only downlopads YB plus predict wind files wihtouth much management -- so when we did the azores and back last year we used amazingly little data... is it time to talk to the neighbours Nick?
Offline
I'm glad. PredictWind sells the unit and the GO was useless with PredictWind. Just horrible.
Couldn't get PredictWind stuff with the GO, but the GO with SailMail is great. Even Expedition using the GO to connect wasn't nearly as good as SailMail. You're just limited to the models available in SailMail, but that's not too bad. If I do my next Mini Globe 5.80 race, I'll definitely get the GO Exec and the issue will go away.