Operation

Normal Operation

Startup Sequence

Gateway boot process typically takes 30-60 seconds:

1. Power On (0-5 seconds)

   • Power LED illuminates
   • Hardware initialization
   • Self-test procedures

2. Network Initialization (5-15 seconds)

   • Network interfaces activate
   • DHCP request (if configured)
   • NTP synchronization

3. Cloud Connection (15-30 seconds)

   • TLS connection establishment
   • Authentication and registration
   • Certificate validation

4. Wirepas Mesh Start (30-45 seconds)

   • BLE radio initialization
   • Network scanning
   • Sink role activation

5. Operational (45-60 seconds)

   • Ready to route sensor data
   • LED indicates normal status
   • All services running

Operational States

Network Management

Wirepas Mesh Network

Network Formation:

1. Gateway advertises as network sink
2. Sensors discover gateway
3. Mesh routes established automatically
4. Multi-hop paths created as needed

Network Topology:

    Sensor ─── Sensor ─── Sensor
       │          │          │
    Sensor ────Gateway──── Sensor
       │                     │
    Sensor ─── Sensor ─── Sensor

Optimal Gateway Placement:

• Single Gateway: Central location, up to 100-200 sensors
• Multiple Gateways: Overlap coverage by 20-30%
• Range Considerations: 5-25m typical indoor, up to 100m line-of-sight
• Obstacles: Minimize concrete walls, metal barriers between gateway and sensors

Network Monitoring

Monitor via Haltian IoT Studio:

1. Active Sensors

   • Total sensor count
   • Sensors per gateway
   • Last message timestamps

2. Network Health

   • Message delivery rate
   • Average latency
   • Hop count distribution
   • Failed message count

3. Routing Performance

   • Route changes per hour
   • Network stability metrics
   • Congestion indicators

Key Metrics:

Multi-Gateway Coordination

For deployments with multiple gateways:

Gateway Placement:

• Overlap coverage areas by 20-30%
• Coordinate channel selection (avoid same channel in overlap)
• Configure different sink costs for load balancing

Load Balancing:

Gateway 1: Sink Cost 0 (preferred for Zone A)
Gateway 2: Sink Cost 5 (preferred for Zone B)
Gateway 3: Sink Cost 10 (backup for both zones)

Monitor Distribution:

• Check sensor-to-gateway assignments
• Verify even load distribution
• Adjust sink costs if imbalanced

Data Flow Management

Uplink Data (Sensors → Cloud)

Normal Data Flow:

1. Sensor generates measurement
2. Message routed through mesh to gateway
3. Gateway buffers message in queue
4. Gateway transmits to cloud via backhaul
5. Cloud acknowledges receipt

Buffer Management:

• Queue size: 1000 messages
• Overflow handling: Drop oldest non-critical messages
• Priority: Configuration commands > Alarms > Measurements

Retry Policy:

Downlink Data (Cloud → Sensors)

Configuration Commands:

1. Cloud sends command to gateway
2. Gateway forwards to target sensor via mesh
3. Sensor applies configuration
4. Sensor sends acknowledgment back through mesh
5. Gateway confirms to cloud

Typical Latency:

• Configuration command: 2-10 seconds end-to-end
• Measurement request: 1-5 seconds response time

Firmware Updates

Update Process

Automatic Updates (Recommended):

1. Notification

   • Gateway checks for updates every 6 hours
   • New firmware detected
   • Update scheduled for maintenance window

2. Download

   • Firmware downloaded during operation
   • No service interruption
   • Download verified (checksum)

3. Installation

   • Scheduled during configured maintenance window
   • Gateway stops accepting new connections
   • Existing messages flushed to cloud
   • Firmware applied (2-3 minutes)
   • Gateway reboots automatically

4. Verification

   • New firmware boots
   • Self-test procedures
   • Cloud reconnection
   • Update confirmed

Manual Updates:

1. Access Haltian IoT Studio
2. Navigate to gateway settings
3. Select “Firmware Update”
4. Choose firmware version
5. Confirm update
6. Monitor update progress
7. Verify completion

Update Duration:

• Download: 2-10 minutes (depending on connection)
• Installation: 2-3 minutes
• Boot and verify: 1-2 minutes
• Total downtime: 3-5 minutes

Rollback:

If update fails:

• Gateway automatically reverts to previous firmware
• Service restored within 5 minutes
• Error logged and reported
• Retry scheduled (if automatic updates enabled)

Update Best Practices

• Schedule during low-traffic periods (typically 02:00-04:00 local time)
• Verify network connectivity before initiating update
• Coordinate with sensor updates if firmware dependencies exist
• Test on single gateway before deploying to all gateways
• Monitor update completion via Studio

Network Diagnostics

Connection Diagnostics

Test Cloud Connectivity:

# Via Haltian IoT Studio:
Gateway Settings → Diagnostics → Test Connection

