Verify Your Mobotix Camera's AI Detection Configuration
Your Mobotix camera is misidentifying objects or missing people. This typically stems from AI detection model limitations, lighting conditions, or incorrect confidence thresholds. The solution involves verifying sensor calibration, adjusting detection parameters, and ensuring firmware compatibility with your VMS platform. Proceed with the following steps to resolve the issue.
Quick Fixes for Mobotix Person Detection Issues
Before diving into advanced diagnostics, perform these 30-second checks:
- Check VMS dashboard status: In MxManagementCenter, ensure the camera shows Online and Analytics Enabled under Camera Status.
- Verify PoE link light: Confirm the switch port shows a solid green LED (Class 3 for Mobotix models requiring 802.3at).
- Ping the camera IP: Use
ping <camera_ip>from the VMS server to confirm network reachability. - Check status LED: A blinking blue LED on the Mobotix M73 indicates normal operation; amber suggests a configuration error.
- Power cycle via switch: Disable then re-enable the switch port to reset the PoE link.
Validate Network Configuration for Mobotix Detection Accuracy
Check VLAN Assignment
In MxManagementCenter, navigate to Camera Settings → Network. Ensure the camera is assigned to a dedicated VLAN (e.g. VLAN 100) with no QoS restrictions. For Mobotix MOVE SD-340-IR PTZ models, confirm the VLAN ID matches the switch port configuration exactly. Use the Network Health Check tool in MxThinClient to identify VLAN misconfigurations that may fragment detection data.
Confirm PoE Budget Allocation
Access the switch's PoE Budget Report. Verify that the Mobotix camera (e.g. MOBOTIX c71) is receiving at least 15.4W (802.3at). If the switch port shows Class 0, reboot the switch or reassign the camera to a port with adequate power. For models requiring 802.3bt (e.g. MOVE SD-340-IR), ensure the switch supports PoE++.
Check DHCP Lease and IP Assignment
In MxManagementCenter, go to Camera Settings → IP Configuration. Ensure the camera is assigned a static IP or the DHCP scope includes sufficient addresses. If the camera is on a VLAN with limited leases, expand the scope to avoid IP exhaustion. Use the DHCP Lease Monitor in MxThinClient to track lease assignments.
Diagnose Mobotix Analytics Module Health
Use MxThinClient for Diagnostic Checks
Open MxThinClient → Diagnostics → Thermal Analytics Status. For models with dual sensors (e.g. MOBOTIX M73), ensure both optical and thermal data are enabled. If the thermal sensor reports Corrupted Data, perform a factory reset via the maintenance port on the camera housing. For MOBOTIX c71 models, check the Thermal Fusion setting under Sensor Configuration.
Adjust Detection Confidence Threshold
In MxManagementCenter, navigate to Camera Settings → AI Detection → Confidence Level. Set the threshold between 75% and 90% for environments with high false positives. For MOBOTIX S ONE Dual models, enable Multi-Sensor Fusion to improve accuracy in crowded areas. Save changes and wait 10 minutes for the AI model to recalibrate.
Verify VMS Integration Settings
Ensure your VMS platform (e.g. Wisenet WAVE VMS) is configured to use the correct RTSP stream profile. In MxManagementCenter, go to Stream Configuration → RTSP Profile and select Main Stream (1080p) for optimal detection accuracy. If using ONVIF Profile S, confirm the VMS is set to Profile S in the camera's ONVIF Settings.
Advanced Troubleshooting for Mobotix Detection Failures
Perform a Packet Capture for Network Issues
Use Wireshark or MxThinClient's Packet Capture tool to monitor traffic on the camera's VLAN. Look for RTSP stream drops or multicast fragmentation that may disrupt detection analytics. For Mobotix MOVE SD-340-IR PTZ models, ensure RTSP over UDP is enabled in Stream Configuration.
Repair VMS Database Corruption
If detection errors persist, open MxManagementCenter → VMS Integration → Database Health Check. Run a Consistency Scan to identify corrupted analytics data. For large deployments, use the Database Repair Tool in Enterprise Tools to rebuild the analytics index.
Escalate to Mobotix Enterprise Support
If all steps fail, contact Mobotix support via their official portal. Provide the Event Log from MxThinClient and the Firmware Channel the camera is using. For UK-based deployments, mention Building Regulations Part Q compliance in your support request to expedite resolution.
Root Causes of Mobotix Person Detection Failures
Enterprise-level issues often stem from PoE budget exhaustion across switches, DHCP scope exhaustion, or VMS licensing limitations. For UK installations, GDPR retention policies may conflict with detection analytics if not configured correctly in MxManagementCenter. Ensure your Mobotix firmware is compatible with your VMS platform's ONVIF Profile and that Edge Storage Failover is enabled for redundancy.
Prevention and Long-Term Maintenance for Mobotix Cameras
Schedule quarterly firmware updates via MxManagementCenter → Firmware Management. Use a Dedicated Camera VLAN with QoS prioritization for analytics traffic. Monitor PoE budget headroom using the Power Allocation Tool in MxThinClient. Full disclosure: we built scOS to address exactly this — the complexity of managing enterprise camera fleets across VLANs — using permanently powered cameras connected via ethernet.
Replacement Planning for Mobotix Camera Lifecycles
Wired Mobotix cameras (e.g. MOBOTIX M73) last 5-8 years; replace if detection accuracy degrades beyond 80% in MxThinClient diagnostics. For UK deployments, factor in salt air corrosion near coasts when planning replacements. Use Surveillance-rated HDDs (WD Purple/Seagate SkyHawk) for VMS storage, replacing them every 3-5 years. If troubleshooting exceeds 30 minutes without resolution, consider hardware failure and initiate an RMA via Mobotix's official support portal.