Topic
This article describes how to maintain and troubleshoot radar track visibility and camera slew-to-cue performance in IP Security Center (IPSC) / Control Center environments. It also covers general database maintenance, alarm handling, camera status checks, and connector/SDK version reviews that help maintain system stability and situational awareness during critical events.
Description
Radar track visibility issues in IPSC can be caused by several factors. These include SQL Server storage problems such as full data folders, incorrect IP configurations for radar servers, large SQL tables that prevent proper data transmission, and service connectivity issues between radar and IPSC servers. When radar track visibility problems occur, recommended troubleshooting steps include clearing SQL Server log space, verifying IP configurations, restarting relevant services, and checking network connectivity between radar and mapping systems.
Camera slew-to-cue issues can arise from multiple sources. These include configuration mismatches between RadarWatch and IPSecurityCenter, service connectivity problems, and hardware control mechanism failures. To troubleshoot camera slew-to-cue problems, recommended actions include verifying configuration settings in RadarWatch and IPSecurityCenter, checking IP-to-serial connection settings, ensuring that only one system (either RadarWatch or IPSecurityCenter) manages PTZ controls, and performing a hard reboot of the camera device if no configuration issues are identified.
Ongoing database and system maintenance is important for stable IPSC operation. Recommended activities include performing database maintenance such as removing very old data; one reference noted removing data older than three months and highlighted large EventDetailsAMAG table growth. Monitoring and resolving alarms regularly is also important; one reference captured more than 3,000 unresolved alarms and recommended resolving alarms at least daily. In addition, checking camera status and addressing offline cameras is advised, as offline cameras can be caused by conditions such as adverse weather. Finally, reviewing connector and SDK versions is recommended, including updating the Milestone connector and using a 64-bit SDK to unlock more resources.