Balto Beacon User Guide
Balto Beacon User Guide
[edit | edit source]This guide is for SAR team members and handlers using Balto Beacon in the field.
Overview
[edit | edit source]Balto Beacon connects to your Loko hardware and shows live positions of every dog on a map, while also relaying those positions to your team's shared CalTopo map so incident command and other field teams can see them too.
Before You Go
[edit | edit source]Hardware needed:
- 1× Loko Ground unit (carried by the handler or base team)
- 1× Loko Air unit per dog, mounted on the collar
Checklist:
- Charge the Ground unit and all Air units fully before deployment.
- Confirm each Air unit is securely mounted on its dog's collar.
- Power on the Ground unit.
- Open Balto Beacon on your phone.
- Confirm Bluetooth is enabled on your phone.
Pairing / Connecting to Hardware
[edit | edit source]Balto Beacon uses a remembered device system: once you've confirmed a Ground unit in the app, it will be recognized automatically on future launches without re-pairing.
- From the main screen, open the device scan/connect view.
- Select your Ground unit from the list of nearby devices.
- Confirm the connection. The unit will now appear as connected, and any Air units reporting through it will begin to populate on the map.
Naming Trackers
[edit | edit source]Each tracker (dog/Air unit) can be given a custom name (e.g., the dog's call name) so it's easy to identify on the map and in CalTopo. Tap a tracker's entry to rename it.
Reading the Map Screen
[edit | edit source]The main map screen shows:
- Live position for each connected tracker, updated as fixes arrive.
- Track lines — a trail showing where each dog has been during the current session.
- Battery gauge — a fuel-gauge style indicator per tracker, showing estimated remaining charge.
- Compass heading — your current heading, shown relative to your position.
- Distance to tracker — live distance from your position to each connected dog.
CalTopo Integration
[edit | edit source]Balto Beacon automatically relays tracker positions to your team's CalTopo Shared Location map, so anyone with access to that map (incident command, other teams) can see live positions without needing Balto Beacon installed themselves.
Notes on CalTopo uploads:
- Uploads are movement-filtered — Beacon avoids spamming CalTopo with redundant fixes when a tracker isn't moving.
- If your device loses cellular connectivity, Beacon buffers positions locally and backfills them to CalTopo automatically once connectivity returns. You will not lose track history due to a temporary outage.
Running in the Background
[edit | edit source]Balto Beacon is designed to keep tracking and relaying positions even when the app isn't in the foreground:
- iOS: Beacon continues receiving and relaying positions while running in the background.
- Android: Beacon runs as a foreground service so tracking continues while you use other apps.
Battery Life Expectations
[edit | edit source]Based on field testing, Air unit battery life is approximately 3 hours 10 minutes to 3 hours 45 minutes at a 5-second fix interval. This currently falls short of a typical 4-hour SAR assignment — plan accordingly:
- Start assignments with fully charged Air units.
- Consider carrying a spare charged Air unit for long assignments.
- Battery life work is ongoing; check with your team lead for the latest guidance.
GNSS Fitness Mode
[edit | edit source]Loko hardware supports a GNSS "fitness mode" that reduces position jitter for moving targets (i.e., a working dog). This generally results in smoother, more accurate tracks and should be left enabled for field use unless directed otherwise.
Troubleshooting
[edit | edit source]| Symptom | Likely cause | What to do |
|---|---|---|
| Ground unit won't connect | Bluetooth off, or unit out of range/not powered on | Enable Bluetooth; confirm unit is powered and nearby |
| Tracker missing from map | Air unit out of LoRa range, dead battery, or link dropout | Check unit battery; move closer to reduce range; gaps will typically resolve as connectivity returns |
| Track has gaps | Radio collisions/link dropouts (not a GPS failure) | No action needed — onboard logging on the hardware preserves the full track even if the live link drops |
| CalTopo not updating | Cellular outage on the phone running Beacon | Beacon will backfill automatically once connectivity returns |
| Short battery life on Air unit | Expected at current hardware generation (~3h10m–3h45m at 5s interval) | Plan for assignment length; carry spares for long assignments |
Getting Help
[edit | edit source]Contact your team's Birchwood Limited point of contact for further support.