See, nobody cares
- Feb 13, 2017
Have you guys, that are having issues, tried calling Kestrel?
Hey, Kestrel folks. I’m having the same problem as Bronc. Followed the same steps and can’t get the firmware to update. Do I need to send the unit back for service?
Thanks much for responding.We are looking into why this is happening. Can anyone with issues not getting prompted for fw update let me know:
Current FW Version
Current Hardware Version (HW)
These can be found in the Kestrel under Main Menu->About->Version
Dumb question. When you send an update, do I just go to the Apple app store to receive the update?If you have had any issues with using Zero Angle and getting bad results, there will be a fix for this with FW update 1.37, which we should be pushing out shortly.
Just pair you Kestrel to your phone and the phone app will check your fw version and if out of date will ask if you want to update the fw. The app handles the update. No need to go to the app store.Dumb question. When you send an update, do I just go to the Apple app store to receive the update?
I have a question, more out of curiosity than anything:
The 4DOF Kestrel has a few range finders that will connect to it. On the Kestrel site it says if you have a BT enabled LRF, contact the manufacturer and ask them to enable the Kestrel protocol. Kestrel lists Leica Rangemaster CRF 2800.com, Leica Rangemaster CRF 3500.com, and Leica Geoid 3200.com, Vectronix Terrapin X and PLRF 25-C, and Bushnell Elite 1 Mile CONX as LRF that communicate with the 4DOF Kestrel, but the non-4DOF version can communicate with additional units, like the Sig 3000BDX. I'm assuming the 3000BDX has the Kestrel bluetooth protocol, so why won't it connect to the 4DOF?
The assumption that they are using Kestrel protocol is not correct. They are using a different protocol that our 4DOF units cannot use. Therefore the LRF manufacturers would need to adapt their units to use Kestrel Protocol in order to connect with our 4DOF units.
I am reffering to linking the 4dof kestel with the HORNADY 4dof phone APP (Not the kestrel app). Is that what you are referring to?To use the wind vane:
1 link the app and Kestrel
2 set environment to live
3 acquire DOF and enter distance
4 Acquire wind dof and speed, but do not press acquired button the second time to stop acquisition, it will remain in the acquisition mode and can be mounted to the wind vane. Be sure your Display Auto shutoff has been turned to off so it doesn't go to sleep on the vane.
Such a pain in the ass for sure. like I have three different loads for one rifle.... Its such a pain in the ass.
So what I have been doing is still using the app, think just synccing it up with my kestrel for all the environmentals.I'm really torn, I got this 4DOF with the Leupold Scope promotion, I have been messing around with the app and I *REALLY* like the 4DOF concept, but like you, I have have several rifles I want to use this with, sometimes on the same trip and have different loads with them. in a 4 hundred dollar device, I can't imaging memory is a limitation at all. I should be able to get 100 profiles into about 5 dollars worth of memory chip without worrying about it.
I may wind up selling this and getting an elite, but then I am back to the AB solver and not the 4DOF. I wish they'd just unlock it. I also wish this one would do the range card function. That's sort of a PITA too
What do you estimate the distance was between the Kestrel and the 2800.com?
You can write more than three profiles in the Kestrel app, but can only load three at a time. Probably in the design to keep cost down.
If you want more than 3 profiles, buy a 5700 Elite or a 5700X
Yes, the Kestrel will not work with a short range. I think it is set for 30 yds.I can have them touching and it makes no difference (I've tried). I think I've found the problem, though. If I range something < 25Y, it does not work. > 25Y seems to be working (aside from aforementioned distance-between-device issues, which is unfortunate). I was testing around the house, so all measurements were below 25Y. This seems like a bug, however unlikely it is that you might try to range for ballistics at these short distances.
I'm sure a LOT of people test this out around the house, and it may be leading to some serious confusion/concern about the reliability. I went outdoors, and was able to range 30Y (and greater) with no issue and get ballistic correction values back/the Kestrel updated with the measured values.
Can you reproduce this behavior? Hopefully an easy fix!
[Edit: I tried to manually set a distance below 25Y on the Kestrel and it will not allow it. This definitely seems to be the issue. It causes the Leica to 'freak out' a bit, I suspect because it's expecting return data. Is there any reason for this restriction other than the unlikely need to range at < 25Y? If not, hopefully it's an easy fix.]