Many thanks Campbell!

I haven't had any problems on Win 11. Expedition seems to run slightly faster.

There was a topic on this forum that mentioned it a few months ago.

 

Campbell_Field wrote:

DuncanR wrote:

Campbell, welcome to the glasses-as-assets club ... unfortunately.  I understand your pain, I am looking for a pair of glasses with windscreen wipers .... solar powered.
If I understand you correctly, in normal mode the Getac sits down below and talks to the instruments (wired or wireless, does not matter unless the Mesa dies) and the Mesa on deck shows a Getac screen capture via RDP or whatever app you like,  Additionally however, if the Getac dies, the Mesa is loaded with a copy of Expedition which can be fired up and which gets and sends data to instruments?  Or are you running two entirely parallel boxes, both running Expedition separately?
Cheers

Tardy reply - sorry.

I typically run Expedition on both machines set up identically with data Tx/Rx Exp data over UDP - the primary machine below connected to the instruments and set as a slave in Exp Settings so any calculated data in the Mesa2 is passed through the remote channels. Should the deck screen die it is easy to return the downstairs machine to primary and carry on.

I find the data is a lot faster and more reliable this way than using RDP or other screen mirroring solutions, and should the connection be dropped can easily be reconnected using Exp Network reconnect.

For some inshore racing I connect the Mesa2 directly to the instruments over WiFi saving the weight and power consumption of an extra machine below.

This seems like a good option. I was messing around with it at home and couldnt get my tablet to connect to the laptop. It seems like it should be pretty simple. Any tricks?

Haha. Yeh I did realize that when I had a look at the yb tracker after the race start.

I might be able to figure it out with enough playing. I can send the data just not receive it.

The way Cambell sets it up seems like a good way of doing it.

Stroppy wrote:

Campbell_Field wrote:

DuncanR wrote:

Campbell, welcome to the glasses-as-assets club ... unfortunately.  I understand your pain, I am looking for a pair of glasses with windscreen wipers .... solar powered.
If I understand you correctly, in normal mode the Getac sits down below and talks to the instruments (wired or wireless, does not matter unless the Mesa dies) and the Mesa on deck shows a Getac screen capture via RDP or whatever app you like,  Additionally however, if the Getac dies, the Mesa is loaded with a copy of Expedition which can be fired up and which gets and sends data to instruments?  Or are you running two entirely parallel boxes, both running Expedition separately?
Cheers

Tardy reply - sorry.

I typically run Expedition on both machines set up identically with data Tx/Rx Exp data over UDP - the primary machine below connected to the instruments and set as a slave in Exp Settings so any calculated data in the Mesa2 is passed through the remote channels. Should the deck screen die it is easy to return the downstairs machine to primary and carry on.

I find the data is a lot faster and more reliable this way than using RDP or other screen mirroring solutions, and should the connection be dropped can easily be reconnected using Exp Network reconnect.

For some inshore racing I connect the Mesa2 directly to the instruments over WiFi saving the weight and power consumption of an extra machine below.

This seems like a good option. I was messing around with it at home and couldnt get my tablet to connect to the laptop. It seems like it should be pretty simple. Any tricks?

I'm back. Did you resolve? You do need to be diligent in specifying the IP addresses etc for the Exp instrument selection in the Instruments Network port, as well as being sure that you have set tx on one machine to match rx on the other, and vise versa.