• the Daily hi thread just say hi :)
  • Please DO NOT discuss the use of optics/NV for HUNTING in this section. Any hunting related Optics questions should go in the hunting section.

HITTAC - Your Thoughts

Need a little help please. I was out with my Zulus HD, I use the “Ballistic table call” option (so I don’t need the constant connection to my mobile on Bluetooth when range finding). Was working fine. Whlist waiting for grey to turn up at the feeder I put the scope to sleep. Later on when I powered the scope back on I realised that the scope is now only giving ballistic changes to the reticle when connected to the phone “Real Time Ballistic calculation“ , It doesn’t seem to use the table data I have sent to the scope, resent the ballistic table from the app a few times to no avail. I have recreated the cartridge data for the pellet and resent ballistic table to the scope , reported it was sent successfully yet when ranging targets the holdover is just showing centre of reticle still (eg as if it’s at my 20 yd zero range.

any ideas please? I have just updated to January firmware but still the same, ranging only works when using the Real Time Ballistic calculation option from the phone on Bluetooth.

ta
Rich
 
Need a little help please. I was out with my Zulus HD, I use the “Ballistic table call” option (so I don’t need the constant connection to my mobile on Bluetooth when range finding). Was working fine. Whlist waiting for grey to turn up at the feeder I put the scope to sleep. Later on when I powered the scope back on I realised that the scope is now only giving ballistic changes to the reticle when connected to the phone “Real Time Ballistic calculation“ , It doesn’t seem to use the table data I have sent to the scope, resent the ballistic table from the app a few times to no avail. I have recreated the cartridge data for the pellet and resent ballistic table to the scope , reported it was sent successfully yet when ranging targets the holdover is just showing centre of reticle still (eg as if it’s at my 20 yd zero range.

any ideas please? I have just updated to January firmware but still the same, ranging only works when using the Real Time Ballistic calculation option from the phone on Bluetooth.

ta
Rich

Within the scope setting you need to go into ballistic calculation and select ballistic table call.

Cheers

Billy
 
Within the scope setting you need to go into ballistic calculation and select ballistic table call.

Cheers

Billy
Hi Billy, thanks mate but I have been using that option fine. It has been ranging fine using ballistic table call for weeks. The only thing I did today was change the BC value for the pellet as it was shooting a tad high at 50 yards , my zero is 20 yds and I then put the scope to sleep, as I hadn’t used the scope again it had powered down after 10 mins. When I powered it back on say 30 mins later and retried the 50 yard range I noticed the holdover was showing at centre reticle (X 0/ Y 0) , tried at 70 and 100 yds and the reticle holdover was not adjusting. It will only show the correct holdover on the reticle when using the Real Time ballistics call option
 
Hi Billy, thanks mate but I have been using that option fine. It has been ranging fine using ballistic table call for weeks. The only thing I did today was change the BC value for the pellet as it was shooting a tad high at 50 yards , my zero is 20 yds and I then put the scope to sleep, as I hadn’t used the scope again it had powered down after 10 mins. When I powered it back on say 30 mins later and retried the 50 yard range I noticed the holdover was showing at centre reticle (X 0/ Y 0) , tried at 70 and 100 yds and the reticle holdover was not adjusting. It will only show the correct holdover on the reticle when using the Real Time ballistics call option

Can you confirm the correct zero profile is being used on the scope?

I've updated a number of scopes and haven't come across this issue.

We will contact Arken to see what can be done. There seems to be a few teathing problems with this firmware version.

Cheers

Billy
 
Can you confirm the correct zero profile is being used on the scope?

I've updated a number of scopes and haven't come across this issue.

We will contact Arken to see what can be done. There seems to be a few teathing problems with this firmware version.

Cheers

Billy
Hi Billy.

Yes I can confirm I had the corresponding zero profile, A for the ballistics table sent to the scope. Here’s some screen shots and rather crude photos of the scope settings as best as I could.

the issue occurred on the November firmware, I have updated this evening to the latest(Jan 2024] firmware hoping it’d fix the issuebut it’s still the same.

you will see in the last but one image I ranged a target at 45 yards yet the hold over is showing the centre of the reticle ( X 0 Y 0 ) which is incorrect.
 

Attachments

  • IMG_2272.webp
    IMG_2272.webp
    43.6 KB · Views: 31
  • IMG_2276.webp
    IMG_2276.webp
    39.3 KB · Views: 28
  • IMG_2280.webp
    IMG_2280.webp
    94.4 KB · Views: 26
  • IMG_2279.webp
    IMG_2279.webp
    37.5 KB · Views: 30
  • IMG_2281.webp
    IMG_2281.webp
    62.6 KB · Views: 28
  • IMG_2282.webp
    IMG_2282.webp
    67.3 KB · Views: 27
  • IMG_2283.webp
    IMG_2283.webp
    54.5 KB · Views: 32
Last edited:
In IMG 2282 is your scope actually pointing down at an angle of 29.7 degrees?
With the data you supplied and if the scope was horizontal, the holdover mark for 45 yards should be around 1.2 mil
If the scope is pointed downwards at around 30 degrees, the holdover mark should be around 0.5 mil
Try changing to the moa reticle and ranging your target horizontally

Cheers

Bruce
 
In IMG 2282 is your scope actually pointing down at an angle of 29.7 degrees?
With the data you supplied and if the scope was horizontal, the holdover mark for 45 yards should be around 1.2 mil
If the scope is pointed downwards at around 30 degrees, the holdover mark should be around 0.5 mil
Try changing to the moa reticle and ranging your target horizontally

Cheers

Bruce
Hi Bruce,

I had ranged the gable end of a house (scope not mounted on a rifle btw) and tried to capture the image on my iPhone but couldn’t manage it without dropping the phone so I pointed the scope towards my patio to get the photo hence the downward angle.

if I connect to my mobile iphone and change the ballistic to the real time option I get the correct holdover. The scope doest seem to be using the ballistics table sent to it when I use the ballistics table call option.

Bruce, Did you notice the MOA value at 5 yds in the ballistics table, is that correct, seems a very high value I thought.

ta

Rich
 
Last edited:
This morning I have deleted the app from my IPhone and reinstallied it. Setup the rifle and cartridge data from scratch and sent the ballistic table data to my scope. Set the scope Ballistic option to Ballistic table call and retested at 20, 45 and 67 yards and the hold over is still just staying at the zero centre on reticle X 0 Y 0. Therefore not showing true hold over. If I change to Real Time Ballistics call option where it communicates via Bluetooth to the iPhone the hold over works fine showing the different holdover positions on the reticle for the different ranges.

I then factory reset the Zulus HD and retested after sending the ballistics table from the iPhone to the scope , set back to Ballistics table call option on the scope , setup the Zero profile A with the required X and Y values and it still doesn’t work. I’m confuzzled,

The LRF is clearly working as is Bluetooth when using the Real Time ballistics call so I can only guess that the table isn’t being referred to despite it being sent successfully to the scope.
 
That would have me confused for sure @rbov , just as a matter of interest what do you have your end distance set at in table settings ?
IMG_1898.webp
 
I have had 3 x 18650 batteries for a while in a few torches, so i'm ok for now but the Zulus is power hungry.
How long are you getting from your Vapcell N40 4000mah's ?
 
This morning I have deleted the app from my IPhone and reinstallied it. Setup the rifle and cartridge data from scratch and sent the ballistic table data to my scope. Set the scope Ballistic option to Ballistic table call and retested at 20, 45 and 67 yards and the hold over is still just staying at the zero centre on reticle X 0 Y 0. Therefore not showing true hold over. If I change to Real Time Ballistics call option where it communicates via Bluetooth to the iPhone the hold over works fine showing the different holdover positions on the reticle for the different ranges.

I then factory reset the Zulus HD and retested after sending the ballistics table from the iPhone to the scope , set back to Ballistics table call option on the scope , setup the Zero profile A with the required X and Y values and it still doesn’t work. I’m confuzzled,

The LRF is clearly working as is Bluetooth when using the Real Time ballistics call so I can only guess that the table isn’t being referred to despite it being sent successfully to the scope.

Only thing I noticed was your table was set to 5 yard increments. Try changing to 1 yard.
 
Hi Bruce,

I had ranged the gable end of a house (scope not mounted on a rifle btw) and tried to capture the image on my iPhone but couldn’t manage it without dropping the phone so I pointed the scope towards my patio to get the photo hence the downward angle.

if I connect to my mobile iphone and change the ballistic to the real time option I get the correct holdover. The scope doest seem to be using the ballistics table sent to it when I use the ballistics table call option.

Bruce, Did you notice the MOA value at 5 yds in the ballistics table, is that correct, seems a very high value I thought.

ta

Rich
Looking at your ballistic table values it seem that your scope is zeroed on the first zero as the pellet crosses the line of sight, with the second zero around 26 yards
The high moa value at 5 yards is because at that distance from the gun, the pellet is still quite a long way below the line of sight
Notice how the moa value gets smaller as you approach your zero distance

Cheers

Bruce
 
Looking at your ballistic table values it seem that your scope is zeroed on the first zero as the pellet crosses the line of sight, with the second zero around 26 yards
The high moa value at 5 yards is because at that distance from the gun, the pellet is still quite a long way below the line of sight
Notice how the moa value gets smaller as you approach your zero distance

Cheers

Bruce
Ah that makes sense, thanks Bruce. I’m not overly familiar with Minute of angle so wasn’t sure if the value seems odd. Ta
 
Only thing I noticed was your table was set to 5 yard increments. Try changing to 1 yard.
hi mate. Just tried changing to 1 yd increments but same . Im thinking that I may have to raise this with Adam as a fault soon through his website. So frustrating that it will not work independent of the iPhone now when it had worked fine. i can’t believe.

Bugger!
 
Okay, so after help and advice from several forum members, especially @GPCBILL , I used a Samsung S9 with the Aiken Ballistcs app to send the Ballistcs table to the scope and now the “ballistcs table call” setting on the scope is working again independently to the mobile app. Hooray!

So I don’t know if the iPhone iOS Aiken Ballistcs app had an update on Sunday that caused the issue or it’s a glitch on the Arken scope that couldn’t refer to the ballistic table that was sent to it.

Any thoughts on that anyone ?

I’m very happy it’s working again and hopefully the iPhone app will work with the scope again at the next update if indeed it’s the iOS app at fault.

Thanks again
Rich
 
@mealiejimmie

Pro Optics is applying to be struck off the company house register.
Will your contacts at Arken confirm that they will take over the warranty?
 
@mealiejimmie

Pro Optics is applying to be struck off the company house register.
Will your contacts at Arken confirm that they will take over the warranty?

Somewhat ironic when yorkyboy was the very one harping on about the warranty benefits of buying from a UK based supplier.

I can't see you having any problems if you have to deal directly with Arken.
 
Back
Top