Follow-up on Previous Inquiry Regarding PTZ API Behavior
In ProgressFollowing up on my previous inquiry regarding the PTZ API behavior, I noticed there hasn’t been a response yet. To recap, I had shared logs and specific details about an issue where the API responses indicate “success,” but the actual PTZ behavior doesn’t seem to align with the expected results.
https://support.networkoptix.com/hc/en-us/community/posts/28200355476247-PTZ-Control-Issue-with-NX-Witness-API-Integration?page=1#community_comment_28408694491287
For reference, here is a brief summary of the issue:
•Problem: PTZ API calls return “success,” but the camera sometimes fails to move to the specified position as intended.
•Logs: [Attach logs or refer to the previously shared logs]
•Question: Could this be related to parameter configurations, network conditions, or firmware compatibility?
-----------------------------------------------------------------------
I would appreciate any updates or insights you might have on this matter. Additionally, if more information is needed from my side, feel free to let me know.We have encountered an issue with the PTZ API where the API responses indicate “success,” but the actual PTZ behavior seems to deviate from the expected operation. Below, I have detailed the situation and included relevant logs for your review. We would appreciate your guidance on resolving this issue or adjusting the API parameters to ensure accurate PTZ operations.
1. Problem Description
•Issue: The API call for PTZ operations, specifically with the “absolute” movement type, returns “success.” However, the camera does not always reach the specified position or behave as expected.
•Question: Could this behavior be related to how the API parameters are configured? Are there recommended parameters or adjustments we should apply to ensure precise PTZ operations?
2. Relevant Logs
Here are some sample logs from our system:
2024-12-09 16:41:17.469 +0800: {Network} {nx} {PTZ get position: {pan: 0.05999999865889549, tilt: 0.41999998688697815, zoom: 0.07000000029802322}} {WARNING}
2024-12-09 16:41:21.928 +0800: {Network} {nx} {PTZ move to: {deviceId: 00eae28a-6d1e-cb5b-a1b8-e4433a0c003a, type: absolute, api: none, pan: -0.2400000013411045, tilt: 0.41999998688697815, speed: 0.5, zoom: 0.07000000029802322}} {WARNING}
2024-12-09 16:41:25.283 +0800: {Network} {nx} {PTZ move success: {deviceId: {00eae28a-6d1e-cb5b-a1b8-e4433a0c003a}, pan: 0, speed: 0, tilt: -1, type: absolute, zoom: 0}} {WARNING}
2024-12-09 16:41:27.064 +0800: {Network} {nx} {PTZ move to: {deviceId: 00eae28a-6d1e-cb5b-a1b8-e4433a0c003a, type: absolute, api: none, pan: -0.5400000013411045, tilt: 0.41999998688697815, speed: 0.5, zoom: 0.07000000029802322}} {WARNING}
-
Hi
Your question has already been answered, and we are still waiting for the necessary troubleshooting information from you. Please review the last response and provide the required details to proceed.
Regarding the movement behaviors, unfortunately, without a video or complete details of the requests made, we are unable to investigate further based solely on assumptions. To assist you more effectively, could you please provide the following:
1.The PTZ model in use.
2.The exact full API request you have made (this is mandatory).
3.Ideally, test the issue using a tool like POSTMAN or a similar API testing platform to isolate the issue at the API level, independent of the APP, camera firmware level, including a screen recording of the process would also help us better understand the behavior and the problem you are encountering.
i.e we will need you to check if every PTZ movement request consistently correct on the camera firmware level and always works as expected while the coordinates and parameters are the same.Nx Witness mediaserver just sends the same API to the camera via standard ONVIF, so it is rarely the issue of the command but more likely the handling on the camera firmware.
So, we kindly ask you to provide the necessary information for further investigation if you wish to proceed.
In short:
•Screen recording: To observe the exact behavior.
•Full API request: Please provide the complete details. (Mandatory)
•PTZ model and capabilities: Information about the PTZ model and its supported capabilities. (Mandatory)
•Isolated testing: The exact issue should be isolated and tested to recognize if that is an API issue or camera firmware issues.Thank you.
Please sign in to leave a comment.
Comments
1 comment