Skip to main content

Networking: IP/Subnet

Networking: IP/Subnet

This page explains IP addressing and subnet concepts essential for properly deploying and managing OV80i cameras in industrial network environments.

IP Addressing Fundamentals for OV80i​

Default Network Configuration​

The OV80i comes with predefined network settings designed for immediate deployment:

Factory Default Settings:

  • Primary IP Address: 10.250.0.100 (static)
  • Subnet Mask: 255.255.255.0 (/24 network)
  • DHCP: Disabled by default

IP Address Format: 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 (10.250.0.x):

  • OV80i Camera: 10.250.0.100 (factory default)
  • QR Code Reader: 10.250.0.20
  • PLC Controller: 10.250.00.50
  • HMI Panel: 10.250.0.30
  • Control PC: 10.250.0.10
  • Subnet Mask: 10.250.0.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:

  • OV80i Camera: 10.250.0.100
  • QR Code Reader: 10.250.0.20
  • PLC Controller: 10.250.0.50
  • Control PC: 10.250.0.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​

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 10.250.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: Connect with Micro-USB and access http://192.168.55.1 to reach the camera UI regardless of Ethernet configuration, then change the IP to a unique address.

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: 10.250.0.101
  • Camera 2: 10.250.0.102
  • Camera 3: 10.250.0.103
  • Control PC: 10.250.0.10
  • PLC Gateway: 10.250.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​

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

🔗 See Also​