Zulus

Yes, @Jelen talked me through it on the phone kindly but we didn't test it there and then.
All sent across and the program is selected in the zero reticle section and saved via the left button long press.
I'm at a loss then, or at least without getting mine out and remembering what I did to set it up!

It did take a bit of fiddling about but once working it's been great.
 
In the "Ballistic Calculation" item in the scope menu, male sure you set it to "Ballistic Table Call"
That way, the app sends the ballistic table to the scope and when that is done, there is no need for any connection between the scope and the phone.
The range data is applied to the downloaded ballistic table, and the holdover is calculated in the scope and displayed on the reticle
If, in the Ballistic Calculation item in the scope menu you select "Real Time Ballistic calculation" the phone and the scope have to be permanently connected because the scope sends the range data to the phone, the phone calculates the holdover and then sends that back to the scope to display the holdover for that range
AFAIK, no-one has found a use for this particular function :)

Cheers

Bruce
 
In the "Ballistic Calculation" item in the scope menu, male sure you set it to "Ballistic Table Call"
That way, the app sends the ballistic table to the scope and when that is done, there is no need for any connection between the scope and the phone.
The range data is applied to the downloaded ballistic table, and the holdover is calculated in the scope and displayed on the reticle
If, in the Ballistic Calculation item in the scope menu you select "Real Time Ballistic calculation" the phone and the scope have to be permanently connected because the scope sends the range data to the phone, the phone calculates the holdover and then sends that back to the scope to display the holdover for that range
AFAIK, no-one has found a use for this particular function :)

Cheers

Bruce
Oh ok, will go check.
Thank you...
 
In the "Ballistic Calculation" item in the scope menu, male sure you set it to "Ballistic Table Call"
That way, the app sends the ballistic table to the scope and when that is done, there is no need for any connection between the scope and the phone.
The range data is applied to the downloaded ballistic table, and the holdover is calculated in the scope and displayed on the reticle
If, in the Ballistic Calculation item in the scope menu you select "Real Time Ballistic calculation" the phone and the scope have to be permanently connected because the scope sends the range data to the phone, the phone calculates the holdover and then sends that back to the scope to display the holdover for that range
AFAIK, no-one has found a use for this particular function :)

Cheers

Bruce
Would this make sense if you had multiple zeros (different ammo or even different rifles) saved each with their own ballistic table and you had the corresponding table open on the phone for the zero you were using?
 
In the "Ballistic Calculation" item in the scope menu, male sure you set it to "Ballistic Table Call"
That way, the app sends the ballistic table to the scope and when that is done, there is no need for any connection between the scope and the phone.
The range data is applied to the downloaded ballistic table, and the holdover is calculated in the scope and displayed on the reticle
If, in the Ballistic Calculation item in the scope menu you select "Real Time Ballistic calculation" the phone and the scope have to be permanently connected because the scope sends the range data to the phone, the phone calculates the holdover and then sends that back to the scope to display the holdover for that range
AFAIK, no-one has found a use for this particular function :)

Cheers

Bruce
Got it, 👍
 
Would this make sense if you had multiple zeros (different ammo or even different rifles) saved each with their own ballistic table and you had the corresponding table open on the phone for the zero you were using?
You can create as many ballistic profiles in the app as you want, but if you operate the scope in "Ballistic Table Call" mode you can only have one ballistic table in the scope at any one time
If you want to change to a different ballistic profile, you need to send that to the scope by Bluetooth where it will overwrite any ballistic table already in the scope
If you operate the scope in "Real Time Ballistics" mode you could select any ballistic profile in the app, receive range data from the scope and send back holdover data - but for the holdover to be accurate, the ballistic profile you are using to do the calculation would need to be for the same rifle and ammo actually being used plus the scope would need to be set for the correct zero profile

Cheers

Bruce
 
Bloody hell.....
I slipped and fell on the rifle across my back!
IMG_20240303_123917.webp
The air turned red and blue I can tell ya.

Zero was lost and soon regained.
They say every cloud has a silver lining....well after adjustment the reticle is now near centered.
So if your reticle moving sighting system is off center give it a dam good whack ! 🤦
 
Bloody hell.....
I slipped and fell on the rifle across my back!
View attachment 354191
The air turned red and blue I can tell ya.

Zero was lost and soon regained.
They say every cloud has a silver lining....well after adjustment the reticle is now near centered.
So if your reticle moving sighting system is off center give it a dam good whack ! 🤦
Ouch - lucky you didn’t snap the stock Smelly.
🦊🦊
 
I am puzzled.
The Zulus has two methods of utilising the RF and BC - one is to show the adjusted aimpoint as a small cross hair on the original large reticle (which still has the old no longer relevant zero) vertical stadia and the other is simply to reposition the large reticle to show the revised aimpoint.
Sooo why the two - when surely the latter is all you need?
Or am I being picky?
🦊🦊
 
