Operation

How Haltian RADAR operates, including occupancy detection, measurement intervals, reporting behavior, and battery management

How RADAR Detection Works

60GHz Pulsed Coherent Radar Technology

The Haltian RADAR uses 60GHz pulsed coherent radar to detect objects within its sensing range.

Detection principle:

Transmit: Sensor emits 60GHz radio pulses
Reflect: Pulses bounce off objects (vehicles, trailers, etc.)
Receive: Sensor receives reflected pulses
Calculate: Time-of-flight determines distance to object
Decide: Distance compared to configured threshold → occupied/unoccupied

Detection Cone

Beam angle: 17 degrees
Pattern: Conical beam from sensor face
Coverage: Widens with distance (wider at far range)
Sensitivity: Uniform across beam width

Calculation example:

At 2m distance: Beam covers ~60 cm width
At 5m distance: Beam covers ~150 cm width
At 10m distance: Beam covers ~300 cm width

This conical pattern means:

Parking: 2m distance covers typical car width perfectly
Loading dock: 5m distance covers full trailer width

Occupancy Detection Logic

Binary State: Occupied or Unoccupied

The sensor reports a simple binary state:

Occupied (true): Object detected within sensing distance
Unoccupied (false): No object within sensing distance

What Constitutes “Occupied”?

Occupied state triggered when:

Any object within configured sensing distance
Object reflects sufficient radar signal
Detection consistent over measurement interval

Examples:

Parking space: Vehicle present → occupied
Loading dock: Trailer backed in → occupied
Empty: Nothing within range → unoccupied

Detection Stability

To avoid false triggers:

Measurement interval allows filtering transient signals
Parking default: 30 seconds (quick detection)
Loading dock default: 60 seconds (more stable for large vehicles)

Edge case handling:

Partially occupied: If any part of object in range → occupied
Multiple objects: Any object in range → occupied (no counting)
Object movement: Continuous presence detected regardless of movement

Measurement and Reporting Intervals

Parking Space Configuration

Default Settings:

Sensing distance: 2 meters
Measurement interval: 30 seconds
Reporting interval: Varies by state change

How it works:

Every 30 seconds, sensor measures distance
Compares to 2m threshold
Determines occupied or unoccupied
Reports if state changed (or periodic update)

Loading Dock Configuration

Default Settings:

Sensing distance: 5 meters
Measurement interval: 60 seconds
Reporting interval: Varies by state change

Why 60 seconds?

Loading docks experience vibrations (sensor may move slightly)
Longer interval provides more stable readings
Trailers take time to position, no need for rapid detection
Battery life extended (fewer measurements)

Reporting Behavior

State change reporting:

Change detected: Report immediately at next transmission cycle
No change: Periodic reports (e.g., every hour) even if state unchanged
Battery optimization: Fewer transmissions when state stable

Example timeline - Parking:

00:00 - Measure: Empty → unoccupied (no report, same as before)
00:30 - Measure: Empty → unoccupied (no report)
01:00 - Measure: Empty → unoccupied (periodic report: still unoccupied)
01:30 - Measure: Vehicle present → occupied (STATE CHANGE → immediate report)
02:00 - Measure: Occupied → occupied (no report)
02:30 - Measure: Occupied → occupied (no report)
03:00 - Measure: Empty → unoccupied (STATE CHANGE → immediate report)

Data Transmission

Measurement Values

The sensor transmits occupancy status and distance (implementation-dependent):

Typical data payload:

{
  "occupied": true,
  "distance": 1.8,
  "battery": 95,
  "timestamp": "2025-01-14T10:30:00Z"
}

Field descriptions:

occupied: Boolean (true/false) - occupancy state
distance: Float - measured distance to nearest object (meters)
battery: Integer - remaining battery percentage
timestamp: ISO 8601 - measurement time (device local or UTC)

Over-the-Air Transmission

Wirepas Massive mesh network:

Sensor generates measurement
Transmits via Wirepas mesh to nearby sensors (routers)
Packet hops through mesh to gateway
Gateway forwards to Haltian Operations Cloud
Data visible in Haltian IoT Studio

Transmission frequency:

State change: Typically transmitted within 1-5 minutes
Periodic: Even without state change, hourly or daily updates
Battery optimized: Minimal transmissions preserve 10-year battery life

Battery Management

10-Year Non-Replaceable Battery

Battery specifications:

