Verify Mobotix Night Vision Functionality
Your Mobotix camera shows partial video but IR night vision fails despite stable network connectivity. This typically stems from IR hardware faults, firmware misconfigurations, or thermal sensor interference. The solution requires brand-specific tools like MxManagementCenter and MxThinClient diagnostics.
Quick Checks for Mobotix Night Vision Issues
Perform these 30-second checks before diving deeper:
- Check VMS dashboard status: In MxManagementCenter, verify the camera appears as 'Online' and that Night Vision Mode is enabled in the device properties.
- Verify PoE link light: Ensure the switch port shows a solid green light (Class 3/4) and that the camera's power budget is within the switch's capacity (check PoE Budget Summary in MxManagementCenter).
- Ping the camera IP: From the VMS server, execute
ping <camera_ip>and check for 0% packet loss. If failed, confirm the camera's IP matches the Static IP setting in MxManagementCenter. - Power cycle via switch port: Disable the switch port for 30 seconds, then re-enable. This resets the camera's network stack without a full reboot.
Diagnose Network Configuration Issues
Check VLAN Assignment
In MxManagementCenter → Network → Camera Configuration:
- Confirm the camera's VLAN matches the switch port's VLAN setting
- Enable QoS prioritization for video streams (set DSCP to 46)
- Ensure IGMP Snooping is disabled on the switch port
- For dual-lens models, verify Multicast Streaming is enabled
Validate PoE Budget
Navigate to Switch Management in MxManagementCenter:
- Check the PoE Budget Summary for the camera's port
- Ensure the switch supports 802.3bt (PoE++) for models like the MOVE SD-340-IR
- For the M73 model, confirm the PoE Negotiation status shows 'Class 4' (30W)
- If budget is exceeded, reconfigure the switch port to a higher-powered port
Confirm Firmware Channel
In MxManagementCenter → Firmware → Channel Management:
- Ensure the camera is subscribed to the Stable firmware channel
- Check for pending updates in the Pending Updates tab
- For models like the c71, verify Thermal Analytics is enabled in the firmware settings
- If using a beta firmware version, consider rolling back to the Stable channel
Check IR and Thermal Sensor Settings
Verify Night Vision Mode
Access the camera's web interface via http://<camera_ip>:
- Navigate to Setup > Event Control > Motion Detection
- Ensure IR Night Vision is set to 'Auto' or 'On'
- For thermal cameras, confirm Thermal Analytics is enabled in MxManagementCenter
- Disable IR Cut Filter if using thermal sensors during daylight hours
Inspect IR LED Functionality
Using MxThinClient diagnostics:
- Connect to the camera via the MxThinClient tool
- Navigate to Hardware Diagnostics > IR LED Status
- Check for any IR LED Faults reported in the event log
- For the M73 model, inspect the Optical Sensor health in the diagnostics tab
- If IR LEDs are faulty, use the Hardware Replacement Wizard in MxManagementCenter
Advanced Diagnostics with MxManagementCenter
Run Network Health Check
In MxManagementCenter → Tools → Network Health Check:
- Select the camera and run a 10-minute scan
- Look for TCP retransmissions on port 554 (RTSP)
- Check for UDP packet loss on port 3702 (ONVIF)
- If anomalies are found, adjust switch port settings for jumbo frames (MTU 9000)
Analyse Thermal Analytics Status
For thermal cameras like the S ONE Dual:
- In MxManagementCenter → Camera Settings → Thermal Configuration
- Check Thermal Sensor Health and Analytics Module Status
- Ensure Thermal IR Cut Filter is set to 'Auto'
- Verify Thermal Analytics Zones are configured correctly in the web interface
Factory Reset for Mobotix Cameras
Model-Specific Reset Procedures
- 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. Access the reset button on the main board
- MOBOTIX MOVE SD-340-IR: Access the reset button through the maintenance port. Hold for 15 seconds
Post-Reset Configuration
After reset:
- Reassign the camera's static IP in MxManagementCenter
- Reconfigure VLAN settings and QoS prioritization
- Re-subscribe to the firmware channel
- Re-enable Thermal Analytics if applicable
Root Causes and Enterprise Considerations
Enterprise-Specific Failures
- PoE Budget Exhaustion: Confirm the switch's total power budget includes headroom for all connected devices
- VLAN Misconfiguration: Ensure all cameras share the same VLAN for consistent IR performance
- Firmware Incompatibility: Verify the camera's firmware version matches the VMS platform's requirements
- Thermal Sensor Interference: For dual-lens models, ensure Dewarping is enabled in MxManagementCenter
- UK Building Regulations: For sites with Brick-Cavity-Block construction, consider deploying PoE++ (802.3bt) switches to compensate for signal loss
Prevention and Long-Term Care
Enterprise Maintenance Practices
- Schedule quarterly firmware updates via Staged Rollout in MxManagementCenter
- Monitor PoE Budget Utilisation monthly in the switch management dashboard
- Enable SNMP Monitoring for real-time camera health alerts
- Use Industrial-Grade MicroSD Cards for edge storage (Samsung PRO Endurance recommended)
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.
Replacement Decisions for Mobotix Cameras
Camera Lifecycle Management
- Wired Camera Lifespan: 5-8 years (replace when sensor degradation impacts IR performance)
- Battery Camera Lifespan: 3-5 years (replace when battery holds less than 70% charge)
- MicroSD Card Lifespan: 1-2 years with continuous recording (use high-endurance cards)
- Consumer Rights Act 2015: UK consumers have up to 6 years to claim faulty goods under the CRA
- Troubleshooting Timeframe: If basic fixes take more than 30 minutes, hardware replacement is likely necessary