Configuration

Configuration Overview

Haltian RADAR sensors are remotely configurable via Haltian Operations Cloud. This allows adjusting key parameters without physical access to the sensor.

Key configurable parameters:

• Sensing distance: 10 cm to 10 meters
• Measurement interval: How often sensor measures
• Reporting interval: How often data transmitted
• Operational mode: Parking, loading dock, or custom

Sensing Distance Configuration

What is Sensing Distance?

Sensing distance defines the threshold for occupancy detection:

• Occupied: Object detected within sensing distance
• Unoccupied: No object within sensing distance

Adjustable range: 10 cm to 10 meters

Default Configurations

Parking Space (default):

• Sensing distance: 2 meters
• Rationale: Covers most passenger vehicles (sedans, SUVs)
• Coverage: Detects vehicles parked in typical parking space depth

Loading Dock (default):

• Sensing distance: 5 meters
• Rationale: Covers typical loading dock depth
• Coverage: Detects trailers backed into loading position

How to Set Sensing Distance

Considerations when choosing distance:

1. Measure your space:

   • Parking space: Measure depth from sensor to back of space
   • Loading dock: Measure from sensor to trailer docking position
   • Add margin for vehicle size variation (±0.5m typical)

2. Avoid over-detection:

   • Don’t set distance beyond intended monitoring zone
   • Example: Parking space 5m deep, but walkway 6m away → set to 5m to avoid detecting pedestrians

3. Account for vehicle types:

   • Compact cars: 1.5-2 meters (shorter vehicles)
   • Standard cars: 2-2.5 meters (most common)
   • SUVs/Trucks: 2.5-3 meters (longer vehicles)
   • Trailers: 5-8 meters (loading docks)

4. Test and adjust:

   • Set initial distance based on measurement
   • Test with actual vehicles/trailers
   • Fine-tune if false positives or missed detections occur

Remote Adjustment Process

To change sensing distance:

1. Contact Haltian support:

   • Email: support@haltian.com
   • Provide sensor ID and desired sensing distance
   • Explain use case (parking, loading dock, other)

2. Haltian configures remotely:

   • Configuration pushed to sensor via Wirepas mesh
   • Update typically applied within 1-24 hours
   • Sensor automatically adopts new sensing distance

3. Verify new configuration:

   • Test with vehicle present and absent
   • Confirm occupancy detection at expected distance
   • Report any issues to Haltian support

Measurement Interval Configuration

What is Measurement Interval?

Measurement interval defines how often the sensor performs a radar measurement:

• 30 seconds: Sensor measures every 30 seconds
• 60 seconds: Sensor measures every 60 seconds
• Custom: Other intervals (e.g., 5 minutes for battery optimization)

Default Settings

Parking Space:

• Interval: 30 seconds
• Why: Vehicles come and go frequently, rapid detection needed

Loading Dock:

• Interval: 60 seconds
• Why: Trailers position slowly, longer interval provides more stable readings, extends battery life

Impact on Battery Life

Shorter intervals = More battery consumption:

• Every measurement activates 60GHz radar → power consumption
• More measurements per day → faster battery drain

Example battery life estimates:

• 30-second interval: ~10 years (parking default)
• 60-second interval: ~10+ years (loading dock default)
• 5-minute interval: 15+ years (custom low-power application)

Recommendation: Use defaults unless specific application requires different interval.

When to Adjust Measurement Interval

Increase interval (e.g., 60s → 5 min):

• Low-traffic areas (rarely used parking)
• Battery life more critical than rapid detection
• Loading docks with infrequent use

Decrease interval (e.g., 60s → 30s):

• High-turnover parking (urban centers, airports)
• Critical applications requiring rapid detection
• (Battery life trade-off)

Contact Haltian support to adjust measurement interval remotely.

Reporting Interval Configuration

What is Reporting Interval?

Reporting interval defines how often the sensor transmits data over Wirepas mesh network:

• On state change: Transmit when occupied → unoccupied or vice versa
• Periodic: Transmit even if state unchanged (e.g., every hour)

Default Reporting Behavior

State change reporting (always enabled):

• Occupied → unoccupied: Report within next transmission cycle
• Unoccupied → occupied: Report within next transmission cycle

