Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Using Localhost IP Address

If you have problems trying to view recorded track data, then check to see the IP address of the Management Server:

...

Using localhost (127.0.0.1) as an IP address is not good practice as the system will not store track data and will not connect the UI to a separate PC.

...

  1. Therefore, the Management Server must be configured to use an accessible interface and IP address.

  2. The solution to this is to reinstall the system software with the database accessed via its outward facing IP address.

...

  1. Check the settings in the User Details:

    Image RemovedImage Added

  2. Navigate to the Background Display settings and check to see if there is a background image option selected. If the Background Map Type is set to None, as in the example below, then click Edit:

    Image RemovedImage Added

  3. Then select Display Background Image and either Google Map or Open Street Map from the drop down list:

    Image RemovedImage Added

  4. If you select Google Maps, there are additional options:

    Image RemovedImage Added

  5. Make a selection and click Save.

...

  1. Check that the camera has been added to the Camera Controller:

    Image RemovedImage Added

Incorrect Stream Format

...

  1. This setting can be changed in the UI Stream within User Settings - not Camera Settings.

  2. You will need to check what the correct Stream Format is, as it will vary depending on the camera model.

    Image RemovedImage Added

VLC Media Player has not been installed

...

  1. Check that you have not zoomed out of the PPI Map Display too far. Witness has been designed to not show any radar data when this occurs:

    Image RemovedImage Added

  2. Simply zoom back in, and the radar data will reappear:

    Image RemovedImage Added

Radar not Allocated to Track Engine

...

  1. Navigate to the Topology page and ensure that the radar has been allocated to a Track Engine:

    Image RemovedImage Added

  2. If the radar has not been allocated as in the example above, drag and drop the radar into the Track Engine:

    Image Removed

    in the example above, drag and drop the radar into the Track Engine:

    Image Added

No Recorded Track Data

If you have problems trying to view recorded track data, then check to see the IP address of the Management Server:

...

Using localhost (127.0.0.1) as an IP address is not good practice as the system will not store track data and will not connect the UI to a separate PC.

  1. Therefore, the Management Server must be configured to use an accessible interface and IP address.

  2. The solution to this is to reinstall the system software with the database accessed via its outward facing IP address.

Time Syncing

If an alarm is given, but tracks do not appear, even though an alarm may be given, there could be a time syncing problem. PC’s will stay to within a second in a month, but other devices such as radar, cameras etc. may not. All devices should be synced to within a second, sometimes to within a quarter of a second.

...

  1. The IP address of the radar is found in Witness>Topology>Track Engine> Radar:

    Image RemovedImage Added

     

  2. Next, go to Windows search and open a 'command prompt' (cmd).

  3. In the command prompt type ping + radar IP address; e.g. ping 10.77.2.210 

    Image RemovedImage Added

  4. Press Enter. If the command prompt replies 4 times as in the picture below, then the network connection is good.

...

  1. The IP address of the camera is found in Witness>Topology>Track Engine> Camera>Connection Details:

    Image RemovedImage Added

  2. Next, go to Windows search and open a 'command prompt' (cmd).

  3. In the command prompt type ping + camera IP address; e.g. ping 10.77.3.11

    Image RemovedImage Added

  4. Press Enter. If the command prompt replies 4 times as in the picture below, then the network connection is good.

...