# Expected result:
- DNS resolution: Success
- HTTPS connection: Success
- Authentication: Success
- Heartbeat: Active

Test Wirepas Mesh:

# Via Haltian IoT Studio:
Gateway Settings → Diagnostics → Mesh Status

# Expected result:
- BLE radio: Active
- Network channel: 15
- Active sensors: 42
- Message rate: 12 msg/min

Performance Monitoring

Real-Time Metrics:

Access via Haltian IoT Studio → Gateway Dashboard:

1. System Health

   • CPU usage: <50% typical
   • Memory usage: <60% typical
   • Storage usage: <80% warning threshold
   • Temperature: 0-50°C operating range

2. Network Performance

   • Uptime: 99.9% target
   • Message throughput: Varies by sensor count
   • Cloud latency: <200ms typical
   • Mesh latency: <2 seconds typical

3. Connectivity Status

   • Backhaul type: Ethernet/WiFi/LTE
   • Signal quality: RSSI/RSRP for wireless
   • IP address: Current assigned IP
   • Last heartbeat: Timestamp

Historical Data:

View trends over time:

• 24-hour view: Minute-by-minute resolution
• 7-day view: Hourly resolution
• 30-day view: Daily resolution

Maintenance

Routine Maintenance

Weekly:

• Review gateway status in Studio
• Check message delivery rate
• Verify sensor connectivity
• Monitor storage usage

Monthly:

• Review firmware update status
• Analyze network performance trends
• Check physical installation (mounting, cables)
• Clean dust from ventilation areas

Quarterly:

• Verify network security (certificates current)
• Review and optimize network configuration
• Test failover mechanisms (if applicable)
• Update documentation (network diagrams, configs)

Annually:

• Replace backup battery (RTC)
• Inspect DC power supply
• Review and update access credentials
• Conduct full system audit

Preventive Maintenance

Power Supply:

• Inspect DC connector for wear
• Verify voltage within 9-36V range
• Check power supply for overheating
• Test PoE injector/switch (if used)

Network Cables:

• Inspect Ethernet cable for damage
• Verify secure RJ45 connection
• Test cable continuity if issues arise
• Replace Cat5e with Cat6 for gigabit speeds

Environmental:

• Verify operating temperature 0-50°C
• Check ventilation (10cm clearance maintained)
• Remove dust from enclosure
• Ensure dry environment (no condensation)

LTE Antenna (LTE version):

• Check antenna connection (hand-tight)
• Verify antenna positioning (vertical optimal)
• Inspect antenna cable for damage
• Monitor signal quality trends

Backup and Recovery

Configuration Backup

Automatic Backups:

• Cloud-stored configuration: Updated on every change
• Retention: Indefinite
• Restore: Via Haltian IoT Studio

Manual Backup:

1. Access gateway in Studio
2. Export configuration (JSON format)
3. Store securely offline
4. Document firmware version with backup

Disaster Recovery

Gateway Replacement:

1. Prepare Replacement Gateway

   • Unbox new gateway
   • Power on and register to account

2. Restore Configuration

   • Access Haltian IoT Studio
   • Import backed-up configuration
   • Verify settings

3. Install Replacement

   • Install in same physical location
   • Connect to same network
   • Verify cloud connectivity

4. Verify Operation

   • Sensors reconnect automatically (15-30 minutes)
   • Monitor message flow
   • Confirm normal operation

Expected Recovery Time:

• Physical installation: 15 minutes
• Configuration restore: 5 minutes
• Sensor reconnection: 15-30 minutes
• Total recovery: 35-50 minutes

Performance Optimization

Network Optimization

Single Gateway:

• Position centrally relative to sensors
• Minimize obstacles (concrete walls, metal)
• Use higher sink priority for critical gateways

Multiple Gateways:

• Overlap coverage 20-30%
• Stagger update schedules
• Balance sensor loads with sink costs

Channel Selection:

• Scan for interference
• Avoid WiFi channels if co-located
• Use Wirepas channels 10-20 for typical deployments

Backhaul Optimization

Ethernet:

• Use gigabit switches for best performance
• Minimize switch hops to gateway
• Enable QoS for IoT traffic if needed

WiFi:

• Use 5 GHz band if available
• Position gateway near access point
• Avoid congested WiFi channels

LTE:

• Position antenna for best RSRP (>-90 dBm)
• Use external antenna for improved signal
• Monitor data usage to avoid carrier throttling

Capacity Planning

Scaling Guidelines

Sensor Capacity per Gateway:

Message Rate Capacity:

• Maximum: 10,000 messages/hour per gateway
• Recommended: <5,000 messages/hour for headroom
• Burst capacity: 20,000 messages/hour (short duration)

Bandwidth Requirements:

Next Steps

• Troubleshooting - Common issues and solutions
• Specifications - Complete technical specifications
• Configuration - Network and system configuration details