Hardware self-test codes
The hardware self-test is a check a Starlink terminal runs on its own components at boot. Nexus Telemetry Fleet reads the result and its codes every 5 minutes. Starlink publishes the result and not the meaning of the codes.
Self-test results
Terminal hardware diagnostics gives the result in the Hardware self-test row. See Diagnostics for the rest of the table and the archive.
| Result | Meaning |
|---|---|
| Passed | The terminal found no fault |
| Failed | The terminal names 1 or more codes beside the result |
| Not reported | The terminal returned no result |
Terminal state
A failed self-test does not change the terminal’s state. The dashboard shows the self-test and the state side by side, and no alert combines them. A terminal whose latency or drop rate stays above its own baseline for 15 minutes reads Warning, with the cause latency above baseline or drop rate above baseline.
Self-test codes
The dashboard shows each code by its Starlink name. The terminal’s own page at http://192.168.100.1 shows the same codes as numbers, under Diagnostics.
| Code | Name | Component in the name |
|---|---|---|
| 0 | GENERAL | Not published |
| 1 | BOOT_UP | Start-up |
| 2 | CPU_VOLTAGE | Central processing unit supply voltage |
| 3 | DBF_AAP_CS | Digital beamformer. The rest of the name is not published |
| 4 | DBF_NUM_FEMS | Digital beamformer: the number of front-end modules |
| 5 | DBF_READ_ERRORS | Digital beamformer: read errors |
| 6 | DBF_T_DIE_0 | Digital beamformer: die temperature 0 |
| 7 | DBF_T_DIE_1 | Digital beamformer: die temperature 1 |
| 8 | DBF_T_DIE_0_VALID | Digital beamformer: validity of die temperature 0 |
| 9 | DBF_T_DIE_1_VALID | Digital beamformer: validity of die temperature 1 |
| 10 | ETH_PRIME | Ethernet. The rest of the name is not published |
| 11 | EIRP | Effective isotropic radiated power, the transmit power |
| 12 | FEM_CUT | Front-end module. The rest of the name is not published |
| 13 | FUSE_AVS | Adaptive voltage scaling. The rest of the name is not published |
| 14 | GPS | Global Positioning System receiver |
| 15 | IMU | Inertial measurement unit, the tilt and orientation sensor |
| 16 | PHY | Physical layer. The interface is not published |
| 17 | SCP_ERROR | Not published |
| 18 | TEMPERATURE | Temperature |
| 19 | VTSENS | Not published |
A code outside this list appears by the name the terminal gives it.
Actions by result
| Result | Action |
|---|---|
| Failed and the terminal Healthy | Record the code. No action is required |
| Failed with latency or drop rate above baseline | Contact Starlink support with the code, the hardware version and the software version. Attach the Download archive from Terminal hardware diagnostics |
| Failed with GPS on a terminal in motion | Contact Starlink support. Starlink states that its positioning without GPS does not work in motion |
Owner reports
See Starlink’s Hidden Hardware Self-Test: What the Codes Mean for reports from terminal owners by code, and for the sources behind the names.