Hitchhiker wrote:

. "Believe me, both these environments can equally challenging with a 7/8/10" tablet swinging around your neck."

This, for me, is key.  Despite having a spectra strap to hold the tablet on my person, it is so much easier to be hiking and trimming runners, which is an active role for me as well as nav/tactics. Using the watch for data to relay time to layline, time to marks, TWA at next mark etc, to the team really does help. 
 

Awesome. Exactly what I built it for.

RichardScanlan wrote:

Im trialing RaceData2 on android, looks very good.

Pinging start line both pin and starboard appears at the gps location on the boat not the bow..

Expedition sets it at the bow but RD 2 sets it at the stern where the GPS physical location is.

botat length setting n RD2 makes no difference as to where the ping mark appears?

Please advise how to correct this.


I note that Nmea Remote for IOS and Ventus PRO also places the mark where the GPS is and not offset to the bow. 

Thanks, will test this immediately.

sailing4life wrote:

Hey Campbell,

I just finished a regatta using RaceData, and noticed there is quite a lot of lag in the numbers displayed.
For example in the prestart the time to gun was between 1 and 3 seconds later than the actual time in expedition. 
Is there any way to decrease this lag?

There will be some network conditions that might slow down the data transfer.

What device?

 

sailing4life wrote:

It was on a ipad mini

I am considering using a device timer set by the Exp race timer for time to gun, will push it up the priority list.

Here are a few tips:
Cheaper, consumer grade routers can throttle or buffer UDP broadcasts
Use 5GHz if possible, 2.4GHz is more congested and has higher latency

iPAD:
Go to Settings → Mobile Data → Wi-Fi Assist — check is OFF
Check Settings → WiFi → [your network] → Low Data Mode — should be OFF
Make sure the iPad isn't in Low Power Mode (Settings → Battery)