Mobotix Pink/Purple Tint on Video: Enterprise Fix Guide

Verify Your Mobotix Camera's Network Configuration

If your Mobotix camera displays a pink or purple tint in video footage, this typically indicates an issue with the IR cut filter, sensor calibration, or firmware. The tint may persist during both day and night modes or appear only in low-light conditions. Begin by verifying basic network settings and firmware updates before proceeding to advanced diagnostics.

Check VMS Dashboard Status

Log into your VMS platform (e.g. MxManagementCenter) and confirm the camera is listed as Online. If it appears offline, ping the camera's IP address from the management server. A successful ping confirms network connectivity but does not rule out video processing errors.

Verify PoE Link Light

Ensure the PoE switch port shows a green link light. If the port is amber or off, the camera may not be receiving sufficient power. For MOBOTIX MOVE SD-340-IR PTZ models, confirm the switch supports PoE++ (802.3bt). For MOBOTIX M73 models, verify the PoE budget on the switch is not exhausted.

Power Cycle the Camera

Disable the PoE port on the switch for 30 seconds, then re-enable it. This forces the camera to re-establish its network connection and may reset transient issues.

Diagnose Mobotix Color Distortion

Check VLAN Configuration

1. Open MxManagementCenter and navigate to Camera > Network Settings.
2. Confirm the camera is assigned to a dedicated VLAN with QoS prioritization enabled for video traffic.
3. If the camera communicates across multiple VLANs, ensure the switch port is configured as trunk and IGMP snooping is disabled.
4. Verify the VLAN has sufficient bandwidth (minimum 100 Mbps for 1080p streams).

Validate Firmware Channel

1. In MxManagementCenter > Camera Health > Firmware Status, check the camera's firmware channel.
2. If the camera is on a beta firmware channel, switch to stable and restart the device.
3. For staged firmware rollouts, isolate the affected camera and perform a direct firmware update via the web interface.

Test RTSP Stream Manually

1. Open a web browser and enter the RTSP URL: rtsp://[camera_ip]:554/cam/realmonitor?channel=1&stream=0&user=[username]&password=[password]``.
2. Replace [camera_ip], [username], and [password] with the camera's details.
3. If the stream plays without distortion, the issue lies in the VMS integration. If the distortion persists, the problem is likely hardware-related.

Advanced Mobotix Pink Purple Tint Troubleshooting

Use MxThinClient Diagnostics

1. Install MxThinClient on a device on the same network as the camera.
2. Launch the tool and select Packet Capture for the camera's IP address.
3. Analyse the captured data for RTSP/ONVIF traffic anomalies or network congestion.
4. Export the Event Log and Network Health Check report for escalation to Mobotix support.

Check MicroSD Card Health

1. Access the camera's web interface via Setup > Storage > MicroSD Card.
2. Verify the card is industrial-grade (e.g. Samsung PRO Endurance) and has sufficient remaining write cycles.
3. Replace the card if it shows error codes or reduced capacity.

Reconfigure Dewarping Settings

1. For MOBOTIX c71 models, open MxManagementCenter > Viewing Options more than 360° Dewarping.
2. Ensure dewarping is enabled and the viewing PC meets hardware requirements (minimum 8GB RAM, 4-core CPU).
3. If the issue persists, disable dewarping temporarily to confirm it is not the root cause.

Support Escalation Path

Submit a Support Ticket

1. Log into the Mobotix support portal at https://www.mobotix.com/en/support.
2. Include the Event Log, Network Health Check report, and Firmware Management logs.
3. For enterprise clients, escalate to Tier 2 support with details on VMS integration and firmware compatibility.

Factory Reset Specific Models

1. MOBOTIX M73: Remove the housing cover and press the reset button for 10 seconds.
2. MOBOTIX c71: Use the supplied tool to remove the dome cover and press the reset button for 10 seconds.
3. MOBOTIX MOVE SD-340-IR PTZ: Access the reset button through the maintenance port and hold for 15 seconds.
4. After reset, reconfigure the camera in MxManagementCenter and reapply firmware updates.

Root Causes and Prevention

Enterprise-Relevant Root Causes

• PoE budget exhaustion across the switch may cause intermittent power delivery.
• DHCP scope exhaustion in the camera VLAN may prevent IP assignment.
• VMS licensing issues or database corruption may affect video processing.
• Firmware incompatibility after a staged rollout may introduce rendering errors.
• UK-specific: Ensure Building Regulations Part Q compliance for thermal cameras and GDPR retention policy alignment for edge storage.

Preventive Measures

• Schedule firmware updates during off-peak hours and use staged rollouts for large deployments.
• Configure a dedicated VLAN for cameras with QoS prioritization and IGMP snooping disabled.
• Monitor PoE budget headroom and use surveillance-rated HDDs for edge storage.
• 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.

Equipment Lifespan Guide

Camera Lifespan and Refresh

• Wired cameras: 5-8 years typical. Replace when sensor degradation or firmware EOL is imminent.
• Battery cameras: 3-5 years typical. Replace after 300-500 charge cycles.
• NVR HDDs: 3-5 years typical. Use surveillance-rated HDDs (WD Purple/Seagate SkyHawk).
• MicroSD cards: 1-2 years typical with continuous recording. Use high-endurance cards for Mobotix storage.
• UK consumers: Under the Consumer Rights Act 2015, you have up to 6 years to claim faulty goods (5 years in Scotland).