Type: Thionyl chloride lithium (LS33600)
Capacity: 19 Ah
Lifespan: Up to 10 years (typical usage)
Non-replaceable: Battery and sensor lifetime are coupled

Power Consumption Factors

Main power consumers:

Radar measurements: 60GHz transceiver active during measurement
Radio transmissions: Wirepas mesh communication
Standby: Minimal consumption between measurements

Battery life variables:

Measurement interval: More frequent = shorter battery life
Reporting interval: More reports = shorter battery life
Mesh hops: Router sensors transmit more (relaying packets) = shorter life
Temperature: Extreme cold reduces battery capacity

Optimizing Battery Life

Best practices:

Use default intervals: 30s (parking) or 60s (loading dock) well-optimized
Avoid over-reporting: Don’t configure unnecessary frequent transmissions
Plan mesh topology: Minimize router hops (direct path to gateway preferred)
Monitor battery level: Review in IoT Studio periodically

Expected battery life:

Parking (30s interval): ~10 years
Loading dock (60s interval): ~10+ years
Heavy router usage: 7-10 years (relaying many packets)

Battery Monitoring

Check battery level in Haltian IoT Studio:

Navigate to device list
Select RADAR sensor
View “Battery” field (percentage)
Review trend over time

Battery alerts:

Configure alerts for low battery (e.g., < 20%)
Plan replacement when < 10% (sensor is end-of-life)
Battery not replaceable → plan new sensor deployment

Distance Measurement

Sensing Range: 10 cm to 10 meters

Full adjustable range:

Minimum: 10 cm (detects very close objects)
Maximum: 10 meters (long-range detection)

Practical ranges:

Parking spaces: 1.5 - 3 meters (typical)
Loading docks: 4 - 8 meters (typical)
Special use cases: 10 cm - 10 m (full flexibility)

Distance Accuracy

Measurement precision:

Resolution: ~1 cm (radar can measure to centimeter precision)
Accuracy: ±5 cm (typical) under stable conditions
Consistency: Very stable (radar less affected by lighting, temperature than alternatives)

Factors affecting accuracy:

Object reflectivity: Metal reflects strongly, absorptive materials weakly
Angle of incidence: Perpendicular mounting best, angled OK up to 45°
Environmental interference: Minimal (60GHz relatively immune)

Interpreting Distance Values

In Haltian IoT Studio:

Distance reported: Actual measured distance to nearest object
Threshold comparison: If distance < configured sensing distance → occupied

Example:

Configured sensing distance: 2.0 meters
Measured distance: 1.8 meters → Occupied (vehicle present)
Measured distance: 5.2 meters → Unoccupied (no vehicle within 2m)

Operational Modes

Parking Space Monitoring Mode

Optimized for:

Rapid vehicle turnover (cars come and go frequently)
Quick detection (30-second interval)
Short sensing distance (2 meters)
Urban parking environments

Typical behavior:

Car parks → occupied detected in 30 seconds
Car leaves → unoccupied detected in 30 seconds
High accuracy for passenger vehicles

Loading Dock Monitoring Mode

Optimized for:

Slower trailer/truck positioning (longer dwell time)
Stable detection (60-second interval filters vibrations)
Longer sensing distance (5 meters)
Industrial environments

Typical behavior:

Trailer backs in → occupied detected in 60 seconds
Trailer pulls out → unoccupied detected in 60 seconds
Tolerates dock vibrations and movement

Custom Configurations

Adjustable via Haltian Operations Cloud:

Sensing distance: 10 cm - 10 m (set to any value)
Measurement interval: 30s, 60s, or custom
Reporting interval: Configure for application needs

Custom use cases:

Warehouse entrance: 8m distance, 60s interval
Bike rack: 1.5m distance, 30s interval
Equipment monitoring: 5m distance, 5-minute interval (battery optimization)

Environmental Operating Conditions

Temperature Range

Operating specifications:

Minimum: -35°C (-31°F) - Arctic conditions
Maximum: +85°C (+185°F) - Extreme heat, direct sunlight
Optimal: 0°C to +50°C - Most common environments

Temperature effects:

Battery capacity: Reduced in extreme cold (< -20°C)
Radar performance: Unaffected (RF stable across temperature range)
Housing integrity: MIL-STD-810H tested for thermal cycling

Humidity and Moisture

IP68 rating:

Waterproof: Continuous immersion up to 1.5 meters
Dustproof: Complete seal against dust ingress
Humidity: 0-100% RH (no condensation impact)

