Node Network Ports for Data Output
Migrated from Original Docs/Node/Node-NetworkPorts.md
Node Network Ports for Data Output
The antenna node exposes multiple output ports for different consumer types.
| Port | Protocol | Data Type | Consumer | Format |
|---|---|---|---|---|
| 8080 | HTTP | Configuration, status | Central server REST API calls | JSON |
| 9001 | UDP or TCP (zmq) | Raw IQ samples | RF analysis, recording tools | Binary (16-bit I, 16-bit Q) |
| 9002 | UDP (multicast or unicast) | Telemetry frames and typed payloads | Central server, clients | Binary frame bytes; optional JSON objects |
| 9003 | HTTP / Prometheus | Metrics | Prometheus scraper, monitoring | Prometheus text format |
| 9004 | gRPC | Streaming status | Central server subscriptions | gRPC EventStream |
| 9005 | UDP | Heatmap data | Live spectrum or DoA visualization | Binary or JSON |
Port Specifications
Port 8080: HTTP Control & Status API
- HTTP/1.1 or HTTPS (HTTPS recommended for production)
- Authentication: Bearer token or API key
- Endpoints:
/radio/config,/pointing/az-el,/frame/config,/stream/start,/status,/capabilities,/metrics - Availability check:
GET /health(central server should poll every 10-30 seconds)
Port 9001: Raw IQ Output (Optional)
- Raw demodulated samples for advanced analysis tools
- UDP datagrams or TCP stream with I/Q 16-bit pairs
- 40 MSPS × 80 MB/s typical data rate
- Optional multicast (224.0.0.1:9001, TTL=1 link-local)
Port 9002: Telemetry Frames Output
- Telemetry frames produced by the node
- Binary frame bytes by default; optional typed JSON objects if
predecode_enabled - UDP multicast (224.0.0.1:9002) or TCP unicast
- JSON or binary format with payload ID, SNR, timestamp, frame data
- Latency target: <100 ms from RF input to frame arrival
- Central source selection happens upstream; the node is not told which stream is preferred
Port 9003: Prometheus Metrics
- HTTP GET endpoint
/metrics - Exposes: uptime, CPU load, memory, RF metrics (RSSI, SNR, frequency offset), lock state, antenna position, frame statistics
- Scrape interval: 15-60 seconds
Port 9004: gRPC Status Subscription (Optional)
- Real-time streaming status for central server
- Configurable metrics selection
- Sub-100 ms latency for status updates
Port 9005: Heatmap and Spectrum Data (Optional)
- Beam pattern, DoA heatmap, or spectrum waterfall
- UDP multicast or TCP
- 1 heatmap/second typical update rate
Related: See Node-ConfigurationProtocols for port 8080 API details.