Periodic reporting:

• Even if state unchanged, transmit periodically (e.g., hourly)
• Ensures system knows sensor is online
• Provides regular battery level updates

Impact on Battery Life

More transmissions = More battery consumption:

• Radio transmission consumes power
• Frequent transmissions reduce battery life

Typical configuration:

• State change: Immediate (always)
• Periodic: Every 1-24 hours (when state stable)

Recommendation: Default reporting balanced for typical use. Only adjust if specific application requires more frequent updates.

When to Adjust Reporting Interval

Increase periodic reporting frequency:

• Real-time parking guidance systems (need latest data)
• Critical applications (loading dock scheduling)
• (Battery life trade-off)

Decrease periodic reporting frequency:

• Low-traffic areas (data updates less critical)
• Battery optimization priority
• Historical analytics only (no real-time need)

Contact Haltian support to configure reporting intervals.

Operational Mode Presets

Parking Mode (Default for Parking)

Pre-configured settings:

• Sensing distance: 2 meters
• Measurement interval: 30 seconds
• Reporting: State change + hourly periodic

Use cases:

• Parking garages
• Street parking
• Commercial parking lots
• Residential parking

Optimized for:

• Rapid vehicle turnover
• Quick detection
• Typical passenger vehicles

Loading Dock Mode (Default for Loading)

Pre-configured settings:

• Sensing distance: 5 meters
• Measurement interval: 60 seconds
• Reporting: State change + hourly periodic

Use cases:

• Warehouse loading docks
• Freight terminals
• Distribution centers
• Retail receiving areas

Optimized for:

• Trailer/truck detection
• Stable readings (tolerates vibrations)
• Extended battery life

Custom Mode

Fully customizable settings:

• Sensing distance: 10 cm - 10 m (any value)
• Measurement interval: 30s, 60s, 5 min, or custom
• Reporting: Tailored to application

Use cases:

• Specialized applications (equipment monitoring, etc.)
• Unique environmental constraints
• Non-standard parking/loading scenarios

Contact Haltian support for custom configuration assistance.

Activation and Provisioning

Initial Sensor Activation

Before first use:

1. Physical installation:

   • Mount sensor in desired location
   • Verify mounting secure and beam direction correct

2. Network join:

   • Sensor automatically joins Wirepas mesh network
   • Join time: 1-10 minutes (typical)
   • No manual activation required

3. Verify in Haltian IoT Studio:

   • Log into IoT Studio portal
   • Navigate to device list
   • Confirm sensor appears with correct ID
   • Check “Last Seen” timestamp (should be recent)

4. Configuration assignment:

   • Sensor ships with default configuration (parking or loading dock)
   • If custom configuration needed, contact Haltian support
   • Configuration pushed remotely after network join

Sensor ID and Identification

Unique sensor ID:

• Each RADAR has unique device ID (printed on label)
• Use ID to identify sensor in IoT Studio
• Reference ID when contacting support for configuration

Labeling best practice:

• Note sensor ID during installation
• Map ID to physical location (e.g., “Parking Space A12”, “Loading Dock 3”)
• Maintain installation records for future reference

Advanced Configuration Options

Mesh Network Role

Sensor can operate as:

• End device: Only transmits own data (lowest power consumption)
• Router: Relays packets for other sensors (higher power consumption)

Automatic role assignment:

• Wirepas mesh automatically assigns roles
• Sensors closer to gateway more likely to be routers
• Optimal network topology managed automatically

Manual role configuration:

• Typically not needed (auto-assignment optimal)
• Contact Haltian support if specific topology required

Transmission Power

Radio transmission power:

• Default: Optimized for balance of range and battery life
• Adjustable: Can increase for challenging RF environments (reduces battery life)
• Contact Haltian support for transmission power adjustments

When to increase transmission power:

• Poor signal strength (RSSI < -85 dBm)
• Long distance to gateway (> 20m, no intermediate routers)
• RF-challenging environment (metal structures, underground)

Trade-off: Higher power = better connectivity but shorter battery life

Configuration Change Process

Step-by-Step Configuration Update

How to request configuration change:

1. Identify sensor:

   • Note sensor ID (from label or IoT Studio)
   • Confirm physical location
   • Determine current configuration (if known)

