Axis Communications
Replies: 2 comments 3 replies
-
|
Issue seems to be corrected in later firmware, do you still see the issue in 11.11.116 - AXIS OS LTS 2024? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for checking on this. This issue was when we were using the Q6215, I believe. Since then, we've upgraded to the Q6225. We're now primarily using VAPIX instead of ONVIF to control the focus (via a custom autofocus plugin) and that seems to be going to the right values. I think you can consider the issue resolved, at least for us. |
Beta Was this translation helpful? Give feedback.
-
|
OK, thanks for the update, we will close the discussion. |
Beta Was this translation helpful? Give feedback.
-
|
When you are zooming, the focus value is related to current zoom value, for example ,zoom from 1 to 30, when current zoom value is 10, you send a focus value to camera, but that focus value is maps to 30, while in reality, the current zoom is only 10, so it seems out of focus. after the zoom value is really in 30, if you send focus, then it will focus correctly. Why not using continuous zoom? the focus should be much better during the whole zoom process, then you can send absolute zoom and focus after the continous zoom finished. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense if I were sending the focus command while the zoom move is still in progress. I did try manually sending the focus command though, I believe, though it's been a while since I worked directly with the focus in our system. As I mentioned in a reply to someone else, we're now using a different approach, and on a different camera version, so we're not experiencing the issue anymore. The reason we don't use the continuous move zoom command is because we need a specific zoom value, corresponding to a specific field of view in degrees, because that's what our client software expects. We could experiment with continuous zoom if it becomes an issue again, but the built in autofocus hasn't worked very well on aerial objects for us. |
Beta Was this translation helpful? Give feedback.
-
Hi,
We're using ONVIF to control our Axis AXIS Q6215-LE PTZ, and recently have started using the focus API in the ONVIF imaging service to set specific focus values. However, it doesn't always go to the value specified. Here are a couple examples from a tool we created to send specific commands:
Going to the wrong focus value when zooming over a large range
We started at 1.75 degrees FOV and sent a command to zoom to 48.8 and then a focus command for the corresponding focus value:
However, the focus was not near the corresponding value. Usually there's some wiggle room, but this was at 7856 rather than 9939:
So then we re-sent the focus command (
lookupin our tool means to send a focus command corresponding to the current FOV) and it did focus at that value:Focus going out of bounds when sending a sequence of zoom and focus commands
Here we started at FOV of 48.9 and sent a sequence of commands for successively narrower FOVs and the corresponding focus values:
But the focus value was out of range (5245) and the picture was, correspondingly, blurry:
Sending the focus command for 9642 again will focus it, but the way it is, a user will be zooming in with our software using the mouse scroll wheel (which generates a series of zoom/focus commands) and it will land on a value with a blurry picture.
We're using firmware version 11.2.68.
Edit to add: Even when the change in FOV is not large, (like zooming in at 2 degrees and varying by half a degree or so), the camera seems inconsistent in its behavior. Sometimes it won't go to the focus value you tell it. Sometimes it won't zoom to the right value. Sometimes it goes to the right values according to the getstatus commands, but may or may not actually be focused at the right range, even when we've tested that focus value for the same target.
Beta Was this translation helpful? Give feedback.
All reactions