Skip to main content
All CollectionsKnowledge Base
Troubleshooting - Performance
Troubleshooting - Performance
Updated over a week ago

OSD and analysis keeps switching on and off.

  • CPU load is too high for the camera.

    • Make sure the stream of the camera is not visualized in unnecessary places
      because every visualization of the camera stream increase CPU load.

    • If recording on in-built motion detection is activated try to decrease the
      quality of the recording to free up CPU.

    • Deactivate recording on in-built motion detection and make sure in-built
      motion detection is deactivated.


A target enters the sterile zone and causes multiple alerts to be raised.

  • Adjust the Post-alarm time in the “Outputs” section. Please refer to the Setup guide.


A pontential target enters the sterile zone, but does not raise an alarm - missed detection

  • Contrast of the object against the background in the scene is too low.

    • Make sure the SafeZone-edge requirements are met (see “SafeZone-edge Requirements” document).

  • There is inadequate lighting in the scene or the low light performance of the camera is insufficient.

    • Make sure the SafeZone-edge requirements are met (see “SafeZone-edge Requirements” document).

  • SafeZone-edge has the sensitivity set too low.

    • Increase the sensitivity in the global scenario parameters.

  • The calibration is not precise enough.

    • Verify the calibration of the camera. Please refer to the Setup Guide.

  • Although the target is in the scene it is not matching a conditional scenario e.g. not moving from one zone to another in the zone crossing scenario.

    • Make sure the scenario is correctly specified, including conditions.

Did this answer your question?