Operation

Normal Operation

Startup Sequence

Gateway boot process typically takes 60-90 seconds:

1. Power On (0-5 seconds)

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

2. Cellular Connection (5-60 seconds)

   • SIM card detection
   • Network search and registration
   • Carrier authentication
   • Data connection establishment

3. Cloud Registration (30-90 seconds)

   • HTTPS connection to Haltian cloud
   • Certificate-based authentication
   • Gateway registration/check-in
   • Synchronize configuration

4. Wirepas Mesh Start (60-90 seconds)

   • BLE radio initialization
   • Network scanning
   • Sink role activation
   • Ready for sensor connections

5. Operational (90+ seconds)

   • All systems operational
   • LEDs show stable status
   • Ready to route sensor data

Operational Status

LED Indicators:

Cellular Connection

Network Selection

Gateway automatically selects best available network:

1. LTE Cat M1 (Preferred)

   • Best performance and battery efficiency
   • Lower latency
   • Purpose-built for IoT

2. 2G GSM (Fallback)

   • Worldwide coverage
   • Reliable but slower
   • Automatic fallback if LTE unavailable

Signal Quality Monitoring

Access via Haltian IoT Studio:

Navigate to Gateway → Diagnostics → Cellular Metrics

Key Metrics:

Improving Signal Quality:

• Reposition Gateway: Move to higher elevation or near windows
• Check Coverage: Verify carrier coverage in your area
• Antenna Position: Ensure nothing blocking gateway (metal shelves, etc.)
• Contact Support: If persistent poor signal despite good coverage

Network Information

Monitor current network connection:

• Operator: Current cellular carrier name
• MCC/MNC: Mobile Country Code / Mobile Network Code
• Network Type: LTE Cat M1, 2G GSM
• IP Address: Assigned by cellular carrier
• Data Usage: Cumulative data transmitted

Data Usage

Typical Usage Patterns:

Sensor Deployment

Network Formation

Automatic Process:

1. Gateway Active: Wirepas mesh network advertised
2. Sensor Discovery: Sensors scan for nearby networks
3. Authentication: Sensors join configured network
4. Route Establishment: Multi-hop paths created automatically
5. Data Flow: Sensor data routes to gateway

Typical Timeline:

• First sensor: 1-5 minutes to connect
• Additional sensors: 5-15 minutes each
• Full network stabilization: 30-60 minutes for large deployments

Sensor Placement

Guidelines:

1. Start Near Gateway

   • Deploy first sensors within 5-10m
   • Establishes direct connections
   • Creates foundation for mesh expansion

2. Expand Coverage

   • Add sensors progressively
   • Each sensor can relay for others (mesh)
   • Typical range: 5-25m indoor, up to 100m line-of-sight

3. Multi-Hop Support

   • Sensors relay through each other
   • Maximum recommended: 8-12 hops
   • More hops = higher latency

4. Redundancy

   • Multiple paths improve reliability
   • Deploy sensors with overlapping coverage
   • Gateway supports 200-500 sensors (message rate dependent)

Optimal Topology:

     Sensor --- Sensor --- Sensor
        |          |          |
     Sensor --- Gateway --- Sensor
        |                     |
     Sensor --- Sensor --- Sensor

Verifying Sensor Connectivity

Via Haltian IoT Studio:

1. Navigate to Gateway device
2. View “Connected Sensors” list
3. Check each sensor:
   • Status: Online
   • Last Message: Recent timestamp
   • Hop Count: Number of hops to gateway
   • Signal Quality: Link quality percentage

Troubleshooting Poor Connectivity:

• High Hop Count (>10): Add intermediate sensors
• Low Signal Quality (<50%): Reposition sensor closer
• Intermittent Connection: Check for obstacles or interference

Network Monitoring

Gateway Health

Monitor via Haltian IoT Studio:

System Metrics:

• Uptime: Time since last reboot
• CPU Usage: Should be <50% typically
• Memory Usage: Should be <70% typically
• Temperature: Operating temperature (internal)

Network Metrics:

• Message Rate: Messages received per minute
• Message Queue: Buffered messages waiting for transmission
• Delivery Rate: Percentage of messages successfully delivered
• Cloud Latency: Round-trip time to cloud

Cellular Metrics:

• Signal Strength: RSSI, RSRP, RSRQ, SINR
• Data Usage: Current billing period usage
• Network Type: LTE/2G
• Operator: Current carrier

Mesh Network Performance

Key Performance Indicators:

Accessing Performance Data:

1. Navigate to Gateway in Studio
2. Select “Network Performance” tab
3. Review metrics over time (24h, 7d, 30d views)
4. Identify trends and anomalies

Firmware Updates

Automatic Updates

Default Behavior:

• Gateway checks for updates every 24 hours
• Updates download automatically when available
• Installation scheduled during low-traffic period (typically 02:00-04:00 local time)
• Gateway reboots automatically after update

Update Process:

1. Notification: Update available notification in Studio
2. Download: Firmware downloaded in background (no service interruption)
3. Scheduled Install: Update applied during maintenance window
4. Reboot: Gateway restarts (3-5 minutes downtime)
5. Verification: Gateway boots with new firmware
6. Confirmation: Update status reported to cloud

Update Duration:

• Download: 5-15 minutes (depending on cellular speed)
• Installation: 2-3 minutes
• Boot and verification: 1-2 minutes
• Total downtime: 3-5 minutes

Manual Updates

Via Haltian IoT Studio:

1. Navigate to Gateway → Settings → Firmware
2. Check current version and available updates
3. Select “Update Now” to install immediately
4. Confirm update
5. Monitor update progress
6. Verify completion and new version

Best Practices:

• Schedule during low-activity periods
• Verify cellular signal stable before update
• Monitor completion in Studio
• Verify sensors reconnect after update (15-30 minutes)

Rollback

If update fails or causes issues:

• Gateway automatically reverts to previous firmware
• Service restored within 5 minutes
• Error logged and reported to Haltian
• Retry scheduled automatically

Data Flow Management

Message Routing

Uplink (Sensors → Cloud):

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

Message Priority:

1. Critical: Alarms, alerts (highest priority)
2. Configuration: Sensor configuration responses
3. Normal: Regular measurements
4. Diagnostic: Debug and diagnostic data

Buffer Management

Queue Characteristics:

• Capacity: 1000 messages
• Overflow Handling: Drop oldest non-critical messages
• Retry Policy: 3 attempts for failed transmissions
• TTL: 24 hours (messages expire if not delivered)

Monitoring Queue:

• Check “Message Queue Depth” in Studio
• Normal: 0-50 messages
• Warning: 50-200 messages (cellular slow or intermittent)
• Critical: >500 messages (cellular connection issue)

Bandwidth Optimization

For High Sensor Counts:

• Configure longer sensor report intervals
• Use CBOR encoding (automatic, more efficient than JSON)
• Enable message compression (zlib)
• Batch messages when possible

Maintenance

Routine Checks

Daily:

• Verify gateway online in Studio
• Check message delivery rate >98%
• Monitor cellular signal quality

Weekly:

• Review sensor connectivity (all sensors reporting)
• Check data usage trends
• Verify firmware version current

Monthly:

• Clean gateway exterior (dust)
• Inspect USB cable and connections
• Review network performance trends
• Verify physical mounting secure

Quarterly:

• Deep performance analysis
• Review sensor network topology
• Optimize sensor placement if needed
• Update documentation (network diagrams)

Preventive Maintenance

Power Supply:

• Inspect USB cable for wear or damage
• Verify power adapter working properly
• Test with different outlet if issues
• Keep spare USB cable and adapter

Physical Condition:

• Check enclosure for damage
• Ensure ventilation not blocked
• Verify mounting stable and secure
• Clean dust from surfaces

Environmental:

• Verify temperature within range (0-40°C)
• Check humidity acceptable (8-90% RH)
• Ensure no condensation
• Keep away from heat sources

Performance Optimization

Cellular Optimization

Improving Connection:

1. Position: Higher elevation improves signal
2. Orientation: Rotate gateway to find best signal angle
3. Location: Move near windows or exterior walls
4. Interference: Move away from metal shelves, thick walls

Mesh Network Optimization

For Best Performance:

1. Sensor Density: Deploy enough sensors for redundant paths
2. Reduce Hops: Position sensors to minimize hop count
3. Avoid Obstacles: Minimize concrete walls, metal barriers
4. Channel Selection: Default channel typically optimal

Capacity Planning

Sensors per Gateway:

Message Rate Capacity:

• Maximum: 10,000 messages/hour
• Recommended: <5,000 messages/hour
• Peak Handling: 15,000 messages/hour short duration

Troubleshooting Quick Reference

Gateway Offline

1. Check power LED (power connected?)
2. Check cellular LED (network connected?)
3. Verify SIM card installed correctly
4. Check cellular coverage in area
5. See Troubleshooting for details

Poor Sensor Connectivity

1. Check sensor proximity to gateway
2. Verify Wirepas mesh network active
3. Add intermediate sensors for range extension
4. Check for RF interference
5. Review Troubleshooting

High Data Usage

1. Review sensor message rates
2. Check for abnormal sensor behavior
3. Verify message batching enabled
4. Reduce sensor report frequencies if needed
5. Contact Haltian support if unexpected

Next Steps

• Specifications - Review technical specifications
• Troubleshooting - Resolve common issues
• Installation - Review installation procedures