Real-world scenarios:

Outdoor parking: Rain, snow, ice → no impact
Loading docks: Water wash-down → sensor survives
Underground parking: High humidity → no issue

Mechanical Resilience

MIL-STD-810H tested:

Shock resistance: Vehicle bumps, impacts
Vibration tolerance: Loading dock vibrations, heavy machinery
Drop test: Survives installation handling

Practical durability:

Install in industrial environments with confidence
Withstands parking garage conditions
Loading dock vibrations don’t affect performance

Operational Best Practices

Placement for Optimal Performance

✅ Do:

Mount perpendicular to monitored area (90° angle ideal)
Clear line of sight to detection zone
Stable mounting (avoid vibration if possible, though sensor tolerates it)
Configure sensing distance to match application

❌ Avoid:

Angling sensor > 45° (reduces accuracy)
Obstructions in 17° cone (posts, signs, equipment)
Detecting beyond intended zone (false positives from adjacent areas)

Configuration Recommendations

For parking:

2m sensing distance (covers most cars)
30s measurement interval (quick turnover)
Wall/pole mount at 40-60 cm height

For loading docks:

5m sensing distance (covers dock depth)
60s measurement interval (stable detection)
Mount above dock door or on approach wall

For custom applications:

Contact Haltian support for configuration assistance
Test in real environment before full deployment
Adjust based on actual object sizes and behavior

Monitoring Sensor Health

Regular checks in IoT Studio:

Battery level: Trend over time, alert at < 20%
Last seen: Confirm recent communication (< 1 hour)
Signal strength (RSSI): Ensure > -85 dBm
State changes: Verify expected occupancy patterns

Troubleshooting indicators:

Battery drain: Faster than expected → check router usage or configuration
Missed detections: Objects not detected → verify sensing distance, check for obstructions
False positives: Occupied when empty → reduce sensing distance or check for reflections

Data Interpretation

Understanding Occupancy Patterns

Parking space analytics:

Utilization: % time occupied over day/week/month
Turnover: How many times occupied → unoccupied per day
Peak times: When parking demand highest
Average duration: How long vehicles stay

Loading dock analytics:

Dock usage: % time trucks at dock
Idle time: Dock empty but available
Loading duration: How long trailers remain (occupied time)
Scheduling efficiency: Gaps between trucks

Integrations and Downstream Use

Common integrations:

Parking guidance systems: Display available spaces
Fleet management: Loading dock scheduling
Building management systems (BMS): Occupancy data feed
Analytics platforms: Historical trend analysis

Data export:

API access to real-time occupancy data
Historical data export (CSV, JSON)
Webhook notifications on state change
Third-party platform integration via Haltian APIs

Operational Limitations

What RADAR Can Detect

✅ Detectable:

Vehicles (cars, trucks, trailers)
Large equipment
Pallets, containers (if sufficient size)
People (at close range, < 1m, though not the primary use case)

❌ Not reliably detected:

Very small objects (< 10 cm)
Radar-transparent materials (some plastics, fabrics)
Objects outside 17° cone
Objects beyond 10m

Environmental Interference

Minimal interference from:

Lighting (bright/dark doesn’t matter - radar works in complete darkness)
Weather (rain, snow, fog don’t affect 60GHz significantly)
Temperature (stable across -35°C to +85°C)

Potential interference:

Other 60GHz devices (very rare, 60GHz not commonly used)
Metal reflections (multi-path) - mitigate with perpendicular mounting
Extreme RF noise (very unusual)

Physical Constraints

Fixed sensing distance: Remotely configurable, but not auto-adjusting
Binary output: Only occupied/unoccupied (doesn’t count multiple objects)
No identification: Cannot identify specific vehicles or objects
Stationary objects: Detects presence, not movement (object can be stationary and still detected)

Support and Maintenance

Routine Maintenance

Minimal maintenance required:

Check battery level quarterly (in IoT Studio)
Verify mounting security annually (physical inspection)
Clean sensor face if heavily soiled (rare - IP68 rated)

No calibration needed:

Sensor self-calibrates
Factory settings optimized
No periodic re-calibration required

Support Contacts

For operational questions:

Email: support@haltian.com
Configuration changes: Remote sensing distance adjustments
Analytics support: Data interpretation and integration assistance

Warranty and replacement:

10-year design life (battery lifespan)
Hardware failure within warranty → replacement
Battery depletion (after ~10 years) → sensor end-of-life, replace unit