fx pocket chrony v2 not reading

Jump to latest Follow Reply
Mine had the same, so I exchanged it for another. First one was very iffy, and missing more shots than registering them. The second one is 100% OK. (Of course I tried all sorts of positions, alignments and multiple airguns, but it clearly was the unit itself and not the circumstances)

The only difference between them that I noticed was that the ‘faulty’ one had the small red and green LEDs (on the opposite side from where the on/off button is) only illuminated for a short time (when pressing the on/off button momentarily), where the 100% one has them illuminated full time. Don’t know if it related to their functionality, but their you have it.
Well that and the fact that the first one had the nut stuck on the screw, so it required a lot of force to break free (literally broke the screw in two pieces!) and it ruined the pristine finish of my 2500 dollar airgun. I call it ”The revenge of FX”. (As the airgun is not from that make):LOL: …
 
Upvote 0
I've found two things that can affect it. One is having it set for the wrong velocity range. If velocities go over or under the range you have it set for in its profile then you won't get a reading. The other is sensitivity. The default setting is 20. On some guns, particularly. 177s and bb guns I've had to go down to 10 or 0. It's best to keep it as high as possible though because with it set really low any rapid movement will cause a false reading. The false reading are typically very obvious however.
 
Upvote 0
Sawney Bean said:
I've found two things that can affect it. One is having it set for the wrong velocity range. If velocities go over or under the range you have it set for in its profile then you won't get a reading. The other is sensitivity. The default setting is 20. On some guns, particularly. 177s and bb guns I've had to go down to 10 or 0. It's best to keep it as high as possible though because with it set really low any rapid movement will cause a false reading. The false reading are typically very obvious however.
Click to expand...
Thanks Sawney this would work for the v1 Fx chronographs the v2 is set fron 400fps -1250fps
 
Upvote 0
MartinT said:
Mine had the same, so I exchanged it for another. First one was very iffy, and missing more shots than registering them. The second one is 100% OK. (Of course I tried all sorts of positions, alignments and multiple airguns, but it clearly was the unit itself and not the circumstances)

The only difference between them that I noticed was that the ‘faulty’ one had the small red and green LEDs (on the opposite side from where the on/off button is) only illuminated for a short time (when pressing the on/off button momentarily), where the 100% one has them illuminated full time. Don’t know if it related to their functionality, but their you have it.
Well that and the fact that the first one had the nut stuck on the screw, so it required a lot of force to break free (literally broke the screw in two pieces!) and it ruined the pristine finish of my 2500 dollar airgun. I call it ”The revenge of FX”. (As the airgun is not from that make):LOL: …
Click to expand...
Yes this is the second one, others are fine.i will have a look at the lights maby it something to do with that,but how to fix it i suppose we send it back to the supplier.
 
Upvote 0
Mine Pocket v2 doesn't read nor register any shots at all. I turned it on and the chrony started reading some "high speed" over 1100 fts. shots without me even using a gun. I turned it off, then, back on and it doesn't read any shoots. I've try placing it in a different location on the barrel, but it didn't help.
I called UA and was told that the issue is because of a bug in the app and that FX is aware of this and is working on a fix. It seems odd because the app connects and recognize the device + V1 chrony I have works fine. Maybe I'm wrong but, if that would be an app issue most likely all Pocket V2 devices won't work. The chrony is 2 months old and was working when I bought it. UA has not offered me a replacement (yet), so I would assume it is well known issue that I wasn't aware of.
 
Upvote 0
You must log in or register to reply here.
Top Bottom
Back
Home
Forums
Resources
Menu