Follow-up on Previous Inquiry Regarding PTZ API Behavior

In Progress

Comments

1 comment

  • Avatar
    Ichiro

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.