Verify Your Mobotix Camera's Video Export Configuration
Mobotix video export failures often stem from misconfigured VMS settings or firmware incompatibilities. This guide provides enterprise-grade diagnostics to resolve export issues within minutes. Begin by confirming the camera's RTSP stream profile matches the VMS requirements and that the firmware channel is set to stable updates. If export fails with a 'file too large' error, check the VMS export format settings in MxManagementCenter and ensure edge storage is enabled for large file transfers.
Quick Checks for Mobotix Video Export Issues
Perform these 30-second checks before diving into advanced diagnostics:
1. Check VMS Dashboard Status
Verify the camera is online in the VMS interface. If it shows offline but responds to ping, the issue may be VMS-specific rather than network-related.
2. Confirm PoE Link Light
Ensure the switch port has a solid green PoE link light. A blinking or absent light indicates PoE negotiation failure.
3. Ping the Camera IP
From the VMS server, ping the camera's IP address. If packets are lost, investigate switch port configurations or VLAN segmentation.
4. Verify Status LED
Check the camera's front panel for LED status: green = normal, amber = warning, red = critical. A red light may indicate firmware update errors or storage failures.
5. Power Cycle via Switch
Disable and re-enable the switch port for 30 seconds to reset the camera's network stack.
Your Network Configuration Checks
Check VLAN Assignment
In MxManagementCenter → Network Settings → VLAN Configuration, ensure the camera is assigned to a dedicated VLAN with no overlapping subnets. VLAN mismatches can prevent RTSP stream negotiation.
Validate PoE Budget
For PoE++ (802.3bt) cameras like the MOVE SD-340-IR PTZ, confirm the switch supports Class 4 power delivery. Use MxThinClient diagnostics to check for PoE negotiation failures — a Class 0 reading indicates a power mismatch.
Review DHCP Lease Exhaustion
If the camera fails to obtain an IP address, check DHCP server logs for repeated lease exhaustion. Configure a dedicated VLAN with sufficient IP pool size for Mobotix devices.
Enable Multicast/IGMP Snooping
For cameras using multicast streams, enable IGMP snooping on the switch to prevent packet loss. This is critical for Mobotix M73 models with dual-lens configurations.
Resolve VMS Integration Issues
Configure RTSP Stream Profile
In MxManagementCenter → Cameras → [device] → Stream Settings, ensure the RTSP profile matches the VMS's required resolution and bitrate. For Wisenet WAVE VMS, verify ONVIF Profile S compatibility.
Re-Register the Camera
If the VMS shows the camera as offline, re-register it via MxManagementCenter → Camera Management → Re-Add Camera. This resets the VMS device token and resolves licensing conflicts.
Check VMS Licence Modules
Ensure the VMS licence includes Mobotix support. In Avigilon Control Center, check Licence Manager for expired or missing modules. Licence expiry can prevent video export operations.
Test ONVIF/RTSP Manually
Use MxThinClient diagnostics to test the RTSP stream URL directly. If the stream fails, the issue may be firewall restrictions or authentication mode mismatches.
Advanced Firmware Management
Check Firmware Channel
In MxManagementCenter → Camera Settings → Firmware Updates, ensure the camera is on the stable firmware channel. Beta firmware versions can conflict with VMS analytics modules.
Use Staged Rollout for Large Deployments
For enterprise deployments, use staged firmware rollout to avoid export failures during updates. This allows rollback if compatibility issues arise.
Factory Reset for Firmware Stuck States
If a firmware update is stuck, perform a factory reset via the reset button (model-specific instructions apply). For MOBOTIX c71, remove the dome cover using the supplied tool to access the reset button.
Enterprise Support Escalation
Capture Diagnostic Logs
Use MxThinClient diagnostics to capture packet loss and RTSP stream latency — export the logs as .zip files and share them with Mobotix support via their portal. Include VMS event logs and firmware version details.
Initiate Hardware Replacement Request
If the issue persists after firmware updates and network checks, initiate an RMA via MxManagementCenter → Support → Hardware Replacement Request. For UK users, reference Building Regulations Part Q compliance in your request.
Root Causes of Mobotix Video Export Failures
Enterprise video export failures often stem from PoE budget exhaustion across switches, DHCP scope exhaustion in camera VLANs, or VMS licensing issues. For UK deployments, GDPR retention policies may conflict with export requirements. Ensure edge storage is enabled for large file transfers and verify firmware compatibility with VMS analytics modules.
Long-Term Mobotix Maintenance Tips
Schedule Firmware Updates
Set a quarterly firmware update schedule in MxManagementCenter to avoid compatibility drift. Use staged rollout for large deployments.
Monitor VMS Health
Implement SNMP monitoring for VMS health and QoS policies to prioritize RTSP streams. For Mobotix MOVE SD-340-IR PTZ, ensure PoE++ (802.3bt) compatibility with the switch.
Plan PoE Budget Headroom
Allocate 20% headroom on switch ports for PoE++ (802.3bt) cameras. Use MxThinClient diagnostics to monitor PoE negotiation states regularly. 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.
When to Replace Your Mobotix Video Equipment for Mobotix Cameras
Enterprise camera lifecycle planning should consider wired camera lifespan (5-8 years) and battery degradation (3-5 years). For UK users, the Consumer Rights Act 2015 provides a 6-year right to bring a claim for faulty goods. If troubleshooting exceeds 30 minutes and basic steps fail, hardware replacement is likely required. Use MxManagementCenter → Support → Hardware Replacement Request to initiate RMA processes.