-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to start the onvif_srvd service of PTZ #51
Comments
I don't know what (gimbal joystick) is. But if you are asking about the PTZ mechanism, one of the users has implemented it, Onvif, the protocol and this daemon(service) simply provides a mechanism for calling a certain command (it can be set via command line parameters) that will be called by the daemon when a command arrives via the protocol. |
The following error occurred when I connected to the service: |
I have not used wsse:Security, you should study the necessary mechanisms yourself. Perhaps in the specification for wsse:Security from ONVIF, the exchange protocol is described, but below, perhaps, the packages depend on the application. Understand ONVIF, this is an exchange, it does not even transmit a picture, this is done by RTSP. You should open the bindings you need and study their types. |
I have successfully started the service and connected the PTZ joystick to our service. I have a question. Does the service only support the following PTZ parameters? Here is a picture of my joystick. In addition to moving forward, backward, left, and right, the joystick also has clockwise and counterclockwise rotation, and a button in the middle. Can these be supported? |
Well, look at how move_preset works, you can probably assign them or something like that, as I understand it, these are sets of preset movements. |
Hello, I would like to know if I want to receive gimbal joystick information, then what parameters need to be configured in my onvif_srvd startup command? Can you provide a gimbal startup example? Thank you very much.
The text was updated successfully, but these errors were encountered: