Hi all,
We are developing a java client using JAX-WS to connect to xProtect Corporate 2017 via Protocol Integration.
We are experiencing problems when we try to move Pelco cameras. We are using the methods “PTZMoveStart” and “PTZMoveStop” located inside “RecorderCommandService”. It seems that there are something blocking several movements in the same direction but, if we move the camera to another direction and then we move it to the previous one, it works. I.e.:
Steps to reproduce the issue in our app:
- Move camera in LEFT direction → Camera moves OK to left
- Move camera in LEFT direction again → Camera doesn’t move
- Move camera in LEFT direction again → Camera doesn’t move
- Move camera in RIGHT direction → Camera moves OK to right
- Move camera in LEFT direction → Camera moves OK to left
We can see this behavior moving the camera to any direction, not only in right or left direction.
There are several camera types in our system, but we only have detected this issue in Pelco Cameras, and we are using the same Protocol Integration methods to move different camera types and it is working, so we have discarded to have a problem in our app.
Is it posible that Protocol Integration have any issue related with Pelco Cameras?
Please, we need to fix this ASAP.
Thanks in advance.
Please tell me:
Which version of XProtect 2017 (R1, R2, R3)?
Which Device pack version?
Camera model and firmware version?
Hi,
Excuse my late response, I was waiting for an our client response.
XProtect 2018 R2
Device pack 9.7
We have three camera types that they have this issue:
Model: Pelco Spectra IV-IP HD
Fw: 2.5.1.1.9340-A0.0
Model: Pelco Spectra IV-IP HD
Fw: 1.9.2.23-20141118-1.9320-A1.10722
Model: Pelco Spectra IV-IP HD
Fw: 1.9.2.19-20140318-1.9330-A1.10443
Regards.
consider to limit the number of commands you send to the Recorder/camera, e.g. as long as the movement is in same directly, send max 10 commands a second (or less). Some cameras have a difficult time handling overflow of PTZ operations.
Hi,
We are sending one command per second as maximum, because initially we thought that it was an overflow issue, but after test with one command per second we saw the same issue.
OK, if you use the Smart Client and operate a JoyStick - do you see same issue?
No, we only have this issue when we are operating through Protocol Integration.
I suggest that you make a WireShark trace of how the Smart Client is doing, and check the content with how you have implemented it. Smart Client are using the protocol towards the RecordingServer. Here there are two options: using the ImageServer XML interface or using the RecorderCommand SOAP interface.
We are using RecorderCommand SOAP interface for all camera movements, and it is working fine for all camera types that we have in our client application except Pelco cameras. I have checked all possibilities to assure that we are sending the correct request every time and everything seems OK.
We suspect that this might be on the Pelco driver when other cameras do not see the issue. Can you please try the newest available device pack and see if the issue is still there?
https://www.milestonesys.com/support/resources/download-software/?type=17&lang=27
Please accurately specify the camera you have, we need make, model and firmware version. Please find in the Management Client the name of the driver used.
Please make a network communication trace between the camera and the recording server and between your client and the recording server at the same time, this will allow us to analyse issue, and hopefully if we find buggy behavior to develop a fix.
https://supportcommunity.milestonesys.com/s/article/Using-Wireshark?language=en_US
Device Pack: “XProtect Device Pack 9.9b”
Cameras that we use:
Model: Pelco Spectra IV-IP HD
Fw: 2.5.1.1.9340-A0.0
Model: Pelco Spectra IV-IP HD
Fw: 1.9.2.23-20141118-1.9320-A1.10722
Model: Pelco Spectra IV-IP HD
Fw: 1.9.2.19-20140318-1.9330-A1.10443
Driver used by all cameras is: “Pelco PTZ Cameras”
Image is not available
Do you have a Wireshark trace?
Hi,
I don’t have Wireshark traces but, today, I have found an interesting behavior… I have found that if I send a movement in the same direction but with different movement speed, it works! I mean, I am sending movements to right with a random speed and the camera is responding but, if I send the same movement always with the same speed, then it only works the first movement… Any idea?
Regards.
Hi again,
Effectively, this is the issue. Something in your pelco driver is crashing when I send the same movement with the same speed, because if I send the movement in the same direction but changing (+/- 1) the previous speed, it works.
I hope this will be usefull for to fix the issue in your driver.
Best regards.