With the recent beta firmware adding native support for Eutelsat OneWeb alongside Starlink, InControl2 is now pulling through some really useful satellite-specific data that wasn’t available before. On OneWeb for example, we’re now seeing:
- Signal Strength (RSSI): -45 dBm
- Signal Quality (SINR): 12.4 dB
- Roundtrip Latency: ~42ms
- Look Angles, Satellite IDs, Blockage status, Temperatures
This is great visibility at the modem level, but the next logical step would be to have RSSI and SINR recorded over time and graphed in InControl2, in the same way cellular WAN signal metrics are already logged and displayed.
Why this matters for satellite specifically:
LEO satellite throughput, latency, and jitter are directly influenced by signal conditions in a way that’s often invisible without historical data. Unlike cellular where tower relationships are relatively static, satellite links are affected by:
- Weather events (rain fade, cloud cover)
- Physical obstructions entering the satellite’s orbital path
- Antenna alignment drift or mounting issues
- Environmental interference
When a customer reports degraded performance on a satellite WAN, having a timestamped RSSI/SINR graph to correlate against the throughput and latency graphs already in InControl2 would make diagnosis significantly faster and more accurate. Right now we’re flying blind, we can see that performance dropped, but not why from a signal perspective.
Request:
Extend the existing WAN signal logging/graphing functionality to cover LEO satellite connections (Starlink and OneWeb) now that the modem data is natively available via the new firmware. RSSI and SINR as a minimum.
This would bring satellite WAN reporting to parity with cellular, which already does this well, and would be a genuinely useful tool for any operator running OneWeb or Starlink as a primary or backup WAN in environments where conditions vary.
Thanks for the continued work on the LEO satellite integration, the native support is a big step forward.