I am puzzled.
The Zulus has two methods of utilising the RF and BC - one is to show the adjusted aimpoint as a small cross hair on the original large reticle (which still has the old no longer relevant zero) vertical stadia and the other is simply to reposition the large reticle to show the revised aimpoint.
Sooo why the two - when surely the latter is all you need?
Or am I being picky?
🦊🦊
I suppose showing both aim points shows you the relevant holdover if you're interested in that sort of thing and also shows you the crosshair has actually moved! I always use the second method and am surprised at sometimes how little it appears to move.
 
What do you do when shooting with a glass scope at ranges longer (or shorter) than the range at which the scope is zeroed?
You can:
a. Use holdover (or hold under) such that some mark on the reticle other than the central mark becomes the aiming point - or you just judge it
b. Dial in - use the windage and elevation turrets to adjust the position of the reticle to a point (usually based on the output of a ballistic calculator) which then becomes the point of aim
Some people prefer holdover -typically hunters who have limited time to aim and take a shot, while others prefer dial in - typically target and long range shooters who usually have plenty time to aim and take a shot
The Arken, with it's options of holdover or dial in, satisfies both groups :)
For what it's worth, my preference when using the Zulus is to have it set for holdover mode so that an aiming mark appears on the reticle, but also have the PiP switched on and actually aim using the reticle in the PiP (which is always in dial in mode)
My main reason for doing this is that, when in dial in mode, the main reticle will stay in it's adjusted position until the rangefinder is used again and the user may not notice this and aim at a target at a different range without knowing the reticle is in the wrong location on the screen
Having the holdover mark on the main reticle gives the user a visible reminder that the ballistic calculator is being used

Cheers

Bruce
 
I am puzzled.
The Zulus has two methods of utilising the RF and BC - one is to show the adjusted aimpoint as a small cross hair on the original large reticle (which still has the old no longer relevant zero) vertical stadia and the other is simply to reposition the large reticle to show the revised aimpoint.
Sooo why the two - when surely the latter is all you need?
Or am I being picky?
🦊🦊
Not sure why you would need both on a digital scope.
I use the Holdover method because seeing the superimposed cross appear reassures me that the Baltic calculator has done its job.
Especially useful with cold fingers where I'm fumbling with the second press of the LRF button. But, as nun hunter has pointed out, between 100 & 200m the movement of the cross is very small.
 
Not sure why you would need both on a digital scope.
I use the Holdover method because seeing the superimposed cross appear reassures me that the Baltic calculator has done its job.
Especially useful with cold fingers where I'm fumbling with the second press of the LRF button. But, as nun hunter has pointed out, between 100 & 200m the movement of the cross is very small.
Thanks.
Must be really cold down your way J!
🦊🦊
 
Today I did three things.
Firstly i did away with the set trigger on my cz527 222 and now its a single stage trigger.
I also swapped out the weight spring for a lighter one. Now its a crisp trigger. A safe crisp trigger.
Next I loaded some bullets @Stalker1962 had sent me with 26.5gn of CFE223.
When I got to the field it became apparent how nicer it was to not have to set the set trigger, never have liked them and never ever really understood why they exist!
Whilst the target is nothing to look at its very good but the rifle was shooting a pinch low. After making some adjustments I wanted to test the baltic ( thanks @Jelen ) calculator at range and found a prominent clod at 448 yards, no not that individual, actual earth clod.
What looked like a new aiming point at 6' of hold I added the windage and fired. Bloody brilliant, the bullet hit it!
Should of filmed it 🤦.
 
Today I did three things.
Firstly i did away with the set trigger on my cz527 222 and now its a single stage trigger.
I also swapped out the weight spring for a lighter one. Now its a crisp trigger. A safe crisp trigger.
Next I loaded some bullets @Stalker1962 had sent me with 26.5gn of CFE223.
When I got to the field it became apparent how nicer it was to not have to set the set trigger, never have liked them and never ever really understood why they exist!
Whilst the target is nothing to look at its very good but the rifle was shooting a pinch low. After making some adjustments I wanted to test the baltic ( thanks @Jelen ) calculator at range and found a prominent clod at 448 yards, no not that individual, actual earth clod.
What looked like a new aiming point at 6' of hold I added the windage and fired. Bloody brilliant, the bullet hit it!
Should of filmed it 🤦.
Nice one.
My experience was slightly different - 2 days ago in flat calm set zero at my normal half an inch high on the triple deuce - perfect grouping at 100yds. Today at 108 yds groups were one inch left and one and a half high off the bipod and Jimny bonnet! Good breeze today at my 1 o’clock which may well have caused the left of zero but so high at 108? Tomorrow is a range day when more stringent testing will apply - I have saved the original setting and the new one done today to correct the apparent shift so it will be interesting to see….
🦊🦊
 
Nice one.
My experience was slightly different - 2 days ago in flat calm set zero at my normal half an inch high on the triple deuce - perfect grouping at 100yds. Today at 108 yds groups were one inch left and one and a half high off the bipod and Jimny bonnet! Good breeze today at my 1 o’clock which may well have caused the left of zero but so high at 108? Tomorrow is a range day when more stringent testing will apply - I have saved the original setting and the new one done today to correct the apparent shift so it will be interesting to see….
🦊🦊
Don't like the sound of that FB 😱
 
Back
Top