Something not working? Start here!

Seervision works with many combinations of hardware, and that means that there is a lot to configure to get everything up and running properly. Often, this configuration will have been done by Seervision in advance, but if that's not the case, and things aren't working, this guide should be a good first step.

If you are using Seervision with a Q-SYS setup or NC Series PTZ camera, please reach out for support via

This page has been divided into four sections:

  1. Debugging a PTZ setup
  2. Debugging a Robotic Head setup
  3. Interface-related debugging
  4. Getting Support

It may be faster to just Ctrl + F (or Cmd + F if you’re on a Mac) to find key words related to your issue. That’s why we put it all in one page!

Debugging a PTZ Setup

Are you getting a video signal?

Make sure you have a video connection from the PTZ to the Seervision server. In most cases, Seervision servers can take at most a FullHD signal. Anything more could result in no image appearing at all.

The only exception to this is if you explicitly opted for a 4k-capable Seervision server.

On the PTZ, make sure you are using the corresponding video output port.

Can you control the PTZ?

If you are moving the PTZ via the UI, but nothing is happening, it’s time to verify the connection between the Seervision server and the PTZ, see below.

Have you correctly configured the PTZ?

Double-check that you’ve correctly modified the settings as specified in the PTZ Quickstart (pan/tilt mode, focus control etc).

Debugging a Robotic Head Setup

Are you getting an SDI/NDI signal?

Make sure you have an SDI connection from the PTU to the Seervision server. In most cases, Seervision servers can take a 3G SDI (FullHD) signal. Anything more will result in no image appearing at all.

The only exception to this is if you explicitly opted for a 4k-capable Seervision Server.

Are you able to control the head?

In the interface, try to move the head, either with the joystick or with the pan/tilt bars at the bottom. If nothing happens:

  • Verify that the head is powered up
  • Verify that the head is correctly connected to the same LAN network as the Seervision server.
    • If possible, verify using the ping network utility that you can ping both the Seervision server and the robotic head.
  • Go into the Operations Server on the Seervision server and verify that the server has got the correct configuration for this head configured.

Are you able to control the lens’ zoom, focus and optionally iris?

If not, there may be an issue with the lens control configuration.

  • If you are using external lens motors (like PDMovie ones):
    • Are the lens motors powered on (LEDs should light up) and connected to the head or to the edge device?
    • Are the lens motors calibrated? Try to move the zoom, focus and iris rings by hand. If you can’t, the PDMovies are calbrated. If they move freely, long press on the bottom of the lens motor, which will cause it to automatically calibrate.
    • Are the lens motors LED colors corresponding to their function? Green for focus, red for zoom, blue for iris. To change the color, double press the button on the lens motor.
  • If you are using a lens with a servo:
    • Verify that the controls at the bottom set to (for manual) and not S (for servo)
    • Verify that the servo is connected to the power port on the camera
    • Verify that the servo is connected to the serial control port on the head

Other Debugging

Tracking performance is poor

This can be caused by quite a few things and it’s probably best to call in Seervision Support. However, in 80% of the cases, it means the correct lens isn’t selected. Verify that you have configured the correct lens by going to the Preferences (little cogwheel icon) in the UI, navigating to the Lenses tab, and confirming that you have selected both the right camera, as well as the right lens.

If that’s not the case, enable the Computer Vision stream under the Streams panel, to get a better feeling for whether the computer vision is causing the poor performance.


As frustrating as it can be to admit, sometimes a restart from scratch can help in fixing issues. We have three options for a restart, ranging from mild to “nuclear”:

In the System panel, click the Reset all Settings button to revert to our default configuration.

If the above didn’t work, head on over to the Operations Server, and click the Relaunch button to relaunch the UI. Allow a few minutes for the system to relaunch.

If that also didn’t work, the “nuclear” option is to just use the Reboot button in the Operations Server, which will restart the Seervision server. This will take a few minutes.

Getting Support

It may happen that the problem is nearly impossible to debug without some “insider information” Seervision Support can provide, no problem!

NOTE: While it can be a frustrating experience, try to provide as much detail as the situation allows when contacting Support. This helps us provide you with more targeted support, and hopefully a quicker resolution time.

If the problem is hardware/control related

Just shoot us an email and we’ll try to call you up and get it fixed as soon as possible.

You can contact or directly.

If it’s software/functionality/performance related

It’s often best to report a bug by the little insect button in the manual control panel. The system will record the last 2 minutes and you can provide details via the question mark icon to report a bug. We go through this process in more detail in our manual.