Troubleshooting CamControl (Mobotix): 7 Common Issues and Fixes

CamControl (Mobotix): Complete Setup Guide for Security Installers

Overview

This guide walks security installers through planning, hardware preparation, network configuration, installation, CamControl (Mobotix) software setup, testing, and maintenance. It assumes basic networking and CCTV installation experience and uses reasonable defaults for small-to-medium installations.

1. Pre-install planning

• Site survey: Note camera locations, mounting heights, fields of view, lighting, and power sources.
• Coverage goal: Define detection vs. identification ranges (e.g., detect at 30 m, identify at 10 m).
• Network and power: Choose PoE (802.3af/at) where possible. Confirm switch capacity, VLANs, and PoE budget.
• Storage needs: Estimate retention (days) × camera bitrate; include handshake for motion vs. continuous.
• Compliance: Check local privacy/signage rules.

2. Hardware checklist

• Mobotix cameras (model-specific mounts and lenses)
• PoE switches or injectors (with sufficient wattage)
• NVR or server if using central recording (specs per camera count/bitrate)
• UPS for network and recording devices
• Network cables (Cat6 recommended), conduit, connectors
• Screwdrivers, drill, fittings, tilt/pozi adapters, fiber modules if needed

3. Network preparation

• IP addressing: Use static IPs or DHCP reservations. Reserve a dedicated subnet for cameras (e.g., 10.10.20.0/24).
• VLANs: Put cameras on an isolated VLAN with firewall rules restricting access to management and NVR.
• Quality of Service (QoS): Prioritize video streams.
• Firewall/NAT: Allow ports required by Mobotix (HTTP/HTTPS for web GUI, RTSP/ONVIF if enabled). Default web GUI ports: ⁄₄₄₃; confirm in camera docs.
• NTP: Point cameras to a reliable time server for synchronized timestamps.

4. Physical installation

1. Mount bracket at chosen location; ensure solid anchor and correct orientation.
2. Run Cat6 to each camera location; terminate at patch panel/switch.
3. Connect PoE to camera; power-on and wait for boot (model-dependent).
4. Seal all outdoor penetrations and use weatherproofing for connectors.

5. Initial camera access and basic configuration

1. Discover the camera on the network using Mobotix Discovery Tool or network scanner.
2. Log in to web GUI (default IP or via DHCP). Change default admin password immediately.
3. Set camera hostname and static IP or configure DHCP reservation.
4. Configure NTP, timezone, and correct system time.
5. Update firmware to the latest stable Mobotix release (follow release notes).
6. Enable HTTPS and upload a trusted TLS certificate if available.

6. CamControl (Mobotix) software setup

• Install CamControl: On the designated server/NVR, install CamControl per Mobotix instructions. Ensure OS and hardware meet requirements: CPU, RAM, storage IOPS for video.
• Database/storage: Point CamControl to the recording storage location. For multi-camera setups, use RAID or NAS with sufficient throughput.
• Add cameras: Use CamControl’s device discovery or add by IP. Use credentials created in step 5.
• Profiles and recording rules: Create recording profiles (continuous, scheduled, motion-triggered, event-based). Reasonable default: ⁄₇ recording for critical cameras, motion for perimeter.
• Analytics and events: Enable Mobotix built-in analytics (e.g., video motion, line crossing). Map analytics to CamControl events (alerts, recording triggers).
• User roles: Create operator and admin accounts; apply least-privilege permissions. Enable audit logging.

7. Video quality and storage optimization

• Bitrate and GOP: Use H.264/H.265; set GOP and bitrate per camera capability. Start with variable bitrate (VBR) and target 1–4 Mbps for 1080p depending on scene activity.
• Resolution and FPS: Use the minimum resolution/FPS that meets identification requirements. Common default: 1080p @ 15–20 FPS.
• Retention policy: Configure automatic pruning. Example: 14 days for regular, 90 days for critical areas.
• Edge vs. central recording: Use camera SD cards as backup; primary recording to central server.

8. PTZ and advanced features

• Configure presets, tours, and privacy masks.
• Integrate motion detection and analytics into preset activation (e.g., move to preset on alarm).
• If using third-party systems, enable ONVIF where supported and map streams.

9. Testing and commissioning

• Functional tests: Verify live view, playback, event-triggered recordings, and alerts.
• Network load test: Simulate peak activity to confirm switch/NVR throughput.
• Failover tests: Test power loss scenarios with UPS, and verify SD-card fallback recordings.
• Handover: Provide the client with login credentials (change admin password), system diagram, and basic user training.

10. Maintenance and troubleshooting checklist

• Weekly: Check camera online status, available storage, and event logs.
• Monthly: Apply firmware patches and verify system time sync.
• Quarterly: Review retention, archive critical footage, and test backups.
• Common fixes:
  • No video: confirm PoE power, IP conflict, and firmware.
  • Dropped frames: check network congestion, switch port, or NVR disk throughput.
  • Time drift: verify NTP settings and network reachability.

11. Security hardening

• Change default ports and administrative credentials.
• Use HTTPS and strong TLS ciphers; disable legacy protocols.
• Limit management access to specific IPs or VPN.
• Regularly update firmware and CamControl software.
• Monitor logs and enable alerts for login failures.

12. Quick reference checklist (installer day)

• Site survey complete and mount points marked.
• PoE switch and NVR powered and on UPS.
• Cameras physically mounted and connected.
• IPs assigned and recorded.
• Firmware updated, admin password changed.
• Cameras added to CamControl and recording configured.
• Event rules and user accounts set.
• Functional and failover tests passed.
• Handover package delivered to client.

If you want, I can produce a printable two-page commissioning checklist or a sample CamControl recording policy tuned for 10–50 cameras.