Wi-Fi and hotspots
Copying the main clock, handing over logs and getting the event setup all need one thing: the devices on the same Wi-Fi network or phone hotspot. It doesn't need internet access. The devices talk to each other directly, which is what makes it work at a control with no signal.
Ways to get one
- A travel router, such as a GL.iNet GL-MT300N-V2 (Mango), powered from a USB power bank. It makes a Wi-Fi network wherever it is: in the sweep car, at the finish, at service or at HQ. This is the most dependable option.
- A phone's hotspot. One crew phone shares a hotspot and the others join it. It usually works, but try it with those phones before the event.
- Existing Wi-Fi at service or HQ, if it lets devices see each other (see below).
Check these once, before the event
- Device isolation off. Guest networks, hotel and public Wi-Fi, and some routers keep devices from seeing each other ("AP isolation", "client isolation", "guest mode"). With isolation on, none of this works. It's off on a GL.iNet router unless someone turns it on.
- "No internet" warnings. When a phone joins Wi-Fi with no internet, Android may say so and offer to disconnect. Choose to stay connected. The phone carries on using mobile data for the internet if it has any, and the Wi-Fi for Rally Clock.
- Android 17 and later: Rally Clock needs the Nearby devices permission. It asks at first launch, and if it was refused, the app shows a notice with an Allow button.
- iPhone and iPad: Rally Clock needs Local network access. iOS asks the first time a screen looks for other devices: tap Allow. If it was refused, turn it on in Settings → Privacy & Security → Local Network.
- Windows laptops: allow Rally Clock through the firewall when Windows asks, and set the Wi-Fi network to Private, not Public (Settings → Network & internet → Wi-Fi → the network). A Public network blocks other devices from reaching the laptop.
- Join every device to the network once at home, so it reconnects by itself in the field.
If devices can't see each other
- Same network? Check the Wi-Fi name on both devices. A phone that dropped back to mobile data is not on the network.
- Is the other device offering anything? A device only appears while it's the main clock, collecting logs, or handing out a setup.
- Android 17: is there a notice saying it's not allowed to reach others on this Wi-Fi? Tap Allow.
- iPhone or iPad: is Local Network on for Rally Clock (Settings → Privacy & Security → Local Network)?
- Windows: is the network set to Private, and was the firewall prompt allowed?
- Isolation: try a phone hotspot instead. If it works there, the Wi-Fi network is keeping devices apart.
- Restart the app on both devices. It reopens its connection to the network when it starts.
For whoever runs the network
Rally Clock uses UDP port 47801 (finding devices, and clock timing), TCP 47802 (log hand-overs) and TCP 47803 (event setups), all on the local network only. Hand-overs aren't encrypted, so use a network you control.
For the crew, Working together (PDF) puts the network, the main clock, hand-overs and setups on a few printable pages.