AI-POWERED DOCS
What do you want to know?
Networking: IP/Subnet
This page explains IP addressing and subnet concepts essential for properly deploying and managing OV20i cameras in industrial network environments.
IP Addressing Fundamentals for OV20i
Default Network Configuration
The OV20i comes with predefined network settings designed for immediate deployment:
Factory Default Settings:
- Primary IP Address:
192.168.0.100(static) - Subnet Mask:
255.255.255.0(/24 network) - Emergency USB IP:
192.168.55.1(fixed, non-configurable) - DHCP: Disabled by default
IP addresses are formatted as XXX.XXX.XXX.YYY. It is usually defined by your IT department, where the XXX.XXX.XXX should be identical across all devices, and YYY is device-specific, so choose an IP for your computer that is not used by any other device on the line.
Network Accessibility Requirements
Same Subnet Principle: When connecting your computer to the camera, it's important to ensure both devices are on the same subnet. If your computer and camera have different subnet configurations, your computer may not be able to locate the camera, and the connection may fail.
Subnet Planning and Network Architecture
Understanding Subnet Segmentation
Subnet Mask 255.255.255.0 Explanation:
This subnet can be identified by the subnet mask of 255.255.255.0. Devices within this subnet will have IP addresses like 192.168.0.1, 192.168.0.2, and so on.
Single Subnet Industrial Example:
Factory Network Subnet (192.168.0.x):
- OV20i Camera:
192.168.0.100(factory default) - QR Code Reader:
192.168.0.20 - PLC Controller:
192.168.0.50 - HMI Panel:
192.168.0.30 - Control PC:
192.168.0.10 - Subnet Mask:
255.255.255.0 - Purpose: All production devices on same network for easy communication
Alternative Subnet Assignment: If your factory uses a different subnet range, all devices can be configured accordingly:
- OV20i Camera:
192.168.1.100 - QR Code Reader:
192.168.1.20 - PLC Controller:
192.168.1.50 - Control PC:
192.168.1.10 - Subnet Mask:
255.255.255.0
Device-Specific IP Assignment Strategy
Unique IP Requirement:
Each device on the network must have a unique IP address within its subnet. The device-specific portion (YYY) should be:
- Unique - Not used by any other device on the line
- Documented - Recorded for maintenance and troubleshooting
- Planned - Allocated according to device type or location
Static IP vs DHCP Configuration
Static IP Addressing (Recommended for Production)
When to Use Static IP:
- ✅ Production environments - Consistent, predictable addressing
- ✅ Critical systems - Eliminates DHCP dependencies
- ✅ Multi-camera installations - Simplified management and troubleshooting
- ✅ PLC integration - Fixed addressing required for industrial protocols
Static IP Benefits:
- Reliability - No dependency on DHCP server availability
- Predictability - Consistent addressing for maintenance
- Integration - Required for many industrial automation systems
- Security - Easier to implement access control and monitoring
DHCP Addressing (Development and Testing)
DHCP Capability: This IP address is configurable and can be automatically assigned via DHCP or changed to suit your networking needs.
When to Use DHCP:
- ✅ Development environments - Simplified network setup
- ✅ Testing scenarios - Reduced configuration overhead
- ✅ Temporary installations - Quick deployment without IP planning
- ✅ Network with DHCP reservations - Combines DHCP convenience with static behavior
⚠️ IP Conflict Prevention and Resolution
Common IP Conflict Scenarios
Router IP Conflicts:
Your network might be utilizing the same IP as the camera, like 192.168.0.100 (some routers have the same default IP). This can cause confusion as there is an IP conflict.
Prevention Strategies: To prevent IP conflicts and ensure smooth connectivity for your camera, it's essential to configure a unique IP address for each device on your network.
IP Conflict Detection and Resolution
Detection Methods: To detect IP conflicts, use an IP scanner tool to identify any devices sharing the same IP address.
Resolution Process: If conflicts are found, adjust the IP address of one or more devices to ensure uniqueness and eliminate conflicts.
Emergency Access for Conflicts: It is best to connect with a Micro USB and change the IP to unique IP setting when conflicts occur.
Industrial Network Integration
TCP Communication Requirements
Network Range Compatibility: The camera's IP address must be in the same range as the device it is communicating with.
Node-RED TCP Integration:
- TCP Input Ports - Camera listens on assigned ports
- TCP Output - Camera sends data to specified device IP addresses
- Port Management - Assignment of free ports for communication
- IP Range Matching - Ensures successful device-to-device communication
Multi-Camera Network Topology
Subnet Planning for Multiple Cameras:
- Camera 1:
192.168.0.101 - Camera 2:
192.168.0.102 - Camera 3:
192.168.0.103 - Control PC:
192.168.0.10 - PLC Gateway:
192.168.0.50
Network Segmentation Benefits:
- Traffic Isolation - Separates vision traffic from control traffic
- Performance Optimization - Reduces network congestion
- Security Enhancement - Limits access between network segments
- Troubleshooting Simplification - Isolates issues to specific subnets
Configuration Best Practices
Network Documentation Requirements
- IP Address Registry - Document all assigned addresses
- Subnet Maps - Visual representation of network topology
- Device Inventory - Correlation between IP addresses and physical devices
- Change Management - Track IP address modifications over time
Emergency Access Planning
Micro-USB Recovery:
- Fixed IP:
192.168.55.1(bypasses network configuration) - No Configuration Required - Always accessible regardless of network settings
- Recovery Purpose - Change IP settings when network access fails
- Troubleshooting Tool - Diagnose and resolve connectivity issues
Network Monitoring and Maintenance
Ongoing Network Management:
- IP Scanner Tools - Regular conflict detection
- Performance Monitoring - Network utilization and response times
- Documentation Updates - Maintain current network maps
- Security Audits - Regular review of network access and permissions
Network Requirements for IT Teams
This section is designed to be shared with your IT or Network Engineering team before deployment. The OV20i operates as a self-contained local server: all AI inference, image storage, and the user interface run on the device itself. No cloud connectivity is required for day-to-day operation. Users access the system through a web browser on the factory LAN.
Initial device activation requires a temporary internet connection. After activation, the camera operates fully offline. Contact support@overview.ai if internet is not available during setup.
Network requirements summary
| Requirement | Details |
|---|---|
| Network Speed | Gigabit Ethernet (1 Gbps) recommended for best dashboard and image library performance |
| Ethernet Interface | 10/100/1000 Base-T, M12 X-Coded connector (M12-to-RJ45 cable included) |
| IP Configuration | Static IP recommended for production; DHCP also supported |
| Default IP Address | 192.168.0.100 (static, configurable) |
| Default Subnet | 192.168.0.X / 255.255.255.0 (/24) |
| Required Port | TCP Port 80 (HTTP). Port 443 (HTTPS) optional, can be enabled for encrypted access |
| Supported Browsers | Google Chrome (recommended), Microsoft Edge, or Safari. Firefox is not supported |
| Cloud / Internet Access | Not required for operation. Required one-time for initial device activation |
| Emergency USB IP | 192.168.55.1 (always available via USB connection for recovery) |
Bandwidth requirements
Live Video Stream
The OV20i serves a browser-based livestream at a fixed rate of 5 Mbps per active browser session. If multiple users are viewing the livestream simultaneously, multiply accordingly.
Dashboard and Image Library
Browsing the on-device image library (reviewing captured inspection images, training data, etc.) benefits significantly from a Gigabit connection. On slower links, loading large image sets will feel sluggish.
Image Data Transfer to MES / External Systems
If your deployment sends captured inspection images off the camera to an MES, data historian, or network storage, the required bandwidth depends on your inspection cycle time and number of cameras. Each captured image is approximately ~0.5 MB at full 1.6 MP resolution. Use the formula below to estimate your sustained bandwidth requirement:
Bandwidth (Mbps) = Images per second x 0.5 MB x 8 bits x Number of cameras
| Scenario | Cycle Time | Cameras | Sustained Bandwidth |
|---|---|---|---|
| Slow line | 1 image every 30 sec | 1 | ~0.13 Mbps |
| Typical line | 1 image per second | 1 | ~4 Mbps |
| Fast line | 3 images per second | 1 | ~12 Mbps |
| Multi-camera | 1 image per second | 4 | ~16 Mbps |
| High-throughput multi-camera | 3 images per second | 4 | ~48 Mbps |
Capture rate by itself does not consume network bandwidth if images remain stored and processed on the camera. Network load rises when the live video is viewed, images are browsed in the library, or captures are exported to external systems in real time.
PLC / Industrial Protocol traffic (EtherNet/IP, PROFINET, OPC UA) is negligible, typically small pass/fail payloads measured in bytes.
Ports, services, and firewall configuration
The OV20i uses a minimal network footprint for standard operation.
| Purpose | Direction | Port / Service | Required | Notes |
|---|---|---|---|---|
| Web UI (default) | To camera | TCP 80 | Yes | Standard browser access to the local interface |
| Web UI (secure) | To camera | TCP 443 | Optional | Used when HTTPS is enabled. HTTP remains available by default |
| Product activation | Camera to internet | Internet access | One-time | Needed for self-service activation on first connection |
| Firmware updates | Camera to internet | Internet access | Optional | Not needed for normal local inspection use |
| Time synchronization | Camera to NTP source | NTP (UDP 123) | Optional | Recommended for production so timestamps remain accurate |
| Custom Node-RED integrations | Customer-specific | Customer-specific | Optional | Any custom TCP, MQTT, REST, or other flows should be documented per application |
For standard deployment, the only confirmed browser-access port required on the camera is TCP 80, unless the customer elects to enable HTTPS (TCP 443). Any additional ports depend on the specific industrial protocol or Node-RED customization implemented for the line.
Security and access recommendations
- Use wired Ethernet only. Avoid Wi-Fi for production access or live monitoring, as unstable wireless bandwidth can cause freezing or disconnects.
- Isolate on a dedicated VLAN. Place the camera on a production VLAN or restricted network segment and allow access only from approved engineering and operations endpoints.
- Enable HTTPS when routing across segments. If the camera must be accessed across routed VLANs, over VPN, or under a corporate encryption policy, enable HTTPS (TCP 443) on the device.
- Use static addressing or DHCP reservations so the camera IP remains stable for operators, HMIs, PLCs, and support personnel.
- Change default passwords and document all IP assignments and any custom integration ports opened for the line.
- Telemetry can be enabled or disabled in system settings based on customer policy.
Industrial protocol integration
The OV20i supports the following industrial communication protocols for PLC and MES integration. These operate over the same Ethernet connection.
- EtherNet/IP
- PROFINET
- OPC UA
- Modbus TCP
- MQTT (via built-in Node-RED for custom integrations)
- Digital I/O: 2 digital outputs (NPN sinking), 2 digital inputs + 1 trigger input (hardwired via M12 connector, not network)
Pre-deployment checklist for IT teams
- Unique camera IP assigned or DHCP reservation created (default: 192.168.0.100)
- Camera and authorized client devices can reach each other on the intended subnet or routed path
- Subnet mask matches across all communicating devices (typically 255.255.255.0)
- TCP port 80 allowed inbound to camera IP, or TCP 443 if HTTPS is enabled
- Internet access approved if self-service activation, firmware updates, or cloud features are required
- NTP source available if production timestamp synchronization is required
- Gigabit Ethernet confirmed end-to-end to the camera's network drop
- Chrome or Edge workstation available for setup and validation
- Camera placed on appropriate VLAN with access restricted to approved endpoints
- Estimate image transfer bandwidth based on cycle time and camera count
- Live view, recipe access, and library performance tested from the actual production network
- Any PLC or Node-RED custom integration requirements documented separately and approved by controls / IT