Configuration

Network configuration, Wirepas mesh settings, and system parameters for Haltian IoT Gateway N8

Overview

The Gateway N8 can be configured for various network topologies and operational parameters. Configuration is performed through the Haltian IoT Studio web interface or via local access methods.

Network Configuration

Ethernet Configuration

DHCP Mode (Default):

The gateway obtains IP address automatically from DHCP server:

  1. Connect Ethernet cable to network
  2. Gateway requests IP via DHCP
  3. Verifies connectivity to Haltian cloud
  4. Registers with assigned IP address

Static IP Configuration:

For networks without DHCP or requiring fixed addresses:

  1. Access Configuration Interface

    • Connect via serial console or temporary DHCP connection
    • Navigate to Network Settings
  2. Configure Static Parameters

    IP Address: 192.168.1.100
    Subnet Mask: 255.255.255.0
    Gateway: 192.168.1.1
    DNS Primary: 8.8.8.8
    DNS Secondary: 8.8.4.4
    
  3. Apply and Verify

    • Save configuration
    • Gateway reboots with new settings
    • Verify cloud connectivity

Network Requirements:

ParameterRequirementNotes
IP AssignmentDHCP or StaticDHCP recommended
Outbound Ports443 (HTTPS), 123 (NTP)Cloud communication
DNS ResolutionRequiredFor cloud endpoint lookup
FirewallAllow outbound HTTPSNo inbound ports needed
Bandwidth1 Mbps minimumPer 100 sensors

WiFi Configuration

Configure WiFi Credentials:

  1. Access WiFi Settings

    • Via Haltian IoT Studio (for registered gateways)
    • Via local configuration interface
  2. Enter Network Details

    SSID: YourNetworkName
    Security: WPA2-PSK / WPA3-PSK
    Passphrase: YourSecurePassword
    
  3. Optional Advanced Settings

    • Static IP (if not using DHCP)
    • Hidden SSID support
    • Channel preference

WiFi Specifications:

FeatureSpecification
Standards802.11 a/b/g/n/ac
Frequency2.4 GHz, 5 GHz
SecurityWPA2-PSK, WPA3-PSK
RangeTypical 30-50m indoor

WiFi Priority:

Configure failover behavior:

  • Primary: WiFi
  • Fallback: Ethernet
  • Or reverse priority based on deployment needs

LTE Configuration (LTE Version)

Automatic Configuration:

Most carriers support automatic APN configuration:

  1. Insert SIM card
  2. Power on gateway
  3. Gateway detects carrier and configures APN
  4. Connection established automatically

Manual APN Configuration:

For carriers requiring manual APN setup:

  1. Access LTE Settings

    • Via Haltian IoT Studio or console
  2. Configure APN Parameters

    APN: carrier.apn.endpoint
    Username: (if required)
    Password: (if required)
    Authentication: PAP / CHAP / None
    
  3. Verify Connection

    • Check signal strength (RSSI, RSRP, RSRQ)
    • Verify data connection active
    • Monitor connection stability

LTE Network Selection:

Configure network preference:

PriorityNetwork TypeUse Case
1LTE Cat 4Best performance
23G/UMTSModerate performance
32G/GSMFallback only

Signal Quality Monitoring:

Monitor these metrics for optimal placement:

  • RSSI: Received Signal Strength Indicator (-70 dBm or better recommended)
  • RSRP: Reference Signal Received Power (-90 dBm or better recommended)
  • RSRQ: Reference Signal Received Quality (-10 dB or better recommended)
  • SINR: Signal-to-Interference-plus-Noise Ratio (10 dB or better recommended)

Wirepas Mesh Configuration

Network Parameters

Basic Mesh Settings:

ParameterDefaultRangeDescription
Network Channel370-39Wirepas mesh channel
Network AddressAuto1-16777215Unique network identifier
Scan Interval5 sec1-60 secSensor discovery interval
Max Hops151-30Maximum mesh routing hops

Channel Selection:

Choose appropriate Wirepas channel to avoid interference:

  • Channels 0-36: Shared with standard BLE advertising
  • Channels 37-39: BLE advertising channels (typically avoid)
  • Recommendation: Use channels 10-20 for typical deployments

Network Address:

Each Wirepas network requires unique network address:

  • Automatically assigned by Haltian cloud
  • Can be manually configured for isolated networks
  • Must be unique across all networks in same physical area

Sink Role Configuration

Gateway acts as network “sink” - endpoint for sensor data:

ParameterDefaultDescription
Sink RoleEnabledGateway receives sensor data
Sink Cost0Lower cost = preferred routing
PriorityHighData routing priority

Multi-Gateway Deployments:

For networks with multiple gateways:

  1. Configure Gateway Priority

    • Assign different sink costs
    • Lower cost = preferred gateway
    • Enables load balancing
  2. Monitor Load Distribution

    • Check sensor routing
    • Verify balanced traffic
    • Adjust costs if needed

Data Routing

Uplink Configuration:

Sensor data flows from sensors → gateway → cloud:

ParameterSettingNotes
Uplink Endpoint238 (TLV), 247 (CBOR)Profile-dependent
Queue Size1000 messagesPer-gateway buffer
Retry Policy3 attemptsFailed message retries
TTL24 hoursMessage expiration

Downlink Configuration:

Cloud commands flow cloud → gateway → sensors:

ParameterSettingNotes
Downlink Endpoint238 (TLV), 247 (CBOR)Profile-dependent
PriorityHighConfiguration commands
Timeout30 secondsResponse timeout

System Configuration

Time Synchronization

Gateway synchronizes time with NTP servers:

Default NTP Servers:

  • Primary: pool.ntp.org
  • Secondary: time.google.com

Custom NTP Configuration:

NTP Server: your-ntp-server.local
Update Interval: 3600 seconds (1 hour)
Timezone: UTC (or local timezone)

LED Configuration

Programmable LEDs can indicate different states:

LEDDefault FunctionCustomizable
PowerPower statusNo
NetworkNetwork activityYes
MeshWirepas mesh statusYes
StatusGeneral statusYes

Custom LED Patterns:

Configure LED behavior for specific events:

  • Sensor count thresholds
  • Network connectivity issues
  • Firmware update status
  • Custom application events

Logging Configuration

Configure log levels and destinations:

Log Levels:

  • DEBUG: Detailed debugging information
  • INFO: Normal operational messages
  • WARNING: Warning conditions
  • ERROR: Error conditions
  • CRITICAL: Critical failures

Log Destinations:

  • Local storage (8GB eMMC, limited retention)
  • Cloud logging (recommended)
  • Remote syslog server

Log Retention:

Local: 7 days (space permitting)
Cloud: 30 days
Syslog: Per server configuration

Firmware Configuration

Auto-Update Settings

Control automatic firmware updates:

SettingOptionsRecommendation
Auto-UpdateEnabled / DisabledEnabled
Update WindowOff-hours preferred02:00-04:00 local
Reboot RequiredAutomatic / ManualAutomatic

Update Policy:

Configure update behavior:

  • Automatic: Updates applied during maintenance window
  • Manual: Updates require explicit approval
  • Staged: Test updates on subset of gateways first

Firmware Channels

Select firmware update channel:

  • Stable: Production-ready firmware (recommended)
  • Beta: Pre-release firmware for testing
  • Development: Cutting-edge features (testing only)

Security Configuration

TLS/SSL Settings

All cloud communication uses TLS 1.2 or higher:

  • Certificate-based authentication
  • Mutual TLS (mTLS) support
  • Automatic certificate rotation

Access Control

Configure administrative access:

Local Access:

  • Console port (internal physical access)
  • SSH (disabled by default, enable if needed)

Remote Access:

  • Haltian IoT Studio (recommended)
  • Remote SSH (requires VPN or secure tunnel)

Authentication:

  • Certificate-based (default)
  • Username/password (console only)

Configuration Backup

Export Configuration

Backup gateway configuration:

  1. Access Haltian IoT Studio
  2. Navigate to gateway settings
  3. Export configuration as JSON
  4. Store securely

Configuration Includes:

  • Network settings (Ethernet/WiFi/LTE)
  • Wirepas mesh parameters
  • System settings
  • Custom configurations

Restore Configuration

Apply backed-up configuration:

  1. Access gateway in Haltian IoT Studio
  2. Select “Import Configuration”
  3. Upload JSON file
  4. Review changes
  5. Apply configuration
  6. Gateway reboots with new settings

Advanced Configuration

Expansion Header

Internal expansion header provides:

  • GPIO pins for custom integrations
  • Serial interfaces (UART)
  • I2C bus access
  • Power output (3.3V, 5V)

CAN Interface (LTE Version)

Configure CAN bus interface:

ParameterRangeDefault
Baud Rate10 Kbps - 1 Mbps250 Kbps
ModeNormal / Listen-onlyNormal
TerminationEnabled / DisabledDisabled

CAN Use Cases:

  • Vehicle integration
  • Industrial equipment monitoring
  • Building automation interfaces

Configuration Examples

Example 1: Simple Ethernet Deployment

{
  "network": {
    "ethernet": {
      "mode": "dhcp"
    }
  },
  "wirepas": {
    "channel": 15,
    "networkAddress": "auto"
  },
  "firmware": {
    "autoUpdate": true,
    "channel": "stable"
  }
}

Example 2: WiFi with Static IP

{
  "network": {
    "wifi": {
      "ssid": "IoT-Network",
      "security": "WPA2-PSK",
      "passphrase": "SecurePassword123",
      "ipMode": "static",
      "ipAddress": "192.168.1.100",
      "subnetMask": "255.255.255.0",
      "gateway": "192.168.1.1",
      "dns": ["8.8.8.8", "8.8.4.4"]
    }
  },
  "wirepas": {
    "channel": 18,
    "sinkCost": 0
  }
}

Example 3: LTE with Multi-Gateway

{
  "network": {
    "lte": {
      "apn": "auto",
      "networkPreference": ["LTE", "3G", "2G"]
    }
  },
  "wirepas": {
    "channel": 15,
    "sinkCost": 10,
    "priority": "high"
  }
}

Configuration Validation

After applying configuration:

  1. Verify Network Connectivity

    • Check cloud connection status
    • Ping cloud endpoints
    • Monitor heartbeat messages
  2. Verify Wirepas Mesh

    • Check sensor connectivity
    • Monitor message routing
    • Verify data flow
  3. Monitor Logs

    • Review system logs for errors
    • Check configuration application status
    • Verify all services started

Troubleshooting Configuration

For configuration issues, see Troubleshooting.

Next Steps