• Top Shot Throwback Contest - Only a Few Hours Left To Enter!

    Tell us about your best shot or proudest moment on the range this past year! Winner gets new limited edition Hide merch. Remember, subscribers have a better chance of winning!

    Join contest Subscribe
  • HideTV Turns 1 Next Week!

    To celebrate the anniversary, we’ve got a full week of planned of exclusive giveaways, special live streams, limited-edition merch, and more surprises along the way. Keep an eye out!

    View thread

AB Elite devices are not synchronizing

RenoBravo

Private
Minuteman
Dec 9, 2023
1
0
Reno, NV
I have the following devices and would like some help figuring out the best connectivity topology to integrate them all and push the real-time target card to my Tactix 8 watch.

- Garmin Tactix 8 with Applied Ballistics (Elite license)
- Kestrel 5700X Elite (AB Elite license)
- Sig Kilo5X rangefinder (BDX-X, BDX-U) Says Ultralight for the device but no upgrade path I can see.
- Garmin Cero X1 chrono
- iPhone 16 with AB Quantum, Garmin Connect, Kestrel Link, and Garmin Shotview.

Latest firmware installed where needed.

So,
I’d like to be able to laze a target with the Kilo5X and use the Kestrel for my Environment variables (wind, temp, barometer etc) and use the chrono for real-time muzzle velocity data. I’d then like to either use Kestrel or AB Quantum on my phone as the solver and push the firing solution to my AB enabled Tactix 8 watch.

I’ve been able to pair and see the Kestrel, the Tactix 8 watch, and the Kilo5x in AB Quantum on my phone, but AB only allows one device at a time to be active/connected.

This has been the primary source of my frustration but on top of that the results on my watch do not appear to mirror what is in the AB Quantum on my phone, even though I do see the profile is being sync’s on my watch.


The elevation on my watch is off by a few .mils or more and the range never updates, as well as the direction. It appears to be working but not really working. Basically my watch is showing results that conflict with the firing solution in my phone, so the watch results can’t be trusted, thus worthless.

Am I missing something obvious in my AB configuration that allows for live updates?

Is there a better workflow for the device connectivity?

Should I be using another app to join all of these devices in a shared network? Or is there a daisy chain topology that would be better suited? Just really surprised AB only allows the single device at a time thing.

Any help or suggestions would be greatly appreciated!!

Thanks in advance

V/r,

-rB
 
Similar setup here - AB binos, AB kestrel, AB tactix watch, AB app. Dealt with similar issues recently.

Wherever possible, push out the same profile from one source to the rest. If you're sure environmentals are the same for a given solution and you're still seeing different results, it's likely slight differences in CDM version giving you trouble. I was able to resolve this by making one profile that I trust on my AB quantum app, and pushing that to my kestrel and watch. My kestrel also likes to change itself to using G7 solving randomly but that's probably something i'm screwing up somehow.

I don't think I can push profiles to my binos so those are being used exclusively for lasing, not putting much stock into their profile.

If you're 100% sure you've synced the profile to your watch, it simply has to be environmentals. Punch in the same number environmentals in the menu in the watch as you have on your app, they should line up. Repeat with kestrel. If something is mismatched, the profile simply has to be set up wrong, yards vs. meters, etc. or you have a different CDM version. It really can't be anything else so check over everything.

The chrono must exist outside of all of this, I don't think you can live-update your average MV based on your chrono results.

I also don't think you can take input from laser + Kestrel on your phone and then live-update that through AB Quantum to your watch. If I remember right, you can link the laser + Kestrel to your watch at the same time. You can set up to have your LRF push its most recent distance to update your current target on the watch, and that's pretty fast. As for the kestrel side of things, I think you can have it set to auto-update every 5 minutes, or manually update environmentals on command. The Kestrel is a bit clunky on the watch (tactix 7 FWIW).

All that said, each tool does a great job separately, especially once the profiles are nicely in line with eachother. During matches, I typically have my Kestrel connected to my phone, ping it for env data before a stage and manually punch in range from LRF. I use the watch more as a target card for stages with multiple target CoFs. It would be great if the phone/watch handled inputs from both devices more intuitively, but I can't imagine integrating hardware from 3+ manufacturers will ever be seamless. All of the involved companies are also pushing new stuff out constantly, so this is subject to change and I'm happy to be corrected. Feel free to DM if you want a hand with fixing up your profiles.
 
The Garmin Chrono does not sync into the AB ecosystem at all. There is no method of doing so.

AB Q can only have 1 device connected at once. It's a huge issue as far as I'm concerned, but as of now, that is the way it is.

You can connect the Kestrel and the Sig to your watch, as they have different protocols to allow that. I don't have an Sig to test with, but some LRFs will allow you to connect the Kestrel directly to them. But it will NOT act as a bridge to get weather and range data to your phone with AB Q.

As for why your information on your watch is different than what is on the phone, it just takes some tinkering to figure out what is different between the two. Is the weather data causing a difference on your phone and that isn't being sent to the watch? CDF set on your phone that isn't being sent correctly?

You can try to send a support request from within AB Q and ask what the issue is, see if they can help determine the cause of the differences.
 
  • Like
Reactions: sidetoss20