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

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

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

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

Maintenance

Routine Maintenance

The following checks are recommended to be performed regularly:

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

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

Performance Optimization

Network Optimization

Single Gateway:

• Position centrally relative to sensors
• Minimize obstacles (concrete walls, metal)

Multiple Gateways:

• Overlap coverage 20-30%

Backhaul Optimization

Ethernet:

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

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