Camera Deployment Troubleshooting

Camera Deployment Troubleshooting (Some steps need admin level user for the camera)
Step	Problem	Troubleshooting Steps
	Deployment > Unsure of which camera type to select	DCM can use Pan Tilt Zoom (PTZ) or fixed. PTZ cameras need to spend most of their time in a pre-calibrated home position. If your camera is fixed, select IP Camera. The optional special detailed mood measurements are only possible for PTZ cameras as this requires image zooming and reframing. Purely analogue cameras cannot be used. If your analogue camera is capable of saving its image stream to an IP accessible location, you may be able to proceed. Choose IP camera in this case. You can choose IP camera even if the actual camera is PTZ. This will work but restrict some functionality. But if the PTZ has a home position set – this may actually be a better option.
	Deployment > Don’t have RTSP link	Most IP cameras have a Management System that can be accessed in a web browser. This may contain the RTSP link of the stream. You will need administrator access to the camera. If the native manufacturer VMS does not show the RTSP details, you can use ONVIF Device manager software: https://sourceforge.net/projects/onvifdm/ You may need to set up an ONVIF compliant user, if the VMS for your specific camera uses a different system for user authentication.

Deployment > Test Device Connection fails

OR

Camera Test Device connection works in ‘IP camera mode but not in ‘PTZ mode’

Check host IP and username password. Check for errors in the port or RTSP URL. A good verification is to use them in another tool from the local network like VLC player, or a VMS system.

Ensure that network setup is complete and ping succeeds from DCM VPN server to your camera IP using the ‘Ping device’ tool on the Network settings page.

If VLC or other tools can connect to the camera but DCM cannot – check the camera password for reserved characters. In general it is advisable to avoid using @#/\ and especially ‘:’ in usernames or passwords. While DCM itself allows them, some camera or VMS systems can also reserve these.

Some specific camera brands – for example Axis, will not work with a password using ‘:’ for example.
Change camera passwords if possible. Blank passwords can work depending on connection types, but are generally not recommended.

Try adding or removing the username and password or RTSP port as part of the RTSP link. On most models these are optional and should work either way, but sometimes can affect connectivity.

Ensure the URL is using the correct stream if multiples are available in the camera.
Example formats below:
rtsp://<user>:<pass>@10.0.0.123/onvif-media/media.amp?profile=profile_1
rtsp://<user>:<pass>@10.0.0.123:554/axis-media/media.amp?camera=2

Try an Alternate RTSP link format – for example

eg rtsp://<user>:<pass>@@192.168.0.43/media/video1
Check the format using the documentation for your particular camera brand.

Try changing the camera type to “IP camera” in the deployment screen, even if the camera is a PTZ.

If this makes it work – port 80 may not be open. PTZ cameras can be used in this mode but DCM cannot control their movement. This may even be desirable if camera is also used for other purposes. If PTZ control is needed, ensure the networking or local VMS system settings have port 80 open.

Main difference, is that DCM cannot detect the camera position has been changed in “IP” mode. If the camera is moved, DCM will continue to gather (now inaccurate) measurements, whereas in PTZ mode it will stop and only resume gathering data when manually restarted on the deploy screen. In some circumstances, where moves are expected to be brief – or a quick auto return to home position is set, it may be preferable to tolerate brief periods of bad data to avoid manual restarts.

Ensure DCM is calibrated in the home position. If possible set an automatic return to this position to minimise impact of camera being moved away.

If camera works in ‘IP camera’ mode, but not in ‘PTZ’ mode - Check camera user account type. A valid, but non ONVIF user account will not function if the camera type is set to ‘PTZ’. User needs to have ONVIF rights to access the PTZ controls – an ‘admin’ level account is the most reliable way to ensure this.

You can check you ONVIF credentials are correct by using the ONVIF Device manager software: https://sourceforge.net/projects/onvifdm/ installed on a machine on the same network as the camera.
Ensure your credentials when entered into this software, can list the target camera, access the live feed and if needed, use the ONVIF compliant PTZ controls.

The default user accounts on some cameras are not ONVIF users, and these need to be created in a separate menu. User credentials used should be an ONVIF admin user to work in all circumstances, and must be ONVIF users when camera is set to ‘PTZ’. A basic user is actually sufficient for a fixed ‘IP camera’ that only needs to connect to the stream rather than control camera movement.

Check the Time settings on the target camera. If the current time on the camera is not accurate, this can block connection requests, even if out by only a few minutes. Best fix is to configure a public ntp server and set to ‘auto’.

Some cameras have security features that if enabled can block DCM from connecting to the stream. Using an admin account for the cameras native Management System, log in and check the configuration. In particular , check for a setting called “Replay attack protection” or similar, typically in a Webservice menu or configuration section. This can interfere with camera control by the software and should be set to off.

10. Contact DCM support

Camera Calibration Troubleshooting (Some steps need admin level user for the camera)
Step	Problem	Troubleshooting Steps
	Calibration > A warning appears that “Deployment coordinates are missing”	System has not saved camera coordinates from the deployment phase. Check coordinates and re-save.
	Calibration > Update satellite image returns no data	Check internet connection Ensure camera latitude and longitude set in the deploy screen are valid and not on 0:0 Try changing to a different zoom level and re-request the satellite image. Satellite and grid options are not user configurable, contact DCM support

Calibration > Capture device view returns no data

Check connection to camera

Using an admin account for the cameras native Management System, log in and check the configuration. In particular , check for a setting called “Replay attack protection” typically in a Webservice menu or configuration section. This can interfere with camera control by the software and should be set to off.

Try changing the camera type selection in the deployment screen to ‘IP camera’ and retry capture. If this works, you may be able to proceed with reduced functionality. Notify DCM support.

Deployment > Satellite image is too blurry to allow exact camera placement

Image resolution is limited by the data sources available. GPS co-ordinates can be sourced from a mobile phone or other device and entered directly at the bottom of the screen.

Finalise > Calibration fails to produce a result image, returns an error or produces North and East points that are clearly in the wrong direction for some pins.

Ensure the best approximate camera orientation was selected in steps 2 and 3.

Try adjusting the camera zoom to have desired area filling as much of the view as possible.

When drawing the area selection box try to only include ground/floor areas.

Ensure landmark pins placed on the device view are not outside the area selection.

Try to be consistent in placing pins in both views, if measuring from the centre of a temporary cone for example, place all pins at the centre in both views as much as possible. Take measurements from ground level.

Area selected for analysis should be at least approximately ten square metres. Defining an area that is too small may result in calibration failure.

Landmark pins placed too close to the camera, or at the edge of the defined area may be more likely to have issues with orientation arrows. Select different landmarks if possible.

Adjust any pins that result in arrows that are clearly not aligned with the others. If the issue persists, consider using a different landmark.