Arken zulus hold over error

Jump to latest Follow Reply
C

corguy15

Member
Apr 12, 2022
22
10
CA, United States
I might be doing something wrong, but I can not get my ballistics table and holdover marks to match.
IMG_5950.jpeg

The blue line is where it should be
IMG_5951.jpeg

I have made sure
- I have the correct table uploaded
- I have the latest updates
- the gyro has been calibrated
- the range was taken from level
- all of my input data is correct.
 
MartinT said:
Maybe the table got corrupted for some reason, try to input some datafields again and resend the table to the scope?
Or try a different memory (A-Z in the zero reticle menu)


I've noticed a bug in the app as well:

When one selects FFP and then go into the reticle page, if you change magnification (zoom) on that page the hashmarks stay the same size, but the holdover distances change. This is of course NOT what happens with an FFP scope... (the hasmarks grow or shrink, but the holdover distances stay the same for any given hashmark. For an SFP scope the hashmarks do stay the same size, and the holdover distances change with varying zoom level so in that case it shows correctly)
Click to expand...
I tried a new profile and a complete reset of the zulus and still have the same issue.

I have gotten a response from the Facebook Zulus group that seems to indicate that Arken knows of a problem.
 
  • Like
Reactions: Airgun Al
Upvote 0
MongooseV8 said:
Have you done a distance drop test to verify BC? How are you measuring atmosphere conditions?
Click to expand...
The BC is good. I have measured it many different ways. The table is correct when it comes to the drop. I have measured this by putting on a regular scope and dialing out to 100 yards. It’s the Zulus calculation that is giving me the wrong holdover point. You can see this from my zero when I put in the correct scope measurements. The holdover it gives me is the wrong point of impact. I have to put my scope height at .5in to get my point of aim dead center at 20 yards.
IMG_5964.jpeg
 
  • Like
Reactions: MongooseV8
Upvote 0
At which vertical angle did you range your target?

Because this is what I noticed: I have set a 12m zero range in my scope. The ballistics is spot on. When I range 12m. horizontal, the holdover aiming mark is centered. (like you'd expect...) But when I range from the same position to a 20 degree up, (using a flagpole) the shown range increases to 15m. (remember: the horizontal distance is still 12m!) now the aiming mark changes slightly to hold over. (like your situation) So it must correct for angle as well, as in my case with a horizontal distance of 15m the aimingmark should indicate a holdunder! (and again: the ballistics when shot horizontal is spot on)
 
Upvote 0
MartinT said:
At which vertical angle did you range your target?

Because this is what I noticed: I have set a 12m zero range in my scope. The ballistics is spot on. When I range 12m. horizontal, the holdover aiming mark is centered. (like you'd expect...) But when I range from the same position to a 20 degree up, (using a flagpole) the shown range increases to 15m. (remember: the horizontal distance is still 12m!) now the aiming mark changes slightly to hold over. (like your situation) So it must correct for angle as well, as in my case with a horizontal distance of 15m the aimingmark should indicate a holdunder! (and again: the ballistics when shot horizontal is spot on)
Click to expand...
When I zeroed, it was relatively flat. I can try and re-zero to make sure it is completely flat
 
Upvote 0
A Hold over solve.

I could not get hold over to show. I'd range then press again and it would say out of range.

I set zero distance at 20mtrs then do your ballistics.. after that save it.

Then All I did was go to ballistic table and press setting in the top right of screen

Top 3 boxes should be..

Start distance =0
End distance=100

More than 100 if you shoot further. Air guns 100 is
plenty.

Incremental distance =1

My app installed with settings of
0-914-100 which is wrong.

Save it and it returns to ballistic table with all the ballistics from 0-100

Now send that to the scope..it should now show your hold over.

It works.. you've just then got to range 20myr somewhere and zero your reticle.. you're all set up..👍

Screenshot_20240802-183408.png


Screenshot_20240802-183200.png


Screenshot_20240802-183416.png


DSC_2385.JPG
 
  • Like
Reactions: TerryE1
Upvote 0
I hear there's a poi correction function potentially. In the new firmware update there's now an alphabet in my zero menu in the scope firmware that I suspect may be related. If it doesnt have that function it would be neat to be able to paper the gun and input the data manually per range if the ballistic calculation was off. Previously I had simply toyed with velocity, bc, and initial zero range to get as close as possible (usually by using strelok to help me achieve the variable mods).

I was fighting a misaligned impact top strap and rail at that time and wished I could enter a windage value for each range to compensate. A 1 piece rail fixed it. My initial problem was shooting left at 15 yards, dead nuts at 60(zero) and then back to way left at 100 and progressively worse farther out.
 
Upvote 0
You must log in or register to reply here.
Top Bottom
Back
Home
Forums
Resources
Menu