Configuration
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:
- Connect Ethernet cable to network
- Gateway requests IP via DHCP
- Verifies connectivity to Haltian cloud
- Registers with assigned IP address
Static IP Configuration:
For networks without DHCP or requiring fixed addresses:
Access Configuration Interface
- Connect via serial console or temporary DHCP connection
- Navigate to Network Settings
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.4Apply and Verify
- Save configuration
- Gateway reboots with new settings
- Verify cloud connectivity
Network Requirements:
| Parameter | Requirement | Notes |
|---|---|---|
| IP Assignment | DHCP or Static | DHCP recommended |
| Outbound Ports | 443 (HTTPS), 123 (NTP) | Cloud communication |
| DNS Resolution | Required | For cloud endpoint lookup |
| Firewall | Allow outbound HTTPS | No inbound ports needed |
| Bandwidth | 1 Mbps minimum | Per 100 sensors |
WiFi Configuration
Configure WiFi Credentials:
Access WiFi Settings
- Via Haltian IoT Studio (for registered gateways)
- Via local configuration interface
Enter Network Details
SSID: YourNetworkName Security: WPA2-PSK / WPA3-PSK Passphrase: YourSecurePasswordOptional Advanced Settings
- Static IP (if not using DHCP)
- Hidden SSID support
- Channel preference
WiFi Specifications:
| Feature | Specification |
|---|---|
| Standards | 802.11 a/b/g/n/ac |
| Frequency | 2.4 GHz, 5 GHz |
| Security | WPA2-PSK, WPA3-PSK |
| Range | Typical 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:
- Insert SIM card
- Power on gateway
- Gateway detects carrier and configures APN
- Connection established automatically
Manual APN Configuration:
For carriers requiring manual APN setup:
Access LTE Settings
- Via Haltian IoT Studio or console
Configure APN Parameters
APN: carrier.apn.endpoint Username: (if required) Password: (if required) Authentication: PAP / CHAP / NoneVerify Connection
- Check signal strength (RSSI, RSRP, RSRQ)
- Verify data connection active
- Monitor connection stability
LTE Network Selection:
Configure network preference:
| Priority | Network Type | Use Case |
|---|---|---|
| 1 | LTE Cat 4 | Best performance |
| 2 | 3G/UMTS | Moderate performance |
| 3 | 2G/GSM | Fallback 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:
| Parameter | Default | Range | Description |
|---|---|---|---|
| Network Channel | 37 | 0-39 | Wirepas mesh channel |
| Network Address | Auto | 1-16777215 | Unique network identifier |
| Scan Interval | 5 sec | 1-60 sec | Sensor discovery interval |
| Max Hops | 15 | 1-30 | Maximum 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:
| Parameter | Default | Description |
|---|---|---|
| Sink Role | Enabled | Gateway receives sensor data |
| Sink Cost | 0 | Lower cost = preferred routing |
| Priority | High | Data routing priority |
Multi-Gateway Deployments:
For networks with multiple gateways:
Configure Gateway Priority
- Assign different sink costs
- Lower cost = preferred gateway
- Enables load balancing
Monitor Load Distribution
- Check sensor routing
- Verify balanced traffic
- Adjust costs if needed
Data Routing
Uplink Configuration:
Sensor data flows from sensors → gateway → cloud:
| Parameter | Setting | Notes |
|---|---|---|
| Uplink Endpoint | 238 (TLV), 247 (CBOR) | Profile-dependent |
| Queue Size | 1000 messages | Per-gateway buffer |
| Retry Policy | 3 attempts | Failed message retries |
| TTL | 24 hours | Message expiration |
Downlink Configuration:
Cloud commands flow cloud → gateway → sensors:
| Parameter | Setting | Notes |
|---|---|---|
| Downlink Endpoint | 238 (TLV), 247 (CBOR) | Profile-dependent |
| Priority | High | Configuration commands |
| Timeout | 30 seconds | Response 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:
| LED | Default Function | Customizable |
|---|---|---|
| Power | Power status | No |
| Network | Network activity | Yes |
| Mesh | Wirepas mesh status | Yes |
| Status | General status | Yes |
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:
| Setting | Options | Recommendation |
|---|---|---|
| Auto-Update | Enabled / Disabled | Enabled |
| Update Window | Off-hours preferred | 02:00-04:00 local |
| Reboot Required | Automatic / Manual | Automatic |
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:
- Access Haltian IoT Studio
- Navigate to gateway settings
- Export configuration as JSON
- Store securely
Configuration Includes:
- Network settings (Ethernet/WiFi/LTE)
- Wirepas mesh parameters
- System settings
- Custom configurations
Restore Configuration
Apply backed-up configuration:
- Access gateway in Haltian IoT Studio
- Select “Import Configuration”
- Upload JSON file
- Review changes
- Apply configuration
- 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)
Expansion header requires hardware modification. Contact Haltian support before use.
CAN Interface (LTE Version)
Configure CAN bus interface:
| Parameter | Range | Default |
|---|---|---|
| Baud Rate | 10 Kbps - 1 Mbps | 250 Kbps |
| Mode | Normal / Listen-only | Normal |
| Termination | Enabled / Disabled | Disabled |
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:
Verify Network Connectivity
- Check cloud connection status
- Ping cloud endpoints
- Monitor heartbeat messages
Verify Wirepas Mesh
- Check sensor connectivity
- Monitor message routing
- Verify data flow
Monitor Logs
- Review system logs for errors
- Check configuration application status
- Verify all services started
Troubleshooting Configuration
For configuration issues, see Troubleshooting.
Next Steps
- Operation Guide - Learn about day-to-day gateway operation
- Monitoring - Monitor gateway and mesh network
- Firmware Updates - Keep gateway firmware current