Verify i-Pro Camera's Recording Configuration
If your i-Pro camera is not recording, the root cause likely lies in its integration with the VMS, firmware status, or network settings. Confirm the camera is correctly registered in the VMS platform (e.g. Wisenet WAVE) and that the iA mode is enabled for optimal performance. Use the i-PRO Configuration Tool (iCT) to check for firmware updates and network compliance. This guide assumes familiarity with enterprise networking and VMS platforms, so focus on advanced diagnostics specific to i-Pro systems.
Check VMS Dashboard Status
Begin by verifying the camera's status in the VMS platform. If the camera shows offline but responds to ping, the issue may be VMS-specific. Navigate to the camera's details in Wisenet WAVE and check for stream profile mismatches or licensing errors. If the camera is registered to the wrong VMS instance, re-register it using the iCT's VMS Integration Wizard.
Verify PoE Budget and Switch Configuration
Ensure the switch port assigned to the camera is configured for PoE++ (802.3bt) if using models like the WV-X2571LN PTZ. Check the PoE budget on the switch to confirm it is not exhausted. For i-Pro multisensor models (e.g. WV-S8574L), ensure the switch port is set to Class 4 to accommodate the higher power draw. Use the iCT's Network Diagnostics tool to identify if the camera is receiving the correct power level and if the PoE negotiation is successful.
Confirm VLAN and Subnet Settings
Access the i-PRO Configuration Tool and navigate to Network > VLAN Settings. Ensure the camera's VLAN matches the switch port configuration. If the camera is on a dedicated VLAN, verify that the switch port is set to Trunk mode and that the native VLAN is correctly assigned. For i-Pro S-Series models, check that multicast traffic is not being blocked by the switch's IGMP Snooping settings, as this can disrupt RTSP streams.
Test RTSP Stream and Authentication
Use the i-PRO Configuration Tool's Stream Tester to verify the RTSP URL is functioning. If the stream fails, check the camera's authentication settings in the web interface under Network > Authentication. Ensure Basic Auth is enabled and the credentials match those configured in the VMS. For i-Pro multisensor models, confirm that the RTSP profiles are correctly assigned to each sensor in the VMS platform.
Diagnose Firmware and AI Analytics Issues
Access the Firmware > Update Status section in the iCT to check if the camera is registered to the correct firmware channel (stable or beta). If an update is pending, ensure the VMS license allows firmware upgrades. For i-Pro S-Series models, verify that the AI Analytics Module is enabled in the camera's web interface under Setup > AI Application. If the module is disabled, re-enable it and restart the camera to ensure proper functionality.
Advanced Troubleshooting and Escalation
If basic fixes fail, proceed with advanced diagnostics. Use the iCT's Packet Capture tool to analyze network traffic and identify issues like RTSP stream drops or VMS handshake failures. For i-Pro multisensor models, run a sensor calibration in the iCT under Sensor > Calibration to ensure accurate motion detection and recording. If the issue persists, contact i-Pro support via their official portal, providing logs from the iCT, VMS, and switch port diagnostics.
Root Causes and Enterprise Considerations
Common root causes include PoE budget exhaustion, VLAN misconfiguration, VMS licensing errors, and firmware incompatibility. In the UK, ensure compliance with Building Regulations Part Q for data retention and consider GDPR implications for camera footage storage. For i-Pro S-Series models, verify that the AI Analytics Module is enabled and that the iA mode is configured for optimal performance in dynamic lighting conditions.
Prevention and Long-Term Maintenance
Implement a firmware update schedule using the iCT's Staged Rollout feature to avoid disruptions. Monitor the VMS database for consistency and allocate sufficient PoE budget on switches for i-Pro multisensor models. Use SNMP monitoring to track switch port utilization and QoS policies to prioritize VMS traffic. 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 and Lifecycle Planning
i-Pro wired cameras typically last 5-8 years, while multisensor models like the WV-S8574L may require earlier replacement due to sensor degradation. For UK users, the Consumer Rights Act 2015 grants a 6-year right to bring a claim for faulty goods. If troubleshooting exceeds 30 minutes and basic steps (restart/reset/reconnect) fail, the issue is likely hardware-related. Replace SD cards every 1-2 years with high-endurance models (Samsung PRO Endurance/SanDisk High Endurance) to avoid corruption.