Validate Mobotix Night Vision Failure
Your Mobotix camera is showing no night vision output despite functioning during daylight. This typically stems from IR cut filter malfunction, firmware incompatibility, or misconfigured VMS integration. The solution lies in brand-specific tools like MxManagementCenter and MxThinClient diagnostics. Begin with quick checks before proceeding to advanced troubleshooting.
Quick Checks for Mobotix Night Vision Issues
Perform these 30-second checks to identify basic failures:
- Verify PoE link light: Confirm the switch port shows a solid green light for 802.3af/at power. For MOBOTIX MOVE SD-340-IR, ensure the 24V AC adapter is connected if using hardwired mode.
- Check VMS dashboard status: In MxManagementCenter, ensure the camera's night vision mode is set to 'on' or 'auto' under Setup > Event Control > Motion Detection.
- Ping the camera IP: Use
ping [camera_ip]to confirm network connectivity. If the camera responds but shows no night vision, proceed to advanced diagnostics. - Inspect status LED: Look for a solid red or amber light indicating IR LED failure. For MOBOTIX M73, remove the housing cover to access the reset button if needed.
- Power cycle via switch: Disable the switch port for 30 seconds then re-enable to reset the PoE link.
Diagnose Network Configuration
Check VLAN Assignment
In MxManagementCenter, navigate to Network > Camera Configuration. Ensure the camera is assigned to a VLAN with sufficient bandwidth and multicast support. Use the Network Health Check tool in MxThinClient to identify VLAN misconfigurations. For Mobotix devices, confirm the VLAN does not conflict with other camera VLANs or management VLANs.
Verify PoE Budget
Access your switch's PoE budget dashboard. For MOBOTIX MOVE SD-340-IR (802.3bt), ensure the switch supports PoE++ and the port is configured for Class 4 power. If the switch port shows Class 0, reconfigure the port to 802.3at or 802.3bt. Use the PoE Budget Calculator in MxManagementCenter to avoid overloading the switch.
Validate Firmware and VMS Integration
Ensure Firmware is Up to Date
In MxManagementCenter, go to Firmware > Update Management. Select the camera and confirm it is registered to the correct firmware channel (stable or beta). Use the Staged Rollout feature to apply updates incrementally. If the camera is stuck in a pending state, initiate a Manual Firmware Force Install via MxThinClient diagnostics.
Confirm VMS Stream Profile
Access your VMS platform (e.g. Wisenet WAVE) and validate that the camera is registered to the correct stream profile. For Mobotix night vision, ensure the profile includes IR sensor data. In MxManagementCenter, check Stream Profiles > Night Vision Settings to confirm ONVIF profile compatibility.
Use Brand-Specific Diagnostic Tools
Run MxThinClient Diagnostics
Launch the MxThinClient application and connect to the camera. Use the Thermal Analytics Status tool to verify the IR sensor is functioning. For MOBOTIX c71 models, ensure the dewarping settings in MxManagementCenter are not interfering with IR detection. Check the Event Log for errors related to the IR cut filter or motion detection modules.
Check IR Cut Filter Status
In the camera's web interface (access via Setup > Event Control > Motion Detection), verify that the IR cut filter is enabled. If the filter is disabled, enable it and restart the camera. For MOBOTIX M73 models, remove the housing cover to access the reset button if the camera fails to apply changes.
Advanced Troubleshooting Steps
Analyse VMS Database Consistency
If the camera is registered to the VMS but shows no night vision, run a VMS Database Consistency Check via MxThinClient. This identifies corrupted metadata related to night vision events. Re-register the camera in the VMS if the database shows inconsistencies. For large fleets, use the Batch Re-registration tool in MxManagementCenter.
Perform Packet Capture Analysis
Use Wireshark or similar tools to capture traffic on the camera's VLAN. Look for RTSP stream drops or ONVIF profile mismatches. For Mobotix cameras, ensure the VMS is using the correct ONVIF profile (e.g. Profile S for IR sensor data). If multicast traffic is failing, enable IGMP Snooping on the switch.
Factory Reset and Escalation
Reset Mobotix Camera
For MOBOTIX M73 models, remove the housing cover and press the reset button for 10 seconds. For MOBOTIX c71, use the supplied tool to remove the dome cover and access the reset button. For MOBOTIX MOVE SD-340-IR, access the maintenance port and press the reset button for 15 seconds. After reset, reconfigure the camera in MxManagementCenter and reapply firmware.
Escalate to Enterprise Support
If all steps fail, initiate an RMA Request via Mobotix's support portal. Include the Event Log from MxThinClient and a Packet Capture Analysis report. For UK customers, reference the Consumer Rights Act 2015 (6-year limitation period) when requesting repairs under warranty.
Enterprise Analysis
Enterprise-Specific Failures
- PoE power budget exhaustion: Multiple Mobotix cameras on the same switch may overload the PoE budget, causing IR LEDs to fail. Use the PoE Budget Calculator in MxManagementCenter to plan capacity.
- VMS licensing conflicts: Ensure your VMS platform (e.g. Wisenet WAVE) has sufficient licences for Mobotix-specific features like MxActivitySensor.
- Firmware incompatibility: Staged rollouts may leave some cameras on outdated firmware. Use the Firmware Channel Verification tool in MxManagementCenter to ensure all devices are on the same channel.
- UK-specific considerations: For Victorian terraced houses, verify that IR signal penetration is not blocked by 9-inch brick walls. Use the Network Health Check tool to identify signal degradation.
Keeping Your Mobotix System Running Smoothly
Enterprise Maintenance Strategies
Schedule firmware updates during off-peak hours using MxManagementCenter's Staged Rollout feature. Monitor PoE budget usage with the PoE Budget Dashboard tool. For large deployments, use the VMS Health Monitoring module to track camera status. 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.
UK Procurement and Lifespan
For Mobotix cameras, plan for 5-8 years of service. Replace microSD cards annually for continuous recording. Use surveillance-rated HDDs for VMS storage. Under the Consumer Rights Act 2015, UK customers have up to 6 years to claim faulty goods. If troubleshooting takes more than 30 minutes and basic steps haven't resolved the issue, hardware failure is likely.