AI-POWERED DOCS
What do you want to know?
System Settings Architecture
This page explains the hierarchical structure and organization of all system configuration elements in the OV20i, showing how different setting levels work together to create a cohesive vision system.
Configuration Architecture Overview
Three-Tier Configuration Hierarchy
The OV20i organizes settings into three distinct architectural layers:
Configuration Levels:
- Device-Level Settings - Hardware and system foundation
- Recipe-Level Settings - Inspection-specific configurations
- Global System Settings - Cross-recipe shared resources and policies
Configuration Scope and Inheritance
Setting Relationships:
- Device settings form the foundation for all operations
- Recipe settings inherit device capabilities but define specific behaviors
- Global settings apply system-wide policies that affect all recipes
- Active recipe determines current operational configuration
Device-Level Settings Foundation
Hardware Configuration Layer
Physical System Configuration:
- Network Identity - IP addressing, subnet configuration, protocol assignment
- Digital I/O Assignment - NPN/PNP logic, trigger inputs, status outputs
- Power Management - 19-24 VDC input configuration, thermal protection
- Port Configuration - M12 Ethernet, Micro-USB emergency access, serial communication
System Identity and Security
Device-Wide Authentication:
- User Management - Engineer/Supervisor/Operator permission levels
- Access Control - Authentication requirements and session management
- Device Identity - Serial numbers, software versioning, activation status
- Emergency Access - Micro-USB recovery procedures and bypass methods
note
Firmware and Software Architecture
System Software Layer:
- Core System Services - Camera control, AI processing, network communication
- Node-RED Platform - Recipe-specific automation workflows (Node-RED lives in each recipe)
- Update Management - Software version control and upgrade procedures
- System Monitoring - Health checks, diagnostic reporting, error handling
Version Management:
- Recipe Compatibility - Older recipes can be opened on newer software versions
- Version Upgrade - Saving recipes updates them to current software version automatically
- Downgrade Limitations - Software downgrades require support assistance and erase all camera data
note
See: Node-RED Basics
Recipe-Level Configuration
Inspection Configuration Hierarchy
Recipe-Specific Settings:
- Imaging Parameters - Exposure, focus, lens settings, lighting configuration
- Template and Alignment - Pattern matching setup, confidence thresholds, search areas
- AI Model Selection - Classification vs Segmentation, training modes, accuracy settings
- Triggering Configuration - Manual, Hardware, PLC, Aligner, or Interval trigger modes
Recipe State Management
Active vs Inactive Configuration:
- Single Active Recipe - Only one recipe operational at any time
- Recipe Switching - Activation/deactivation procedures and system state changes
- Configuration Validation - Settings compatibility checks and error detection
- Recipe Dependencies - Template images, training data, and model requirements
- Node-RED Integration - Each recipe contains its own Node-RED automation workflows
Inspection Workflow Architecture
Recipe Execution Pipeline:
- Trigger Processing - Input signal handling and capture initiation
- Image Acquisition - Camera control and image capture procedures
- AI Processing - Model execution and result generation
- Output Communication - Digital I/O, PLC, and HMI result delivery
Global System Settings
Cross-Recipe Shared Resources
System-Wide Data Management:
- Library Storage - Image capture history with automatic cleanup when memory full
- Storage Management - SD card allocation, retention policies, oldest-first deletion
- Training Data Protection - Training images preserved regardless of storage constraints
- Data Export/Import - Recipe backup, restoration, and transfer capabilities
- System Logs - Diagnostic data, error tracking, and performance monitoring
- Small File Storage - Camera can store small reference files (CSV, etc.) for Node-RED access
Storage Hierarchy:
- Training Data - Highest priority, never automatically deleted
- Recent Captures - Newest images preserved first
- Oldest Captures - Automatically deleted when storage nearly full
- Reference Files - Small files for Node-RED workflows (must remain small)
note
Communication and Integration
External System Connectivity:
- Network Protocols - Ethernet/IP, Profinet, TCP communication configuration
- Industrial Integration - PLC communication parameters and data exchange formats
- Node-RED Workflows - Recipe-specific automation logic and third-party system integration
- Remote Monitoring - Web interface access and diagnostic capabilities
- File Access - Small reference files (CSV, etc.) accessible to Node-RED workflows
System-Wide Policies
Operational Governance:
- Default Behaviors - Fallback settings and error handling procedures
- Performance Optimization - System resource allocation and processing priorities
- Maintenance Schedules - Automated cleanup, health checks, and system validation
- Data Retention - Archive policies, storage limits, and data lifecycle management
Configuration Management
Settings Persistence and Recovery
Configuration Backup Architecture:
- Recipe Export/Import - Individual recipe backup and restoration
- System Configuration - Device-level settings preservation
- Factory Reset - Complete system restoration to default state
- Emergency Recovery - USB-based configuration access and repair
Version Compatibility:
- Software Updates - Settings migration during system upgrades
- Recipe Version Handling - Older recipes open on newer software, saving updates version
- Downgrade Restrictions - Software downgrades require support assistance and erase all data
- Backward Compatibility - Legacy configuration support with automatic version conversion
Change Management and Validation
Configuration Control:
- Change Tracking - Modification history and audit trails
- Settings Validation - Conflict detection and compatibility checking
- Rollback Procedures - Recovery from failed configuration changes
- Testing Workflows - Configuration validation and performance verification
System State Consistency
Architectural Integrity:
- Configuration Dependencies - Cross-layer setting relationships and validation
- Resource Allocation - System resource management across configuration levels
- Performance Impact - Setting changes and system performance implications
- Operational Continuity - Configuration changes without production disruption
Configuration Priority Matrix
| Setting Category | Device Level | Recipe Level | Global Level | Active Recipe Override |
|---|---|---|---|---|
| Network Identity | ✅ Primary | ❌ N/A | ❌ N/A | ❌ N/A |
| User Permissions | ✅ Primary | ❌ N/A | ❌ N/A | ❌ N/A |
| Imaging Parameters | Hardware Limits | ✅ Primary | ❌ N/A | ✅ Active Recipe |
| AI Model Selection | ❌ N/A | ✅ Primary | ❌ N/A | ✅ Active Recipe |
| Trigger Configuration | Hardware Capability | ✅ Primary | ❌ N/A | ✅ Active Recipe |
| Data Storage | Hardware Capacity | Usage | ✅ Primary | ❌ N/A |
| Communication Protocols | Interface Config | Recipe Data | ✅ Primary | Recipe Data |