2. Determine desired configuration:

   • Sensing distance: Measure and calculate (include margin)
   • Measurement interval: 30s, 60s, or custom
   • Reporting interval: State change + periodic (specify frequency)

3. Contact Haltian support:

   • Email: support@haltian.com
   • Include:
     • Sensor ID(s)
     • Desired configuration parameters
     • Use case description (parking, loading dock, other)
     • Reason for change (if not obvious)

4. Haltian applies configuration:

   • Configuration created in Haltian Operations Cloud
   • Pushed to sensor via Wirepas mesh network
   • Update typically applied within 1-24 hours

5. Verify configuration:

   • Test sensor with vehicle present and absent
   • Confirm occupancy detection as expected
   • Monitor for 24-48 hours to ensure stable operation
   • Report any issues to Haltian support

Configuration Rollback

If new configuration causes issues:

• Contact Haltian support immediately
• Describe problem (false positives, missed detections, etc.)
• Haltian can revert to previous configuration remotely
• Or adjust to alternative settings

Multi-Sensor Configuration Management

Configuring Multiple Sensors

For deployments with many sensors:

1. Group by configuration type:

   • Group A: Parking spaces → 2m distance, 30s interval
   • Group B: Loading docks → 5m distance, 60s interval
   • Group C: Custom application → specific settings

2. Provide sensor IDs per group:

   • List all sensor IDs for Group A
   • List all sensor IDs for Group B
   • Etc.

3. Submit single request to Haltian:

   • Configuration pushed to all sensors in each group
   • Reduces coordination overhead

Configuration Templates

Reusable configuration templates:

• Define standard configurations for your organization
• Apply same template to new sensors as deployed
• Simplifies future installations

Example templates:

• Standard Parking: 2m, 30s, state change + hourly
• Standard Loading Dock: 5m, 60s, state change + hourly
• Low-Power Parking: 2m, 5 min, state change + daily

Contact Haltian to establish configuration templates for your deployment.

Monitoring Configuration Effectiveness

Verification After Configuration

Key metrics to check in IoT Studio:

1. Occupancy accuracy:

   • Does “occupied” align with actual vehicle presence?
   • Does “unoccupied” align with empty space?
   • Any false positives or missed detections?

2. Signal strength (RSSI):

   • Maintained after configuration change?
   • If degraded, may need transmission power adjustment

3. Battery consumption:

   • Monitor battery level trend over weeks
   • Excessive drain may indicate too-frequent measurements/transmissions

4. Last seen timestamp:

   • Confirm sensor reporting as expected
   • Gap > 24 hours may indicate issue

Troubleshooting Configuration Issues

False positives (occupied when empty):

• Sensing distance too long: Detecting beyond intended zone
• Solution: Reduce sensing distance

Missed detections (unoccupied when vehicle present):

• Sensing distance too short: Not reaching vehicle position
• Solution: Increase sensing distance
• Obstruction in beam path: Clear obstructions or reposition sensor

Rapid battery drain:

• Measurement interval too short: Measuring too frequently
• Solution: Increase measurement interval (e.g., 30s → 60s)
• Router role: Sensor relaying many packets
• Solution: May not be avoidable, plan for shorter battery life or add more routers

No communication:

• Mesh network issue: Sensor not reaching gateway
• Solution: Add intermediate router sensors, move gateway closer, increase transmission power

Default Configurations Reference

Parking Space Default

Loading Dock Default

Configuration Best Practices

✅ Do:

• Measure your space before requesting configuration
• Test configuration with actual vehicles/trailers
• Document configuration per sensor (map ID to settings)
• Monitor battery and detection accuracy after configuration changes

❌ Avoid:

• Setting sensing distance beyond intended monitoring zone
• Excessive measurement frequency (battery trade-off)
• Configuring all sensors identically without considering individual locations

Support Resources

For configuration assistance:

• Email: support@haltian.com
• Configuration requests: Include sensor ID, desired settings, use case
• Troubleshooting: Describe issue, provide sensor ID, current behavior vs expected

Response time:

• Configuration requests: Typically applied within 1-24 hours
• Support inquiries: Response within 1 business day