Verify Mobotix Motion Detection Configuration
Motion detection failure in Mobotix cameras often stems from misconfigured analytics modules or firmware incompatibilities. Begin by confirming the Motion detection toggle is enabled in MxManagementCenter under Camera Settings → Analytics. If the feature is disabled or set to low sensitivity, reconfigure it to high and ensure the detection range aligns with the camera's physical coverage. For models like the M73, verify the optical and thermal sensors are not obstructed and the detection angle matches the installed orientation.
Quick Fixes for Mobotix Motion Detection
Before diving into advanced diagnostics, perform these immediate checks:
- Verify VMS dashboard status: In MxManagementCenter, confirm the camera is online and motion detection is active in the Device Health tab.
- Check PoE link light: On the switch port, ensure the PoE negotiation is successful (Class 3 or 4). If the port shows Class 0, reconfigure the switch to support 802.3at or 802.3bt.
- Ping the camera IP: From the VMS server, use
ping[camera_ip]`` to confirm network reachability. If packets are lost, investigate switch port configurations or VLAN assignments. - Inspect status LED: On the camera housing, a solid green LED indicates normal operation. A flashing red LED suggests a firmware update failure or hardware fault.
- Power cycle via switch port: Disable the switch port for 10 seconds, then re-enable it to force a PoE reset and reinitialise the camera's network stack.
Diagnose Network Configuration in MxManagementCenter
Check VLAN Assignment
Access Network Settings in MxManagementCenter and confirm the camera's VLAN matches the switch port configuration. If the camera is on a separate VLAN from the VMS server, motion detection signals may be blocked. Use the Network health check tool in MxThinClient to validate VLAN compliance and identify any isolated traffic.
Validate PoE Budget
Ensure the switch port supports 802.3at or 802.3bt for models like the MOVE SD-340-IR. In MxManagementCenter, navigate to Power Management and confirm the PoE budget is within the switch's capacity. If the port shows Class 0, reconfigure the switch to support the required PoE standard.
Confirm DHCP Lease
In MxManagementCenter, check the DHCP lease for the camera to ensure it's not exhausted. If the camera is on a shared VLAN with other devices, expand the DHCP scope or assign a static IP to the camera.
Analyse Firmware and Analytics Module
Check Firmware Channel
Access Firmware management in MxManagementCenter and confirm the camera is on the stable channel. If the camera is on the beta channel, switch to stable to resolve compatibility issues with motion detection. Use the Firmware rollback feature if recent updates caused detection failures.
Validate Analytics Module Status
In MxManagementCenter, navigate to Device Health → Analytics Module. For models with thermal sensors (e.g. M73), ensure the thermal analytics engine is enabled and not in error. If the module is disabled, re-enable it via Thermal analytics settings and adjust the detection range to maximum.
Test RTSP Stream Profile
For models like the MOVE SD-340-IR, ensure the RTSP stream profile in MxManagementCenter is set to main (not sub). Sub-profiles may omit motion detection metadata, leading to false negatives. Use the RTSP stream URL directly in a media player to confirm motion detection signals are transmitted correctly.
Advanced Diagnostics with MxThinClient
Capture Network Packets
Use MxThinClient diagnostics to capture packets on the camera's network interface. Look for dropped packets or TCP retransmissions that could disrupt motion detection signals. If multicast traffic is blocked, enable IGMP snooping on the switch.
Check Event Logs
In MxManagementCenter, review the Event log for errors related to motion detection. Look for entries like 'Analytics module disabled' or 'Firmware update failed'. If errors persist, initiate a factory reset via the model-specific procedure and reconfigure settings.
Factory Reset for Mobotix Cameras
If basic fixes fail, perform a factory reset:
- MOBOTIX M73: Remove the housing cover to access the reset button on the main board. Press and hold for 10 seconds while powered.
- MOBOTIX c71: Use the supplied tool to remove the dome cover, then press the reset button on the main board for 10 seconds.
- MOBOTIX MOVE SD-340-IR: Access the maintenance port and press the reset button for 15 seconds until the reset sequence begins. After resetting, reconfigure VLAN assignments, firmware channel, and motion detection settings in MxManagementCenter.
Root Causes of Mobotix Motion Detection Failure
Enterprise-level failures often stem from PoE budget exhaustion across switches, DHCP scope exhaustion in camera VLANs, or firmware incompatibilities after staged rollouts. For UK deployments, condensation in junction boxes may corrupt firmware updates, requiring waterproof cable glands and self-amalgamating tape. Ensure GDPR retention policies do not conflict with motion detection analytics module operations.
Mobotix Motion Detection Preventive Maintenance Guide
Schedule regular firmware updates via staged rollouts in MxManagementCenter to avoid compatibility issues. Use dedicated camera VLANs with QoS policies to prioritise motion detection traffic. Monitor PoE budget headroom using MxThinClient diagnostics. Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.
Mobotix Motion Detection Repair vs. Replacement Guide and Support
If troubleshooting exceeds 30 minutes and basic fixes fail, contact Mobotix support via https://www.mobotix.com/en/support. For UK deployments, the Consumer Rights Act 2015 provides a 6-year limitation period for claiming faulty goods. Replace wired cameras after 5-8 years and battery-powered models after 3-5 years to avoid sensor degradation. Use surveillance-rated HDDs for VMS storage and high-endurance SD cards in hybrid models.